These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Utility Outage Management
- Features
- Service areas
Service areas
Districts, circuits and territories with contacts.
OverviewActive service areas×
Utility Outage Management · Service areas
New
Active service areas
Service areas
| Code | Name | Contact name | Eligibility note | |
|---|---|---|---|---|
| CDE-460 | Area 367 | Contact 467 | EN-836 | |
| CDE-295 | Area 180 | Contact 756 | EN-606 | |
| CDE-877 | Area 489 | Contact 199 | EN-939 | |
| CDE-613 | Area 478 | Contact 528 | EN-727 | |
| CDE-275 | Area 110 | Contact 222 | EN-314 |
6 of 6 records
CDE-460Service areas · SA-51287
NameArea 367
Contact nameContact 467
Eligibility noteEN-836
What you can do
Organise outages the way your network is organised
Service areas are the districts, circuits and territories where outages are reported. Each has a code, a name, a contact, an address and an eligibility note that records anything special about it, such as hospitals on the circuit or restricted access roads. Areas belong to an organization and can be made inactive without losing their history.
Cases are recorded against a service area, so the open cases, affected units and restoration times for each area can be seen together. The contact on the area is the person the coordinator calls when an outage there needs local knowledge.
How the work is organized
The admin maintains areas; coordinators work cases within them.
- Every case in an area. Cases are always tied to a service area.
- Notes that matter. Eligibility notes flag critical customers or access constraints.
- Contacts on hand. Each area names its contact.
What to agree during setup
Agree how your network divides into service areas and how they are coded, matching your outage reporting and network records. Agree what goes in the eligibility note, such as critical customers, access or safety constraints. Decide who keeps area contacts current. Prepare examples of an outage crossing two areas, an area with a hospital and an area being retired.
Check the handoff on an actual case
The storm affects two circuits. Each has its own service area, so the coordinator sees open cases and affected units per circuit. One area’s note flags a dialysis clinic, so its case is triaged first and the area contact is called to confirm access to the substation.
When the storm has passed, the manager compares the two areas. One had most of the affected units but was restored faster because the crew could reach the substation easily. The other had fewer customers out but a longer restoration time because of a flooded access road noted on the area. That comparison comes straight from the cases recorded against each area.
What your team sees
- Active service areas — Areas with codes, contacts and notes.
- Open service cases — Cases by area.
Follow the work through
- Report to restoration: How areas shape triage.
Check the data model before loading areas.
What it keeps track of
Data model- Service areas
- Districts, circuits and service territories where outages are reported.
- Service cases
- Outage service cases from report through verified restoration.
- Organizations
- Utility operating companies and their operating configuration.
Who uses it
Permissions- Admin
- , Outage Coordinator.
- The admin maintains areas; coordinators use them.
Set up Utility Outage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.