Readiness checks: power, loops, signage, and access control.
Commissioning success is planned months ahead. Lock in witness points, test lists, and evidence standards (631–638, 716), reserve tools/spares, and define temporary protection for HVM bollard equipment. Arrange safe access, logging sheets, and clear roles that align with control logic tests (342–355). Use objective Go/No-Go criteria so the SAT (638) closes cleanly with documents ready for handover (736, 739). Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
249.1 What to plan early
Witness points, scripts, tools, and spares (631–638, 529). Early planning prevents HVM bollard SAT drift and readies crash rated bollard evidence (716).
Start with a commissioning roadmap tied to the Pre-Commission Checklist (631). Define scope boundaries, dependencies, and the state machine states to be proven. Book the SAT window early and publish a simple RACI so everyone knows who runs scripts, who witnesses, and who signs.
Pre-agree your test sequence: power health (632), induction loops and photo-eyes (633, 345), interlocks (634, 352–355), performance/duty (636), and EFO/failure modes (637). Tie each to an evidence artifact (photo set, counters, signature). This reduces back-and-forth and keeps the day focused on proving outcomes, not debating process.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested barrier + footing; rating assumptions | Crash standards overview |
| Operations | Duty cycle, fail-state, safety devices & measures | Installation Guide |
249.2 Evidence & witness points
Define photos, forms, and sign-offs (714, 638). Evidence proves HVM bollard behavior and preserves crash rated bollard compliance (431).
Decide exactly what “proof” looks like before testing. Use the Inspection & Test Plan (ITP) (714) to list witness points, photo angles (photo/redline logbook 937), counters, and signatures. Align your “as-tested configuration” with drawings (731) and serials (732) so later maintenance and claims match what was actually proven.
For UAE jobs, note if a SIRA observer is expected; include SIRA Bollards (UAE) in the pack cover sheet. Evidence should be atomic (each test = self-contained proof) and chained (index, filenames, and sign-offs) to support the certificates & documentation (431).
249.3 Commissioning test list
List loops, interlocks, alarms, EFO, and duty (344–345, 342, 354, 636). Tests validate HVM bollard lanes and adjacent crash rated bollard safety zones.
Structure your list from safe-to-risky: (a) power & controller health (632, 520–526), (b) sensor proving (633–345), (c) interlocks and interlock matrix (634, 352), (d) duty/performance (636), and (e) EFO & failure modes (637, 355).
Include negative tests (intrusion/obstruction 635) and edge cases: tailgating, signage/markings visibility (357), and manual release behavior. For each, define inputs (e.g., loop simulator), expected state transitions, timeouts, and alarms reported to BMS/SCADA (533–536).
249.4 Tools & spares
Simulators, gauges, oils, and fuses (529, 512–513). Right kit sustains HVM bollard uptime and protects crash rated bollard hardware.
Bring the essentials: loop simulator, multimeter/insulation tester, gap gauge, spare fuses/relays, hydraulic oil (for HPUs, 512), and a USB with latest PLC program & I/O list (523, 537). Add PPE, signage covers, and cleaning kit to keep photos legible.
Stock minimal spares that unblock testing without turning the site into a store: 1–2 spare photo-eyes & beacons (345, 353), one control card, and one actuator/valve kit where lead time is critical.
249.5 Temporary protection
Guard heads, sockets, and panels from works damage (611). Protection keeps HVM bollard finishes and the crash rated bollard base intact.
Before testing, shield vulnerable parts: bollard heads, sleeves, and control panels. Use breathable wraps and rigid guards that don’t impede movement. Keep pits dry (245, 616) and verify gland plates (622) are sealed. Temporary plates over open sockets prevent trip hazards and keep debris out of the drainage path (334, 616).
249.6 Access & safety arrangements
Set barriers, permits, and isolation points (723, 514). Safe access preserves HVM bollard integrity and prevents crash rated bollard strikes.
Mark an exclusion zone with barriers and a stewarded perimeter. Prepare PTWs, toolbox talks, and hold points. Confirm isolation/LOTO (725) for adjacent equipment and identify a “latched safe” state for each lane. During live movement, keep a single test conductor on the HMI with clear voice comms to spotters.
249.7 Data capture sheets
Standardize logs, counters, and defect lists (541–542, 716). Data supports HVM bollard KPIs and crash rated bollard closeout (938).
Use pre-printed forms for each test: inputs, expected outputs, counters, and pass/fail with notes. Enable controller fault logs & counters (541) and set KPI thresholds (542) so run-time evidence is visible. File names should match your submission index (938) for frictionless review.
249.8 Roles & responsibilities
Name testers, witnesses, and approvers (131). Clear roles shorten HVM bollard SAT and stabilize crash rated bollard sign-offs.
Create a one-page RACI: Accountable owner, test lead, safety steward, client/authority witness, and approver. Include escalation path, decision windows, and who can stop works (safety first). Share 72 hours before SAT with contact numbers and arrival instructions to reduce churn on the day.
249.9 Go/No-Go criteria
Define pass thresholds and blockers (433, 714). Criteria prevent partial HVM bollard handovers and protect crash rated bollard claims.
Turn each test into an objective decision: what metric, what tolerance, what evidence. Examples: cycle time within acceptance band; loop hold/release times; alarm routing to BMS within X seconds; spec clauses (433) met; all hold points cleared (714). If a blocker appears (e.g., water ingress, unsafe signage sightlines), pause, record an NCR (719), and reschedule—no partial sign-offs.
Related
External resources
- NPSA: Hostile Vehicle Mitigation overview
- ASTM F2656: Crash testing for vehicle security barriers
- ASIS: Security Risk Assessment Standard
249 Pre-commission planning for HVM Bollards — FAQ
What’s the minimum we must prepare before turning power on?
Have the Pre-Commission Checklist completed, isolation/LOTO verified, a signed ITP with witness points, tested emergency stops, and loop/photo-eye simulators on hand. Confirm the as-tested configuration matches drawings and serials.
Who needs to be present during SAT and what do they do?
The test lead executes scripts, the safety steward controls the exclusion zone, the client/authority witness observes and signs, and the approver confirms contractual acceptance. Use a one-page RACI with contacts and escalation.
How do we prove safety devices & measures are working?
Run sensor proving (loops/photo-eyes), obstruction/intrusion tests, and interlock checks. Record counters, alarms, and time-stamped photos. Failures are logged as NCRs and retested after fixes.
What triggers a No-Go decision?
Uncontrolled water ingress, failed isolation, non-functional safety devices, out-of-band cycle times, unresolved hold points, or missing evidence artifacts. Stop, log, and reschedule rather than accept partial sign-offs.