ArchHubBABOOMDownload

Office BIM Glossary

BBM-STD-00 · V0.4 · This is the office's controlled vocabulary for its information standard, manual, appointments, BEPs, delivery plans, guides and exchanges.

Download WordAll standards

BBM-STD-00-GLOSSARY-V0.4 · Office standard · Revision date 5 November 2026 · Draft for office adoption · Private controlled copy

Introduction#

Revision history, ownership and use#

RevisionDateDescriptionApproval status
V0.1Source records changes on 9–10 October 2025Terms, parties, teams, assets and lifecycle BIM usesEmpty approval particulars in export; no approved baseline evidenced
V0.214 October 2026Correct AIM/AIR and appointment EIR; add PIR, current LOIN, open-exchange distinctions and applicability; retain and strengthen BIM usesPrepared in lane O1; office review/adoption pending
V0.32026-11-04closure: UAE authority, code, rating, permit-BIM and CRS terms (new 1.8, 6.7); edition register updated (Revit 2024–2027, Uniclass July 2026, BCF 3.0/2.1, IMI Framework, ISO 9001:2026 and others); suitability and code pointers to BBM-STD-93; decision links to BBM-STD-11; each office decision stated once; …121 applied; + cross-doc pointer pass (BEP terms LDC/PMC/CC/KCP and office role titles in 2.4; CRS register keys) + folder names without dotsPrepared for office review; adoption pending
V0.42026-11-05Standard watch no. 1: new term "Building Quality and Safety Certificate" (1.8) and DM circular 11-9-1 of 2026 cited with Dubai Law No. 3 of 2026; COBie V3.0 published 2023 (1.4, S15/S23); ISO 12006-2 confirmed 2020, to be revised (edition register)Prepared for office review; adoption pending

This is the office's controlled vocabulary for its information standard, manual, appointments, BEPs, delivery plans, guides and exchanges. It is not the generic TBP glossary and does not claim to define every contract term. Definitions are original explanatory paraphrases, not reproduced normative definitions. The governing appointment and incorporated standards determine contractual meaning and authority. Resolve conflicts explicitly; do not silently rewrite an issued appointment or transfer private office records into TBP.

Decision (BIM Manager, 2026-10-14): 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. Basis: One standards function avoids competing terminology owners; actual staffing and delegation require evidence G-A.

Decision (BIM Manager, 2026-10-14): 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. Basis: Office governance does not transfer contractual or statutory powers G-A, G-E.

Decision (BIM Manager, 2026-10-14): 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. Basis: Founder-authorised choices settle defaults without fabricating contract approval or implementation G-E, S04.

Control fieldCompletion / recommended treatment
Master / distributionDecision (BIM Manager, 2026-10-14): 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. Basis: Controlled identity, access and history must survive publication and change G-C, S05.
Review cycleDecision (BIM Manager, 2026-10-14): 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. Basis: A policy review cadence does not prove that live records or tools are ready P04.
Change recordDecision (BIM Manager, 2026-10-14): 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. Basis: Controlled changes prevent inconsistent dependent records G-C, P04.
Applicability recordStandard/edition or convention; jurisdiction/appointment scope; exact software/schema/profile; owner; verification date; evidence
Release checkNo conflated requirements/models; clear exchange purposes; office choices decided and linked; source editions and unresolved particulars explicit

Use full party/requirement names on first occurrence. Record approved appointment-specific meanings. A glossary does not grant access, acceptance authority, legal rights, design competence or certification. Gates must test actual information and workflows.

Section 1 defines requirements, models, exchanges, controls, local conventions and UAE authority terms (1.8). Sections 2–4 retain the source's teams, actors and assets. Sections 5–8 retain Planning, Design, Construct and Operate BIM uses with inputs, outputs and checks. Section 9 controls editions, legacy terms, office decisions and review. References identify the researched sources used.

1 General: terms, requirements and controls#

1.1 Standards basis and interpretation#

ISO 19650-1:2018 supplies concepts; ISO 19650-2:2018 covers delivery; ISO 19650-3:2020 covers operation; ISO 19650-4:2022 covers exchange decisions; ISO 19650-5:2020 addresses security; ISO 19650-6:2025 addresses collaborative health and safety information. ISO 7817-1:2024 supplies the current level of information need framework. ISO/DIS 19650-1 (edition 2) and ISO/DIS 19650-2 are drafts at stage 40.93 on 2026-11-04 and are not in force; the 2018 editions remain the basis until an approved change. Public catalogue evidence establishes scope/edition, not verified clause compliance.

The source's unversioned CSI MasterFormat, BIMForum LOD and NCS references do not establish adopted editions. Treat them as legacy benchmarks pending selection of controlled publications and permitted use. Uniclass 2015 is live classification; “2015” is not the release date of the tables used (office baseline: July 2026 release, see 9.2). RIBA Plan of Work 2020 is a stage framework, not an automatic contractual duty or LOD schedule. Revit terms are product-specific; supported releases are Revit 2024–2027 with 2023 legacy only (matrix in BBM-STD-91). UAE authority, code and rating terms are in 1.8; one code dictionary for discipline, role, suitability, gate and approval codes is BBM-STD-93.

1.2 Requirements, models and plans#

Term / abbreviationControlled meaning and boundaryBasis / context
Organisational information requirements / OIRInformation supporting organisational objectives and decisions. Identify consumer, decision, scope, owner, timing and quality. OIR inform AIR and relevant PIR; they are not a list of file extensionsISO 19650-1:2018; Guidance D ed.2, 2021; office BBM-STD-02
Asset information requirements / AIRRequirements supporting asset management/operation: decisions, trigger events, maintainable-asset data and update needs. AIR are requirements, never another acronym for AIMISO 19650-1:2018 and ISO 19650-3:2020; Guidance D
Project information requirements / PIRInformation supporting specified project decisions, objectives and milestones. Trace purpose/consumer into appointment exchanges; not every PIR needs detailed geometryISO 19650-1:2018; Guidance D; ISO 7817-1:2024
Exchange information requirements / EIRAppointment-specific requirements for exchanges: purpose, recipient, timing, information need, formats, standards, security and acceptance. The appointing party for that appointment establishes them. A lead appointed party can establish downstream requirements when appointing others. EIR apply in delivery and operationISO 19650-2:2018; ISO 19650-3:2020; Guidance D/E
Employer's information requirements / legacy EIRHistorical term in earlier frameworks/contracts. Preserve the original contract meaning, then map to current exchange information requirements. Do not silently relabel a contract or assume only the ultimate asset owner issues requirementsHistorical; appointment-specific mapping; Guidance D/E
Information modelOrganised set of structured/unstructured information containers serving a purpose; includes data and documentation as well as geometryISO 19650-1:2018
Project information model / PIMManaged delivery information supporting project decisions/exchanges, including models, drawings, schedules and other records. Accepted relevant information contributes to AIMISO 19650-1:2018; ISO 19650-2:2018
Asset information model / AIMManaged information supporting asset operation/management, including required geometry, data, documentation and links. Maintain at trigger events; an unverified as-built export is not automatically reliable AIMISO 19650-1:2018; ISO 19650-3:2020
BIM execution plan / BEPTeam plan for information management responding to requirements. Distinguish tender/pre-appointment proposals from the confirmed plan. Covers organisation, methods, federation, checks and delivery; not the legal protocolISO 19650-2:2018; Guidance E; NBIMS-US v4
Task information delivery plan / TIDPTask-team container plan: scope/need, producer, dependencies, production duration, review windows and delivery milestones/dates. A task team need not be a whole discipline. A role matrix is not a TIDPISO 19650-2:2018; Guidance F ed.1, 2020
Master information delivery plan / MIDPCoordinated plan compiled from TIDPs, resolving interfaces, dependencies and dates. Maintain baseline/change evidence; not a combined RACI or milestone listISO 19650-2:2018; Guidance F
Information management functionActivities/resources for managing information across the appointment/lifecycle. Allocate to actual parties/roles with capability/capacity evidence; not necessarily one job or transfer of design liabilityGuidance A ed.2, 2021; ISO 19650-1/-2
Information standardAgreed rules for identification, classification, metadata, structure and exchange conventions; appointment annex fixes version/deviationsISO 19650-2:2018; Guidance E
Information production methods and procedures / IPMPAgreed methods for producing, checking, reviewing, authorising, exchanging, maintaining and retaining information. Include tested tool steps; an acronym does not prove implementationISO 19650-2:2018; office abbreviation
Information protocolContractual arrangements for information duties, rights, use/reliance and related particulars incorporated in appointments as applicable. Technical BEP cannot override signed termsIMI Framework (formerly UK BIM Framework, renamed May 2025) Information Protocol template for BS EN ISO 19650-2, Ed 6; information protocols guidance ed.3, Aug 2022 (explanatory); CIC BIM Protocol 2nd ed. 2018 is legacy; specialist review of particulars
Responsibility matrix / RACIAllocation of activities/production responsibilities. Responsible, Accountable, Consulted, Informed is a chosen management legend, not a CDE code list. Distinguish IM activity allocation from detailed container responsibilityGuidance A/F; local legend
MobilisationPreparing/testing people, methods, access, resources and exchanges before production/release. Installation or attendance alone does not prove readinessISO 19650-2:2018; Guidance E
Information riskInaccurate, incomplete, late, inaccessible, insecure or misused information could harm a decision/outcome. Record cause/event/consequence, owner, treatment, residual risk and escalationISO 19650-5:2020; NPSA; local register
Trigger eventPlanned/unplanned event requiring information obtained, changed or exchanged: inspection, replacement, change of use, failure or emergency. Unplanned events can have planned responses; unforeseen does not mean no preparationISO 19650-3:2020

OIR inform relevant PIR/AIR; appointment EIR define exchanges, and controlled information supports PIM/AIM use and updates.

1.3 Level of information need and detail conventions#

