When an underground incident occurs, time and visibility matter. Missing Miner is an applied R&D capability that improves who-is-where visibility underground and gives response teams a repeatable coordination path under pressure.
What this capability delivers
This capability brings together:
- Real-time personnel visibility to support accountability and rapid triage
- Response workflows that help teams coordinate actions under pressure
- Communication support patterns for constrained underground environments
- Safety analytics that turn events and near-misses into leading indicators
Outcomes you can expect
- Reduced time-to-action during emergencies through clearer visibility and coordination
- Stronger incident reporting and post-event review with better evidence
- Improved operational readiness through repeatable drills and workflows
- A safer baseline by identifying patterns before they become incidents
Who it is for
Mining operations that need accurate underground personnel visibility, drill-tested incident response, and reporting that supports compliance and continuous improvement.
How it works in practice
We design the system around the full response lifecycle:
- Before incidents: readiness, coverage strategy, and operational responsibilities
- During incidents: visibility, escalation paths, communications, and coordination
- After incidents: review, evidence capture, and measurable improvement actions
The specific technology stack and deployment topology depend on your environment (infrastructure, connectivity, and constraints). The guiding principle stays the same: reduce uncertainty and increase coordination when it matters most.
Typical deliverables
- Personnel visibility and accountability workflow design
- Incident response playbooks and escalation paths
- Dashboards and reporting outputs aligned to operational roles
- Data retention and audit readiness approach
- Rollout plan that starts with priority areas and adds coverage incrementally
Common questions
Does this require perfect connectivity underground?
No. We design for constrained environments and emphasise workflows that still function under partial failure, with synchronisation and evidence capture when connectivity returns.
How do you avoid adding operational burden?
By aligning the solution to existing roles and routines, minimising manual steps, and focusing on a clear operating model for who owns what.