Recap of HVM principles: energy, standoff, penetration, rating.
This page translates building threats into concrete HVM bollard requirements. Start with VDA results (221–229) to choose rating/tier (432–435), then lock arrays and clear gaps (321–322, 232). Foundation feasibility (331–333), drainage (334, 245), and controls/safety (341–357) complete the system. We signpost evidence/documents (431, 938), human factors for daily use (215, 353), and maintenance planning (734, 842) to keep crash-rated performance intact. Include context links up to this section and the chapter hub. For UAE projects, align any approvals with SIRA Bollards (UAE) as required. For delivery details, see What to Expect and the 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.
371.1 HVM vs low-speed recap
Low-speed handles bumps and misparking; an HVM bollard addresses deliberate, higher-energy impacts (123, 434). Use crash rated bollard certificates to prove energy and penetration limits (431, 413).
Low-speed systems (e.g., ASTM F3016 storefront tests) are designed for accidental roll-aways and driver error. Hostile Vehicle Mitigation (HVM) focuses on intentional, higher-energy strikes proven by standards such as IWA 14-1 / ASTM F2656. For buildings, start by clarifying the threat scenario and desired stand-off.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read crash ratings |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
371.2 Threat→requirement chain
Translate VDA outcomes into tier/rating, then arrays and foundations (221–235, 321, 332). This chain keeps HVM bollard intent traceable to a crash rated bollard model.
Summarize VDA inputs—vehicle class, approach speed/angle, run-up—and map them to a performance tier using the Purpose→Tier Matrix. Select a rating string (e.g., IWA vehicle/speed + penetration) that meets the building’s protection zone. Trace each choice to a tested model and its rating-critical dependencies.
371.3 Arrays & clear gaps
Pick patterns that respect desire lines and compute gaps with deflection/set allowances (321–322, 314). Arrays must keep HVM bollard acceptance bands (232).
Choose an array pattern that channels pedestrians and discourages vehicle weaving. Calculate clear-gap using nominal centers minus expected deflection & permanent set. Keep gaps ≤ the acceptance band across the frontage and near doors. Add chicanes or island clusters where desire lines are strong.
371.4 Foundations dependency
Ratings depend on base type/depth and soil (331–333, 423). Matching the tested base preserves crash rated bollard performance.
A rating certifies the system—core + footing. Confirm ground conditions and utilities early via utilities/surveys. If depth is constrained, consider shallow foundations that are part of the product’s as-tested configuration. Validate bearing and overturning with project soils and respect groundwater/soil effects. Drain sumps and weep paths per drainage strategy.
371.5 Controls & safety
For lanes, define drives, interlocks, and signage (341–343, 353). Safe logic prevents incidents around an HVM bollard portal.
Automatic portals pair the tested barrier with a drive (hydraulic or electromechanical) and a documented interlock matrix. Define fail-safe/fail-secure, EFO & overrides, and safety signalling with clear operator cues. Keep enclosures & cabling suitable for site environment, and verify logic during commissioning and SAT.
371.6 Evidence & documentation
Bundle annotated plans, certificates, and ITP links (444, 431, 714). Strong packs speed crash rated bollard approvals (938).
Prepare a certificate pack with rating string, vehicle class, penetration, and foundation class. Add marked drawings showing protection zones and keepered openings, and link tests/witness points in the ITP. Use the Submission-Pack Guidance to structure the index and reviewer journey, reducing back-and-forth and change risk.
371.7 Operation & human factors
Design HMIs and cues around users and visibility (524, 237). Good HF keeps HVM bollard lanes intuitive.
Place HMI & local controls within the driver’s cone, coordinate with sightlines & signage, and set clear “request→authorize→execute” flows. Include night dimming, audible beacons where appropriate, and simple recovery hints for mode errors. Confirm pedestrian wayfinding and egress widths near portals with people-flow guidance.
371.8 Maintenance & lifecycle
Plan intervals, spares, and KPIs (365, 542, 842). Lifecycle care sustains crash rated bollard availability.
Define preventive tasks and inspection intervals from the product O&M and site conditions; log counters, health pings, and alarms to drive action. Track KPIs like cycles/hour and MTBF; stock common spares to meet SLAs. See Lifecycle & Maintenance and Design for Maintenance for practical checklists.
371.9 Common pitfalls
Undersizing tiers, ignoring utilities, or sloppy gaps. Use checklists to protect HVM bollard outcomes (235, 243, 232).
Frequent failure modes include assuming a depth the site cannot accept, picking a rating without a traceable threat basis, and allowing near-door clear-gaps to drift during reinstatement. Counter them with the tier matrix, early utility detection, and a post-reinstatement gap check before witness testing.
Related
External resources
- FEMA 426 / DHS — Building Security
- NPSA — Hostile Vehicle Mitigation
- ASTM F2656 — Crash Testing Standard
371 Building Security with HVM Bollards — FAQ
How do I choose between low-speed and HVM bollards for a building frontage?
Use low-speed (e.g., ASTM F3016) for accidental impacts only. If your VDA shows credible deliberate threats or higher approach speeds, select an HVM rating (e.g., IWA/ASTM F2656) with a penetration class suitable for your protection zone, then verify foundation feasibility on site.
What if utilities limit foundation depth?
Do not “shrink” a deep system. Choose a product whose as-tested configuration includes a shallow or rail foundation, or redesign the array position. Confirm soil and groundwater effects and provide drainage per the product documentation.
When should I use automatic (active) lanes versus passive fixed/removable arrays?
Use automatic lanes where credentialed vehicles must pass regularly. Keep passive arrays where no vehicles should ever cross. If mixing types, document the interlock and signage strategy so pedestrians and drivers understand the portal language.
What documents are needed to obtain approval quickly?
Provide rating certificates, annotated plans showing protection zones and keepered openings, an ITP with witness points, product O&M and maintenance plan, and a structured submission index that matches reviewer expectations (see Submission-Pack Guidance).