Products come in families with many variants—only some preserve the rating. This page explains how height, diameter, sleeves/finishes, foundation depths, and accessories interact with the tested configuration. We outline how test matrices are built and how to cross-reference certificates. Use this when writing specs (433, 852), naming products (125), and locking rating-critical dependencies (421) for crash rated bollard arrays. 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.
415.1 Family vs model vs variant
Clarify tree: family → model → variant. Precision stops off-spec HVM bollard substitutions.
Think of a product family as a container for closely related models sharing a core as-tested configuration. A “model” is the named article that appears on drawings and certificates. A “variant” is a controlled change—e.g., alternative head, sleeve, or finish—that the manufacturer has proven does not degrade the certified outcome. Clear naming prevents unverified swaps that erode your crash rating.
Document the tree in your submittal index and align it with the documentation & certificates page so reviewers can trace each field reference back to the right record. When ambiguity remains, use a “like-for-like” confirmation referencing the rating-critical dependencies.
| Aspect | What matters | Where to verify |
|---|---|---|
| Naming | Family → Model → Variant mapping | Certificate scope; manufacturer data sheet |
| Performance | Tested system (bollard + footing) | Crash Standards Overview |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
415.2 Height/diameter options
Changing either may void results. Keep crash rated bollard geometry within tested bounds (421).
Alterations to visible height or core diameter shift capture height, stiffness, and impact posture. Increasing height without re-testing can raise bending moments at the socket; trimming height can lower engagement with the vehicle’s mass. Similarly, small diameter changes affect the section modulus and local buckling behavior.
Use the geometry pages—diameter & section selection and height setting—to stay within published variant windows. If a proposed size sits outside the certified tolerance band, treat it as a new model and demand fresh evidence.
415.3 Sleeve/finish variants
Sleeves can add mass or change edges. Validate so HVM bollard safety isn’t degraded (313).
A bollard sleeve or cap that changes the leading edge, width, or slip surface may affect vehicle engagement and pedestrian snag risk. Heavy composite or stainless sleeves also change total mass and dynamic response. Cosmetic finishes alone rarely change performance—unless their build-up, texture, or attachment modifies the head profile.
Cross-check sleeve options against Heads & Attachments and durability pages (coatings, galvanic risks). If the sleeve is sold as a “sleeve-only upgrade,” insist on the manufacturer’s matrix showing it was included or validated against the as-tested article.
415.4 Foundation depth variants
Depth shifts rotation/penetration (333). Respect tested ranges for the crash rated bollard.
Foundations are part of the certified system. Shallower sockets change base rotation and can increase penetration and debris spread. Deeper sockets raise stiffness and may reduce energy dissipation. Unless the certificate explicitly lists multiple foundation classes (e.g., Deep-Socket vs Shallow-Rail), do not assume equivalence.
Coordinate with foundation design checks and depth & utilities choices if utilities or slabs force a depth change. Where evidence is weak, specify re-test or simulation + model correlation.
415.5 Automatic vs fixed siblings
Automatic mechanisms add dependencies (341). Ensure HVM bollard variants align.
Automatic siblings include drives, controls, and safety devices & measures that do not exist on fixed/passive models. Families may share a core but have distinct rating-critical dependencies such as head geometry, stroke, or locking features. Treat drive technology (e.g., Auto-Hyd vs Auto-EM) as separate variants unless the certificate explicitly groups them.
For operations, tie the selection to modes of operation, health pings, and EFO behavior to keep the family mapping consistent from design to SAT.
415.6 Accessory impacts on rating
Rails/caps/lighting can snag or stiffen (313). Accessories must preserve crash rated bollard behavior.
Handrails, link bars, caps, beacons, and signage add stiffness, snag points, or mass. If a rail spans bollards, it can change group stiffness and alter penetration outcomes. Treat any accessory that touches the core or head as a performance-relevant change and verify it in the manufacturer’s variant matrix or by addendum evidence.
Use Heads & Attachments and array patterns to check whether accessories change clear-gap or capture height. If lighting requires penetrations, align with enclosure/cabling good practice and maintain IP rating.
415.7 How test matrices are built
Matrices show which combinations were proven. Use them to select HVM bollard variants.
Manufacturers assemble a matrix of test articles covering the edges of the family’s parameter space (e.g., tallest/shortest, thinnest/thickest, deepest/shallowest foundation, with and without sleeve). Interpolation is allowed only where the standard or certificate states the rule. Your job is to stay inside the “proven box.”
Ask for a family overview that links each matrix row to a test report, video/imagery, and the resulting rating string. Where only one configuration was tested, treat all other options as unproven unless a written engineering rationale (and, ideally, simulation correlation) is supplied.
415.8 Certificate cross-referencing
Cross-check codes and serials (431). Cross-refs prevent wrong crash rated bollard picks.
Use a simple cross-reference sheet: model code, variant ID (or SKU), certificate number, test report number, and certificate scope. Match the model on the drawing to the certificate entry—never assume similar names imply coverage. For UAE projects, add a SIRA note if an approved list is required and link reviewers to SIRA Bollards (UAE).
Build the cross-ref into your submission-pack guidance so it survives tender to construction. If a vendor proposes a substitution, apply the anti-downgrade clause and request a complete evidence pack.
415.9 Specifying allowable variants
List allowed SKUs in specs (433). Lists block unsafe HVM bollard swaps.
In the specification, list “allowable variants” by exact code for: geometry window (height/diameter), foundation class, sleeve/finish, and accessories. State that any deviation must be supported by certificate references and, where applicable, simulation correlation plus written acceptance by the Owner’s Engineer. Add an explicit equivalence clause to prevent degradation via substitution.
Point readers to the spec template and design selection guide. During review, use the submission-pack guidance checklist to verify all fields.
Related
External resources
- ASTM F2656 — Crash-Rated overview
- BSI — Impact test specifications for VSB
- NPSA — Hostile Vehicle Mitigation guidance
