ArchHubBABOOMDownload

Drawings sheets annotation and issue outputs

BBM-STD-67 · V0.2 · The documentation lead maintains one project drawing index

Download WordFormsAll standards

Ribbon tools that apply it: Sheet Maker, Copy Sheets to Project, BABOOM Export, Renumber, Duplicate Sheet Numbers, Align Viewports, Revisions, Keynotes, Legends, Title Block & Text Check

BBM-STD-67-DRAWINGS_AND_SHEETS-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft

Revision history

VersionDateChange
V0.12026-10-16Initial controlled WIP draft.
V0.22026-11-04Closed audit rows: 5.1 Dubai BIM permit drawings (circulars 9-1-2/9-1-3), relinked Manual V0.4/BEP V0.5, title-block superset, SYN-REQ66 reference, ISO 5457/ISO 216 margins, DDA Circular 400 pointer, IMI Framework naming; minimum text 2.5 mm; discipline prefix per BBM-STD-93; spacing fixes + cross-doc pointer pass. + template alignment (..148)

1 Drawing set index and identity#

This standard covers,054,055,056,058 and 059. The documentation lead maintains one project drawing index; discipline leads own design content; independent reviewers check graphics and references; delegated authorisers release only the defined scope. Use Manual V0.5 §4/§7/§8/§9, BEP V0.5 §8.3/§8.4, BBM-STD-51, BBM-STD-65, BBM-STD-66 and the editable sheet/output pack. Native title blocks, specimen sheets and exports below are specifications awaiting application checks.

Retain internal sheet grammar DISC-CAT-INDEX: discipline prefix = the one-letter ROLE code from BBM-STD-93, two-digit category and three-digit allocated sequence, e.g. A-10-101. Category 01=general notes/index,10=plans,20=sections,30=elevations,40=details,50=schedules. Record zone/level/system separately in the index; do not add unapproved filename tokens. Multiple zones need distinct allocated sheet numbers, not duplicate A-10-101 records. Stage/set requirements are derived from the appointment and Manual §7.1, with actual exclusions approved; a generic minimum list cannot replace purpose-led delivery scope.

The external logical container uses BBM-STD-51's eight tokens and four-digit NUMBER, e.g. CLI-OFF-P001-Z01-L01-DR-A-0002.pdf. CLI/OFF/P001 are fictional approved token values. Native sheet number A-10-101 maps one-to-one to that logical container for its declared use; PDF and DWG variants share its stem and source revision. Rnn, suitability and CDE state are metadata, not extra identity tokens. Unchanged sheets retain their actual revisions; a pack IssueID does not force a false revision change on every sheet. Reconcile sheet index, title block, revision schedule, output filenames, variant manifest and transmittal; no issued sheet is renamed to tidy history.

2 Title block field and native mappings#

ISO 7200:2004 informs identification, descriptive and administrative fields; it is not a mandated office logo/layout. Retain Manual §4.10 native family names BBM-G-TTB-A0, BBM-G-TTB-A1, BBM-G-TTB-A2 and BBM-G-TTB-A3; the hyphenated labels in the asset specification are logical shorthand only, with exact family/block names and hashes recorded at adoption. Required fields are project title/code, sheet number/title, discipline, zone/level where applicable, scale or As indicated, revision/date, permitted issue purpose/suitability, originator/designer/checker/approver functions and controlled document/container ID. Record language, sheet count/index relation and owner/rights particulars where required by the appointment. No scanned seal or signature substitutes for actual authorisation. The mandatory field list itself is owned by Manual V0.5 §4.10 (ISO 7200 data fields plus ISO 19650 metadata: container ID, suitability, purpose of issue, approver, sheet n of N and the others listed there); this standard adds only the CDE state as a recorded field.

Title fields map authoritative register values to native Revit built-in Sheet Number/Sheet Name, revision schedule and project information; controlled shared parameters cover custom fields only after BBM-STD-72 reconciles their GUIDs. DWG title-block attributes use the same semantic field keys and one source value. Title fields specifies native destinations and actual-definition holds; never invent a custom shared GUID. Place any secondary language below the title without overlap, with approved glyphs/readability. Preserve designated approval zones and printable margins. Date is ISO 8601; role labels in synthetic examples are not real signatures.

