What is an outage management system?
An outage management system (OMS) is the software at the centre of how an electricity distributor handles loss of supply. It answers the questions every network control room needs answered during an event: what is off, where, how many customers are affected, why, who is working on it and when it will be back.
An OMS is used by electricity distribution businesses in New Zealand and DNSPs in Australia, and similar systems exist for gas and water networks. It is used for both planned and unplanned outages.
How an OMS works
Most outage management systems bring together several sources of information:
- A network model. Usually drawn from the GIS, it shows how every customer connects through transformers, feeders and substations.
- Network monitoring. Alarms from SCADA and smart meters show when devices trip or supply is lost.
- Customer fault reports. Calls to the fault line, web forms and app reports, each tied to an address or connection point.
- Crew information. Job status, crew locations and restoration progress, often linked to a work management or field crew dispatch system.
From these, the OMS groups individual reports into incidents. If ten customers on the same transformer report no power, the system can predict that the transformer or its fuse is the likely cause, rather than raising ten separate jobs. As crews switch sections back on, the OMS tracks which customers are restored and which are still off.
Why the OMS matters to the contact centre
During an outage, most callers want to know two things: whether the network already knows, and the estimated time of restoration. Both answers come from the OMS. That makes the link between the OMS and the contact centre one of the most important integrations a utility has.
Good outage information flows in both directions:
- From the contact centre into the OMS. Accurate, fast fault logging gives the control room the location data it needs, particularly on parts of the low-voltage network that aren’t directly monitored.
- From the OMS to customers. Outage status and restoration times feed agents’ screens, IVR announcements, outage maps and proactive outage notifications.
When that link is weak, agents give out-of-date information, customers hear different restoration times from different channels, and repeat calls multiply.
Common problems to plan for
- Stale restoration times. An ETR that isn’t updated as conditions change creates repeat calls and complaints.
- Duplicate jobs. Without good address matching, one fault can generate many jobs.
- Single-channel updates. Information that reaches the website but not the IVR or AI assistant leaves callers with less information than web users.
- Performance under load. The OMS, outage map and contact centre systems all face their highest demand at the same moment. Load-testing them together before storm season is worth the effort.
- Missing vulnerability data. Restoration priorities and welfare checks depend on knowing where medically dependent consumers are affected.
Outage data also feeds reliability reporting. The start and end times recorded in the OMS are the raw material for SAIDI and SAIFI calculations.