Service Territory Domain

Overview#

A field technician is dispatched to a fault reported at a specific GPS coordinate. Before the crew rolls, the work order system queries the Service Territory domain to confirm which feeder area that coordinate falls within, then routes the job to the crew assigned to that zone. No manual lookup, no dispatcher guesswork. The Service Territory domain manages the geographic boundaries that drive this kind of automatic routing: named zones with polygon boundaries, classified by territory type and utility type, each with customer counts and crew assignments to support planning as well as dispatch.

Key Features#

• Territory Definition: Define service territories with geographic boundaries, categorised by type (service area, district, feeder area, pressure zone, grid sector) and utility type (electric, water, gas, sewer, telecom, waste).

• Geographic Boundary Management: Store and manage territory boundaries as geographic shapes, enabling spatial queries to determine which territory covers a given location for automatic routing.

• Point-in-Territory Lookup: Determine which service territory contains a specific GPS coordinate, enabling automatic territory assignment for incidents, customers, and field operations.

• Territory Statistics: View summary statistics including territory counts by type, customer distribution, and population estimates to support operational planning.

• Customer and Population Metrics: Track key metrics for each territory including customer count, population estimates, and primary crew assignments.

• Search and Filtering: Search territories by name, code, type, or utility classification to quickly locate relevant service areas.

Use Cases#

Service territory management is fundamental to any utility or infrastructure operation where work must be routed to the right crew for the right area. Key industries include electric power, water and wastewater, and gas distribution.

• Incident Routing: Automatically determine which service territory an incident falls within to route work orders and dispatch the correct crew.

• Coverage Analysis: Evaluate territory boundaries relative to population centres and infrastructure to identify underserved areas and plan expansion.

• Regulatory Reporting: Report on service territory metrics including population served and area covered to satisfy regulatory requirements.

• Resource Planning: Use territory metrics to plan crew assignments and equipment positioning based on the characteristics of each service area.

Territory Types#

Integration#

The Service Territory domain supports geographic operations across the platform:

• Work Order Management: Territory assignments drive crew dispatch and work routing
• Utility Infrastructure: Physical assets are associated with their service territory
• Incident Management: Incidents are mapped to the appropriate territory
• Customer Management: Customer accounts are linked to their service territory

Open Standards#

• OGC Simple Features for SQL (ISO 19125): Territory boundaries are stored as PostGIS GEOMETRY(POLYGON, 4326) columns and point-in-territory lookups use ST_Contains and ST_MakePoint, which implement the OGC Simple Features geometry model and spatial predicate interface.
• EPSG:4326 / WGS 84 (ISO 6709): All geographic boundaries and coordinate pairs are expressed in the WGS 84 coordinate reference system (SRID 4326), ensuring interoperability with GPS receivers, mapping platforms, and other geospatial systems.
• OGC GiST Spatial Indexing: Boundary and centre-point columns are indexed with PostGIS GiST indexes, conforming to the OGC spatial index model to accelerate point-in-polygon containment queries at scale.
• GraphQL (June 2018 Specification): The territory query and mutation interface is fully exposed via a typed GraphQL schema, enabling structured queries, filtering, and pagination for any GraphQL-compatible client.
• OAuth 2.0 / JSON Web Tokens (RFC 6749 / RFC 7519): All territory operations require a validated JWT bearer token, with access control enforced at the resolver level against the authenticated tenant context.
• JSON / JSONB (RFC 8259): Territory metadata is stored and exchanged as JSON, with PostgreSQL JSONB used for efficient server-side storage and indexing of arbitrary key-value attributes.
• ISO 8601: All audit timestamps (created_at, updated_at) are stored as timezone-aware values and serialised in ISO 8601 format, ensuring unambiguous temporal representation across integrations.

Last Reviewed: 2026-02-24 Last Updated: 2026-04-14