This customization allows you to display on the Dashboard outage statistics using Network Level groupings. This control will appear on the Analytical tab.

In order for this configuration to work, you must follow the steps below, and you must have Network Level fields configured in your geodatabase. The Network Level fields allow you to filter outage data based on custom groupings. The Network Level section on the Dashboard displays outages by Network Level groupings determined by an Administrator. Any outage features that do not have an assigned Network Level grouping (or value) are displayed as "Unspecified".

1. Open the Web.config file. This file is installed here: C:\Inetpub\wwwroot\Responder.
2. Look for the following XML:

   Copy Code

   <!--<add key="service.providerKeys" value="customerStatus, crewStatus, incidentStatus, wiresDownStatus, regionAreaPath, affectedLoadPoints, incidentDevicePoints, hazardPoints, callStatus, outageMonetaryStatus, networkLevelStatus" />--> <add key="service.providerKeys" value="customerStatus, crewStatus, incidentStatus, wiresDownStatus, regionAreaPath, affectedLoadPoints, incidentDevicePoints, hazardPoints, callStatus, outageMonetaryStatus" />

3. The first line in the example above includes the Network Level statistics. Remove the comment tags on this line (highlighted in the example above.
4. The second line in the example above does NOT include the Network Level statistics. Add comment tags to this line to comment it out.
5. Look for the following XML:

   	Copy Code
   <!--<add key="service.networkLevelStatus.type" value="Miner.Responder.Web.DataProviders. NetworkLevelStatusProvider, Miner.Responder.Web.DataProviders"/> <add key="service.networkLevelStatus.incidentCauseFilter" value="10"/> <add key="service.networkLevelStatus.incidentTroubleFilter" value="1 2 3"/> <add key="service.networkLevelStatus.incidentStatusFilter" value="2 3 4 5 6"/>-->

6. Remove the comment tags (highlighted in the example above).
7. The incidentCauseFilter, incidentTroubleFilter, and incidentStatusFilter all correspond with specific domains in the Responder geodatabase. Note that these filters are exclusive.

   incidentCauseFilter: This value corresponds to the Cause domain (0=Unknown; 1=Weather; 2=Vegetation; 3=Animals; 4=Foreign Interference; 5=Human Cause; 6=Planned Outage; 7=Undetermined; 8=Equipment Failure; 9=All Remaining; 10=Non-Outage). All values listed are excluded from the statistics displayed on the Dashboard. In the example above, incidents that have a Cause value of 10 are excluded from the statistics.

   incidentTroubleFilter: This value corresponds to the Trouble domain (0=No Power; 1=Partial Power; 2=Flickering Lights; 3=High Voltage; 4=Low Voltage; 6=Other). All values listed are excluded from the statistics displayed on the Dashboard. In the example above, incidents that have a Trouble value of 1, 2, or 3 are excluded from the statistics.

   incidentStatusFilter: This value corresponds to the Status domain (0=Created; 1=Crew Assigned; 2=Restored; 3=Completed; 4=Rolled Up; 5=Cancelled; 6=Closed). All values listed are excluded from the statistics displayed on the Dashboard. In the example above, incidents that have a Status of 2, 3, 4, 5, or 6 are excluded from the statistics.

8. Look for the following XML:

   	Copy Code
   <!--<add key="dashboard.grid.controlKeys" value="customerStatus, incidentStatus, crewStatus, wiresDownStatus, callStatus, outageMonetaryStatus, networkLevelStatus" />--> <add key="dashboard.grid.controlKeys" value="customerStatus, incidentStatus, crewStatus, wiresDownStatus, callStatus, outageMonetaryStatus" />

9. The first line in the example above includes the Network Level statistics. Remove the comment tags on this line (highlighted in the example above.
10. The second line in the example above does NOT include the Network Level statistics. Add comment tags to this line to comment it out.
11. Look for the following XML:

    	Copy Code
    <!--<add key="dashboard.grid.networkLevelStatus.path" value="~/Controls/NetworkLevelInformationControl.ascx" />-->

12. Remove the comment tags (highlighted in the example above).
13. Save and close Web.config.