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 cases
Service cases
Outage reports from intake to closure.
OverviewCases awaiting review×
Utility Outage Management · Service cases
New
Cases awaiting review
Service cases
| Record number | Subject | Counterparty | Affected units | Reported at | Revision | |
|---|---|---|---|---|---|---|
| SC-28361 | Review sc-933 | SA-4540 | 730 | 10 Oct | 290 | |
| SC-44786 | Review sc-396 | SA-5861 | 210 | 03 Oct | 920 | |
| SC-77283 | Review sc-985 | SA-8423 | 50 | 05 Oct | 860 | |
| SC-92522 | Review sc-797 | SA-6590 | 500 | 17 Oct | 500 | |
| SC-66186 | Review sc-785 | SA-6861 | 450 | 23 Oct | 230 |
6 of 6 records
Review sc-933Service cases · SC-28361
CounterpartySA-4540
Affected units730
Reported at10 Oct
Revision290
What you can do
One case for every outage, from the first call to closure
A service case is the record of one outage: the subject, the service area it affects, the asset involved, how many units are without service, when it was reported and, once fixed, when service came back. The case moves from reported to triaged, assigned, under review, restored and closed. Its revision number rises with each change, so an action taken on an out-of-date view of the case is refused rather than applied to the wrong state.
When an outage is first logged in another system, such as a call centre platform or an outage map, its external incident ID is kept on the case. That stops the same outage being entered twice when it is reported through more than one channel. Each case has an owner, the coordinator responsible for seeing it through.
How the work is organized
The outage coordinator owns the case; the supervisor reviews it; the field crew supplies evidence.
- One case per outage. Duplicate reports of the same incident are matched on the external incident ID rather than opened again.
- Affected units on the case. The number of units out of service is recorded at intake and kept current, so priorities are clear.
- Closed only after restoration. A case closes only once restoration has been confirmed and recorded.
What to agree during setup
Agree where outage reports come from and which system’s incident ID is the one to keep. Agree how affected units are counted (meters, customers or premises) and who may close a case. Decide what makes a case high priority. Prepare examples of a single-street outage, a feeder outage reported many times, a case that turns out not to be an outage and a case reopened after a second failure.
Check the handoff on an actual case
At 18:20 a storm takes out a feeder serving two neighbourhoods. Calls come in through the contact centre and the outage map. The first report opens a service case with its external incident ID and 640 affected units; later reports with the same ID are recognised as the same outage. The coordinator owns the case through triage, field work and review. When the crew’s evidence confirms power is back, the case is restored with the real restoration time and then closed.
What your team sees
- Open service cases — Reported, triaged, assigned and in-review cases with affected units.
- Case status board — Every case grouped by status.
- My service cases — Each coordinator’s own cases.
Follow the work through
- Report to restoration: The full path of an outage case.
Review the implementation plan before connecting outage reports.
What it keeps track of
Data model- Service cases
- Outage service cases from report through verified restoration.
- Service areas
- Districts, circuits and service territories where outages are reported.
- Organizations
- Utility operating companies and their operating configuration.
Who uses it
Permissions- Outage Coordinator
- , Utility Supervisor.
- The coordinator owns cases; the supervisor follows them through review.
Set up Utility Outage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.