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
- Restoration records
Restoration records
Confirmed restoration and approved outage incident records.
OverviewIncidents awaiting decision×
Utility Outage Management · Restoration records
New
Incidents awaiting decision
Approval waits for the utility supervisor
| Id | Parent | Service area | Started at | Restored at | Affected customers | |
|---|---|---|---|---|---|---|
| IDD-390 | SC-60281 | SA-844 | 14 Oct | 23 Oct | 510 | |
| IDD-859 | SC-95055 | SA-494 | 04 Oct | 12 Oct | 280 | |
| IDD-606 | SC-63697 | SA-815 | 22 Oct | 30 Oct | 480 | |
| IDD-547 | SC-11850 | SA-545 | 05 Oct | 07 Oct | 270 | |
| IDD-776 | SC-31593 | SA-571 | 24 Oct | 02 Nov | 150 |
6 of 6 records
IDD-390Outage incidents · OI-47696
ParentSC-60281
Service areaSA-844
Started at14 Oct
Restored at23 Oct
Affected customers510
What you can do
Record restoration once, with the evidence behind it
Restoration is confirmed from authorised crew evidence. The coordinator restores the case with the real restoration time, after the system checks the organization, the case’s current revision and that the confirmation comes from the coordinator assigned to the case. The confirmation writes an operation receipt, so it cannot be applied twice. A local confirmation never stands in for an acknowledgement that should come from telemetry or a remote-control system.
Each outage also gets an incident record for reporting: the service area, when the outage started, how many customers were affected and when service was restored. The coordinator submits the record. An independent supervisor approves it against the field evidence and the frozen revision, and the verified restoration is recorded once.
How the work is organized
The coordinator confirms restoration and prepares the incident record; the supervisor approves the record.
- Evidence first. Restoration needs crew evidence; the incident record needs the supervisor’s approval.
- Real times. Start and restoration times are what actually happened, not when the record was typed.
- Recorded once. Repeated confirmations or approvals return the first result.
What to agree during setup
Agree what counts as restored for each outage type and who confirms it. Agree how affected customers are counted for incident records and who approves them before they go into regulatory or management reports. Prepare examples of a straightforward restoration, a confirmation sent twice, an incident record returned for a wrong start time and a partial restoration.
Check the handoff on an actual case
After the storm the coordinator confirms restoration on the feeder case at 23:05, from the crew’s evidence. The next morning they submit the incident record with the service area, a start time of 18:20, 640 affected customers and restoration at 23:05. The supervisor checks it against the evidence lines, approves it, and the verified restoration is recorded for the monthly reliability report.
What your team sees
- Incidents awaiting decision — Submitted incident records for the supervisor.
- Outage incident board — Incident records by status.
- Restored cases — Restored and closed cases with report and restoration times.
Follow the work through
- Incident record approval: From restoration to an approved record.
See reports built on incident records.
What it keeps track of
Data model- Outage incidents
- Outage incident records supporting record verified service restoration.
- Service cases
- Outage service cases from report through verified restoration.
- Service evidence
- Source-identified operational evidence received against a service case.
- Review decisions
- Independent reviewer decisions recorded against a frozen revision.
Who uses it
Permissions- Outage Coordinator
- , Utility Supervisor.
- The coordinator confirms and submits; the supervisor approves.
Set up Utility Outage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.