Overview#
A distribution utility's outage management team receives a high-voltage fault alarm at 02:15. To coordinate the response, they need the asset location from the GIS, the customer impact count from the CIS, the crew assignment from the work management system, and the estimated restoration time from the field team's tablets. In most utilities, pulling that information together means switching between four separate systems while a customer communications team waits for data to update their IVR. Utility Enterprise Connectors make those systems aware of each other through a governed integration layer, so the outage workflow draws on live context from every connected platform.
The module provides a managed integration fabric for utility, infrastructure, and public operations environments. It connects mapping, telemetry, maintenance, customer, scheduling, and collaboration systems through repeatable connector patterns rather than brittle point-to-point integrations. The result is an operating environment where dispatch, outage response, field work, and customer-impact decisions share the same live data.
Open Standards#
- OPC Unified Architecture (IEC 62541): The SCADA telemetry adapter interoperates with OPC-UA REST gateways, consuming OPC-UA data model constructs including NodeId, StatusCode, ConditionType, and sourceTimestamp to normalise substation and pump-station readings into the integration fabric.
- OGC API Features (OGC 17-069r4): A dedicated integration client and domain implement the OGC API Features protocol, syncing geospatial feature collections from GIS servers with coordinate reference systems resolved against the OGC CRS84 definition URI.
- AVEVA PI Web API: The connector integrates with AVEVA PI System via its published REST specification, querying data streams, executing batch requests, and traversing the PI Asset Framework hierarchy through the
/piwebapi/endpoint contract. - OAuth 2.0 (RFC 6749): The ArcGIS Enterprise connector acquires short-lived tokens via the OAuth 2.0 client-credentials grant, and connector-to-registry heartbeat calls are authenticated with RFC 6750 Bearer tokens.
- GraphQL (June 2018 Specification): All connector configuration, telemetry queries, outage management operations, and OGC feature sync are exposed through a GraphQL API, with the connector registry, utility telemetry, and outage domains each defining typed GraphQL schemas.
- OASIS Common Alerting Protocol 1.2 (CAP 1.2): The connector registry recognises CAP 1.2 as a first-class output contract that connectors may declare, enabling utility connectors that emit emergency or outage alerts to express conformance to the OASIS emergency-messaging standard.
- ISO 8601: All timestamps across the integration fabric, including sync events, telemetry readings, alarm triggers, and outage lifecycle transitions, are serialised as ISO 8601 date-time strings to ensure interoperable time exchange between connected systems.
Last Reviewed: 2026-03-25 Last Updated: 2026-04-14
Key Features#
- Enterprise System Adapters: connect mapping, telemetry, enterprise asset management, work management, customer, and productivity systems through governed connector patterns that version independently from the source systems
- Operational Sync Scheduling: control full, incremental, and event-driven synchronisation through configurable schedules and health-aware sync policies that pause or retry based on downstream system availability
- Cross-System Context Bridging: align telemetry, outage, customer, maintenance, and location data so each operational workflow has the right context at the moment a decision needs to be made, not minutes later
- Outage and Work Coordination: link customer impact, asset state, work execution, and restoration activity across connected systems so the entire outage lifecycle is visible in one place
- Directory and Collaboration Context: bring communications and workforce context into operational workflows where assignments, notifications, and reviews depend on shared system state
- Connector Health and Governance: track connector readiness, status, and operational trust so teams know when a downstream system is stale or degraded before that data influences a field decision
- Standards and Contract Discipline: apply versioned integration contracts and repeatable connector patterns instead of custom one-off mappings per deployment, reducing maintenance burden and improving reliability
Use Cases#
- Outage Response Fusion: combine telemetry alarms, mapping context, customer records, and maintenance systems into one outage workflow so response coordinators have complete situational awareness from the first alert
- Field Maintenance Coordination: keep work management, location context, and asset state aligned as crews move from dispatch through completion, preventing the information lag that causes avoidable return trips
- Customer Impact Operations: connect restoration activity to affected customers, service areas, and communication workflows for higher-quality updates that reduce inbound call volume during outages
- Infrastructure Modernisation: introduce shared connector patterns that reduce integration duplication while preserving the systems utilities already depend on and trust
Integration#
- Enterprise mapping, telemetry, work-management, customer, and productivity platforms
- Outage, work-order, restoration, and dispatch workflows
- Sync scheduling, connector governance, and data-quality services
- Zone hierarchy and service-territory intelligence
- All connector configuration and sync logs scoped to the organisation with a complete audit trail