Cut through jargon so reviewers and site teams speak the same language. We define penetration values, debris zones, occupant risk (where applicable), residual set vs dynamic deflection, and what “tested configuration” really covers. You’ll also see how certificates are structured and the pitfalls in equivalency claims. Link this with the rating-decoding page (413) and the acceptance checklist (431) to protect HVM bollard intent on drawings and submittals. 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.
412.1 Common terms defined
Define penetration, deflection, and test orientation. Clear terms align HVM bollard drawings and crash rated bollard acceptance.
Penetration is the distance the vehicle or designated payload crosses the defend line. Dynamic deflection is the peak elastic movement under impact, while test orientation describes the approach/angle the standard specifies. Getting these basics straight helps reviewers read 413 rating strings correctly and designers maintain clear-gaps in 322 Clear-Gap Calculations.
Crash ratings are always tied to a tested system (article + footing + layout). For a quick standards primer, see 411 Crash-Rated Bollards: crash standards overview. When terms appear in submittals, cross-reference with 431 Documentation & certificates.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | 413 How to read ratings |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
412.2 Penetration ‘P’ values
State how far payload crosses the line. P-values prove a crash rated bollard limits intrusion at your HVM bollard line.
P-ratings express the measured penetration distance of a defined vehicle or payload through the defend line. Standards specify how the defend line is established and what part of the vehicle is referenced. Use P-values alongside impact energy/speed in the 220–229 VDA to check the selected rating controls the credible worst case.
When verifying submittals, ensure the P-value belongs to the same test orientation, vehicle class, and foundation class as your design. If near doors or glazing, combine P-limits with 234 Frontage protection.
412.3 Dispersion/debris zones
Note debris expectations so frontage glazing is protected (234). Zones inform HVM bollard stand-off.
Standards may report dispersion—the spread of major debris—to help set safe offsets from glazing and pedestrian areas. Treat debris zones as planning tools: combine with stand-off distance and clear-gap rules from 232 Spacing rules to keep fragments away from queues and entrances.
412.4 Occupant risk (if used)
Where applicable, clarify head/neck metrics. Contextualize so HVM bollard choices aren’t misread.
Some standards or program addenda include occupant-risk metrics (e.g., head/neck criteria). Treat these as context-specific; they do not replace core intrusion/penetration limits. Use them to inform frontage detailing (e.g., tempered/laminated glass) and people-flow choices linked from 231 People Flow & Egress Widths. Where authorities require explicit acceptance, note it in your 431 evidence pack and, for UAE projects, confirm any SIRA expectations via SIRA Bollards (UAE).
412.5 Residual set/deflection
Translate movement into spacing allowances (314, 232). Movement informs crash rated bollard clear-gap checks.
Dynamic deflection is elastic movement under impact; residual set is permanent post-impact displacement. Designers should budget for both: first to protect near-side elements during impact, then to validate post-event clear-gaps. Apply this with 314 Deflection vs Permanent Set and lay out arrays from 320 Arrays & Spacing.
412.6 Tested configuration
List height, sleeve, foundation, and array. Staying within bounds preserves HVM bollard certification (421).
The reported result applies to the as-tested configuration: core model, effective height, sleeve/cladding, foundation type/depth, spacing, array geometry, and test orientation. If your design departs from any of these (e.g., sleeve-only upgrades or different depth class), confirm coverage or seek fresh evidence. See 421 Rating-critical dependencies and 415 Product families/variants.
412.7 Equivalency claims
Demand energy, speed, and configuration evidence (414). Tough claims protect crash rated bollard integrity.
Use a strict, written equivalency policy. Claims must show equal or greater vehicle mass, speed, energy and matching (or more severe) orientation, with configuration limits intact. Reference 414 Standards equivalency and protect scope in specifications using 435 Anti-Downgrade / Equivalence Clauses.
412.8 Certificate anatomy
Show fields reviewers expect (431). Anatomy speeds HVM bollard reviews.
Certificates should state the issuing body/lab and accreditation, product/model, rating string, full certificate scope, as-tested configuration, vehicle class and speed, P-value/penetration, dispersion notes (if applicable), and any limitations or installation dependencies. Use 431 Documentation & certificates to build a repeatable reviewer checklist.
412.9 Misuse of terms to avoid
Ban vague words like “equivalent” without data. Precision protects crash rated bollard approvals.
Avoid “tested to a similar standard,” “equivalent,” or “like-for-like” without proof. Do not split apart system results (e.g., swapping sleeves, changing depth class, or altering spacing) without formal coverage. Keep terms aligned with 413 How to read ratings and the dependency checks in 421.
Related
External resources
- BSI: VSB impact test specifications (IWA/PAS)
- ASTM F2656: Crash testing for perimeter barriers
- NPSA: Hostile Vehicle Mitigation
