What to inspect after impacts and how to document.
After impact or misuse, inspect fast and methodically. Check bollard structures and sleeves, control/safety functions (342–345), and foundations/paving for movement or cracking (333–334, 626). Capture evidence (716), apply clear return-to-service criteria aligned to rating-critical dependencies (421), and weigh repair vs replacement (842). Feed findings into incident response (547) and design lessons (844). 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.
735.1 Trigger events
Impact, EFO misuse, flooding, power anomalies (518). Triggers protect HVM bollard safety.
Establish clear power failure modes triggers and visible cues (unusual permanent set, oil on paving, fault beacons). Typical triggers include any vehicle strike (even glancing), repeated Emergency Modes & incident response, actuator stalls, flood ingress beyond design limits, or unexplained alarms. Treat “near-miss” contact and vandalism as triggers too; both can knock sensors out of tolerance.
Use a simple decision gate: “Is anyone at risk? Is the lane safe to hold?” If not, proceed to cordon and isolation before any close inspection.
| Aspect | What matters | Where to verify |
|---|---|---|
| Certification | As-tested configuration & footing remain intact | Rating-critical dependencies |
| Controls | Modes, interlocks, safe local mode | Interlock Matrix Verification |
735.2 Safety cordon & LOTO
Secure area; isolate systems (725). Cordon prevents crash rated bollard secondary harm.
Set an LOTO boundary sized to debris risk and public proximity. Use modes of operation to place lanes in Safe Local or Maintenance mode, then prove-dead (electrical) and bleed hydraulic pressure where applicable. Record who holds the locks (group lock box) and log temporary bypasses if any are required to stabilize the site.
- Block vehicular approach vectors with cones/barriers; brief stewards on safe egress lines.
- Confirm zero unexpected motion with a try-start check after isolation.
735.3 Structural checks
Heads, sockets, foundations, surrounding slabs (331–333). Checks decide HVM bollard serviceability.
Visually scan for deformation, torn welds, cracked foundation collars, and spalled paving. Measure tilt and rotation against baseline marks; note any uplift of sleeves or rocking under push. Look for shear rings of broken grout, loose anchor templates, or grout voids around rails/sockets.
Check the surrounding slab and joints for new cracking patterns radiating from the array. Record gap drift and effective width changes across the lane; these can indicate footing rotation or group stiffness loss in arrays. Where damage is suspected below grade, schedule a localized breakout or non-destructive test before any return-to-service.
735.4 Controls & wiring
Panel ingress, terminations, fault logs (347, 541). Controls confirm crash rated bollard integrity.
Open enclosures and check for water marks, IP rating breaches, and loose terminations. Review the fault log & counters around the incident time to correlate alarms with operator reports. Verify ferrules and trunking integrity; inspect loop feeder joints, photo-eye leads, and safety-edge whips for strain or cuts.
If flooding occurred, check power test points, IR/continuity on critical circuits, and look for nuisance trips from wet devices before proceeding to functional tests.
735.5 Sensor alignment
Re-aim beams/loops; retune (344–345). Alignment restores HVM bollard detection.
Re-aim photo-eyes to recover the designed driver cone and egress cone; fit beam hoods if glare increased after an impact. For loops, confirm geometry (lead-in twists, base inductance) and retune sensitivity to avoid cross-talk with adjacent lanes. Use a Loop Placement Helper where alignment lines were disturbed by paving repairs.
735.6 Functional proving
Run interlock and stop tests (634–635). Proving validates crash rated bollard readiness.
Execute a reduced-risk script: dry-run I/O, then single-cycle movements under stewards. Prove interlocks, obstruction/intrusion, and mode authority including E-stops. Compare cycle time and ops/hour to baseline; abnormal lag may indicate hidden mechanical damage or hydraulic bypass.
735.7 Documentation
Incident report, photos, measurements (716). Docs support HVM bollard claims.
Capture a wide→detail photo set (geo-tagged if possible), measurement notes (tilt, rotation, gap drift), and device logs. File the pack under the site’s File Index & Naming Rules, and raise an NCR if acceptance criteria were breached. Link the event to the Asset Register & Serials.
735.8 Repair & replacement path
Criteria for swap vs remedial works. Path preserves crash rated bollard certification (421).
Use the rating-critical dependencies to decide if repairs compromise as-tested geometry, footing, or anchorage. Where sockets, rails, or cages are distorted, replacement of the tested system (not just the sleeve) is often required to maintain certification integrity. Coordinate parts under the Warranty & Spares Policy and document any concessions for the audit trail.
735.9 Return-to-service
Sign-offs and update of 731/732. RTS keeps HVM bollard records accurate.
Only release lanes after supervisor sign-off confirming structural checks, controls proving, and safety devices. Update As-Built Drawings & Models and the Asset Register with any component swaps, serials, and revised alignments. If flooding or corrosion was involved, schedule accelerated inspections in the Preventive Maintenance Plan until trend data stabilizes.
Related
External resources
735 Post-incident inspection of HVM/Crash-Rated Bollards — FAQ
What should be checked first after a suspected impact?
Make the area safe, then isolate power (LOTO). Visually scan for deformation, loose sleeves, new cracks in paving, and leaking fluids. Only after cordon and isolation should close inspections begin.
Does minor contact require a full inspection?
Yes. Even glancing contact can misalign sensors or introduce small footing rotations. Complete structural, controls, and functional checks before returning to service.
How do we decide between repair and replacement?
Use rating-critical dependencies: if as-tested geometry, anchorage, or footing are compromised, replace the tested system (not just the sleeve) to preserve certification integrity.
What records must be updated before return-to-service?
Update the Asset Register with serial changes, the As-Built drawings with any geometry updates, and file the incident pack under the site’s naming rules. Schedule follow-up checks if water or corrosion were factors.