Minimum drawing set and redline conventions.
As-builts prove what was actually installed, protecting the HVM bollard design intent and each crash rated bollard’s certification. Capture coordinates/benchmarks (612), utilities/ducts (241–246), foundations/rebar (331–333, 621), and panel/cable routes (347–348, 515). Record deviations with redlines (937), export in standard formats (931), and secure stamps for submission packs (938) and authority closeout (717). This page sits under this section and the broader chapter hub. For UAE projects involving approvals, see SIRA Bollards (UAE) for context on what reviewers expect at handover.
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.
731.1 Required documents
Issue marked-up plans, sections, and schedules. As-builts anchor HVM bollard acceptance (638).
At minimum, compile redlined general arrangement plans, foundation/section details, electrical/control layouts, and schedules that cross-reference device IDs and serials. First mention of any jargon is kept simple: an as-built drawing is the final record of installation. A witness pack (638) can only be closed when these records match the field reality.
Plan sets should map cleanly to the file index & naming rules (911), and they should be exportable as both printable PDFs and modifiable CAD/BIM files for future maintenance. Link the set to the snagging & handover workflow (639) to avoid rework.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Installed system = tested model (bollard + footing) | Global crash ratings |
| Operations | Duty, fail-state, safety devices & measures match drawings | Installation Guide |
731.2 Coordinate system & datums
State grid/benchmarks used (612). Consistent datums protect crash rated bollard traceability.
Document the project grid, survey control, and datums & benchmarks that were actually transferred to site (612). Show at least one key plan with northing/easting ticks and a level reference (e.g., ±0.000 = finished floor). This ensures later surveys, maintenance, or replacements can locate each unit precisely, including re-establishing datum & alignment checks (626).
731.3 Foundation details
Show socket dimensions, rebar, concrete classes (333). Details preserve HVM bollard certification (421).
Provide final foundation types and dimensions with reinforcement (bar size/spacing), concrete class, and any design checks (333) relevant to the installed unit. Because HVM performance is system-dependent, the socket geometry and concrete specification are rating-critical dependencies (421). Include any approved deviations (e.g., alternative grade beams or shallow foundations 244) and reference the corresponding approvals in 717/718.
731.4 Services & ducts
Record actual duct routes, depths, IDs (615). Records support crash rated bollard maintenance.
As-built duct banks, draw pits, and cable pathways must include route geometry, depth from finished level, conduit IDs, and pit references (615, 246). Note any changes from the design utilities layout (240–247) and keep drawings consistent with ducting & trench details (934). Clear duct mapping reduces fault-finding time and helps avoid utility strikes during future works.
731.5 Levels & clear gaps
List final head heights and verified gaps (232, 626). Values prove HVM bollard compliance.
Report the finished bollard head height and the verified clear-gap at each array position. Include any measured tolerances and the results of alignment checks (626). These values link directly to the spacing rules (232) that underpin site safety and certification intent.
731.6 Panels & wiring
Panel locations, enclosure types, cable tags (347, 515). Clarity speeds crash rated bollard fault-finding.
Mark the final locations of control panels and enclosures, ingress ratings, door swing/clearances, and the cable schedule identifiers (515). Tagging should follow the enclosure layout & access (528) and cables & routing (515) guidance. Where panels moved from the original design, note the reason and cross-reference the approved change request (718).
731.7 Change log
Link revisions to CRs/NCRs (718–719). Logs keep HVM bollard history clean.
Maintain a tabulated log of all drawing revisions with dates, description of change, and references to the relevant variations & change log (718) or NCRs (719). This provides traceability and prevents outdated information from creeping into the submission pack (938) or the final archive (939).
731.8 Photo index
Before/after, key details, geo-stamped (716). Photos strengthen crash rated bollard records.
Include a structured photo/redline logbook (937) with “wide→detail” sets, geo-stamps, timestamps, and filenames that match the evidence capture standards (716). Index photos to drawing callouts so a reviewer can jump straight to the relevant frame during SAT witness (638) or later audits.
731.9 File formats & naming
PDF/DWG with 911 naming. Standardization streamlines HVM bollard handover (736).
Deliver layered, purged DWG (or native BIM) plus locked, print-ready PDFs. Follow CAD/BIM standards (931) and file naming rules (911) so the handover pack index (736) can be assembled without manual renaming. Lock the released bundle in the final archive (939) and list any superseded files.
Related
External resources
- ASTM F2656 (Crash-Rated overview)
- NPSA — HVM Guidance
- BSI — Vehicle Security Barriers (standards & terminology)
731 As-Built Drawings & Models — FAQ
What drawings are mandatory in an HVM bollard as-built set?
At minimum: redlined general arrangements, sections/foundation details, electrical/control layouts, and device/cable schedules that reference IDs and serials. Include a photo index and a change log linked to CRs/NCRs.
How do I show coordinate control and levels correctly?
Declare the project grid and benchmarks used on site, show the level datum (e.g., ±0.000), and include coordinates/levels on plans and key sections. Cross-reference Setting-Out & Benchmarks (612) and the alignment checks (626).
Why do foundation details affect certification?
Crash performance depends on the installed system (bollard + footing). Socket geometry, reinforcement, and concrete class are rating-critical dependencies; if they change, approvals and evidence must reflect the final installation.
What formats and naming should I use at handover?
Provide print-ready PDFs and editable CAD/BIM files. Follow the site’s File Index & Naming Rules (911) and CAD/BIM Standards (931) so the Handover Pack Index (736) can be compiled quickly and audited later.