Move material safely across a changing mine

Version haul roads and exclusion zones, dispatch compatible equipment, track cycles, and reconcile safety and production evidence.

Business outcomeHigher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses.

The operating situation

A blast changes the active pit and closes a ramp midway through a shift. Dispatch must publish the newly approved road and exclusion-zone version, reassign compatible trucks and loaders, guide offline-capable cycles, distinguish telemetry delay from a stopped vehicle, preserve safety interventions, and reconcile production only from accepted load and dump evidence.

Mine dispatcherPit supervisorHaul-truck operatorGeotechnical engineerSafety and production reviewer

Keep authority explicit across the stack

01Mine plan and safety authorityThe mine system of record owns surveyed geometry, blast areas, geotechnical restrictions, road classes, equipment compatibility and operating authorization.
02Versioned offline map releaseApproved pit, road, zone and configuration manifests move through signed dual-slot qualification and rollback before vehicles activate them.
03Dispatch aggregateApplication state owns shift, equipment/operator assignments, load/dump targets, priorities, expected versions and deliberate cancellation.
04Haul-cycle evidenceInTouch observations and offline commands derive travel, queue, load and dump stages by event time while keeping raw source identity and freshness.
05Safety and production reconciliationGeofence or route exceptions stop automatic progress and require human review; tonnes and cycles close only against authoritative scale and dispatch evidence.

From intent to reconciled outcome

1
Stage 1

Publish the approved pit, road, and exclusion-zone version

Capture intent and source evidence without inventing a more precise state than the inputs support.

2
Stage 2

Assign compatible equipment and operators

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

3
Stage 3

Guide and observe offline-capable haul cycles

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

4
Stage 4

Stop and review safety or geofence exceptions

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

5
Stage 5

Reconcile tonnes, cycles, maintenance, and shift closure

Reconcile the terminal result to every authoritative system and retain attributable evidence.

Records that must survive restarts and retries

Mine map package ↔ survey/version, region, signature, compatibility and approval

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Assignment ↔ equipment/operator capability, shift, plan version and expected aggregate version

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Cycle event ↔ source/content identity, event/receipt time, map version and stage

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Safety exception ↔ zone/rule version, accuracy, intervention and reviewer decision

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Production result ↔ accepted load/dump identities, tonnes, shift and reconciliation status

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Design recovery before rollout

A truck wakes with the previous pit map

Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.

Telemetry silence looks like an idle vehicle

Separate freshness from motion state, show last verified evidence, and ask dispatch to reconcile rather than charging productive-time loss automatically.

Duplicate dump evidence inflates tonnes

Deduplicate by source/content and cycle identity, reject conflicting replays, and reconcile against the authoritative scale record.

Products and evidence

Earn the right to automate

1
Rollout gate

Version one pit and equipment compatibility matrix

2
Rollout gate

Prove offline package update and rollback on representative hardware

3
Rollout gate

Run haul cycles in shadow mode with event-time reconciliation

4
Rollout gate

Pilot safety exception review and authoritative scale matching

5
Rollout gate

Expand after geotechnical, functional-safety, workforce, cyber, environmental and emergency-response approval

Measure the outcome

Tonnes per operating hourCycle-time varianceGeofence exceptionsUnplanned equipment idle time

Tutorials and downloadable applications

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

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.

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.