Pedestrian Detection System Check

This check verifies detection equipment on mobile plant on a monthly cycle. It is not the daily pre-use check, not a defect report, and not an assessment of whether the right system was chosen. Mixing those together produces a monthly record full of shift-level noise and a scoring trend that means nothing.

The template is built against ISO 45001 clause 8.1, operational planning and control, with the supporting clauses that make a fitted device a maintained control rather than a purchase.

No major jurisdiction mandates pedestrian detection on mobile plant outright. All of them require the risk to be controlled and any fitted safety device to be maintained, which is the obligation this check evidences.

Four judgements decide whether this check is worth running. The rest of the form is verification of things you can see.

These are the findings that recur wherever this check is run for more than a quarter, with the clause each one touches.

A distribution centre fitted tag-based proximity detection across twenty-two counterbalance trucks after a serious near miss at a dock door. Commissioning set the detection zone at six metres, which in a narrow-aisle operation meant an alarm every few seconds whenever anyone picked nearby. Monthly checks passed cleanly for eight months: powered, detecting, alarming, sensors clean, tags charged.

The near miss that prompted the review happened at the same dock door. Sixteen of the twenty-two cab speakers had been packed with foam or turned to minimum, and pickers had stopped wearing tags because the constant alarming made operators short with them. Every one of those trucks had passed its check the previous week. The functional questions were answered correctly; nothing on the form asked whether the alarms were believable or whether anyone still reacted. That is the gap Tuning and use exists to close.

The hardware questions look after themselves. What slips is the cycle, the follow-through on defects, and noticing that nuisance alarming has risen for three months before somebody tapes over the speaker.

KnowFleet

Holds the check against the plant register, schedules the cycle per system rather than per machine, and flags any unit still in service past its next check date.

KnowMaintain

Carries the work order from a failed item through to verification, so the next check starts from a known repair rather than the same defect logged again.

KnowSafe

Links the check to the pedestrian assessment and near miss reporting, so a No on segregation reaches the risk assessment instead of a maintenance queue.

Ella

Tracks the trends that decide whether the system really works — false alarm counts, repeat defects, bypass findings — and holds every write for approval before it touches a record.

Proximity detection system

Equipment that senses a person within a defined zone around plant and warns the operator, the pedestrian, or both. Usually tag-based, radar or vision.

Detection zone

The commissioned distance and shape within which the system triggers. Widening it reduces missed detections and multiplies nuisance alarms: the tuning trade-off.

Alarm desensitisation

The progressive loss of operator response to a warning that fires too often to be informative. The end state is a system technically working and practically inert.

Hierarchy of controls

The ordered preference for eliminating, substituting, engineering out, administratively controlling and finally protecting against a hazard. Detection sits low in it.

Segregation

Physical separation of pedestrians from mobile plant by barriers, routes and time. The higher-tier control detection backs up rather than replaces.