1
Stage 1
Version the network and hazard context
Capture intent and source evidence without inventing a more precise state than the inputs support.
Production solution blueprint
Restore the grid from alarm to verified service
Correlate network alarms, weather exposure, switching plans, field crews, and restoration evidence.
Business outcomeFaster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk.
The operating situation
A monsoon storm trips feeders across two districts while flood exposure changes road access by the minute. Grid operations must correlate alarms against an exact network version, estimate affected service points, obtain an independently approved switching plan, dispatch capable crews, preserve every field observation, and avoid declaring restoration until telemetry and customer-impact evidence converge.
Grid control operatorOutage coordinatorSwitching authorityField crewCustomer-impact lead
Keep authority explicit across the stack
01Network and hazard authorityThe utility system of record owns assets, connectivity, protection settings, switching authority and customer-service relationships; versioned mGIS layers add terrain, flood, access and vegetation context without replacing that authority.
02Outage correlationAppend-only alarms and calls map to exact network versions and form bounded incidents under a versioned correlation rule with operator correction.
03Switching and dispatchAn application-owned plan separates electrical safety approval from skill-, equipment- and ETA-aware Workmate assignments; no map or route result authorizes switching.
04Field executionOffline-safe tasks, route evidence, asset identity, observations and proof submissions preserve stable command IDs, expected versions and event/receipt time.
05Restoration reconciliationClosure requires authoritative device state, switching completion, crew evidence and customer-impact recovery; mismatches remain an owned exception.
From intent to reconciled outcome
2
Stage 2
Correlate alarms into bounded outage incidents
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
3
Stage 3
Approve a switching and crew plan
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
4
Stage 4
Guide crews and capture field evidence
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
5
Stage 5
Reconcile telemetry, customer impact, and restoration
Reconcile the terminal result to every authoritative system and retain attributable evidence.
Records that must survive restarts and retries
Grid asset ↔ topology/configuration version, owner and safety class
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Alarm ↔ source/event/content identity, event/receipt time and mapped asset
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Switching plan ↔ exact assets, sequence, approver, version and expiry
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Crew task ↔ eligibility snapshot, route evidence, provider identity and proof
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Restoration ↔ telemetry, customer-impact and operator reconciliation evidence
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Design recovery before rollout
Many alarms collapse onto the wrong feeder
Retain each source alarm, topology version and correlation reason; require operator correction and create a new incident revision rather than rewriting prior evidence.
A road route crosses a newly flooded segment
Append the hazard revision, invalidate the route identity, keep the switching plan separate, and require dispatch to approve a safe replacement.
Crew completion arrives before telemetry recovery
Keep the task evidence complete but the outage in reconciliation; query authoritative device and customer-impact sources before closure.
Products and evidence
GIS & AnalyticsSpatial data, analysis, maps, dashboards, and embeddable location intelligence.InTouch TelematicsLive tracking, trips, devices, vehicles, events, geofences, and fleet intelligence.WorkmateWorkforce automation for people, clients, tasks, attendance, proof, and live operations.Routes & NavigationRoutes, matrices, optimization, map matching, predictive ETAs, and turn-by-turn navigation.Capture & FeedbackOn-demand location capture, camera evidence, map feedback, and update workflows.
stateful
Field-service task lifecycle
Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.
statefulConnected fleet trip
Provision an observable trip, follow live vehicle state, explain exceptions, close deliberately, and retain a replayable operational record.
statefulFleet geofence exception
Create a governed zone, evaluate vehicle activity, suppress noise, raise an actionable case, and retire the rule safely.
statefulCoordinated incident response
Resolve an incident location, select a capable available responder, route and observe the unit, adapt to hazards, establish arrival, resolve with evidence, and review every decision.
Earn the right to automate
1
Rollout gate
Reconcile one feeder model and its ownership
2
Rollout gate
Replay historical storms through correlation in shadow mode
3
Rollout gate
Pilot approved switching plus offline crew evidence
4
Rollout gate
Require multi-source restoration reconciliation in one district
5
Rollout gate
Expand after electrical-safety, privacy, resilience, workforce and regulatory review
Measure the outcome
Tutorials and downloadable applications
Intermediate
Build a route preview with alternatives
Resolve endpoints, request alternatives, decode geometry, and explain toll/time trade-offs.
AdvancedTrack a delivery with a trustworthy ETA
Join asset telemetry, map matching, route progress, ETA refresh, and customer visibility.
AdvancedAutomate a complete Workmate task lifecycle
Provision workers, dispatch jobs, consume transitions, enforce proof, and reconcile closure.
AdvancedBuild fleet geofence operations
Create zones, process enter/exit events, suppress noise, and power an exception queue.
AdvancedBuild a reproducible site-selection model
Publish layers, generate catchments, join signals, score candidates, and share results.
IntermediateGive an AI agent grounded Mappls tools
Run the MCP server, scope credentials, call search and routing tools, and inspect provenance.
Advanced · verified app
Grid Restoration Desk
Correlate an outage, govern independent switching approval, dispatch an assigned crew, preserve rework, and reconcile restoration from telemetry and customer-impact evidence.
Advanced · verified app
Care Transfer Desk
Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.
Advanced · verified app
Airside Turnaround Desk
Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.