Level of information need (LOIN) specifies the necessary extent and granularity of information. Specify purpose, delivery milestone/trigger, actors and objects before geometric information, alphanumeric information and documentation. ISO 7817-1:2024 is the researched current basis. BS EN 17412-1:2020 is a withdrawn predecessor in the researched British adoption; record national adoption and contractual context before replacing an issued reference.

Level of development (LOD) is a convention in published or appointment-specific model-element specifications. “Level of detail” concerns geometric detail and can have different meanings between authors. Neither is an alternative name for LOIN. Do not convert a RIBA stage automatically to LOD 200/300/400 or clash tolerance. Record the exact adopted LOD publication, edition, element scope and reliability limits. A label alone cannot define data/documentation needs.

Decision (BIM Manager, 2026-10-14): 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. Basis: ISO 7817-1:2024 distinguishes information need from bare LOD/stage labels S07.

Requirement fieldSynthetic example
Purpose / consumerCheck safe maintenance access; operations reviewer
Milestone / actorsBefore plant selection; supplier produces, discipline designer checks, appointed receiver accepts
ObjectsSelected maintainable equipment and access/withdrawal zones
GeometryLocation, envelope, access route and manufacturer-required maintenance zone; no internal fabrication detail
AlphanumericStable asset/system/space IDs; dimensions/units; maintenance clearance/source; access method and limits
DocumentationCurrent manufacturer maintenance instruction and reviewed access assessment
CheckCompare zones/route to current coordinated geometry; verify fields/links; receiver demonstrates use
Precision / uncertaintySource/method recorded; acceptance tolerance approved for the decision before exchange, not inferred from LOD

1.4 Open-exchange and structured-data terms#

TermMeaning / purposeBoundary and version context
Industry Foundation Classes / IFCVendor-neutral schema exchanging built-asset objects, geometry, relationships and propertiesISO 16739-1:2024 = IFC 4.3.2.0. Office default IFC 4.0.2.1 Reference View; IFC 4.3.2.0 only by recorded approval after sender and receiver pass a test exchange; IFC2x3 only when an appointment or authority profile requires it; authority submissions use the schema the authority states. Dubai permit submissions: see "Dubai BIM permit submission" in 1.8. Newer is not automatically correct for an appointment
IFC versus issued for constructionIFC is also informal shorthand for a drawing issue purposeExpand the phrase in exchange/status fields. An .ifc model file does not mean authorised construction design
BIM Collaboration Format / BCFExchange of model issues, IDs, viewpoints, element references, assignments and commentsSpecify BCF 3.0 XML or API as supported (BCF 3.0 final, 18 June 2021). BCF 2.1 (2017) only as a recorded fallback where a receiver cannot read 3.0, with a field-loss check. Not the complete model; not proof of design-issue closure
Information delivery manual / IDMMethod for describing use cases, participants, processes and information exchangesISO 29481-1:2025 methodology/format; ISO 29481-2:2025 interaction framework. Describes process; not an IFC checker file
Information Delivery Specification / IDSComputer-interpretable specification of applicable IFC information requirements/checksbuildingSMART IDS 1.0, final June 2024. Run schema conformance (buildingSMART IFC Validation Service or an approved offline validator) before IDS requirement checks. Audit the IDS, then check IFC against it. Does not cover geometric coordination or replace design/safety review
COBieStructured asset-operation information exchange, often tabular, using an agreed schema/profileDelivered when the EIR requires it. Version as specified in the client EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4; COBie V3.0 published 2023). Specify format, fields, exclusions and receiver checks; preserve required older contract profiles unless changed by agreement
BS 1192-4:2014Historic COBie exchange code of practiceWithdrawn in 2022. ISO 19650-4:2022 covers exchange processes, not a replacement COBie schema. Keep legacy contract context
Open exchangeExchange using agreed openly specified structures and tested mappingsExtension alone does not prove preserved identity, geometry, properties or recipient usability
Schema validationFile structure/content rules tested against selected schemaDoes not prove required population, design correctness or receiver acceptance
Requirement checkingContent tested against agreed scoped requirementsExpected population, applicability, values and exceptions defined; a passing sample does not prove the package
Data dictionary / propertyControlled definition with identity, meaning, datatype, units/values, owner and change historyISO 23386:2020; matching display names do not prove identical properties
Data templateStructure of properties describing an object type for its lifecycle useISO 23387:2025 ed.2; govern version, classification and exchange mapping; distinct from populated data
ClassificationGrouping information using adopted tables/codesISO 12006-2:2015 is a framework, not codes. Uniclass 2015 is NBS-maintained: record table/code/title/release. Other systems require edition/mapping
Whole-life carbon / LCA / EPDAssessment over a defined lifecycle boundary; EPD supplies specified product environmental dataState method, scope, units, dataset/version, assumptions and uncertainty. ISO 22057:2022 concerns EPD templates, not whole-building assessment; RICS second edition (2023, updated 2024) applies where adopted

IDM describes process, IDS specifies checkable IFC data, IFC exchanges model information, and BCF carries issues and responses.

Decision (BIM Manager, 2026-10-14): 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. Basis: Data conformance alone cannot demonstrate access or acceptance S18, S20, S04.

This is a synthetic training scenario. Supplier, checker, operations reviewer and timing must be stated; an IDS pass alone cannot close the blocked-access issue.

1.5 CDE, review and acceptance terms#

TermControlled meaning / applicationBoundary
Common data environment / CDEAgreed process and enabling technical solutions for collecting, managing and disseminating information through controlled workflowsMay involve connected systems; define actual permission/state mappings. A shared folder or brand alone is insufficient. Guidance C ed.1, 2020
Information containerIdentifiable persistent unit retrievable in the agreed system: model, file, document or dataset with controlled metadataMay be editable/native. Editability does not make it uncontrolled; PDF does not automatically make it authorised
Work in progress / WIPInformation under development within its production scopeControlled task-team arrangement; not automatically suitable for another team's reliance
SharedInformation made available for agreed coordination/reference after defined review/release checksRecord permitted use, revision, status and recipients; not automatically construction approval
PublishedInformation authorised for defined use under the agreed workflow. Formal delivery is the transition to Published after authorisation (ISO 19650-2 5.7)Record actual authorisation and receiving acceptance as applicable; browser label alone does not prove state
ArchiveRetained history/evidence of container development, exchange and decisionsNot merely a fourth folder visited at project end; retain superseded revisions/audit evidence under approved schedule
Folder name / project folder treeEvery folder is named NN-NAME: two-digit number, hyphen, name in capitals; no dots, spaces, underscores or "&" (write -AND-). The one project folder tree, ordered state → data type → discipline → files, is defined in Manual V0.5 §12.1Dots in folder names break some CAD/xref path handling; a dot appears only in a file name before its extension. Discipline folder codes and numbers come from BBM-STD-93 §2. A folder location alone does not prove a CDE state
Revision / versionRevision identifies a controlled change baseline per container: R00 initial WIP, never recycled, unchanged containers keep their revision, no pack-wide revision; platform version may be intermediate save/upload historyMap explicitly; preserve issued identities; larger version number does not prove authorisation
Status / suitabilityMetadata describing agreed permitted purpose/use. Office codes SU-WIP, SU-COORD, SU-INFO, SU-REVIEW, SU-ISSUEMapping to client and UK National Annex codes (S0–S7, A, B, CR) is in BBM-STD-93 and recorded in the project register; an appointment code list overrides through that mapping. Distinct from RACI letters, gate letters and issue status
Check / review / authorise / acceptProducer checks; appropriate team reviews; authorised delivery role releases; receiver assesses/records acceptance against requirementsAppointment/delegation defines powers. Job title, software button or A/B/C label grants none
GateDecision point using specified evidence/criteria. Three families mapped in BBM-STD-93: office stage gates (Manual 2.1), basis-of-design gates G0–G5 (BBM-STD-12), authority gates (BBM-STD-57 §4). Outcomes are letters A/B/CRecord scope, criteria, reviewers, authority, exceptions and resubmission; not necessarily a RIBA stage boundary
Issue / RFI / nonconformanceTracked question/request/deficiency with ID, type, source/revision, owner, status, due date and dispositionBCF may carry model issues; notices/formal changes use appointment channels
Exception / residual riskDeparture/remaining risk with scope, consequence, owner, authority, action and review/expiryAcceptance cannot waive law, statutory duties or unapproved contractual obligations
Traceability / lineageFollowing a value/decision to source/revision, transformation, checker and acceptance/use recordDashboard refresh time alone does not prove source date/reliability
Security-minded approachProportionate sensitivity/consequence management across people, organisations, process and technologyISO 19650-5:2020; NPSA. Includes aggregation, supplier access, awareness, retention/removal, incidents and monitoring
Structured safety informationHazards, risks, controls and residual issues usable by duty holders across delivery/operationISO 19650-6:2025; link object/location and owner. Information checks do not discharge safety duties

Decision (BIM Manager, 2026-10-14): Use WIP / Shared / Published / Archive as logical CDE states; the Published state folder is 03-PUBLISHED and the earlier platform alias is retired; keep revision, suitability, permitted use and acceptance as separate metadata. Basis: Logical workflow maps to platform labels without changing issued identity or reliance G-C.

Archive retains history throughout workflows, not only after publication. Renaming a folder cannot change issued identity or permitted reliance.

Decision (BIM Manager, 2026-10-14): 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. Basis: Local gate letters differ from RACI and suitability and cannot waive binding criteria S04.

Decision (BIM Manager, 2026-10-14): Require 100% valid applicable mandatory geometry, data and documentation and zero unresolved required hard-intersection or mandatory access/safety failures in the issued scope. Basis: An issue count or optional-data percentage cannot average away a mandatory exchange failure S04.

Decision (BIM Manager, 2026-10-14): 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. Basis: O3 mandatory acceptance covers geometry, data and documentation S04.

Define scope, rules and receiving checks before reporting percentages. No 90%/95% completeness or zero-clash target is a universal ISO threshold. Use the single Clash matrix section 3 tolerance table.

1.6 Authoring, geometry and identification terms#

