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
- Integrations and source ownership
Integrations and source ownership
Connect outage reports, network systems, crews and identity with clear ownership.
- Utility Outage Management
- Outage reports and contact centre
- Network operations and SCADA
- Field crew devices
- Identity provider
Systems to connect
-
Outage reports and contact centre. Bring reports in as service cases with their external incident ID so duplicates are recognised.
-
Network operations and SCADA. Outage detection and telemetry stay in network systems; agree which events open cases and which acknowledgements they provide.
-
Field crew devices. Send crew evidence with its source and measured values.
-
Identity provider. Map staff to team members and user accounts.
How connections are governed
Each connection needs an agreed source of truth, a field mapping, an event identifier and a retry policy. Keep credentials in the approved secret store with the smallest scope that works. A repeated delivery must not create a second case or evidence line. Rejected records wait with their identifier and a visible reason.
Reconcile cases with your outage reporting source daily during the pilot. Test a duplicate report, a missing evidence source and a revoked credential before turning on schedules. Availability depends on each provider’s interface, commercial access and configuration.
Use the implementation plan to agree integration acceptance criteria.
Set up Utility Outage Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.