Reading paths, symbols, references, tooltips, and internal-link conventions.
Skim intros, then jump to the task at hand: compare HVM bollard tiers and spacing ( 232 ), pick arrays ( 321–326 ), or prepare specs ( 433 ) and submission packs ( 938 ). Use glossary tooltips ( 117 ) and standards pages ( 411–416 ) to validate terms. Download live templates ( 912–919 ) and follow decision flows ( 339 ) to keep projects moving with minimal back-and-forth. For context, see this section and the chapter hub. If your project involves UAE approvals, see SIRA Bollards (UAE). When installation implications matter, jump to What to Expect and the 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.
114.1 Read order vs jump-in navigation
Short on time? Skim intros, then jump to your task: layout/spacing (232, 321–326), foundations (331–334), or specs (433). If the decision is HVM bollard vs low-speed, start at 432/434/443. For a specific crash rated bollard, decode ratings (411–413) and lock dependencies (421) before drawing.
Most readers don’t need to read linearly. If you are validating an HVM scheme, begin with 232 Spacing rules and 320 Arrays & spacing. If the task is product naming, verify standards at 411–413 and dependencies at 421 before committing.
| Task | Start here | Next steps |
|---|---|---|
| Compare tiers | 123 Purposes & tiers | 443 Selecting Low-Speed vs HVM |
| Pick an array | 321 Patterns | 322 Clear-gap · 323 Frontage arrays |
| Write specs | 433 Spec template | 435 Anti-downgrade |
114.2 Using the “On this page” TOC
Use the sticky TOC to hop across sections. It mirrors the X00→XX0→XXX structure and deep-links to spacing (232), patterns (321–326), and acceptance (638). For HVM bollard lanes, TOC anchors speed commissioning pages. For a crash rated bollard, TOC jumps land on standards and certificates (411, 431).
The TOC matches visible H2 codes (e.g., “114.3 …”), making citations unambiguous in emails and reviewer notes. When you reference SAT guidance, link directly to 638 SAT / Witness Procedure. For spacing decisions, jump to 232 and the array subpages under 320.
114.3 Using internal links smartly
Prefer Page-ID links (e.g., 232.4) in emails/specs so reviewers trace logic. Chain VDA (221–229) → selection (432) → arrays (321–326) → foundations (331–334). This keeps HVM bollard choices and crash rated bollard evidence coherent in submission packs (938).
For design reviews, cite the path explicitly: start at 221 VDA method, carry speed estimates from 222 Run-up and 225 Angles, then justify array choice in 320 Arrays. Lock foundation comparability at 333 Design checks and file the trail in 938 Submission-Pack Guidance.
114.4 Using FAQs and JSON-LD blocks
FAQ blocks answer recurring reviewer queries (444) and add rich results without fluff. Include terms from the glossary (117) and rating strings (413). For HVM bollard pages, clarify spacing and EFO (232, 354). For a crash rated bollard, show certificate scope and limits (431).
Keep Q&A short and exact; the visible FAQ text must match the JSON-LD beneath it. Use descriptive anchors like “How do I verify a certificate?” rather than “Certificate?”. When approvals are in scope, add a brief pointer to SIRA Bollards (UAE) for local process context.
114.5 When to use downloads/templates
Any time you need structure: site forms/VDA (912–913), ITP (714), submission index (938), and SAT scripts (638). They reduce rework on HVM bollard projects and ensure crash rated bollard dependencies are captured (421).
Start with 912 Site Assessment Template and the 913 VDA Worksheet. During commissioning, pair 633 Loop & sensor proving with your 714 ITP so witness checks align with the installed configuration.
114.6 Cross-checking with standards
Before naming a product, verify language and acceptance against 411–416. This protects HVM bollard intent and prevents over-claiming a crash rated bollard. Equivalence claims must meet 414.
Confirm the standard (e.g., ASTM F2656, PAS 68, IWA 14-1) at 411, read rating strings at 413, and check any “equivalent to” claims at 414 Standards equivalency.
114.7 Applying examples to your site
Translate examples by matching run-up (222), angles (225), and utilities (241–243). For HVM bollard arrays, adjust spacing (232). For a crash rated bollard, confirm foundation comparability (331–333, 421).
When adapting a reference layout, re-check 222 approach/run-up and 225 angles. If underground conflicts exist, use 242 Underground detection and depth guidance at 422 before finalizing foundations at 330 Foundations & Loads.
114.8 Saving/printing key pages
Print or PDF spacing rules (232), patterns (321–326), and ITP (714) for site folders. Keep HVM bollard commissioning steps (631–639) and crash rated bollard certificate checklists (431) to hand.
For quick field use, save 232 Spacing rules, the array set under 320, and the 714 ITP. When verifying delivered items, keep 431 Certificates and 639 Snagging & Handover nearby.
114.9 Getting support
Escalate via 131 (RACI), cite the affected code (e.g., 323.2), and attach evidence (716). For HVM bollard queries, include spacing photos (232). For a crash rated bollard, include the certificate excerpt (431) and dependency list (421).
Use 131 Stakeholders & Responsibilities to route questions. When raising an NCR, add photographic evidence per 716 Evidence Capture Standards, and point to the exact array rule (e.g., 323 Frontage arrays). For UAE projects, reference SIRA Bollards (UAE) when approvals are implicated.
Related
External resources
- NPSA: Hostile Vehicle Mitigation guidance
- BSI: Vehicle Security Barriers standards overview
- ASTM F2656 overview
114 How to Use This Guide — FAQ
What is the fastest path to choose an array for my site?
Start with 232 Spacing rules, then pick a pattern under 320 Arrays (321–326). Validate foundations in 330 before you draw.
Where do I verify that a product’s crash rating is valid for my installation?
How do I cite sections when emailing consultants or authorities?
Use the visible codes and anchors, e.g., “See 232.3 clear-gap” with a link to the specific H2/H3. Include screenshots or photos per 716 Evidence Capture Standards. For UAE approvals, add a note linking to SIRA Bollards (UAE).
What should I print for site teams and witness tests?
Print 232 Spacing rules, your chosen array page(s) under 320, the 714 ITP, and 638 SAT / Witness Procedure.