112.1 Roles: client, consultant, contractor, vendor

Clients set purpose and risk appetite; consultants translate VDA outputs (221–229) into HVM bollard requirements; contractors build to ITP (714); vendors supply crash rated bollard evidence (431) and commissioning support (631–638). Use the RACI snapshot (131) and submission map (135, 938) so ownership is clear and approvals land first time.

In practice, the VDA and purpose/tier choices cascade into spacing, foundations, and any rating-critical dependencies. Consultants should map these into a concise scope and specification (see 433 — Specification template). Contractors then plan works, temporary traffic arrangements, and QA against 714 — ITP and the commissioning sequence (631–638).

Vendors add value by surfacing the right evidence pack early (see 431) and confirming feasibility for foundations and utilities (421–423). Use the 131 — Stakeholders & Responsibilities RACI snapshot to keep handoffs crisp.

112.2 Readers by background (Civils, MEP, Security)

Civils: focus on foundations, drainage, and set-out (331–336, 612–629). MEP/Security: drives, controls, safety (341–357). All: spacing/arrays (232, 321–326) and evidence (444). Whether you deliver an HVM bollard lane or specify a crash rated bollard line, each section links to your next task and the records reviewers expect (717, 938).

Civils. Start at 330 — Foundations & Loads then check utilities constraints and depth classes (243–244). Align set-out with 320 — Arrays & spacing and 336 — Setting-Out before you pour.

MEP/Security. Use 340 — Electrical & Controls and the interlock matrix (352) to design safe operations. Plan induction loops (344) and run an early FAT/SAT readiness check (715).

Everyone. Confirm 232 — Spacing rules and pick an array pattern (321–326). Capture evidence as you go (see 444 — Evidence & Documentation).

112.3 What you need to know first

Define purpose/tier (123, 235), capture site facts (211–219), and sketch array options (321–326) before talking products. Spacing (232) and standoff (213) are non-negotiable for any HVM bollard layout. If you’ll name a crash rated bollard, read ratings/terminology (411–413) and dependencies (421) so spec wording (433) can lock performance.

Most delays come from unclear objectives and missing constraints. Use the 235 — Purpose/Tier Matrix to set intent, document approach/run-up (222), and record stand-off distance. Only then shortlist systems whose tested footprints and utilities can fit your site (422–423).

112.4 What you don’t need to know

You don’t need finite-element detail to choose between HVM bollard options. Use the decision flow (339) and equivalence notes (414) to stay evidence-based. For a crash rated bollard, certificates (431) summarize what matters; model correlation (416) is optional unless you’re pushing limits. Lean on templates (912–919) rather than inventing formats.

Focus on outcomes and acceptance criteria: penetration class, array clear-gaps, and operability. For most projects, the practical path is to apply 339 — Decision Flow, check 414 — Standards equivalency, and proceed with the right evidence pack.

112.5 Typical questions each role asks

Clients: “Do we need HVM?” Start at 432/443. Consultants: “What rating and spacing?” See 232, 411–416. Contractors: “How do we pass SAT?” Read 631–639. Vendors: “What evidence unlocks approval?” Use 431, 444, 938. When naming a crash rated bollard, confirm dependencies (421) and foundation feasibility (332–334) early.

Fast answers by role:

• Client: Compare 432 — HVM vs Low-Speed and 443 — Selecting Low-Speed vs HVM.
• Consultant: Use 232 — Spacing rules and 413 — How to read ratings.
• Contractor: Plan your route through 631 — Pre-Commission Checklist to 638 — SAT/Witness.
• Vendor: Prepare 431 — Documents & certificates and align with 938 — Submission-Pack Guidance.

112.6 Fast paths for busy readers

Need a yes/no on HVM vs low-speed? Use 432 then 443. Fixing a layout? Jump to 232 and 321–326. Selecting a crash rated bollard model? Read 413 then 421. Preparing handover? Open 731–739. Each path points to the minimum evidence reviewers accept (444, 717, 938). For execution expectations, skim What to Expect During Bollard Installation.

1. Decision: HVM vs low-speed → selection.
2. Layout: spacing rules → array patterns.
3. Product: read ratings → dependencies.
4. Handover: as-builts / O&M / training → closeout checklist.

112.7 How to use checklists/templates

Start with the site form and VDA worksheet (912–913), then the ITP (714) and submission index (938). Checklists embed HVM bollard spacing/height checks (232, 312) and crash rated bollard evidence (431, 421). Using the standard set prevents omissions that cause redesign or rejection.

Download the 912 — Site Assessment Template, the 913 — VDA Worksheet, and the 917 — Submission Index & Covers. Tie these to your ITP and maintain an evidence pack throughout execution.

112.8 Skills you’ll gain by the end

You’ll translate scenarios into defensible HVM bollard arrays (221–229 → 321–326), read and specify a crash rated bollard rating (411–413), and deliver buildable foundations/drainage (331–334, 245). You’ll also assemble reviewer-ready packs (444, 938) and run clean commissioning/SAT (631–638).

Concretely, you will: (a) create a credible VDA that drives array geometry; (b) choose between passive and active systems with correct modes of operation; (c) sequence commissioning to pass SAT first time.

112.9 Where to go next

If you’re early, read 123–125 and 339. If design is live, use spacing/patterns (232, 321–326) and foundations (331–334). If product choice is pending, decode ratings (413) and lock dependencies (421) for your crash rated bollard. If approvals loom, assemble evidence (431, 444) and the submission pack (938).

Recommended next stops:

• 123 — Purposes & performance tiers and 125 — Structured bollard name.
• 232 — Spacing rules and 320 — Arrays & spacing.
• 413 — How to read ratings and 421 — Rating-critical dependencies.
• 938 — Submission-Pack Guidance.

112 Who This Is For — FAQ