Train operators, FM, and security on real workflows. Set outcomes, build modules around modes/interlocks (525, 352), signage/markings (357, 353), and EFO/overrides (354). Include hands-on drills and assessments, then record attendance and sign-offs. Feed feedback into O&M and dashboards (733, 544) so day-to-day use of HVM bollards and crash rated bollards remains safe and consistent. This page sits under this section and the broader chapter hub. Where UAE authority approvals are in scope, align deliverables with SIRA Bollards (UAE). If training involves live movement, see Installation Guide and What to Expect for safe interfaces.
737.1 Audience mapping
Operators, FM techs, security, management. Mapping tailors HVM bollard training.
Start with a role map that distinguishes day-to-day operator workflows from technical maintenance and incident leadership. For each audience, define outcomes (e.g., safe local control for operators, planned maintenance for FM). Use a simple ITP alignment so demonstrations match witnessable points.
Document access levels and the alarm philosophy they’ll see on site. Security teams need hazard awareness around the modes of operation; FM techs need HMI familiarity; managers focus on sign-off criteria and escalation.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read crash ratings |
| Operations | Duty cycles, fail-state, safety devices | Installation Guide |
737.2 Syllabus
Modes, alarms, EFO, resets (525, 536, 354). Syllabus prevents crash rated bollard misuse.
Build modules around the modes, interlocks, and signage/markings so trainees always read the lane correctly. Include alarm states, acknowl./silence rules, and typical recoveries. Teach EFO initiation, cooldown, and reset hierarchy.
Close with fault-aware workflows (e.g., loop failure, power events) and hand-offs to escalation. Keep each lesson outcome-based and refer back to the site’s FDS and I/O list for local specifics.
737.3 Practical drills
Hands-on sequences and fault sims (632–637). Drills harden HVM bollard response.
Run live sequences with barricaded zones, a spotter, and a pre-commission checklist mindset. Demonstrate raise/hold/lower, queue clearing, and safe local mode with two-person confirmation. Capture timings so operators appreciate cycle time and KPIs.
Simulate common issues: loop inhibited, sensor proving failure, interlock conflict, or E-stop. Use structured “talk-through, do-through, teach-back” so participants can recover confidently and log what happened using the evidence standards.
737.4 Assessments
Written/practical with pass marks. Assessments confirm crash rated bollard competence.
Assess knowledge with short scenarios and practical demonstrations (raise/hold/lower, safe recovery from a latched fault). Define pass marks per role and record any remedial training. Practical sign-off should include correct use of HMI indicators, interlock matrix awareness, and communication discipline on radios.
Map each assessment item to an ITP witness/hold point where applicable and keep scripts aligned with SAT procedures. Store results in the project’s O&M manual annex and the organization’s training register.
737.5 Refresher cadence
Annual or after incidents/changes (718, 735). Cadence sustains HVM bollard capability.
Set a baseline annual refresher for all operators and first responders, then trigger interim refreshers after any configuration change (change control), incident (post-incident inspection), or staffing turnover. Use short “micro-sessions” to reinforce high-risk tasks like EFO and manual recovery.
Tie refresher frequency to measured performance: if fault counters or alarm floods spike, increase cadence for the affected shifts. Record all sessions in the handover pack index with dates, topics, and attendees.
737.6 Materials & aids
Quick cards, videos, HMI screenshots (524). Aids improve crash rated bollard recall.
Provide laminated quick cards for lane states, a one-page EFO checklist, and a reset hierarchy card placed near local controls. Embed short clips or GIF-style loops in the O&M (733) showing correct button sequences and annunciator behavior. Include annotated HMI screenshots and lane signage examples from Safety Signalling.
Where cyber policy allows, host materials on an internal portal and log access. For UAE sites requiring documentation parity, package a bilingual set for SIRA contexts and keep a one-page index of all training assets.
737.7 Trainer qualifications
Approved vendor or certified instructor. Qualification ensures HVM bollard accuracy.
Trainers should be approved by the product vendor or carry demonstrable experience with the installed family/variant. They must be competent in the site’s state machine, local MS/RA, and commissioning history. Keep CVs, certificates, and a brief “trainer method statement” on file, and note any language coverage for multi-lingual crews.
For witnessed sessions, log the lead witness name and reference the witness procedure. Where authorities require it, include a trainer accreditation letter in the submission pack.
737.8 Records & certification
Certificates linked to personnel IDs (716). Records support crash rated bollard audits.
Use a standard attendance sheet with printed names, signatures, roles, and unique personnel IDs. Attach the pass/fail sheet and practical checklist for each attendee. Issue named certificates that reference role, scope, pass mark, and expiry date, and file them in the project’s final archive with a searchable filename convention.
Log records in the asset & people register or the client’s HR training system. For gated sites, add a rule in operator workflows: no panel access until in-date certification is verified.
737.9 Feedback loop
Collect suggestions; update 711/733. Loop evolves HVM bollard practice.
At session close, run a short survey and an after-action review to capture unclear steps, nuisance alarms, or signage gaps. Feed changes into the FDS (711) and O&M manuals (733) so future trainees see the updated truth. Summarize trends on operational dashboards.
Where a change impacts behavior or ratings dependencies, follow change control and schedule a micro-refresher. Close the loop by noting outcomes in the handover pack index.
Related
External resources
- NPSA: Hostile Vehicle Mitigation (overview)
- FEMA 426 / DHS: Reference Manual
- ASIS: Risk Assessment Standard
