1
Stage 1
Geocode and classify the service location
Capture intent and source evidence without inventing a more precise state than the inputs support.
Production solution blueprint
Dispatch the right technician, with the right proof
Turn outages or service requests into skill-aware, route-efficient field jobs.
Business outcomeHigher first-time-fix rates and auditable work from dispatch through customer sign-off.
The operating situation
A utility receives a no-power complaint for a commercial unit. Dispatch must resolve the service point, choose a technician with the correct certification and inventory, survive an offline basement visit, collect readings and imagery, route weak proof to review, and close the job only after the provider and customer records agree.
Service requesterDispatcherTechnicianProof reviewerOperations manager
Keep authority explicit across the stack
01Work-order systemOwns customer/service asset, SLA, required skills, inventory, commercial outcome, and the authoritative terminal status.
02Spatial service contextSearch, asset layers, and mGIS context bind the request to a stable service location, access notes, network assets, and hazards.
03Workmate lifecycleProvider task identity mirrors explicit create, assign, accept, travel, arrive, prove, review/rework, and close transitions through an outbox/callback boundary.
04Technician experienceMobile guidance, offline command queue, checklists, evidence capture, and conflict UI operate under scoped task and consent policy.
05Operations and analyticsOwned exception/review queues, audit, repeat-fault spatial analysis, and SLA metrics derive from immutable task/evidence history.
From intent to reconciled outcome
2
Stage 2
Assign by skills, shift, inventory, and ETA
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
3
Stage 3
Guide the technician
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
4
Stage 4
Collect checklist, image, and signature proof
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
5
Stage 5
Analyze repeat faults spatially
Reconcile the terminal result to every authoritative system and retain attributable evidence.
Records that must survive restarts and retries
Work order ↔ service asset/location ID, SLA, skill and inventory requirements
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Assignment ↔ technician eligibility snapshot, ETA evidence, policy version
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Offline command ↔ stable idempotency key, expected aggregate version, device time
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Proof ↔ immutable submission ID/hash, consent, accuracy, checklist, reviewer decision
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Design recovery before rollout
Technician accepts while another assignment races
Use optimistic aggregate versions and one active assignment invariant; surface conflict instead of last-write-wins.
Offline commands replay after reassignment
Validate actor, task version, and transition preconditions for every queued command; retain rejected evidence.
Proof is incomplete
Move to named review/rework with reason and a new submission identity; never overwrite the rejected attempt.
Products and evidence
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.GIS & AnalyticsSpatial data, analysis, maps, dashboards, and embeddable location intelligence.
stateful
Field-service task lifecycle
Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.
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.
hybridRecoverable navigation session
Move from route intent through preview, guidance, reroute, arrival, and cleanup while surviving process, sensor, and network interruption.
hybridGoverned spatial analysis
Ingest versioned data, validate and publish it, execute reproducible analysis, review lineage, and share a governed decision layer.
Earn the right to automate
1
Rollout gate
Model task states and audit without provider mutation
2
Rollout gate
Connect one Workmate sandbox team through outbox and signed reconciliation
3
Rollout gate
Pilot offline-safe execution and proof review for one job type
4
Rollout gate
Add skill/ETA-assisted assignment in recommendation mode
5
Rollout gate
Scale with policy versioning, workforce consent, retention, and support certification
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 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.
AdvancedConsume Mappls events exactly once in effect
Verify signatures, deduplicate deliveries, order per aggregate, retry, and replay safely.
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.