Utility Zone Fusion

Overview#

During a major storm, a utility's outage management coordinator needs to know which field crews are already working inside the affected feeder zone, which customers in that zone are flagged as critical (dialysis patients, medical equipment users), and whether the neighbouring distribution zone shares any assets that could be rerouted to restore power faster. That question crosses at least three different zone definitions: the operational feeder zone from the GIS, the customer sensitivity zone from the CIS, and the work assignment region from the work management system. Without a unified zone model, answering it takes calls and manual lookups.

Utility Zone Fusion provides a hierarchy-aware location framework that reconciles geographic definitions from multiple source systems into a single operational model. Dispatch, outage response, maintenance, and public coordination all draw on the same zone intelligence, so the boundaries they work with are consistent and current.

Open Standards#

• GeoJSON (RFC 7946): Zone boundary polygons are stored, ingested, and emitted in GeoJSON; the ST_GeomFromGeoJSON / ST_AsGeoJSON PostGIS calls confirm that all spatial boundaries exchanged between source systems and the fusion engine conform to this format.
• OGC Simple Features (ISO 19125) via PostGIS: Spatial predicates (ST_DWithin, ST_Contains, ST_SetSRID) used for outage scope resolution and point-in-zone queries implement the OGC Simple Features geometry model with coordinates referenced to EPSG:4326 (WGS 84).
• WGS 84 / EPSG:4326: All zone centroids and boundary geometries are stored and queried using the WGS 84 geographic coordinate reference system, ensuring interoperability with external GIS and mapping systems.
• ArcGIS REST API (Esri): The platform ingests zone definitions from ArcGIS Enterprise MapServer / Feature Service layers via the Esri ArcGIS REST specification, translating features into the unified zone model with cross-source fusion links.
• OPC UA (IEC 62541): Facility-level zone data is correlated with real-time substation and pump-station telemetry ingested through OPC UA SCADA gateways, enabling zone-aware alarm detection and outage propagation.
• GraphQL (June 2018 Specification): The full zone hierarchy API, queries, mutations, and live subscriptions, is exposed via a typed GraphQL schema, allowing external systems to retrieve zone trees and subscribe to outage scope updates using a standard query language.
• WebSocket (RFC 6455): Real-time outage zone scope updates are pushed to connected clients over authenticated WebSocket connections, enabling field crews and dispatch teams to receive boundary changes without polling.

Last Reviewed: 2026-03-25 Last Updated: 2026-04-14

Key Features#

• Hierarchical Zone Model: manage nested service areas, districts, feeders, response regions, and temporary operational zones within one structure, so every level of the organisation works from the same geographic frame
• Cross-Source Zone Fusion: reconcile overlapping zone definitions from mapping, operational, and infrastructure systems into a single usable field model, removing the ambiguity that causes coordination failures during multi-system incidents
• Outage Zone Context: attach affected assets, customers, and work to the correct outage geography for prioritisation and restoration planning, with automatic updates as the outage boundary changes
• Crew and Assignment Routing: use zone intelligence to direct crews and tasks to the right area with clearer ownership boundaries, reducing duplication and missed areas during large-scale response events
• Emergency Overlay Support: combine day-to-day service territories with incident, hazard, or contingency overlays during abnormal operations, such as storms, contamination events, or major infrastructure failures, without disrupting the underlying permanent zone model
• Zone-Aware Analytics: review response, restoration, workload, and impact data by operational geography rather than raw asset lists, making it easier to identify which zones are consistently underperforming or overloaded
• Mapping and Operational Consistency: keep map views, work execution, and customer impact reporting aligned to the same zone model so every team sees the same boundaries

Use Cases#

• Service Territory Operations: understand which customers, assets, and crews sit inside each operational territory at any given moment, combining data from systems that previously held separate geographic definitions
• Outage Prioritisation: focus restoration decisions based on zone impact, customer criticality, and field conditions, with the zone model providing the shared frame that dispatch, field crews, and communications teams all use
• Cross-Agency Coordination: share a common geographic frame when utilities, PSAP teams, and field responders need aligned boundaries during joint responses to infrastructure incidents
• Temporary Incident Control Areas: create and manage dynamic operational zones during storms, contamination events, or major infrastructure failures, with those zones visible across all connected systems in real time

Integration#

• Enterprise mapping and connector services for zone definition synchronisation
• Outage, work-order, restoration, and dispatch workflows for zone-based routing and prioritisation
• Service-territory, customer, and infrastructure intelligence platforms
• Mobile responder and field-routing applications for on-device zone awareness
• All zone data scoped to the organisation with a complete audit trail on every zone change and overlay activation