For the valid specimen, project SYN-P001, sheet A-10-101, Level 01 General Arrangement Plan, zone Z01/level L01, R01 dated 2026-10-16, scale 1:100, SU-REVIEW/WIP and roles SYN-AUTHOR67/SYN-CHECK67/SYN-APPROVER67 are fictional particulars only. Approver field is explicitly Pending; SU-REVIEW is the intended fixture metadata and no actual submission/release is claimed. Live review, authorisation and recipient decisions are blank/Not executed in Acceptance. Do not stamp an issue purpose that has not been authorised.

3 Sheet composition scales and cross references#

Use approved A0, A1 landscape 841x594 mm, A2 landscape 594x420 mm or A3 landscape 420x297 mm title-block variants; portrait requires a registered native layout, not rotation/cropping of an unsuitable block. Use one primary view except schedule-only sheets; key plans/legends/details support it and must not obscure content. Sheet sizes and scales are selected for purpose/recipient legibility; plans 1:100 and sections 1:50 are the synthetic baseline, details 1:5/1:10 where required. Mixed view scales use title-block As indicated and explicit view titles. Do not scale the printed page to fit a missing margin.

SYN-SHT67-VALID specifies A1 landscape; protected 20 mm left and 10 mm other edge margins follow ISO 5457 (sizes and layout of drawing sheets) on ISO 216 A-series sheets, subject to actual device printable-area qualification. Reserve title zone x651..831, y10..150 mm, main plan region x30..620, y170..550 mm and key/legend region x651..821, y180..540 mm, measured from lower-left paper origin. The 6x4 m fixture room at 1:100 occupies 60x40 mm before annotations and sits at x100, y300 mm. This is a reproducible composition specification, not an issued drawing. The section sheet contains the same room's 3 m height at 1:50 = 60 mm. All view titles include reference number, name and scale; north arrow is tied to the approved BBM-STD-63 orientation, not hand-rotated.

Use stable grid/level IDs, aligned datums and measured dimensions from the source. Paired matchlines have reciprocal sheet/view references, adjoining scope/overlap and an agreed cut position; section/detail/elevation bubbles resolve to actual index targets. The References sheet has source/target sheet and view IDs, zone/level, revision and checker evidence. Reject A-10-101 duplicates, missing A-20-201 target, conflicting scale, orphan matchline or title/index revision mismatch. Record referential dependencies and rerun both ends after a sheet split/renumbering. Keep internal CAD layers separate from sheet and container identities.

4 Graphics annotations schedules and specification links#

Keep Manual §4.1/4.2 category/cut/projection hierarchy and scale-specific Revit lineweight tables. Use BBM-STD-66's proposed CAD lineweight/CTB specimen as its single CAD width source; Revit pen-to-millimetre widths per view scale follow the Manual V0.5 §4.1.1 table, confirmed by test print. Compare plots side by side at intended sheet scale. Cut poche conveys material/solid cut without hiding openings, fire/structural interfaces or dimensions; background links are subordinate but legible. Use approved patterned fills, symbol/arrowhead assets and controlled legends; no contradictory legend, unapproved colour or invisible required line.

Minimum plotted text height is 2.5 mm on all sheets, measured at paper size and not scaled by view; title text heights follow Manual V0.5 §4.3. Dimensions are associative, architectural values whole mm, no falsified text overrides; arrow/tick sizes follow Manual §4.6. This is an office rule, not an ISO universal minimum. Apply text case, font, hatch and annotation-scale rules from Manual/66. Bilingual content needs approved font/glyph/line-break verification. Crosshatching and tile/module patterns must preserve physical meaning and remain readable at intended scale.

Schedules come from the same source snapshot as drawings with stable element IDs, declared fields/units, filters/itemisation and required totals; check itemised data before grouped presentation. SYN-DOOR67 has one D- door 900x2100 mm; tag and schedule show that same Mark, Width and Height. No manually typed schedule value replaces the model. Legend entries and keynotes have stable controlled codes/version/source, with keynote 10.20.30 referring to fictional specification SYN-SPEC67 section 10.20.30 R01. Verify that actual specification exists and matches current detail/material intent before real use; this fixture is text-only. Do not use a classification code as a specification clause without an explicit mapping. Abbreviations are expanded once and unambiguous; unresolved acronym/keynote/spec links hold affected release.

