434.1 Low-speed use-cases

Car parks, traffic calming, and incidental bumps fit low-speed. Where threat is intentional, escalate to an HVM bollard (443).

Low-speed systems address accidental impacts and gentle roll-aways. They’re validated by standards like PAS 170-1 and ASTM F3016 for controlled speeds and trolley/storefront events. A key concept is stand-off distance: if generous stand-off exists and calming features constrain approach speed, low-speed can be adequate.

Typical locations: supermarket fronts, internal car-park aisles, and slow urban streets with traffic calming. If a DBT is not hostile and the run-up distance is short, start with Selecting Low-Speed vs HVM and the ASTM F3016 storefront context.

434.2 HVM use-cases

Frontages near roads, plazas with vehicle approach, or sensitive assets need certified crash rated bollard solutions (371–374).

Choose HVM when approach geometry enables higher speeds or where assets and crowds are exposed. Certified crash-rated systems come with a rating string that defines vehicle class, speed band, and penetration. Use VDA inputs—run-up, impact angle, credible vehicle—to select the tier.

Typical HVM contexts: building frontages on fast carriageways (frontage protection), crowded plazas, and critical infrastructure perimeters. For UAE approvals, coordinate early with SIRA and align submittals with Submission-Pack Guidance and Documentation & certificates.

434.3 Mixed environments

Blend low-speed furniture with an HVM bollard line guarding approaches (238, 321). Mixing reduces cost without losing control.

Many sites combine low-speed measures for internal circulation with an outer HVM array on the true defend line. Use array patterns and clear-gap rules to prevent drive-around defeat.

Inside the protected zone, use low-speed posts or planters as wayfinding and crowd guides, keeping egress widths clear. Document the “mixed-type array” intent so substitutions don’t erode the HVM barrier’s performance.

434.4 Injury vs hostile risk

If risks are mainly pedestrian injury, low-speed may suffice; hostile intent mandates a crash rated bollard (212, 235).

Differentiate accidental injury scenarios (slow reversing, mis-parking) from deliberate ramming. A risk management lens asks: what is the credible worst case? If the threat analysis includes hostile intent, move to HVM tiers using the Purpose/Tier Matrix.

When in doubt, run a short VDA sensitivity: small increases in run-up or angle can escalate energy dramatically. Capture assumptions in an assumptions register to support approvals.

434.5 Evidence & approval needs

Authorities favor VDA-backed choices (221–229, 717). Evidence unlocks HVM bollard approvals.

Compile an evidence pack: rating certificate, test video, as-tested configuration notes, and site comparability. Use certificate review checklists and include Submission-Pack Guidance items for reviewers.

In the UAE, reference SIRA and align your ITP/SAT witness procedure with rating-critical dependencies (421) so installed works preserve certification.

434.6 Cost/benefit trade-offs

Compare lifecycle, downtime, and aesthetics (841–843, 316). Long-run value often favors a crash rated bollard.

Headline cost differences can mislead. Consider risk/benefit & ROI, lifecycle/maintenance, and disruption costs. For automatic HVM lanes, include controls, fail-state, and aesthetic finishes.

Where low-speed is borderline today but escalation is foreseeable, a planned conversion path (section 434.7) can minimize sunk cost while protecting people and assets.

434.7 Upgrade path planning

Provide ducts/sleeves and clear gaps for later HVM bollard upgrades (446, 246).

Future-proof by reserving MEP provision, selecting modules that accept deeper foundations later, and maintaining the clear-gap geometry needed for HVM patterns. Document the upgrade path with drawings and a short change-control note.

At key penetrations, pre-lay ducting & pathways and leave pull strings. Keep an anti-downgrade clause in specs to protect later HVM adoption.

434.8 Real examples

Document sites that moved from low-speed to a crash rated bollard, noting triggers and lessons (118).

Common triggers: redevelopment placing doors closer to traffic, new traffic patterns increasing effective run-up, or incidents that reset the evidence threshold. Capture before/after geometry, chosen rating, and commissioning results in the Change Log format.

When publishing case studies, follow the Case Study Content Checklist and link to relevant design pages (e.g., impact angles, array patterns).

434.9 Decision pitfalls

Common errors: misread speeds, ignored angles, poor spacing (222, 225, 232). Avoid to protect HVM bollard integrity.

Frequent mistakes include assuming posted speed equals impact speed, neglecting oblique angles, and exceeding clear-gap limits. Another is accepting product “families” without checking which variants are certified.

Protect against pitfalls with a brief design selection guide, enforce anti-downgrade clauses, and cross-check rating strings with How to read ratings.

434 When to use low-speed vs HVM Bollards — FAQ