Models that fit and inform.
BIM should prevent clashes and capture data that matters. Define families/blocks and parameters for bollards, sockets, ducts, and panels; set LOD and visibility for plans/sections/3D; and include anchors, sleeves, and connectors. Export rules and naming keep coordination tight and rating-critical dependencies protected in crash rated bollard designs. 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.
932.1 BIM execution plan hooks
Define roles, LOD, naming. A clear plan keeps HVM bollard models aligned with crash rated bollard evidence (911, 444).
Related IDs linked: 911 File Index & Naming Rules · 444 Evidence & Documentation
A solid BIM Execution Plan (BEP) sets who does what, when, and how. Capture naming aligned to our file index rules, model element responsibilities, and approval gates. On first mention, define key terms briefly—e.g., HVM and crash-rated—so every reviewer reads requirements the same way.
Lock the BEP to reference pages that govern traceability and sign-off (e.g., 431 Documentation & certificates, 718 Variations & Change Log). This also helps protect rating-critical dependencies through design changes.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash ratings hub |
| Information | Evidence links & page IDs in BEP | FDS/SAP/ITP/SAT |
932.2 LOD/LOI matrix
LOD for sleeves/foundations; LOI for serials and settings. Granularity preserves HVM bollard traceability and crash rated bollard dependencies (421).
Related ID linked: 421 Rating-critical dependencies
Agree the Level of Development (LOD) for foundations, sleeves, cages, anchors and ducts by design stage. In parallel, set Level of Information (LOI) for serial numbers, foundation class, finish, and control settings. A clear LOD/LOI matrix prevents re-work and safeguards evidence trails across submittals and site changes.
As a rule of thumb: by construction issue, models should carry clear-gap, height, embedment, duct size, and termination points so schedules and shop drawings remain synchronized.
932.3 Interfaces & federations
Federate civils/MEP/controls to see conflicts. Federation protects HVM bollard ducts and crash rated bollard bases (246, 332).
Related IDs linked: 246 Ducting & Pathways · 332 Foundation types
Create a weekly federated model pulling architecture, civils/structural, MEP, and controls. Explicitly model bollard pits, sleeves, trench runs, draw pits, and panel clearances. Use a Clash ID naming scheme and tag each issue with location, array ID, and affected services so decisions are auditable.
Where bollard foundations meet utilities or basements, pull in survey deliverables and shallow-mount options from 248 Survey Deliverables and 244 Shallow foundations to reduce diversion needs.
932.4 Coordinates & datums
Shared base points avoid shifts. Stable grids keep HVM bollard spacing and crash rated bollard set-out consistent (612, 626).
Related IDs linked: 612 Setting-Out & Benchmarks · 626 Datum & Alignment Checks
Use a shared coordinate system (project base + survey point) with a documented “model origin” note in the BEP. A tiny shift can alter array centreline, gap, and footing set-out. Freeze the grid early and publish a “benchmark transfer” method for site.
For remodels or late design changes, include a rotation/translation log so federations remain aligned and installers can verify against the datums & benchmarks pinned in the drawings.
932.5 Parameters & schedules
Tag diameter, height, clear gap, foundation class. Schedules prove HVM bollard counts and crash rated bollard specs (125, 322).
Related IDs linked: 125 Structured Bollard Name · 322 Clear-Gap Calculations
Define a minimum shared parameter set: bollard family, effective height, diameter/section, sleeve type, foundation class, finish, power/loop needs, and lane identifier where automatic systems are used. Use these to drive schedule exports and cross-check BOQs.
Parameter names should match our CAD/BIM Standards (931) so COBie/IFC mappings are predictable across authoring tools and coordination software.
932.6 Clash detection rules
Tolerance bands and priority matrix. Rules prevent HVM bollard pit clashes and crash rated bollard anchor clashes (243, 621).
Related IDs linked: 243 Utilities conflicts & depth classes · 621 Rebar Cages & Anchors
Define “hard” vs “soft” clash sets. Example: bollard foundation vs major utilities (no-go envelope), sleeve vs rebar (minimum cover), ducts vs cage (side clearance), pit vs sump (freeboard). Record tolerances and the priority matrix so everyone understands the auto-flagging logic.
Schedule a recurring clash review (with witness points where needed) and publish a short “disposition” set: fix, accept, or redesign with documented justification and updated drawings.
932.7 Issue tracking
BIM issues linked to Page IDs. Tracking closes HVM bollard defects and crash rated bollard changes (718, 846).
Related IDs linked: 718 Variations & Change Log · 846 Risk Register & Governance
Each clash or change request should store the Page-ID reference, sheet/detail, and decision log. Use short, searchable titles (“Bollard B12 duct crossing S/W 300 at L2”). Maintain a “status lane” (Open → In-Design → In-Review → IFC → Closed) and tie to submittals so approvals align.
For governance, mirror high-risk issues in the risk register with clear owners and due dates. Close the loop in the BEP change control section.
932.8 Exchange formats
IFC/NWC/DWG with property sets. Reliable exchange keeps HVM bollard data and crash rated bollard certificates coherent (431).
Related ID linked: 431 Documentation & certificates
Use open IFC for model handoff, NWC for coordination, and DWG for sheet exchange. Publish which property sets carry HVM essentials (rating string, foundation class, serials, evidence URLs). Where required, export COBie to feed the asset register.
Always include a “self-canonical” document URL in properties so certificates and photos resolve back to the controlled source in 939 Final Archive & Retrieval.
932.9 As-built sync
Push field changes back to models. Sync preserves live HVM bollard records and crash rated bollard audit trails (731, 739).
Related IDs linked: 731 As-Built Drawings & Models · 739 Closeout Checklist & Retention
Capture deviations: actual invert levels, pit sizes, rebar adjustments, duct routes, and panel locations. Update the as-built model and republish schedules so O&M packs stay correct. Link photos and redlines to elements using stable Page-IDs.
Before handover, run a final federation and a “delta” clash to ensure no late interferences were introduced during construction, and align this with 638 SAT / Witness procedure outcomes.
Related
External resources
- NPSA — HVM guidance
- BSI — Vehicle Security Barriers: Impact test specifications
- ASTM F2656 — Crash testing standard (overview)
932 BIM Coordination & Data Exchange — FAQ
What should a BIM Execution Plan (BEP) include for HVM bollards?
Spell out naming and roles, shared coordinates, LOD/LOI targets, clash rules, issue workflow, and how evidence (ratings, certificates, photos) is referenced by Page-ID. Tie it to our CAD/BIM Standards (931) and documentation pages (431, 718).
How do LOD and LOI differ in practice?
LOD governs geometric detail (e.g., foundation shape, sleeve/duct geometry). LOI governs data fields (e.g., rating string, foundation class, serials). Both are needed so schedules, BOQs, and certificates agree.
Which formats should we exchange: IFC, NWC, DWG, or COBie?
Use IFC for model handoff, NWC for coordination reviews, DWG for annotated sheets, and COBie when the client needs a spreadsheet-style asset register. Publish which property sets carry HVM essentials.
How do we keep models in sync with site changes?
Log deviations with photos and redlines, update the as-built model, regenerate schedules, and re-federate for a final clash check before SAT/witness. Keep links back to the controlled archive for auditability.