414.1 What ‘equivalence’ can mean

Energy, speed band, and configuration parity—not brand swaps. Equivalence must keep HVM bollard outcomes intact.

“Equivalence” means a proposed system can deliver the same outcome envelope as the specified system under comparable rating string conditions. Parity spans impact energy, speed band, vehicle class/geometry, and the as-tested configuration (including as-tested configuration).

True equivalence is not a brand substitution. It requires like-for-like evidence that the vehicle penetration distance and debris outcomes will remain within acceptance bands when installed on comparable foundations and spacing.

To keep discussions concrete, treat equivalence like a model of “outcomes parity” with explicit tolerances (e.g., penetration within the same class; pass margin not eroded). Capture assumptions in an assumptions register.

414.2 Like-for-like pitfalls

Vehicle shape/ride height alter results. Avoid shallow comparisons that misapply a crash rated bollard.

Changing the test vehicle’s ride height or nose stiffness can shift impact point and load path, leading to very different penetration outcomes. A “same speed & mass” argument is incomplete if the geometry changes (e.g., cab-over vs SUV). Validate against the correct vehicle class envelope.

Beware “certificate shopping” where a supplier presents their best-case orientation or spacing while your scheme requires a different tested orientation or an array pattern that wasn’t validated. Cross-check against Clear-Gap Calculations and Foundation & Installation Dependencies.

414.3 Vehicle energy alignment

Match kinetic energy and mass distribution. Energy parity underpins HVM bollard safety.

Start with kinetic energy (½ m v²), but don’t stop there. Mass distribution affects the effective impact point and capture height, changing bending moment at the base. Where possible, compare filmed tests and wide→detail photo sets to confirm comparability.

Document “energy parity” explicitly: the proposed system must demonstrate equal or higher energy absorption without exceeding the same penetration class. Note any sensitivity band near the pass/fail threshold.

414.4 Speed band mapping

Map tested bands to site speeds (224). Mapping defends crash rated bollard use.

Use VDA Speed Estimation Methods to estimate realistic approach speeds. Then map to the standard’s tested band so your acceptance is within the correct envelope. If the site is close to a band edge, add a prudent safety factor or require a higher band certificate.

Record the mapping in your VDA Report Template and carry it into the specification, so substitutions must meet the same band-to-site mapping without eroding pass margin.

414.5 Foundation/array effects

Bases and spacing change penetration (331–333, 322). Effects must be shown for HVM bollard claims.

Crash ratings are inseparable from foundations and spacing. Shifting from a deep socket to a shallow rail alters rotational stiffness and can increase dynamic deflection, widening the clear gap at peak load. Verify comparability against Design checks for foundations and Arrays & spacing.

State foundation class equivalence (e.g., “Deep-Socket ↔ Deep-Socket” only) and require re-validation if utilities push you to Shallow foundations.

414.6 Evidence required for claims

Demand certificates, photos, and calc notes (431, 444). Evidence secures crash rated bollard acceptance.

Request an evidence pack containing: accredited certificate (with certificate scope), test photos/video, penetration plots, and concise calculation notes linking the as-tested arrangement to your site. Use Documentation & certificates and the Evidence & Documentation page as checklists.

For UAE projects referencing authority submissions, align the pack with authority submittals requirements and, where applicable, SIRA expectations.

414.7 Acceptance wording examples

Provide strict substitution text (435). Wording locks HVM bollard performance.

Use clause language that preserves outcomes and dependencies. Example: “Proposed substitutions must match or exceed the specified rating string, penetration class, test vehicle class, tested orientation, and foundation class. Certificates shall evidence the as-tested array spacing within ±5% of the design spacing. Any change to foundation class or spacing requires re-submittal under Anti-Downgrade / Equivalence Clauses.”

Where risk appetite is low (embassy, critical infrastructure), add a prohibition on like-for-like substitution without full parity evidence.

414.8 Reviewer checklist

Quick checks spot weak claims. Checklist protects crash rated bollard intent.

• Does the certificate’s vehicle class & mass match the site’s VDA?
• Is the tested speed band mapped to the site approach speed (with margin)?
• Are orientation, foundation class, and array spacing equivalent?
• Is the penetration class equal (or better) with similar pass margin?
• Are photos/video adequate for site comparability judgment?

Log any uncertainties in the uncertainty budget and request clarifications via RFI.

414.9 When to reject equivalence

Reject if energy/config diverge or bases differ. Rejections safeguard HVM bollard design.

Reject when: (a) vehicle geometry or mass distribution is not comparable; (b) the tested orientation/foundation/spacing differ; (c) penetration moves into a worse class; or (d) the substitution consumes critical pass margin near constraints (doors, glazing). Record the decision and cite Anti-Downgrade / Equivalence Clauses.

If a supplier can only achieve parity by changing foundation class, require redesign under Foundation & Installation Dependencies and re-submit with new certificates.

414 Standards equivalency for Crash-Rated Bollards — FAQ