Standard sections, figures, and appendices to include.
Package your analysis so it passes review the first time. This template structures front-matter, annotated plans/photos, scenario logic, vehicle/speed tables, vectors/standoff, and sensitivity results. Propose preferred arrays and spacing with references (232, 321–326) and note caveats. Tie sign-offs and versioning to 911/115. The report is the bridge to selection/specification pages (432–435, 433). 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.
229.1 Front-matter & scope
State project, location, date, authors, and scope/limits. Tie the report to drawing sets and codes. This frames HVM bollard conclusions and the crash rated bollard rating recommendation (413).
Open with a clear cover page and transmittal. List the project Site ID, client, and distribution. Add a concise purpose statement: “This Vehicle Dynamics Assessment (VDA) establishes credible impact conditions to support product selection.” Declare inclusions/exclusions and any data reliance (e.g., traffic counts, GIS, surveys). Reference drawing issue numbers and the governing rating standard (e.g., ASTM F2656 or IWA 14-1).
End the section with a short “How to read this report” pointer and a cross-reference to 413 — How to read ratings to keep reviewers aligned on rating strings.
| Aspect | What matters | Where to verify |
|---|---|---|
| Project identity | Consistent Site ID & drawing set | 911 — File Index & Naming |
| Standard | Declared basis for rating string | 413 — Read Ratings |
| Scope & limits | Data sources, assumptions, exclusions | 221 — VDA method |
229.2 Site plan & photos
Annotated key-plan with vector/run-up overlays and wide→detail photos (214, 716). Visuals accelerate HVM bollard understanding and pre-answer crash rated bollard reviewer questions (444).
Provide a legible key plan with vector diagrams, measured effective run-up, and likely 225 — approach vectors. Use wide-to-detail photo sets and mark camera positions. Follow 716 — Evidence Capture Standards for clarity and naming. If UAE approvals apply, note where SIRA-relevant frontages appear and cross-link to the SIRA Bollards (UAE) hub.
Close with a “hotspots” list highlighting doors, corners, and 324 — pinch points that shape arrays and 232 — clear-gap rules.
229.3 Scenario selection
List credible scenarios with reasons (221). A concise table connects to HVM bollard array options and the candidate crash rated bollard bands (411–414).
State the credible worst case and any alternative cases (e.g., lower-probability night-time runs). Each scenario should name the 212 — threat scenario, vehicle class, run-up corridor, and governing impact angle. Keep the list short and defensible.
Map scenarios to rating frameworks and short-list bandings using 411 — Standards overview and 414 — Standards equivalency.
229.4 Vehicles & speeds table
Summarize classes, run-ups, gradients, and resulting speeds (223–224). Speeds map to HVM bollard spacing and to rating strings for the crash rated bollard.
Present a compact table listing 223 — vehicle classes, unladen mass, ride height, run-up length, gradient, surface, and calculated speed (show method: stopwatch/video timings vs. 224 — estimation methods). Where helpful, attach calculations in 922 — Approach-Speed Helper.
Explain how speed outcomes influence 232 — spacing and the recommended rating string.
229.5 Vectors & standoff
Angles, approach lanes, and minimum offsets (225, 213). These drive HVM bollard orientation and confirm the crash rated bollard’s tested orientation envelope (421).
Overlay likely approach vectors and minimum stand-off distance on the plan. Identify governing angles (e.g., glancing vs. head-on) and confirm orientation constraints against 421 — rating-critical dependencies. Reference 213 — Standoff & Protection Zones and 225 — Impact Angles & Approach Vectors.
229.6 Sensitivity summary
Show ± bands and the chosen conservative case (228). This justifies HVM bollard counts and demonstrates margin within the crash rated bollard penetration limit (413).
Summarize the sensitivity band on speed, angle, and mass. State the selected conservative case and why it is credible. Where penetration is the limiter, show that margin against P-value reading. Point to the methods in 228 — Sensitivity & Safety Factors.
229.7 Preferred array options
Two or three patterns with pros/cons (321–326), clear-gap tables (232), and foundation notes (331–334). Each is compatible with the shortlisted crash rated bollard.
Offer 2–3 feasible patterns (e.g., line with near-door reinforcement; 326 — mixed-type arrays). Include a compact clear-gap table per option referencing 232 — Spacing rules and layout pages like 324 — Corners, Islands & Pinch Points. Note foundation class and utilities constraints with links to 333 — foundation checks.
229.8 Assumptions & caveats
Declare what could change—works, policies, or traffic (216, 239). Caveats prevent over-reliance on single HVM bollard numbers and constrain crash rated bollard claims (414).
List the assumptions register: surface friction, seasonal sand/rain, temporary event modes, construction phasing, or policy changes. Flag where new works (e.g., kerbs, rumble strips) could reduce speeds. Link to 216 — Existing constraints and 239 — Temporary/Event Modes. Note any UAE approvals touchpoints and refer to SIRA Bollards (UAE). Keep standards equivalency claims inside the limits of 414 — Equivalency.
229.9 Sign-offs & versioning
Reviewer signatures, version table, and file rules (115, 911). This seals HVM bollard recommendations and locks the crash rated bollard evidence for 938.
Add a reviewer grid with names, roles, and dates. Include a simple version table (Release ID, changes, Issue-for-Use status). Apply 115 — Versioning & Numbering and 911 — File Index & Naming. Archive the signed PDF and source files per 939 — Final Archive & Retrieval and list it in the 938 — Submission-Pack Guidance.
Related
External resources
229 VDA Report Template — FAQ
What is a VDA and why does every project need one?
A Vehicle Dynamics Assessment (VDA) turns site evidence into credible speeds, impact angles, and standoff. It underpins whether you need an HVM solution and what crash rating the bollards must meet.
How detailed should the photos and plans be?
Provide a key plan with annotated run-ups and vectors plus wide-to-detail photos. Follow our Evidence Capture Standards (716) so reviewers can reproduce your findings.
Do I include multiple scenarios or just the worst case?
List the credible worst case and a small number of realistic alternates. Each scenario must state vehicle class, approach, run-up, and angle, with reasons. Keep it defensible, not exhaustive.
Where do I show uncertainty and safety margins?
Use a sensitivity summary with ± bands for speed, mass, and angle, then name the selected conservative case. Explain the margin to penetration limits using rating interpretation (413).