432.1 Risk & purpose inputs

Start with purpose, consequence, and credible threat (221–229). Risk clarity drives HVM bollard need or low-speed sufficiency.

Define why protection is needed (public safety, building security, asset protection, or vehicle access/traffic control) using the purpose & tiers primer. Then evidence your Design Basis Threat (DBT) with a concise VDA: approach speeds, angles, run-up, and credible vehicle classes. If the site’s consequence of failure is high or threats include intent, you are likely in certified crash-rated territory rather than low-speed.

Use tiers appropriate to your purpose and standoff. For shopfront scuffs and mis-pedals, low-speed may suffice. For deliberate threats or crowd-adjacent frontages, lean to tested systems with defined penetration control. Cross-check your intent against Low-Speed Impact Ratings versus full crash-test standards.

432.2 People/crowd proximity

High proximity near glazing nudges toward an HVM bollard; distance and barriers may allow low-speed (231, 234).

Map desire lines and standing areas, then compare them to the egress & people-flow widths. If pedestrians queue or dwell close to the facade (or within the vehicle line-of-attack), favor certified HVM with tighter penetration distance limits. Where people are set back behind robust planters/walls and traffic is slow/filtered, a low-speed solution may be proportionate.

432.3 Vehicle access context

Open perimeters and service lanes raise risk; segregated streets reduce it (214, 215). Context shapes crash rated bollard necessity.

Assess permeability. Open forecourts, drop-offs and mixed-mode streets with long run-up routes increase approach speed and require higher tiers. Conversely, filtered streets with physical calming (terrain/calming effects) and limited approach vectors may justify low-speed measures. Tie the access picture into your array type (e.g., door/frontage arrays vs service access).

432.4 Evidence threshold

Authorities expect defendable evidence: VDA, speeds, vectors, and spacing (224–225, 232). Evidence justifies the HVM bollard choice.

Plan for a concise evidence pack: VDA calculations, array & clear-gap checks, and the certificate set (see 431 certificates). Where products differ from the tested article, use 414 equivalency and 435 anti-downgrade wording. For UAE projects, add a short note clarifying SIRA expectations and link to SIRA Bollards (UAE).

432.5 Budget & lifecycle

Balance capex with OPEX, downtime, and repaint cycles (842, 365). Lifecycle may favor a durable crash rated bollard.

Compare total cost of ownership across options. Low-speed units may be cheaper upfront but need more frequent repainting or replacements after minor knocks. Certified systems typically cost more initially but can reduce incident severity and downstream disruption. Use 842 lifecycle & maintenance and finishes guidance (365 design for maintenance) to set repaint intervals and spares. Capture assumptions in your cost notes (841).

432.6 Upgrade potential

Plan sleeves, ducts, and space for later escalation (446). Upgrade paths protect HVM bollard investments.

Where the present risk permits low-speed, design an escalation path: reserve ducting, provide adequate pit sizes, and avoid paving patterns that would block future array density. On existing HVM, allow for 446 upgrade paths such as sleeve swaps or deeper sockets within the family’s tested window (see 415 product families/variants).

432.7 Regulatory/authority signals

SIRA or site governance may require certified solutions (133). Signals often compel a crash rated bollard.

Check market/authority cues early. Some clients’ governance frameworks, insurers, or local authorities require certified systems for specific frontages or occupancies. If in the UAE, confirm whether the project falls under SIRA scope and reference SIRA Bollards (UAE). Align your specification language with 433 specification template and prepare 938 submission-pack guidance artifacts.

432.8 Decision tree

Follow inputs→tier→array→foundation→controls (339). Tree yields a defendable HVM bollard answer.

Use this flow: (a) confirm purpose & DBT → (b) pick a tier and check spacing rules → (c) select array type & clear-gap rule → (d) validate foundations (330 foundations & loads) → (e) set controls and interlocks → (f) compile the authority submittal. Keep a short assumptions register for reviewer clarity.

432.9 Example outcomes

Show two contrasting sites with notes and IDs. Examples make crash rated bollard decisions transparent (444).

Example A — Busy mall frontage (high dwell near glazing): VDA indicates 30–40 km/h potential via service road; minimal standoff; crowd density high. Outcome: certified HVM frontage array with tight clear-gaps; documented certificate pack (431), foundations validated (331–333), and submission via 938 guidance.

Example B — Staff parking island (filtered access, low dwell): Short run-up and strong physical filtering; low consequence. Outcome: low-speed storefront measure per PAS 170-1 or ASTM F3016, with a reserved escalation path (446) if risk changes. Record decisions in the 444 evidence & documentation note.

432 Design selection guide: HVM vs Low-Speed Bollards — FAQ