How “type” pages work, when to use them, and cross-links.
Start from the Type pages (371–374) when scoping new work. Filter by rating (HVM vs low-speed), operation (fixed, removable, automatic), and context (frontages, lanes, perimeters). Each Type links forward to spacing (232), array patterns (321–326), foundations (331–334), and commissioning (631–638). This keeps selections evidence-based and aligned with crash rated bollard certificates (431). Continue exploring this section and return to the chapter hub Basics of HVM bollards whenever you need broader context. For UAE approvals, see the SIRA Bollards (UAE) hub.
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.
116.1 Five functional types (site-wide mapping)
Types span entrances, perimeters, lanes, service yards, and temporary/event modes. Start here to frame HVM bollard needs and short-list any crash rated bollard families (415) that fit.
The four purpose pages in 370 map coverage across typical sites: building frontages and public safety zones, outdoor asset perimeters, and controlled vehicle lanes. Use this mapping to shortlist solutions that satisfy HVM objectives without locking into products too early.
Each Type page points to mandatory constraints: 232 Spacing rules, 321 Array patterns, and 330 Foundations & loads. Lock these early to avoid rework during detailed design.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | 421 Rating-critical dependencies |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
| Context | Frontage vs lane vs perimeter | 370 Purposes |
116.2 When a Type page is your best entry
Use Type pages at concept/brief stage to avoid premature product picks. They point to spacing (232), arrays (321–326), and foundations (331–334) for HVM bollard design, plus rating checks for any crash rated bollard (411–413).
Arriving via Types clarifies constraints before aesthetics: clear-gap limits from 322, frontage patterns for doors in 323, corners/pinch points in 324, and turning/service access in 325. Only then consider finishes and sleeves.
116.3 Linking from Type to Design/Install
Each Type links forward: geometry (231, 321), utilities/drainage (241–246, 245), and commissioning (631–639). This keeps HVM bollard paths clear and anchors crash rated bollard acceptance (431).
From a Type page, jump to 231 People flow & egress for width assumptions, then to 240 Utilities/Surveys for conflicts and 245 Drainage strategy. For delivery, use 631 Pre-commission through 638 SAT/Witness so evidence in 431 aligns with the chosen Type.
116.4 Quick filters (rating, operation, context)
Filter by HVM vs low-speed (432–434), fixed/removable/automatic (124), and site context (137). For a crash rated bollard, filter by rating string and foundation limits (413, 421).
Start with intent: 432 HVM vs Low-Speed. Then pick the operation from 124 Bollards by Function (fixed, removable, automatic). Finally, confirm the rating string per 413 How to read ratings and dependency limits in 421.
116.5 Do’s & don’ts for Type selection
Do validate run-up (222) and angles (225). Don’t pick on aesthetics alone. HVM bollard choices must pass spacing (232). Any crash rated bollard must match tested configuration (421).
- Do estimate 222 run-up distance and 225 approach angles early.
- Do check 232 spacing and clear-gap compliance.
- Don’t alter sleeves/heights for a crash-rated model unless the test configuration allows it (see 421).
116.6 Examples per Type
Compact layouts show door arrays (323), corner treatments (324), and turning (325). Adapt for your HVM bollard case, then confirm crash rated bollard dependencies (431).
For frontages/entrances, review 323 Door protection arrays; for street corners and island pinch points use 324; for turning/service aisles confirm swept paths with 325. Capture assumptions for the ITP and SAP/SAT.
116.7 Handing off from Type to VDA
Type informs scenarios; VDA (221–229) confirms speed/vehicle. This closes the loop for HVM bollard selection and sets rating inputs for a crash rated bollard.
Once a Type narrows feasible options, proceed to 221 VDA method to set vehicle class, likely speed, and approach vectors. The VDA output drives rating candidates and supports the 433 Specification template.
116.8 Common pitfalls with Type pages
Skipping utilities/drainage (243–245) or accessibility (237–238) triggers redesign. For HVM bollard lanes, controls (342–355) get missed. For a crash rated bollard, sleeve/height changes can void the certificate (415).
- Underspecifying utilities: see 242 Underground detection, 243 Utilities conflicts & depth classes, and 245 Drainage strategy.
- Overlooking accessibility & sightlines: see 237 and 238.
- Lane control without controls: coordinate 342 Control logic, 343 Safety circuits, and 344 Loops.
116.9 Related tools & checklists
Use 912–919 templates, 714 ITP lines, and 638 SAT scripts. They standardize HVM bollard delivery and capture crash rated bollard evidence (431, 444).
- Downloads & templates: 910–919 (incl. 920 Calculators)
- Quality checkpoints: 714 ITP, 638 SAT/witness, and 444 Evidence
Related
External resources
- NPSA — Hostile Vehicle Mitigation (HVM)
- BSI — Impact test specifications for VSB systems
- FEMA 426 — Reference Manual (Building Security)
116 Using Type Pages In Section 370 — FAQ
How do Type pages reduce redesign later?
They front-load constraints (spacing, patterns, foundations, utilities) before you pick products. By following links to 232, 321–326, and 331–334, your option set already respects site geometry and service conflicts, cutting rework during detailed design and approvals.
What’s the quickest way to check if a crash-rated option actually fits?
Where do VDA inputs show up in Type decisions?
VDA pages 221–229 set approach speed, vehicle class, and angles. Those values drive the Type filter (frontage vs lane vs perimeter), spacing limits in 232, and which array patterns (321–326) are viable. Capture them in your spec using 433.
Do Type pages cover SIRA approvals in the UAE?
They set the technical groundwork. When approvals apply, use the SIRA Bollards (UAE) hub, then align your MS/RA and evidence pack with 431 and the commissioning flow (631–638) before witness tests.