5 Output profiles signatures and visual review#

Freeze native source model/hash/revision, view/template/title-block/dictionary assets, exporter/driver and output preset/hash, format version, units, page setup, CTB if CAD, fonts and receiver. PDF profile SYN-PDF67 R01 uses exact media, no Fit-to-paper, printable margins and tested vector/raster settings; embed fonts where permitted, otherwise qualify an approved substitute and compare glyphs/line breaks/widths. DWG profile reuses SYN-REQ66/SYN-PLOT66 R01 plus the appointed export map and isolated clean-open checks; no unsupported proxy/resource loss. Record same-snapshot PDF/DWG variant hashes and page count. One file per sheet is the default qualification specimen, with any combined review set a separately identified derivative.

Full-sheet review checks completeness, orientation, hierarchy, margins, index/title/revision, cropping, colour/screening and coordination. Critical-detail review at intended print size checks smallest text, dimensions/arrows, overlapping tags, hatches, schedule rows, symbols, matchlines and warning/risk notes. Use nine tiles covering each entire sheet plus targeted critical details; no skipped edge/title region. Compare a known 6000 mm model length as 60 mm at 1:100 and the 100 mm paper bar using BBM-STD-66's synthetic plot criterion. Reopen in the actual recipient PDF/DWG tool and produce/measure a physical print where required. A preset name or green automated check is not this visual evidence.

If digital signing is required, record the applicable authority/appointment profile, authorised signatory/delegation, certificate verification/revocation and validation time, exact pre/post-sign hashes, signature scope and receiving verification. No signature is applied in this task and no legal effect is asserted. Any content change after signing requires a new controlled output/signature decision. Do not insert someone else's seal to make the fixture look complete.

DDA Circular 400 is registered once in BBM-STD-57, with its verified URL, date and subject; the current Final Design Approval service carries a current document checklist. BBM-STD-57's owner must reconcile the exact project route/portal profile and current instrument before adopting either; this office PDF/DWG test does not claim to satisfy DDA submission by itself. DM openBIM and ADM infrastructure exchanges have separate applicability. No fee, turnaround promise or UAE-wide drawing mandate is provided.

5.1 Dubai BIM permit drawings#

Scope test, recorded per project through BBM-STD-57 and BBM-STD-85: DM circular 9-1-3 (15 January 2026, effective 1 April 2026) requires architectural and structural BIM with the permit for new buildings above G+12 or of 15,000 m² or more, and for the listed alterations (adding or removing floors, adding 1,500 m² or more, full redesign, change of main use, relocation on the plot); other alterations need a final BIM model before the completion certificate. Circular 9-1-2 (13 October 2023) already requires Open BIM submission from 1 January 2024 for buildings over 20 floors (architectural) or 40 floors (structural), over 20,000 m² (architectural) or 30,000 m² (structural), specialised buildings such as hospitals and universities, and government projects. When the test applies, every permit sheet is generated from the submitted model, with no detached 2D sheets, and the drawing index records model-to-sheet traceability (source model, revision and hash per sheet).

6 Asset specifications rejection and issue control#

Asset specs defines title blocks, output presets, annotation/spec/legend dependencies and sheet specimens with owners, revisions/hashes and tests. The Valid/rejected specimen records are filled synthetic examples: valid layout/control data; duplicate number and stale revision; wrong scale/missing section target; and substituted-font/edge clipping failure. Mutations are tested independently from the valid baseline. Actual native/output results stay Not executed; none of the specimen descriptions is a passed issued sheet.

Before issue, producer freezes the scope, independent discipline and drawing reviewers resolve all mandatory failures, authoriser records permitted use and transmittal/recipient list, then recipients acknowledge exact variants. Reconcile every index entry against actual sheet count/file/name/revision/size/hash and all references. Retain prior issues, withdraw superseded copies through the CDE process and notify affected parties under one ChangeID. If output fails, restore the preserved source/preset baseline and regenerate/review; do not patch an issued PDF alone. Actual title-block creation, model drawing, signing, print/export and recipient acceptance are Not executed by this editorial pack.

References#