We piloted the system on two 40-tonners this week and the alarms curbed those close passes at the portal without killing our cycle time. For those who’ve taken this from pilot to full deployment, how did you keep compliance high and nuisance alarms down while protecting load counts?
On the “keep compliance high and nuisance alarms down while protecting load counts?” piece, switching from distance-based alerts to time-to-collision with zone profiles (portal/ramp/dump) and blocking mute while in gear cut nuisance about 60% without touching cycle… Did your pilot log speed vectors so you can tune TTC per zone off the first week’s near-miss replays?
Since your “two 40‑tonners” at the portal didn’t hurt cycle time, the single change that kept our compliance high was tying tag heartbeat to dispatch — no job drops until the unit’s tag checks in at lineup; we took a about 30‑second hit at start of shift, but load counts held and nuisance complaints fell once dead/missing tags stopped triggering junk alerts. Do you have a way to block assignments when a tag hasn’t reported?
I hear you on the nuisance alerts. In our mine, we found that calibrating the system for each specific zone really minimized false alarms. It helped us maintain focus on real hazards without annoying the crew.