Lo que el programa ofrecía.
Alertas de proximidad vehículo–peatón en los puntos ciegos.
Responsabilidad de personal en el momento de la convocatoria.
Responsabilidad en evacuación vs llamada manual.
Composite worked example — figures are ranges from comparable programmes, not attributed named-client results. Named references available under NDA. We model your own numbers when you engage.
El reto
Los puntos ciegos alrededor de maquinaria pesada suponen un riesgo de fatalidad. La concentración manual es lenta e incierta cuando los minutos importan.
Nuestro enfoque
- UWB / etiquetas de proximidad para zonas de detección de vehículo y peatones.
- Alertas en cabina y control de velocidad por zona.
- Puntos de concentración en tiempo real con verificación de personal.
- Trabajador solitario y coacción en zonas aisladas.
- Integra con sistemas de seguridad y flota.
Tecnología e integración
Pila desplegada: UWB / proximidad RTLS, dispositivos portátiles robustos, unidades en cabina; LoRaWAN para área amplia.
Integración: Sistemas de seguridad / EHS, gestión de flotas, control de acceso.
Relacionado: Minería RTLS · Seguridad minera y concentración · UWB vs BLE
Programme pattern for this vertical
Surface and underground mines typically phase collision avoidance: instrument a high-risk fleet slice and one production level, prove escalating proximity zones and in-cab alerts, then expand. UWB or dedicated proximity radios dominate where GNSS fails; LoRaWAN often carries wide-area telemetry and SOS.
Integration targets are EHS incident systems, fleet dispatch and access control — not a standalone safety app. Mustering is usually co-designed so the same wearable identity supports evacuation headcount.
Outcomes to expect — and how they are earned
Comparable programmes aim for fewer vehicle–pedestrian near-misses in instrumented zones, faster verified muster, and a review ritual that ties alerts to coaching — not mute fatigue. Figures vary with fleet mix and culture; we model yours from baseline near-miss and roll-call data.
Success looks like supervisors trusting the alert ladder and workers trusting that privacy is limited to safety purposes.
Lessons from comparable programmes
Failure modes: alerting without zone calibration in metal-dense headings; no ownership of false-positive review; treating lab ranging specs as underground truth; skipping union/workforce consultation on wearables.
Keep productivity tracking out of the safety business case. It poisons adoption.
Deeper problem framing
Haul-truck and light-vehicle interactions in pits, plus pedestrian exposure at crushers and workshops, create fatality risk that radio call-outs cannot manage at shift scale. Near-miss reporting is inconsistent; culture may punish reporting. Underground headings add multipath and infrastructure limits that invalidate open-pit GNSS assumptions.
Procurement pressure often pushes 'collision avoidance' as a single SKU. In practice you are buying a system of wearables, vehicle units, alerting logic, training and EHS review rituals.
Approach that survives underground and surface reality
Phase instrumentation on the worst fleet segment; calibrate escalating zones with operators aboard; integrate alerts into in-cab workflow without mute culture; co-design muster identity on the same wearable where possible.
Run RF surveys in representative headings, not only workshops. Define false-positive review owners before go-live. Align with existing isolation and traffic management rules so digital alerts do not contradict site law.
Outcome bands and measurement discipline
Comparable programmes seek fewer serious near-misses in instrumented zones, faster verified headcount in drills, and a coaching loop tied to alert data. Exact percentages vary; measure your own baseline for 4–8 weeks first.
Exclude lab ranging sheets and any period without a live review ritual from claimed success.
Governance, risk and what we refuse to claim
These pages remain composite worked examples — not named-client results. We will not attribute percentages to a confidential site. When you engage, we rebuild baselines from your incidents, labour samples and system logs.
We refuse vanity accuracy claims without a coverage map, and we refuse programmes that silently add productivity surveillance onto a safety business case without a fresh DPIA or labour consultation.
Implementation sequence and change management
Week 0–2: baseline near-miss and roll-call timing; traffic rules review; union/workforce briefing on safety-only purpose. Week 3–6: instrument pilot fleet and one level; calibrate zones with operators; mute-prevention training. Week 7–12: expand fleet; connect EHS logging; first scored drill.
Budget for spare wearables, charger discipline and a named false-positive owner. If supervisors treat every alert as noise, redesign zones before buying more tags. Technology last — traffic management and training first.
Competitive note: several proximity vendors will claim plug-and-play. Ask for underground references, spoofing/security posture, and integration to your incident system — not only ranging charts.
Última actualización: