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
- Implementation and migration
How a Utility Outage Management rollout works
Start with one district's service areas and a month of outages.
Agree the operating boundary
The system holds cases, evidence, reviews, incident records and operation receipts. Outage detection, telemetry and customer notifications stay in connected systems. The utility decides priorities and when service counts as restored.
Map the source data
Agree service area codes, case numbers and which external incident ID to keep. Load open cases and recent incidents.
Configure a bounded pilot
Run one district for a month: triage, evidence review, restoration and incident approval.
Rehearse the exceptions
A repeated confirmation never restores twice, a coordinator cannot approve their own incident record, restoration needs crew evidence, and a duplicate external incident is not entered twice.
Reconcile and release
Compare cases and restoration times with your current records, get sign-off from the supervisor and agree the rollback window.
What the customer provides
- Service areas with codes, contacts and notes.
- Open cases and recent incidents with their external IDs.
- The evidence each outage type needs.
- The team with their roles and areas.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the supervisor and replay the pilot’s exception cases before release. Approved incident records keep the rules that applied when approved.
Set up Utility Outage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.