TermMeaning / boundaryContext / check
Building information modelling / BIMManaged collaborative use of built-asset information to support lifecycle decisionsGeometry/software are components; management also covers data, documents and responsibilities
Physical assetTangible item/system in the applicable management scopeEquipment, structural/architectural components and systems; collect only required AIR scope
Spatial assetIdentified spatial entity or managed area/zone for a decision/functionRoom, compartment or management zone; measurement basis/relationships explicit
Federated modelReferenced combination of separately controlled models for defined usePreserve origin/revision/coordinates/authorship; not a merger of design responsibilities
Coordinate reference system / CRSDefined spatial reference including relevant datum, coordinate system, units and applicable projection/vertical referenceRevit base/survey points and true north are implementation settings, not a complete CRS definition. Record the project CRS by EPSG code with the vertical datum and transformation in BEP §8.2; register in BBM-STD-86 §2 (keys CRS-DXB, CRS-AUH, CRS-OTH). Never hard-code a CRS (for example EPSG:32640) without the authority source
EPSG codeRegistry identifier of a coordinate reference system, datum or transformationRecord with the vertical datum; a vertical datum may have no EPSG code, then record its name and source
DLTM / Dubai Local Transverse MercatorDubai horizontal CRS: EPSG:3997 "WGS 84 / Dubai Local TM" (Transverse Mercator, central meridian 55°20′ E, scale factor 1, false easting 500 000 m)Register key CRS-DXB (BBM-STD-86). Dubai projects; vertical datum DMD (Dubai Municipality Datum, equal to Port Rashid datum), no EPSG code. Confirm against the DM survey data issued for the plot
Abu Dhabi CRSThe CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plotRegister key CRS-AUH (BBM-STD-86). Record EPSG code and transformation in BEP §8.2 once read from that guideline; vertical datum Ras Ghumays (EPSG datum 1146)
Survey control / coordinate authorityVerified reference/control information and authorised adoption/change ownerAt least 3 well-distributed control points plus elevation and unit probes; provenance, points, units, orientation and revision; rough maps remain provisional, not survey/as-built evidence
Shared coordinates / site modelProduct arrangements relating project models to agreed site referenceSupported installed file/cloud workflow and receiving checks; visual alignment/browser groups are not authority
WorksetRevit worksharing group supporting collaborative editing, loading and organisationBorrowing/whole-workset ownership and relinquishment govern editing. Not CAD layer/security lock; family/type catalogue does not set project workset defaults
Central / local / cloud workshared modelProduct-specific collaborative storage/editing arrangementsFollow installed-version supported workflow; synchronise and publish differ and neither alone records formal acceptance
Family / type / instanceRevit component behaviour; shared configured variation; placed occurrenceCategory, host and bindings serve actual use. A type-value change can affect many instances
Shared parameter / GUIDReusable Revit parameter definition with persistent identifierGovern meaning, GUID, datatype, units, category/type-instance binding and tag/schedule/IFC mappings; name match alone is insufficient
Global parameterRevit project-level relationship control/reporting where supportedDistinct from shared parameter and exchange-property identity
Built-in parameterParameter supplied by softwareDefinition/binding may be constrained; values can be editable. Do not claim all values immutable
View / template / filter / overrideProduct presentation and graphics mechanismsNo CDE status, approval or security powers. Test duplication, precedence and final output in installed build
Drawing / renditionRepresentation for a defined purpose, such as sheet/PDF, derived/authored from controlled informationSource/view/sheet/revision and output QA; fixed format alone is not acceptance
Room / tag / area / scheduleSpatial elements, annotations, measurement structures and tabular viewsTag is not room. Areas have schemes/boundaries. Grouped rows may represent multiple elements; schedule edits can alter data
Asset ID / tag / element IDGoverned operational identity (canonical Asset_ID; AssetTag is a mapped alias); external label mapped to it; tool/model-specific element identityDefine persistence/export mapping; do not equate transient authoring IDs, Asset Tags and operational IDs blindly
System ID / Space IDControlled identifiers of related systems/spacesResolve references; maintain retirement/changes; human-readable name is separate
Quantity take-off / QTOScoped quantities under declared inclusion/measurement rulesSource revision, units and exclusions; not automatically complete BOQ, cost or carbon assessment
NWC / NWD / NWFNavisworks cache, published snapshot and working-reference formats respectivelyVendor-specific build/content/receiver tested; product “published” is not CDE acceptance
Clash / clearance / toleranceInterference finding, required separation/access space, and agreed test/acceptance limitSeparate screening settings, physical clearances and installation/survey tolerances; units/scope/authority explicit
Record / as-built / verified existingDocumented information; asserted installed representation; existing information with specified verification/uncertaintyA redline or inferred stair level does not alone prove installed accuracy; method/date and limitations recorded
Authority having jurisdiction / AHJCompetent authority for relevant approval/duty/locationActual jurisdiction/instrument/edition/applicability in maintained annex; UAE authorities and instruments are defined in 1.8; template code list does not determine jurisdiction
Code validation / compliance evidenceScoped review against adopted applicable requirementsAutomation supports competent reviewer; model constraints/clash pass do not prove complete legal compliance

1.7 Naming, metadata and property conventions#

V0.1's filename ProjectCode-Discipline-Type-Number-Revision is not universal ISO grammar and is retired (BBM-STD-11 change trace C02). Preserve issued identities. Resolve naming in an approved annex: grammar, code lists, examples, revision/status, aliases and effective date. No glossary revision silently renames files.

Decision (BIM Manager, 2026-10-14): Use CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext when an appointment supplies no grammar; retain per-container Rnn revisions and the suitability codes in 1.5. Basis: Adopts the Manual/BEP external candidate and existing Rnn convention consistently; appointment requirements take precedence through one recorded mapping G-C (re-affirmed by). Authority: code lists and mappings in BBM-STD-93 Code dictionary; naming/revision rule in Clash matrix section 2.

Decision (BIM Manager, 2026-10-14): 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. Basis: Retains the shared Manual/BEP convention while separating display from identity S35, G-C.

Decision (BIM Manager, 2026-10-14): 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. Basis: One external identity prevents parallel grammars and IFC format/purpose ambiguity G-C.

Synthetic external example: CLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc. M3/A and every token derive from the approved code dictionary BBM-STD-93: 3-letter discipline codes for views, folders, clash and QA (ARC, STR, MEC, ELE, LSC, PLU, FLS, INT, CIV, SUR, QTY, CON, GEN) and 1-letter ROLE codes for file names and sheet prefixes (A, S, M, E, L, P, F, I, C, G, Q, W, Z). LSC = Landscape and FLS = Fire and Life Safety. This eight-token grammar is an office default, not an ISO mandate; existing appointments keep their approved grammar until authorised migration.

Decision (BIM Manager, 2026-10-14): 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. Basis: Stable semantic identity matters more than display aliases or blind renaming S16, S17.

Decision (BIM Manager, 2026-10-14): 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. Basis: Definition, binding and classification version require one dictionary S16, S09.

Decision (BIM Manager, 2026-10-14): 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. Basis: Typed units and provenance prevent misleading conversions S16, S17.

Decision (BIM Manager, 2026-10-14): 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. Basis: Unambiguous dates/units support traceable schedules and exchanges S16, G-F.

See (§1.5).

See (§1.5).

Source label / ambiguityOffice semantic baselineMapping / check before deployment
Asset Tag / Asset_ID / Asset IDAsset_ID: canonical text operational occurrence ID; map AssetID / Asset Tag / AssetTag; physical tag separate where neededExisting GUIDs/bindings, persistence/retirement and receiving mapping; no blind rename
System ID / Space IDSystemID, SpaceID: text relational keysType/instance follows semantics; references/export persistence validated
Classification / Classification CodeClassification_Code (alias ClassificationCode), ClassificationTable, ClassificationTitle, ClassificationReleaseAdopted system/table/release; avoid untyped combined code/title
Expected Life / LIFE EXPECTENCYExpected_Life_Years (alias ExpectedLife): numeric years, with basis/uncertaintyMap legacy text/numeric fields; unknown is not numeric zero
Approval status / A/B/C / stateDistinct GateResult, Suitability, Revision, CDEState, issue statusSeparate legends and actual appointment/platform mapping
Source model / view / sheet / revisionExplicit controlled-source/revision and output linksTrace rendition/report; display name is not immutable identity

These are adopted semantic names, not newly allocated Revit GUIDs or IFC property definitions. Record datatype, units, permitted/unknown values, category, type/instance, GUID where relevant and exact exchange mapping in the property dictionary. Do not manufacture GUIDs or replace installed bindings through glossary revision. ISO 23386:2020 and ISO 23387:2025 support property/template governance.

1.8 UAE authority, code, rating and permit terms#

These terms name the authorities and instruments the office works under. Editions and dates are the values checked on 2026-11-04; the one edition register is BBM-STD-51 §3 and the requirement detail is in BBM-STD-85 UAE authority and submissions annex. Record the edition in force at project start (permit submission for permit rules) in the BEP. A term here does not prove that an instrument applies to a project.

