Readable sheets, consistent metadata.
Drawings succeed when anyone can find, read, and trust them. Standardize sheet sizes, views, scales, legends, and title blocks with project, revision, and Page-ID fields. Add array/spacing codes, foundation types, and setting-out data. Consistency reduces errors in fabrication and install, and speeds approvals for HVM 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.
915.1 Sheet sizes & scales
A1/A3 standards; consistent scales for arrays and details (321–324). Readability protects HVM bollard clarity.
Use A1 for design packs and A3 for site/print-on-demand. Keep a single primary scale per sheet; reserve insets for details. Arrays from 320 Arrays & spacing and patterns in 321 Array Patterns should be drawn at clear, repeatable scales (e.g., 1:100 for layouts, 1:20 for trench/duct sections). Mark the scale next to each viewport.
Always show a graphic scale bar and north arrow so printed and PDF views match measured intent. For tightened detail, keep arrays, clear-gap checks, and foundations on separate callouts that reference the parent sheet.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
Cross-reference layout scales to detail scales so reviewers can jump between 322 Clear-Gap Calculations, 332 Foundation types, and 934 Ducting & Trench Details.
915.2 Title block fields
Project, Page ID, sheet number, rev, status, drawn/checked/approved. Trackable through 911.
Minimum fields: Project name & Site ID; Page-ID; sheet title & number; revision code; issue status (IFC/IFA/IFU); dates; Drawn / Checked / Approved initials; scale; units. Page-ID and file naming must follow 911 File Index & Naming Rules so PDFs remain searchable.
Add controlled document elements where needed: approval stamp, revision history, and a QR pointing to the current record in the transmittal or 939 Final Archive & Retrieval. For UAE jobs, include authority sheet notes (e.g., SIRA submission identifiers) on the cover or in the title block comments.
915.3 Layer & color rules
Civils, electrical, drainage, controls separated. Prevents crash rated bollard confusion in overlays (347, 246).
Adopt a layer naming convention that separates civils (foundations/setting-out), electrical (power/controls), drainage, and field devices. Keep colors consistent with 931 CAD/BIM Standards. This reduces clashes between 347 Enclosures & Cabling and 246 Ducting & Pathways when xrefs are stacked.
Keep bollard geometry on distinct layers from duct banks, sumps, and draw pits; lock non-editable xrefs to avoid accidental edits. Publish a legend of layer names in the pack for quick checks.
915.4 Symbols & legends
Standard heads, sleeves, ducts, loops, beacons (313, 344–345). Legends avoid misreads.
Use a governed symbol library: bollard 313 heads & attachments, sleeve outlines, 344 induction loops, 345 beacons & detectors, and cable routes. Each symbol must carry a short tooltip/description in the legend plus a drawing note for unit and device IDs.
Legends live on the first sheet of each discipline subset and reference the symbol file path. If a symbol deviates (e.g., site-specific beacon), tag “VARIANT” and include a brief note explaining why.
915.5 Dimensions & tolerances
Show clear gaps, heights, offsets (232, 312). Tolerances match 315.
Dimension the 232 spacing rules and 312 height setting explicitly: finished level (FFL), top-of-bollard height, and clear-gap rule. Tolerances must align with 315 Tolerances & Manufacturability—state installation tolerances separately from product manufacturing tolerances to avoid ambiguity.
Call out offsets from control lines/benchmarks and show a datum & benchmarks diagram. Where utilities constrain depth, reference 243 utilities conflicts & depth classes.
915.6 Detail callouts
Reference 931 typicals and 934 trenches. Links speed review.
Use keyed callouts that point to standard details first, then to project-specific variants. Foundation selections should reference 933 Foundation typicals and trench/duct sections to 934 Ducting & Trench Details. For submission packs, cross-link to 938 Submission-Pack Guidance so reviewers can follow a predictable path.
Each callout bubble must include sheet number and detail ID. If a nonstandard variant is used, add a short “variance reason” note on the parent sheet.
915.7 Revision clouds & notes
Highlight changes; note reasons (118). Reduces drawing churn.
Apply revision clouds only to changed geometry/text and place a numbered delta next to the cloud. In the revision table, log the reason succinctly and keep the 118 Change Log consistent with transmittals. For “approval only” changes, use status codes and avoid mixing design edits with administrative fixes in the same rev where possible.
For multi-discipline updates, list affected sheets under a “Change note” panel and update the transmittal log reference in the title block.
915.8 As-built conventions
Hatch or color for deviations; tag 626 checks. Keeps crash rated bollard records honest.
On as-built drawings, retain the original design layers and add a dedicated “ASBILT” layer group. Use a consistent hatch or color code to show deviations (e.g., moved array line, depth change). Link measurement notes to the 626 Datum & Alignment Checks and include evidence references if needed.
Publish a short legend explaining as-built symbology and reference where evidence resides (e.g., “Photo 12, 937 Photo/Redline Logbook”). Final packs should also be indexed in 731 As-Built Drawings & Models.
915.9 Plot & export
PDF settings, line weights, fonts. Outputs render cleanly in 938.
Export to PDF using embedded fonts and vector linework. Keep line weights legible for A3 print—test one sheet before batch plotting. Include bookmarks and a bookmarked PDF index where applicable. Place the scale bar and north arrow on any sheet with measurable geometry.
Verify the final set against 938 Submission-Pack Guidance (file names, issue status, and self-canonical links in the pack page). If the project requires authority approvals (e.g., SIRA), ensure submission PDFs meet local title/metadata rules.
Related
External resources
915 Drawing Sheet & Title Block Standards — FAQ
What is the minimum information a title block must include?
At minimum: project name & Site ID, Page-ID, sheet number & title, revision & issue status, dates, scale, units, and Drawn/Checked/Approved initials. For authority submissions, include any mandated stamps or notes.
How should arrays and clear-gaps be shown on layouts?
Draw arrays at a consistent layout scale (e.g., 1:100) and dimension the clear-gap between bollards. Reference any calculations on a companion sheet and cross-link to standard details.
When do I use revision clouds versus a simple note?
Use revision clouds to mark geometry or note changes that affect design, coordination, or installation. Minor administrative edits (typos, title tweaks) can be recorded in the revision table without clouds.
What are the key PDF export settings for submissions?
Embed fonts, keep vector linework, verify line weights for A3 printing, add bookmarks, and confirm file names/metadata match the submission index. Test a single sheet before batch plotting.