931.1 Purpose & scope

Set drawing/model rules so HVM bollard layouts and crash rated bollard details are readable and reviewer-ready across all trades (852, 717).

These standards define how teams build and publish GA drawings, sections, and coordinated BIM views so reviewers can quickly validate HVM intent. We reference the file index & naming rules (911), sheet/title-block standards (915), and submission-pack guidance (938) to keep outputs consistent.

Scope covers civil works (levels, drainage), foundations and ducts, power and controls, and signage/markings. Outputs must trace back to security requirements and rating evidence (see global crash ratings (410)).

Success looks like: (a) repeatable layer naming, (b) correct sheet codes and zones, (c) clear acceptance bands around key dimensions, and (d) clean exports for PDF/DWG/NWC that pass model audits before issue.

931.2 Sheet set & numbering

Use consistent sheet codes tied to Page IDs and zones. This keeps HVM bollard arrays and crash rated bollard foundations traceable (911, 915).

Build a master drawing register keyed to the Page-ID reference (911). Sheet numbers pair discipline + area + sequence (e.g., “C-Z2-210”). Title blocks adopt the same client/site data used in 915: Drawing Sheet & Title Block Standards so reviewers see a familiar layout.

Organize sheets into sets: Site & Levels; Foundations & Details; Ducting & Draw-pits; Power/Controls; Signage & Markings. Cross-reference to related guidance like 322 Clear-Gap Calculations and 333 Foundation design checks.

Every PDF should be a bookmarked PDF with a clickable index matching the drawing register to speed review in workshops and remote calls.

931.3 Layers, linetypes, colors

Standardize civils, drainage, power, control layers. Clear layering prevents HVM bollard clashes and crash rated bollard misreads (347, 246).

Adopt a sitewide layer naming convention (e.g., DISC-CODE-ZONE-STATUS). Separate proposed vs existing, isolate services by voltage/type, and keep duct banks, draw pits, and loops on distinct layers (see 246 Ducting & Pathways and 347 Enclosures & Cabling).

Linetypes/colors signal meaning, not style: proposed = continuous strong; existing = dashed light; protection zones = chain; underground utilities by discipline color. Freeze/lock external references during plotting to avoid accidental overrides; publish a “layer matrix” on the project wiki or in the document matrix.

Common pitfalls: mixing units (metric/imperial), plotting “color by entity,” or exploding xrefs. Enforce a template CTB/STB and prohibit ad-hoc overrides in Issue-for-Use sets.

931.4 Symbology & blocks

Provide approved blocks for heads, sleeves, loops, beacons. Symbols protect HVM bollard intent and crash rated bollard safety (313, 344–345).

Maintain a signed library of parametric blocks: bollard heads, sleeves, induction loops (344), field beacons & devices (345), glands, and north arrow/scale bar. Use attributes for IDs, materials, and as-tested configuration when relevant.

Block geometry must include anchor points and rotation constraints. Provide 2D/3D variants and plan/section/isometric symbols. Protect the library under version control and list it in the drawing register so only approved symbols appear in issue packs.

931.5 Dimensions & tolerances

Show clear gaps, offsets, heights with acceptance bands. Precise dims preserve HVM bollard spacing and crash rated bollard compliance (232, 312, 315).

Dimension the clear-gap rule (232), centreline offsets, finished heights (312 height setting), and installation tolerances (315). Add an acceptance band to each critical dimension and show a note for survey benchmarks and datums.

Where bollards are “keepered” (lift-out or automatic lanes), publish the keepered dimensions and minimum effective width. Include a simple step-through gauge diagram or refer to the Go/No-Go gauge used at SAT.

931.6 Coordination views

Publish plan/section/isometric views for utilities and ducts so HVM bollard routes avoid conflicts with crash rated bollard sockets (241–246, 332).

For each array, include: (a) plan with utilities clash zones (241–246), (b) long/short sections showing sockets, ducts, and draw-pits, and (c) isometrics around congestion. Tie these to 332 foundation types and show minimum offsets to red-zone utilities from 242 Underground Detection.

Provide view templates (scale, visibility, filters) and a legend for no-go envelopes. For shallow rails and trenches, call out sump locations and gradients, with references to 245 Drainage strategy.

931.7 Revision control

Clouds/notes reference 118; PDFs carry rev/date. Control prevents accidental HVM bollard downgrades and crash rated bollard drift (435, 537).

Follow the site 118 Change Log convention. Use a consistent revision cloud style and delta notes; stamp “Issue-for-Use” when approved. Cross-link rev history to 435 Anti-Downgrade clauses and 537 Change Control & Versioning so the rating string cannot be weakened by edits.

Each PDF title block shows Rev, Date, Author, Checker, and status; the drawing register mirrors that, including superseded references.

931.8 Export & deliverables

PDF/DWG/NWC with xrefs bound. Clean exports speed HVM bollard reviews and crash rated bollard SAT prep (638).

Deliver a tri-format pack per set: bookmarked PDF; clean DWG(s) with xrefs bound or eTransmitted; and NWC/NWD for model review. Ensure units, origins, and coordinate systems are consistent; purge unused layers/linetypes, audit files, and regenerate before archive.

Name files per 911 Index and include a SHA-256 checksum manifest. For witnessed sets, include the SAT reference from 638 Witness Procedure.

931.9 Model audits

Run clash/QA checks before issue. Audits stop HVM bollard rework and crash rated bollard NCRs (858, 719).

Before publishing, run a lightweight clash against utilities and structure; verify levels, slopes to sumps, and socket depths; and confirm keepered dimensions. Record results in a “clash log” and close out actions.

Quality assurance: check layer purity, purge results, title-block metadata, and that every sheet appears in the register. Link audits to 858 Quality Audits & Surveillance and 719 Nonconformance & Defects so findings are traceable.

931 CAD/BIM Standards — FAQ