TermMeaning / instrument and status (checked 2026-11-04)Boundary / where used
DM / Dubai MunicipalityDubai planning and building-permit authority; issues the DBC, the BIM permit circulars and Al Sa'fatMaster-developer and free-zone authorities may also approve; record the actual authority per plot in the BEP
DMT / ADMAbu Dhabi Department of Municipalities and Transport and Abu Dhabi Municipality; publish the ADIBC, the Estidama Pearl rules and the ADM BIM Code of Practice (Oct 2020)ADM BIM Code of Practice applies where appointed; no universal Abu Dhabi building-permit BIM threshold was found
Civil Defence / DCDEmirate civil-defence authority approving fire and life-safety designApplies the UAE FLS Code plus the emirate authority's amendments
DBC / Dubai Building CodeDubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 (13 Aug 2024) "amending some building specifications in the DBC"Apply the DBC plus all DM amending resolutions in force at permit submission
Dubai Law No. 3 of 2026Emirate law (not federal) on the Quality and Safety of Buildings, issued 27 Feb 2026, in force 60 days after Official Gazette publication. A Quality & Safety Certificate is needed after 20 years from completion, valid 10 years (5 years when the building is 40 years or older). Applied by DM circular 11-9-1 of 2026 (register ED-DM-11-9-1)Periodic inspection of existing buildings: an asset-life obligation (BBM-STD-75, BBM-STD-76, BBM-STD-85), not a design-permit rule
Building Quality and Safety CertificateThe Dubai Municipality certificate (Arabic: shahadat jawdat wa salamat mabna) that a building completed 20 or more years ago is of sound quality and safety and fit for continued use. Issued under Dubai Law No. 3 of 2026 and DM circular 11-9-1 of 2026 on the Build in Dubai platform, after a licensed engineering office has assessed the building against the DM technical checklist (structure, external cladding, windows/doors/guards, external and common-area MEP, Civil Defence and SIRA requirements) and any defects have been remedied. Valid 10 years (under 40 years since completion) or 5 years (40 years or more); renewed in the last 90 days before expiryAn owner duty. The office may act as the owner's appointed engineering office: assessment, technical report, remediation supervision and applications (BBM-STD-75 §7, BBM-STD-85 §4)
UAE FLS CodeUAE Fire & Life Safety Code of Practice, September 2018 edition (current on the DCD site)Edition plus the emirate authority's amendments current at project start, recorded in the BEP; fire rating stored per
ADIBCAbu Dhabi International Building Codes, adopted by Executive Council Resolution 7C 26/2013, effective 1 Oct 2013The ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04)
Dubai BIM permit submissionOpen BIM (IFC) submission with the building permit through buildindubai.gov.ae/bim. Circular 9-1-2 (13 Oct 2023): from 1 Jan 2024 for buildings over 20 floors (ARC) or 40 floors (STR), over 20,000 m² (ARC) or 30,000 m² (STR), specialised buildings such as hospitals and universities, and government projects. Circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026): ARC and STR BIM with the permit for new buildings above G+12 or of 15,000 m² or more; BIM with the application for alterations that add or remove floors, add 1,500 m² or more, fully redesign, change the main use or relocate on the plot; final BIM before the completion certificate for other alterations; drawings extracted from the model. Circular 9-1-1 (2021) on applying BIM is cited by 9-1-2Neither circular states an IFC version: use the IFC schema and export setup stated in the current Dubai BIM Standard, checked at project start and recorded in the BEP; attributes per the Model Attribute Matrix issued with that standard. Submission as zipped openBIM IFC within the portal upload limit. BIM use 6.7
Estidama Pearl Rating SystemAbu Dhabi green-building rating; building-permit condition: private projects minimum 1 Pearl, government-funded projects minimum 2 Pearl (DMT, 8 Jan 2025)Record target, edition and assessor in the BEP; data fields per BBM-STD-58/60/61/62
Al Sa'fatDubai Green Building System, 2nd edition (Jan 2023): Silver Sa'fa mandatory for all new buildings in Dubai; Golden and Platinum optionalRecord target and edition in the BEP
UAE PDPLFederal Decree-Law No. 45 of 2021 on the Protection of Personal Data, effective 2 Jan 2022Executive regulations as listed on uaelegislation.gov.ae at project start; personal-data handling per BBM-STD-90
Decennial liabilityFederal Decree-Law No. 25 of 2025 (Civil Transactions Law, effective 1 Jun 2026) Art. 821: engineer and contractor jointly liable for 10 years from delivery; Art. 823 voids exemption clauses; Art. 824 three-year claim period. Contracts signed before 1 Jun 2026: Federal Law 5/1985 Art. 880Records retention minimum and schedule owned by BBM-STD-90
SIRA security drawingsSecurity-system design approval in DubaiFollow the current SIRA/DM requirement for the plot, confirmed at permit stage; classify per BBM-STD-87

2 Types of teams#

2.1 Project team#

The appointing party and all delivery teams involved in the project scope. Broader than daily model authors. Express governance/interfaces through appointments and delegated functions rather than a presumed project-wide BIM approver. ISO 19650-1:2018 supplies the conceptual basis.

Decision (BIM Manager, 2026-10-14): 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. Basis: A title, RACI or Directory listing does not establish authority S01, G-A.

Decision (BIM Manager, 2026-10-14): Every exchange needs current EIR, verified recipient/actual acceptor, decision deadline and recorded accepted/rejected scope; verify powers through appointment and private Directory. Basis: Exchange decisions require defined requirements and empowered recipients S04, G-E.

Inputs: brief, objectives, AIR/PIR/EIR and procurement constraints. Outputs: applicable governance arrangements and recorded project decisions. Directory records identities; appointment/delegation records powers.

2.2 Delivery team#

Lead appointed party and its appointed parties for the relevant appointment, with production performed by task teams. Multiple delivery teams may operate on a project; no lead automatically represents every appointment/lifecycle period.

Decision (BIM Manager, 2026-10-14): 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. Basis: Production, authorisation and acceptance are distinct evidenced actions S02, S04.

Decision (BIM Manager, 2026-10-14): 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. Basis: Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence G-F. Authority: TIDP section 2, ownership and change propagation.

The delivery team maintains BEP, coordinates TIDPs/MIDP and manages interfaces. Design responsibility remains with the relevant appointed designer.

2.3 Task team#

People assembled for particular information-production tasks/scope: discipline, supplier or narrower group. Not defined only by profession. TIDP identifies containers, inputs, duration, dependencies, checker and timing.

See (§2.2).

See (§2.2).

Publish to Shared requires actual CDE review/release; moving browser views or pressing cloud publish alone is insufficient.

2.4 Office role titles and appointment abbreviations#

Job titles do not carry ISO 19650 powers; powers come from the appointment and delegation recorded in the Directory. The master responsibility matrix is BBM-STD-55; the BEP §1.4 terms and §2.4 resource table use these meanings.

Title / abbreviationMeaningISO 19650 function it usually serves
BIM ManagerOffice information-standards owner and glossary custodian; on a project, leads the information management function for the officeInformation management function of the LAP or appointed party, as delegated
BIM CoordinatorRuns federation, coordination cycles, clash matrix and issue trackingTask-team coordination within the delivery team
BIM SpecialistDevelops and maintains templates, scripts, checks or exchange presets for a defined scopeSupports the information management function; no acceptance power
BIM EngineerProduces discipline model and data content and runs discipline checksTask-team producer
BIM ModelerProduces model geometry and documentation under a discipline leadTask-team producer
LDCLead design consultantLead appointed party where so appointed; otherwise an appointed party
PMCProject management consultant acting for the clientAppointing party's delegate, only within recorded delegation
CCCost consultantAppointed party (task team)
KCPKey contact person of an organisationRole contact only; personal details held in the Directory

3 Types of actors#

3.1 Appointing party#

Receiver of information concerning works, goods or services under the relevant appointment. The role is relational: ultimate asset owner or a lead appointed party procuring its supply chain can occupy it. It is not always one project-wide client job title.

See (§2.1).

The appointing party establishes requirements and receiving arrangements within its actual powers, with OIR/AIR/PIR and brief as inputs and EIR, clarifications and acceptance decisions as outputs.

3.2 Lead appointed party#

Appointed party leading information coordination/exchange for the relevant appointment/delivery team. Lead designer or contractor may fulfil the role depending on procurement; label alone does not transfer others' design liability or authority over every project team.

See (§2.2).

See (§2.2).

Coordinate BEP, delivery plans, federation and exchanges within actual scope, capacity and dependencies; receiving acceptance remains separate.

3.3 Appointed party#

Provider of information concerning works, goods or services under an appointment; may also appoint others. Roles are not permanently fixed by organisation name/discipline.

See (§2.1).

See (§2.1).

The appointed party produces/checks information, maintains its TIDP and resolves assigned issues; verify resources and property/coordinate baselines.

4 Types of assets#

4.1 Physical assets#

Tangible items/systems, such as equipment, doors, structure and envelope components. Not every modelled object is maintainable; geometry alone does not establish operational information. Select scope from AIR and decisions. Asset records follow (4.2) and Asset_ID (1.7).

4.2 Spatial assets#

Spaces, rooms, zones, compartments or parcels managed for a purpose. Identity/relationships can persist through geometry changes. Authoring room, area-scheme element and fire compartment may be different concepts despite matching names/boundaries.

Decision (BIM Manager, 2026-10-14): 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. Basis: AIR and operational decisions determine asset obligations S03, S07.

See (§1.7).

Decision (BIM Manager, 2026-10-14): Use Uniclass 2015 as office default, freezing adopted table/release/licence; preserve appointed/authority classifications through mappings and controlled upgrades. Basis: Uniclass is maintained, not a fixed release or exclusive mandate S09, S10.

Decision (BIM Manager, 2026-10-14): 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. Basis: Space decisions need consistent identity/measurement and proportionate privacy S03, S05.

5 BIM uses — Planning#

5.1 Existing conditions modelling#

Definition: represent existing conditions for a defined decision, with stated source, coverage, verification and uncertainty. Inputs: survey control/CRS, scans, drawings, inspection records and field-check plan. Techniques may include scanning, photogrammetry and selective verification; a plausible visual fit does not establish accuracy.

Outputs: scoped existing-conditions model, dated source/control record and deviation/uncertainty report. Check: independent control-point/alignment tests, source dates, coverage/occlusions and uncertainty suitable for the decision. Record unresolved areas and restrictions. A map-based estimate or stair-step inference remains provisional until verified; do not relabel it as-built.

5.2 5D cost estimation#

Definition: relate model-derived quantities to cost information for an explicit estimate or option decision. Inputs: classified scoped elements, measurement rules, source revisions, rate/currency/price-base and exclusions. Outputs: quantity/cost schedule or BOQ as commissioned, alternative comparisons and variance/assumption record.

