Overview#
Utilities incidents are geographic, customer-visible, and politically noisy. A damaged feeder, a flooded district metered area, or a gas escape is simultaneously a network problem and a list of households who will call within minutes. Operators who live in that world should not have to hunt through investigator menus or type raw identifiers into forms designed for another industry. They need the zone hierarchy, the activity inside a service zone, and the impacted customer roster, with an authority lens that suggests dispatch-shaped navigation without granting unrelated privileges.
The Utilities Operator Workspace gathers those flows for people holding utilities operator authority. On console and on mobile-worker utilities workflows, staff browse the utility zone tree, open service-zone activity, and work an impacted-customer roster for the event in front of them. auth_service utilities roles participate in lens suggestion so a utilities dispatcher can land somewhere that looks like their job. Downstream field features (equipment bay, vulnerable persons near a job, fireground-adjacent hazmat lookups when the incident demands them) remain available through the wider mobile worker suite without forcing utilities staff to become investigators.
For multi-utility and municipal buyers comparing Argus to standalone OMS/DMS companions, this workspace is the customer-facing proof that utilities is a first-class operating mode on the platform, not a renamed public-safety screen.
Last Reviewed: 2026-09-15 Last Updated: 2026-09-15
Key Features#
-
Zone tree browse: Operators walk the utility zone hierarchy for their tenant and select the geographic scope that drives activity and customer views.
-
Service-zone activity lists: Open or recent activity inside the selected zone stays scoped to that zone so control rooms are not flooded with unrelated network noise.
-
Impacted customer roster: Customer-operations staff see who is affected by the current utilities event or outage context and can drive outbound messaging or field follow-up from the same picture.
-
Authority-aware entry: auth_service utilities roles appear in lens suggestion and authority catalogues so utilities operators are not forced through investigator-first navigation.
-
Picker-first field patterns: Mobile worker utilities flows follow the wider platform move away from typed UUIDs toward list pickers for vehicles, equipment, and related entities, reducing field error under gloves and glare.
-
Shared mobile worker adjacency: When a utilities job overlaps fireground hazmat, vulnerable persons, or equipment status, responders reuse the hardened mobile worker panels rather than a second app.
-
Honest empty and denied states: Missing zones, empty rosters, and unauthorised deep links use the shared UI language introduced across fe2 audits.
Use Cases#
-
Storm and flood desks: A network controller selects a damaged zone, reviews activity, and opens the impacted-customer roster for proactive contact while crews are still en route.
-
Gas escape or water burst: Field supervisors keep zone context on a handset, including nearby vulnerable persons disclosures when policy allows, without switching into a police RMS mental model.
-
Municipal multi-utility operations: Organisations running electric, water, and gas under one tenant give each crew a utilities-shaped entry while RBAC still separates who can action which network.
-
Executive situational awareness: Duty managers use the roster and activity lists for briefings without needing full administrative rights.
Integration#
Utility domain services supply zone, activity, and customer roster data. fe2 hosts console surfaces and mobile-worker utilities workflows. Navigation Operator Lens suggests utilities-relevant landings from auth_service role strings. Workforce and responder mobile clients carry the field half of the experience. Customer notification can connect through Tenant Notification Channels when outbound messaging is configured for the tenant.
Open Standards#
- CIM (IEC 61968 / 61970): Zone and network concepts can align with Common Information Model naming when customers map their GIS that way.
- GS1 / GLN: Site and facility references may use global location identifiers shared with inventory modules.
- OAuth 2.0 / OIDC: Operator identity and tenant binding use the platform auth stack.
- WCAG 2.2: Console and mobile controls meet the platform accessibility baseline.