BBM-STD-11-DECISIONS-LOG-V0.7 · Office standard · Revision date 5 November 2026 · Private controlled copy
Conflict records carried from the drafting lanes#
Drafting-lane conflict records cited by the set. Each is resolved here; its current home section is named.
| Record | Document | Resolution | Basis |
|---|---|---|---|
| W1-C01 | BBM-STD-51 V0.2 §4; BBM-STD-82 V0.2 §2 | The eight-token external identity (BEP V0.5 §8.3) applies; the Manual five-token wording is a legacy internal alias only. Guides that cite Manual V0.1/BEP V0.2 need an owner-reviewed mapping to Manual V0.5/BEP V0.5 (BBM-STD-82 §2 enrolment gate); issued guides are not rewritten. | Reconciles the retained wording without a second naming authority |
| W3-C01 | BBM-STD-69 V0.2 §2 | Preserve published family/index identities; map any legacy or abbreviated name explicitly to the Manual family naming convention before a curated change; never mass-rename the read-only library or infer a current release from folder/year labels. | Published index metadata and Manual family naming serve different identity controls; index snapshots quoted per |
| W3-C02 | BBM-STD-70 V0.2 §1, §3 | Keep published BBM-DET-section-sequence IDs separate from Manual DET-DISC-CAT-INDEX-DESC view aliases; retain published index bytes; verify ambiguous indexed scale tokens (such as 1:0) against the native view/viewport and print before reuse; never silently repair the share. | Read-only library metadata cannot establish native scale, licensing or technical acceptance |
| W3-C03 | BBM-STD-68 V0.3 §3 | Preserve both byte-identical published QA templates until the QA owner and document controller nominate one; join supplemental evidence by source hash/sheet/row/ITEM. Legacy average-score A/B/C/D labels are diagnostic only and never gate A/B/C, suitability, NC codes or release; mandatory failures cannot be averaged away. | Read-only formula inspection shows different code semantics |
| D13 | BBM-STD-69 V0.2 §4 | The family parameter cleaning rule (formerly D13) is registered as and lives once in BBM-STD-69 §4. | See |
Document coverage#
One row per document at its current name. Column 2 lists the decision IDs cited in the document's own text; column 3 lists the settled decisions –169 that change it. Regenerate after every set revision.
| Document | O-DEC IDs cited in the current text | Settled decisions affecting it (–169) |
|---|---|---|
| BBM-STD-00-GLOSSARY-V0.3.md | ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, | ,,,,,,,,, |
| BBM-STD-01-MANUAL-V0.6.md | ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, | ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, |
| BBM-STD-02-OIR-V0.3.md | ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, | ,, |
| BBM-STD-03-DIRECTORY-V0.3.md | ,,,,,,,,,,,,,,,,,,,,,, | ,, |
| BBM-STD-10-BEP-V0.5.md | ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, | ,,,,,,,,,,,,,,,, |
| BBM-STD-11-DECISIONS-LOG-V0.4.md | All (this log) | ,, –183 |
| BBM-STD-13-ARCHITECT_OF_RECORD_SERVICES-V0.1.md | ,,,,,,, | ,,,,,,, |
| BBM-STD-12-BASIS_OF_DESIGN_REPORT-V0.2.md | ,,,,,,,,,,,,,,, | ,,,,,,,,, |
| BBM-STD-50-CLASH_MATRIX-V0.4.md | ,,,,,,,,,, | ,,,,,,,,, |
| BBM-STD-51-REGISTERS-V0.3.md | ,,,,,,,,,,,,,,,,,,,,, | ,,,,,,,,,,,,,,,, |
| BBM-STD-52-AIR-V0.2.md | ,, | |
| BBM-STD-53-PIR-V0.2.md | No office decision cited | |
| BBM-STD-54-EIR_AND_LOIN-V0.2.md | ,,, | ,, |
| BBM-STD-55-RESPONSIBILITIES-V0.2.md | , | ,, |
| BBM-STD-56-INFORMATION_PROTOCOL-V0.2.md | No office decision cited | , |
| BBM-STD-57-CODES_AND_SUBMISSIONS-V0.2.md | ,,,,,, | ,,,,,,, |
| BBM-STD-58-ARCHITECTURAL_MODELLING-V0.2.md | , | , |
| BBM-STD-59-STRUCTURAL_MODELLING-V0.2.md | ||
| BBM-STD-60-MEP_MODELLING-V0.2.md | ||
| BBM-STD-61-LANDSCAPE_MODELLING-V0.2.md | No office decision cited | |
| BBM-STD-62-INTERIORS_MODELLING-V0.2.md | No office decision cited | |
| BBM-STD-63-SURVEY_AND_CIVIL-V0.2.md | ,, | , |
| BBM-STD-64-FEDERATION-V0.2.md | ,,, | ,, |
| BBM-STD-65-TEMPLATES_AND_RELEASE-V0.2.md | ,,,,,,,,, | ,,,,,,,,, |
| BBM-STD-66-CAD_STANDARD-V0.3.md | ,,,,,, | ,,,,,,,, |
| BBM-STD-67-DRAWINGS_AND_SHEETS-V0.2.md | ,,,, | ,,,,, |
| BBM-STD-68-QUALITY_PLAN-V0.4.md | ,,,,,,,,,,,, | ,,,,,,,,,,,, |
| BBM-STD-69-FAMILY_STANDARD-V0.2.md | ,,,,, | ,,,,,,,, |
| BBM-STD-70-DETAIL_LIBRARY-V0.2.md | ,,,,,,, | ,,,,, |
| BBM-STD-71-MATERIALS-V0.2.md | , | ,, |
| BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2.md | ,,,,,, | ,,,,,,, |
| BBM-STD-73-AUTOMATION_AND_AI-V0.2.md | , | , |
| BBM-STD-74-OPENBIM_PROFILES-V0.2.md | , | |
| BBM-STD-75-HANDOVER_AND_AIM-V0.2.md | ,, | |
| BBM-STD-76-RECORDS_AND_RECOVERY-V0.2.md | , | |
| BBM-STD-77-POINT_CLOUD_AND_SCAN-V0.2.md | ||
| BBM-STD-78-QUANTITIES_AND_5D-V0.2.md | No office decision cited | |
| BBM-STD-79-FOUR_D_PLANNING-V0.2.md | No office decision cited | |
| BBM-STD-80-VISUALISATION-V0.2.md | ,, | |
| BBM-STD-81-ANALYSIS_AND_SUSTAINABILITY-V0.2.md | No office decision cited | |
| BBM-STD-82-TRAINING_AND_ASSESSMENT-V0.2.md | , | |
| BBM-STD-83-METRICS_AND_BENEFITS-V0.2.md | No office decision cited | |
| BBM-STD-MIDP-V0.3.md | ,, | ,, |
| BBM-STD-TIDP-V0.3.md | ,, | ,, |
| BBM-STD-85-UAE_AUTHORITY_SUBMISSIONS-V0.2.md | ,,,,,,,,,,,, | ,,,,,,,,, |
| BBM-STD-86-COORDINATES_AND_GEOREFERENCING-V0.2.md | ,,,,,,, | ,,,, |
| BBM-STD-87-SECURITY_MANAGEMENT-V0.1.md | , | |
| BBM-STD-88-HEALTH_AND_SAFETY_INFORMATION-V0.1.md | , | None |
| BBM-STD-89-LOIN_TO_IDS-V0.1.md | ,,,,,,,, | None |
| BBM-STD-90-RECORDS_RETENTION_AND_PERSONAL_DATA-V0.1.md | No office decision cited | |
| BBM-STD-91-SOFTWARE_SUPPORTED_RELEASES-V0.1.md | ,, | ,,, |
| BBM-STD-92-AI_GOVERNANCE-V0.1.md | No office decision cited | None |
| BBM-STD-93-CODE_DICTIONARY-V0.2.md | ,,,,,,,,,,,,,,, | ,,,,,,,,,,,,, |
| BBM-STD-94-LICENCE_REGISTER-V0.1.md | No office decision cited | None |
| BBM-STD-95-OFFICE_DESIGN_SYSTEM-V0.1.md | ||
| BBM-STD-96-QUALITY_MANAGEMENT_SYSTEM-V0.1.md | ,,, | ,, |
| BBM-STD-97-QUALITY_PROCEDURES-V0.2.md | ,,,,, | ,,, |
| BBM-STD-98-QUALITY_KPIS-V0.1.md | , | |
| BBM-STD-99-PROJECT_TRACKERS-V0.1.md | ,,,,,,,,, | ,,,,,,,,, |
Baseline and implementation evidence#
- Naming/revision/suitability/states use the O3 grammar and one project code register; issued identities are preserved.
- Only Clash matrix section 3 H/C/A/D/V is the tolerance table. Stage 5 15/5 mm and blanket 150/500/10 mm limits are retired.
- defines mandatory acceptance; optional 95% is progress only.
- uses weekly/change/comment-round/pre-exchange runs and S1/S2/S3 severity with existing response deadlines.
- –007 preserve L1 2, L2 2, rework 2, L3 1, release 1, acceptance 3 working days, normally sequential; task-team TIDP and LAP MIDP changes share ChangeID.
- Office defaults are decided on 2026-10-14. No live test pass, installed build, role acceptance or project contractual approval is claimed.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-14 | 101 office decisions (–101), including seven prior O3 decisions |
| V0.2 | 2026-11-04 | Closes rows: every row re-mapped to the current documents and headings (original line numbers dropped); research links fixed to../../RESEARCH.md; /086/090/092/094 extended (authority profile, Dubai/Abu Dhabi CRS, Uniclass July 2026, Revit support); sub-ID aligned with OIR V0.3; settled decisions –141 added (122–141 from the batch proposals); marked superseded by; drafting-lane conflict records W1-C01, W3-C01–C03 and D13 anchored; document coverage table for all 43 documents and BBM-STD-85–94 replaces the source-line table + template alignment (..148) + folder names without dots + QMS patch |
| V0.3 | 2026-11-05 | Settles the 21 values the documents did not state (standard rule tables archhub-claude-dat-tab-011, README gaps) and records them as –169: Dubai circular 9-1-1 thresholds, Dubai BIM Standard 1.4 / IFC4 / Appendix B, AR 225/2024 parameters, Law 3/2026 gazette, Dubai and Abu Dhabi CRS, transformation and vertical codes, control-point tolerance, rule-based authority rows, register rows ISO 10002 / Abu Dhabi planning / utility regulations, container token lists, QMS workbook codes, warnings gate and blocking list, check attributes, pass-criteria tolerances, the full 91-pair clash matrix and its owners; coverage table updated |
| V0.4 | 2026-11-05 | –183: the Architect of Record services standard BBM-STD-13 and the project tracker standard BBM-STD-99 (numbers, AOR definition, review-before-stamp, comment levels 0–4, construction review codes A–E, one row per revision, turnaround defaults, record IDs and file names, one tracker set, evidence rule, data date, the 13th tracker, service models) and the legal basis update in BBM-STD-97 V0.2 (AR 275/2024, Dubai Law 14/2025, FDL 25/2025 Art. 821); coverage table rows for BBM-STD-13, BBM-STD-97 V0.2 and BBM-STD-99 |
| V0.5 | 2026-11-05 | Standard watch no. 1, appended after: ISO 19011:2026; DM circular 11-9-1 of 2026 and the office's Building Quality and Safety Certificate assessment service; ED-SIRA settled on the SIRA Preventive Systems Manual (replaces the ED-SIRA part of) |
| V0.6 | 2026-11-05 | : the BBM-STD-66 layer mapping rules (name, content, MasterFormat division; no Hold), the colour/linetype/lineweight rules beyond the starter catalogue and the 204-layer detail library set (BBM-STD-66 V0.3 §1.2–§1.4); coverage row for BBM-STD-66 V0.3 |
| V0.7 | 2026-11-05 | : one office Revit template for all disciplines, BBM-GEN-TMP-R23-REV04 (founder 2026-11-05); discipline templates retired; no loadable model families or details in the template (BBM-STD-65 V0.3) |
Authority: BIM Manager, 2026-10-14, under the founder's instruction. Existing O3 decisions are preserved as –007. Repeated questions use one canonical ID and value. –141 were settled on 2026-11-04 to close the contradictions found by; –148 settle the standard-versus-template conflicts found in the office template on the same date; records the founder's folder-name decision of the same date; –152 record the QMS patch (BBM-STD-96–98) of the same date. –169 were settled on 2026-11-05 to close the 21 values the documents did not state, each from a primary source read that day or as a stated office choice. –183 were settled on 2026-11-05 with BBM-STD-13 and BBM-STD-99, from the office practice survey and primary sources of that day.
Office defaults are decided here; actual appointments, signed rights, recipient approvals, installed configurations and successful tests remain activation gates. Sources support the basis; frequencies, percentages, pilots and negotiating defaults are local choices, not universal ISO requirements. Binding appointment/authority requirements govern through one controlled mapping.
Applies to: Glossary V0.3, Manual V0.5, OIR V0.3, Directory V0.3, BEP V0.5, BoD V0.2, Clash Matrix V0.3, MIDP V0.3, TIDP V0.3, BBM-STD-51–83 V0.2 (BBM-STD-68 V0.3) and the new documents BBM-STD-85–98 V0.1.
Coverage: 186 decisions (–101 from V0.1, –152 settled 2026-11-04, –183 settled 2026-11-05, of which –148 are the template alignment, is the founder's folder-name rule and –152 are the QMS patch) across all 43 current documents, the 10 new documents BBM-STD-85–94, BBM-STD-95 and the QMS documents BBM-STD-96–98. 45 of the other 56 current documents cite an O-DEC ID in their text; every document is listed in the coverage table below with the decisions that touch it, or "No office decision cited". The document and section columns are generated from the current text of each document (heading in which the ID is cited); "not cited by ID" marks a decision that still applies but whose ID no longer appears in that document's text.
| id | document | section | decision | basis | source tag |
|---|---|---|---|---|---|
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-12 V0.2 | BBM-STD-00 V0.3 §7.1, §9.3, §9.4; BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §8.12; BBM-STD-12 V0.2 Existing office authority and… | Retire all blanket RIBA-stage tolerances, including the conflicting Stage 5 15 mm and 5 mm settings; apply the single test-type table in section 3 at every stage. | Purpose, pair, zone and clearance evidence determine the test; stage and LOD do not determine an allowable intersection. | S07 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §9.4; BBM-STD-01 V0.5 §3.1, §12.3, §14; BBM-STD-10 V0.5 §8.3.1 | Use CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext when an appointment supplies no grammar; retain internal Rnn revisions and the suitability list below. | Adopts the Manual/BEP external candidate and existing Rnn convention consistently; appointment requirements take precedence through one recorded mapping. | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-10 V0.5, BBM-STD-12 V0.2 | BBM-STD-00 V0.3 §1.5, §9.4; BBM-STD-01 V0.5 §3.2, §14; BBM-STD-02 V0.3 §5.2, §7; BBM-STD-10 V0.5 §6.5, §8.12, D. DATA INTEGRITY; BBM-STD-12 V0.2 Control, purpose and method | Require 100% valid applicable mandatory geometry, data and documentation and zero unresolved required hard-intersection or mandatory access/safety failures in the issued scope. | An issue count or optional-data percentage cannot average away a mandatory exchange failure. | S04 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §8.12 | Run weekly, every coordination comment round, on affected source/rule changes and before exchange; use Manual severity S1 Critical, S2 Major, S3 Minor. | Retains the office issue-management service levels and adds revision-specific evidence and independent retest. | S04 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §6.3, §6.4, §10.1 | Reserve L1 discipline QC 2 working days, L2 cross-discipline review 2 working days, correction/retest contingency 2 working days, L3 technical committee 1 working day, authorisation/release 1 working day and appointing-party acceptance 3 working days per normal exchange package. | A visible allowance protects checks and exchange decisions; these are office planning minima and must increase for complexity or binding recipient terms. | S04 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §9.1; BBM-STD-10 V0.5 §6.3 | Use unique stable ExchangeIDs allocated from the approved project exchange register; separate RIBA Stage 2 Concept Design and Stage 3 Spatial Coordination unless an appointment explicitly groups their outcomes. | Duplicate #01 and numbering gaps cannot establish the intended historic mapping; distinct decisions and dates must remain traceable. | G-F | |
| BBM-STD-00 V0.3, BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §2.2, §2.3, §3.2; BBM-STD-03 V0.3 §6, Decision register; BBM-STD-10 V0.5 §6.3, §6.4 | The task-team lead owns the TIDP commitment; the LAP owns the coordinated MIDP baseline; every approved delivery-row change must propagate by the same ChangeID before the affected new commitment takes effect. | Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence. | G-F | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-03 V0.3 | BBM-STD-00 V0.3 Revision history, ownership and…, §2.4, §9.4; BBM-STD-01 V0.5 §2.2, §13; BBM-STD-03 V0.3 §6, Decision register | The BIM Manager is the office information standards owner and glossary custodian, supported by discipline, CDE, security and asset-information contributors; record a distinct deputy and actual holder in the private Directory before activation. | One standards function avoids competing terminology owners; actual staffing and delegation require evidence. | G-A | |
| BBM-STD-01 V0.5, BBM-STD-03 V0.3 | BBM-STD-01 V0.5 §1.1, §9.1, §14; BBM-STD-03 V0.3 §6, Decision register | The BIM Manager owns the Manual and its maintenance; appoint a distinct deputy with capacity and record actual role holders in the private Directory before activation. | Policy maintenance needs accountable ownership and resources. | G-A | |
| BBM-STD-02 V0.3, BBM-STD-03 V0.3 | BBM-STD-02 V0.3 Revision history and control, §7; BBM-STD-03 V0.3 §6, Decision register | The BIM Manager acts as office information management lead and owns the OIR document; each business function owns its applicable requirement and authorised business decision. | Document maintenance and business authority are distinct functions. | G-A, G-D | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 Summary and document control, Decision register | Assign Ahmed Fargaly, in the office BIM/information management function, as accountable Directory owner; the director records role acceptance, capacity and a distinct deputy before activation. | Retains the existing author-based choice without inventing a deputy or operational appointment evidence. | G-A | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-03 V0.3 | BBM-STD-00 V0.3 Revision history, ownership and…; BBM-STD-01 V0.5 §1.1, §2.2, Locking and governance, §12.1, §14; BBM-STD-02 V0.3 Revision history and control; BBM-STD-03 V0.3 Summary and document control, §6, Decision register | The office director approves office standards and business requirements after relevant QMS, security, safety and business-owner reviews; project departures require the actual appointment authority and recorded scope/date. | Office governance does not transfer contractual or statutory powers. | G-A, G-E | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-03 V0.3 | BBM-STD-00 V0.3 Revision history, ownership and…; BBM-STD-01 V0.5 §1.1; BBM-STD-02 V0.3 Revision history and control, §7; BBM-STD-03 V0.3 Summary and document control, Decision register | Keep controlled masters in the restricted office standards CDE with document ID, revision, approval and exact URI; distribute read-only approved office views and retain superseded editions without overwriting issued project baselines. | Controlled identity, access and history must survive publication and change. | G-C, S05 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 Revision history and control, §7 | Give office users role-based approved views and external recipients only sensitivity-reviewed appointment-relevant extracts; authorise and audit access and export separately. | Distribution follows purpose and sensitivity. | S05, P06 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3 | BBM-STD-00 V0.3 Revision history, ownership and…, §9.4; BBM-STD-01 V0.5 §1.1, §14; BBM-STD-02 V0.3 Revision history and control | Adopt office policy choices on 2026-10-14; review controlled standards every 12 months and at material standard, appointment, requirement, tool, authority, incident or ambiguity change; record actual implementation approval and first-use date separately. | A policy review cadence does not prove that live records or tools are ready. | P04 | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 Revision history, ownership and…, §9.4 | Record stable ChangeID, old/new meaning or value, reason/source, affected documents/appointments, approver, effective revision/date, alias impact, notifications and required retest; retain the prior baseline. | Controlled changes prevent inconsistent dependent records. | G-C, P04 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5, BBM-STD-89 V0.1 | BBM-STD-00 V0.3 §1.3, §7.1, §9.4; BBM-STD-10 V0.5 §3.2.1; BBM-STD-89 V0.1 §2 | Adopt purpose-led worksheets recording purpose, timing, producers/receivers, objects, geometry, alphanumeric information, documentation and measurable checks; keep synthetic examples as templates and populate actual requirements before exchange. | ISO 7817-1:2024 distinguishes information need from bare LOD/stage labels. | S07 | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §1.4 | Adopt the equipment-maintainability training exchange: describe actors/timing, validate IFC data with audited IDS 1.0 where supported, check geometry/access separately, and retain BCF issue, corrected revision, independent retest and receiving decision. | Data conformance alone cannot demonstrate access or acceptance. | S18, S20, S04 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5 | BBM-STD-00 V0.3 §1.5, §1.7; BBM-STD-01 V0.5 §12.4, §14 | Use WIP / Shared / Published / Archive as logical CDE states; the Published state folder is 03-PUBLISHED (the earlier platform folder alias is superseded by); keep revision, suitability, permitted use and acceptance as separate metadata. | Logical workflow maps to platform labels without changing issued identity or reliance. | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.5, §1.7, §9.4; BBM-STD-01 V0.5 This section defines decision…; BBM-STD-10 V0.5 §5.2.4 | Use A = accepted for stated purpose without required changes, B = accepted for stated purpose with listed nonblocking comments, owners and dates, C = rejected/revise and resubmit with affected use held; record scope, actual acceptor, authority, evidence and permitted use; B cannot cover mandatory failure. | Local gate letters differ from RACI and suitability and cannot waive binding criteria. | S04 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.5; BBM-STD-01 V0.5 §3.1, §14; BBM-STD-10 V0.5 §8.3.1 | Use R00 for initial WIP, then R01, R02 and never-recycled per-container revisions, expanding digits beyond R99; unchanged containers retain their actual revision; appointment codes override through one approved mapping. | Carries forward O3 Rnn without forcing equal revisions on unchanged content. | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.5; BBM-STD-01 V0.5 §3.1, §3.1.1, §14; BBM-STD-10 V0.5 §8.3.1 | Use local SU-WIP = team work, SU-COORD = coordination, SU-INFO = reference, SU-REVIEW = formal review, SU-ISSUE = authorised defined use; record permitted use and recipient acceptance separately; map appointment codes in one register. | The O3 list prevents confusion with S1/S2/S3 severity and RACI. | G-C, S04 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §9.4; BBM-STD-01 V0.5 §3.1, Acceptance for 3.1, §12.3; BBM-STD-10 V0.5 §8.3.1 | Retain ORG-PROJ-DISC-PHASE-SEQUENCE only for approved legacy internal WIP aliases with one external identity mapping; retire PHASE from external identity and keep purpose/status as metadata; preserve historic issued names. Superseded for issued names by: the alias is internal WIP only and never issued. | One external identity prevents parallel grammars and IFC format/purpose ambiguity. | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7; BBM-STD-01 V0.5 §3.1; BBM-STD-10 V0.5 §8.3.1, §8.4.1, §8.8, References | Use DISC-LEVEL[-ZONE]-TYPE-DESC for views and DISC-CAT-INDEX for sheet numbers, with separate readable title and revision; register Start View/library exceptions and validate codes. | Retains the shared Manual/BEP convention while separating display from identity. | S35, G-C | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §8.3.1 | The project IM maintains one naming/code register, approved by LAP/recipient within appointment powers; validate eight uppercase hyphen-separated tokens, registered volume/level/type/role, four-digit NUMBER and lowercase approved extension; use ISO 8601 dates. | Syntax, dictionaries, uniqueness and permitted use must agree across documents. | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §4.1, §4.2, §9.4; BBM-STD-01 V0.5 §3.2, Core parameter set (defaults); BBM-STD-02 V0.3 §5.1; BBM-STD-10 V0.5 §8.6, §8.6.1 | Use canonical Asset_ID as stable text occurrence identifier for applicable maintainable assets; map AssetID, Asset ID, Asset Tag and AssetTag aliases, retaining distinct physical/finance tags where needed; preserve GUIDs and receiver mappings. | Stable semantic identity matters more than display aliases or blind renaming. | S16, S17 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §9.4; BBM-STD-01 V0.5 §3.2, Core parameter set (defaults); BBM-STD-10 V0.5 §1.11, §8.6 | Use canonical Classification_Code with separate ClassificationTable, ClassificationTitle and ClassificationRelease; map ClassificationCode and legacy labels; use type binding only when valid for the entire type and verify IFC classification-reference mapping. | Definition, binding and classification version require one dictionary. | S16, S09 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §9.4; BBM-STD-10 V0.5 §8.6, §8.6.1 | Use canonical Expected_Life_Years as numeric duration in years with source/assumptions; map ExpectedLife and legacy text only after validation; unknown is not zero and no lifespan is invented. | Typed units and provenance prevent misleading conversions. | S16, S17 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §8.6 | Use canonical Fire_Rating with approved units/definition and certification evidence; map FireRating/Fire Rating and bind type/instance from certification scope; verify native/IFC export. | Nonempty text does not establish certified performance. | S16, S06 | |
| BBM-STD-00 V0.3, BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §1.7, §9.4; BBM-STD-03 V0.3 §2, Decision register; BBM-STD-10 V0.5 §8.6, §8.6.1 | Use ISO 8601 dates (YYYY-MM-DD), access timestamps with UTC offset, and explicit units/source for service intervals; validate chronology and receiver mappings with actual calendars/time zones. | Unambiguous dates/units support traceable schedules and exchanges. | S16, G-F | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §2.1, §2.4, §3.3, §9.4 | Prefer full terms appointing party, lead appointed party and appointed party; retain APOP/LAPP/APP as documented legacy aliases only; verify appointment, IM functions, primary/deputy contacts, delegation and escalation before baseline. | A title, RACI or Directory listing does not establish authority. | S01, G-A | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §2.2, §2.3, §3.2 | Release only after scoped information need, current inputs, metadata, QA and permitted exceptions pass; LAP retains coordinated plan/interface and release evidence; receiver acceptance stays separate; critical unresolved interfaces hold the affected exchange. | Production, authorisation and acceptance are distinct evidenced actions. | S02, S04 | |
| BBM-STD-00 V0.3, BBM-STD-02 V0.3 | BBM-STD-00 V0.3 §2.1, §3.1, §3.3; BBM-STD-02 V0.3 §7 | Every exchange needs current EIR, verified recipient/actual acceptor, decision deadline and recorded accepted/rejected scope; verify powers through appointment and private Directory. | Exchange decisions require defined requirements and empowered recipients. | S04, G-E | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §4.1, §4.2 | For scoped maintainable assets record Asset_ID, SystemID/SpaceID links, classification, required manufacturer/model/performance, source/verification date, condition, warranty/service and O&M links; collect progressively and review substitutions into the AIM without invented values. | AIR and operational decisions determine asset obligations. | S03, S07 | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §4.2 | Record stable SpaceID, name/function, level/zone, geometry/source revision, adopted measurement basis/units, capacity/use and links; preserve split/merge/retirement aliases and aggregate occupancy where sufficient. | Space decisions need consistent identity/measurement and proportionate privacy. | S03, S05 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §7.1; BBM-STD-10 V0.5 §1.10, §3.2.1 | Adopt Glossary sections 5–8 procedures/gates as a purpose-led menu; start project selection with Design Authoring, Design Review, 3D Coordination and required Asset Management; add 4D/5D/carbon/VR only for an evidenced decision, resources and receiving criteria. | BIM uses serve outcomes rather than software availability or universal deliverables. | P01, S07 | |
| BBM-STD-00 V0.3, BBM-STD-02 V0.3 | BBM-STD-00 V0.3 §8.2; BBM-STD-02 V0.3 §4.2 | Review safety-critical overdue maintenance/defects before affected operation; assign owner, action date and competent disposition rather than masking them in portfolio percentages. | Safety information must serve the affected activity and duty holder. | S06, S03 | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §8.6, §9.4 | Exercise disaster-information availability/recovery annually and after material system/role changes; test authorised outage/offline access and deputies, record findings/retest, and exclude sensitive details from broad Directory views. | Operational resilience needs testing without wider sensitive distribution. | S03, S05 | |
| BBM-STD-00 V0.3 | BBM-STD-00 V0.3 §9.1 | Adopt section 9.1 many-to-many TBP-phase/RIBA-context map for learning/navigation; actual project outcomes remain distinct, including separate Stage 2 Concept Design and Stage 3 Spatial Coordination unless explicitly grouped by appointment. | Manual phases do not establish stage tolerances, LOD or dates. | S21, G-F | |
| BBM-STD-00 V0.3, BBM-STD-02 V0.3 | BBM-STD-00 V0.3 §9.2, §9.4; BBM-STD-02 V0.3 §4.1 | Keep jurisdiction authority, building/fire code, rating and submission particulars in appointment annexes verified from current official sources for the actual UAE jurisdiction/project; core abbreviations and historic lists do not prove compliance. Edition and adoption are recorded once in the BBM-STD-51 §3 register; UAE authority and submission detail is in BBM-STD-85. | RESEARCH.md distinguishes local applicability and evidence limits. | S26, S27, S28, S29 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §3.2, §14; BBM-STD-10 V0.5 §6.5, D. DATA INTEGRITY | Use 95% valid applicable non-mandatory values as informational progress only; define numerator, denominator, scope and cut-off and report missing/invalid/excluded/not-applicable separately; all applicable mandatory geometry/data/documentation must pass before release. | O3 acceptance forbids averaging away mandatory failures. | S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §3.3, Workset templates (per discipline)…, §14; BBM-STD-10 V0.5 §8.7 | Use only required user worksets: Shared Levels and Grids, Core Modeling, Links by loading group and Imports where needed, with owners/valid exceptions; system/browser documentation groups are not user worksets or security locks. Re-affirmed by. | Retains the shared minimal policy and actual worksharing semantics. | A02 | |
| BBM-STD-01 V0.5 | BBM-STD-01 V0.5 §9.1.1, §14 | Review QMS performance quarterly and at material incident using actual controlled procedure IDs and evidence for overdue actions, rejected exchanges, recurring defects, security incidents and correction effectiveness. | Management review tests effectiveness rather than attendance. | P04 | |
| BBM-STD-01 V0.5 | BBM-STD-01 V0.5 §9.3, §14 | Independently review min(total sheets, max(10, ceiling(10% of total sheets))) per discipline plus every safety-critical/changed high-risk item; mandatory-field checks cover the full applicable scope. | Risk-based visual sampling supplements complete mandatory validation. | P04, S04 | |
| BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §2.2, §9.4, §14; BBM-STD-02 V0.3 Revision history and control; BBM-STD-10 V0.5 §1.13, §10.4 | Assign office Security Lead with project IT/data owners to sensitivity, access, suppliers, distribution, retention and incidents; record actual competent holders/delegation before access. | Security governance continues through operation and disposal. | S05, P06 | |
| BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §2.2, §9.4, §14; BBM-STD-02 V0.3 Revision history and control; BBM-STD-10 V0.5 §1.13, §10.4 | Assign competent Design Safety Lead during delivery and appointed asset/operator safety owner at handover; record hazards/objects/locations, source revision, controls, reviewer, residual owner and receiving acknowledgment. | Structured safety information does not transfer designer/duty-holder duties. | S06 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §9.4; BBM-STD-10 V0.5 §10.4 | Use 1–5 likelihood × 1–5 impact for information-delivery risk; scores 15–25 require escalation and competent residual-risk disposition before affected release; any unresolved mandatory failure blocks release regardless of score; specialist design/safety methods remain separate. | The office scale defines escalation without replacing specialist assessment. | P04, S06 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §9.4; BBM-STD-01 V0.5 §11.3, §14; BBM-STD-02 V0.3 §7; BBM-STD-03 V0.3 §6, Decision register; BBM-STD-10 V0.5 §7.4, §8.10 | Freeze authoring/exporter/checker/receiver full builds, presets, dictionaries and profile hashes; upgrades require impact, compatibility, receiver and recovery tests with controlled change approval. | Infrastructure qualifies for a purpose through actual capability evidence. | P02, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3; BBM-STD-10 V0.5 §6.1.1, §10.3 | Require isolated representative mobilisation pack: native seed, known-value IFC/data/documents, valid/invalid fixtures, coordinates, allowed/denied access, BCF round trip, correction/retest log and restored backup; project tests stay NOT EXECUTED until evidenced. | Specified test design and workshop screenshots do not prove live exchange success. | P02, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §12.5, §14; BBM-STD-10 V0.5 §7.3.1 | The appointed operational owner reviews AIM after inspection, failure, substitution, replacement, use/system/access change, incident or disposal and annually for unchanged records; office performs only appointed updates. | ISO 19650-3:2020 centres operational trigger events. | S03 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §2.1, §7 | Adopt the objective: make timely, traceable decisions using minimum sufficient checked information; use OBJ-01 safety, OBJ-02 environment, OBJ-03 investment/resources, OBJ-04 lawful dependable operation and OBJ-05 space/capacity only where scope applies. | OIR support authorised business decisions, not invented corporate mission claims. | G-D, S01 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §2.3, §7 | Use stable OIR-nnn, AIR-nnn, PIR-nnn and EIR-nnn IDs with separate revision, derivation links and preserved issued aliases; these are requirement keys, not filename tokens. | Requirement lineage must survive change and appointment conventions. | G-D | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §3, §7 | Adopt OIR-001–010 with sections 3–4 owner/consumer functions, triggers and acceptance rules wherever applicable; expand into section 2.3 records and approve explicit not-applicable scope; actual holders/source systems remain activation particulars. | Decision records derive relevant AIR/PIR/EIR without invented portfolio facts. | G-D, S03 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §3.1 | Adopt OIR-001: safety lead supplies significant-risk records before affected work/change and in monthly exceptions; every significant unresolved risk has owner/disposition and no safety-critical record is missing. | Safety information serves affected decisions/activities. | S06 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §3.2 | Adopt OIR-002: environmental data owner reports energy/water/waste monthly and at meter/occupancy/boundary change; reconcile each included site to source evidence and identify missing periods/estimates. | Comparable measures need units, boundaries and provenance. | G-D, S04 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §3.3 | Adopt OIR-003: sustainability lead reports at option selection/substitution and quarterly portfolio review; link quantities/model revision, assessment boundary/stages, dataset/EPD version and exclusions to the adopted methodology. | Quantity extraction alone is not an environmental assessment. | V04, V06 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §3.4 | Adopt OIR-004 before funding, quarterly forecast and material scope/cost change with ledger reconciliation/no double-counted benefits; adopt OIR-005 monthly and before new appointments with actual capacity, plan revisions and scoped metrics. | Investment/capacity need comparable baselines and full cost/resource evidence. | P03, G-D | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §4.1 | Adopt OIR-006: compliance lead verifies approvals/conditions/expiry before submission/use, at monthly expiry review and changed rules; overdue/unverified mandatory approvals hold affected decisions. | Authority annex applicability and verified status establish readiness. | S28, G-D | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §4.2 | Adopt OIR-007: maintenance data owner reports monthly backlog and inspection/failure/replacement/handover events; require unique Asset_ID, system/location links and safety-critical action owner/date. | Operational information supports prioritisation at trigger events. | S03, S06 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §4.3 | Adopt OIR-008: operations data owner reports incident/change events and monthly service review, linking incidents to affected services/assets/current documents and reconciling source counts. | Operational records remain traceable to current affected services. | S03 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §4.4 | Adopt OIR-009: space data owner reports quarterly and at use/reconfiguration change; reconcile SpaceID, measurement/model revision, report uncertainty and aggregate occupancy. | Space/capacity needs comparable measures and minimal personal data. | S03, S05 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §4.5 | Adopt OIR-010: portfolio change owner supplies options/cost/risk and affected asset/space evidence before approval/handover and after verified completion; distinguish assumed/surveyed/designed/installed/verified information and update AIM. | Changed assets/services need reviewed operational information and provenance. | S03, G-D | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §5.1 | Adopt synthetic OIR-007/AIR-007/PIR-007/EIR-007-A/-D maintenance trace as office example; pilot a structured UTF-8 table with controlled document links and confirm actual receiver schema/build and known-record reconciliation before activation. | An adopted example does not assert live holdings or successful ingestion. | G-D, S04 | |
| BBM-STD-00 V0.3, BBM-STD-02 V0.3 | BBM-STD-00 V0.3 §1.5; BBM-STD-02 V0.3 §5.2, §7 | Apply OIR section 5.2: 100% required scope accounted for, every mandatory value valid, zero duplicate IDs, required references/codes valid, units/method/source stated, critical results traced and receiver use/permissions demonstrated; accuracy is purpose-specific. | O3 mandatory acceptance covers geometry, data and documentation. | S04 | |
| BBM-STD-02 V0.3 | BBM-STD-02 V0.3 §5.3, §6, §7 | Issue monthly requirement-by-requirement exceptions within 5 working days of cut-off and before the supported decision; review usefulness/benefits quarterly and full OIR annually; urgent triggers follow the earlier decision deadline. | Explicit timeliness/review prevents averages hiding critical exceptions. | G-D, S04 | |
| BBM-STD-02 V0.3, BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-02 V0.3 §6, §7; BBM-STD-03 V0.3 §1, Decision register; BBM-STD-10 V0.5 §1.8 | Use records/legal-owner-approved retention by record class and actual legal/contract duties; apply legal holds, preserve approvals/accepted evidence and revoke redundant access; no universal deletion period, and missing schedules hold affected activation. | Security/protocol guidance supports proportionate records control, not invented jurisdiction-wide periods. | S05, S37 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 Summary and document control, §3.2, Decision register | Review active Directory memberships monthly and at joiner/mover/leaver, deputy/expiry, incident or appointment change; sponsors verify roles/channels and CDE administrators reconcile actual memberships/exports. | Current routing/access requires evidence beyond stale titles. | S05, G-A | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 Objectives, Decision register | Adopt DIR-OBJ-01–04: 100% active exchanges have primary/deputy/escalation, 100% memberships have approved/tested access, zero known leavers retain access after termination, and critical tasks have capability/capacity evidence or hold. | Routing, access and competence are mobilisation gates, not historical completion claims. | S05, G-E | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 Summary and document control, §1, Decision register | Use Restricted identity master, Appointment contact view and Role-only office view with section 1 minimum fields/audiences; authorise exports separately and exclude private channels, unrelated memberships and assessment details. | Audience-specific views minimise aggregated relationship/personal exposure. | S05, P06 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §1, Decision register | Expire Directory exports after 30 calendar days or earlier relevant appointment/role/access change; replace affected extracts promptly and use approved retention for removal. | Export freshness and retention are separate controls. | S05 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §2, §5, Decision register | Use stable ORG-nnn, APT-nnn, TEAM-nnn, PER-nnn, MEM-nnn, EX-nnn and ACC-nnn linked keys; preserve system aliases and one person identity across memberships; assign permanent ProjectIDs after sponsor verification. | Linked identities separate organisation, appointment, role and access. | G-A, G-F | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 Access and authorised-channel template…, Decision register | Use CDE for formal submission/authorisation/acceptance, approved issue platform for coordination, and verified role channels for urgent notice recorded back in CDE; appointment alternatives require mapping. | Notification/sync/browser Publish do not establish acceptance. | G-C, S04 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §3.3, Decision register | Revoke at agreed departure/role-end timestamp and immediately on authorised urgent suspension; verify revocation and update Directory/views within one working day; transfer planned custody first, urgent security action takes priority. | Access changes require timely verified completion. | S05 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §3.4, Decision register | Escalate routine queries primary to deputy after one working day without acknowledgment, then task-team manager/delivery IM after one further day; immediately escalate for deadline/risk and apply stricter appointment windows. | Routing respects actual authority, calendars and deadlines. | G-A, S04 | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §2, §4, §5, Decision register | Quarantine 20 contacts as SRC-P01–SRC-P20 and 3 source project rows pending sponsor verification; allocate permanent identity/appointment keys from trusted evidence only and correct SRC-P20 privately without guessing. | Historic labels/status do not prove active identity, access or delegation. | S05, G-A | |
| BBM-STD-03 V0.3 | BBM-STD-03 V0.3 §6, Decision register | Reserve 2 hours/week for assigned training where capacity permits and task-team approval is recorded; competence/training owner and technical assessor require inspectable outcomes for critical-role activation or approved supervised remediation. | Competence/capacity differ from attendance. | P08, G-E | |
| BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-03 V0.3 §6, Decision register; BBM-STD-10 V0.5 §1.1, §3.4.2, §6.1.1 | LAP owns project BEP, maintained by delegated IM with recorded deputy/project authoriser; review every exchange milestone and material team/tool/requirement change. | Appointment functions determine ownership and authority. | S02, G-E | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §1.2, §1.10 | No blanket omission of cables/wires/conduits/items ≤50 mm needed for safety, coordination, quantities or assets; permitted omissions need scoped requirement, owner, alternative documentation and receiving approval. | Information need is purpose-led, not blanket size/LOD. | S07, S06 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §1.8 | Use non-exclusive project-purpose licence as negotiation baseline; retain background IP, schedule project-created/background/third-party rights and defined lifecycle uses/recipients; contract owner settles duration/transfer/sublicensing/revocation/exclusivity in signed terms before reliance. | Adopts a negotiation position, not rights absent a signed protocol. | S37, S36 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §1.8 | Rely only on authorised accepted revisions for stated scope/use and contract accuracy/limitations; no unrelated project/public/AI reuse is implied; protect distribution, records and appointed operational custody. | Rights/reliance follow signed terms and exchange decisions. | S37, S04 | |
| BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-03 V0.3 §6, Decision register; BBM-STD-10 V0.5 §5.2.2, §9.4 | Select Autodesk Construction Cloud as office default for agreed model/document workflows; qualify actual tenant/modules/permissions/formal transactions; appointment-mandated alternatives/bridges require one authoritative mapping. | Retains office ACC method without assuming configured capability. | A03, G-C | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §6.2, §6.2.1 | Adopt BEP section 6.2 production fields and 6.2.1 RACI as templates with one A/activity; map appointments/people before activation and separate production/check/authorisation/acceptance. | Matrices do not replace plans or transfer statutory duties. | G-F, G-A | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §6.3 | Maintain exact source TIDP ID/row/revision, exchange/EIR/container IDs, parties, dependencies, production dates, separate L1/L2/rework/L3/release/acceptance windows, forecast/actual evidence and ChangeID in MIDP; synchronise all affected TIDPs. | O3 ownership and source-row lineage govern. | G-F | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3; BBM-STD-10 V0.5 §7.3.1, §7.4 | Use COBie v3/XLSX as default qualification profile where AIR/receiver support it; retain appointed earlier version/alternate schema until approved change; freeze template/schema, units, fields, keys, exclusions and receiving tests. Superseded by (COBie version per EIR, default COBie 2.4). | NBIMS-US v4 COBie v3 context does not prove implementation. | S15, S03 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §7.3.1 | Plan asset drops at early construction, approved procurement/installation updates and handover; plans set actual dates/windows/tests with required geometry/data/docs/safety and ongoing custody. | Progressive verified receiving use establishes the AIM contribution. | S03, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4 | Use IFC 4.0.2.1 (IFC4 ADD2 TC1) Reference View as default building reference qualification profile; IFC 4.3.2.0 needs approved purpose and exporter/receiver support; freeze mappings/units/transforms/preset hashes. Authority submissions use the schema the authority states: Dubai DM permits triggered by circulars 9-1-2 (13 Oct 2023) or 9-1-3 (15 Jan 2026, effective 1 Apr 2026) use the IFC schema and export setup in the current Dubai BIM Standard, checked at project start and recorded in the BEP; detail in BBM-STD-85. | Retains Manual/BEP interoperability baseline without automatic upgrades. | S11, S12, P02, DM 9-1-2, DM 9-1-3 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-50 V0.3 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1; BBM-STD-50 V0.3 §1 | Use BCF 3.0 XML as default qualification route; BCF 3.0 API requires separately approved endpoints/permissions and returned-issue test; preserve issue ID/revision/GUID/viewpoint/assignment/status/retest. | XML/API are separate implementations needing endpoint compatibility. | S13 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.2, §11.3, §14; BBM-STD-10 V0.5 §7.4 | Use audited IDS 1.0 where supported for IFC data with rule IDs/hash/checker and valid/invalid fixtures; geometry/access/competent review remain separate. | IDS scope is information validation, not full geometric/safety assurance. | S20, S04 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §8.1, §9.1, §10.3 | Treat 300 MB as performance investigation/splitting trigger only; measure actual hardware/network/workload and preserve IDs, ownership, federation and receiver use when splitting. | Size alone is not exchange acceptance or a universal limit. | P02, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-86 V0.1 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §8.2; BBM-STD-86 V0.1 §5 | Survey/site-control owner approves coordinate evidence, BIM Coordinator implements, independent receiver checks ≥3 well-distributed control points plus elevation/unit probes; record CRS/datum/units/provenance/uncertainty/local-shared transform/True North. Default CRS: Dubai projects use DLTM, EPSG:3997 "WGS 84 / Dubai Local TM", with vertical datum DMD (Dubai Municipality Datum = Port Rashid datum), unless the authority or surveyor states otherwise; Abu Dhabi projects use the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, recorded with EPSG code and transformation, vertical datum Ras Ghumays (EPSG datum 1146). Never hard-code EPSG:32640. Register in BBM-STD-86 and BEP §8.2. | Retains shared coordinate method without asserting zero survey uncertainty. | A10, S04, EPSG:3997, Ras Ghumays | |
| BBM-STD-10 V0.5, BBM-STD-64 V0.2 | BBM-STD-10 V0.5 §8.5; BBM-STD-64 V0.2 References | Assign one accountable task team/source model and controlled Shared snapshot/coordination cycle; freeze IDs/revisions/transforms/profile/coverage/interfaces; boundary changes preserve aliases/IDs and trigger retests. | Federation needs approved source revisions and owned boundaries. | G-F, S04 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 §4.2; BBM-STD-10 V0.5 §8.11.2 | Use Uniclass 2015 as office default, freezing adopted table/release/licence; preserve appointed/authority classifications through mappings and controlled upgrades. Office baseline: Uniclass 2015 July 2026 release (Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27); upgrade only by controlled change. | Uniclass is maintained, not a fixed release or exclusive mandate. | S09, S10, Uniclass | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-68 V0.3 | BBM-STD-01 V0.5 §9.2, §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.1, §10.3; BBM-STD-68 V0.3 §2 | For declared representative seed target native open ≤120 s, sync ≤60 s and prescribed IFC export ≤180 s; record device/network/build/model and approve actual workload-class targets before project acceptance. | Existing BEP pilot targets are local, not vendor minima or universal limits. | P02, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1 | Select Revit 2025.5 full build 25.5.0.57 as new-project qualification baseline; retain mandated build until approved tested change; verify actual install/licence/OS/native-cloud compatibility before activation. Review the baseline at each Autodesk major release. Supported majors are Revit 2024–2027 (latest 2027 update 2027.3, 15 Sep 2026); Revit 2023 is out of Autodesk support: legacy, no new projects, existing projects only with a recorded risk acceptance and upgrade plan; matrix in BBM-STD-91. Superseded by: new projects start by upgrading the office template; the qualified build per release stays a recorded field in BBM-STD-91. | Retains BEP publisher-checked pilot choice; infrastructure research requires capability evidence. | P02, A01, Autodesk previous versions | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1 | Select Autodesk IFC for Revit 2025 package 25.4.40 for qualification; verify package/binary versions/source/licence/hash, preset/mapping and export/receiver tests before activation. | Retains BEP frozen pilot choice without claiming installed compatibility. | P02, S12 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1 | Use same qualified Revit full build for editable native receiver; verify build/OS/link-cloud access and open/edit/sync; no lower-major backward opening assumed. | Common tested route protects appointed native capability. | A01, P02 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1, §10.1 | Select Navisworks Manage as default checking/federation route; freeze actual installed full build/rules and known-result tests; Solibri requires separately qualified approval for the use; missing actual builds hold activation. | One identified route/use avoids unverified interchangeable checking. | P02, S04 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5 | BBM-STD-01 V0.5 §11.3, §14; BBM-STD-10 V0.5 §7.4, §9.2.1 | Recipient freezes actual viewer/FM build or dated cloud configuration, schema/profile/units/document-access mapping; intended-use/update tests must pass before acceptance. | Receiver capability cannot be invented from export format. | S03, S04 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §10.4 | LAP/task leads own information risks and review resources/dependencies/requirements/tools/security/safety before commitment/mobilisation/exchange and material change. | Risk ownership follows actual delivery functions. | G-E, G-F | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-03 V0.3, BBM-STD-10 V0.5 | BBM-STD-00 V0.3 Revision history, ownership and…, §9.4; BBM-STD-01 V0.5 §1.1; BBM-STD-02 V0.3 Revision history and control, §7; BBM-STD-03 V0.3 Decision register; BBM-STD-10 V0.5 §10.5 | Record defaults as decided office policy on 2026-10-14 with linked IDs; activation still requires actual authorised holders, scoped registers, signed rights, installed builds and passing mobilisation/receiver evidence; preserve NOT EXECUTED/NOT VERIFIED facts. | Founder-authorised choices settle defaults without fabricating contract approval or implementation. | G-E, S04 | |
| BBM-STD-10 V0.5 | BBM-STD-10 V0.5 §1.1 | Distribute confirmed project BEPs only to authorised project roles with recipient/access register and acknowledgments; use role-scoped office templates and approved appointment extracts separately. | Project access follows appointment scope and sensitivity. | S05, G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-50 V0.3, BBM-STD-51 V0.2, BBM-STD-67 V0.2, BBM-STD-93 V0.1 | Manual §11.1, §11.2, §12.3, Annex A.6/A.7; BEP §8.3.1; Glossary §1.7; BBM-STD-50 §2; BBM-STD-51 §4; BBM-STD-67 §1 | External containers use the 8-token CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext (re-affirms); ORG-PROJ-DISC-PHASE-SEQUENCE survives only as a mapped internal WIP alias and is never issued; the PHASE token is retired. | One external identity per container. Authority: ISO 19650-2:2018 container naming and the IMI Framework (formerly UK BIM Framework, renamed May 2025) Information Protocol for BS EN ISO 19650-2 Ed 6, https://www.iso.org/standard/68080.html; https://ukbimframework.org/resources/ | G-C | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-50 V0.3, BBM-STD-51 V0.2, BBM-STD-66 V0.2, BBM-STD-68 V0.3, BBM-STD-93 V0.1 | BBM-STD-93 (owner); pointers in BBM-STD-51 §4, BBM-STD-66 §1, Manual §12.1/§12.3, BBM-STD-50, BBM-STD-68 | One discipline/role dictionary in BBM-STD-93 replaces the lists in 51 §4, 66 §1, Manual §12.1/§12.3, 50 and 68. 3-letter code (views, folders, clash, QA) / 1-letter ROLE (file names, sheet prefix): Architecture ARC / A; Structure STR / S; Mechanical MEC / M; Electrical ELE / E; Plumbing/public health PLU / P; Fire & Life Safety FLS / F; Landscape LSC / L; Interiors INT / I; Civil CIV / C; Survey SUR / G; Cost/quantities QTY / Q; Contractor CON / W; General/multi-discipline GEN / Z. LSC = Landscape and FLS = Fire & Life Safety everywhere. Extra disciplines take the next free code in BBM-STD-93. Other documents keep only a pointer and any local subset. | Three conflicting lists cannot all be right. Authority: ISO 13567-2:2017 (CAD layer concepts and codes), https://www.iso.org/standard/70182.html; ISO 12006-2:2015, https://www.iso.org/standard/61753.html | S35 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-50 V0.3, BBM-STD-51 V0.2, BBM-STD-64 V0.2, BBM-STD-93 V0.1 | BBM-STD-64 §2; BBM-STD-93 suitability map | Office suitability codes are SU-WIP, SU-COORD, SU-INFO, SU-REVIEW and SU-ISSUE only (re-affirms); "S1" and similar in BBM-STD-64 are replaced; the mapping to the UK National Annex codes S0–S7, A, B and CR is held in BBM-STD-93. | S1/S2/S3 are severity codes in the office set and cannot also be suitability. Authority: BS EN ISO 19650-2 UK National Annex via the IMI Framework, https://ukbimframework.org/resources/ | G-C | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-54 V0.2, BBM-STD-74 V0.2, BBM-STD-TIDP V0.3, BBM-STD-85 V0.1, BBM-STD-91 V0.1 | Manual §11.1/§11.3; BEP §7.4; BBM-STD-54 §4; BBM-STD-74 §2; TIDP §5; BBM-STD-85; BBM-STD-91 | Default exchange schema is IFC 4.0.2.1 Reference View (re-affirms). IFC 4.3.2.0 (ISO 16739-1:2024) only by recorded approval when the sender's build and the receiver both pass a test exchange; Revit IFC exporter 27.4.0.30 (30 Oct 2026) exports IFC4x3, and IFC 4.3 RV is used only after a test export from the project build passes the project IDS. IFC2x3 only when an appointment or authority profile requires it. Authority submissions use the schema the authority states. | No automatic schema upgrade. Authority: ISO 16739-1:2024, https://www.iso.org/standard/84123.html; Autodesk revit-ifc releases, https://github.com/Autodesk/revit-ifc/releases | S11, S12 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-63 V0.2, BBM-STD-86 V0.1 | BBM-STD-63 §2; BEP §8.2; Manual §11.3; BBM-STD-86 | Survey control needs at least 3 well-distributed control points plus elevation and unit probes (re-affirms); the "2 horizontal points plus a benchmark" rule in BBM-STD-63 is retired. | Three points detect rotation and scale errors that two cannot. Georeferencing context: ISO 16739-1:2024 IfcMapConversion/IfcProjectedCRS, https://www.iso.org/standard/84123.html; Dubai DLTM EPSG:3997, https://epsg.io/3997 | A10 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-50 V0.3, BBM-STD-64 V0.2 | BBM-STD-50 §7; Glossary §1.5; Manual §2.1/§12.4; BEP §5.2.4 | Gate outcomes are the letters A/B/C everywhere, with the meaning in Glossary §1.5 (re-affirms); the wording "gate decisions are words" is retired. | One outcome vocabulary for every gate. Authority: ISO 19650-2:2018 5.7 review and acceptance, https://www.iso.org/standard/68080.html | S04 | |
| BBM-STD-10 V0.5, BBM-STD-50 V0.3, BBM-STD-68 V0.3, BBM-STD-MIDP V0.3 | BEP §6.3 and §10.1; BBM-STD-50 §7; BBM-STD-68 | Review tiers are L1 discipline, L2 cross-discipline and L3 committee; the BIM Manager is not a review tier; BEP §10.1 is aligned. | A role is not a review tier. Authority: ISO 19650-2:2018 5.6.4–5.7 (quality assurance and review before authorisation), https://www.iso.org/standard/68080.html | S04 | |
| BBM-STD-01 V0.5, BBM-STD-12 V0.2, BBM-STD-57 V0.2, BBM-STD-93 V0.1 | Manual §2.1; BBM-STD-12 C5; BBM-STD-57 §4; BBM-STD-93 gate map | There are three gate families, mapped in BBM-STD-93: office stage gates (Manual §2.1), BoD gates G0–G5 (BBM-STD-12) and authority gates (BBM-STD-57 §4). G1 = Concept/planning, G2 = Permit/final design, G3 = Construction activity, G4 = Completion/operation. | The families answer different questions and must not be merged. Authority: RIBA Plan of Work 2020, https://www.riba.org/work/insights-and-resources/riba-plan-of-work/ | S21 | |
| BBM-STD-12 V0.2, BBM-STD-57 V0.2, BBM-STD-93 V0.1 | BBM-STD-57 §2/§4; BBM-STD-12 C4; BBM-STD-93 | The BBM-STD-57 §2/§4 approval-status set is canonical (planned, submitted, approved, conditionally approved, rejected, expired; unknown applicability = Unverified); the BBM-STD-12 C4 working statuses map to it through BBM-STD-93. | One status vocabulary per approval. Authority: the competent authority's own decision records, e.g. Dubai Municipality building-permit services, https://www.dm.gov.ae/municipality-business/buildings-regulation-permits-agency/ | S28 | |
| BBM-STD-12 V0.2, BBM-STD-51 V0.2, BBM-STD-57 V0.2, BBM-STD-85 V0.1 | BBM-STD-51 §3 (owner); BBM-STD-12 A3; BBM-STD-57 §2; BBM-STD-85 | BBM-STD-51 §3 is the one edition and adoption register for the set (ID, instrument, edition, date, URL, source-check date); BBM-STD-12 A3 and BBM-STD-57 §2 cite its IDs and keep no edition list of their own; UAE requirement detail is in BBM-STD-85. | One register per fact (no duplicated edition lists). Authority: ISO 9001:2026 clause 7.5 control of documented information, https://www.iso.org/standard/88464.html | P04 | |
| BBM-STD-03 V0.3, BBM-STD-10 V0.5, BBM-STD-55 V0.2 | BEP §1.1 and §6.1; BBM-STD-55 | The lead appointed party (LAP) owns the BEP; the delegated information manager maintains it (re-affirms); the "LDC BIM Manager manages revisions" wording in BEP §6.1 is replaced. | Ownership follows the appointment. Authority: ISO 19650-2:2018 5.3.2/5.4.1 (BEP by the lead appointed party), https://www.iso.org/standard/68080.html | S02, G-E | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-50 V0.3, BBM-STD-51 V0.2, BBM-STD-93 V0.1 | Manual §3.1, §12.2; BEP §8.3.1; BBM-STD-50; BBM-STD-51 | Revisions are per container: R00 initial WIP, never recycled, and unchanged containers keep their revision (re-affirms); there is no pack-wide monotonic revision. | A pack-wide counter forces false revisions on unchanged content. Authority: BS EN ISO 19650-2 UK National Annex revision codes via the IMI Framework, https://ukbimframework.org/resources/ | G-C | |
| BBM-STD-01 V0.5, BBM-STD-12 V0.2, BBM-STD-54 V0.2, BBM-STD-75 V0.2 | Manual §11.3; BBM-STD-75; BBM-STD-54; BBM-STD-12 IM-08 | COBie is delivered when the EIR requires it; the version is the one the EIR specifies, default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4). | COBie v3 / NBIMS-US V4 final publication is not confirmed; the EIR decides. Authority: NIBS NBIMS-US, https://nibs.org/nbims/v4/resources/ | S15 | |
| All 43 current documents | Header line and title of every document | The version in a document's header and title equals the version in its filename; every revision adds a revision-history row. | Identification of documented information. Authority: ISO 9001:2026 clause 7.5.2, https://www.iso.org/standard/88464.html | P04 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-72 V0.2 | BEP §8.6 and §8.11.2; BBM-STD-72; Glossary §1.7 | Classification_Code with ClassificationTable, ClassificationTitle and ClassificationRelease is canonical (re-affirms); Assembly Code and "Classification Code (Uniclass)" are mapped aliases only. | One classification parameter set. Authority: ISO 12006-2:2015 (confirmed 2026), https://www.iso.org/standard/61753.html; Uniclass 2015 July 2026 release, https://uniclass.thenbs.com/download | S09 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-56 V0.2 | BEP §5.2.4 and §5.x; Glossary §1.5 | Formal delivery is the transition to Published after authorisation (ISO 19650-2 5.7); BEP §5.x is aligned (re-affirms). | Upload or sharing is not delivery. Authority: ISO 19650-2:2018 5.7, https://www.iso.org/standard/68080.html | S04, G-C | |
| BBM-STD-01 V0.5, BBM-STD-66 V0.2, BBM-STD-67 V0.2 | Manual sheet/text rules; BBM-STD-66; BBM-STD-67 | Minimum plotted text height is 2.5 mm on all sheets, measured on paper and not scaled by the view, in the Manual, BBM-STD-66 and BBM-STD-67. | Office legibility decision (local choice, not an ISO figure); drawing presentation context in ISO 128-1:2020, listed in the BBM-STD-51 §3 register | S35 | |
| BBM-STD-00 V0.3, BBM-STD-10 V0.5, BBM-STD-58 V0.2, BBM-STD-69 V0.2, BBM-STD-72 V0.2 | BEP §8.6; BBM-STD-72; BBM-STD-58; BBM-STD-69 | Canonical Fire_Rating is stored as integer minutes, with Fire_Rating_Standard and Fire_Rating_Source; the basis is the UAE Fire & Life Safety Code of Practice (September 2018 edition) plus the tested assembly. | Typed values with their test basis. Authority: UAE Fire & Life Safety Code of Practice, September 2018, https://www.dcd.gov.ae/portal/preventive-safety/uae-fire-and-life-safety-code-of-practice.jsp | S16 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-65 V0.2, BBM-STD-69 V0.2, BBM-STD-70 V0.2, BBM-STD-91 V0.1 | BBM-STD-65 §1.1; BBM-STD-91; Manual §11.3; BEP; BBM-STD-69/70 library save versions | Supported Revit majors are 2024–2027 (latest 2027 update 2027.3, 15 Sep 2026); Revit 2023 is out of Autodesk support: legacy, no new projects, existing projects only with a recorded risk acceptance and an upgrade plan; the full release matrix is in BBM-STD-91. | Releases outside vendor support have no fixes or downloads. Authority: Autodesk previous-versions list and support lifecycle, https://www.autodesk.com/support/account/manage/versions/previous-versions; https://help.autodesk.com/view/RVT/2027/ENU/?guid=RevitReleaseNotes_2027updates_html | A01 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-10 V0.5, BBM-STD-72 V0.2, BBM-STD-75 V0.2 | Glossary §1.7; Manual §3.2; OIR §5.1; BEP §8.6; BBM-STD-72; BBM-STD-75 | Asset_ID is the canonical asset identifier (re-affirms); AssetTag is a mapped alias. | Stable semantic identity over display aliases. Authority: ISO 23386:2020, https://www.iso.org/standard/75401.html | S16, S17 | |
| BBM-STD-01 V0.5, BBM-STD-66 V0.2, BBM-STD-67 V0.2 | Manual §4.1.1; BBM-STD-66 §4; BBM-STD-67 §4 | Revit pen widths map to the ISO 128 line-width series: pens 1–10 = 0.13–1.00 mm at 1:50, one step thinner at 1:100 and two at 1:200; pens 11–16 = 1.00/1.00/0.70 mm; confirmed by a test print before adoption. | ISO 128-1:2020 line-width series 0.13–2.0 mm (register ED-ISO128-1); scale steps are an office choice | ||
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-02 V0.3, BBM-STD-03 V0.3 | Glossary §9.4; Manual §14.C; OIR §7; Directory §7 | Each office decision is stated in full once, in its home section; repeats and register tables carry the ID link only. | Duplicated controlled text drifts; one statement per decision (office good practice, audit //) | ||
| BBM-STD-01 V0.5 | Manual §12.1 | Retired folder numbers are never reused (02-SHARED/05-DOCUMENTS 00/01 stay retired after RFP and scope analysis moved to 01-ADMIN 06/07). | Numbers-never-reused rule ( principle applied to folders) | ||
| BBM-STD-12 V0.2, BBM-STD-55 V0.2 | BBM-STD-12 Control; BBM-STD-55 §3 RACI | The Lead Design Consultant owns the integrated Basis of Design; competent discipline leads own technical criteria; the authority coordinator maintains external submissions; the BIM Manager controls information records; actual holders are recorded per project. | Appointment functions, ISO 19650-1/-2:2018, https://www.iso.org/standard/68080.html | S02 | |
| BBM-STD-12 V0.2, BBM-STD-51 V0.2, BBM-STD-57 V0.2 | BBM-STD-12 A3; BBM-STD-51 §3; BBM-STD-57 §2 | Project code applicability, editions/amendments, transition dates, jurisdiction and verified clauses are frozen before technical reliance; the newest publication is not automatically the adopted code; the freeze is recorded in the BBM-STD-51 §3 register. | DBC + AR 225/2024, https://www.dm.gov.ae/?p=352286; ADIBC 2013, https://www.dmt.gov.ae/-/media/Project/DMT/DMT/Codes/3-ADIMC-2013_1-12-2013.pdf | S28 | |
| BBM-STD-12 V0.2, BBM-STD-57 V0.2 | BBM-STD-12 C0, C4; BBM-STD-57 §4 | Each design approval, construction permission, inspection, connection, completion and occupancy decision is tracked as its own record, with authority/service, prerequisites, exact revisions, confirmed review-cycle source and gate. | DMT Binaa platform, https://www.dmt.gov.ae/en/Media-Centre/News/Binaa-Construction-Permits-Platform-Launched; DM permit services | S28 | |
| BBM-STD-50 V0.3, BBM-STD-93 V0.1 | BBM-STD-50 §4; BBM-STD-93 §2.1 | Trade aliases DU (dry utilities) and WU (wet utilities) map to ROLE C / CIV for external utility networks; a project annex may override where a building-services team produces the network. | dictionary (CIV/C for civil); external networks are civil (office good practice) | ||
| BBM-STD-01 V0.5, BBM-STD-67 V0.2 | Manual §4.10; BBM-STD-67 §2 | Manual §4.10 owns the mandatory title-block field list (including suitability SU-code, approver/authoriser and external container ID); BBM-STD-67 adds only CDE state as a recorded field. | ISO 7200:2004 title-block data fields (register ED-ISO7200);, | ||
| BBM-STD-68 V0.3 | BBM-STD-68 §4 | Independent sampling checks min(total, max(10, ceil(0.10 × total))) items plus every safety-critical or changed item; this is an office choice, not an ISO requirement. | Office decision (audit); ISO 9001:2026 clause 8.6 release check context, https://www.iso.org/standard/88464.html | ||
| BBM-STD-01 V0.5, BBM-STD-65 V0.2, BBM-STD-85 V0.1 | Manual §11.2, §11.4; BBM-STD-65 §4; BBM-STD-85 §3 | The Dubai permit export preset ID is EXP-DM-PERMIT-<schema>-<rev>, held in BBM-STD-65 and used by BBM-STD-85; the former DBP-<schema>-vNN name is a retired alias of the same asset. | One asset, one ID; DM circular 9-1-3, https://www.dm.gov.ae/wp-content/uploads/2026/02/Circular-9-1-3.pdf | S28 | |
| BBM-STD-70 V0.2, BBM-STD-72 V0.2 | BBM-STD-70 §1; BBM-STD-72 §3 | The detail library keeps MasterFormat as a library-only classification; the office classification stays Uniclass 2015; each detail carries a Uniclass Pr/Ss mapping with the pinned release. | Uniclass 2015 July 2026 release, https://uniclass.thenbs.com/download | S09 | |
| BBM-STD-69 V0.2 | BBM-STD-69 §4 | The family parameter cleaning rule (formerly D13 in the retired family DECISIONS.md) lives once in BBM-STD-69 §4; the retired file is not re-created. | Current FAMILIES-DECISIONS-2026-10-28.md holds no cleaning rule (SHA-256 88ed062b…, read 2026-11-04) | ||
| BBM-STD-10 V0.5, BBM-STD-80 V0.2 | BEP §9.2, §9.2.1; BBM-STD-80 §2 | Blender is a fixture-only renderer outside the office software register; production renders use a renderer registered in BEP §9.2/§9.2.1. | Blender LTS, https://www.blender.org/download/lts/; BEP software register | ||
| BBM-STD-51 V0.2, BBM-STD-69 V0.2, BBM-STD-72 V0.2 | BBM-STD-51 §2; BBM-STD-69 §1; BBM-STD-72 §2 | Library index snapshots are always quoted with filename, row count, read date and full SHA-256 hash. | The family index grew 568 → 878 → 889 rows between reads (read-only 2026-11-04) | ||
| BBM-STD-01 V0.5, BBM-STD-MIDP V0.3, BBM-STD-TIDP V0.3, BBM-STD-87 V0.1 | BBM-STD-87 §2; Manual §9.4; MIDP/TIDP §3 | Security triage outcomes are T0 Not sensitive / T1 Sensitive / T2 Sensitive, externally directed; SensitivityClass values Public / Internal / Confidential / Restricted are recorded on every container and delivery row. | ISO 19650-5:2020 clause 4 requires the assessment and a proportionate response, not these labels, https://www.iso.org/standard/74206.html | S05 | |
| BBM-STD-01 V0.5, BBM-STD-93 V0.1 | Manual §12.1; BBM-STD-93 §2 | Project folder discipline numbers keep 00-ARC, 01-STR, 02-MEC, 03-ELE (legacy alias 03-ELEC) and 04-LSC, and add 05-PLU, 06-FLS, 07-INT, 08-CIV, 09-SUR, 10-QTY, 11-CON and 12-GEN. | (folder codes follow the 3-letter codes); existing Manual §12.1 order | ||
| BBM-STD-01 V0.5, BBM-STD-76 V0.2, BBM-STD-90 V0.1 | BBM-STD-90 §3; BBM-STD-76 §1; Manual §9.4 | Office retention minimum for design, model, approval, correspondence, H&S and record classes is 13 years after handover (Decree-Law 25/2025 Art. 821 ten years + Art. 824 three-year claim period); the legal owner rules the final value. | Federal Decree-Law No. 25 of 2025 (Civil Transactions Law), https://uaelegislation.gov.ae/en/legislations/4011 | ||
| BBM-STD-01 V0.5, BBM-STD-65 V0.2, BBM-STD-69 V0.2, BBM-STD-70 V0.2, BBM-STD-71 V0.2, BBM-STD-91 V0.1 | BBM-STD-91 §3; BBM-STD-65 §4.1; BBM-STD-69 §4; BBM-STD-70 §1 | Library save version is the oldest supported Revit major used by live projects; no upgrades inside the library. Refined by: library and template content is saved in the office template's authoring release (currently Revit 2023). | Autodesk previous-versions list (no down-save), https://www.autodesk.com/support/account/manage/versions/previous-versions | A01 | |
| BBM-STD-12 V0.2, BBM-STD-57 V0.2, BBM-STD-93 V0.1 | BBM-STD-57 §2/§4; BBM-STD-93 §7; BBM-STD-12 C4 | Canonical approval statuses are Unverified, Planned, Submitted, Conditionally approved, Approved, Rejected and Expired; BBM-STD-12 C4 Superseded maps to Expired with the Superseded flag kept; Not applicable is an applicability decision, not a status (refines). | Competent authority decision records, e.g. Dubai Municipality building-permit services, https://www.dm.gov.ae/municipality-business/buildings-regulation-permits-agency/ | S28 | |
| BBM-STD-66 V0.2, BBM-STD-93 V0.1 | BBM-STD-93 §2; BBM-STD-66 §1.1 | The ISO 13567 agent-responsible field is the 1-letter BBM-STD-93 ROLE plus hyphen (e.g. "A-"), unless the recipient's mapping defines other values. | ISO 13567-2:2017 two-character agent field, https://www.iso.org/standard/70182.html | S35 | |
| BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-65 V0.2, BBM-STD-69 V0.2, BBM-STD-70 V0.2, BBM-STD-91 V0.1 | Manual §11.3, §11.3.1; BEP §7.4, §9.2.1; BBM-STD-65 §1, §1.1, §4.1; BBM-STD-69 §4; BBM-STD-70 §1; BBM-STD-91 §2, §2.1, §3, §4 | The office Revit template BBM-ARC-TMP-R23 is THE office template (founder decision). It is authored in the oldest Revit release in office use (currently Revit 2023) and must open and upgrade cleanly in Revit 2023–2027; new projects start in a supported release (2024–2027) by upgrading the template and recording the upgrade test (BBM-STD-91 §5); the qualified build per release stays a recorded field. Library and template content is saved in the template's authoring release. Revit 2023 stays out of Autodesk support: legacy authoring release, recorded risk; (no new project in Revit 2023) is unchanged. Supersedes the new-project baseline build; refines. | Revit opens and upgrades older files but cannot save back to an earlier major, so one template in the oldest release serves every supported release. Authority: Autodesk previous-versions list, Revit 2023 not listed (checked 2026-11-04), https://www.autodesk.com/support/account/manage/versions/previous-versions | A01 | |
| BBM-STD-01 V0.5, BBM-STD-65 V0.2 | Manual §4.12, §4.13, §14 A.3/A.4; BBM-STD-65 §2 | Revit view, view-template and filter names never contain ":"; the separator is " - " and a scale is written 1-100 (e.g. "DOC - Plan 1-100", "DETAIL - 1-5 / 1-10", "DOC - Phasing - Existing Halftone"). | Revit rejects names with prohibited characters, including ":" in view names. Authority: Revit API NamingUtils.IsValidName (prohibited-character check), https://help.autodesk.com/cloudhelp/2026/ENU/Revit-API-MainReference/files/html/68b151b1-b170-f351-914a-5aa09ecdb1af.htm | Template alignment 2026-11-04 | |
| BBM-STD-01 V0.5, BBM-STD-65 V0.2, BBM-STD-67 V0.2, BBM-STD-69 V0.2, BBM-STD-93 V0.1 | Manual §4.10, §4.11.2, §5; BBM-STD-65 §2; BBM-STD-67 §2; BBM-STD-69 §2; BBM-STD-93 §2 | Office title blocks are the published library series BBM-G-TTB- plus sheet size (BBM-STD-69 §2 grammar, published identity kept per W3-C01): BBM-G-TTB-A0, BBM-G-TTB-A1, BBM-G-TTB-A2, BBM-G-TTB-A3 (ISO 5457 sizes); A1, A2 and A3 must exist in the office template, A2 and A3 are created in the next template pass; the former TITLEBLOCK - A0/A1/A2/A3 labels are retired. The G token is the library's published general token, not the BBM-STD-93 Survey ROLE G. | Published library holds BBM-G-TTB-A0.rfa and BBM-G-TTB-A1.rfa in 02-LIBRARIES/01-FAMILIES/00-STD-TTB (read-only listing 2026-11-04); one family series, no second naming authority | Template alignment 2026-11-04 | |
| BBM-STD-01 V0.5, BBM-STD-65 V0.2 | Manual §3.3; BBM-STD-65 §2 | Keep the four user worksets (Shared Levels and Grids, Core Modeling, Links by loading group, Imports); Links may be split per linked discipline as Manual §3.3 already allows; the template workset file BBM-STD_WRKST.txt (52 worksets) is regenerated to match in the next template pass. | Re-affirms; unused user worksets add ownership and loading overhead without a use. | A02 | |
| BBM-STD-65 V0.2, BBM-STD-72 V0.2 | BBM-STD-72 §2; BBM-STD-65 §2 | BBM-SHARED_PARAMETERS.txt carries every Manual §3.2 core parameter under its canonical name (Classification_Code with ClassificationTable/Title/Release, System, Fire_Rating with Fire_Rating_Standard/Source, Asset_ID, Export Exclude, Model Origin OK?) plus the COBie parameters of the EIR's COBie version (default COBie 2.4); the file is updated in the next template pass, GUIDs assigned once by the curator. | One property dictionary bound by GUID (/119/121). Authority: ISO 23386:2020, https://www.iso.org/standard/75401.html | S16 | |
| BBM-STD-66 V0.2 | BBM-STD-66 §1 | The DWS-checked layer grammar D-MMMM[-MMMM[-MMMM]]-S of BBM-STD-66 §1 is the office layer standard; the office CAD standards files (DWS/DWT) are rebuilt to it; layers outside it are mapped, not adopted. | ISO 13567-1/-2:2017 organisational concepts; local grammar is an office selection, https://www.iso.org/standard/70182.html | S35 | |
| BBM-STD-66 V0.2 | BBM-STD-66 §4 | The fixed-weight monochrome CTB SYN-PLOT66 (ISO 128 widths, all black 100%, reference halftone ACI8 0.13 mm at 50%) is the office plot style; the office plot files (CTB and page setups) are rebuilt to it; observed client-derived CTBs are not office masters. | ISO 128-1:2020 line-width series (register ED-ISO128-1), https://www.iso.org/standard/65296.html; pen mapping | Template alignment 2026-11-04 | |
| BBM-STD-00 V0.3, BBM-STD-01 V0.5, BBM-STD-10 V0.5, BBM-STD-11 V0.2, BBM-STD-12 V0.2, BBM-STD-51 V0.2, BBM-STD-57 V0.2, BBM-STD-65 V0.2, BBM-STD-66 V0.2, BBM-STD-68 V0.3, BBM-STD-69 V0.2, BBM-STD-70 V0.2, BBM-STD-71 V0.2, BBM-STD-72 V0.2, BBM-STD-73 V0.2, BBM-STD-80 V0.2, BBM-STD-82 V0.2, BBM-STD-93 V0.1, BBM-STD-95 V0.1, BBM-STD-25 Guide V0.3 | Manual §12.1 (owner); Glossary §1.5; BBM-STD-93 §2, §4; BEP §5.2.1, §5.2.4; BBM-STD-51 §2 | Folder names use NN-NAME without dots, spaces or &, for CAD path safety (founder decision 2026-11-04); one project folder tree defined in Manual §12.1, ordered state → data type → discipline. State folders 01-WIP, 02-SHARED, 03-PUBLISHED, 04-ARCHIVE under 00-PIM; data types 00-RVT, 01-DWG, 02-PPT under WIP and SHARED; discipline folders carry the BBM-STD-93 numbers everywhere; PUBLISHED is split by stage, then by YYYY-MM-DD-DESCRIPTION issue pack; retired numbers stay retired. Supersedes the dotted folder forms and the platform folder alias of. | Founder decision 2026-11-04, verbatim: "سقط الدوتس عندنا في الاستاندرد علشان ساعات بتعمل مشاكل في باث الكاد … احنا مش هنصلح السيرفر احنا بنعمل لنا استاندرد عاوزه يبقى مظبوط … المهم متبقاش في حاجة عندي في الاستاندرد مش متغطية" (drop the dots from folder names in our standard because they sometimes break CAD paths; we are making our standard right, not fixing the server; nothing in the standard may be left uncovered). Reason: dots in folder names break some CAD/xref path handling. | Founder decision 2026-11-04 | |
| BBM-STD-01 V0.5, BBM-STD-68 V0.3, BBM-STD-96 V0.1 | BBM-STD-96 §4, §4.1, §5; Manual §9.1; BBM-STD-68 §1 | The practice director owns the office QMS (policy, objectives, management review); the BIM Manager's quality framework is its information-quality part. | ISO 9001:2026 5.1 and 5.3 top-management accountability (register ED-ISO9001); keeps ownership of the information framework unchanged | QMS patch 2026-11-04 | |
| BBM-STD-68 V0.3, BBM-STD-96 V0.1, BBM-STD-97 V0.1, BBM-STD-98 V0.1 | BBM-STD-96 §1; BBM-STD-97 §0 | The office QMS documents are BBM-STD-96 (manual and policy), BBM-STD-97 (procedures) and BBM-STD-98 (KPIs); BBM-STD-99 is left free. Procedure IDs are QP-01 to QP-15; checklist IDs read <workbook>-<sheet>-<nn> with workbook codes DR, PR, SP, SU, SB, SV, DC, QA; the checklists live in 07-QA-QC/01-BIM to 09-AUDIT (names per). | One numbered home per QMS document and one ID per check (ISO 9001:2026 7.5; ISO 10005 quality-plan structure, register ED-ISO10005) | QMS patch 2026-11-04 | |
| BBM-STD-97 V0.1, BBM-STD-98 V0.1 | BBM-STD-98 §3, §4; BBM-STD-97 QP-02, QP-12 | Office time choices: site visit report within 2 working days, complaint acknowledgement within 2 working days, complaint answer within 10 working days, project quality plan within 4 weeks of appointment. | Office choices, not taken from a standard (BBM-STD-98 §4); complaints handling per ISO 10002:2018 (register ED-ISO10002) | QMS patch 2026-11-04 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2 | BBM-STD-51 §3 ED-DM-9-1-1; BBM-STD-85 §3 | DM circular 9-1-1 of 2021 (dated 23 Aug 2021) applies BIM to the architectural and mechanical works of buildings over 20 floors, over 200,000 sq ft, specialised buildings (hospitals, universities and the like), all government projects and all projects submitted by a foreign office subsidiary; and to the structural works of buildings over 40 floors, over 300,000 sq ft, specialised buildings and buildings submitted by a foreign office subsidiary. It is recorded as the 2021 BIM-use scope; the permit-submission scope is 9-1-2 and 9-1-3, and where several apply the widest scope is followed. | Circular text read in full 2026-11-05 (English technical translation; the Arabic version prevails), https://dmpmedia.dm.gov.ae/uploads/2024/11/9-1-1-Application-of-Buildings-Information-Modelling.pdf | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-68 V0.4, BBM-STD-85 V0.2, BBM-STD-86 V0.2 | BBM-STD-51 §3 ED-DUBAI-BIM-STD; BBM-STD-85 §3; BBM-STD-86 §2; checklist AU-07 | The current Dubai BIM Standard is Version 1.4 (changelog release 8 Jun 2026). Permit IFC files use the IFC4 schema with the.ifc extension (§6.1.1), exported with the authority Revit setup "Dubai BIM E-Submission (IFC4)Reference View"; the office preset is EXP-DM-PERMIT-IFC4-<rev>. The attribute matrix is Appendix B Model Attribute Matrix issued with Version 1.4 (file dated 5 Jun 2026; it carries no separate version number, so the record is "Appendix B, Dubai BIM Standard 1.4" and the attribute BIMStandardVersion = 1.4.0), with Appendix A Model Element Matrix, Appendix C Usage Codes and the DM IDS DMBIM_IDS_V1. Geo-referencing is EPSG:3997 with elevations on the DMD level (§4.1.2, §7.7). The ZIP is within the platform maximum (150 MB in the 1.4 changelog). Supersedes the rule-only wording of F07 and the checklist setup name "IFC2.3/IFC4 Dubai Building Permit". | Dubai BIM Standard package read 2026-11-05 from the authority download named on https://buildindubai.gov.ae/bim: https://api.buildindubai.gov.ae/assets/BIM/Documents/DubaiBIMStandards.zip (Last-Modified 2 Nov 2026): DubaiBIMStandard.pdf v1.4, Misc/Changelog.xlsx, Appendix B, Templates/Revit/Dubai BIM E-Submission_IFC4_ReferenceView.json; DM bSDD dictionary DMBIMInfo 1.0.4 (5 Mar 2026), https://search.bsdd.buildingsmart.org/uri/dm/DMBIMInfo/1.0.4 | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2 | BBM-STD-51 §3 ED-DBC; BBM-STD-85 §4 | DM Administrative Resolution No. 225 of 2024 (issued 16 Jul 2024, published 13 Aug 2024, in force 30 days after publication, Art. 6) applies only to plots of 250 m² or less and the building on them (Art. 1–2) and permits seven DBC building-parameter changes (Art. 3, table): (1) no lifts where the building is G+2 or lower and has 100 occupants or fewer; (2) ground-floor lift lobby width 1.8 m; (3) typical-floor corridor and lift lobby width 1.5 m; (4) one shared WC per shop of 100 m² or less, or grouped shop WCs per the DBC; (5) no bulky-waste area; (6) no recycling area in the refuse room; (7) no extra 300 mm parking-bay width beside columns and walls, the DBC minimum clear bay still applying. It is read together with the DBC (Art. 4). The resolution names parameters, not DBC clause numbers: the DBC clause per item is recorded at project start against ED-DBC. | Resolution text read in full 2026-11-05 (Arabic), https://dmpmedia.dm.gov.ae/uploads/2024/08/قرار-إداري-رقم-225-لسنة-2004.pdf; DM document page https://www.dm.gov.ae/documents/administrative-resolution-no-225-of-2024-regarding-amending-some-building-specifications-in-the-dubai-building-code/ | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2 | BBM-STD-51 §3 ED-DXB-LAW-3-2026; BBM-STD-85 §4 | Dubai Law No. 3 of 2026 was published in the Dubai Official Gazette, issue 764, on 12 Mar 2026; it is in force 60 days after publication (Art. 25), i.e. from 11 May 2026. | Supreme Legislation Committee legislation portal, record of Law No. (3) of 2026 (issue 764, status in force, issued 27 Feb 2026, listing date 12/03/2026), read 2026-11-05, https://slc.dubai.gov.ae/ar/legislation-portal/detail?id=0900000a805341fc | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2, BBM-STD-86 V0.2 | BBM-STD-86 §2 CRS-DXB, §6; BBM-STD-85 §3 | Dubai permit models use EPSG:3997 (WGS 84 / Dubai Local TM) as required by the Dubai BIM Standard 1.4 §4.1.2. EPSG:3997 is defined on WGS 84 (base CRS EPSG:4326), so WGS 84 survey data needs no datum transformation (record "none: WGS 84 based"). Legacy grids (Clarke 1880 / Nahrwan, e.g. EPSG:27040) are converted only through the DM Survey Department service "Request for Coordinates Transformation", never with a generic EPSG operation (EPSG:15953 for Dubai states 5 m accuracy). Heights are on the DMD level (Port Rashid datum), which has no EPSG vertical CRS: record the name "DMD (Port Rashid)"; GNSS heights are converted through the DM "orthometric height conversion" service. The transformation field of the CRS record holds "none: WGS 84 based" or the DM service reference. | Dubai BIM Standard 1.4 §4.1.2, §7.7 (https://api.buildindubai.gov.ae/assets/BIM/Documents/DubaiBIMStandards.zip); https://epsg.io/3997; https://epsg.io/27040 (transformation list); DM Survey Department geodesy services, https://www.dm.gov.ae/survey-department/geodesy; all read 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-68 V0.4, BBM-STD-86 V0.2 | BBM-STD-86 §5; BBM-STD-68 §2.3; checklist MH-01, MH-02 | Office default control-point acceptance: at each of the at least three control points the value read back from the native model and from the exported IFC equals the surveyed E/N/H within 10 mm horizontally and 10 mm vertically. Where the surveyor's stated control accuracy is coarser, that stated accuracy is the limit and is recorded. A stricter appointment or authority value governs. The DM figure for the plot is checked at project start against the DM Survey Department control-coordinate certificate and recorded in BEP §8.2 (rule-based: DM publishes no BIM tolerance). | Published Dubai authority figure: DIFC Registrar of Real Property, Directives for the Preparation of Survey Plans in DIFC §3.4.3, control points at 10 mm + 20 ppm horizontal and vertical relative to the origin station, https://assets.difc.com/v1/media/edge/images/dubaiintern0078-difcexperie96c5-production-3253/media/project/difcexperiences/difc/difcwebsite/documents/registrars-and-commissioners/registrar-of-real-property/registrar-of-field-property-directives/directives_for_the_preparation_of_survey_plans_in_difc.pdf; Dubai Law No. 6 of 2017 leaves survey specifications to DM, https://dlp.dubai.gov.ae/Legislation%20Reference/2017/Law%20No.%20(6)%20of%202017%20Regulating%20Survey%20Works.html; read 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2, BBM-STD-86 V0.2 | BBM-STD-86 §2 CRS-AUH | Abu Dhabi horizontal CRS: WGS 84 (ITRF2000, epoch 2000.0) / UTM zone 40N, EPSG:32640, for plots east of 54°E, and UTM zone 39N, EPSG:32639, for plots west of 54°E (the zone is chosen from the plot, never one emirate-wide code). Vertical: Ras Ghumays, vertical CRS EPSG:5843 (datum EPSG:1146). The plot's ADM/DMT guideline still overrides when it states otherwise. Supersedes "rule-based, no default" in BBM-STD-86 V0.1. | DMT / ITC Unified As-Built GeoSpatial Data Submission Standards §2.1 (Abu Dhabi Emirate Spatial Reference System) and §3.5 (EPSG:32639 / EPSG:32640, vertical datum Ras Ghumays), https://admobility.gov.ae/services/-/media/As-Built-Data-Submission-Standards.pdf; https://epsg.io/5843; read 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3, BBM-STD-85 V0.2 | BBM-STD-85 §5, §6, §8, §10; BBM-STD-51 §3 ED-UAE-FLS, ED-ADIBC, ED-SIRA | Rule-based (no primary source states the value on 2026-11-05): emirate amendments to the UAE Fire & Life Safety Code, the SIRA security-drawing rule, any ADIBC edition after 2013 and the other authority routes (fit-out, UAS, advertising, Arabic text, registration, portal checks) are checked at project start against the named authority document (the emirate Civil Defence code page and circulars; the SIRA / DM permit checklist for the plot; the DMT codes page; the service page of the authority that controls the plot) and recorded in BEP §1.12 with title, edition, URL and check date. Each such row is marked "rule-based" in BBM-STD-51 §3 and BBM-STD-85. | §2 F03, F06, F11, F15 searches and the 2026-11-05 re-search found no primary text stating these values; the rule removes dependence on them (BBM-STD-85 §1) | Settlement 2026-11-05 | |
| BBM-STD-51 V0.3 | BBM-STD-51 §3 ED-ISO10002, ED-AUH-PLANNING, ED-UTILITY-REGS | ED-ISO10002 = ISO 10002:2018, edition 3, published 2018-07 (60.60 on 2018-07-16), confirmed 2023-12-11. ED-AUH-PLANNING = Abu Dhabi Capital Development Code (DMT) for plots in Abu Dhabi City Municipality; for Al Ain and Project the DMT development code of that municipality, recorded at project start. ED-UTILITY-REGS = Dubai: DEWA Regulations for Electrical Installations, 2017 Edition; Abu Dhabi: Abu Dhabi Emirate Guideline for Infrastructure Services Standards, 2nd edition, January 2017 (index of the ADDC / RSB water and electricity codes); other utilities (district cooling, gas, telecom) per the provider's current regulation recorded at project start. | https://www.iso.org/standard/71580.html; https://www.dmt.gov.ae/-/media/Project/DMT/DMT/E-Library/Abu-Dhabi-Capital-Development-Code.pdf; https://www.dewa.gov.ae/-/media/DEWA_Regulations_for_Electrical_Installations_2017_Edition.ashx; https://www.dmt.gov.ae/-/media/Project/DMT/ADM/E-Library/Abu-Dhabi-Emirate-Guideline-for-Infrastructure-Services-Standards.pdf; read 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-01 V0.6, BBM-STD-93 V0.2 | BBM-STD-93 §2.2; Manual §12.3 | Container-name token lists are office rules with patterns, held in BBM-STD-93 §2.2: CLIENT ^[A-Z0-9]{2,6}$ (client's own code, else 3 letters allocated at mobilisation); ORG ^[A-Z0-9]{2,6}$ (this office = BABOOM; each other party one code in the project naming register); PROJ ^[A-Z0-9]{2,6}$ (client project code, else office job number P001–P999, never reused); VOLUME = ZZ (whole), XX (none) or 01–99 from the project volume register; LEVEL = ZZ, XX, GF, RF, 01–99, B1… (basements) or M1… (mezzanines); TYPE from the 28-code information-type list. All are valid from mobilisation (the first container, Stage 0/1); a registered value is never changed or reused after first issue. Client-imposed lists map one-to-one in the BEP. | ISO 19650-2:2018 5.1.7 / UK National Annex information types via the IMI Framework, https://ukbimframework.org/resources/; Manual §12.3 regex lengths; office project register (synthetic examples only) | Settlement 2026-11-05 | |
| BBM-STD-93 V0.2, BBM-STD-97 V0.1 | BBM-STD-93 §2.3 | QMS checklist workbook codes: DR Design review (02-DESIGN-REVIEW), PR Proposals (03-PROPOSALS), SP Specifications (04-SPECIFICATIONS), SU Sustainability (05-SUSTAINABILITY), SB Authority submissions (06-SUBMISSIONS), SV Site supervision (07-SUPERVISION), DC Document control (08-DOCUMENT-CONTROL), QA QMS audit (09-AUDIT); the BIM checklist in 01-BIM keeps its sheet prefixes (MH, IC, DS, DI, AR, ID, LS, ST, ME, AU, IS). SU here is a workbook code, never a suitability code (SU-…). | Read 2026-11-05 from the published workbooks in BABOOM-BIM-STANDARD\ 07 QA-QC (check IDs DR-, PR-, SP-, SU-, SB-, SV-, DC-, QA- per workbook) | Settlement 2026-11-05 | |
| BBM-STD-01 V0.6, BBM-STD-68 V0.4 | Manual §9.2; BBM-STD-68 §2.1; checklist MH-15 | Model warnings gate (office choice): at share, 0 warnings of the blocking list WRN-01..WRN-11; all other warnings at most 100 per 10,000 model elements (element count from the Model Checker count of model categories); no warning type above its count at the previous gate without a recorded disposition; the total is recorded at each gate. Above the limit is a nonconformity S3 Minor with a correction plan before the next gate, not an automatic block. Replaces the mobilisation-baseline limit and the checklist placeholder "BEP X per 10k". | Autodesk states there is no fixed per-warning performance benchmark and advises classifying warnings by risk, resolving high-impact types and documenting accepted low-risk ones (Autodesk support, May 2026, https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Impact-of-model-warnings-on-the-hardware-resource-usage-of-Revit.html); Autodesk Construction IQ health score separates critical and non-critical warnings (https://help.autodesk.com/cloudhelp/ENG/Docs-Insight/files/construction-IQ/get-started-with-construction-IQ/Construction-IQ-Model-Analytics-Metrics.html); 100 per 10,000 is an office trend trigger, not an Autodesk figure | Settlement 2026-11-05 | |
| BBM-STD-68 V0.4 | BBM-STD-68 §2.1 | The blocking warning list is WRN-01 overlapping walls; WRN-02 identical instances in the same place; WRN-03 room not in a properly enclosed region; WRN-04 multiple rooms in the same enclosed region; WRN-05 area not in a properly enclosed region; WRN-06 multiple areas in the same enclosed region; WRN-07 space not in a properly enclosed region; WRN-08 multiple spaces in the same enclosed region; WRN-09 overlapping floors; WRN-10 overlapping room separation lines; WRN-11 duplicate Mark or Number values. Each is matched on the leading warning text in the qualified Revit build (BBM-STD-91); the template custodian confirms each text on a fixture before the list is loaded in the office check set, and a new entry needs a row here. | Autodesk: warnings on geometry, rooms, areas, constraints or overlapping elements are the most likely to have functional impact (https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Impact-of-model-warnings-on-the-hardware-resource-usage-of-Revit.html); double counting and unenclosed rooms/areas/spaces corrupt schedules and area reports (BBM-STD-58, BBM-STD-60); BBM-STD-68 V0.3 §2 starter list extended | Settlement 2026-11-05 | |
| BBM-STD-68 V0.4 | BBM-STD-68 §2.2 | Every check carries three attributes. Automation: auto = a rule-based tool (Model Checker checkset, IDS validator, naming regex, office script) gives pass/fail without judgement; assisted = a tool, schedule or report gives the data and a person compares it with the criterion; manual = inspection. Evidence path, by checklist sheet: Model health and discipline sheets ARC/ID/LSC/STR -> 00-PIM/02-SHARED/06-REPORTS/01-MODEL-HEALTH; MEP coordination -> 00-PIM/02-SHARED/06-REPORTS/02-CLASHES; Data & IDS -> 00-PIM/02-SHARED/09-NON-GRAPHICAL/02-IFC-VALIDATION (at issue also the pack 04-REPORTS/00-IFC-VALIDATION); Information container -> pack 04-REPORTS/01-NAMING-VALIDATION; Drawings & sheets -> pack 04-REPORTS; Authority submission -> 02-REG/00-PERMITS/01-BIM-SUBMISSIONS; Issue sign-off -> pack 05-TRANSMITTAL; the completed checklist copy -> 00-PIM/02-SHARED/05-DOCUMENTS/07-QA-QC. Guide link: the one BBM-STD-21..37 guide that teaches the task (mapping in BBM-STD-68 §2.2); where no guide teaches it, the BBM-STD-82 training module. | Prior art: Autodesk Model Checker rule-based checksets report counts and pass/fail (https://www.autodesk.com/learn/ondemand/module/check-standards-compliance-on-building-projects-using-revit/unit/1l5dHwxx6XAQeiltaSDnec); IDS 1.0 machine validation (register ED-IDS); Manual §9.2 and §12.1 evidence folders; BBM-STD-82 guide set | Settlement 2026-11-05 | |
| BBM-STD-68 V0.4 | BBM-STD-68 §2.3; checklist MH-01, MH-02, LS-01, AR-04, AR-13, ST-05, ST-06 | Office default tolerances in pass criteria (a stricter appointment, brief or authority value governs): MH-01 / MH-02 per; LS-01 topography within the survey's stated vertical accuracy, recorded in BEP §8.2; AR-04 room area within ±5% of the brief area or ±1.0 m², whichever is greater, unless the brief states its own; AR-13 and ST-06 zero open H failures at 0 mm and zero open C/A failures against each active rule's recorded requirement (BBM-STD-50 §3); ST-05 rebar and construction tolerances as stated by the structural engineer of record for the stage, recorded in the BEP. | Office choice for AR-04 (common brief practice; not an ISO figure); H/C/A semantics BBM-STD-50 §3; survey evidence BBM-STD-63 §2 | Settlement 2026-11-05 | |
| BBM-STD-50 V0.4 | BBM-STD-50 §4.1 | All 91 trade pairs are decided in BBM-STD-50 §4.1; no pair stays U in the office baseline. The 63 pairs outside the §4 illustration take: self-pairs ID, LI, LS, CI = H,D and DU, WU = H,D,CA; ID with AR/ME/EL/LI/WS/DR/FF = H,CA, ID-ST = H, ID-LS = H (zero population allowed with a scope note), ID-CI/DU/WU = NA (no shared space; building entries are tested in the services-utility pairs); LI with AR/ME/WS/DR/FF/LS/CI/DU = H,CA, LI-ST = H, LI-EL = H,D (one owner of each luminaire across the EL/LI boundary), LI-WU = H; LS, CI, DU and WU with every services trade (ME, EL, WS, DR, FF) and with each other = H,CA; AR with LS/CI = H,CA and with DU/WU = H; ST with LS/CI = H and with DU/WU = H,CA. The C and A rows of AR-AR and ST-ST are NA (in-model designer checks, not federated tests). A project copy may switch a pair to NA only with a recorded reason and approver. | Clearance/access is applied wherever a service, network or maintained element meets another trade, following common federated clash-matrix practice (hard tests by trade pair, clearance tests for serviced elements); utility separations come from the utility authority regulations (register ED-UTILITY-REGS); BBM-STD-50 §3 semantics | Settlement 2026-11-05 | |
| BBM-STD-50 V0.4 | BBM-STD-50 §4.1 | Rule owner per pair: the lead appointed party owns the test baseline; the resolver of a clash is the discipline lead of the lower trade in the office routing precedence ST > AR > CI > DR > WU > DU > ME > FF > WS > EL > LI > ID > LS (self-pairs: that trade). C and A tolerances are never blanket values: each active C/A rule carries the recorded requirement (design, manufacturer, code or utility regulation) with its source ID; a rule without it stays inactive. | Routing precedence follows common MEP coordination practice (structure and architecture fixed, gravity systems before large ducts, before pressurised pipework, before containment and lighting, then finishes and planting); office choice recorded here | Settlement 2026-11-05 | |
| BBM-STD-13 V0.1, BBM-STD-99 V0.1 | BBM-STD-13 header; BBM-STD-99 header | The Architect of Record standard is BBM-STD-13 and the project tracker standard is BBM-STD-99. BBM-STD-84 is already used (00-FOLDER-STRUCTURE information-system record) and is not reused; 13 is the first free number after the core project series 10–12; 99 was left free by and sits after the QMS documents 96–98 it serves. | Numbers are never reused (BBM-STD-51 §2 stable IDs) | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1 | BBM-STD-13 §2 | The Architect of Record / consultant of record is the engineering consultancy registered with the permit authority of the emirate for the discipline and building category (Dubai: DM register under Dubai Law No. 14 of 2025; Abu Dhabi: DMT classification with registered engineers). One consultant of record per discipline per permit; holders and registration cards in the private Directory. | Dubai Law 14/2025; DM AR 255/2021 categories; DMT classification and AD Decision 113/2025 engineer grades | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1 | BBM-STD-13 §4.2, §7 | The office signs or stamps only what it has reviewed and adopted: a container is stamped only when its AOR review is recorded in TRK-CMT with no open Level 0/1 comment and the registered engineer of the discipline has checked it; a refusal is one line "held: <condition>" in the tracker row. The sign-off matrix in BBM-STD-13 §7 is the office default. | Decennial liability is joint and cannot be excluded (FDL 25/2025 Arts. 821, 823); office practice of AOR comment trackers | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1, BBM-STD-99 V0.1 | BBM-STD-13 §4.2; BBM-STD-99 TRK-CMT | Review comments carry the five-level classification 0 Rejected, 1 Significant, 2 Minor, 3 Closed, 4 Note; an unanswered Level 2 becomes Level 1 at the next stage review. These levels are comment severity only; they are not gate outcomes (A/B/C), issue severity (S1–S3) or review tiers (L1–L3). | Client comment trackers found in office practice (survey 2026-11-05); BBM-STD-93 §5, §8 | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1, BBM-STD-99 V0.1 | BBM-STD-13 §6; BBM-STD-99 §4 | Construction-stage review codes are A Approved, B Approved as noted, C Revise and resubmit, D Rejected, E Information/records, plus UR Under review, as on the office Material Inspection Request form; the client decision (No objection, proceed / Objection, resubmit) is a separate field. They map to the BBM-STD-93 §5 gate outcome only where a gate needs it: A to A, B to B, C and D to C; E has no gate meaning. | Office supervision forms 04 01, 04 03, 04 05, MIR (Oct 2021); Procore default responses; BBM-STD-93 §5 | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1 | BBM-STD-99 §4 | Resubmissions are a new row with the same record ID and the next revision (R00, R01 …), never an overwrite; only the latest revision of an ID counts in status totals, and the number of rows per ID is the cycle count. | Office site submittal registers (one row per revision); BBM-STD-93 §3 revision forms | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1, BBM-STD-99 V0.1 | BBM-STD-13 §6; BBM-STD-99 §5 | Turnaround defaults, used when the contract states none: submittals 14 calendar days from complete receipt (FIDIC 2017 Engineer review period of 21 days is the outer reference); RFI 7 calendar days; inspection request answered by the requested time with at least 1 working day notice; SOR response 3 working days, then it becomes an NCR; NCR close-out 14 days; site instruction acknowledgement and transmittal acknowledgement 2 working days; minutes issued in 2 working days; review comments answered in 10 working days or by the next issue; variation evaluation 14 days from a complete proposal; authority rows use the authority service time entered per row. Working days exclude Saturday and Sunday and the holidays listed in Settings. | Office SOR form (3 days), office NCR log templates (14 days), FIDIC 2017 Sub-Clause 5.2/4.4 (21 days), (2 working days); UAE federal weekend | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1 | BBM-STD-99 §3 | Tracker record IDs read <PROJ>-<KIND>-<ROLE>-<NNNN> (PROJ and ROLE per BBM-STD-93 §2, §2.2; KIND per BBM-STD-99 §3; NNNN never reused) with the revision in its own column. The library templates are named BBM-FRM-TRK-<NN>-<TITLE>-v01.xlsx in 01-TEMPLATES/04-DOCUMENT-CONTROL/03-TRACKERS; a project copy is a container named CLIENT-ORG-PROJ-ZZ-XX-SH-Z-NNNN.xlsx (type SH schedule, role Z general). | ,, | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1, BBM-STD-57 V0.2, BBM-STD-MIDP V0.3 | BBM-STD-99 §2 | One tracker set, no second register: TRK-NOC is the BBM-STD-57 §4 submission register in working form (its 23 columns kept in order, working columns added after them) and TRK-DEL holds the MIDP Progress columns; a project keeps one of each, never both. The registers named in the BBM-STD-97 checklists (submittal, RFI, NCR, instruction, inspection, visit report, document, transmittal, handover) are the BBM-STD-99 trackers. | One of everything; BBM-STD-57 §4; MIDP V0.2 Progress sheet | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1 | BBM-STD-99 §6 | Evidence rule: the tracker is an index, the signed form or decision is the record. A closed row carries the CDE link of its evidence; rows are never deleted (void with a reason); a row is closed only by the role named in BBM-STD-99 §5. | ISO 9001:2026 7.5; ISO 19650-2 5.7; BBM-STD-76 | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1 | BBM-STD-99 §5 | All ageing and overdue values are computed against the Data date in Settings (default today); a reported snapshot is saved as PDF with its data date, population and period, following the BBM-STD-83 stale-snapshot rule. | BBM-STD-83 §1–3; BBM-STD-98 §2 | Survey and research 2026-11-05 | |
| BBM-STD-97 V0.2, BBM-STD-13 V0.1 | BBM-STD-97 QP-09 §2, references; BBM-STD-13 §8 | Legal basis updated: DM Administrative Resolution 275 of 2024 replaces Resolution 10 of 2019 (its Art. 16); Dubai Law No. 14 of 2025 replaces Local Order 89 of 1994; for contracts from 1 June 2026 decennial liability is Federal Decree-Law 25 of 2025 Arts. 821–824 (Arts. 880–883 of Federal Law 5 of 1985 for earlier contracts). The QMS checklist sources DMAR275 and ART821 carry the same text. | dlp.dubai.gov.ae AR 275/2024 Art. 16; slc.dubai.gov.ae Law 14/2025; uaelegislation.gov.ae FDL 25/2025 Art. 821 | Survey and research 2026-11-05 | |
| BBM-STD-99 V0.1 | BBM-STD-99 §3 | The tracker set has 13 trackers: the 12 requested plus TRK-CMT review comments, the tracker the office already uses most and the data source of K-DR-02. Site visit reports (K-SV-01) are a sheet of TRK-SI. | Office practice survey 2026-11-05; BBM-STD-98 K-DR-02, K-SV-01 | Survey and research 2026-11-05 | |
| BBM-STD-13 V0.1 | BBM-STD-13 §3, §9 | Every AOR appointment records one service model (M1 design and supervision, M2 AOR for a design architect, M3 supervision only or replacement, M4 novated design consultant, M5 design only) at contract review and in the BEP; a change of model is a services variation in TRK-VO approved before the new scope starts. The BBM-STD-13 §9 RACI is the office default for M2. | Office agreements, novations and supervision variations (names only, survey 2026-11-05); FIDIC White Book 2017 Cl. 5 | Survey and research 2026-11-05 | |
| BBM-STD-51 V0.4, BBM-STD-68 V0.5, BBM-STD-96 V0.2, BBM-STD-97 V0.3 | BBM-STD-51 §3 ED-ISO19011; BBM-STD-68 §1.1 and references; BBM-STD-96 §9.2, §11 and references; BBM-STD-97 QP-13 and references | ED-ISO19011 = ISO 19011:2026, edition 4, published May 2026 (stage 60.60); ISO 19011:2018 was withdrawn on 27 May 2026 and is no longer cited. It is the auditing guidance for the internal audit (QP-13), the audit programme and auditor competence and independence. | https://www.iso.org/standard/19011; https://www.iso.org/standard/70017.html; read 2026-11-05 (standard watch no. 1) | Settlement 2026-11-05 | |
| BBM-STD-51 V0.4, BBM-STD-75 V0.3, BBM-STD-85 V0.3, BBM-STD-00 V0.4, BBM-STD-01 V0.7, BBM-STD-02 V0.4, BBM-STD-10 V0.6, BBM-STD-12 V0.3, BBM-STD-52 V0.3, BBM-STD-57 V0.3, BBM-STD-97 V0.3 | BBM-STD-51 §3 ED-DM-11-9-1; BBM-STD-75 §7; BBM-STD-85 §4, §11; BBM-STD-12 AP-070, R42; BBM-STD-52 AIR-006; BBM-STD-57 §2; BBM-STD-97 QP-09 §2 | New register row ED-DM-11-9-1 = DM circular (11-9-1) of 2026, dated 1 Oct 2026, applying ED-DXB-LAW-3-2026, with guidance manual 11-9-1-1 (May 2026): Building Quality and Safety Certificate for buildings completed 20 or more years ago, valid 10 years (under 40 years) or 5 years (40+), renewed in the last 90 days before expiry. Office treatment: the office takes this work only when the owner appoints it in writing as the engineering office and its Dubai licence, DM registration and classification match the building height (checked under QP-01); it then runs BBM-STD-75 §7 steps A1–A11: assessment against the DM technical checklist, technical report, Build in Dubai applications (QP-07, TRK-NOC), remediation supervision (QP-09, TRK-IR, TRK-NCR, TRK-SI, TRK-SUB) and records (QP-10). The office does not issue the Civil Defence or SIRA compliance certificates; the certificate is DM's decision. | https://dmpmedia.dm.gov.ae/uploads/2026/10/11-9-1.pdf; https://dmpmedia.dm.gov.ae/uploads/2026/10/11-9-1-1.pdf; both read in full 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-51 V0.4, BBM-STD-85 V0.3 | BBM-STD-51 §3 ED-SIRA; BBM-STD-85 §8 | ED-SIRA is no longer rule-based (replaces the ED-SIRA part of): the instrument is the SIRA Preventive Systems Manual approved by SIRA Administrative Resolution No. 13 of 2025 (issued 14 Apr 2025) under Law No. 12 of 2016 and its Implementing Bylaw (Resolution No. 1 of 2018). Security drawings follow the Manual chapter for the establishment type; the Security Plan Certificate is applied for on the SIRA e-services and stamped by a SIRA-licensed security consultancy and installation company, not by the office. Chapter and route re-checked at project start. | https://dlp.dubai.gov.ae/Legislation%20Reference/2025/Administrative%20Resolution%20No.%20%2813%29%20of%202025%20Approving%20the%20Preventive.html; https://www.sira.gov.ae/en/services/security-plans-certification; read 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-66 V0.3 | BBM-STD-66 §1.2, §1.3, §1.4 | Every CAD layer outside the grammar is mapped by rule, never left on Hold: name tokens first, then what the layer holds (dimensions, text, hatch, viewports, blocks, linework and its linetype), discipline from the name, else from the MasterFormat division of the folder (03, 05 1x S; 21 F; 22 P; 23, 25 M; 26-28 E; 31, 33+ C; 32 L; others A), status N unless the name says E, D or T. A layer that cannot be purged after a merge keeps its content under the BABOOM name with minor group LGCx. Layers outside the starter catalogue take the colour, linetype and lineweight of the catalogue row with the same groups and status, else the status D/E rule, else the minor-group rule (CUTT 1/0.50; TEXT, TTLB, SYMB, REFR 3/0.25; DIMS 4/0.18; PATT 5/0.13; HIDD 8 HIDDEN/0.18; CNTR 1 CENTER/0.13; NPLT 8/0.13; BLCK 2/0.25; other 3/0.25). The office detail library (425 drawings) is converted to these rules: 2,804 layers become 204 BABOOM layers, 204 of 204 follow the grammar; originals are kept in 03-DETAILS/98-ARCHIVE. Replaces the "Hold until status/representation is established" default of BBM-STD-66 V0.2 §1 for unmapped legacy layers. | Founder rule 2026-11-05: no decision is left waiting for a person; BBM-STD-66 V0.3; BABOOM CAD BBM_LAYERAUDIT and BBM_LAYERFIX (14-BBM-CAD); library rescan 2026-11-05 | Settlement 2026-11-05 | |
| BBM-STD-65 V0.3 | BBM-STD-65 §1, §2, §4.1 | ONE office Revit template for every discipline: BBM-GEN-TMP-R23-REV04 in 01-TEMPLATES/02-REVIT (architecture, structure, MEP, landscape, interiors). Discipline templates are retired (BBM-ARC-TMP-R23-REV03, BBM-MEP-TMP-R19-REV03, BBM-STR-TMP-R21-REV01 to 98-ARCHIVE). The template carries each discipline's settings (view templates and filters, browser organisation, object/line styles, line and fill patterns, MEP system, duct, pipe, cable tray and conduit types with segments and electrical types, structural rebar and cover types, shared parameters, schedules) and no loadable model family, detail component family, detail group or drafting-view detail: those come from the family and details libraries. It keeps annotation families (tags, symbols, title blocks) only; MEP fittings, profiles and railing parts are loaded by the ribbon (Load discipline kit) from the library, so the template holds zero loadable model families and zero details. | Founder decision 2026-11-05: the template is one for all disciplines; families and details already have their library, so they are not kept in the template | founder 2026-11-05 |