Check: reconcile required quantities and units to known samples and model IDs; account for unmodelled allowances, overlaps, waste and exclusions. Distinguish capital/operating, forecast/actual and cost/benefit; avoid double counting. A cost-linked model is not automatically a complete estimate. Record estimate owner, reviewed baseline and uncertainty before reliance.

5.3 4D phase planning#

Definition: link physical scope/locations and temporary works to planned activities for sequence/logistics review. Inputs: programme/WBS with actual dates, current models, location mapping, temporary works and access/safety constraints. Outputs: sequence simulation, phasing/logistics sheets and constraints register.

Check: all scoped critical activities map to objects/locations or have a justified nongeometric representation; temporary works and required access zones are included. Review sequence for spatial/time conflicts with actual construction/safety authorities. Record exclusions, responsible owners, change impacts and disposition. Playback is evidence for a decision, not a guarantee of a safe method or achievable programme.

5.4 Programming#

Definition: test required functions, spatial capacity, adjacencies and relationships against a brief. Inputs: approved space programme, area/occupancy measurement basis, adjacency and performance criteria. Outputs: typed-space model, brief-compliance matrix, stacking/adjacency studies and exceptions.

Check: reconcile room/space counts and area denominators to the current brief using agreed units/tolerances. Explain gross/net/usable distinctions, shared/unallocated spaces and exclusions. Stable SpaceIDs support change comparisons; department/use values and approvals are current. A schedule total alone does not prove spatial suitability.

5.5 Site analysis#

Definition: assess decision-relevant site constraints/opportunities, such as access, utilities, environment, orientation and context. Inputs: surveys, current official/authorised datasets, studies and source dates/rights. Outputs: constraints register, source-based risk map and design assumptions.

Check: coordinate references, dataset age/coverage, uncertainty and verified versus indicative services. Critical constraints link to a decision owner and required survey/consultation. Do not treat historical mapping as field utility clearance or formal authority approval. Review sensitivity before sharing detailed asset/site information.

6 BIM uses — Design#

6.1 Design reviews#

Definition: multidisciplinary assessment of current design information against the agreed brief, information requirements and technical criteria. Inputs: controlled model/drawing revisions, review scope/rules, outstanding issues and appropriate reviewers. Outputs: review record, issue dispositions and recommendation to the actual decision authority.

Check: all scoped zones/systems reviewed; critical issues resolved or held with responsible owners; model references, viewpoints, decisions and rationale retained. Use BCF where compatible, without assuming issue closure equals formal package acceptance. Authorisation, receiving acceptance and design safety duties remain separately evidenced.

6.2 Design authoring#

Definition: produce design geometry, properties and documentation to agreed requirements. Inputs: approved templates, property/GUID mappings, classification release, coordinates, linked inputs, naming annex and TIDP. Outputs: controlled models, views, sheets and schedules with QA evidence.

Check: required fields and scoped relationships, model/drawing/schedule consistency, coordinate/export tests and justified warning/performance limits. Use a minimal approved workset strategy; do not mandate a workset for every level/system or purge indiscriminately. Preserve needed data, constraints and revision history; test external content before library admission. Native editability is compatible with control.

6.3 Energy analysis#

Definition: assess energy/load performance using documented analytical abstractions. Inputs: current geometry/constructions, thermal zones, climate data, schedules, gains, systems and baseline/proposed assumptions. Outputs: EUI with declared denominator/period, loads, comparison and sensitivity report.

Check: source revision and transformation into the analysis model; reproducible inputs, schedules and operating assumptions; baseline/proposed comparability and reviewed exclusions. Record analytical tool/build, calculation method and technical reviewer. Revit geometry does not automatically provide valid thermal assumptions; a result is not a permit approval or measured performance.

6.4 Structural analysis#

Definition: assess structural behaviour using an appropriate analytical model, loads, combinations and boundary conditions. Inputs: current physical/analytical models, material properties, design basis and interfaces. Outputs: analysis/design report, sizing or serviceability checks and reactions/interface requirements.

Check: reconcile physical/analytical geometry and offsets, load paths, supports and declared code basis with the responsible engineer. Record reviewed assumptions, exclusions, opening/embed coordination and model revisions. A successful solver run or data transfer does not establish engineering adequacy or authorise another discipline's design.

6.5 Sustainability evaluation#

Definition: assess adopted environmental/performance objectives, including energy, water, materials, waste and carbon where required. Inputs: applicable brief/authority annex, quantity/model revisions, chosen methodology, datasets/EPDs and supporting declarations. Outputs: assessment/credit tracker, evidence map, option results and uncertainty record.

