BBM-STD-51-REGISTERS-V0.4 | Office standard | 5 November 2026 | V0.4 | Private controlled WIP draft for office review and adoption
1 Purpose and control#
Use one controlled office register to select current standards, resolve dependencies, validate container identities and establish permission to use software, content and licensed publications. The BIM Manager maintains the register; the document controller checks references; the office director approves adoption within office powers. Project departures need the actual appointment authority. Actual holders and deputies remain in the restricted Directory.
This document closes the drafting scope of, and. It extends the existing glossary, Manual and BEP without changing issued baselines. The companion editable register contains blank input rows, a disk-derived current drafting inventory and a fictional SYN-P001 example. Inventory presence and a hash establish identity, not adoption. No office approval, entitlement or installed tool capability is asserted.
| Control | Required entry |
|---|---|
| Register identity | RegisterID, revision, custodian, restricted CDE URI and effective date |
| Adoption | Prepared, independently checked and director decision IDs; exact approved files and hashes |
| Review | At material standard, appointment, tool, authority, licence or incident change and the glossary's 12-month office review cycle |
| Change | Stable ChangeID, prior/new revision, impact, approval, notification and retest evidence |
2 One master index and dependencies#
Allocate each document or asset a stable ID before drafting. Record title, kind, revision, owner function, approval state, current master URI, issued-history URI, exact dependency IDs/revisions, next review date and evidence of approval. A companion form or native asset has a distinct AssetID linked to its parent standard. Markdown and DOCX are representations of the same controlled standard, not competing authorities. Record their source/build relationship and reconcile changes before issue.
All workbook file paths are relative to the office-rev root, one directory above xlsx; this base is stated on Read me. The workbook Master index is a baseline inventory of existing office standards, guides and their available companion assets at this drafting date. Standard IDs are BBM-STD-nn or BBM-STD-MIDP/TIDP, with the descriptive filename held separately. Companion AssetIDs have their own namespace and parent standard ID. A blank Next review date is an adoption hold, not a completed field. The Allocations table reserves 51, 55, 57, 52, 53, 54 and 56 for this queue. Planned entries have no current-release URI. Each new release is promoted into the index only after checking its actual pack, dependency revisions and decision. Do not label a proposed ID approved because the allocation exists.
| Dependency record | Validation |
|---|---|
| ConsumerID and revision | Exists exactly once in the master index for the selected baseline |
| RequiredID and revision | Resolves to an available current source or a retained explicitly pinned issued baseline |
| Applicability and reason | Identifies affected clause, asset, project or exchange |
| Impact and decision | Changed dependency triggers owner assessment, same ChangeID and notified consumers |
Library index snapshots. The shared family library index grows between reads, so every use quotes filename, row count, read date and full SHA-256. Recorded snapshots (read-only; owner of the index is the library-production owner, BBM-STD-69 §1 and BBM-STD-72 §2 cite these rows):
| Snapshot | File | Rows | Read / modified | SHA-256 | State |
|---|---|---|---|---|---|
| LIB-IDX-S1 | Family CSV, filename not recorded; no longer on the share | 568 | read 2026-10-16 | ccb2ced96efd2e3b91cfaf70a5279dcd9800ca5a583ba3d6d94f9bbef9ceb38b | History only |
| LIB-IDX-S2 | 02-LIBRARIES/01-FAMILIES/BBM-FAMILY-LIBRARY-INDEX.csv | 878 | read 2026-10-16 | 6d4ecac1310377706ce3937e98a64a5fc097f0d07784a617d450691cd5ae45a4 | Superseded snapshot |
| LIB-IDX-S3 | 02-LIBRARIES/01-FAMILIES/BBM-FAMILY-LIBRARY-INDEX.csv | 889 | read 2026-11-04; modified 2026-10-29 | 5b586168d9ff202f747b85bf14d0caaacbee48485bf24529aa5712d6cb504aaa | Current at 2026-11-04 |
Library and share paths in this standard are written in the NN-NAME folder form without dots. A share that still carries an earlier dotted folder name maps one-to-one to the path written here; the file name, row count and SHA-256 identify the file.
Before a release, traverse every applicable dependency and current link, including companion forms and diagrams. Check exact case/path, revision, actual availability, approval and permitted audience. Zero unresolved IDs or broken current references are permitted within the released scope. An unbuilt future interface is an open condition, never an active approved dependency. Preserve historic issued files and their references. A baseline snapshot is retained with its manifest and decision evidence.
3 Adopted publications and precedence: the one edition register#
Binding applicable law and authority conditions cannot be waived by a workbook or appointment. The commercial/legal owner records the actual appointment hierarchy; the technical team must not invent a universal order among contract documents. Within that agreed hierarchy, EIR fixes required exchanges, the BEP describes delivery and this office register controls the selected standards and aliases. Escalate conflicts and hold only the affected use.
This section is the ONE edition and adoption register for the whole office standard set. Every other document cites a register ID below instead of restating an edition or date. BBM-STD-12 A3 (CODE-nnn) and BBM-STD-57 §2 (InstrumentID) reference these IDs. UAE requirement detail (thresholds, submission steps, evidence) lives in BBM-STD-85; this register holds only the edition facts. Where a value could not be confirmed from a primary source, the row states the dependence-free rule instead of an edition. All rows checked 2026-11-04. Project code applicability, editions/amendments, transition dates, jurisdiction and verified clauses are frozen in the project copy of this register before technical reliance; the newest publication is not automatically the adopted code.
International and professional publications
| ID | Instrument | Edition / status | Date | Office treatment | Primary URL | Checked |
|---|---|---|---|---|---|---|
| ED-ISO19650-1 | ISO 19650-1 Concepts and principles | 2018, ed.1, in force. ISO/DIS 19650-1 ed.2 at stage 40.93, not in force | 2018-12 | Concepts baseline; a draft never replaces the edition automatically | https://www.iso.org/standard/68078.html | 2026-11-04 |
| ED-ISO19650-2 | ISO 19650-2 Delivery phase | 2018, ed.1, in force. ISO/DIS 19650-2 at stage 40.93, not in force | 2018-12 | Delivery baseline (BEP, MIDP/TIDP, formal delivery per 5.7) | https://www.iso.org/standard/68080.html | 2026-11-04 |
| ED-ISO19650-3 | ISO 19650-3 Operational phase | 2020, ed.1 | 2020-07 | Operational context (BBM-STD-52, 75) | https://www.iso.org/standard/75109.html | 2026-11-04 |
| ED-ISO19650-4 | ISO 19650-4 Information exchange | 2022, ed.1 | 2022-08 | Exchange review and acceptance (BBM-STD-50, 54, 64) | https://www.iso.org/standard/78246.html | 2026-11-04 |
| ED-ISO19650-5 | ISO 19650-5 Security-minded approach | 2020, ed.1, confirmed 2025 | 2020-06 | Security triage and plan in BBM-STD-87 | https://www.iso.org/standard/74206.html | 2026-11-04 |
| ED-ISO19650-6 | ISO 19650-6 Health and safety information | 2025, ed.1 (replaces PAS 1192-6) | 2025-01-13 | H&S information in BBM-STD-88 | https://www.iso.org/standard/82705.html | 2026-11-04 |
| ED-ISO7817-1 | ISO 7817-1 Level of information need | 2024, ed.1 (replaces EN 17412-1:2020) | 2024-06-20 | LOIN baseline (Glossary 1.3, BEP 6.5, BBM-STD-54, 89) | https://www.iso.org/standard/82914.html | 2026-11-04 |
| ED-EN17412-1 | BS EN 17412-1:2020 | Withdrawn; replaced by ISO 7817-1:2024 | 2020 | Keep only a contracted reference, with a successor mapping to ED-ISO7817-1 | https://standardsdevelopment.bsigroup.com/projects/2018-02659 | 2026-11-04 |
| ED-ISO16739-1 | ISO 16739-1 IFC | 2024, ed.2 = IFC 4.3.2.0 | 2024-03-22 | Office default exchange schema stays IFC 4.0.2.1 (IFC4 ADD2 TC1) Reference View; IFC 4.3.2.0 by recorded approval after a passing test exchange; IFC2x3 only when an appointment or authority profile requires it | https://www.iso.org/standard/84123.html | 2026-11-04 |
| ED-IDS | buildingSMART Information Delivery Specification | IDS 1.0 final | June 2024 | Machine-readable alphanumeric LOIN checks (BBM-STD-54 §4.1, BBM-STD-89) | https://github.com/buildingSMART/IDS/releases | 2026-11-04 |
| ED-BCF | buildingSMART BIM Collaboration Format | BCF 3.0 final (bcfXML and BCF-API); BCF 2.1 (2017) fallback | 2021-06-18 | bcfXML 3.0 default; API after endpoint qualification; 2.1 via recorded field map (BBM-STD-50) | https://github.com/buildingSMART/BCF-XML/releases/tag/v3.0 | 2026-11-04 |
| ED-IFC-VALIDATION | buildingSMART IFC Validation Service | Live service | live | Schema/specification conformance before IDS and clash runs | https://technical.buildingsmart.org/services/validation-service/ | 2026-11-04 |
| ED-ISO12006-2 | ISO 12006-2 Classification framework | 2015, ed.2, last reviewed and confirmed 2020; stage 90.92 to be revised, ISO/DIS 12006-2.2 under development | 2015 | Classification framework behind Uniclass (BBM-STD-72) | https://www.iso.org/standard/61753.html | 2026-11-05 |
| ED-ISO12006-3 | ISO 12006-3 Object-oriented information | 2022, ed.2 | 2022-07-15 | Data dictionary framework (bSDD) | https://www.iso.org/standard/74932.html | 2026-11-04 |
| ED-ISO23386 | ISO 23386 Property definition | 2020, ed.1, confirmed 2025 | 2020-03 | Property definition attributes (BBM-STD-52, 54, 72) | https://www.iso.org/standard/75401.html | 2026-11-04 |
| ED-ISO23387 | ISO 23387 Data templates | 2025, ed.2 | 2025-09-22 | Data templates (BBM-STD-52, 54, 72) | https://www.iso.org/standard/85391.html | 2026-11-04 |
| ED-ISO21597 | ISO 21597-1 and -2 Information container for linked document delivery | 2020 (both); -2 confirmed | 2020-11 | Linked-container exchange where an appointment requires it | https://www.iso.org/standard/74389.html; https://www.iso.org/standard/74390.html | 2026-11-04 |
| ED-ISO29481 | ISO 29481 Information delivery manual | -1:2025 ed.3; -2:2025 ed.2; -3:2022 | 2025 / 2022-09 | IDM method for exchange definitions (BBM-STD-74) | https://www.iso.org/standard/88515.html; https://www.iso.org/standard/81261.html | 2026-11-04 |
| ED-UNICLASS | Uniclass 2015 (NBS) | July 2026 release: Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27 | 2026-07 | Classification_Code + ClassificationTable/Title/Release; cite the release used | https://uniclass.thenbs.com/download | 2026-11-04 |
| ED-RIBA-POW | RIBA Plan of Work | 2020 (current) | 2020 | Stage names | https://www.riba.org/work/insights-and-resources/riba-plan-of-work/ | 2026-11-04 |
| ED-ISO13567 | ISO 13567-1 and -2 CAD layers | 2017, ed.2 (both), confirmed | 2017-09 | CAD layer structure (BBM-STD-66) | https://www.iso.org/standard/70181.html; https://www.iso.org/standard/70182.html | 2026-11-04 |
| ED-ISO128-1 | ISO 128-1 TPD general principles of representation | 2020, ed.2 | 2020-05 | Drawing principles (BBM-STD-67) | https://www.iso.org/search.html?q=ISO%20128-1 | 2026-11-04 |
| ED-ISO7200 | ISO 7200 Title blocks and document headers | 2004, ed.2, confirmed 2025 | 2004-02 | Title-block fields (BBM-STD-67) | https://www.iso.org/standard/35446.html | 2026-11-04 |
| ED-ISO5457 | ISO 5457 Sizes and layout of drawing sheets | 1999 + Amd 1:2010; confirmed 2021 | 1999 / 2010-06 | Sheet margins and layout (BBM-STD-67) | https://www.iso.org/standard/29017.html; https://www.iso.org/standard/46218.html | 2026-11-04 |
| ED-ISO216 | ISO 216 Paper sizes A and B series | 2007; confirmed 2021 | 2007 | Sheet sizes (BBM-STD-67) | https://www.iso.org/standard/36631.html | 2026-11-04 |
| ED-ISO10005 | ISO 10005 Quality plans | 2018, ed.3; confirmed 2023 | 2018-06 | Quality plan structure (BBM-STD-68; office QMS BBM-STD-96, 97 QP-02) | https://www.iso.org/standard/70398.html | 2026-11-04 |
| ED-ISO19011 | ISO 19011 Auditing management systems | ISO 19011:2026, edition 4, published May 2026 (stage 60.60); ISO 19011:2018 withdrawn 27 May 2026 | 2026-05 | Auditor competence and independence, audit programme guidance (BBM-STD-68; BBM-STD-96 §9.2 and §11; BBM-STD-97 QP-13) | https://www.iso.org/standard/19011 | 2026-11-05 |
| ED-ISO10006 | ISO 10006 Quality management in projects | 2017; confirmed 2023 | 2017 | Project quality plans (BBM-STD-96 §8, BBM-STD-97 QP-02) | https://www.iso.org/standard/70376.html | 2026-11-04 |
| ED-ISO10002 | ISO 10002 Complaints handling | 2018, ed. 3 (published 2018-07-16; confirmed 2023-12-11, stage 90.93) | 2018-07 | Complaints (BBM-STD-97 QP-12) | https://www.iso.org/standard/71580.html | 2026-11-04 |
| ED-ISO10004 | ISO 10004 Customer satisfaction: monitoring and measuring (ed.2, confirmed 2023, stage 90.93) | 2018 | 2018-07 | Client feedback and satisfaction KPIs (BBM-STD-97, BBM-STD-98) | https://www.iso.org/standard/71582.html | 2026-11-04 |
| ED-LEED | USGBC LEED | Version per project registration | per project | Client-targeted rating only (BBM-STD-97 QP-06) | https://www.usgbc.org/leed | 2026-11-04 |
| ED-ISO9001 | ISO 9001 Quality management systems | 2026, ed.6 (replaces 9001:2015 + Amd 1:2024) | 2026-09-16 | Office QMS (BBM-STD-96, 97, 98) and QMS interface (BBM-STD-68); certificates to 2015 follow the certification body's transition period | https://www.iso.org/standard/88464.html | 2026-11-04 |
| ED-ISO27001 | ISO/IEC 27001 Information security management | 2022, ed.3 + Amd 1:2024 | 2022-10 / 2024 | CDE/service-provider security evidence (BBM-STD-56, 87) | https://www.iso.org/standard/82875.html | 2026-11-04 |
| ED-ISO42001 | ISO/IEC 42001 AI management system | 2023, ed.1 | 2023-12 | AI governance (BBM-STD-92) | https://www.iso.org/standard/42001 | 2026-11-04 |
| ED-ISO55001 | ISO 55001 Asset management systems | 2024, ed.2 (2014 withdrawn) | 2024-07 | Asset-management interface (BBM-STD-02, 75) | https://www.iso.org/standard/83054.html | 2026-11-04 |
| ED-ISO22057 | ISO 22057 EPD data templates for BIM; RICS WLCA | ISO 22057:2022 (under revision); RICS whole life carbon assessment 2nd ed. effective 1 Jul 2024 | 2022 / 2024-07-01 | Carbon data (BBM-STD-81) | https://www.iso.org/standard/72463.html | 2026-11-04 |
| ED-PAS1958 | PAS 1958 Built environment data and information standards landscape. Guide | PAS 1958:2026, current | 2026-03-31 | Data/AI readiness reference (BBM-STD-92) | https://knowledge.bsigroup.com/search?query=PAS%201958 | 2026-11-04 |
| ED-COBIE | COBie (NIBS NBIMS-US) | COBie 2.4 (NBIMS-US V3, 2015) default; COBie V3.0 published 2023 as part of NBIMS-US V4 (NIBS version history) | — | Delivered when the EIR requires; version as the EIR specifies; default COBie 2.4 unless the EIR names v3 | https://nibs.org/nbims/v4/resources/; https://nibs.org/nbims/v3/cobie/2-7 | 2026-11-05 |
| ED-IMI | IMI Framework (formerly UK BIM Framework, renamed May 2025) guidance | Guidance Parts A–F archived (A/D/E ed.2 Feb 2021 retained as archived explanatory editions) | 2025-05 | Explanatory only; not UAE statute | https://ukbimframework.org/resources/ | 2026-11-04 |
| ED-INFO-PROTOCOL | IMI Framework Information Protocol template for BS EN ISO 19650-2 | Template Ed 6 for new appointments; protocol guidance ed.3 (Aug 2022) | 2022 / live | Protocol baseline for BBM-STD-56; the one dated entry all docs cite | https://ukbimframework.org/resources/ | 2026-11-04 |
| ED-CIC-PROTOCOL | CIC BIM Protocol | 2nd ed. 2018, legacy (PAS 1192 era) | 2018 | Do not use for new appointments | https://www.cic.org.uk/shop/cic-bim-protocol-2nd-edition | 2026-11-04 |
| ED-BS1192 | BS 1192 / PAS 1192 family; BS 8536 | WITHDRAWN: BS 1192:2007+A2:2016 16 Jan 2019; PAS 1192-2 18 Jan 2019; PAS 1192-3 18 Aug 2020; PAS 1192-5 1 Jul 2020; BS 1192-4 16 Sep 2022; PAS 1192-6 23 Jan 2025. BS 8536:2022 supersedes BS 8536-1/-2 | as listed | Successors ISO 19650-1/-2/-3/-5/-6. Legacy mapping only through §3.1; never cited as current | https://knowledge.bsigroup.com/products/specification-for-information-management-for-the-capital-delivery-phase-of-construction-projects-using-building-information-modelling | 2026-11-04 |
| ED-REVIT | Autodesk Revit supported releases and IFC exporter | Supported 2024, 2025, 2026, 2027; 2023 out of Autodesk support (legacy, existing projects only with risk acceptance and upgrade plan); latest update 2027.3; IFC exporter 27.4.0.30 exports IFC4x3 | 2026-09-15 / 2026-10-30 | Matrix in BBM-STD-91; IFC 4.3 RV only after a test export from the project build passes the project IDS | https://www.autodesk.com/support/account/manage/versions/previous-versions; https://github.com/Autodesk/revit-ifc/releases | 2026-11-04 |
UAE instruments (requirement detail in BBM-STD-85; jurisdiction applicability per project through BBM-STD-57 and the BoD). There is no UAE federal BIM mandate, and no universal Abu Dhabi building-permit BIM threshold was found.
| ID | Instrument | Edition / status | Date | Office treatment | Primary URL | Checked |
|---|---|---|---|---|---|---|
| ED-DM-196-207 | DM BIM circulars 196 (2013) and 207 (2015) | Earlier circulars, cited by circular 9-1-2 | 2013 / 2015 | Historical context only | https://dmpmedia.dm.gov.ae/uploads/2023/10/تعميم-BIM-9-1-2.pdf | 2026-11-04 |
| ED-DM-CIRC-INDEX | DM Building and Planning Circulars index | Live official index (no dates per entry); the single DM circular index URL used by BBM-STD-57, 61 and 67 | live | Watch source for new DM circulars (BBM-STD-57 §6) | https://www.dm.gov.ae/building-planning-circulars-2/ | 2026-11-04 |
| ED-DM-9-1-1 | DM circular 9-1-1 of 2021 on applying BIM | Dated 23 Aug 2021. BIM for architectural and mechanical works: over 20 floors; over 200,000 sq ft; specialised buildings (hospitals, universities and the like); all government projects; all projects by a foreign office subsidiary. BIM for structural works: over 40 floors; over 300,000 sq ft; specialised buildings; buildings by a foreign office subsidiary | 2021-08-23 | 2021 BIM-use scope; permit submission scope is 9-1-2 / 9-1-3; follow the widest scope that applies | https://dmpmedia.dm.gov.ae/uploads/2024/11/9-1-1-Application-of-Buildings-Information-Modelling.pdf | 2026-11-05 |
| ED-DM-9-1-2 | DM circular 9-1-2 BIM with new building permits | Open BIM submission per the Dubai BIM Standard from 1 Jan 2024: over 20 floors (ARC) / 40 floors (STR); over 20,000 m² (ARC) / 30,000 m² (STR); specialised buildings (hospitals, universities); government projects except utility projects | 2023-10-13 | Permit BIM route in BBM-STD-57 §3 / BBM-STD-85 | https://dmpmedia.dm.gov.ae/uploads/2023/10/تعميم-BIM-9-1-2.pdf | 2026-11-04 |
| ED-DM-9-1-3 | DM circular 9-1-3 BIM with building permits | From 1 Apr 2026: ARC + STR BIM with the permit for new buildings above G+12 or 15,000 m² or more; listed alterations (add/remove floors, +1,500 m² or more, full redesign, change of main use, relocation on plot) with the application; other alterations: final BIM before the completion certificate; drawings extracted from the model | 2026-01-15; effective 2026-04-01 | Permit BIM route in BBM-STD-57 §3 / BBM-STD-85 | https://www.dm.gov.ae/wp-content/uploads/2026/02/Circular-9-1-3.pdf | 2026-11-04 |
| ED-DUBAI-BIM-STD | Dubai BIM Standard and Model Attribute Matrix | Version 1.4 (changelog 8 Jun 2026): IFC4 schema,.ifc files (§6.1.1); authority Revit setup "Dubai BIM E-Submission (IFC4)Reference View"; Appendix B Model Attribute Matrix issued with 1.4 (file 5 Jun 2026, no separate version number; BIMStandardVersion = 1.4.0); Appendix A Model Element Matrix; Appendix C Usage Codes; DM IDS DMBIM_IDS_V1; CRS EPSG:3997 with DMD elevations; ZIP within the platform maximum (150 MB per changelog); package re-read 2026-11-05 (server date 2 Nov 2026): still Version 1.4.0 | 2026-06-08 | Office preset EXP-DM-PERMIT-IFC4-<rev> built on the authority setup; re-checked at project start and before each submission (BBM-STD-85 §9) | https://buildindubai.gov.ae/bim; https://api.buildindubai.gov.ae/assets/BIM/Documents/DubaiBIMStandards.zip | 2026-11-05 |
| ED-DBC | Dubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 | Apply the DBC plus all DM amending resolutions in force at permit submission. AR 225/2024 (issued 16 Jul 2024, published 13 Aug 2024, in force 30 days later) applies to plots of 250 m² or less only and permits seven parameter changes: no lifts for G+2 or lower with 100 occupants or fewer; ground-floor lift lobby 1.8 m; typical-floor corridor and lift lobby 1.5 m; one shared WC per shop of 100 m² or less; no bulky-waste area; no recycling area in the refuse room; no extra 300 mm bay width beside columns/walls | 2021 / 2024-08-13 | Design basis (BBM-STD-12, 57, 85); DBC clause per AR 225 item recorded at project start | https://www.dm.gov.ae/municipality-business/laws-and-orders/; https://dmpmedia.dm.gov.ae/uploads/2024/08/قرار-إداري-رقم-225-لسنة-2004.pdf | 2026-11-05 |
| ED-DXB-LAW-3-2026 | Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (emirate law) | Issued 27 Feb 2026; Official Gazette issue 764, 12 Mar 2026; in force 60 days after publication, i.e. from 11 May 2026; Quality & Safety Certificate after 20 years from completion, valid 10 years (5 years if 40+ years); applied by DM circular 11-9-1 of 2026 (ED-DM-11-9-1) | 2026-02-27 | Asset-life obligation for existing buildings (BBM-STD-75, 76, 85); not a design-permit rule | https://dlp.dubai.gov.ae/Legislation%20Reference/2026/Law%20No.%20%283%29%20of%202026%20Concerning%20the%20Quality%20and%20Safety%20of%20Buildings.html | 2026-11-04 |
| ED-DM-11-9-1 | DM circular (11-9-1) of 2026 applying Law No. 3 of 2026 (parent row ED-DXB-LAW-3-2026), with the guidance manual "Building Quality and Safety Certificate" (attachment 11-9-1-1, May 2026) | Dated 1 Oct 2026, applies from that date: owners of buildings completed 20 or more years ago obtain a Building Quality and Safety Certificate after a technical assessment against the DM technical checklist and remediation of any defects found; valid 10 years (under 40 years since completion) or 5 years (40 years or more), renewed in the last 90 days before expiry by the same procedure; phased, first multi-storey buildings over 40 years old, each owner on DM notice with a deadline; the owner appoints an engineering office licensed in Dubai whose classification matches the building height; applications on the Build in Dubai e-service; Civil Defence and SIRA compliance certificates mandatory | 2026-10-01 | Existing-building assessment service: BBM-STD-75 §7, BBM-STD-85 §4 and §11; the office acts only as the appointed engineering office | 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 | 2026-11-05 |
| ED-UAE-FLS | UAE Fire & Life Safety Code of Practice | September 2018 edition; emirate amendments (rule-based): the edition plus the emirate Civil Defence amendments current at project start, checked on the emirate Civil Defence code page and circulars, recorded in BEP §1.12. Abu Dhabi: ADCDA Circular No. 3 of 2026 (12 Mar 2026, 54 decisions amending the 2018 edition) and an ADCDA smoke-management duct circular are reported by secondary sources only; neither was found on adcda.gov.ae on 2026-11-05, so they apply only from the ADCDA text obtained at project start | 2018-09 | Fire basis; Fire_Rating per | https://www.dcd.gov.ae/portal/preventive-safety/uae-fire-and-life-safety-code-of-practice.jsp; https://www.adcda.gov.ae/ | 2026-11-05 |
| ED-ADIBC | Abu Dhabi International Building Codes | The ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-05; Executive Council Resolution 7C 26/2013, effective 1 Oct 2013); a later edition is rule-based: checked on the DMT codes page at project start | 2013 | Abu Dhabi design basis | https://www.dmt.gov.ae/-/media/Project/DMT/DMT/Codes/3-ADIMC-2013_1-12-2013.pdf | 2026-11-04 |
| ED-ADC9-2026 | Abu Dhabi UPPC Circular No. 9 of 2026, supervision consultant and contractor roles | Issued 2026-10-14 | 2026-10-14 | Supervision roles, phase notices and joint phase reports (BBM-STD-97 QP-09) | https://www.Project.ae/en/article/c2qm3pn-uppc-issues-circular-streamline-construction | 2026-11-04 |
| ED-DDA-CIRC-400 | DDA Circular 400: Drawings Submission Standards | Dated 29 Sep 2021: A1 DWF drawings, monochrome except perspectives and shaded area diagrams, discipline tabs and sheet naming; the current Final Design Approval service checklist governs where it differs | 2021-09-29 | DDA drawing submissions (BBM-STD-57 §3, BBM-STD-61, BBM-STD-67) | https://dda.gov.ae/-/media/436DDFA50D8B4AC1A075607917327616.pdf | 2026-11-04 |
| ED-AUH-PLANNING | Abu Dhabi planning and area-definition regulations | Abu Dhabi Capital Development Code (DMT) for plots in Abu Dhabi City Municipality; Al Ain and Project: the DMT development code of that municipality, title and edition recorded at project start | 2022 | Area definitions (BBM-STD-58 §3.1) | https://www.dmt.gov.ae/-/media/Project/DMT/DMT/E-Library/Abu-Dhabi-Capital-Development-Code.pdf | 2026-11-05 |
| ED-UTILITY-REGS | Utility authority regulations (Dubai DEWA; Abu Dhabi utility) | Dubai: DEWA Regulations for Electrical Installations, 2017 Edition. Abu Dhabi: Abu Dhabi Emirate Guideline for Infrastructure Services Standards, 2nd edition, January 2017 (index of ADDC / RSB water and electricity codes). Other utilities (district cooling, gas, telecom): the provider's current regulation recorded at project start | 2017 / 2017-01 | MEP design basis, utility separations and NOCs (BBM-STD-50 §4.1, BBM-STD-57 §3, BBM-STD-60 §3) | 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 | 2026-11-05 |
| ED-ADM-BIM | ADM BIM Code of Practice; Infrastructure Documentation Guidelines; Infrastructure BIM Object Catalogue | CoP Oct 2020 (cover v1, headers v1.1); Guidelines v1.0 Oct 2020; Object Catalogue v2.0 May 2021 | 2020–2021 | Abu Dhabi BIM context; infrastructure scope | https://www.dmt.gov.ae/adm/-/media/Project/DMT/ADM/E-Library/0001-Jan-2022-Doc/ADM-BIM-005Code-of-Practice.pdf | 2026-11-04 |
| ED-ESTIDAMA | Estidama Pearl Rating System | Private projects minimum 1 Pearl; government-funded minimum 2 Pearl | 2025-01-08 | Statutory minimum (BBM-STD-57, 81, 85) | https://www.dmt.gov.ae/en/adm/Media-Centre/News/08Jan2025 | 2026-11-04 |
| ED-ALSAFAT | Al Sa'fat Dubai Green Building System | 2nd edition: Silver Sa'fa mandatory for all new buildings in Dubai | 2023-01 | Statutory minimum (BBM-STD-57, 81, 85) | https://www.dm.gov.ae/municipality-business/al-safat-dubai-green-building-system/ | 2026-11-04 |
| ED-UAE-PDPL | Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data | Active; executive regulations as listed on uaelegislation.gov.ae at project start | effective 2022-01-02 | Personal data (BBM-STD-03, 90) | https://uaelegislation.gov.ae/en/legislations/1972 | 2026-11-04 |
| ED-UAE-CTL | Federal Decree-Law No. 25 of 2025 (Civil Transactions Law) | Decennial liability Art. 821 (engineer and contractor jointly, 10 years from delivery); Art. 823 bars exemption clauses; Art. 824 three-year claim period. Contracts signed before 1 Jun 2026: Federal Law 5/1985 Art. 880. Corrigendum in the annex of Official Gazette No. 821 (14 Apr 2026) checked: the text as corrected lists no change to Art. 821–824, and the official Art. 821, 823 and 824 read as quoted here (read 2026-11-05) | effective 2026-06-01 | Retention minimum 10 years after handover + 3 years; final schedule ruled by the legal owner (BBM-STD-90) | https://uaelegislation.gov.ae/en/legislations/4011; https://www.lexismiddleeast.com/gazette/UnitedArabEmirates/2026_821_Annex/en | 2026-11-05 |
| ED-SIRA | Dubai SIRA security-system requirements | Law No. 12 of 2016 regulating the security industry in Dubai and its Implementing Bylaw (Resolution No. 1 of 2018); SIRA Administrative Resolution No. 13 of 2025 approving the Preventive Systems Manual (issued 14 Apr 2025, in force on Official Gazette publication): camera views, ANPR, access control, guards and system health monitoring per establishment type; Security Plan Certificate (SPC) and Security System Certification e-services | 2025-04-14 | Security-system drawings follow the Manual chapter for the establishment type; the SPC is stamped by a SIRA-licensed security consultancy and installer, not by the office; classified per BBM-STD-87; SIRA compliance certificate needed for ED-DM-11-9-1 | 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 | 2026-11-05 |
| ED-UAE-CRS | Project coordinate reference systems (CRS register keys CRS-DXB, CRS-AUH, CRS-OTH in BBM-STD-86 §2) | Dubai: DLTM, EPSG:3997 "WGS 84 / Dubai Local TM", required by the Dubai BIM Standard 1.4 §4.1.2; WGS 84 based, so no datum transformation for WGS 84 data; vertical DMD (Port Rashid datum, no EPSG code). Abu Dhabi: WGS 84 (ITRF2000) / UTM 40N EPSG:32640 east of 54°E, UTM 39N EPSG:32639 west of 54°E; vertical Ras Ghumays, EPSG:5843 | 2026-06-08 / 2023-02 | Register and procedure in BBM-STD-86; zone chosen from the plot, never one emirate-wide code | https://epsg.io/3997; https://admobility.gov.ae/services/-/media/As-Built-Data-Submission-Standards.pdf; https://epsg.io/5843 | 2026-11-05 |
| ED-UAE-NATIONAL | UAE federal BIM mandate | None found; MoEI green building codes (2022) noted | 2022 | No federal BIM rule is assumed | https://www.Project.ae/en/details/1395303033593 | 2026-11-04 |
For every adoption record retain publisher/source URL, standard identifier, edition, published/draft/withdrawn status, national adoption, jurisdiction, applicable clauses, contractual incorporation, verification date, licensed access route and approving function. Licensed texts remain in their controlled permitted store. No copied paid-standard paragraphs or licence keys belong here.
ISO clause pointers are paraphrased reading directions: ISO 19650-1 clause 5 concerns requirements; ISO 19650-2 clauses 5.1.4 and 5.1.5 concern the project's information standard and production methods. Check the licensed publication before a formal compliance assertion. Public catalogue pages prove scope and edition only.
3.1 Legacy transition worksheet#
The following is an office mapping method for BS 1192-era project records, not a reproduced BS code table. Compare the actual historical project standard and signed appointment before adopting a mapping. Preserve every issued literal and its original meaning.
| Legacy component or record | Current treatment | Approval or unsupported condition |
|---|---|---|
| Project; originator | PROJ; ORG | Verify allocated project/organisation codes; CLIENT is an additional office token, not a claimed BS requirement |
| Volume or system; level or location | VOLUME; LEVEL | Confirm scope and granularity; no inferred ZZ for an unknown division |
| Type; role; number | TYPE; ROLE; NUMBER | Validate code meanings and number namespace; use a controlled alias where meanings differ |
| Legacy suitability/status literal | Preserve old literal and meaning; map to one SU value only after use/recipient review | A similar-looking S code is not an automatic ISO/SU equivalent. Unknown meaning holds the affected use |
| Legacy revision literal | Retain issued literal; use an explicit old-to-new revision map for future issues | Rnn continues where already adopted; other series need the appointment authority's decision, never an arithmetic conversion |
| Internal ORG-PROJ-DISC-PHASE-SEQUENCE | Mapped internal WIP alias only, linked to one eight-token external identity; never issued | Trade maps to role through BBM-STD-93; the PHASE token is retired (stage is permitted-use metadata); multi-token descriptors require registered handling |
The workbook Legacy map records the old literal, current meaning, applicability, ChangeID, approver, effective revision and retained-history URI. For the synthetic example, LEG-SYN-COORD is explicitly defined as coordination in its fictitious project standard and maps to SU-COORD. It is not represented as a BS 1192 code. Review and notify all affected CAD, Revit and CDE users before the next applicable exchange.
4 Shared naming and metadata register#
Retain O3-POL-01 in Clash Matrix section 2 and BEP 8.3 as the existing policy authority. This table implements that decision, rather than establishing another grammar. Register one appointment mapping when the recipient requires different tokens or codes. The eight-token external identity is CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext. Tokens are uppercase, separated by single hyphens; NUMBER has four digits; the approved extension is lowercase. Revision and suitability are metadata.
Code values live in one place: BBM-STD-93 Code dictionary. This section keeps only the token order and validation rules. Short summary for orientation; BBM-STD-93 governs where they differ:
| Token / metadata | Rule (values in BBM-STD-93) |
|---|---|
| CLIENT / ORG / PROJ | Allocated project lists; fictional example CLI / OFF / P001, never a client identity |
| VOLUME / LEVEL | Registered zone and level codes; ZZ only where whole scope is explicitly adopted; never omit a token |
| TYPE | Registered container type codes (e.g. M3 model, DR drawing) |
| ROLE | One-letter ROLE from BBM-STD-93 (A, S, M, E, L, P, F, I, C, G, Q, W, Z). A trade alias is not a role code |
| NUMBER | Four digits, unique in the recorded numbering namespace |
| Extension | Lowercase; same-stem variants map to one logical container and declared source revision |
| Revision | R00 initial WIP, then R01, R02…, expanding beyond R99; per container, never recycled; unchanged containers keep their revision |
| Suitability | SU-WIP, SU-COORD, SU-INFO, SU-REVIEW, SU-ISSUE only; mapping to UK National Annex S0–S7/A/B/CR in BBM-STD-93 |
| CDE state | WIP, Shared, Published, Archive. Distinct from workspace WIP/PRODUCTION/DEPLOYED folders |
| Release evidence | Exact identity/revision, source/export manifest, permitted use, author/checker/authoriser, recipients and separate receiving decision |
These SU codes are local. They are not ISO/national-annex suitability codes, issue severities or RACI letters. SU-ISSUE does not prove statutory approval or recipient acceptance. An.ifc extension does not mean issued for construction.
CAD, Revit and CDE use the same external register. Retain internal view names DISC-LEVEL[-ZONE]-TYPE-DESC (3-letter discipline code from BBM-STD-93), sheet numbers DISC-CAT-INDEX (1-letter ROLE prefix from BBM-STD-93) and the registered STD00-STARTING-VIEW exception under Manual 12.3/BEP 8.3. Preserve approved legacy WIP aliases through a one-to-one alias-to-external-ID map. Never rename issued records to clean up a convention.
4.1 Validation fixtures#
The workbook Test pack specifies positive and adverse cases for a future CAD/Revit/CDE validation implementation. Expected outcomes below are test specifications, not executed host evidence.
| Case | Input | Expected result and reason |
|---|---|---|
| N01 | CLI-OFF-P001-Z01-L01-M3-A-0001.ifc | Accept syntax and dictionary membership when manifest/revision/permission checks also pass |
| N02 | CLI-OFF-P001-Z01-M3-A-0001.ifc | Reject missing LEVEL; no token shift |
| N03 | CLI-OFF-P001-Z01-L01-M3-A-001.ifc | Reject sequence width |
| N04 | CLI-OFF-P001-Z01-L01-M3-A-0001-R01.ifc | Reject revision embedded in external identity |
| N05 | CLI-OFF-P001-Z99-L01-M3-A-0001.ifc | Reject unregistered volume even when a regex matches |
| N06 | Same container and revision, conflicting payload hashes | Reject unrecorded overwrite; investigate source/history |
| N07 | Same stem.rvt and.ifc, same manifest source | Permit declared representations; still test schema and receiver |
| N08 | Revision R02 followed by R01 as new issue | Reject regression unless expressly retrieving retained historical evidence |
| N09 | SU-COORD requested for fabrication | Hold incompatible intended use; naming alone cannot authorise it |
| D01 | Consumer points to an absent dependency ID | Reject release until allocation/source is resolved |
| D02 | Consumer pins old issue, master now newer | Preserve issued pin; assess migration rather than silently upgrade |
A validator checks lexical syntax, code dictionaries, identity/representation uniqueness, metadata, revision history, dependency resolution and intended-use authority separately. Regex alone is insufficient. A future implementation must run every case in all affected tools and record exact versions and actual outputs before claiming enforcement.
5 Rights and licensed access#
The licence and credential register itself is owned by BBM-STD-94; this section states the office rule only. The rights steward records EntitlementID, holder function/account reference, product/content/publication, provider and licence instrument/version, covered installations/users, authorised uses/recipients, expiry/renewal/review dates, evidence URI and restrictions. Store credentials only in the approved credential store. The register contains a non-secret reference, never a password, key, token or activation code.
Software permission, ability to open a file, third-party content redistribution rights and access to a paid standard are different checks. Record each separately. A valid software seat does not authorise redistribution of a family library, a standards PDF or model IP. Apply ISO 19650-5:2020 security context proportionately. Actual licence particulars follow the signed instrument, not this template.
| Fictional record | Permission decision |
|---|---|
| ENT-, modelling software | Internal named-user use only; renewal and installation evidence pending. No actual vendor entitlement asserted |
| ENT-, external content | Internal evaluation only; no client or public redistribution until rights owner clears the exact item |
| ENT-, standards access | Licensed-reader access at controlled portal; citation allowed within terms; do not redistribute the full publication |
On expiry, revoked access, changed recipients or changed terms, the steward alerts the owner and holds the affected new use. Retention and retrieval of existing records follow the actual instrument and records/legal owner, not assumed immediate deletion.
6 Reference reconciliation and controlled migration#
The current guide headers cite Manual V0.1 and BEP V0.2 while the current controlled drafts are Manual V0.5 and BEP V0.5; Manual V0.2/V0.3 and BEP V0.3/V0.4 are historical baselines. Do not bulk-rewrite other lanes' guides or issued project packs. The Migration table records each actually observed stale guide reference, its source line, proposed current target, exact dependency revision, affected steps, responsible guide owner, compatibility review, approval and effective revision. The row state remains Pending owner revision; the old reference is resolved as a historical baseline and the proposed target is a current draft, not an approved migration. Current draft paths must resolve; historical citations remain visibly historical until that owner's controlled revision is adopted.
A second conflict is retained Manual 12.3 wording that appears to prescribe the legacy five-token external filename. BEP 8.3, O3-POL-01 and settle this: legacy internal alias only, never issued; external eight-token identity; PHASE token retired. Record W1-C01 in the office decisions log and carry this interpretation in the project naming annex. Do not silently edit the source Manual.
Migration sequence: identify affected references; compare meanings; verify target availability/rights; obtain the controlling decision; revise the owner's draft and linked plans using one ChangeID; independently retest; notify recipients and retain the prior issue. If the newer document is still a draft, do not imply office adoption. BBM-STD-72/75/76 V0.1 are draft dependencies: index them in the Master index with draft state (BBM-STD-72, BBM-STD-75, BBM-STD-76 at their current draft revision); consumers pin the draft revision until adoption.
7 Acceptance and activation#
| Check | Evidence required |
|---|---|
| Index and dependency integrity | Every current ID unique, all required pinned revisions accessible, zero unresolved current references and a dated manifest |
| Naming and representations | Test pack actual outputs, code-register revision, alias map, revision/suitability/state and manifest checks |
| Rights | In-date evidence for actual use, account/seat allocation and every intended recipient; no credentials in the register |
| Migration | Impact, authority, effective revision, notification and independent retest; issued originals preserved |
| Adoption | Director/appointment decisions and actual authorised custodians. Draft review is not project mobilisation |
The present pack supplies the method, editable forms and filled examples. Native CAD/Revit/CDE validation, real entitlements, office adoption and project receiving tests are NOT EXECUTED. Activate only the actual affected uses after their records and evidence are complete.
References#
- R1. ISO, ISO 19650-1:2018 catalogue and ISO 19650-2:2018 catalogue. Requirements clause 5 and delivery 5.1.4–5.1.5 are reading pointers, not a licensed compliance audit. Checked 2026-11-04.
- R2. ISO, ISO 19650-3:2020 catalogue and ISO 19650-5:2020 catalogue. Operational and security scope. Checked 2026-11-04.
- R3. ISO, ISO 7817-1:2024 catalogue; BSI BS EN 17412-1:2020 project record, withdrawn predecessor. Checked 2026-11-04.
- R4. IMI Framework (formerly UK BIM Framework, renamed May 2025), resources: archived Guidance A edition 2, Guidance D edition 2 and Guidance E edition 2, February 2021; Information Protocol template Ed 6. Explanatory context only. Checked 2026-11-04.
- R5. Local controlling drafts: Glossary V0.3, Manual V0.5, BEP V0.5, Code dictionary, UAE authority annex, office decisions, writing plan and gap matrix. Access date 4 November 2026.
- R6. Every edition and URL in the §3 register tables is a primary source checked 2026-11-04; those rows are the reference list for the edition facts.
- R7. Standard watch no. 1 (2026-11-05): ISO 19011:2026; DM circular 11-9-1 of 2026 and guidance manual 11-9-1-1, both read in full; SIRA Administrative Resolution No. 13 of 2025; SIRA Security Plans Certification; NIBS COBie version history; ISO 12006-2:2015 page; Dubai BIM Standards package. The ADCDA amendments circular was not found on a primary source.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | First controlled draft |
| V0.2 | 2026-11-04 | closure: §3 rebuilt as the ONE edition register with international rows, UAE instrument rows, IMI Framework row and withdrawn BS 1192/PAS 1192 family; §4 code values moved to BBM-STD-93 (/104); §6 current drafts and BBM-STD-72/75/76 indexed; §5 licence register pointer to BBM-STD-94; references re-checked + cross-doc pointer pass + folder names without dots + QMS patch |
| V0.3 | 2026-11-05 | §3 rows settled from primary sources (–): ED-DM-9-1-1 thresholds, ED-DUBAI-BIM-STD version 1.4 / IFC4 / Appendix B, ED-DBC with the AR 225/2024 parameters, ED-DXB-LAW-3-2026 gazette, ED-UAE-CRS Abu Dhabi EPSG codes, ED-ISO10002 date, ED-AUH-PLANNING and ED-UTILITY-REGS instruments; rule-based rows marked |
| V0.4 | 2026-11-05 | Standard watch no. 1 applied: ED-ISO19011 = ISO 19011:2026 edition 4, the 2018 edition withdrawn; new row ED-DM-11-9-1, DM circular 11-9-1 of 2026 applying ED-DXB-LAW-3-2026; ED-SIRA settled on the SIRA Preventive Systems Manual (Administrative Resolution 13 of 2025) and the Security Plan Certificate service; ED-UAE-FLS records the reported ADCDA amendments circular, rule kept; ED-DUBAI-BIM-STD re-read on the DM package, still 1.4; wording: ED-COBIE (COBie V3.0 published 2023), ED-ISO12006-2 (confirmed 2020, to be revised), ED-UAE-CTL (corrigendum OG 821 checked, Art. 821/823/824 unchanged) |