When threats, authorities, or incidents change, you may need to move from low-speed to an HVM bollard system. We outline credible triggers, interim controls, and retrofit strategies: shallow bases (244, 332), reconfigured arrays (321–327), and added controls/safety (341–355). Evidence, approvals, and phasing align with submission packs (938), specs (433, 435), cost models (841, 842), and operational KPIs (542) so upgrades are defensible and buildable. 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.
446.1 Why upgrades are needed
Threat changes, authority mandates, or incidents can outgrow low-speed measures (118, 133). Upgrades move you to an HVM bollard or a certified crash rated bollard.
Low-speed devices verified to storefront standards are designed for accidental roll-throughs, not hostile intent. When the Design Basis Threat increases, authorities tighten the accepted evidence and you must adopt a certified crash-rated system. This typically means new foundations, tighter clear-gap rules, and integration with safety devices & measures.
Moving to HVM is not a like-for-like swap of posts. It is a system upgrade: certified bollard + as-tested footing + array geometry + controls. Start with the decision pages that set the boundary between low-speed and HVM: Selecting Low-Speed vs HVM and the higher-level Design selection guide.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read crash ratings |
| Operations | Duty cycle, fail-state, safety | Installation Guide |
446.2 Triggers for upgrade
Record speed increases, glazing/frontage rework, tenant shifts, or crowd growth (222, 234, 371–373). Triggers justify escalation.
Typical upgrade triggers include longer run-up distance enabling higher approach speed; frontage redesign adding more glazing; new tenants (e.g., government, luxury retail) increasing attractiveness; or recurring crowd peaks per public-safety contexts. Capture evidence in your VDA report and change log, then map it to the Decision Flow for an auditable escalation path.
446.3 Interim risk controls
Use temporary barriers, stewarding, and re-marking (239, 357). Interim steps maintain HVM bollard intent while upgrading.
Where delivery of certified systems takes time, deploy cordoned routes, temporary/event modes, traffic re-marking, and stewarded gaps. Portable barriers can protect vulnerable approach cones and entrances. Document interim measures in the MS/RA and coordinate with the authority (in the UAE, see SIRA Bollards (UAE)) to accept the temporary control set and review signage per Safety Signalling.
446.4 Foundation retrofit options
Adopt shallow slabs, retrofit frames, or micro-piles (244, 332). Options preserve crash rated bollard behavior in constrained sites.
Legacy sites often have utilities, thin slabs, or poor soils. Consider shallow foundations, retrofit frames, mini caissons, or micro-piles tied into a grade beam. Match the solution to soil stiffness and drainage; integrate sumps/weep holes to avoid buoyancy and hydrostatic uplift. Verify the as-tested depths and reinforcement against rating-critical dependencies.
446.5 Array reconfiguration
Shift to staggered/island patterns; tighten gaps (321–324, 232). Reconfiguration improves HVM bollard performance.
Escalation often requires a new array pattern that reduces clear-gaps and closes drive-around defeats: staggered frontage, island clusters, or pinch-point corners. Near doors, apply near-door spacing rules and maintain egress width per people-flow guidance.
446.6 Controls & safety additions
Add loops, beams, signalling, and EFO logic (344–355). Additions convert lanes to automatic HVM bollard quality.
Upgrading to automatic (active) lanes typically adds induction loops, photo-eyes, traffic aspects, and EFO logic. Align interlocks with the interlock matrix, set fail-safe/secure philosophy, and prove device health during commissioning tests. Document drive type (hydraulic or electromechanical), duty cycle, and safety devices & measures in the FDS.
446.7 Evidence & approvals
Update certificates, arrays, spacing calcs, and ITP lines (431, 322, 714). Evidence secures crash rated bollard acceptance.
Authorities will expect current certificates for the chosen family/variant, array drawings with keepered dimensions, spacing/penetration checks, and a commissioning plan. Package these using Submission-Pack Guidance, and include certificate verification, ITP witness points, and SAT scripts. In the UAE, note any SIRA reviewer requirements and provide a clear authority submittal path.
446.8 Cost & phasing
Phase by frontage or lane; reuse ducts and sleeves (246, 338, 855). Phasing limits downtime while adding HVM bollard coverage.
Create a phased plan that keeps entries open: lane-by-lane changeovers, temporary diversions, and night shifts. Reuse compliant ducts & draw pits and any salvageable sleeves; otherwise include diversions in the budget. Use cost ranges, lifecycle plans, and a programme & phasing schedule to justify spend against risk reduction and KPIs.
446.9 Case studies
Summarize before/after, KPIs, and lessons (542, 544). Studies prove crash rated bollard value.
For each upgrade, capture the pre-upgrade risk picture, chosen HVM class, foundations and array decisions, commissioning outcomes, and post-go-live KPIs (e.g., ops/hour, MTBF, incident count). Present the dashboard view per Operational dashboards and discuss common pitfalls & lessons to drive better next-project decisions.
Related
External resources
- ASTM F3016 — Storefront/Low-Speed
- ASTM F2656 — Crash-Rated Overview
- NPSA — Hostile Vehicle Mitigation