Check: quantities/units and assessment boundary, lifecycle stages, dataset versions and gaps; reconcile schedules, drawings, specifications and procurement substitutions. Competent reviewer records result, noncompliance/variance and permitted authority disposition. Do not assume a regional rating system or green-building code applies universally, but in the office's UAE jurisdictions ratings are statutory: Abu Dhabi Estidama Pearl (minimum 1 Pearl private, 2 Pearl government-funded) and Dubai Al Sa'fat (Silver Sa'fa minimum for all new buildings); see 1.8. Record edition and target in the jurisdiction annex (BBM-STD-85) and BEP. ISO 22057:2022 data templates do not replace whole-life assessment; follow the adopted RICS method where applicable.

6.6 Code validation#

Definition: evaluate scoped design/submission evidence against applicable codes and approvals. Inputs: controlled code basis/editions/applicability, current design, competent reviewers and AHJ requirements. Outputs: calculations, code/life-safety drawings, required schedules/forms, comments and closure record.

Check: occupant load, exit/travel/access dimensions and relevant fire/structural/MEP conditions against the actual adopted requirements; reconcile calculations to current drawings and schedules. Record limitations of automated checks and significant safety information. Model constraints, ramp settings or clash rules cannot prevent every code violation. Only competent authorised review and actual AHJ evidence establish the relevant approval; approved variances need traceable authority. UAE code basis: DBC with amending resolutions, UAE FLS Code 2018 with emirate amendments, ADIBC edition in force (1.8; BBM-STD-57, BBM-STD-85).

6.7 Authority submission (e-permit BIM)#

Definition: prepare and submit model-based information to a permitting authority under its BIM submission rules, such as the Dubai BIM permit submission (1.8). Inputs: applicability test against circulars 9-1-2 and 9-1-3 (storeys, floor area, building type, alteration triggers), the current Dubai BIM Standard export setup and Model Attribute Matrix (version checked at project start), the authority CRS (BBM-STD-86) and drawings extracted from the same model. Outputs: zipped openBIM IFC submission, the extracted drawing set, portal receipt, validation result and authority comments with dispositions.

Check: test the applicability trigger and record the result in the BEP; export with the authority-stated schema and setup, then validate schema, required attributes and coordinates before upload; confirm the submitted drawings are extracted from the submitted model revision. Record portal receipt, authority comments, resubmissions and final BIM before the completion certificate where required. A portal upload is not an approval; only the authority decision is.

7 BIM uses — Construct#

7.1 3D coordination / clash detection#

Definition: identify and resolve geometry/interface, clearance and access conflicts for a defined exchange. Inputs: agreed model pairs/revisions, zones, coordinates, rule types/units, exclusions, severity and acceptance scope. Outputs: federated review model, issue register/BCF, designer dispositions, retest results and residual-risk sign-off.

Check: distinguish hard intersections, service/maintenance clearances, duplicates and intentional penetrations. Each rule records model pair/zone, method/tool build, numerical setting, purpose, exclusions, issue owner and actual acceptance authority. A clash count or LOD is insufficient; tests can miss required but absent elements. Close an issue only after disposition, corrected source revision and retest evidence, or an authorised, scoped exception that does not waive mandatory duties.

Decision (BIM Manager, 2026-10-14): 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. Basis: BIM uses serve outcomes rather than software availability or universal deliverables P01, S07.

See (§1.3).

A BIM use is an application of information to an outcome, not a software licence or mandatory deliverable for every project. Penn State BIM Project Execution Planning Guide v2.2 (2019) supplies planning context. Appointment-specific deliverables, thresholds and authorities remain binding.

Decision (BIM Manager, 2026-10-14): 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. Basis: Purpose, pair, zone and clearance evidence determine the test; stage and LOD do not determine an allowable intersection S07. Authority: Clash matrix section 3, the sole H/C/A/D/V tolerance table.

For hard intersections use rule H in the single Clash matrix section 3 table: 0 mm deliberate penetration allowance with qualified tool precision/contact behaviour. Acceptance is not a claim of perfect surveyed or installed geometry; clearance/access rules have their own required evidence.

See (§7.1).

Rule fieldFillable record
ID / purpose / scope[pair, zone, stage/exchange and required decision]
Input / method[model revisions, coordinates, tool/build, hard/clearance method]
Screening / acceptance / units[separate numerical settings; reason and exclusions]
Issue / disposition / retest[ID, elements/viewpoint, severity, owner, due date, revised source and result]
Residual / authorisation[consequence, compensating control, designer and actual accepting authority]

7.2 Site utilisation planning#

Definition: plan construction logistics over time. Inputs: constraints/permits, phasing, temporary works, access requirements and site information. Outputs: fencing, access, crane/hoist/laydown/welfare and safety-zone arrangements with sequence overlays and constraints.

Check: public/occupier interfaces, access/egress, lifting and temporary-work zones against actual method/permit requirements. Resolve interfaces with competent construction/safety owners and record assumptions and dates. A 4D overlay is planning evidence, not a lifting permit or engineered temporary-works approval.

7.3 Construction system design / virtual mockup#

Definition: test complex assemblies/interfaces and build sequence before fabrication/installation. Inputs: current shop/design models, manufacturer tolerances, access/erection assumptions and interface details. Outputs: reviewed mockup/views, tolerance stack-up, sequence narrative and inspection/test checkpoints.

Check: critical interfaces, assembly/removal access, dimensional chains and stated fabrication/site tolerances. Link inspection/test requirements and unresolved items to objects/views, owners and dates. Preserve design/manufacturer responsibilities; virtual agreement does not replace required physical tests or designer approval.

7.4 Digital fabrication#

Definition: derive machine/fabrication information from controlled design/shop information. Inputs: authorised fabrication scope/revision, material specification, verified machine/profile/units and tolerances. Outputs: CAM/CNC files, cut/spool lists, nesting and production IDs with source trace.

Check: receiving-machine compatibility, dimensions/units/orientation, tool/process limits and representative trial/inspection results before batch release. Record who authorises fabrication and what change invalidates downstream files. An IFC export or visually correct model is not automatically machine-ready. Retain accepted outputs and rollback to the last authorised batch where needed.

8 BIM uses — Operate#

8.1 Record modelling#

Definition: maintain a representation of installed/operational conditions with declared evidence and verification. Inputs: reviewed field changes, redlines/RFIs, inspection/commissioning records, scans and asset information. Outputs: checked record model/AIM updates, asset register/document links and variance report.

Check: source dates/coverage and approved design-versus-installed differences; stable tags/IDs; relevant O&M/warranty/test links; geometry/data uncertainty appropriate to the operational decision. Receiver tests the actual update/import. Record missing/inaccessible areas explicitly. A compiled shop model or visually plausible reconstruction must not be described as verified as-built without evidence.

8.2 Building maintenance scheduling#

Definition: plan preventive, statutory and condition-driven maintenance for scoped maintainable assets. This corrects V0.1, which duplicated building-systems analysis here. Inputs: asset/system/location IDs, manufacturer/service instructions, criticality, inspection condition, warranty/statutory intervals, service history and constraints.

Decision (BIM Manager, 2026-10-14): Review safety-critical overdue maintenance/defects before affected operation; assign owner, action date and competent disposition rather than masking them in portfolio percentages. Basis: Safety information must serve the affected activity and duty holder S06, S03.

Every scoped maintenance task links to current asset/instruction and responsible owner; intervals need an approved basis and receiver import/update/exception tests.

8.3 Building systems analysis#

Definition: evaluate actual system/service performance and diagnose anomalies. Inputs: BMS point list, meter/sensor trends with dates/calibration/units, asset/space mapping, operating schedules and comfort/incident records. Outputs: baseline/comparison, root-cause findings and retuning/maintenance recommendations.

Check: data coverage/time alignment, sensor mapping/quality, declared assumptions and reviewer interpretation. Record anomaly/action owners/dates and test interventions against measured results. Forecast savings are separate from verified actual benefit. Restrict sensitive control-system details and occupant data; reporting connectivity does not authorise live system control.

8.4 Asset management / FM#

Definition: use maintained asset information for operation, condition, lifecycle and replacement decisions. Inputs: AIR, AIM/register, condition and cost/service records, integration mapping and actual receiving-system profile. Outputs: accepted CAFM/CMMS records, asset/document links, lifecycle forecasts and replacement actions.

Check: unique stable IDs, locations/system relationships, required fields and relevant document links, then test an actual import/update and reconcile counts/known records. Specify exact COBie version/profile only where required. Set update owner and trigger for replacement, inspection, incident and handover; a one-off spreadsheet is not ongoing AIM management. Forecast life is an assumption with basis/uncertainty, not a manufacturer guarantee.

8.5 Space management and tracking#

Definition: manage space allocation, moves/changes and utilisation for an explicit business decision. Inputs: stable space inventory/measurement basis, department/function, approved move requests and proportionate occupancy surveys/data. Outputs: revised assignments, utilisation report, move plan and chargeback where commissioned.

Check: space IDs, period/denominator, sampling coverage, source revision and approvals; reconcile allocation and physical change records. Record split/merge/retirement and maintain asset-system links. Avoid inferring people-level behaviour from sparse sensors. Distribute only minimum aggregate information necessary for the decision.

8.6 Disaster planning#

Definition: prepare usable information for authorised response and recovery from fire, flood, power loss, cyber incidents or other selected scenarios. Inputs: verified critical asset/location/shut-off records, role-based emergency routes, response plans, sensitivity assessment and recovery requirements. Outputs: controlled response information, accessible/offline extracts where approved, drill and recovery-test records.

Decision (BIM Manager, 2026-10-14): 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. Basis: Operational resilience needs testing without wider sensitive distribution S03, S05.

Information preparation does not replace emergency-service procedures or authorise untrained intervention.

9 Editions, legacy mappings and office adoption#

9.1 Lifecycle and stage terminology map#

RIBA Plan of Work 2020 has eight stages: 0 Strategic Definition; 1 Preparation and Briefing; 2 Concept Design; 3 Spatial Coordination; 4 Technical Design; 5 Manufacturing and Construction; 6 Handover; 7 Use. Stage 3 “Developed Design” is legacy wording. Stage 4/5 can overlap depending on procurement. No stage automatically sets LOD, geometric tolerance, design liability or a file's suitability.

Decision (BIM Manager, 2026-10-14): 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. Basis: Manual phases do not establish stage tolerances, LOD or dates S21, G-F.

Decision (BIM Manager, 2026-10-14): 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. Basis: Duplicate #01 and numbering gaps cannot establish the intended historic mapping; distinct decisions and dates must remain traceable G-F. Authority: MIDP section 4, exchange identity and stage reconciliation.

The nine TBP phases are manual groupings, not project stages; use the map below for learning and tailor actual exchanges to the appointment.

TBP phaseTypical RIBA 2020 contextInformation-management focus
Intro0–1; refreshed at new appointmentsBusiness purpose, decisions, OIR and role awareness
Setup1–2 and each mobilisationRequirements, teams, methods, access and exchange tests
Modeling2–5 and relevant operational changesPurpose-led information production; no automatic LOD mapping
DeliveryAny agreed exchange across 0–7TIDP/MIDP, checks, release, receiver acceptance
Information0–7Properties, classification, documentation, lineage and currency
Coordination2–5 and operational interfacesFederated scope, interface rules, issues and verified closure
DisciplineScope-specific across 0–7Technical responsibility and competent review
AuthorityApplicable decision/submission gatesVerified instruments, jurisdiction and actual powers
Handover6–7; progressive transfer and later triggersAccepted AIM contribution, receiver usability and maintained updates

9.2 Edition and applicability register#

The researched edition is a reference baseline, not an instruction to upgrade an appointment or installed tool. Record the exact publication/version actually adopted, where it applies, owner, evidence and change decision. ISO drafts are not replacements for published standards; reassess currency before adoption. The RESEARCH.md cut-off is 14 October 2026; the editions below were re-checked on 2026-11-04. This table is the Glossary view of the one edition register, BBM-STD-51 §3.

TopicResearched edition / boundaryRequired office applicability entry
Information managementISO 19650-1/-2:2018; -3:2020; -4:2022; -5:2020; -6:2025. ISO/DIS 19650-1 ed.2 and ISO/DIS 19650-2 at stage 40.93, not in forceAdopted parts/national annexes, appointment/operational scope and licensed compliance review
LOINISO 7817-1:2024 (replaces EN 17412-1:2020, withdrawn)National adoption, existing contractual reference and agreed transition
ClassificationISO 12006-2:2015 framework (last confirmed 2020; to be revised); Uniclass 2015 (NBS), office baseline July 2026 release: Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27Frozen per project in the annex; upgrades by ChangeID; licence, code validation and alias mapping
Data dictionariesISO 12006-3:2022 (data dictionary framework); buildingSMART Data Dictionary (bSDD)Dictionary and version used, mapping to office properties
Open exchangeISO 16739-1:2024 = IFC 4.3.2.0; office default IFC 4.0.2.1 RV; BCF 3.0 XML/API (final 2021), BCF 2.1 recorded fallback; IDS 1.0 (June 2024)Exact schema/profile/tool builds, limitations, representative sender/receiver test and results
Linked containersISO 21597-1/-2:2020 (ICDD)Use only where an appointment requires linked containers; receiver test
Process descriptionsISO 29481-1:2025 ed.3, ISO 29481-2:2025 ed.2, ISO 29481-3:2022Adopted process/method edition and local interaction/authority map
ValidationbuildingSMART IFC Validation Service (schema and normative rules) versus IDS (project information requirements)Both scopes recorded; confidential models only with data-owner approval or an approved offline validator
Properties/templatesISO 23386:2020 and ISO 23387:2025 ed.2Dictionary/template version, identity, units/bindings and exchange mappings
Handover dataCOBie version as specified in the client EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3; BS 1192-4:2014 withdrawn 2022Actual contractual COBie or other profile, receiving system and accepted sample/update
GuidanceIMI Framework (formerly UK BIM Framework, renamed May 2025): Guidance Parts A/D/E ed.2 (2021) and C/F ed.1 (2020) archived; Information Protocol template for BS EN ISO 19650-2 Ed 6; protocol guidance ed.3 (Aug 2022); CIC BIM Protocol 2nd ed. 2018 legacyExact guidance used; archived guidance is not a claim to latest edition
Standards landscape and AI readinessPAS 1958:2026 (31 Mar 2026); ISO/IEC 42001:2023AI use per BBM-STD-92
Management systemsISO 9001:2026 ed.6 (16 Sep 2026, replaces 9001:2015); ISO/IEC 27001:2022 + Amd 1:2024; ISO 55001:2024 ed.2Office adoption and certification-body transition recorded separately
Drawing/CADISO 128-1:2020; ISO 13567-1/-2:2017; ISO 7200:2004Applied through BBM-STD-66 and BBM-STD-67
StagesRIBA Plan of Work 2020Procurement-specific milestones, overlap and appointment allocation
AuthoringAutodesk Revit supported majors 2024, 2025, 2026, 2027 (latest 2027.3, 15 Sep 2026); Revit 2023 out of Autodesk support: legacy, no new projects, existing projects only with recorded risk acceptance and upgrade plan. Revit IFC exporter 27.4.0.30 (30 Oct 2026) exports IFC4x3; IFC 4.3 RV used only after a test export from the project build passes the project IDS. AutoCAD release per BBM-STD-66Qualification baseline per Manual 11.3; full release/exporter/library matrix in BBM-STD-91; actual installed build, add-ins, licences and receiver compatibility; no automatic “or later” permission
Local codes/rating schemesDBC + DM amending resolutions; Dubai Law 3/2026; UAE FLS Code Sept 2018 + emirate amendments; ADIBC (2013 edition at 2026-11-04); DM circulars 9-1-2 / 9-1-3; Estidama Pearl; Al Sa'fat 2nd ed. (definitions in 1.8)Jurisdiction/authority, binding instrument/edition/effective date, applicability and exceptions, submission profile, owner, verification date and official source; detail in BBM-STD-85

Decision (BIM Manager, 2026-10-14): 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. Basis: RESEARCH.md distinguishes local applicability and evidence limits S26, S27, S28, S29.

Regional abbreviations remain in the relevant jurisdiction annex only after verification. V0.1 submission lists are prompts, not evidence of a complete current authority package.

Annex fieldFillable example
Authority / scope[competent authority; location/category; appointment; why applicable]
Instrument / edition / date[official title, identifier, effective date and controlled URL/copy]
Required submission[actual package, schema/profile, reviewers, approval stages and conditions]
Responsible owner / currency[authorised role, verified date, next review and change trigger]
Approval / exception evidence[official record; conditions; unresolved queries and affected-use hold]

9.3 Legacy and conflict resolution#

Legacy conflict (BBM-STD-11 change-trace ID)Resolution in this revisionOffice implementation action
C01 AIM/AIR and client-only EIRAIR is requirements; AIM operational information; PIR included; EIR appointment-specific in delivery/operationUpdate dependent definitions and requirement/exchange links without changing signed meaning silently
C02 filename/revision patternsNo universal grammar; default proposal in 1.7, revision/status separateNaming owner approves code lists, project annex, aliases, effective date and migration
C03 RACI versus plansRACI activity allocation differs from TIDP/MIDP container plansActual delivery-plan owners populate schedules/dependencies
C04 native editability / publishMetadata/workflow establish control; software publish is distinctMap actual CDE actions, authorisation and receiver acceptance
C05 worksets and ownershipWorksets support worksharing; no family defaults/security locksVerify project strategy and supported ownership/relinquishment workflow
C06 15/5 mm and zero clashesResolved by: the BBM-STD-50 §3 H/C/A/D/V table is the only tolerance rule; stage values retiredApply BBM-STD-50 rule IDs per pair/zone
C07 90/95/100%, A/B/C and authorityCritical-field denominator and actual powers explicit; gate letters localAdopt scoped quality rules, code legends and exception/resubmission authority
C08 office/TBP custodyOffice glossary owns this revision; private records stay privateGeneric TBP remains freshly authored and separately controlled
C09 aliases/property identitySemantic dictionary and GUID/binding/export mapping requiredProperty owner validates installed mappings; glossary names alone change nothing
C10 coordinates / existing evidenceProvisional and verified information distinct; CRS not reduced to model pointsCoordinate owner records provenance/control and receiving tests
C11 RIBA/LOD/nine phasesEight RIBA stages; many-to-many manual map; LOIN distinctAppointment-specific milestone and information-need schedule
C12/C14 tools/readinessActual build/access/capacity and task evidence requiredVerify installed/operational readiness separately from source guidance
C15/C16 rights/safetyProtocol/appointment and actual technical duty holders governSpecialist particulars and safety/authority evidence; no glossary waiver
C17–C20 content and teaching absolutesContent/graphics/schedules scoped and tested; no indiscriminate cleanup or guaranteed compliancePreserve required data, validate admission/edits, test known examples in installed tools
V0.1 duplicated maintenance/system-analysis sectionsMaintenance tasks/intervals distinct from BMS performance analysisConfirm AIR, maintenance receiver and operational triggers

9.4 Office decisions, review and self-check#

See (Introduction).

See (Introduction).

See (§2.1).

See (§1.7).

See (§1.5).

See (§1.5).

See (§1.7).

See (§1.7).

See (§1.7).

See (§7.1).

See (§9.2).

See (§8.6).

Decision IDDecided office valueActual owner / evidence needed
GLO-D01;Director confirms holder, capacity, controlled master, approval and dates
GLO-D02;Standards and appointment owners; dependent-document and contractual mappings
GLO-D03;Naming owner; code lists, examples, aliases and effective date
GLO-D04;Quality/appointment authority; denominator, check methods and exception powers
GLO-D05;;;Property owner; dictionary and export/tag/schedule tests
GLO-D06Coordination/design authorities and O3 matrix owner; sensitivity test, exclusions and approved pair/zone limits
GLO-D07; (freeze authoring/exporter/checker/receiver builds, presets and profile hashes; upgrade only by tested, approved change);Authority/technical/security owners; current sources, actual installed/receiver tests and exercise results

See (Introduction, change record).

Apply the existing five-step terminology change procedure below with actual authority, alias/migration plan, affected templates, producer/receiver notice and required tool tests.

  1. Submit term, ambiguity, affected decision/documents, recommended meaning and official source/edition. Distinguish factual correction, local choice and contract-specific meaning.
  2. Custodian checks this glossary, RESEARCH.md, the BBM-STD-11 change trace and affected office documents. Technical/security/legal owners review the actual implications in their scope.
  3. Record accepted/proposed/rejected status, approving authority, alias/migration plan and effective revision. No clause number is cited without verified source evidence; none is asserted in this revision.
  4. Update affected templates/guides and project annex references under their ownership. Preserve issued identities and contractual meaning; notify affected producers/receivers and retain previous baseline.
  5. Run semantic examples and actual tool/exchange tests where behaviour is affected. Publish approved vocabulary only after the authorised decision; unresolved drafts remain clearly labelled.
Review testExpected result / acceptance evidence
“AIR contains the operational model”Reject: AIR specifies requirements; AIM holds operational information
“Only the ultimate client sets EIR”Reject: each appointing party sets appointment exchanges; operational exchanges also apply
“RIBA 3 means LOD 300 and a 15 mm tolerance”Reject: stage, LOD convention, LOIN and tolerance are independently specified
“The IDS passed, so access geometry is safe”Reject: IDS checks scoped IFC data; geometry/safety require separate checks and authority
“The native file is editable, so uncontrolled”Reject: CDE workflow, metadata, revision and evidence establish control
“Cloud publish means formally accepted”Reject: product action and formal authorisation/receiving acceptance differ
“Source roster title grants permission to accept”Reject: verify appointment/delegation and access separately through the Directory
“Existing filename is noncompliant because glossary proposes another”Reject: adopted appointment baseline governs; proposals require approved migration
“Schedule row always equals one element”Reject: grouping may aggregate elements; edits can affect model data
Research / gapWhere addressed
T03.1 parties, appointments, teams, PIM/AIM1.2 and sections 2–3 with source editions
T03.2 OIR/AIR/PIR/EIR and legacy terms1.2 and lifecycle diagram; appointment/operation example
T03.3 LOIN versus geometry/development1.3, fillable worked need and 9.1
T03.4 IFC/BCF/IDM/IDS distinctions1.4, comparison diagram and worked exchange
T03.5 edition/jurisdiction/software context1.1, 9.2 and controlled annex template
O01 P1/P2/P3Correct model/requirement/appointment terms and office custody; editions/PIR/LOIN/open exchange; lifecycle map

The generic TBP glossary is a separate lane. No approved revised TBP edition was supplied for this rewrite; no claim of synchronised adoption is made. This office revision uses freshly stated research-backed meanings and identifies dependent owner actions rather than borrowing private text into TBP.

References#

Sources used from RESEARCH.md. Standards references are explanatory scope/edition references; detailed normative clauses were not audited. Archived guidance editions are cited as used, not asserted to be the latest. Undated technical pages are checked against the adopted schema/tool before use.

  • S01 — ISO, ISO 19650-1:2018 — Concepts and principles, 2018. https://www.iso.org/standard/68078.html
  • S02 — ISO, ISO 19650-2:2018 — Delivery phase of the assets, 2018. https://www.iso.org/fr/standard/68080.html
  • S03 — ISO, ISO 19650-3:2020 — Operational phase of the assets, 2020. https://www.iso.org/standard/75109.html
  • S04 — ISO, ISO 19650-4:2022 — Information exchange, 2022. https://www.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/82/78246.html?browse=tc
  • S05 — ISO, ISO 19650-5:2020 — Security-minded approach to information management, 2020. https://committee.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/42/74206.html
  • S06 — ISO, ISO 19650-6:2025 — Health and safety information, 2025. https://www.iso.org/standard/82705.html
  • S07 — ISO, ISO 7817-1:2024 — Level of information need: concepts and principles, 2024. https://www.iso.org/standard/82914.html
  • S08 — BSI, BS EN 17412-1:2020 withdrawal / BS EN ISO 7817-1:2024 replacement record, 2020/2024. https://standardsdevelopment.bsigroup.com/projects/2018-02659; https://knowledge.bsigroup.com/products/building-information-modelling-level-of-information-need-concepts-and-principles-2
  • S09 — ISO, ISO 12006-2:2015 — Framework for classification, 2015. https://www.iso.org/standard/61753.html
  • S10 — NBS, Uniclass — Download tables and change history, July 2026 release (Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27), checked 2026-11-04. https://uniclass.thenbs.com/download
  • S11/S12 — ISO, ISO 16739-1:2024 — IFC: data schema, 2024; buildingSMART International, Industry Foundation Classes, undated version page. https://committee.iso.org/standard/84123.html?browse=tc; https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/
  • S13 — buildingSMART International, BCF 3.0 XML and API, final 18 June 2021 (BCF 2.1, 2017, fallback); https://github.com/buildingSMART/BCF-XML/releases/tag/v3.0, checked 2026-11-04; https://github.com/buildingSMART/BCF-API/releases; https://github.com/buildingSMART/BCF-API/blob/release_3_0/README.md?plain=1
  • S14 — BSI, BS 1192-4:2014 — COBie code of practice, 2014; withdrawn 2022. https://knowledge.bsigroup.com/products/collaborative-production-of-information-fulfilling-employer-s-information-exchange-requirements-using-cobie-code-of-practice
  • S15/S23 — NIBS, NBIMS-US v4 resources, COBie v3 and BEP foreword, v4, live pages undated; COBie V3.0 was published in 2023 as part of NBIMS-US V4 (NIBS version history, https://nibs.org/nbims/v3/cobie/2-7, checked 2026-11-05); the office default stays COBie 2.4 (NBIMS-US V3) unless the EIR names v3. https://nibs.org/nbims/v4/resources/; https://nibs.org/nbims/v4/bep/foreward/
  • S16 — ISO, ISO 23386:2020 — Properties in interconnected data dictionaries, 2020. https://www.iso.org/standard/75401.html?browse=tc
  • S17 — ISO, ISO 23387:2025 — Data templates for objects, edition 2, 2025. https://www.iso.org/standard/85391.html
  • S18/S19 — ISO, ISO 29481-1:2025 — IDM: methodology and format, edition 3; ISO 29481-2:2025 — Interaction framework, edition 2, 2025. https://www.iso.org/standard/88515.html; https://www.iso.org/standard/88516.html?browse=tc
  • S20 — buildingSMART International, Information Delivery Specification, 1.0, final June 2024 (https://github.com/buildingSMART/IDS/releases, checked 2026-11-04). https://www.buildingsmart.org/standards/bsi-standards/information-delivery-specification-ids/
  • S21 — RIBA, RIBA Plan of Work 2020, 2020. https://www.riba.org/work/insights-and-resources/riba-plan-of-work/
  • S22 — IMI Framework (formerly UK BIM Framework, renamed May 2025), Resources, live index including archived Guidance Parts A–F, checked 2026-11-04. https://ukbimframework.org/resources/
  • S37 — IMI Framework (formerly UK BIM Framework, renamed May 2025), Information protocols supporting delivery and operational phases, edition 3, August 2022 (explanatory; current template: Information Protocol for BS EN ISO 19650-2, Ed 6, at https://ukbimframework.org/resources/, checked 2026-11-04). https://imiframework.org/wp-content/uploads/2022/08/Information_protocols_supporting_the_delivery_phase_BS_EN_ISO_19650-2_and_the_operational_phase_BS_EN_ISO_19650-3_of_assets-Guidance_Edition-3.pdf
  • G-A — IMI Framework (formerly UK BIM Framework, renamed May 2025), archived guidance, Guidance A — The information management function and resources, edition 2, February 2021. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-A_The-information-management-function-and-resources_Edition-2.pdf
  • G-C — IMI Framework (formerly UK BIM Framework, renamed May 2025), archived guidance, Guidance C — Facilitating the CDE workflow and technical solutions, edition 1, September 2020. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf
  • G-D — IMI Framework (formerly UK BIM Framework, renamed May 2025), archived guidance, Guidance D — Developing information requirements, edition 2, February 2021. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-D_Developing-information-requirements_Edition-2.pdf
  • G-E — IMI Framework (formerly UK BIM Framework, renamed May 2025), archived guidance, Guidance E — Tendering and appointments, edition 2, February 2021. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-E_Tendering-and-appointments_Edition-2.pdf
  • G-F — IMI Framework (formerly UK BIM Framework, renamed May 2025), archived guidance, Guidance F — About information delivery planning, edition 1, September 2020. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-F_About-information-delivery-planning_Edition-1.pdf
  • P01 — Penn State Computer Integrated Construction Research Program, BIM Project Execution Planning Guide, v2.2, 2019. https://psu.pb.unizin.org/bimprojectexecutionplanningv2x2/front-matter/readers-guide/
  • P06 — NPSA, Security-Minded Approach to Digital Engineering, undated. https://www.npsa.gov.uk/security-best-practices/build-it-secure/security-minded-approach-digital-engineering
  • A02/A03 — Autodesk, Worksharing setup and Cloud Worksharing, Revit 2026 help, 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Collaborate/files/GUID-D9797137-09C7-4F92-AFC3-670202D043E2.htm; https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Cloud/files/GUID-ABFFFEE6-2C6D-4779-B508-A1C4BC0C4885.htm
  • A06 — Autodesk, Create Shared Project Parameters, Revit 2026 help, 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Model/files/GUID-114C68A9-FF2B-4D4C-A2DF-3AE7E1F174C8.htm
  • V04 — RICS, Whole life carbon assessment for the built environment, second edition 2023, updated 2024. https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/construction-standards/whole-life-carbon-assessment
  • V06 — ISO, ISO 22057:2022 — Data templates for EPDs in BIM, 2022. https://www.iso.org/standard/72463.html

Sources checked 2026-11-04#

  • DM-9-1-2 — Dubai Municipality, Circular 9-1-2 on BIM submission, 13 Oct 2023. https://dmpmedia.dm.gov.ae/uploads/2023/10/تعميم-BIM-9-1-2.pdf
  • DM-9-1-3 — Dubai Municipality, Circular 9-1-3, 15 Jan 2026, effective 1 Apr 2026. https://www.dm.gov.ae/wp-content/uploads/2026/02/Circular-9-1-3.pdf
  • DBC — Dubai Municipality, Laws and orders: Dubai Building Code (Decree 45/2021). https://www.dm.gov.ae/municipality-business/laws-and-orders/; Administrative Resolution No. 225 of 2024, 13 Aug 2024. https://www.dm.gov.ae/?p=352286
  • DUBAI-LAW-3-2026 — Government of Dubai, Law No. 3 of 2026 Concerning the Quality and Safety of Buildings, 27 Feb 2026. https://dlp.dubai.gov.ae/Legislation%20Reference/2026/Law%20No.%20%283%29%20of%202026%20Concerning%20the%20Quality%20and%20Safety%20of%20Buildings.html
  • DM-11-9-1 — Dubai Municipality, Circular (11-9-1) of 2026 applying Law No. 3 of 2026, 1 Oct 2026, with guidance manual 11-9-1-1 (May 2026). 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 (checked 2026-11-05)
  • UAE-FLS — UAE Civil Defence, UAE Fire and Life Safety Code of Practice, September 2018. https://www.dcd.gov.ae/portal/preventive-safety/uae-fire-and-life-safety-code-of-practice.jsp
  • ADIBC — DMT, Abu Dhabi International Building Codes 2013 (e.g. ADIMC-2013). https://www.dmt.gov.ae/-/media/Project/DMT/DMT/Codes/3-ADIMC-2013_1-12-2013.pdf
  • ADM-BIM — ADM, BIM Code of Practice, Oct 2020. https://www.dmt.gov.ae/adm/-/media/Project/DMT/ADM/E-Library/0001-Jan-2022-Doc/ADM-BIM-005Code-of-Practice.pdf
  • ESTIDAMA — DMT news, Pearl Rating minimums, 8 Jan 2025. https://www.dmt.gov.ae/en/adm/Media-Centre/News/08Jan2025
  • ALSAFAT — Dubai Municipality, Al Sa'fat Dubai Green Building System, 2nd ed., Jan 2023. https://www.dm.gov.ae/municipality-business/al-safat-dubai-green-building-system/
  • DUBAI-CRS — EPSG registry, EPSG:3997 WGS 84 / Dubai Local TM. https://epsg.io/3997; DMD vertical datum: FIG 2011 paper by DM authors. https://www.fig.net/pub/fig2011/papers/ts08j/ts08j_gopi_alkhatibi_et_al_5058.pdf
  • AD-VDATUM — EPSG registry, Ras Ghumays vertical datum (1146). https://epsg.io/1146-datum
  • PDPL — UAE, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data. https://uaelegislation.gov.ae/en/legislations/1972
  • CTL-2025 — UAE, Federal Decree-Law No. 25 of 2025 Promulgating the Civil Transactions Law, effective 1 Jun 2026. https://uaelegislation.gov.ae/en/legislations/4011
  • REVIT-SUPPORT — Autodesk, Previous versions and Support lifecycle. https://www.autodesk.com/support/account/manage/versions/previous-versions; https://www.autodesk.com/support/account/manage/versions/support-lifecycle; Revit 2027 updates: https://help.autodesk.com/view/RVT/2027/ENU/?guid=RevitReleaseNotes_2027updates_html; IFC exporter releases: https://github.com/Autodesk/revit-ifc/releases
  • IFC-VALIDATION — buildingSMART, IFC Validation Service. https://technical.buildingsmart.org/services/validation-service/
  • ISO12006-3 — ISO 12006-3:2022. https://committee.iso.org/standard/74932.html
  • ISO21597 — ISO 21597-1:2020 and -2:2020. https://committee.iso.org/standard/74389.html; https://www.iso.org/standard/74390.html
  • ISO29481-3 — ISO 29481-3:2022. https://www.iso.org/standard/81261.html
  • ISO19650-DIS — ISO/DIS 19650-1 ed.2, stage 40.93. https://www.iso.org/standard/89703.html
  • PAS1958 — BSI, PAS 1958:2026 Built environment. Data and information standards landscape. Guide, 31 Mar 2026. https://knowledge.bsigroup.com/search?query=PAS%201958
  • ISO42001 — ISO/IEC 42001:2023. https://www.iso.org/standard/42001
  • ISO9001 — ISO 9001:2026 ed.6, 16 Sep 2026. https://committee.iso.org/standard/88464.html
  • ISO27001 — ISO/IEC 27001:2022 + Amd 1:2024. https://committee.iso.org/standard/82875.html
  • ISO55001 — ISO 55001:2024 ed.2. https://www.iso.org/standard/83054.html
  • ISO13567 / ISO128 / ISO7200 — ISO 13567-1/-2:2017 (https://www.iso.org/standard/70181.html; https://www.iso.org/standard/70182.html); ISO 128-1:2020; ISO 7200:2004. https://committee.iso.org/standard/35446.html