413.1 Decoding a rating string

Parse vehicle mass, speed, and penetration. Decoding turns a label into HVM bollard inputs.

A rating string (e.g., IWA or PAS format) compresses the rating string essentials into a few tokens: the test vehicle class and mass, the impact speed, and the penetration (P). Read the whole line, not just the headline letter/number: variants can differ by height, sleeves, or footing. Treat the string as a pointer into the certificate, video, and data pack—not a standalone promise.

Convert each element into design inputs: minimum clear-gap policy, defend line placement, and vehicle class envelope. Log assumptions and use a brief “reader guide” when circulating excerpts during design reviews.

413.2 Vehicle & speed line items

Confirm the exact mass/speed used. Line items bound crash rated bollard applicability (414).

Standards list multiple line items (vehicle classes and speed bands). Your design is bounded by the exact item tested—e.g., a 7,200 kg N2A truck at 48 km/h is not evidence for a heavier class or higher speed. Cross-check the certificate scope and test lab’s accreditation. Document any gaps with a short “comparability note,” then escalate for re-test, simulation correlation (416), or an alternative product.

413.3 Penetration value meaning

Relate P to protected line or asset. Correct meaning defends HVM bollard spacing.

P is measured to a defined defend line or datum (varies by standard). Don’t confuse vehicle dynamic deflection with permanent set—a distinct topic covered in Deflection vs permanent set. Small P does not mean “no debris”: review dispersion and major debris notes before setting pedestrian routes behind arrays.

413.4 Test orientation & angle

Orientation matters for corner/oblique hits (225). Respect limits when laying out a crash rated bollard array.

Most tests are conducted at a specific impact angle and approach vector. Corner islands and oblique arrivals can increase effective penetration or cause “vehicle lift” over low heads. Use the site’s governing angles from 225 Impact Angles & Approach Vectors, and demonstrate that your array orientation stays within the tested envelope—or document a conservative margin and rationale.

413.5 Foundation/testbed notes

Carry foundation constraints into drawings (332). Bases keep HVM bollard claims valid.

A rating attaches to the tested system—the core plus its foundation/testbed. If the product offers multiple foundation classes (e.g., Deep-Socket vs Shallow-Rail), the certificate will state which one was used. Reflect those details in 332 Foundation types and installation notes; if your slab or soil differs, verify performance via calculations (331, 333) or seek an alternative with appropriate evidence.

413.6 Array/config dependencies

Single vs multi-post behavior differs. Array notes stop over-claiming a crash rated bollard.

Certificates may specify whether the tested article was a single post, an inline pair, or a multi-post array with spacing/links. Array effects change load paths and group stiffness. Don’t assume a single-post result extends to a long, mixed-type line. Where mixes are needed, see 326 Mixed-Type Arrays and plan for conservative spacing or a higher tier.

413.7 Validity limits

List soil, height, and accessory boundaries (421). Limits avoid noncompliant HVM bollard installs.

Look for explicit validity conditions: minimum effective height, sleeve additions, soil class, groundwater, frost, or installation tolerances. These are rating-critical dependencies (see 421). Record them in the specification and enforce via ITP witness points during installation (714). If site conditions breach limits, raise an RFI and re-baseline the design.

413.8 Interpreting photos/footage

Photos reveal impact angle, lift, and debris. Visuals support crash rated bollard reviews (444).

Still frames and test videos expose tell-tales: front-end dive, rear lift, wheel snagging, or debris trajectories. Use a simple wide→detail photo set; annotate the defend line and any measured P-points. Cross-reference with the submission’s 444 Evidence & Documentation so reviewers see exactly what was tested and what was achieved.

413.9 Red flags in reports

Watch for extrapolations, missing base data, or unclear P-lines. Flags protect HVM bollard integrity.

Common issues: missing foundation drawings, ambiguous defend line definition, unaccredited labs, mixing standards equivalency with no mapping (see 414), or selectively cropped videos. Another red flag is “family claim” without 415 product-family rules. Where uncertainty remains, require an independent peer review or a controlled on-site proof test.

How to read HVM/Crash-Rated Bollards ratings — FAQ