Repeatable template with metrics, photos, and lessons.
Use this template to turn projects into teachable, approval-ready stories. Capture context, risk/purpose, and why the design selected HVM bollards or crash rated bollards (432–434). Summarize installation/QA (611–629, 714), commissioning/SAT (631–638), and outcomes/KPIs (542, 544). Close with lessons and links to evidence (431, 444, 938) so reviewers and new readers can validate decisions and replicate success. 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.
831.1 Context & objectives
Summarize site, threat, people flow, and the measurable outcomes. Link to assessment (211), VDA scope (221), and stakeholder aims (131). Frame why an HVM bollard or crash rated bollard solution was required.
Open with a clear site summary: location, frontage uses, peak flows, and any nearby critical assets. State the Design Basis Threat (DBT) in plain language and connect it to intended outcomes (e.g., prevent hostile access, protect glazing). Cross-reference your Site Assessment Checklist (211) and Stakeholders & Responsibilities (131) so reviewers can see inputs and accountable owners.
State measurable objectives and KPIs—throughput, Ops/hour & cycle time (542), availability—and how they’ll be evidenced later in Operational Dashboards (544). Briefly justify “HVM vs low-speed” with links to Design Selection Guide (432) and Low-Speed Evidence (444).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read ratings (413) |
| Operations | Duty cycles, fail-state, safety | Fail-safe/secure (355) |
831.2 Site & constraints
Capture utilities, slabs, groundwater, visual/heritage limits (216, 241–245, 334). Explain how constraints shaped HVM bollard and crash rated bollard feasibility.
Summarize constraints from Existing Site Constraints (216) and Utilities searches (241), noting conflicts, PT slabs, and groundwater. Record drainage needs with Drainage strategy (245) and foundation dewatering risks referenced later in 334.
Explain what these mean for depth classes and constructability. If heritage or view-corridor limits apply, note any height or finish constraints and cross-link to Color & Aesthetic Finishes (366).
831.3 VDA & risk baseline
Present scenarios, vehicles, run-up, angles, sensitivities (221–229). Show why HVM bollard over low-speed—or vice versa—was justified (432, 434, 443).
Summarize your VDA method (221): approach/run-up (222), vehicle classes (223), speed estimation (224), and impact angles (225). Include a brief sensitivity note (228) showing which inputs govern the tier choice.
Conclude with the selection logic: cite 432, when 443 allowed low-speed, and when 434 mandated HVM. This anchors risk to a defensible standard-led basis.
831.4 Options considered
List short-listed types/patterns with pros/cons (124, 321–326). Note when a crash rated bollard family/variant was swapped and why (415, 435).
Show the short list using Bollards by Function (124) and array patterns (321, 326). For each option, capture spacing, depth class, drainage, and operational fit. If a product family/variant (415) changed, explain the trigger (e.g., utilities conflict) and guard against scope drift with anti-downgrade clauses (435).
831.5 Arrays, spacing & foundations
Show clear-gap calcs and edge cases (232, 322, 324) with chosen foundation type (331–334). Tie decisions to HVM bollard performance.
Document clear-gap rules (232) with worked examples and calcs (322), noting corners and pinch-points (324). State the selected foundation approach and why—e.g., foundation type (332), checks (333), and drainage (334). Tie each choice back to certificate scope and as-tested configuration.
831.6 Controls, safety & operations
Summarize drives, logic, interlocks, signals, and EFO/fail states (341–355). Explain operator impacts around HVM bollard lanes and crash rated bollard arrays.
Capture the chosen drive type (341–345), core logic with state machine/interlocks (526), and safety devices & measures like signals (353), EFO (354), and fail-safe/secure (355). Note operator workflows and error-proofing (545), including degraded states and recovery steps.
831.7 Evidence & results
Embed certificates, SAT excerpts, photos/overlays (431, 638, 936). Prove each HVM bollard or crash rated bollard claim with traceable media (911).
Provide a compact evidence pack: link certificates (431), SAT excerpts with witness procedure (638), and annotated overlays following Mark-Up & Overlay Standards (936). Ensure filenames and indices follow the File Index & Naming Rules (911) so reviewers can audit the chain.
831.8 Cost, programme & VE
Record milestones, variations, VE guardrails, lifecycle notes (855, 338, 842). Show value without downgrading crash rated bollard intent.
Summarize schedule highlights with Programme & Phasing (855), and document approved variations. Show any Value Engineering (338) decisions alongside “no-downgrade” constraints. Add lifecycle insights and service outcomes referencing Lifecycle & maintenance (842).
831.9 Lessons & links
Write what to repeat/avoid, then link to tools/templates used (912–919). Aid reuse across HVM bollard and crash rated bollard projects.
Close with 5–7 practical lessons (design, build, operate). Then link the exact tools you used: Site Assessment Template (912), VDA Worksheet (913), Witness & Inspection Forms (918), and Handover Pack Checklists (919). For authority submittals, see Submission-Pack Guidance (938).
Related
External resources
- NPSA: Hostile Vehicle Mitigation (risk & planning)
- ASTM F2656: Crash test standard overview
- BSI: Impact test specifications (standards & terminology)
831 Case Study Template — FAQ
What documents should I attach to a case study?
Include the product certificate and test summary (431), key SAT excerpts (638), marked-up photos per overlay standards (936), and an index that follows the File Index & Naming Rules (911). Link to your Submission-Pack Guidance (938) for completeness.
How do I decide between HVM and low-speed bollards?
Use your VDA baseline (221–229) to set credible speed/angle scenarios, then apply Design Selection Guide (432) and When to use low-speed vs HVM (434). If low-speed is chosen, comply with Evidence & Documentation (444) to avoid under-specification.
What installation milestones should be summarized?
Summarize pre-works and permits (611), set-out (612), foundations and pours (621–627), backfill/reinstatement (628–629), and the ITP points (714). Then cover commissioning steps (631–637) and SAT/witness (638).
Which KPIs prove operational success?
Track Ops/hour and cycle time with alert thresholds (542), uptime and availability via dashboards (544), and any safety-related KPIs (e.g., nuisance alarms). Include a short notes section on data sources and how anomalies are handled.