Step-by-step design path from requirement to detail.
A one-page route from brief to build. Start with requirements and context (211–219), choose type and rating/tier (124, 432–435), then pick arrays/spacing (321–327, 232). Select foundation options (331–334) gated by utilities/drainage (241–246), and lock controls/safety (341–357). A buildability check, cost/time review (841, 855), and sign-off steps prepare submittals (938) and commissioning (631–639). 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.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
339.1 From requirements to type
Gather VDA/context (211–219), then pick functional family (124). Correct entry avoids rework on HVM bollard arrays and mis-specified crash rated bollard models.
Start by capturing an Operational Requirements Document and the site’s VDA. Record purpose, users, access modes, and credible threats. This ensures you choose the right functional family from Bollards by Function before jumping to products.
Translate context into a short list of needs: protection zone, access policy, footfall, and emergency priorities. Distinguish Passive vs Active solutions early to avoid downstream rework.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read crash ratings |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
Related quick reads: Purpose/Tier Matrix · Array Patterns
339.2 Rating/tier decision
Map purpose→tier (235) and standards (411–414). Decision anchors whether an HVM bollard or a specific crash rated bollard is justified.
Use the purpose→tier mapping to pick HVM vs low-speed. Align with recognized standards (e.g., global crash ratings) and cite the exact rating string needed by the site.
Document assumptions and uncertainty bands. If in the UAE and approvals apply, add a brief SIRA note and consult SIRA Bollards (UAE) for authority expectations on tiers and evidence.
339.3 Array & spacing choice
Select patterns (321–327) and compute gaps (322). Spacing preserves HVM bollard acceptance and respects crash rated bollard deflection/set (314).
Choose a layout pattern—inline, staggered, islands—based on approach vectors and pedestrian desire lines. Then compute clear gaps using measured deflection and set (see Clear-Gap Calculations).
Check near-door spacing and frontage rules where relevant, and record the results into your ITP. Lateral references: Array Patterns · Mixed-Type Arrays
339.4 Foundation selection path
Gate by utilities/soil/drainage (241–246, 423). Foundation choice keeps HVM bollard geometry buildable and matches the crash rated bollard certificate (421, 332).
Run a utilities search and clash review, then choose among deep sockets, shallow rails, micro-piles, or retrofit frames (see Foundation types). Respect the as-tested configuration and depth class in the certificate (rating-critical dependencies).
Where groundwater or dewatering is expected, coordinate with drainage options (sumps/outfalls) before freezing the footing choice. Reference: Groundwater/soil effects · Underground Utilities
339.5 Controls/safety selection
Define drives, interlocks, and safety circuits (341–343). Control choices make automatic HVM bollard behavior predictable and auditable.
Select the drive (hydraulic vs electro-mechanical) and size the HPU or motor/gear package for the duty cycle. Then define the interlock matrix, fail-safe/secure states, and modes of operation with test points for commissioning.
Include photo-eyes, loops, and obstruction logic (Field Devices · Induction Loops). Plan interfaces with fire/BMS/SCADA and define EFO/override policy.
339.6 Drainage/utilities gating
Confirm pits/ducts before pour (334, 615–616). Gating avoids HVM bollard soak issues and damage to a crash rated bollard base.
Approve the pit drainage scheme (sump/outfall/NRV/soakaway) and verify duct banks, draw pits and gland plates before any pour. Use a short hold-point checklist so nothing is buried without inspection photos and mandrel tests on conduits.
Cross-link with installation steps: Ducting & Draw Pits · Drainage for HVM/Crash-Rated Bollards
339.7 Buildability check
Sequence, access, and permits (611–614). Buildability prevents HVM bollard delays and keeps crash rated bollard pours compliant.
Validate access routes, excavation/shoring, dewatering, crane placement, and curing windows. Confirm that templates/jigs, datum benchmarks, and tolerance stack-up won’t jeopardize clear-gap targets. Use a short pre-pour go/no-go decision gate.
Helpful detail pages: Setting-Out & Benchmarks · Grout Beds & Levelling
339.8 Cost/time evaluation
Use VE guardrails (338) and programme links (855). Balanced choices sustain HVM bollard performance and certification integrity.
Evaluate options with Value Engineering guardrails so substitutions don’t erode certification or safety. Compare shallow vs deep foundations, mixed-type arrays, and local finishes. Align with programme/permits and delivery lead times.
For lifecycle impact, reference Lifecycle & maintenance and factor spares, MTBF, and access windows into TCO.
339.9 Sign-off & next steps
Freeze design, prep specs/submittals (433, 938). Clear sign-offs move HVM bollard works to commissioning and protect crash rated bollard approvals.
Issue a design freeze memo, then compile the specification and the submission pack with the exact certificate scope, drawings, and evidence chain. Where required in the UAE, coordinate authority submittals and witness bookings—see SIRA Bollards (UAE) and Submission-Pack Guidance.
Plan commissioning using the 630-series pages: pre-commission checks, loop/sensor proving, interlock verification, performance/duty tests, EFO/failure modes, and SAT/witness procedures.
Related
External resources
- NPSA: Hostile Vehicle Mitigation (risk-led approach)
- ASTM F2656: Crash testing for vehicle security barriers
- BSI: Impact test specifications for VSB systems
339 Decision Flow — FAQ
What’s the minimum evidence to justify a crash-rated system?
List the credible threats from your VDA, map them to a tier in the Purpose→Tier Matrix, and cite a specific rating string with matching certificate scope and foundation depth class. Include drawings, clear-gap calculations, and a short rationale that ties back to standards.
When should I lock the foundation type?
After utilities proving and drainage design are approved. Picking deep vs shallow too early risks clashes, water ingress problems, or a departure from the as-tested configuration, which can undermine approvals.
How do I avoid downgrades during value engineering?
Use VE guardrails: no substitution that alters the rating string, depth class, rebar cage geometry, or pit/drainage intent. Document like-for-like boundaries and require vendor confirmation of certificate equivalence.
What are the must-do commissioning steps for automatic lanes?
Run pre-commission checks, power/controls health, loop & sensor proving, interlock matrix verification, performance/duty tests, and EFO/failure-mode drills, then complete SAT/witness with an evidence pack and sign-offs.