ArchHubBABOOMDownload

Office BIM Manual

BBM-STD-01 · V0.7 · 2026-11-05 · This manual defines the standards, methods, and governance needed to deliver coordinated, information-rich BIM across design, documentation, and handover.

Download WordHSI formsSecurity formsAll standards

Ribbon tools that apply it: New Project from Template, Apply BABOOM Standard, Project Info, Rotate / Flip, Align / Distribute, Regions, Lines, Groups, Levels, Translate Notes, Check Names, Auto-Dimension, Batch Tag, BABOOM Export, Revisions, Wipe / Purge, Title Block & Text Check, Clash to BCF, QA Sample, MIDP/TIDP, BABOOM Standard, Egress Paths, Occupant Load, Fire Compartments, Link to Spec Section, Estidama / Al Sa'fat Credits, Energy Model Export

1 INTRODUCTION#

1.1 DOCUMENT CONTROL AND OFFICE ADOPTION#

This manual covers the office's information-management and authoring processes through delivery, handover and operational exchanges within its appointment. It does not claim ISO certification or replace the office QMS, statutory design duties or signed contracts. ISO 19650-1:2018 and ISO 19650-2:2018 establish the information-management basis; ISO 19650-3:2020 addresses operational information. The current research basis is dated 14 October 2026; detailed normative clauses have not been audited.

ControlRecommended value / completion fieldRelease check
Process ownerDecision (BIM Manager, 2026-10-14): The BIM Manager owns the Manual and its maintenance; appoint a distinct deputy with capacity and record actual role holders in the private Directory before activation. Basis: Policy maintenance needs accountable ownership and resources G-A.Office assigns accountable role and deputy
Approval authorityDecision (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.Record approval ID, role, date and scope
Effective date / next reviewDecision (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.Enter actual dates; notify users
Controlled locationDecision (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.Record CDE URI, document ID, revision and approval
Superseded editionDecision (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.No historic issue renamed or overwritten
QMS interfaceLink existing document control, competence, audit, non-conformance and management-review proceduresPopulate actual procedure IDs; no invented accreditation

ISO 9001:2026 is the QMS reference in the research register. Any transition from an existing certified QMS needs the office's own adoption and certification-body arrangements; this draft is not evidence of that transition. Record the adopted edition in the standards register.

Policy and precedence. Applicable law and binding authority requirements must be satisfied. Resolve contractual document precedence using the signed appointment and Information Protocol; do not invent a hierarchy where they disagree. Approved appointment requirements/EIR and the confirmed project BEP/annex govern project-specific technical choices within that hierarchy. The approved office manual provides the baseline; approved software guides implement it. A guide, plugin, browser folder or diagram cannot change contractual obligations. Escalate unresolved conflict to the Lead Appointed Party and contract owner before the affected exchange.

LayerContentChange ownerEvidence before use
Office policyReusable procedures, roles, forms and principlesManual ownerApproved edition and distribution record
Project annex / BEPActual appointment, grammar, dates, requirements, thresholds, tools and recipientsLead Appointed Party with relevant appointing-party approvalsApproved annex IDs and authorised deviations
Software guideExact tested operations for the approved buildTechnical leadRepresentative test and guide revision

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.

1.2 PURPOSE#

This manual defines the standards, methods, and governance needed to deliver coordinated, information-rich BIM across design, documentation, and handover.

Problems solved: inconsistent modeling, naming, and deliverables. unclear roles and gates. variable model health and data completeness.

Audience: project team members producing or consuming BIM. discipline leads. coordinators. reviewers. client representatives.

Outcomes: predictable information drops. consistent drawings and schedules. validated exports for IFC and CDE. clear QA-QC thresholds and acceptance gates.

1.3 SCOPE#

In scope:

Standards and naming conventions

Roles, responsibilities, and RACI

Governance, acceptance gates, and evidence

Information delivery milestones and data drops

Parameters, data dictionaries, and LOIN

Worksets and model partitioning

Graphic standards for documentation

Content and detail libraries

Documentation rules for drawings, schedules, and publishing

Workflows and protocols for modeling, coordination, and issue tracking

Quality standards: model health and data completeness thresholds

Coordination and clash responsibility matrix

Data exchange and IFC export and validation

CDE structure, permissions, and versioning

Glossary and appendices referenced by this manual

Out of scope:

Commercial terms, fees, and contracts

Non-project corporate policies unrelated to BIM delivery

Software procurement and licensing administration

Individual training plans and HR processes

Construction means and methods beyond documented deliverables

Project-specific EIR/BEP content not adopted into this manual (unless cross-referenced)

Acceptance for scope

Every new topic added to the manual must be explicitly mapped to In scope or Out of scope.

Where conflict exists, the explicit lists above override section text.

1.4 DEFINITIONS AND ABBREVIATIONS#

This manual inherits canonical term definitions from the central glossary.

Primary reference: Office Glossary V0.3 (adopt approved edition in the register)

Manual-specific terms below extend or specialize meanings for this manual only.

Initial terms

Acceptance Gate: A formal decision point with criteria and evidence required for A, B, or C acceptance.

Data Completeness: The minimum required population of parameters for a given exchange (LOIN worksheet), discipline, and element class.

Model Health: Quantitative thresholds that indicate model stability and maintainability, measured by agreed metrics.

Uniclass: The classification system adopted for structuring content and metadata across the project.

Policy, project annexes and software instructions govern nine recurring manual phases; they are not nine project stages.

1.5 NINE-PHASE NAVIGATION AND EXIT EVIDENCE#

The phases organise work and repeat when a delivery or operational trigger changes. RIBA Plan of Work 2020 has eight stages, 0–7; there is no automatic phase-to-stage, LOD or clash-tolerance equivalence. Procurement can overlap Technical Design and Manufacturing and Construction. Use the project stage/exchange schedule to allocate services and outputs.

Manual phaseProcedure / form in this manualResponsible functionExit evidence / decision
Intro1.1–1.5; requirements trace 2.5Office management / appointing-party liaisonScope, adopted editions and decision needs recorded
Setup2.2–2.5; 3.1–3.3; 8.1 initiationLead Appointed Party / task-team leadsApproved annex, roles, tested coordinates and mobilisation record
Modeling3.2–3.3; 4–6; 8.2 methodologiesDiscipline leadsPurpose-led information produced; library and borrowing checks
Delivery2.3; 7.3; 11; 12.2Delivery-team authoriserIdentified checked container set and transmittal
Information2.5; 3.2; 11.3Information Manager / data ownersRequirements-to-properties/docs trace and validation
Coordination8.1.5; 10BIM Coordinator / designersVersioned federation, disposition and retest evidence
Discipline4–9; design assurance in 9.4Discipline lead / competent design reviewerDesign, documentation and required-data checks complete
Authority2.1; 2.6; 11.4; 12.4; BBM-STD-85 authority annexAppointed submission / acceptance roleAuthorisation, authority submission and recipient decisions separated
Handover2.5; 11.3; 12.5Asset information owner / operational recipientTested operational ingestion, training, residual risks and update ownership

A link or empty form does not demonstrate completion. Each project records evidence IDs, source revisions, checks, owners and actual decisions against this map.

2 PROJECT STRUCTURE#

2.1 GOVERNANCE AND GATES#

This section defines decision gates, criteria, and evidence required to progress#

Office stage gates (one list, the eight gates in 2.3): Strategic Need / Business Case (RIBA 0); Brief / Information Requirements Approval (RIBA 1); Concept Design Approval (RIBA 2); Coordination Freeze (RIBA 3); Issue for Review (RIBA 4); Verified Construction Information Exchange (RIBA 5, procurement-dependent); Handover Data Acceptance (RIBA 6); Operational Trigger / AIM Update Acceptance (RIBA 7). These are one of three gate families; the basis-of-design gates G0–G5 (BBM-STD-12) and the authority gates (BBM-STD-57 §4) are mapped to them in BBM-STD-93.

Evidence per gate: drawing set snapshot, schedules, model health report, data completeness report, change log since last gate.

Acceptance legend: gate outcomes are letters A = Accepted, B = Accepted with comments, C = Rejected, with meanings per Glossary 1.5. Comments logged with owners and due dates.

Decision authority: Task-team reviewers check and approve sharing; the LAP authorises the delivery-team submission; the appointing party or its delegated recipient accepts the exchange. Design and authority approval remain separate duties. Record actual delegated powers in the project annex; a job title alone grants no gate authority.

Records: Store evidence sets in CDE under the gate folder. Link references in this manual where applicable.

Acceptance for 2.1#

Each active project has a gate calendar and required evidence list per gate.

Every gate outcome has owners, due dates for B/C comments, and storage links in the CDE.

Cross-reference: 2.3 Information delivery milestones

2.2 ROLES AND RESPONSIBILITIES#

Define parties per ISO 19650 and assign accountability using a lightweight RACI.

Core roles: Appointing Party. Lead Appointed Party (LAP). Task Teams per discipline. Information Manager. BIM Coordinator. Discipline Leads. QA-QC Lead. Office roles: BIM Manager (office standards owner, /009). Security Lead. Design Safety Lead. Asset Information Owner / operational safety owner (handover recipient). Office Director (approves office standards). The master responsibility matrix is BBM-STD-55.

Responsibilities:

Appointing Party: sets EIR. approves major gates. accepts deliverables.

LAP: consolidates BEP. plans information delivery. ensures gate evidence.

Information Manager: governs CDE, naming, metadata, permissions.

BIM Coordinator: runs coordination cycles. maintains clash matrix. tracks issues.

Discipline Leads: own model health and data completeness within discipline.

QA-QC Lead: audits against thresholds. logs findings and follow-ups.

BIM Manager: owns this Manual, the Glossary and the office quality framework; proposes office standard changes.

Security Lead: runs the security triage and security management plan (9.4; BBM-STD-87).

Design Safety Lead: owns structured health and safety information during delivery (9.4; BBM-STD-88).

Asset Information Owner: confirms AIR scope and accepts handover information (12.5).

Office Director: approves office standards and their changes.

RACI summary (high level)#

BEP preparation/confirmation: LAP (A/R), task-team leads (R for their commitments), Information Manager and BIM Coordinator (C); appointing party reviews/accepts the response as required by the appointment. Keep receiving acceptance in a separate activity row.

Gate Evidence: LAP (A), BIM Coord (R), Disc Leads (R), QA-QC (C), Appointing (I)

CDE Governance: Info Manager (A/R), LAP (C), All Teams (I)

Coordination & Clash: BIM Coord (A/R), Disc Leads (R), QA-QC (C), LAP (I)

Model Health & Data Completeness: Disc Leads (A/R), QA-QC (C), BIM Coord (C)

Security assessment: Security Lead (A/R), Information Manager (R), LAP (C), Appointing (I)

HSI records: Design Safety Lead (A), Disc Leads (R), Asset Information Owner (C at handover), LAP (I)

Standards change: BIM Manager (R), Office Director (A), Disc Leads and Security Lead (C), All Teams (I)

Acceptance for 2.2#

Named role → named person on the project roster with contact. RACI conflicts resolved.

Each responsibility mapped to at least one measurable check or artifact.

2.3 INFORMATION DELIVERY MILESTONES#

Define when information is produced, who owns it, and the completion rules at each stage.

STAGE MAPPING (RIBA → PROJECT GATES)#

RIBA 0 STRATEGIC DEFINITION → GATE: STRATEGIC NEED / BUSINESS CASE

RIBA 1 PREPARATION AND BRIEFING → GATE: BRIEF / INFORMATION REQUIREMENTS APPROVAL

RIBA 2 CONCEPT DESIGN → GATE: CONCEPT DESIGN APPROVAL

RIBA 3 SPATIAL COORDINATION → GATE: COORDINATION FREEZE

RIBA 4 TECHNICAL DESIGN → GATE: ISSUE FOR REVIEW

RIBA 5 MANUFACTURING AND CONSTRUCTION → GATE: VERIFIED CONSTRUCTION INFORMATION EXCHANGE (procurement-dependent)

RIBA 6 HANDOVER → GATE: HANDOVER DATA ACCEPTANCE

RIBA 7 USE → GATE: OPERATIONAL TRIGGER / AIM UPDATE ACCEPTANCE

REQUIRED DROPS PER STAGE (MINIMUM)#

MODELS: Discipline models current to stage, federated model published, origin and coordinates validated

DRAWINGS: Minimum sheet set per discipline for the stage, title blocks and revisions correct

SCHEDULES: Agreed list with required fields populated to the LOIN worksheet of the exchange (BBM-STD-54)

NON-GRAPHICAL: Parameter exports, COBie (version per EIR, default COBie 2.4) or asset registers as required by EIR

REPORTS: Model health report and data completeness report since last gate

CHANGE LOG: Summary of design changes since previous gate with impacts

OWNERSHIP#

LAP: Confirms completeness of the drop and signs off the pack

DISCIPLINE LEADS: Own discipline deliverables and schedule fields

BIM COORDINATOR: Publishes federated model, runs clash, and records outcomes

INFORMATION MANAGER: Verifies naming, metadata, and CDE placement

CADENCE#

COORDINATION: Weekly during RIBA 3–4. Biweekly at other stages unless project dictates otherwise

PRE-GATE MINI-DROP: 2–3 days before gate for automated checks and comment buffering

FINAL EVIDENCE PACK: Posted to CDE by T-0 (gate day) 09:00 local time

ACCEPTANCE FOR 2.3#

A dated checklist for the next gate is published one week before the gate and includes owners per item

A coordination run is executed within 48 hours before the gate with issues triaged

No mandatory blocking check fails at gate time. Any permissible non-blocking exception has the appointment-defined approval, recipient scope and competent design/safety concurrence recorded.

All naming and metadata validations pass for the drop location in CDE

2.4 CDE NAVIGATION#

Section 12.1 is the maintained folder outline and permissions schedule referenced as 2.4 by legacy procedures. Section 12.4 defines the state/decision workflow. Folder structure is a project implementation. Where a platform differs, use the approved folder/state alias register in 12.4.

2.5 REQUIREMENTS CASCADE AND DECISION TRACE#

Under ISO 19650-1:2018 and ISO 19650-3:2020, OIR states organisational decision needs; PIR states project decisions; AIR states operational asset needs. EIR defines appointment-specific exchanges supporting those needs. Delivery information develops the PIM; accepted operational information supports the maintained AIM. AIR is not an AIM, and an EIR can apply to delivery or operational appointments. Do not assume every office produces or owns the client's OIR/AIR: request and clarify them within the office's scope.

Use the private Office OIR V0.3, Directory V0.3 and Glossary V0.3 as companion review drafts until each is approved. Adopt original generic TBP controls only through an office review and project annex; do not copy private project data into generic TBP. Requirements follow ISO 19650-1/-2; IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance D ed.2 (2021, archived) and Guidance F ed.1 (2020, archived) are explanatory. Information Protocol: IMI template for BS EN ISO 19650-2, Ed 6.

Trace IDUpstream decision / ownerRequirement and purposeAppointment / producerExchange / recipientGeometry; data; documentationAcceptance / evidence
(synthetic example)PIR-P01; design decision owner: confirm room capacityEIR-E01; spatial coordination reviewAppointment A; architectural task teamEX-01 at agreed coordination gate; design reviewerRoom extents; unique room ID, use, area in m²; brief comparison reportEvery in-scope room reconciled to approved brief; omissions/discrepancies dispositioned by decision owner
(synthetic example)AIR-A01; operational owner: plan servicingEIR-E02; handover into AIMAppointment A; equipment producerEX-02 at handover; maintenance recipientEquipment location/access envelope; asset ID, type, service interval/unit; approved O&M document linksRequired maintainable assets and mandatory values valid; recipient import and document-link test recorded
[ID][OIR/PIR/AIR ID, decision, owner][EIR ID, intended use][appointment, task team][exchange ID/date, recipient][objects, precision, properties, documents][rule IDs, report IDs, authorised decision]

For each row, the Information Manager obtains the requirements revision and records exclusions with rationale, confidentiality, source/update owner and receiving capability. Task-team leads derive actual container rows in their TIDP; the LAP reconciles dependencies and receiving review windows in the MIDP. A RACI, bare LOD number or stage label is not a delivery plan or a complete level of information need.

At change: identify affected requirement/use/container/test IDs; assess date, resource, security, safety and operational impacts; seek the governing approval; revise EIR response, BEP/annex, TIDP/MIDP and rule set together. Notify producers and recipients before the next exchange. Preserve the prior approved baseline and the change decision.

2.6 LOCAL REGULATORY BASIS#

Every project records its jurisdiction and the binding instruments before the first exchange. The one edition register is BBM-STD-51 §3; UAE requirement detail is in BBM-STD-85; terms are in Glossary 1.8. There is no UAE federal BIM mandate; BIM submission duties come from the emirate authority.

ControlRequirement (checked 2026-11-04)Evidence in the BEP / project annex
Jurisdiction testDubai / Abu Dhabi / other emirate or free zone; name the permitting authority and master developer for the plotAuthority list, plot reference, date and owner
Dubai building codeDubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 (13 Aug 2024); apply the DBC plus all DM amending resolutions in force at permit submissionResolution list read at submission, source URL and check date
Abu Dhabi building codeThe ADIBC edition published by DMT and in force at project start (2013 edition, Executive Council Resolution 7C 26/2013, at 2026-11-04)Edition and source URL
Fire and life safetyUAE Fire & Life Safety Code of Practice, September 2018 edition, plus the emirate authority's amendments current at project startEdition, amendment list and check date
Rating-system minimumAbu Dhabi Estidama Pearl: private minimum 1 Pearl, government-funded minimum 2 Pearl. Dubai Al Sa'fat 2nd ed. (Jan 2023): Silver Sa'fa mandatory for all new buildingsTarget rating, edition, assessor and the model data it needs (BBM-STD-58/60/61/62, BBM-STD-81)
Permit BIM submissionDubai circulars 9-1-2 and 9-1-3: test applicability and follow 11.4Applicability result and submission profile
Existing-building dutiesDubai Law No. 3 of 2026 (Quality and Safety of Buildings): Building Quality and Safety Certificate after 20 years from completion, procedure in DM circular 11-9-1 of 2026 (ED-DM-11-9-1); an asset-life obligation handed to the operator (12.5; BBM-STD-75/76)Handover note to the asset information owner
Security drawingsFollow the current SIRA/DM requirement for the plot, confirmed at permit stage; classify per BBM-STD-87Confirmation record
Owner and verificationAppointed submission lead with the BIM Manager; re-check at each permit submissionOwner, check date and source URLs

3 PROJECT INFO#

3.1 PROJECT IDENTIFIERS AND CODES#

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.

External containers use the 8-token grammar below; ORG-PROJ-DISC-PHASE-SEQUENCE survives only as a mapped internal WIP alias, never issued, and the PHASE token is retired. External issues use the same Project Naming Register as BEP 8.3. In an approved legacy PHASE list, IFC may mean Issue for Construction; .ifc is a format, never construction permission.

Register fieldRecommended value / exampleValidation / decision evidence
External grammar where recipient supplies noneDecision (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 below. Basis: Adopts the Manual/BEP external candidate and existing Rnn convention consistently; appointment requirements take precedence through one recorded mapping G-C. Authority: code lists in BBM-STD-93; naming rule in Clash matrix section 2.Same register ID/revision in Manual and BEP; confirm token count and dictionaries with recipient
Synthetic valid exampleCLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifcCLIENT CLI; ORG OFF; PROJ P001; whole volume/level ZZ; model M3; architecture A; number 0001; agreed format
Invalid exampleCLI-OFF-P001-ZZ-M3-A-0001.ifcMissing LEVEL token; reject rather than silently reinterpret
Internal model aliasesDecision (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.Map internal ID to external container ID; no two live files claiming one identity
Views / sheetsDecision (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.Validate approved values; libraries and Start View have explicit exceptions
RevisionsDecision (BIM Manager, 2026-10-14): Use R00 for initial WIP, then R01, R02 and never-recycled per-container revisions, expanding digits beyond R99; unchanged containers retain their actual revision; appointment codes override through one approved mapping. Basis: Carries forward O3 Rnn without forcing equal revisions on unchanged content G-C. Decision (BIM Manager, 2026-10-14): Use local SU-WIP = team work, SU-COORD = coordination, SU-INFO = reference, SU-REVIEW = formal review, SU-ISSUE = authorised defined use; record permitted use and recipient acceptance separately; map appointment codes in one register. Basis: The O3 list prevents confusion with S1/S2/S3 severity and RACI G-C, S04.Keep per-container sequence and issue manifest; do not impose equal revision on unchanged sheets
Suitability / stateOffice codes SU-WIP, SU-COORD, SU-INFO, SU-REVIEW, SU-ISSUE (table 3.1.1); appointment code lists override through the BBM-STD-93 mappingA/B/C decisions and RACI are separate legends; no code inferred from extension
MigrationMap prior ID, new ID, reason, effective date, affected references and approverRetain historic issues; rename only future approved containers with alias history

The Information Manager validates token grammar and code-list membership, uniqueness, extension, purpose, revision and state; regex alone does not establish validity. Confirm the annex at mobilisation and whenever appointment requirements change.

ItemSpecification
Naming schema (defaults)- File: CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext - View: DISC-LEVEL-ZONE-TYPE-DESC - Sheet: ROLE-CAT-INDEX - Revision: Rnn per container - Date: YYYY-MM-DD
Examples- File: CLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc - View: ARC-L02-Z03-PLAN-Furniture - Sheet: A-10-101 - Revision: R03
Rules- Use ISO 8601 dates in titles and transmittals - Category block per discipline standard on sheets - Rnn increases per changed container and is never recycled; unchanged containers keep their revision; the pack manifest lists each container's actual revision
Acceptance criteriaQuality checksOwnerEdit criteria
All filenames, views, and sheets validate against 12.3 rulesAutomated regex validation for file/view/sheet tokensInformation ManagerOnly to fix validation failures or after approved standard change
Each changed container has a new, never-recycled Rnn; manifest lists actual revisionsCompare sheet index vs title block revision; flag gaps or regressionsDiscipline LeadRevise only via approved issue workflow; no manual backdating
All dated folders/files use YYYY-MM-DDScan publish pack paths and filenames for ISO date formatInformation ManagerRename through CDE action to preserve history

Naming schema (defaults)#

ContextPatternExampleNotes
Project codeORG-PROJOFF-P001Stable short code used across all assets
File name (external)CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.extCLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc8 tokens, NUMBER 4 digits, lowercase extension
Internal WIP alias (legacy)ORG-PROJ-DISC-PHASE-SEQUENCEOFF-P001-ARC-WIP-W2Mapped one-to-one to the external ID; never issued
View nameDISC-LEVEL-ZONE-TYPE-DESCARC-L02-Z03-PLAN-FurnitureOmit ZONE if not applicable
Sheet numberDISC-CAT-INDEXA-10-101Category block per discipline standard
RevisionRnnR03Per container: R00 initial WIP, never recycled; unchanged containers keep their revision
Date formatYYYY-MM-DD2026-10-14ISO 8601 in titles and transmittals

Acceptance for 3.1#

PHASE tokens are retired from external identity. Governed by 12.3 (Naming and metadata).

All filenames, views, and sheets validate against 12.3 rules

Rnn increases per changed container and is never recycled; unchanged containers keep their revision; the pack manifest lists each container's actual revision

All dated folders and files use ISO 8601 (YYYY-MM-DD)

Cross-reference: 12.3 Naming and metadata

3.1.1 SUITABILITY CODES#

Office codes only. The mapping to client and UK National Annex codes (S0–S7, A, B, CR, P/C revision forms) and to authority profiles is held once in BBM-STD-93; the appointment code list overrides through that mapping and is recorded in the project register.

Office codeMeaning / permitted useCDE stateWho may set it
SU-WIPTask-team work in progressWIPTask-team author
SU-COORDShared for coordinationSharedTask-team lead after check
SU-INFOShared for information / referenceSharedTask-team lead after check
SU-REVIEWShared for review and comment, or submitted for authorisationSharedLAP
SU-ISSUEAuthorised for the defined usePublishedLAP after authorisation

3.2 PARAMETERS AND DATA DICTIONARIES#

Decision (BIM Manager, 2026-10-14): Use 95% valid applicable non-mandatory values as informational progress only; define numerator, denominator, scope and cut-off and report missing/invalid/excluded/not-applicable separately; all applicable mandatory geometry/data/documentation must pass before release. Basis: O3 acceptance forbids averaging away mandatory failures 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.

Required export core properties use the mandatory rule. Exclusions need scope, justification, owner and approval before checks; no failed safety, identity or exchange-mandatory value is hidden in a portfolio average.

Dictionary controlRequired record / recommended mappingTest
Stable property IDDictionary ID, definition, owner, version, shared GUID where applicableMatch GUID and semantics, not display name alone
BindingCategories, instance/type/project scope, required exchange IDsRepresentative placed element, tag, schedule and IFC result
Value schemaType, unit, allowed values, validation, source/update ownerKnown valid/invalid/empty/unit-conversion cases
ClassificationUniclass table and frozen release recorded in annexValidate code and table; do not silently switch quarterly editions
Asset identity aliasesDecision (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.Unique applicable maintainable asset IDs; preserve source identity across issues
Classification aliasesDecision (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.Exact table/code and IFC classification-reference mapping
Export mappingNative parameter ID → IFC entity/property or asset schema field; null semanticsRound-trip into named receiving build and compare with source

Use ISO 23386:2020 for property governance, ISO 23387:2025 for data-template principles, ISO 12006-2:2015 for classification context and the adopted NBS Uniclass release. ISO 7817-1:2024 requires purpose-led geometry, alphanumeric information and documentation; stage-only parameter rows below are starting points requiring exchange-specific qualification. Fire rating is a controlled performance value with evidence, not free text judged merely non-empty. A Boolean audit flag or Export Exclude never substitutes for the underlying check or authorises omitting required content.

ItemSpecification
Core parameter set (defaults)See the core parameter table below (canonical names Classification_Code, Fire_Rating, Asset_ID)
Coverage rules- Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2) - No duplicate parameter names with conflicting types across disciplines - Exports include the fields required by the LOIN worksheet of the exchange
References- 12.3 Naming and metadata - BBM-STD-54 EIR and LOIN - BBM-STD-72 Parameters and classification
Acceptance criteriaQuality checksOwnerEdit criteria
Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2)Automated completeness report by stage and element classDiscipline LeadAdjust only via approved parameter map; record change log
No duplicate parameter names with conflicting typesScan parameter dictionaries per discipline; flag collisionsInformation ManagerRename with prefix/suffix standards; update bindings
Exports confirm fields required by the LOIN worksheet are populatedSpot-check CSV/COBie exports; validate required columnsQA-QC LeadBackfill via schedules or scripts before issue

Core parameter set (defaults)#

ParameterTypeScopeRequired for exchange (LOIN worksheet ID; typical first exchange)SourceLegacy name (mapped alias)Notes
Classification_CodeTextInstance or typeLOIN worksheet; typically from RIBA 2UniclassClassification, ClassificationCode, Assembly CodeWith ClassificationTable, ClassificationTitle, ClassificationRelease
SystemTextInstanceLOIN worksheet; typically from RIBA 3Manual—HVAC, Power, Lighting, etc.
ZoneTextInstanceLOIN worksheet; typically from RIBA 3Manual—Z01, Z02 … when zone splits apply
LevelTextInstanceLOIN worksheet; typically from RIBA 3Model—L01, L02 … align to shared coordinates
Fire_RatingInteger (minutes)TypeWhen the fire strategy is issuedFire strategy / tested assemblyFire Rating, FireRatingPlus Fire_Rating_Standard (text, test standard) and Fire_Rating_Source (document ID/revision); basis UAE FLS Code 2018 and the tested assembly
Asset_IDTextInstanceWhen the client asset register is defined (AIR/EIR)Client registerAsset Tag, AssetTag, AssetIDStable occurrence identifier
Export ExcludeCheckboxInstanceAs neededManual—Exclude from IFC or schedules when true
Model Origin OK?CheckboxProjectFirst exchange (RIBA 2)QA-QC—Ticked only after origin and CRS check passes

Acceptance for 3.2#

Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2)

No duplicate parameter names with conflicting types across disciplines

Export checks confirm the fields required by the LOIN worksheet are populated

3.3 WORKSETS AND MODEL PARTITIONING#

Worksets organise project elements and loading; they are not CAD layers, security permissions or discipline responsibility matrices. Revit system worksets for views/families differ from optional user worksets. Project placement uses the active project workset; a family template/type catalogue does not set future project-workset ownership. Keep only necessary user worksets; browser grouping and view filters manage presentation. Autodesk Revit Help 2026 is the research reference; qualify the adopted release.

  1. Record model/federation boundaries, required user worksets, responsible roles and borrowing rules in the annex. Role ownership means accountability, not a permanently checked-out workset.
  2. Borrow only the elements needed where practical; agree whole-workset checkout and release windows for controlled bulk tasks. Synchronise and relinquish after the task and at team handoff; confirm the colleague can edit the agreed elements.
  3. If editing is blocked, contact the current owner, preserve changes and agree a handoff. Do not force ownership or delete another user's local/cache. Escalate orphan ownership to the administrator using the tested recovery procedure.
  4. Record whether the central model is file-based or supported cloud worksharing. Synchronise, platform Publish and formal CDE authorisation are separate operations. Test restore in an isolated copy and preserve the live model.

Decision (BIM Manager, 2026-10-14): Use only required user worksets: Shared Levels and Grids, Core Modeling, Links by loading group and Imports where needed, with owners/valid exceptions; system/browser documentation groups are not user worksets or security locks. Basis: Retains the shared minimal policy and actual worksharing semantics A02.

These four user worksets are the office decision; Links may be split per linked discipline as the table below allows. The template workset file BBM-STD_WRKST.txt (52 worksets) is regenerated to match in the next template pass.

The Workset1=0 criterion is limited to adopted user-workset policy and in-scope elements, with system elements and valid exceptions reported separately.

Workset templates (per discipline)#

WorksetOwnerNotes
Shared Levels and GridsDiscipline LeadLevels, grids, reference planes. Controlled after coordination gate; named change approval and temporary borrowing, not a security lock
Links — Architecture/Structure/MEPDiscipline LeadExternal model links only. Pinned. Visibility managed by View Templates
Core — ModelingDiscipline TeamPrimary production elements for the discipline
ImportsDiscipline TeamDWG, images, point clouds. Do not leave imported CAD in production worksets

Views and sheets are organised by browser organisation (4.11), not worksets; view worksets are system-managed. Temporary coordination elements live in Core — Modeling or a registered exception.

Partition strategy (mixed, As per BEP documented per model)#

Each model must declare its primary partition basis in the Model Notes view: Floor (L01, L02 …), Zone (Z01, Z02 …), System (HVAC, Power …), or a mix

Mixed models must include a short rule: which categories split by floor, which by zone, which remain global

Naming rules

Floors: L01, L02, LRF (roof). Zones: Z01, Z02. Systems: HVAC, Power, Lighting

View and workset names reflect the split (e.g., ARC-L02-PLAN-Layouts, MEC-Z03-3D-Coord); discipline codes per BBM-STD-93

Rules#

No elements remain on Workset1. All placed elements belong to an intentional workset

Links are pinned and placed on the dedicated Links worksets per discipline

Imports kept on Imports workset and purged or unloaded before issue

Large scope → split model per the declared strategy. Record the split rule in the model’s readme or 2.3 evidence pack

Avoid scope overlap between split models; document handoff boundaries (by level, zone, or system)

Acceptance for 3.3#

Model declares partition basis and workset ownership in Model Notes

0 elements on Workset1 at gate checks

Links pinned and isolated from production elements

No empty or redundant worksets at issue

If mixed strategy is used, handoff boundaries are stated and respected across models

4 REVIT STANDARD#

4.1 LINES#

Category line weights, colours and patterns are set once in the 4.2 Object Styles tables; this section sets what a pen number plots as. MATCHLINE (special): cut weight 6, DASH-DOT-DOT, standard type, no ByElement override.

Acceptance criteriaQuality checksOwnerEdit criteria
No category uses line weight 0 in cutAutomated scan of Object Styles against baselineInformation ManagerAdjust only via standards update; log change
Plans at 1:100: WALLS cut = 8, FLOORS cut = 10Template spot-check on representative viewsDiscipline LeadUpdate view templates if mismatch; do not per-view tweak
Only approved line patterns in issue viewsSearch for non-standard patterns; flag overridesQA-QC LeadReplace with approved patterns; purge only demonstrably unused, non-required content after a protected-copy comparison
Colors are UPPERCASE named or explicit RGB; consistent per rowLint colors in Object Styles; flag mixed casing or ByElementQA-QC LeadNormalize naming; remove ByElement overrides
MATCHLINE uses Dash-Dot-Dot with weight 6Check MATCHLINE type in typical sheetsDiscipline LeadFix in template; avoid per-sheet edits

4.1.1 LINE WEIGHTS#

Revit pen numbers map to ISO 128 line widths (mm, plotted) per view scale. The template Line Weights table uses these values; BBM-STD-66 uses the same widths for DWG plot styles. Confirm by test print before template release.

Pen1:50 and larger1:1001:200 and smaller
10.130.130.13
20.180.180.13
30.250.180.18
40.350.250.18
50.350.350.25
60.500.350.25
70.500.500.35
80.700.500.35
90.700.700.50
101.000.700.50
11–161.001.000.70

Acceptance — 4.1 Lines#

No category uses line weight 0 in cut.

Plans at 1:100 use: WALLS cut = 8. FLOORS cut = 10.

Only approved line patterns are used. No ad-hoc patterns at issue.

Colors use the approved convention: named colors in UPPERCASE or explicit RGB values. Do not mix styles within a single table row.

Special lines: MATCHLINE uses Dash-Dot-Dot with weight 6.

4.2 OBJECT STYLES#

MODEL CATEGORIES#

CATEGORYPROJECTION LINE WEIGHTCUT LINE WEIGHTLINE COLORLINE PATTERN
WALLS28BLACKSOLID
FLOORS210BLACKSOLID
ALL MEP CATEGORIES11GREYSOLID
ALL STRUCTURE CATEGORIES210BLACKSOLID
OTHER CATEGORIES11BLACKSOLID

ANNOTATIONS CATEGORIES#

CATEGORYPROJECTION LINE WEIGHTLINE COLORLINE PATTERN
REFERENCES1REDALIGNING
OTHER CATEGORIES1BLACKSOLID
CALLOUTS1BLACKDASH-DOT-DOT
MATCHLINE6RGB 128-064-064DASH-DOT-DOT
DISPLACEMENT PATH1BLACKDASH
SCOPE BOXES1RGB 128-000-000ALIGNING
GUIDE GRIDS1RGB 000-145-201SOLID

Acceptance — 4.2 Object Styles#

No category uses ByElement color overrides at issue.

Cut representation uses approved cut fills and line weights per table.

Projection weights remain readable at target plot scales.

Colors are either UPPERCASE named colors or explicit RGB values.

MEP vs STR rows use consistent casing and tokens across the table.

4.3 TEXT#

Acceptance — 4.3 Text#

Font family is fixed to the approved project font. No mixed fonts on sheets.

Minimum plotted text height 2.5 mm on all sheets (paper size, annotative/plotted, not scaled by view). Titles 3.5 / 5 / 7 mm per the office lettering table. Same rule in BBM-STD-66 and BBM-STD-67.

Leaders use the standard arrowhead. No freehand styles at issue.

Case rules: sheet title presentation follows the approved title block; stored titles use Title Case as in 12.3 unless the project annex requires another convention. View DESC uses Title Case; general notes use Sentence case.

No text overrides within dimensions or tags; use parameters or view templates.

4.4 DIMENSIONS#

Acceptance — 4.4 Dimensions#

Units display and precision follow the project standard. No mixed unit formats on the same sheet.

Rounding: architectural dimensions round to whole millimeters. No suppressed zeros for millimeters.

Witness gap and extension lines use the approved spacing. No manual graphic edits.

Prefixes and suffixes are standardized; no free-text overrides in placed dimensions.

Spot elevations and levels use the standard type and arrowhead.

4.5 FILL PATTERNS#

NAMETYPESCALEUSAGE
CONCRETE – CAST IN PLACEDrafting1.0Sections and details
INSULATION – RIGIDDrafting1.0Sections and details
EARTHDrafting1.0Below grade cut
BRICK – RUNNING BONDModelDefaultPlans and elevations
TILES – 300x300Model300Plans and elevations

Acceptance — 4.5 Fill Patterns#

Only approved pattern names are used. No ad-hoc or duplicated names.

Drafting patterns used in details and sections only. Model patterns used in model views only.

Pattern scales match published values. No per-view manual scaling.

Cut fills are set in Object Styles or Materials, not overridden ByElement.

4.6 ARROW HEADS#

USETYPE NAMESIZE (MM AT PLOT)NOTES
LeadersARROW – FILLED2.0Default for text leaders and tags
DimensionsDIM – TICK 45°2.0Use on all linear and radial dimensions
Spot elevationsSPOT – OPEN ARROW2.0Consistent across plans and sections
Matchline indicatorsML – CHEVRON2.5Used with MATCHLINE graphics only

Acceptance — 4.6 Arrowheads#

Arrowhead type matches table for leaders, dimensions, and spots.

Printed size is within ±0.1 mm of the specified size at plot scale.

No view-specific overrides of arrowhead types.

4.7 ANNOTATION SYMBOLS#

Acceptance — 4.7 Annotation Symbols#

Only approved families are used; names match table exactly.

All required parameters are populated; no free-text overrides on tags.

Arrowheads and leader types match 4.6.

Symbol sizes plot to standard dimensions across all sheets.

4.8 KEYNOTES#

Spec — 4.8 Keynotes#

Method: Element Keynotes for model categories where applicable. User Keynotes permitted only for legacy details.

Keynote table location: 02-SHARED/05-DOCUMENTS/06-CLASSIFICATIONS/Keynotes.txt; use the approved tab-delimited Revit keynote text schema and tested encoding. CSV may be a source worksheet, not the loaded keynote format

Numbering: Hierarchical numeric codes (e.g., 10.20.30). No alphanumeric mixes.

Maintenance: Changes logged with date, owner, and rationale in the Keynotes change log.

Acceptance — 4.8 Keynotes#

All placed keynotes resolve to current Keynotes.txt with no missing entries.

No free-text in keynote tags. Only codes and descriptions from table.

Deprecated or duplicate codes not present in the issue set.

4.9 START VIEW#

ItemSpecification
PurposePinned Start View used for QA, identifiers, and warnings. Never placed on sheets.
IdentifiersORG, PROJ, DISC, Model file name, Revit version, Date stamp
Audit panelModel Origin OK? Workset1 elements, Warnings count, Link status, File size
Warnings boardTop 5 warning types with counts
Issue bannerNext gate name and date
GovernanceStart View is default on open and uses a locked View Template
Acceptance criteriaQuality checksOwnerEdit criteria
Exactly one Start View named “STD00-STARTING-VIEW” per modelAutomated view name check per modelDiscipline LeadRename via template rule; do not duplicate
Start View is default and uses a locked templateOpen-default check; template lock status scanBIM CoordinatorLock at template; no per-view overrides
Audit panel fields are current at issuePre-issue audit refresh and screenshotQA-QC LeadUpdate via script or schedule; no manual text
No uncropped 3D or heavy graphics in Start ViewView type and crop checkDiscipline LeadAdjust template; avoid per-view tweaks

4.10 TITLE BLOCKS#

Spec — 4.10 Title Blocks#

Family naming: BBM-G-TTB-A0, BBM-G-TTB-A1, BBM-G-TTB-A2, BBM-G-TTB-A3 (ISO 5457 sizes; published library series under the BBM-STD-69 §2 grammar). A1, A2 and A3 title blocks must exist in the office template; A2 and A3 are created in the next template pass

Mandatory fields (ISO 7200:2004 data fields plus ISO 19650 metadata): Project Name, Project Code, Container ID (external 8-token grammar), Sheet Number, Sheet n of N, Sheet Title, Discipline, Scale, Drawn/Checked/Approved with Approved-by date, Revision, Date of issue, Suitability code, CDE state, Purpose of issue, Document type, Language, North point (plans), Consultant licence/stamp zone

Field list and sheet layout detail: BBM-STD-67 V0.2 §2 is the controlled superset of this list

Bilingual option: Secondary language line allowed below Sheet Title, same font size, lighter weight

Revision system: Rnn per sheet container; it increases only when the sheet changes and is never recycled; unchanged sheets keep their revision; cloud visibility per View Template

Seals and approvals: Reserved zones at lower right; never overlap issue stamps

Acceptance — 4.10 Title Blocks#

Correct title block family for sheet size; no edited duplicates

All mandatory fields populated; no placeholder text on issue

Revision stamp equals the sheet's own Rnn in the pack manifest and appears in title block and index

No manual moved borders or unlocked geometry; family remains unmodified

4.11 BROWSER ORGANIZATION#

4.11.1 VIEWS#

Spec — 4.11.1 Views

Root folders by discipline: 3-letter codes from BBM-STD-93: ARC, STR, MEC, ELE, LSC, PLU, FLS, INT, CIV, SUR, QTY, CON, GEN; use only those the project needs

Purpose subfolders per discipline:

COORD — Working coordination views (no sheets)

DOC — Sheet production parent views

DETAIL — Detail drafting views

QA — Model checks and audit views

SHT-PREP — Sheet prep views with tags and scopes

Tokens in view names: <DISC>-<LEVEL/ZONE>-<TYPE>-<DESC>

Examples: ARC-L02-PLAN-Layouts, STR-L03-SECTION-Framing, MEC-L01-3D-Coord

Sorting: Browser organization by Discipline > Purpose > Level/Zone > Type

Acceptance — 4.11.1 Views#

No orphan views at root. All non-template views live inside a purpose subfolder.

View names conform to token pattern with valid DISC and TYPE tokens.

COORD views are not placed on sheets. DOC model views provide issue parents; approved details, schedules, legends and dependent views have recorded exceptions.

QA/browser groups include the Start View and gate checks; record the approved view types and exceptions.

4.11.2 SHEETS#

TYPENUMBER PATTERNMINIMUM CONTENTNOTES
PlansA-10-XXX (ARC) / S-10-XXX (STR) / M-10-XXX (MEC)Title, north arrow, scale, dims, tags, levels, grids, keynotesUse DOC templates only; no COORD views on sheets
SectionsA-20-XXX / S-20-XXX / M-20-XXXCut markers, levels, materials, keynotes, dimsCut graphics per 4.1 and 4.2
ElevationsA-30-XXX / S-30-XXXLevels, materials, tags, keynotesMatch object styles and fill patterns
DetailsA-40-XXX / S-40-XXX / M-40-XXXDetail components, dims, notes, keynotesUse DETAIL views only; drafting patterns per 4.5
SchedulesA-50-XXX / M-50-XXXApproved schedule fields, filters, legends if requiredSchedules sourced from parameters per 3.2
General notesA-01-001Approved notes blocks, symbols, abbreviationsLinked to 4.15 Notes and 4.7 Symbols
Acceptance criteriaQuality checksOwnerEdit criteria
Correct title block family for sheet size (A0/A1/A2/A3)Scan placed title block family namesDiscipline LeadReplace via template; no custom duplicates
All mandatory fields populated (4.10)Automated title block parameter auditQA-QC LeadBackfill before issue; no placeholder text
Each sheet's Rnn matches its title block and the pack manifestCompare sheet index and title block revisionInformation ManagerRevise only via approved issue workflow
No manual geometry edits to title blocksFamily lock status and instance checksQA-QC LeadFix in family; avoid per-sheet tweaks
Only approved issue views and recorded exceptions placed on sheetsBrowser path check for placed viewsBIM CoordinatorReassign views; COORD views forbidden on sheets
DisciplineSheet numberSheet titlePrimary view
ARCA-10-101Level 01 — General Arrangement PlanARC-L01-PLAN-Layouts
STRS-20-201Section — Core Wall at Grid BSTR-ALL-SECTION-Framing
MECM-50-501Mechanical Equipment ScheduleMEC-ALL-SCHEDULE-Equipment

Placement rules#

One primary view per sheet except schedules-only sheets.

Key plans required on plans and elevations; scale noted per 4.3 Text.

Legends reused from 4.14; no duplicated one-off legends.

Start View is never placed on sheets (see 4.9).

Only approved annotation symbols (4.7) and arrowheads (4.6) allowed.

4.12 VIEW TEMPLATES#

TEMPLATE NAMEVIEW TYPEPURPOSEKEY SETTINGS
DOC - Plan 1-100Floor PlanSheet productionGraphics per 4.1/4.2. Text heights per 4.3. Tags on. Halftone links. Section/elevation markers on. Scale 1:100
DOC - SectionSectionSheet productionCut patterns per 4.5. Line weights per 4.1. Reference tags on. Depth cue off. Scale 1:50 or 1:100
DOC - ElevationElevationSheet productionObject styles per 4.2. Pattern display per 4.5. Key plans on via legend. Scale noted per sheet
DETAIL - 1-5 / 1-10Drafting ViewDetailsDrafting patterns only. Text and dims per 4.3/4.4. No model categories visible
COORD - 3D Clash3D ViewCoordinationSection box on. Links by discipline visible. Categories simplified. Colors by system where applicable
QA - AuditSchedule + 2DModel checksSchedules for warnings, Workset1, link status. Plain graphics. No annotations
SHT-PREP - ParentAnySheet prepAnnotations on. Reference tags controlled. Matchline type set per 4.1/4.6

Locking and governance#

All issue views must use a locked template. No per-view overrides at issue.

Template names are canonical. Do not duplicate with variant spellings. View, view-template and filter names never contain ":" (Revit rejects it); use " - " as separator and write scales as 1-100.

Changes to office templates are proposed by the BIM Manager and approved by the office director; project-local template changes are approved by the Information Manager. Log in 1.1 and archive in 04-ARCHIVE/01-STANDARD-UPDATES.

Acceptance criteriaQuality checksOwnerEdit criteria
100% of issued views report a valid templateTemplate usage audit by view listBIM CoordinatorFix misassigned views before issue
No per-view graphic overrides at issueOverride scan on issued viewsQA-QC LeadNormalize in template; purge overrides
Template names match the table above exactlyName lint against canonical listInformation ManagerRename or consolidate variants; update references

4.13 FILTERS#

FILTER NAMESCOPERULES (EXAMPLE)PURPOSE
QA - Workset1 OnlyAll viewsWorkset = Workset1Detect stray elements before issue
DOC - Hide LinksDOC parentsCategory = Revit Links → OffSheet graphics clarity where links are not needed
COORD - Discipline IsolationCOORD viewsCategory = Non-discipline categories → OffFocus by active discipline during coordination
QA - Elements Without Classification_CodeDOC parentsClassification_Code = EmptyCheck classification coverage per 3.2
QA - Elements Without KeynoteDOC parentsKeynote = EmptyCheck keynote coverage per 4.8
DOC - Phasing - Existing HalftoneSheeted viewsPhase = Existing → Halftone + Thin linesConsistent phasing convention
Acceptance criteriaQuality checksOwnerEdit criteria
Only approved filters in issued viewsFilter-name lint against table aboveQA-QC LeadConsolidate variants; update templates
QA filters present in QA viewsSpot-check QA view templatesBIM CoordinatorAdd to template; do not per-view tweak
Phasing and keynote checks pass prior to issuePre-issue report exported and filed in 2.3 evidenceDiscipline LeadFix underlying data, not filters

4.14 LEGENDS#

LEGEND NAMEAPPLIES TOREQUIRED FIELDSNOTES
Legend — SymbolsAll sheetsApproved annotation symbols per 4.7Place on first plan sheet of each discipline set
Legend — Line TypesPlans, SectionsLine pattern, weight, color tokensMust reflect 4.1 / 4.2 tables exactly
Legend — HatchesSections, DetailsPattern name, type (Drafting/Model), scaleMatches 4.5 Fill Patterns; no per-view scaling
Legend — Key PlanPlans, ElevationsZone and level markers, sheet highlightConsistent location and size across sheets
Acceptance criteriaQuality checksOwnerEdit criteria
Legend names match canonical listName lint against table aboveInformation ManagerRename variants; update templates
Only one instance of each legend per sheetDuplicate legend scanQA-QC LeadConsolidate; remove duplicates
Legend scales and symbols plot to standard sizePrint preview spot-checkDiscipline LeadAdjust in template; avoid per-sheet tweaks

4.15 NOTES#

NOTES BLOCKAPPLIES TOCONTENT RULESGOVERNANCE
General Notes — DisciplineDiscipline front sheetsNumbered list. Sentence case. No inline overrides. Use approved symbols per 4.7Owned by Discipline Lead. Changes logged in 04-ARCHIVE/01-STANDARD-UPDATES
AbbreviationsFirst sheet of each setTwo-column table: Term, Definition. Aligns with central glossary in 13Information Manager maintains canonical list; deltas mirrored to 13
Keynote IndexAs requiredAuto-generated from Keynotes.txt. No free-text editsQA-QC Lead validates against 4.8 before issue
Revisions and Issue NotesAll sheetsRnn format, per sheet; increases only on change, never recycled. No manual backdatingInformation Manager compares with sheet index during pack build
Acceptance criteriaQuality checksOwnerEdit criteria
No mixed fonts or manual overrides in notesStyle scan per 4.3 TextQA-QC LeadNormalize via templates; remove direct formatting
Abbreviations match glossaryDiff abbreviations vs 13 GlossaryInformation ManagerUpdate glossary or notes, then re-publish
Revisions table matches title block and indexAutomated pack comparisonInformation ManagerFix via issue workflow only

5 CAD STANDARD#

TOPICSTANDARDSETTING / MAPNOTES
UnitsMetric (mm)Project Units: Length = mm, Angle = degreesNo mixed units on sheets; see 4.4 Dimensions
CoordinatesShared Coordinates; project CRS = authority CRS by EPSG codeDubai (BBM-STD-86 key CRS-DXB): DLTM, EPSG:3997, vertical datum DMD (no EPSG code). Abu Dhabi (key CRS-AUH): the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, vertical datum Ras Ghumays. Record vertical datum, units m/mm, rotation, survey control points (≥3) and the transform to the local origin in BEP §8.2 / BBM-STD-86 before the RIBA 2 exchange; never hard-code a CRS“Model Origin OK?” parameter ticked at RIBA 2 (3.2)
Layer namingISO 13567-1/-2:2017 profile defined in BBM-STD-66Mandatory fields agent / element / presentationBBM-STD-66 governs DWG work; this section governs Revit import/export only
Drawing conventionsISO 128-1:2020 via BBM-STD-66 / BBM-STD-67Line widths per 4.1.1—
DWG ImportByLayer mappingLayers → Categories map v2.0 (BBM-STD-66 grammar; v1.0 legacy for projects already using it) stored in 02-SHARED/05-DOCUMENTS/02-STANDARDSImports placed on Imports workset; purge before issue
DWG ExportCustom export setupExportTable-DWG-v2.0.txt (v1.0 legacy, BBM-STD-66)Lineweights and colors align to 4.1/4.2
Line typesPer 4.1/4.2Matchline = Dash-Dot-Dot, wt=6No ByElement overrides
FontsPer 4.3 TextSingle project font familyNo mixed fonts on issue
TitleblocksPer 4.10BBM-G-TTB-A0/A1/A2/A3No geometry edits; parameters mandatory
Acceptance criteriaQuality checksOwnerEdit criteria
All DWG imports isolated on Imports worksetCategory + workset scanDiscipline LeadPurge unused; unload before issue
Export uses approved DWG mapExport preset name checkBIM CoordinatorUpdate preset in template; do not per-model tweak
Coordinates validated at initiationStart View audit panel screenshotQA-QC LeadRecord in 2.3 evidence pack

6 LIBRARIES#

6.1 CONTENT LIBRARIES#

TOPICSTANDARDSETTING / FIELDNOTES
NamingORG-DISC-CAT-TYPE-DESC-vNNFamily Name, Type NameTokens align to 3.1 and 12.3; no spaces around dashes
ClassificationUniclassParameter: Classification_Code (+ Table/Title/Release)Required per the LOIN worksheet of the exchange
Parameters — CorePer 3.2Classification_Code, System, Zone, Level, Export ExcludeBound at instance or type as specified in 3.2
Information needPer BBM-STD-54 LOIN worksheet for the exchangeGeometry, alphanumeric, documentationNo over-modeling; maintain lightweight symbols
MaterialsApproved set onlyMaterial Name, AppearanceNo project-specific ad-hoc materials in library families
ConnectorsDiscipline rulesMEP connectors typedSystems, units, and directions validated
VisibilityView discipline awareSubcat + visibility statesSheet graphics match 4.1/4.2; no masking hacks
Library structure02-SHARED/08-PROJECT-LIBRARY00-TTB-AND-COVER, 01-GENERAL, 02-ARC …Per 12.1 tree; read-only except curators
Acceptance criteriaQuality checksOwnerEdit criteria
100% of issued families include core parameters per 3.2Parameter presence and type auditInformation ManagerBackfill map; log changes in 01-STANDARD-UPDATES
Classification_Code populated where the LOIN worksheet requires itClassification coverage reportDiscipline LeadUpdate via schedules before issue
No rogue materials or subcategoriesMaterials and subcat lintQA-QC LeadNormalize to approved set; purge only demonstrably unused, non-required content after a protected-copy comparison

Examples — naming

Furniture Chair: ORG-ARC-FUR-CHAIR-Visitor-v01

Diffuser Square: ORG-MEC-AIR-DIFF-SQ600-v02

6.2 DETAIL LIBRARIES#

TOPICSTANDARDSETTING / FIELDNOTES
NamingDET-DISC-CAT-INDEX-DESCView Name, Sheet RefIndex numeric, e.g., 401, 402 …
SourceDrafting ViewsDetail groups curatedNo model geometry inside detail views
HatchesPer 4.5Drafting patterns onlyNo per-view scaling
LineworkPer 4.1/4.2Categories + subcategoriesNo ByElement color overrides
KeynotesUser Keynotes allowedLegacy details onlyPrefer Element Keynotes where possible
Location02-SHARED/08-PROJECT-LIBRARY00-TTB-AND-COVER, 01-GENERAL, 02-ARC …Read-only; curated by Discipline Lead
Acceptance criteriaQuality checksOwnerEdit criteria
All library details pass 4.1, 4.5 checksGraphics lint on sample setQA-QC LeadFix in source views; no sheet fixes
Keynotes resolve to table with no missing entriesKeynote resolution scanDiscipline LeadUpdate Keynotes.txt; avoid free-text
Detail naming pattern consistentName lint vs patternInformation ManagerRename to standard; update references

7 DOCUMENTS#

7.1 DRAWING SET COMPOSITION#

DISCIPLINEMINIMUM SHEETS (STAGE 3)MINIMUM SHEETS (STAGE 4)NOTES
ARCA-10 GA Plans L00–LRF, A-30 Elevations x4, A-20 Key Sections x2+ A-40 Details x10, A-50 Schedules: Doors, Windows, FinishesPlans at 1:100 baseline; details 1:5/1:10
STRS-10 Framing Plans key levels, S-20 Sections x2+ S-40 Typical Details x8, S-50 Rebar SchedulesCoordinates validated vs ARC grids
MEPM-10 HVAC GA L00–L02, E-10 Power GA L00–L02+ M/E-50 Equipment and Fixture SchedulesSystem legends placed per 4.14

Assembly rules#

Each sheet contains exactly one primary view except schedule-only sheets.

Sheet numbers and titles follow 4.11.2 and 3.1 token rules.

Legends: Symbols and Key Plan per 4.14 on first sheet of each set.

Revisions are per sheet container; each changed sheet gets a new Rnn and unchanged sheets keep theirs (3.1, 4.10).

Acceptance criteriaQuality checksOwnerEdit criteria
Minimum list per stage is present per disciplineSheet index diff vs stage templateDiscipline LeadAdd missing sheets before issue
Sheet titles and numbers match token patternsRegex validation per 12.3Information ManagerRename via templates; no manual hacks
Legends placed correctly on required sheetsLegend presence scanQA-QC LeadInsert from standard legends; no duplicates

7.2 SCHEDULES AND LEGENDS#

SCHEDULEREQUIRED FIELDSFILTERS / GROUPINGNOTES
DoorsMark, Type, Width, Height, Fire_Rating (min), Fire_Rating_Standard, Classification_CodeOnly placed elements. Group by LevelFire_Rating populated when the fire strategy is issued
WindowsMark, Type, Width, Height, Glazing, Classification_CodeOnly placed elements. Group by LevelSizes as built-in parameters; no text overrides
Room/Space DataName, Number, Level, Area, System (MEP), ZoneExclude not placed. Group by ZoneZone required at RIBA 3+
Equipment (MEP)Mark, Family, Type, System, Level, Classification_Code, Asset_IDExclude unplaced. Group by SystemAsset_ID required when the client asset register is defined
Material Takeoff (STR)Category, Type, Volume/Area, LevelExclude demo. Group by CategoryUnits per 4.4; precision fixed per template

Legends linkage#

Legends used by schedules must be sourced from 4.14 canonical legends.

No schedule-embedded symbol images; use legends for symbology.

Acceptance criteriaQuality checksOwnerEdit criteria
Required fields present with correct data typesField-schema audit vs 3.2Information ManagerAdjust in template; backfill data before issue
No text overrides in schedule cellsOverrides scanQA-QC LeadFix parameters; do not override cells
Grouping and filters match table abovePreset comparisonDiscipline LeadUpdate preset only; document change in 1.1

7.3 PUBLISHING AND REVISIONS#

A) Issue pack workflow (from T−3 days to T day)#

T−3 days: Pre-gate mini-drop to SHARED

LAP announces scope and recipients

BIM Coordinator runs clash and Start View audits

Discipline Leads address B/C items from last gate

T−2 days: Freeze candidates

DOC parent views reviewed and locked via templates

Naming and metadata validation (12.3) on prospective pack

T−1 day: Dry-run build in restricted WIP staging; retain the final container IDs for validation

Build pack with date folder name: YYYY-MM-DD-DESCRIPTION

Verify sheet index, title blocks, revisions, legends

T day 09:00: Final build and transmittal

Build final pack in its stage folder of 03-PUBLISHED (12.1)

Generate transmittal and post evidence

B) Pack build checklist (minimum)#

Folder

Name format: YYYY-MM-DD-DESCRIPTION

Children present: 00-COVERSHEETS, 01-DRAWINGS, 02-MODELS, 03-SCHEDULES, 04-REPORTS, 05-TRANSMITTAL

Drawings

Sheet index present and matches placed sheets

Title blocks: mandatory fields filled; correct family size

Legends: Symbols and Key Plan placed as required

Each changed container has a new Rnn; unchanged containers keep theirs; manifest lists actual revisions

Models

Federated model current; links pinned; section box states per template

Start View present and default; audit panel refreshed

Schedules

Required schedule fields per 7.2; no text overrides

Reports

Model health KPIs and clash report from last 48h

Data completeness report per discipline

Transmittal

Recipient list, purpose, and distribution codes

File list with immutable CDE versions and sizes; use hashes where the platform allows them, retaining equivalent immutable identity evidence otherwise

C) Revision rules#

Legacy internal revision token: Rnn with nn as zero-padded integer; external code list follows 3.1 / BEP 8.3

Revisions increase monotonically per changed container under the approved register; unchanged containers retain their revision in the issue manifest

Clouding visibility controlled by template, not per-view

Sheet title blocks and sheet index must match each sheet's own revision in the pack manifest

No manual backdating; corrections issued as new revision with change note

D) Transmittals#

File: PDF transmittal + optional CSV manifest

Includes: Project code, pack date, description, recipients, confidentiality, file table

Location: 05-TRANSMITTAL inside the dated pack folder

Acceptance criteriaQuality checksOwnerEdit criteria
Pack folder name matches YYYY-MM-DD-DESCRIPTIONRegex check on pack root folder nameInformation ManagerRename via CDE action only
Children 00–05 subfolders exist with required contentPack structure scanBIM CoordinatorAdd missing folders; re-export as needed
Title block fields complete; sheet index consistentAutomated title block + index comparisonQA-QC LeadFix via template or parameters; no manual text
Each container's Rnn matches index, title block and manifestRevision coherence auditInformation ManagerResolve by reissue as new Rnn; never backdate
Evidence set posted (health, clash, completeness)Presence check in 04-REPORTSBIM CoordinatorRegenerate within 48h window before issue
Transmittal present with recipients and file listTransmittal parse for required fieldsLAPUpdate recipients or description; preserve date

8 WORKFLOWS & PROCEDURES#

8.1 PROTOCOLS#

8.1.1 PROJECT INITIATION PROTOCOL#

Inputs

EIR or brief, appointing party contacts

Project codes and naming tokens (3.1)

Initial folder tree baseline (12.1)

Steps (T0 = project kickoff)

T0−5 to T0−3: Setup and codes

Information Manager confirms ORG-PROJ codes and naming tokens (3.1)

Create CDE root skeleton per 12.1 with README placeholders

T0−3 to T0−2: Coordinates and templates

Establish Survey Point, Project Base Point, and True North from the project CRS (authority CRS by EPSG code, vertical datum, units, rotation, ≥3 control points, transform to local origin) recorded in BEP §8.2 / BBM-STD-86 (see 5)

Create and pin Start View; set as default (4.9)

Load approved templates: View Templates, Title Blocks, Legends (4.10–4.14)

T0−2 to T0−1: Parameters and worksets

Bind core parameters per 3.2 across seed models

Create default worksets per discipline (3.3) and assign owners

T0: Kickoff and publish "INIT PACK"

Post kickoff agenda, BEP draft location, and contacts in SHARED/05-DOCUMENTS

Run initial model audits (warnings, Workset1, links) and screenshot Start View

T0+5: Validation checkpoint

QA-QC Lead verifies naming, templates, parameters, and Start View compliance

Record deltas and actions in 00-PROJECT-LOG and 01-STANDARD-UPDATES if needed

Deliverables

Seed models by discipline with Start View, templates, parameters, and worksets

CDE skeleton per 12.1 with README exceptions placeholders

INIT PACK notes and initial audits in SHARED

Acceptance criteriaQuality checksOwnerEdit criteria
Survey Point, Base Point, True North set and documentedStart View audit panel screenshotBIM CoordinatorAdjust via template; capture evidence in SHARED
Core parameters bound per 3.2Parameter binding reportInformation ManagerUpdate shared parameter file; log changes
Default worksets exist and have ownersWorkset list and ownership checkDiscipline LeadAlign to 3.3; remove redundant worksets
Templates and legends loaded from approved setTemplate name lint vs 4.12 listQA-QC LeadReplace variants; keep canonical names

8.1.2 COMMUNICATION PROTOCOL#

Purpose

Define who communicates what, where, and by when to keep decisions traceable and aligned with gates (2.1) and CDE structure (12.1).

Channels and purpose

CDE (authoritative): Decisions, issues, transmittals, evidence packs

Email: External notices and formal approvals, linked back to CDE RECORD

Coordination platform: Issue tracking and clash items, linked to CDE paths

Meetings: Decisions and action items posted to 00-PROJECT-LOG within 24h

Message taxonomy

Decision: Single-sentence decision + rationale + link to evidence

Action: Verb-first task with owner, due date, and acceptance criteria

Info: Reference only; include CDE path and version or date stamp

SLAs (working hours, local time)

Routine queries: respond within 1 business day

Gate-critical questions (T−3 to T): respond within 4 working hours

RFI or authority requests: acknowledge same day, target response within 3 business days unless specified

Records and traceability

All decisions and transmittals filed under 02-SHARED/07-RECORD with date-prefixed filenames

Meeting minutes saved to 02-REG/05-MOMS for formal forums; action items mirrored to 00-PROJECT-LOG

Use ISO 8601 dates and Rnn references when tied to issue packs

Acceptance criteriaQuality checksOwnerEdit criteria
Decisions include rationale and CDE linkRandom sample of weekly decisionsInformation ManagerUpdate format template if recurring gaps
Action items have owner and due dateAction list audit in 00-PROJECT-LOGDiscipline LeadsAssign before meeting close; track slippage
Gate-critical questions met 4-hour SLA during T−3..TResponse time report around gatesBIM CoordinatorEscalate to LAP if SLA breached
Minutes posted to CDE within 24hMOMs timestamp checkMeeting chairPost draft within 12h; finalize by 24h

8.1.3 IMPORTING PROTOCOL#

Purpose

Bring external references into models safely without polluting production worksets or violating graphics and naming standards.

Supported inputs and defaults

DWG: Units = mm. Colors = ByLayer. Import as link where possible

Images/PDFs: For tracing or markups in working views only

Point clouds: received as E57 (version recorded) with registration/accuracy report; indexed to RCP/RCS for Revit; link only, shared coordinates validated (BBM-STD-77)

Steps

Pre-flight in CDE

Verify source file name complies with 12.3 naming. Store under 02-SHARED/07-RECORD/01-IN

Confirm coordinate basis and units with sender or metadata

Staging model and workset

Open staging or working file. Set active workset = Imports (3.3)

For DWG: Link instead of import when feasible. If a scoped import is required, retain the original and review layers/units in staging; do not automatically explode. Exploding requires a documented need and before/after check, and is forbidden in the production model

Clean and map (DWG)

Review regapps, xrefs and unused layers in a controlled staging copy. Preserve required reference geometry/provenance and compare the cleaned result before admission

Apply ByLayer mapping per 5 CAD Standards. Lineweights align to 4.1/4.2

Place and pin

Place links on Links or Imports worksets as applicable. Pin all links

For point clouds, align via shared coordinates. Document shift if any

Visibility control

Use View Templates to control Imported Categories. No ByElement overrides

Handover to production

Copy necessary reference geometry only via controlled methods. No exploded DWGs in production categories

Before issue

Unload or purge Imports workset. Confirm 0 imported elements in production worksets

Forbidden

Exploded DWG in production models

ByElement color or lineweight overrides for imported content

Unpinned external links

Acceptance criteriaQuality checksOwnerEdit criteria
All imports live on Imports or Links worksetsWorkset + category scanDiscipline LeadMove or purge; re-link if needed
No exploded DWGs in production categoriesImported Categories and element category scanQA-QC LeadRemove and replace via mapped content
DWG mapping matches approved tableExport/import map verificationInformation ManagerUpdate 5 CAD mapping; log change
Point clouds aligned to shared coordinatesShared coordinates check and Start View noteBIM CoordinatorRe-register clouds; capture evidence
Imports unloaded or purged before issuePre-issue purge reportDiscipline LeadUnload, purge, or segregate to staging

8.1.4 PUBLISHING PROTOCOL#

Purpose

Standardize how drawings, models, schedules, and reports are packaged and issued to ensure consistency, traceability, and compliance with naming and revisions.

Inputs

Approved DOC parent views using locked templates (4.12)

Sheet list per 7.1 and schedules per 7.2

Revision intent and description for the pack

Evidence reports: model health, clashes, data completeness

Steps (aligns with 7.3 A–D)

Prepare the pack

Confirm required views use locked templates and pass override scans

Verify legends and key plans are present where required

Validate sheet numbers, titles, and tokens per 3.1 and 4.11.2

Build staging pack

Create a dated staging candidate in restricted WIP. Promote the verified identified set to its stage folder in 03-PUBLISHED only after the 12.4 authorisation and acceptance workflow

Export PDFs for sheets to 01-DRAWINGS. Export federated model to 02-MODELS

Export schedules to 03-SCHEDULES in CSV or PDF as agreed

Add evidence and metadata

Place model health, clash, and completeness reports to 04-REPORTS

Insert README with pack summary in 00-COVERSHEETS or 05-TRANSMITTAL

Finalize and transmit

Run revision coherence audit. Ensure Rnn matches sheet index and title block

Generate transmittal and place in 05-TRANSMITTAL

Notify recipients per Communication Protocol with CDE links

Post-issue housekeeping

Lock the pack folder structure. Move any superseded drafts to 04-ARCHIVE with cross-link

Update 00-PROJECT-LOG with issue reference and deltas since previous pack

Rules

One pack per date folder. Never overwrite an issued pack

Revisions increase monotonically per changed container under the approved register; unchanged containers retain their revision in the issue manifest. Corrections require new Rnn

Only approved DOC issue views and recorded schedule/legend/detail/dependent-view exceptions may be placed on sheets. COORD views are not issued by default

Acceptance criteriaQuality checksOwnerEdit criteria
Pack structure and naming match 7.3 and 2.4Folder regex + children checkInformation ManagerFix names via CDE; do not rename locally
All issued views use locked templates, no per-view overridesTemplate usage + override scanBIM CoordinatorNormalize in template; purge overrides
Revision coherence across index and title blocksAutomated Rnn auditQA-QC LeadRebuild and reissue; no backdating
Evidence set complete within last 48hPresence and timestamp check in 04-REPORTSBIM CoordinatorRegenerate evidence and reattach
Transmittal includes recipients, purpose, and file listTransmittal parseLAPAmend metadata; preserve pack date

8.1.5 COORDINATION PROTOCOL#

Purpose

Run predictable, timeboxed coordination cycles that reduce rework and feed gate evidence (2.1, 2.3).

Cadence and forums

Weekly during RIBA 3–4. Biweekly otherwise unless project dictates

Forums: Discipline huddles → Cross-discipline review → Issue triage

Inputs

Federated model updated to latest SHARED models

Open issue list from last cycle with statuses

Change log since previous cycle

Steps

Pre-coordination (T−24h)

BIM Coordinator updates federated model and runs baseline clash sets

Discipline Leads push latest SHARED models and schedules

Session (T)

Review top clashes by severity and system, assign owners and due dates

Record decisions and actions per Communication Protocol

Capture screenshots or viewpoints for evidence

Post-coordination (T+24h)

Publish clash report and updated issue list to 02-SHARED/06-REPORTS/02-CLASHES

Update 00-PROJECT-LOG with summary and deltas

Escalate blockers to LAP if due dates risk gate

Rules

Only SHARED models enter federated model. No WIP links

Severity matrix defined per project. Blocking clashes must be resolved/retested; only permissible exceptions may be accepted by the authorised recipient with competent designer/safety concurrence

Issue statuses: Open → In Progress → Ready for Review → Closed. No direct Open → Closed transitions

Acceptance criteriaQuality checksOwnerEdit criteria
Federated model uses only latest SHARED discipline modelsLink path and timestamp checkBIM CoordinatorRelink to SHARED; remove WIP links
Critical clashes trend downward cycle-to-cycleSeverity trend chartDiscipline LeadsFocus next cycle scope; escalate persistent items
100% issues have owner and due dateIssue list completeness auditInformation ManagerAssign owners during session; no unowned issues
Evidence posted within 24h of sessionPresence and timestamp in 02-CLASHESQA-QC LeadPublish summary; link viewpoints

8.2 METHODOLOGIES#

8.2.1 MODELING METHODOLOGIES#

Purpose

Ensure consistent, efficient modeling that supports documentation, coordination, and data exchange without over-modeling.

Principles

Model to the LOIN worksheet of the next exchange (3.2; BBM-STD-54)

Separate modeling, documentation, and coordination concerns via worksets and view templates (3.3, 4.12)

Prefer native elements and families over detail lines and filled regions in model views

Setup

Start from the approved seed model with Start View and templates loaded (4.9, 4.12)

Declare partition basis in Model Notes: Floor, Zone, System, or mixed, and record boundaries (3.3)

Bind core parameters per 3.2 and verify on representative categories

Modeling rules by stage

RIBA 2: Primary massing, grids, levels, major systems placeholders. Classification_Code populated for modeled elements

RIBA 3: Spatial coordination fidelity. Systems, zones, and levels populated. No temporary overlaps at gate

RIBA 4: Constructible geometry for documented elements. Fire_Rating and Asset_ID-bearing elements prepared per the fire strategy and client register

Graphics and data

Use View Templates for all working views. No per-view overrides at issue (4.12)

Populate parameters through schedules wherever possible. No text overrides in tags or schedules (7.2)

Apply classification and system tags per discipline. Avoid duplicate parameter names across files (3.2)

Performance and maintenance

Keep warnings below project threshold. Resolve high-impact warnings weekly

Purge unused families and materials prior to gate; never purge template assets

Split models if scope exceeds thresholds; document split rule in Model Notes and 2.3 evidence

Do and don’t

Do pin links, use coordination views, and follow matchline rules (4.1, 4.6)

Don’t leave elements on Workset1. Don’t place COORD views on sheets

Acceptance criteriaQuality checksOwnerEdit criteria
Model Notes declare partition basis and boundariesPresence check in Model Notes viewDiscipline LeadUpdate notes; align browser folders
0 elements on Workset1 at gateWorkset1 schedule = 0QA-QC LeadReassign or delete; recheck
Template usage = 100% for issued viewsTemplate usage auditBIM CoordinatorFix misassignments; purge overrides
Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2)Completeness report by element classInformation ManagerBackfill via schedules; log deltas
Warnings below threshold and no critical types persist > 1 cycleWarnings trend vs thresholdDiscipline LeadResolve or escalate; record waivers

8.2.2 FAMILY CREATION METHODOLOGIES#

Purpose

Create consistent, lightweight, and data-ready families that comply with graphics, parameters, and naming standards.

Naming and versioning

Family Name: ORG-DISC-CAT-TYPE-DESC-vNN (approved library convention; not the external container grammar)

Type Names: Clear size or option tokens only. No free text beyond tokens

Increment vNN on any geometry or parameter schema change (6.1)

Required parameters and bindings

Core parameters per 3.2 bound at the correct scope:

Instance: System, Zone and occurrence identifiers where meaningful; Classification_Code and Export Exclude follow the dictionary/category binding. Do not impose one binding on every family category

Type or Instance as appropriate for discipline rules

Discipline parameters: add only if referenced by schedules or tags. Avoid duplicates across libraries

Geometry and LOIN

Model to the LOIN worksheet of the exchange (BBM-STD-54). Avoid over-modeling and tiny face details

Use subcategories to control visibility in view templates (4.12). No masking hacks

Place reference planes with proper origins. Flex critical dimensions across typical types

Materials and graphics

Use approved Materials only. No ad-hoc materials in library source

Linework follows 4.1 and 4.2. No ByElement overrides

Plan/elevation symbolic lines sized to plot correctly per 4.3 and 4.6

Connectors (MEP)

Typed connectors with correct systems, flow units, directions, and loss coefficients where applicable

Test system propagation and schedule fields in a sandbox project before release

QA and publishing workflow

Author in library workspace; set preview type and visibility states

Flex types. Run parameter presence audit and purge only demonstrably unused, non-required content after a protected-copy comparison subcategories and materials

Graphics check at target plot scales in DOC templates

Publish to 02-SHARED/08-PROJECT-LIBRARY under the correct discipline folder (12.1). Record vNN and change note

Do and don’t

Do include meaningful Type Catalogs for large size sets

Do centralize shared parameters and keep GUIDs stable

Don’t hard-code text labels that belong to tags or schedules

Acceptance criteriaQuality checksOwnerEdit criteria
Naming follows ORG-DISC-CAT-TYPE-DESC-vNNName lint vs 6.1 patternInformation ManagerRename to standard; update references
Core parameters present with correct scopesParameter presence and scope auditQA-QC LeadRebind via shared parameter file; log change
Graphics pass at target plot scalesTemplate print preview in DOC viewsDiscipline LeadAdjust subcats or symbolic lines; avoid overrides
No rogue materials, subcategories, or ByElement overridesMaterials and subcat lintQA-QC LeadNormalize to approved set; purge only demonstrably unused, non-required content after a protected-copy comparison
MEP connectors propagate systems correctly (if applicable)Sandbox system propagation testDiscipline LeadFix connector types and directions; retest
Published to correct library path with vNN notePath and README check in 02-SHARED/08-PROJECT-LIBRARYInformation ManagerMove and annotate change; update index

8.2.3 PROJECT INITIATION METHODOLOGY#

Objective

Stand up a project BIM environment that is coordinates-correct, standards-compliant, and ready for modeling and documentation within five working days of kickoff.

Scope of workstreams

Governance setup: Roles, RACI, gate calendar and evidence (2.1, 2.2, 2.3)

CDE scaffold: Folder tree per 12.1 with READMEs and permissions guardrails (12.1)

Technical baseline: Coordinates, Start View, templates, parameters, worksets (4.9, 4.10–4.15, 3.2, 3.3)

Communication: Channels, SLAs, decision and action logging (8.1.2)

Timeline and checkpoints (T0 = kickoff)

T0−5.. T0−3: Codes and CDE

Confirm ORG-PROJ tokens (3.1). Create CDE skeleton (12.1). Draft READMEs and default permissions

T0−3.. T0−2: Coordinates and templates

Establish Survey Point, Base Point, True North from the recorded project CRS (5; BBM-STD-86). Load View Templates, Title Blocks, Legends

T0−2.. T0−1: Parameters and partitioning

Bind core parameters (3.2). Create discipline worksets and Model Notes for partition basis (3.3)

T0: Kickoff and INIT PACK

Publish INIT PACK to SHARED. Record audits and decisions. Set Start View default (4.9)

T0+5: Validation

QA-QC runs naming, template, parameter, and Start View checks. Capture evidence to RECORD

Roles and responsibilities

Information Manager: CDE scaffold, naming governance, permissions, READMEs

BIM Coordinator: Coordinates, Start View, template lock, clash presets

Discipline Leads: Worksets, partition strategy, initial checks, schedule seeds

LAP: Sign-off on readiness to start production

Artifacts and locations

INIT PACK: 02-SHARED/07-RECORD with audits and screenshots

CDE README set: Each top folder with exception fields (12.1 D)

Parameter map and shared parameters: STANDARDS under SHARED

Model seeds: 00-PIM/01-WIP/<NN-DATA-TYPE>/<NN-DISCIPLINE> per 12.1

Quality controls and acceptance

Acceptance criteriaQuality checksOwnerEvidence
Shared coordinates established and documentedStart View audit panelBIM CoordinatorScreenshot in INIT PACK
Templates loaded and locked for DOC viewsTemplate usage and lock scanInformation ManagerReport in INIT PACK
Core parameters bound per 3.2Parameter presence reportInformation ManagerCSV/PDF in INIT PACK
Worksets created, owners assigned, 0 on Workset1Workset list + schedule checkDiscipline LeadsChecklist in INIT PACK
CDE mirrors 2.4. READMEs present where exceptions existTree diff vs canonical outlineInformation ManagerDiff report in RECORD

Risks and mitigations

Late coordinates: use labelled provisional local coordinates only for an approved limited purpose. Coordinate owner controls the later transform; test affected links/exports and record the change before survey/construction reliance.

Template drift: Lock templates and prohibit per-view overrides at issue (4.12)

Parameter collisions: Single source of truth for shared parameters. Prefix discipline-specific variants

Handover to production

LAP signs readiness. Teams may commence modeling only after INIT PACK acceptance and all critical checks pass

Any deltas after T0+5 are tracked as 01-STANDARD-UPDATES with rationale and links to impacted sections

9 QUALITY STANDARD#

9.1 QUALITY MANAGEMENT#

Purpose

Define how information quality is planned, executed, and governed across the project so information is reliable at every gate. This section is the BIM and information part of the office quality management system: the office policy, scope, process map and RACI are in BBM-STD-96, the office procedures (proposals, project quality plan, design review per discipline, coordination, specifications, sustainability, authority submissions, supervision, document control, nonconformity and lessons, client feedback, audit, management review, subconsultants) are BBM-STD-97 QP-01 to QP-15, and the quality objectives are the KPIs of BBM-STD-98.

Roles and cadence

BIM Manager: Owns the office quality framework and its continuous improvement. Information Manager: Runs it per project, including audits and corrective actions

QA-QC Lead: Runs checks, compiles reports, tracks corrective actions

Discipline Leads: Ensure conformance within discipline models and sheets

BIM Coordinator: Automates checks, aggregates results, and monitors trends

Practice director: Owns the office QMS and chairs the management review (BBM-STD-96 §4). The BIM Manager's framework above is the information-quality part of it.

Cadence: Weekly during active design. Pre-gate intensives at T−3, T−2, T−1, and T day

Plan–Do–Check–Act (PDCA)

Plan: Define thresholds, acceptance criteria, and checklists per section 2.3 and 7.3

Do: Apply templates, naming, parameters, and workflows per sections 3–8

Check: Run automated audits and targeted reviews; log deltas and owners

Act: Correct issues, update standards if systemic, record 01-STANDARD-UPDATES

Quality artifacts

Quality Plan excerpt in BEP referencing this manual

KPI dashboard: model health, data completeness, clash trends, template adherence

Audit library: scripts, filters, and checklists versioned in SHARED/05-DOCUMENTS/02-STANDARDS

Office checklists: 07-QA-QC, one workbook per area: 01-BIM (BBM-STD-68-CHECKLIST), 02-DESIGN-REVIEW, 03-PROPOSALS, 04-SPECIFICATIONS, 05-SUSTAINABILITY, 06-SUBMISSIONS, 07-SUPERVISION, 08-DOCUMENT-CONTROL, 09-AUDIT (with the BBM-STD-98 KPI register)

Acceptance criteriaQuality checksOwnerEvidence
KPI dashboard updated weeklyLast-updated timestamp within 7 daysBIM CoordinatorScreenshot in 06-REPORTS/00-PLANNING
Quality Plan aligned to gatesCross-check vs 2.3 gate evidence listInformation ManagerPlan PDF in 02-STANDARDS
Findings assigned with due datesAction register completenessQA-QC Lead00-PROJECT-LOG items with owners

9.1.1 OFFICE QMS AND IMPROVEMENT RECORD#

Decision (BIM Manager, 2026-10-14): Review QMS performance quarterly and at material incident using actual controlled procedure IDs and evidence for overdue actions, rejected exchanges, recurring defects, security incidents and correction effectiveness. Basis: Management review tests effectiveness rather than attendance P04.

QMS procedures: document control BBM-STD-97 QP-10; subconsultants and suppliers QP-15; competence BBM-STD-82; nonconformity, corrective action and lessons learned QP-11; internal audit QP-13; management review QP-14 (quarterly and at material incident, as decided above). Inputs per ISO 9001:2026 9.3.2 include changes in the needs and expectations of interested parties.

Finding ID / sourceRequirement / affected revisionsCause and corrective actionOwner / due dateRetest and independent reviewerEffectiveness / closure decision
[NC ID; audit/recipient/incident][rule ID, container IDs/revisions][root cause, correction and recurrence prevention][role/person, date][known failure case, result, evidence URI][monitoring period, recurrence check, approving role/date]

Keep approved changes in the standards register with affected annex/guide IDs, training needs and rollback/version history. Pilot a changed rule on representative isolated content before office-wide adoption. Verify effectiveness after release rather than closing an action when a script was merely edited.

9.2 QUALITY CONTROL#

Model health thresholds (typical baselines)

Warnings: 0 warnings from the blocking list WRN-01..WRN-11 at share; all other warnings ≤ 100 per 10,000 model elements and no type above its count at the previous gate without a disposition; total recorded at each gate (BBM-STD-68 §2.1)

Workset discipline: 0 elements on Workset1 at gate. Links pinned and isolated

File hygiene: No imported DWG in production categories. Unused families and materials purged before gate

Performance: per 11.3 targets (open ≤ 120 s, sync ≤ 60 s, IFC export ≤ 180 s for the representative seed); file-size investigation trigger stated per model class in the annex; software releases and builds per BBM-STD-91

Data completeness thresholds

Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2)

Naming and tokens: 100% file/view/sheet names pass 12.3 regex and BBM-STD-93 code-list checks

Keynotes: 100% placed keynotes resolve to table (4.8)

Drawing set QC

Template adherence: 100% issued views report locked templates (4.12)

Legends and symbols: Required legends present. Only approved symbols and arrowheads used (4.14, 4.6, 4.7)

Title blocks: Mandatory fields populated. Revisions coherent across index and sheets (4.10, 7.3)

QC workflow

Pre-check in working models with QA views and filters (4.13)

Discipline pass: fix local issues, update schedules and parameters

Consolidated pass: BIM Coordinator runs scripts and compiles delta list

Sign-off: Discipline Leads confirm fixes. Information Manager validates naming and CDE placement

Acceptance criteriaQuality checksOwnerEvidence
Warnings below thresholdWarnings report vs baselineDiscipline LeadReport in 06-REPORTS/01-MODEL-HEALTH
Mandatory applicable requirements: 100% valid; non-mandatory coverage target per approved annex (3.2)Completeness by class and stageInformation ManagerCSV + chart in 06-REPORTS
Naming and tokens 100% validRegex pass for files/views/sheetsInformation ManagerValidation log in 06-REPORTS
Issued views use locked templatesTemplate usage audit = 100%BIM CoordinatorAudit in 04-REPORTS of the pack

9.3 QUALITY ASSURANCE#

Purpose

Provide independent oversight to ensure QC is effective, evidence is complete, and standards evolve with learning.

Activities

Independent audits each stage against acceptance criteria in sections 2–7

Evidence sampling: validate a subset of sheets, models, and schedules against source requirements

Process audits: verify that Publishing and Coordination Protocols were followed (8.1.4, 8.1.5)

Continuous improvement: log 01-STANDARD-UPDATES with rationale and impact analysis

Audit scope and sampling

Decision (BIM Manager, 2026-10-14): Independently review min(total sheets, max(10, ceiling(10% of total sheets))) per discipline plus every safety-critical/changed high-risk item; mandatory-field checks cover the full applicable scope. Basis: Risk-based visual sampling supplements complete mandatory validation P04, S04.

Retain the existing additional model/federation and schedule-type sampling requirements below.

At least one model per discipline plus the federated model

At least one schedule per required schedule type

Non-conformance and corrective action

NC-1 (blocking): Blocks gate; resolve and retest. Exceptions require the appointment-defined authority and competent design/safety concurrence; mandatory legal or safety duties cannot be waived by the LAP.

NC-2 (conditional): Only non-blocking comments within expressly accepted scope; track owner, due date and receiving conditions in 00-PROJECT-LOG

NC-3 (minor): Cosmetic; backlog with owner. These NC codes are separate from gate A/B/C and RACI A/C.

All NCs (information, design, site, authority rejection, client complaint) are recorded in the one office NC log of BBM-STD-97 QP-11; corrective action requires a root cause and an effectiveness check.

Acceptance criteriaQuality checksOwnerEvidence
Independent audit completed each stage100% of applicable audit checklist items dispositioned; sampling scope recordedQA-QC LeadSigned checklist in 06-REPORTS
All NC-1 items closed or authorised permissible exceptions recordedNC register statusLAP + Information ManagerNC log and waivers in RECORD
01-STANDARD-UPDATES logged with impactChange log completenessInformation Manager01-STANDARD-UPDATES entries

9.4 LIFECYCLE SECURITY AND HEALTH/SAFETY INFORMATION#

ISO 19650-5:2020 and NPSA security-minded digital-engineering guidance require proportionate sensitivity-led controls. ISO 19650-6:2025 provides the structured health and safety information basis. These procedures support competent design, construction and operational safety processes; a model check, slope parameter or clash pass does not establish compliance with all applicable codes.

Interfaces: office ISMS (ISO/IEC 27001:2022 + Amd 1:2024 where certified or adopted); security triage (outcomes and SensitivityClass values per BBM-STD-87 §2) and security management plan per ISO 19650-5 in BBM-STD-87; structured H&S information per ISO 19650-6:2025 in BBM-STD-88; personal data in directories, occupancy and CCTV/BMS data handled under the UAE PDPL (Federal Decree-Law No. 45 of 2021, effective 2 Jan 2022) and any executive regulations listed on uaelegislation.gov.ae at project start, or the free-zone law where the project sits in a free zone (rules in BBM-STD-90 §4); retention per BBM-STD-90. Security-system drawings follow the current SIRA/DM requirement for the plot, confirmed at permit stage.

FunctionRecommended office accountabilityRequired project evidence
Security governanceDecision (BIM Manager, 2026-10-14): Assign office Security Lead with project IT/data owners to sensitivity, access, suppliers, distribution, retention and incidents; record actual competent holders/delegation before access. Basis: Security governance continues through operation and disposal S05, P06.Sensitivity assessment, approved distribution/retention, supplier and incident controls
Safety information governanceDecision (BIM Manager, 2026-10-14): Assign competent Design Safety Lead during delivery and appointed asset/operator safety owner at handover; record hazards/objects/locations, source revision, controls, reviewer, residual owner and receiving acknowledgment. Basis: Structured safety information does not transfer designer/duty-holder duties S06.Requirements, competent discipline reviewers, structured residual-risk transfer and receiving acknowledgment
Production / maintenanceTask-team leads create/update records; Information Manager controls exchange metadataSource revision, location/object IDs, changed records and access policy
Release / receivingLAP authorises submission; delegated appointing-party/operational recipient acceptsSeparate documented decisions within appointment scope

Security procedure. Before choosing sharing tools, assess whether asset/information disclosure, aggregation, incorrect change or loss could cause harm. Record sensitivity by dataset and recipient, consequence, legal/contract restrictions and controls; restrict assessment details themselves. Approve least-privilege role access and supplier conditions, then test allowed and denied read/write/download routes. Record induction/awareness and joiner/mover/leaver changes; review access at each gate and when the team/asset sensitivity changes. Use approved protected transfer/storage; never put sensitive input into an unapproved plugin, AI service or public test upload.

At an incident, users report immediately to the security lead through the approved channel; preserve evidence, contain access with IT, identify affected revisions/recipients, and let the designated legal/security authority decide notifications. Restore only a verified baseline; record corrective action and retest. At retention expiry or authorised offboarding, remove access, address downloaded copies and backup/legal-hold constraints, and retain deletion/disposition evidence. Do not set a universal retention duration without the appointment and records schedule; design records are kept at least 10 years after handover plus the 3-year claim period (decennial liability, Federal Decree-Law No. 25 of 2025 Art. 821/824; Federal Law 5/1985 Art. 880 for contracts signed before 1 Jun 2026), with the final schedule ruled by the legal owner in BBM-STD-90 §3.

SEC recordDataset / sensitivity and consequenceRecipient / minimum permissionControls / verificationRetention / removalOwner / review / incident route
[ID][asset/information scope, rationale][role, organisation, read/write/download][approved platform, allowed/denied test IDs][trigger, duration, hold, disposal authority][role, next review, protected reporting channel]

Safety procedure. At briefing, identify decision-specific safety information and responsible designers. At each design/coordination change, update structured records and trace them to objects, zones and controlled documents. A competent reviewer verifies significance, evidence, proposed controls and residual-risk communication before sharing. At construction/handover, verify current condition/provenance and transmit outstanding risks to the appointed recipient and operational owner; record acknowledgment, understanding and update responsibility. At replacement, inspection, incident or decommissioning, reopen relevant records and update the AIM and associated documents.

HSI record IDHazard / location / objectCause / consequence / lifecycle activitySource revision / uncertaintyControl / designer and reviewerResidual risk / action ownerExchange / recipient acknowledgment
SYN-H01 (synthetic)Restricted maintenance access; equipment EQ-01Service activity in confined access zone; unsafe access if clearance lostCoordination model R01; access method awaiting approvalCompetent designer confirms access envelope and maintenance method; review record requiredRecheck after layout change; operational safety owner receives remaining restrictionsEX-02; date, recipient decision and linked approved method
[ID][hazard, zone, stable ID][cause/event/consequence, stage/trigger][document/model revision, known limits][prevention/control, competent reviewers][remaining risk, owner, due date][exchange ID, evidence, decision/date]

Release check: all in-scope significant safety records have a responsible owner, reviewed control/residual-risk decision, current location/document links and authorised recipient. Unresolved mandatory safety requirements block the affected exchange; an information-manager waiver cannot remove design duties.

Decision (BIM Manager, 2026-10-14): Use 1–5 likelihood × 1–5 impact for information-delivery risk; scores 15–25 require escalation and competent residual-risk disposition before affected release; any unresolved mandatory failure blocks release regardless of score; specialist design/safety methods remain separate. Basis: The office scale defines escalation without replacing specialist assessment P04, S06.

Record declared likelihood/impact definitions, escalation authority, mitigations and residual risk in the risk register.

Risk IDCause → event → consequenceCategory / linked requirementsInitial evaluationMitigation / owner / due dateResidual evaluation / acceptanceReview trigger
SYN-R01Survey not approved → assumed coordinates reused → wrong recipient alignmentTechnology/dependency; EX-01Pending project assessmentCoordinate owner approves controls and recipient transform test before external releaseRecord reviewer and residual decision; no fictitious scoreNew survey, model split or coordinate change
[ID][cause, event, consequence][resource, requirement, security, safety, dependency][method/score][action, owner, date][score, competent authority, evidence][date/event]

10 COORDINATION AND CLASH#

10.1 CLASH MATRIX AND RESPONSIBILITY#

Purpose

Define who is responsible for preventing, detecting, and resolving clashes by discipline, system, and interface.

Clash responsibility matrix

InterfacePrimary ownerSecondary ownerNotes
ARC vs STRSTRARCStructure governs penetrations and tolerances. ARC coordinates openings
ARC vs MEP (HVAC)MEPARCMEP routes within ARC zones and clearances. ARC provides ceiling and shaft constraints
STR vs MEP (all)MEPSTRMEP requests openings. STR approves size and placement
MEP internal (MEC vs ELE vs PLU)MEP system ownerMEPSystem owner resolves internal conflicts before cross-discipline review
ARC vs FLSARCFLSFire and life-safety clearances prevail. FLS flags violations; ARC resolves routes
ARC vs LSC (Landscape)ARCLSCInterfaces at podium, planters, paving and drainage; ARC coordinates levels and waterproofing

Severity and SLAs

Severity 1 Critical: Blocks construction or design intent. Resolve/retest pre-gate; any permissible residual exception requires authorised recipient and competent design/safety approval. SLA: 2 working days

Severity 2 Major: Impacts coordination or documentation. SLA: 5 working days

Severity 3 Minor: Cosmetic or low impact. SLA: before next gate

Clash rules of engagement

Federated model sources: Only latest SHARED models allowed (2.4, 8.1.5)

Tolerances: Apply approved rules by pair, purpose, zone, units and source revisions. Do not mark an intersection or safety/access failure harmless merely because it falls inside a numerical threshold; disposition and retest are required (11.3).

Ownership: Primary owner proposes fix. Secondary owner concurs. Escalate to LAP if stalemate

Evidence: All Severity 1 and 2 clashes require a viewpoint, comment, and proposed action

Acceptance criteriaQuality checksOwnerEvidence
Clash matrix published and referenced in BEPPresence and link checkInformation ManagerMatrix table in this section + BEP link
Severity definitions applied consistentlySample of 20 issuesQA-QC LeadIssue list annotation
Only SHARED models in federated setLink path auditBIM CoordinatorReport in 06-REPORTS/02-CLASHES

10.2 COORDINATION CYCLES#

Purpose

Establish a predictable loop of coordination that reduces rework, drives decisions, and produces evidence for gates (2.1, 2.3).

Cycle types

Weekly cycle (design stages RIBA 3–4)

Biweekly cycle (other stages unless project dictates)

Pre-issue mini-cycle (T−2..T day, aligned with 7.3 and 8.1.4)

Inputs and prerequisites

Federated model composed from latest SHARED discipline models (12.1)

Open issues from prior cycle with status and owners (10.3)

Change log since previous cycle and agenda published 24h in advance

Standard agenda (time-boxed 60–90 minutes)

Roll-call and scope confirmation (5 min)

Review of metrics trend (warnings, critical clashes, data completeness) (10 min)

Top clashes by severity and system with owner updates (20–30 min)

Interfaces review per Clash Matrix (10.1) (10–15 min)

Decisions and actions, due dates, and escalations (10–15 min)

Wrap: confirm evidence posting and next steps (5 min)

Evidence and posting rules

Within 24h, publish: clash report, viewpoints, metrics snapshot, and action list to 02-SHARED/06-REPORTS/02-CLASHES

Update 00-PROJECT-LOG with decisions and deltas since last cycle

Tag items blocking the next gate as Gate-Critical in the issue tracker

Tools and configurations (baseline)

Clash test sets by discipline and interface, versioned with rule-set ID

Color by system where applicable; section boxes standardized for typical zones/levels

Viewpoint naming: <SEV>-<DISC/CROSS>-<ZONE/LEVEL>-<SHORTDESC>-YYYYMMDD

Acceptance criteriaQuality checksOwnerEvidence
Cycle held per cadence with agenda and minutesCalendar vs minutes posted within 24hBIM CoordinatorMOMs + 00-PROJECT-LOG entries
Metrics snapshot attached each cyclePresence of snapshot filesQA-QC LeadReports in 02-CLASHES
Gate-Critical items flagged and trackedIssue fields contain Gate-Critical tagInformation ManagerIssue list export
Evidence posted within 24hTimestamps within windowBIM CoordinatorFolder timestamps

Interlocks

Uses owners and interfaces defined in 10.1 Clash Matrix

Feeds Publishing checklist in 7.3 and evidence in 2.3

Aligns with Coordination Protocol 8.1.5 for steps and SLAs

10.3 ISSUE TRACKING#

Purpose

Track, triage, and close coordination and quality issues with clear ownership, dates, and evidence, feeding gates and publishing (2.1, 2.3, 7.3).

Tracker fields (minimum schema)

FieldTypeRequired?Notes
IDAuto or short codeYesMonotonic per project. Used in filenames and viewpoints
TitleTextYesVerb-first and concise, e.g., "Resize opening at Grid B2"
DisciplineSelectYes3-letter code from BBM-STD-93 (ARC, STR, MEC, ELE, LSC, PLU, FLS, INT, CIV, SUR, QTY, CON, GEN)
OwnerPersonYesSingle accountable individual
SeveritySelectYesS1 Critical, S2 Major, S3 Minor (10.1)
StatusStatusYesOpen → In Progress → Ready for Review → Closed
Due dateDateYes (S1/S2)Per SLA (below)
Gate-CriticalCheckboxConditionalTrue if blocks upcoming gate (2.3)
Location (CDE path)Text / URLYesExact 12.1 path to affected artifact
Linked itemsRelationOptionalSheets, models, viewpoints, RFIs
EvidenceFile / URLYes at Ready/ClosedScreenshot, viewpoint, report excerpt

Open: New item with owner and severity set. Due date required for S1/S2

In Progress: Owner actively working. Provide interim comment or sketch if change is non-trivial

Ready for Review: Fix implemented. Attach evidence and list impacted files/views/sheets

Closed: Reviewer confirms acceptance; reference commit, export, or sheet rev if applicable

Forbidden: Open → Closed without Ready for Review

SLAs

S1 Critical: acknowledge within 4 working hours. Due in 2 working days unless waived (10.1)

S2 Major: due in 5 working days

S3 Minor: due before next gate

Views and reporting

Board view grouped by Status for standups

Table view filtered to Gate-Critical = true during T−3..T window

Weekly export of open items to 02-SHARED/06-REPORTS/02-CLASHES with timestamp

Governance and evidence

Every Closed item must have evidence attached and CDE path updated

Gate packs include an extract of Gate-Critical items and their outcomes (7.3)

Non-conformances elevated to QA with severity mapping (9.3)

Acceptance criteriaQuality checksOwnerEvidence
100% issues have Owner, Severity, and StatusWeekly completeness auditInformation ManagerAudit log in 02-CLASHES
S1/S2 have valid Due dates within SLADue-date SLA checkBIM CoordinatorReport snapshot
No Open → Closed transitionsStatus transition auditQA-QC LeadTransition log
Closed issues include evidence and CDE pathAttachment and path presence checkQA-QC LeadSampled checklist

Interlocks

Uses severity and ownership model in 10.1

Consumed by 10.2 Coordination Cycles and 7.3 Publishing

Evidence stored per 12.1 paths and referenced in 2.3 gate packs

11 DATA EXCHANGE AND IFC#

11.1 EXCHANGE REQUIREMENTS#

Purpose

Define the required open-standard exchanges, model views, and data payloads per stage so external stakeholders can reliably consume the information.

Schemas and model view definitions (MVD)

IFC schema: Default office qualification profile IFC4 ADD2 TC1 (IFC 4.0.2.1) Reference View; project use requires the approved exchange profile and receiving test. IFC 4.3.2.0 only by recorded approval when sender build and receiver both pass a test exchange; IFC2x3 only when an appointment or authority profile requires it; authority submissions use the schema the authority states (11.4). ISO 16739-1:2024 is the current research reference, not an instruction to upgrade every project.

Primary MVDs

Design: IFC4 Reference View (RV)

Coordination: Reference View for agreed reference/federation use. Design Transfer View is a separate candidate for specified transfer purposes and tested receiver capability; it does not promise lossless native editability.

Asset data: IFC4 RV plus COBie XLSX when the AIR/EIR require it; COBie version as specified in the EIR, default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3; BS 1192-4 withdrawn 16 Sep 2022

Exchange matrix by stage and discipline

StageDisciplineIFC Schema + MVDNotes
RIBA 3ARC, STR, MEPIFC4 RVFederation and coordination. No authored param hacks
RIBA 4ARC, STRIFC4 RV + DTV (select)DTV only where editable handoff is explicitly requested
RIBA 4MEPIFC4 RVSystems and connectors consistent; units validated (4.4)
RIBA 5–6AllIFC4 RV + COBie (if required; version per EIR)Asset_ID populated per 3.2; classification stable

Coordinate system and units

Coordinates: Use a stable local modelling origin for numerical performance and an approved mapping to the project CRS named by EPSG code with its vertical datum (5; BBM-STD-86); export IfcMapConversion and IfcProjectedCRS where the schema supports them. Do not force georeferenced exports to 0,0,0. Record units, datum, True North, offset/rotation and independent receiving checks (11.3).

Units: Metric. Length mm. Areas m². Volumes m³. Angles degrees (4.4)

Classification and property sets

Classification: Classification_Code (Uniclass) mapped to IfcClassificationReference and element/type Psets (3.2)

Core properties

Identity: Mark, Family, Type, Classification_Code, System, Zone, Level

Performance: Fire_Rating (exported to Pset_*Common.FireRating with the standard), LoadBearing (as applicable)

Asset: Asset_ID (when the client asset register exists)

Do not overload free-text parameters when a standard IFC property exists

Files, naming, and packaging

IFC file naming: CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ifc per 3.1 / 12.3

One model per discipline export unless split rules are documented (3.3). Use VOLUME / LEVEL tokens and NUMBER to indicate split

Package location: 03-PUBLISHED/<NN-STAGE-N>/<YYYY-MM-DD-DESCRIPTION>/02-MODELS

Include export preset name and version in transmittal (7.3)

Validation and acceptance

Geometry

No missing solids in target viewers for representative categories (walls, floors, beams, ducts, pipes)

No unbounded or far-from-origin geometry

Data

100% of required core properties populated for the categories the LOIN worksheet requires (3.2)

Classification_Code present where the LOIN worksheet requires it

Asset_ID present where the client asset register exists

Structure

Correct schema and MVD per exchange matrix

Project/global IDs stable across consecutive issues

Acceptance criteriaQuality checksOwnerEvidence
IFC schema and MVD match exchange matrixHeader parse + preset name checkBIM CoordinatorPreset screenshot + schema header
No far-from-origin or unbounded elementsAutomated validator reportQA-QC LeadHTML/PDF validation report
Core properties populated to stageIFC property spot-check vs 3.2Information ManagerChecklist in 04-REPORTS
Files named per 3.1 and placed per 12.1Regex + path checkInformation ManagerPack structure scan

Interlocks

Uses naming and tokens from 3.1 and CDE paths from 2.4

Property population governed by 3.2 Parameters and LOIN

Feeds Publishing 7.3 and Validation 11.2

11.2 EXPORT AND VALIDATION#

Purpose

Standardize how open-standard exports are produced and validated so recipients get consistent geometry, data, and metadata.

Export presets (baseline)

Preset naming: IFC4-RV-vNN, IFC4-DTV-vNN, IFC2x3-Ref-vNN, EXP-DM-PERMIT-<schema>-<rev>

Scope

IFC4-RV-vNN: Default for coordination and downstream viewing

IFC4-DTV-vNN: Limited to requested editable handoffs (see 11.1 matrix)

IFC2x3-Ref-vNN: only where an appointment or an authority submission profile requires it

EXP-DM-PERMIT-<schema>-<rev>: Dubai Building Permit setup per the current Dubai BIM Standard (11.4); preset ID owned by BBM-STD-65; former alias DBP-… retired

Governance

Presets are stored in SHARED/05-DOCUMENTS/02-STANDARDS/IFC/Exports

Version increments vNN on any rule change. Record change in 01-STANDARD-UPDATES and update the BEP reference

Export preparation checklist (per model)

Coordinates validated and Start View default (4.9, 5 CAD)

View Templates applied to DOC parent views; no per-view overrides (4.12)

Workset1 = 0 elements. Links pinned. Imports unloaded (3.3, 8.1.3)

Naming tokens validated for file and views (3.1, 4.11.1, 12.3)

Parameters complete per the LOIN worksheet of the exchange (3.2)

Export steps (IFC)

Open source model, confirm Start View and template lock

Load correct IFC preset (per 11.1 matrix) and confirm options:

Coordinates: Shared coordinates

Property sets: Export schedules and parameters mapped to IFC Psets where available

Elements: Exclude non-issued worksets and temporary categories (QA/COORD) if client requires clean deliverable

Export to local staging path using the external container ID CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ifc

Run validation (below). If checks pass, request authorisation/acceptance under 12.4 before committing the formal set to 03-PUBLISHED/<NN-STAGE-N>/<YYYY-MM-DD-DESCRIPTION>/02-MODELS

Validation tools and rules

1 Schema and normative rules: buildingSMART IFC Validation Service, or an approved offline validator when the model is confidential (record validator and version)

2 Information requirements: IDS 1.0 file ID/hash, checker name and build, pass/fail per rule; one IDS file per exchange built from the LOIN worksheet, sequence and record per BBM-STD-89 §3–§5

3 Geometry and coordinates, as listed below

Structural checks

Far-from-origin test, bounding boxes sanity, invalid solids count = 0

Schema and header

IFC schema and MVD match 11.1 matrix; file header includes Project Code and Export Preset name

Geometry sampling

Representative element categories visualize in a neutral viewer (Walls, Floors, Beams, Columns, Ducts, Pipes, Equipment)

Property sampling

Required core properties populated for sampled elements: Classification_Code, System, Zone, Level, Fire_Rating (where applicable), Asset_ID (where the client register exists)

File hygiene

No orphan GUID churn between consecutive issues beyond changed items; file size within expected bounds for model class

Validation artifacts

Validator report: HTML/PDF placed under 03-PUBLISHED/<NN-STAGE-N>/<Pack>/04-REPORTS/00-IFC-VALIDATION

Screenshot set: Neutral viewer screenshots of 2–3 typical views per discipline

Mapping log: Export preset name and version noted in transmittal and README

Troubleshooting guide (quick)

Missing geometry in viewer

Re-export with solids/triangulation options per preset. Check category visibility and phase filters in preset view

Wrong coordinates

Verify shared coordinates and survey/base points. Obtain coordinate-owner approval for any transform; test affected links and exports before reissue. Do not rebase an issued model merely to match a viewer

Missing properties

Confirm parameters exist and are bound per 3.2. Re-map fields in export setup if a native Pset exists

Acceptance criteriaQuality checksOwnerEvidence
Correct preset and schema usedHeader + preset name in transmittalBIM CoordinatorTransmittal + preset screenshot
Validator report shows no critical errorsHTML/PDF report statusQA-QC LeadReport in 04-REPORTS/00-IFC-VALIDATION
Core properties present on sampled elementsSpot-check against 3.2Information ManagerChecklist attached
Coordinates and units correctViewer probe + header unitsQA-QC LeadScreenshot + note
Files named and placed per 3.1 and 2.4Regex + path checkInformation ManagerPack structure scan

Interlocks

Presets stored and versioned under 12.1 paths; referenced in 7.3 transmittal

Property completeness per 3.2; naming per 3.1; coordinates per 5 CAD and 4.9

Exchanges governed by 11.1; results filed as evidence for 2.3 gate packs

11.3 PROJECT EXCHANGE QUALIFICATION AND RECEIVING CHECKS#

Decision (BIM Manager, 2026-10-14): Freeze authoring/exporter/checker/receiver full builds, presets, dictionaries and profile hashes; upgrades require impact, compatibility, receiver and recovery tests with controlled change approval. Basis: Infrastructure qualifies for a purpose through actual capability evidence P02, S04.

Decision (BIM Manager, 2026-10-14): Use IFC 4.0.2.1 (IFC4 ADD2 TC1) Reference View as default building reference qualification profile; IFC 4.3.2.0 needs approved purpose and exporter/receiver support; freeze mappings/units/transforms/preset hashes. Basis: Retains Manual/BEP interoperability baseline without automatic upgrades S11, S12, P02.

Decision (BIM Manager, 2026-10-14): Use BCF 3.0 XML as default qualification route; BCF 3.0 API requires separately approved endpoints/permissions and returned-issue test; preserve issue ID/revision/GUID/viewpoint/assignment/status/retest. Basis: XML/API are separate implementations needing endpoint compatibility S13.

Decision (BIM Manager, 2026-11-04, replacing): Deliver COBie (XLSX) when the EIR requires it; version as specified in the EIR, default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4); freeze template/schema, units, fields, keys, exclusions and receiving tests. Basis: COBie v3 final publication is not confirmed (NIBS draft May 2023) S15, S03.

Decision (BIM Manager, 2026-10-14): Use audited IDS 1.0 where supported for IFC data with rule IDs/hash/checker and valid/invalid fixtures; geometry/access/competent review remain separate. Basis: IDS scope is information validation, not full geometric/safety assurance S20, S04.

Decision (2026-11-04,, replaces the new-project baseline): The office Revit template BBM-ARC-TMP-R23 is authored in the oldest Revit release in office use (currently Revit 2023) and must open and upgrade cleanly in Revit 2023–2027; new projects start in a supported release (2024–2027) by upgrading the template and recording the upgrade test (BBM-STD-91 §5); the qualified build per release stays a recorded field in BBM-STD-91. Revit 2023 stays out of Autodesk support (previous-versions list checked 2026-11-04): legacy authoring release, recorded risk. Basis: Revit cannot save back to an earlier major, so one template in the oldest release serves every supported release A01.

Decision (BIM Manager, 2026-10-14): Select Autodesk IFC for Revit 2025 package 25.4.40 for qualification; verify package/binary versions/source/licence/hash, preset/mapping and export/receiver tests before activation. Basis: Retains BEP frozen pilot choice without claiming installed compatibility P02, S12.

Decision (BIM Manager, 2026-10-14): Use same qualified Revit full build for editable native receiver; verify build/OS/link-cloud access and open/edit/sync; no lower-major backward opening assumed. Basis: Common tested route protects appointed native capability A01, P02.

Decision (BIM Manager, 2026-10-14): Select Navisworks Manage as default checking/federation route; freeze actual installed full build/rules and known-result tests; Solibri requires separately qualified approval for the use; missing actual builds hold activation. Basis: One identified route/use avoids unverified interchangeable checking P02, S04.

Decision (BIM Manager, 2026-10-14): Recipient freezes actual viewer/FM build or dated cloud configuration, schema/profile/units/document-access mapping; intended-use/update tests must pass before acceptance. Basis: Receiver capability cannot be invented from export format S03, S04.

Decision (BIM Manager, 2026-10-14): Survey/site-control owner approves coordinate evidence, BIM Coordinator implements, independent receiver checks ≥3 well-distributed control points plus elevation/unit probes; record CRS/datum/units/provenance/uncertainty/local-shared transform/True North. Basis: Retains shared coordinate method without asserting zero survey uncertainty A10, S04.

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.

Decision (BIM Manager, 2026-10-14): For declared representative seed target native open ≤120 s, sync ≤60 s and prescribed IFC export ≤180 s; record device/network/build/model and approve actual workload-class targets before project acceptance. Basis: Existing BEP pilot targets are local, not vendor minima or universal limits P02, S04.

Qualification is purpose-specific under ISO 19650-4:2022. Blank actual build/profile/results fields do not represent passed mobilisation.

Annex controlDecided qualification baseline / required particularsQualification evidence
SoftwareSupported majors Revit 2024–2027, 2023 legacy (11.3.1). New projects start in a supported release by upgrading the office template BBM-ARC-TMP-R23 (authored in Revit 2023) with the upgrade test recorded; qualified build and IFC exporter per release recorded in BBM-STD-91; common exact native build per model group; freeze actual checker/receiver/plugins and retain mandated appointment buildsNative open/edit/sync test where needed; backward compatibility and upgrade/rollback plan
Open profileDefault qualification: IFC 4.0.2.1 Reference View; IFC 4.3.2.0 only for approved purpose and demonstrated exporter/receiver supportApproved schema/profile, preset/hash, entity/property mapping and receiver comparison
IssuesBCF 3.0 XML default; API only as separately approved/tested route; freeze both endpoint buildsGUID/viewpoint/assignment/status exchange and reviewer retest
Asset exchangeCOBie XLSX when the EIR requires it; version per EIR, default COBie 2.4 unless the EIR names v3; retain appointed version/profile, required fields/exclusions and receiver schemaKnown-data import with keys, units, document links and change/update tests
Information needISO 7817-1:2024 purpose + objects/actors/timing + geometry/data/docsPer-use worksheet, mandatory rule IDs and source evidence
Survey / coordinatesApproved survey/control owner; project CRS by EPSG code (Dubai DLTM EPSG:3997; Abu Dhabi per authority guideline) with vertical datum, datum, units, rotation/offset, True North, control-point provenance/uncertaintyAt least three well-distributed independent control points plus elevation and unit probes; tolerances set by approved survey purpose
Clash rulesOnly Clash matrix section 3 H/C/A/D/V table, referenced by rule/revision; retire stage and 5/15/20/25 mm blanket thresholdsPair/zone/units/rule ID, geometry source revisions, threshold rationale, exclusions, designer disposition and retest
PerformanceMeasure open/sync/export time on representative devices/models; size is an investigation triggerBaseline, sample size, device/network/build and target times; record justified split strategy
Automation / AIApproved inputs, provider, licence, build/dependencies, script/hash and human reviewer; isolated representative test before bulk changesBefore/after diff, known failure/pass cases, rollback/recovery, allowed data and access; no unverified free/safe claim

IFC schema conformity, IDS 1.0 information validation, geometric/clearance checks and competent design review are distinct. Audit the IDS requirements file itself and retain its version/hash, checker build and scope; an IDS pass does not prove geometry, all safety requirements or receiving acceptance. Do not upload confidential models to public validation services without explicit data-owner authorisation.

  1. Freeze the candidate source revisions and annex/rule versions; validate every applicable mandatory property and identity across the full required scope.
  2. Export the prescribed native, open, drawing, data and documentation set. Inspect representative geometry and all high-risk areas; reconcile object counts, omissions and stable IDs against source and approved exclusions.
  3. Check coordinates/units independently in the specified receiver. Assumed positioning remains PROVISIONAL - not verified for survey/as-built use and may only be shared for its approved limited purpose.
  4. Receiver runs the intended workflow: reference/federation, required editing, structured asset ingestion or decision review. Compare values, relationships, document links and permitted-use metadata. Record failure and correction against exact revisions.
  5. LAP authorises the identified corrected set; receiving authority records accept/conditional/reject and evidence. Rejected containers return through WIP correction and a new controlled submission, preserving the rejection and prior baseline.
Test ID / exchangeContainer ID, revision, CDE version / checksumRequirement / method / scopeExpected vs actualProducer/checker and receiver / buildsResult / corrective action / retestRelease and acceptance IDs
[ID][immutable identity][rule, mandatory population, geometry sample][expected measurable values; observed][roles, dates, tool builds][pass/fail/blocked, action owner, new evidence][authoriser; receiver decision/date]

Decision (BIM Manager, 2026-10-14): Require isolated representative mobilisation pack: native seed, known-value IFC/data/documents, valid/invalid fixtures, coordinates, allowed/denied access, BCF round trip, correction/retest log and restored backup; project tests stay NOT EXECUTED until evidenced. Basis: Specified test design and workshop screenshots do not prove live exchange success P02, S04.

A filled template or workshop screenshot is not a current project test result. Actual results remain pending until executed and recorded.

11.3.1 SOFTWARE VERSION POLICY#

The full supported-release matrix (release, support status, qualified build, IFC exporter, seed and library save version, Dynamo and AutoCAD releases) is BBM-STD-91.

ItemRule (checked 2026-11-04)
Supported majorsRevit 2024, 2025, 2026, 2027 (Autodesk previous-versions list). Latest Revit 2027 update: 2027.3 (15 Sep 2026)
Revit 2023Out of Autodesk support: legacy, no new projects; existing projects continue only with recorded risk acceptance and an upgrade plan. It stays the authoring release of the office template BBM-ARC-TMP-R23, which must open and upgrade cleanly in 2023–2027
Upgrade path and testUpgrade on an isolated copy: open, upgrade, sync, link reload, IFC export with the project preset, IDS check and receiver test; record result before the live upgrade
IFC exporterExporter per major recorded in BBM-STD-91. Revit IFC exporter 27.4.0.30 (30 Oct 2026) exports IFC4x3; use IFC 4.3 RV only after a test export from the project build passes the project IDS
Library save versionFamilies, details and template content are saved in the office template's authoring release (currently Revit 2023) and recorded per library release
SourceAutodesk previous-versions and lifecycle pages, Revit release notes, Autodesk revit-ifc releases (References)

11.4 AUTHORITY BIM SUBMISSIONS#

Applicability is tested at project start and before each permit submission, and recorded in the BEP with the source and check date. Detail and updates live in BBM-STD-85; terms in Glossary 1.8.

ItemDubaiAbu Dhabi
InstrumentDM circular 9-1-2 (13 Oct 2023): Open BIM submission per the Dubai BIM Standard from 1 Jan 2024 for buildings over 20 floors (ARC) / 40 floors (STR), over 20,000 m² (ARC) / 30,000 m² (STR), specialised buildings (hospitals, universities) and government projects. DM 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 alterationsNo universal building-permit BIM threshold found; ADM BIM Code of Practice (Oct 2020) where appointed
Schema and export setupThe IFC schema and export setup stated in the current Dubai BIM Standard (buildindubai.gov.ae/bim), checked at project start and recorded in the BEP; office preset EXP-DM-PERMIT-<schema>-<rev> (BBM-STD-65)Per the appointment or ADM requirement
AttributesThe Model Attribute Matrix issued with the current Dubai BIM Standard, downloaded at project start and recorded in the BEPPer appointment
DrawingsSubmitted drawings are extracted from the submitted model revisionPer authority
PackageopenBIM IFC, zipped, within the upload limit stated on the portalPer authority
CoordinatesCRS-DXB: Dubai DLTM (EPSG:3997), vertical datum DMD (5; BBM-STD-86)CRS-AUH: authority CRS for the plot (5; BBM-STD-86)
EvidenceApplicability result, preset ID, validation result (11.2), portal receipt, authority comments and dispositions, approval recordSame
Folder02-REG/00-PERMITS/01-BIM-SUBMISSIONS (12.1)Same

12 CDE AND VERSIONING#

12.1 FOLDER STRUCTURE AND PERMISSIONS#

This section is the one project folder tree of the office standard. Every other document points here and does not copy it. Section 2.4 is the legacy pointer to this section.

A) Folder name rule

  • Every folder is named NN-NAME: a two-digit number, a hyphen, then the name in capitals, with words joined by hyphens. Examples: 00-PIM, 01-WIP, 02-SHARED, 03-PUBLISHED, 04-ARCHIVE, 00-TTB-AND-COVER.
  • No dots, no spaces, no underscores and no "&" (write -AND-). Dots in folder names break some CAD and xref path handling. A dot appears only in a file name, before its extension; file names follow 12.3 unchanged.
  • The tree is ordered state → data type → discipline → files. Under every data type, in every state, the discipline folders carry the BBM-STD-93 folder codes with the same numbers in the same order: 00-ARC, 01-STR, 02-MEC, 03-ELE, 04-LSC, 05-PLU, 06-FLS, 07-INT, 08-CIV, 09-SUR, 10-QTY, 11-CON, 12-GEN (BBM-STD-93 §2). A project creates only the discipline folders it needs.
  • The data types are the three this standard defines: 00-RVT (Revit models), 01-DWG (CAD drawings), 02-PPT (presentations). A new data type is an office standard change (see "Acceptance for 12.1 updates").
  • Numbering is continuous within each level and starts at 00; the four state folders under 00-PIM are numbered 01–04, one per CDE state (12.4). No number appears twice in one level. A retired number stays retired, is shown in the tree and is never reused.
  • One spelling per state: WIP, SHARED, PUBLISHED, ARCHIVE.
  • 03-PUBLISHED is split by stage, then by issue. Stage folders follow the stages of 2.3. Issue pack folders are the one named exception to NN-NAME: YYYY-MM-DD-DESCRIPTION, so packs sort by date (example: 2026-10-14-IFC-PACKAGE-W2).
  • An existing project or server folder that still carries an earlier dotted name maps one-to-one to the name in this tree. Renaming a folder never changes a file's issued identity or permitted reliance (Glossary 1.5).

B) Project folder tree

  • 00-PIM — Project Information Model: live work, shared coordination, published issues and archive
  • 01-WIP — work in progress per data type and discipline; task team only
  • 00-RVT — discipline folders 00-ARC … 12-GEN
  • 01-DWG — discipline folders 00-ARC … 12-GEN
  • 02-PPT — discipline folders 00-ARC … 12-GEN
  • 02-SHARED — checked and approved to share with other task teams
  • 00-RVT — discipline folders 00-ARC … 12-GEN
  • 01-DWG — discipline folders 00-ARC … 12-GEN
  • 02-PPT — discipline folders 00-ARC … 12-GEN
  • 03-URS — user requirements and similar upstream references
  • 04-RENDITIONS — shared visual outputs for review
  • 05-DOCUMENTS — initiation, standards, plans and registers
  • 00 retired: RFP moved to 01-ADMIN/06-RFP; number not reused
  • 01 retired: scope analysis moved to 01-ADMIN/07-SCOPE-ANALYSIS; number not reused
  • 02-STANDARDS
  • 03-TASK-TEAM
  • 04-KICKOFFS
  • 05-BEP
  • 06-CLASSIFICATIONS
  • 07-QA-QC
  • 08-LOIN
  • 09-TIDP
  • 10-MIDP
  • 06-REPORTS
  • 00-PLANNING
  • 01-MODEL-HEALTH
  • 02-CLASHES
  • 07-RECORD
  • 00-PROJECT-LOG
  • 01-IN
  • 02-OUT
  • 08-PROJECT-LIBRARY
  • 00-TTB-AND-COVER
  • 01-GENERAL
  • 02-ARC … 13-CON — discipline library folders in BBM-STD-93 order (02-ARC, 03-STR, 04-MEC, 05-ELE, 06-LSC, 07-PLU, 08-FLS, 09-INT, 10-CIV, 11-SUR, 12-QTY, 13-CON); general items stay in 01-GENERAL
  • 09-NON-GRAPHICAL
  • 00-COBIE
  • 01-ASSET-REGISTERS
  • 02-IFC-VALIDATION
  • 03-PARAMETER-EXPORTS
  • 03-PUBLISHED — authorised issues, split by stage, then by issue pack
  • 00-STAGE-0 … 07-STAGE-7 — one folder per stage of 2.3 that has an issue
  • YYYY-MM-DD-DESCRIPTION — one folder per issue pack
  • 00-COVERSHEETS
  • 01-DRAWINGS — discipline folders 00-ARC … 12-GEN
  • 02-MODELS — discipline folders 00-ARC … 12-GEN
  • 03-SCHEDULES
  • 04-REPORTS
  • 00-IFC-VALIDATION
  • 01-NAMING-VALIDATION
  • 05-TRANSMITTAL
  • 04-ARCHIVE — read-only history and learnings
  • 00-LESSONS-LEARNED
  • 01-STANDARD-UPDATES
  • 02-LIBRARY-UPDATES
  • 01-ADMIN — administration and commercial records
  • 00-DIRECTORY
  • 01-FEE-ANALYSIS
  • 02-AUTHORITIES
  • 03-CONTRACT-DOCS
  • 04-SITE-SUPERVISION
  • 05-HANDOVER
  • 06-RFP
  • 07-SCOPE-ANALYSIS
  • 02-REG — regulatory records
  • 00-PERMITS
  • 00-APPLICATIONS
  • 01-BIM-SUBMISSIONS
  • 01-RISK
  • 02-PROCEDURES
  • 03-REQUESTS
  • 04-SITE-ARCHIVE
  • 05-MOMS
  • 03-EI — engineering intelligence and analytics
  • 00-DASHBOARDS
  • 01-ANALYTICS
  • 02-POTENTIALS
  • 03-PRESENTATIONS
  • 04-R-AND-D
  • 05-EXTRACTIONS
  • 04-DOCS — strategies, client profile and basis of design
  • 00-BOD
  • 01-STRATEGIES
  • 02-ANALYTICS
  • 03-PROCUREMENT
  • 04-CLIENT-PROFILE
  • 05 retired (general strategy documents merged into 01-STRATEGIES; STR is the Structure code)

C) Schedule — mirrors the tree above

Naming fast checks

  • Every folder matches ^[0-9]{2}-[A-Z0-9]+(-[A-Z0-9]+)$, except issue pack folders, which match ^[0-9]{4}-[0-9]{2}-[0-9]{2}-[A-Z0-9]+(-[A-Z0-9]+)$.
  • No dots, spaces, underscores, "&", trailing spaces, double hyphens or emojis in any folder name.
  • Discipline folders use only the BBM-STD-93 folder codes and numbers.

Group purposes (authoritative, 1 sentence each)

PIM: Project Information Model workspace used for live working, shared coordination, published issues and archive.

ADMIN: Central administration records including directory, contracts, fees, and site supervision, restricted to the core team for governance and compliance.

REG: Regulatory procedures, requests, permits, and risk records maintained for authority coordination and audit trail.

EI: Engineering intelligence and analytics work products, dashboards, and derived insights to support decision-making.

DOCS: Canonical documents for strategies, client profiles, and basis-of-design, curated for consistent reference.

NON-GRAPHICAL canonical formats

COBie: XLSX is the canonical exchange format

IFC validation: HTML or PDF reports including rule-set ID and version

Parameter exports: CSV with timestamp and schema reference

Permissions matrix (levels 1–2)

GroupDefault accessExceptions allowed?Exception owner
00-PIMProject teamYes (via README)Information Manager
00-PIM/02-SHAREDAll project teamsYes (via README)Information Manager
01-ADMINCore teamYes (via README)Information Manager
02-REGCore teamYes (via README)Information Manager
03-EICore teamYes (via README)Information Manager
04-DOCSCore teamYes (via README)Information Manager
ItemHierarchy levelAccess levelDescription
00-PIM1Project teamProject Information Model workspace. Live working, shared coordination, published issues and archive.
01-WIP2Task Teams onlyWork in progress per data type and discipline. Not visible externally. Subject to model segregation rules.
00-RVT, 01-DWG, 02-PPT (under 01-WIP)3Task Teams onlyData type folders.
00-ARC … 12-GEN (under each WIP data type)4Task Teams onlyDiscipline folders, BBM-STD-93 codes. Hold WIP files.
02-SHARED2All project teamsInterdisciplinary space for information approved to share across teams.
00-RVT, 01-DWG, 02-PPT (under 02-SHARED)3All project teamsData type folders for shared models, drawings and presentations.
00-ARC … 12-GEN (under each SHARED data type)4All project teamsDiscipline folders, BBM-STD-93 codes. Producer discipline writes; others read.
03-URS3All project teamsUser requirements and similar upstream references.
04-RENDITIONS3All project teamsShared visual outputs such as renders or exports for review.
05-DOCUMENTS3All project teamsStructured document set for initiation, standards, plans, and registers.
02-STANDARDS4Core teamAdopted standards referenced by the project.
03-TASK-TEAM4Core teamTask team definitions and allocations.
04-KICKOFFS4Core teamKickoff decks, minutes, and decisions.
05-BEP4Core teamBIM Execution Plan and revisions.
06-CLASSIFICATIONS4All project teamsClassification systems and mappings, e.g., Uniclass.
07-QA-QC4All project teamsQuality procedures, checklists, and reports.
08-LOIN4All project teamsLOIN worksheets per exchange and object class (BBM-STD-54).
09-TIDP4All project teamsTask Information Delivery Plan files.
10-MIDP4All project teamsMaster Information Delivery Plan and updates.
06-REPORTS3All project teamsPlanning, model health, and clash coordination reports.
00-PLANNING4All project teamsSchedules, calendars, and planning outputs.
01-MODEL-HEALTH4All project teamsModel health KPIs and audit outputs.
02-CLASHES4All project teamsClash reports and resolutions.
07-RECORD3Core teamRegisters of inbound and outbound transmittals and logs.
00-PROJECT-LOG4Core teamCentral project log.
01-IN4Core teamInbound correspondence and files.
02-OUT4Core teamOutbound correspondence and files.
08-PROJECT-LIBRARY3All project teamsShared project assets used across documentation.
00-TTB-AND-COVER4All project teamsTitle blocks, covers, and sheet assets.
01-GENERAL4All project teamsCommon reusable resources.
02-ARC … 13-CON4Discipline teamDiscipline library items, BBM-STD-93 order.
09-NON-GRAPHICAL3All project teamsNon-graphical data deliverables and validations.
00-COBIE4All project teamsCOBie exports and checks.
01-ASSET-REGISTERS4All project teamsAsset registers per client requirements.
02-IFC-VALIDATION4All project teamsIFC validation reports and rule sets.
03-PARAMETER-EXPORTS4Authorised project usersParameter CSV exports with timestamp and schema reference.
03-PUBLISHED2Internal + External recipientsFormal submittals, split by stage, then by issue pack.
00-STAGE-0 … 07-STAGE-73Internal + External recipientsOne folder per stage of 2.3 that has an issue.
YYYY-MM-DD-DESCRIPTION4External recipientsOne issue pack; children 00-COVERSHEETS, 01-DRAWINGS, 02-MODELS, 03-SCHEDULES, 04-REPORTS, 05-TRANSMITTAL.
2026-10-14-IFC-PACKAGE-W2Example of required naming for an issue pack.
04-ARCHIVE2Read-onlyImmutable records and learnings.
00-LESSONS-LEARNED3All project teamsRetrospectives and process improvements.
01-STANDARD-UPDATES3Core teamArchived updates to standards.
02-LIBRARY-UPDATES3Core teamArchived updates to libraries.
01-ADMIN1Core teamAdministration and commercial records.
00-DIRECTORY2Core teamProject directory and contacts.
01-FEE-ANALYSIS2RestrictedFee breakdowns and financial analysis.
02-AUTHORITIES2Core teamAuthority communications and approvals.
03-CONTRACT-DOCS2RestrictedContracts and legal documents.
04-SITE-SUPERVISION2Core teamSite supervision records.
05-HANDOVER2Core teamHandover planning and artifacts.
06-RFP2Core teamRequest for Proposal and related correspondence (moved from 02-SHARED/05-DOCUMENTS).
07-SCOPE-ANALYSIS2Core teamScope breakdowns and clarifications (moved from 02-SHARED/05-DOCUMENTS).
02-REG1Core teamRegulatory materials and records.
00-PERMITS2Core teamPermit applications and approvals.
00-APPLICATIONS3Core teamPermit applications, receipts and approvals.
01-BIM-SUBMISSIONS3Core teamAuthority BIM submissions, validation results, portal receipts and comments (11.4).
01-RISK2Core teamRisk registers and assessments.
02-PROCEDURES2Core teamRegulatory procedures and SOPs.
03-REQUESTS2Core teamRFIs and formal requests.
04-SITE-ARCHIVE2Read-onlyOn-site archival materials.
05-MOMS2All project teamsMinutes of meetings.
03-EI1Core teamEngineering intelligence and analytics.
00-DASHBOARDS2All project teamsLive dashboards and summaries.
01-ANALYTICS2All project teamsAnalytical outputs and datasets.
02-POTENTIALS2Core teamOpportunities and initiatives.
03-PRESENTATIONS2All project teamsPresentation decks.
04-R-AND-D2Core teamResearch and development materials.
05-EXTRACTIONS2All project teamsData or drawing extractions.
04-DOCS1Core teamDocuments repository for strategies and profiles.
00-BOD2Core teamBasis of Design documents.
01-STRATEGIES2Core teamDesign and delivery strategies.
02-ANALYTICS2Core teamAnalyses and studies.
03-PROCUREMENT2Core teamProcurement documents.
04-CLIENT-PROFILE2Core teamClient background and preferences.
05 (retired)2—Merged into 01-STRATEGIES; number not reused.

Rule: Access level = default role. Any exception must be listed in a README with owner and expiry date.

Notes

File names must follow the project naming standard. See 12.3 Naming and metadata.

If a model exceeds size or scope, split by floor, zone, or system. Record the rule in Model Notes (3.3).

Keep analytical, coordination, and documentation models distinct when required, and document links in 2.3 evidence.

Acceptance for 12.1

The CDE root mirrors the exact tree above.

Every folder name passes the naming fast checks above.

Issue packs use a YYYY-MM-DD-DESCRIPTION folder under the stage folder of 03-PUBLISHED.

Do not add new top-level folders without updating this manual.

Acceptance for 12.1 updates

Any change to the office tree (top-level groups or their immediate children, data types or discipline folders) is an office standard change: proposed by the BIM Manager and approved by the office director. Project-specific access exceptions are approved by the Information Manager and LAP through the README below.

Evidence of approval and rationale must be logged in the local change log below and mirrored in 1.1 Revision History.

The permissions schedule must mirror the tree with zero drift.

DateChangeSection/IDOwnerReason

Interlocks and guardrails

Interlocks

Permissions: Align changes in 2.4 with 12.1 (Folder structure and permissions). No access changes without README + sign-off.

Naming: All folder and file names must validate against 12.1 A) and 12.3 (Naming and metadata) before issue.

Evidence: Pre-gate evidence packs in 2.3 must reference the exact 12.1 paths used at issue.

Do not create (by area)

SHARED: No personal drafts, temporary zips, or raw tool exports.

PUBLISHED: No analytical scratch files, no partial or empty subfolders, no files without approved container metadata.

ADMIN/REG/DOCS: No WIP models or federations. Documents only.

EI: No formal submittals. Place formal outputs in PUBLISHED only.

ARCHIVE: Read-only. No edits; add new items via approved archiving action only.

D) Label conventions and access-exception README

Label conventions

All folders, at every level, use NN-NAME as set in A); issue pack folders use YYYY-MM-DD-DESCRIPTION.

Hyphens join words: SITE-SUPERVISION, CLIENT-PROFILE, TTB-AND-COVER.

Access exceptions README

Title line: README — Access Exception

Exception: <describe the exception precisely>

Owner: <name or role>

Rationale: <why the exception is required>

Effective date: YYYY-MM-DD

Expiry date: YYYY-MM-DD

Approved by: Information Manager, LAP

Review cadence: Per gate

Scope:

  • Affected group/folder: <e.g., 00-PIM/02-SHARED/05-DOCUMENTS>
  • Affected teams/users: <list>
  • Permissions delta: <from → to>

Notes:

  • On expiry, remove the exception and restore default access.
  • Archive this README in 04-ARCHIVE when the exception is closed.

Location: Place a README in each top-level group and any folder with exceptions

Filename: README.md

Fields: Exception, Owner, Rationale, Effective date, Expiry date, Approved by

12.2 VERSIONING AND TRANSMITTALS#

Spec — 12.2 Versioning and Transmittals

Purpose

Provide consistent rules for version control of models, drawings, schedules, and data, and a standard process to package and send formal issues.

Versioning model

Working versions

File naming does not include ad-hoc version suffixes in WIP. Version is tracked by the CDE history and the Project Log

Optional local working tokens allowed only in WIP: -draft, -work. Must be removed before moving to SHARED or PUBLISHED

Shared versions

SHARED is for approved-to-share information. No personal tokens. Names must pass 12.3 checks

Updates to SHARED require a short change note in 00-PROJECT-LOG and, when relevant, links to affected items

Published issues (formal packs)

Use dated folder “YYYY-MM-DD-DESCRIPTION” in the stage folder of 03-PUBLISHED (12.1)

Rnn increases per changed container and is never recycled; unchanged containers keep their revision; the pack manifest lists each container's actual revision (3.1, 7.3)

Never overwrite or rename an issued pack. Supersede with a new dated folder

File- and sheet-level revision rules

Sheets: Rnn per sheet, matching the sheet index and the pack manifest

Models: Do not embed ad-hoc text revisions in model filenames. Revision is captured by issue pack metadata and transmittal

Schedules and data: Include a date and hash or row count in the cover note for traceability

Change control and audit

Every move from WIP → SHARED or inclusion in a PUBLISHED pack requires:

Change note: what changed, why, and impact

Owner and date

Links to evidence, issues, or approvals

Gate evidence (2.3): Include change summaries since the previous gate

Transmittals

Required for each formal pack (7.3)

Content

Header: Project code, pack date, description, confidentiality

Recipient list: company, contact, role

Distribution codes: A for action, I for information, R for review (or project-specific codes)

File table: filename, version or revision, type, size, optional checksum

Notes: purpose of issue, references to contracts or instructions where applicable

Storage

Place in 05-TRANSMITTAL inside the dated PUBLISHED pack

Copy or link the PDF to SHARED/07-RECORD/02-OUT with the same date prefix

Supersedence and archive

Superseding rule: The authorised manifest explicitly lists superseded container IDs/revisions and replacement IDs/revisions. A later folder with the same DESCRIPTION does not automatically supersede every earlier container

Archive: Move superseded drafts or temporary staging packs to 04-ARCHIVE with a short README stating reason and link to the superseding pack

Naming interactions

All filenames must validate against 12.3 naming rules

Container ID + revision + suitability/state + immutable CDE version is the authoritative issue identity; date folders group issues and do not replace container metadata

Quick workflows

Minor correction after issue (same day)

New pack folder with same DESCRIPTION and later date, or same date + “-CORRECTION” suffix

Transmittal with explanation and affected file list; Rnn increases on affected sheets only

Client-requested re-issue without design change

New transmittal referencing prior pack. Only administrative updates allowed

Acceptance criteriaQuality checksOwnerEvidence
No issued pack overwritten or renamedFolder history audit in CDEInformation ManagerPack timeline view
All pack folders named “YYYY-MM-DD-DESCRIPTION”Regex check on each 03-PUBLISHED stage folderBIM CoordinatorFolder scan
Each sheet's Rnn coherent with index and manifest; no recycled revisionAutomated comparison reportQA-QC LeadReport in 05-TRANSMITTAL or 04-REPORTS
Transmittal present with required headers and file tableTransmittal parse for required fieldsLAPPDF in 05-TRANSMITTAL
Change notes recorded for SHARED updates and issuesSpot-check 00-PROJECT-LOG entriesInformation ManagerLog excerpts

Interlocks

Folder structure and pack location per 12.1

Sheet and revision rules per 3.1 and 7.3

Evidence and gate interactions per 2.3

IFC and data exports per 11.1–11.2

12.3 NAMING AND METADATA#

Purpose

Define tokenized naming rules and required metadata so files, views, sheets, folders, and data exports are consistent, searchable, and pack-ready.

Token model (general)

Tokens are UPPERCASE with hyphen separators

No spaces around separators. No emojis. No double separators

Allowed separators: hyphen - for tokens. No underscore and no dot in folder names; pack child folders use NN-NAME (12.1)

File names (models, details, exports)

External container pattern: CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext (8 tokens, NUMBER 4 digits, lowercase extension) per the Project Naming Register

CLIENT: Client code. ORG: Originator code. PROJ: Project code

VOLUME: Volume/system or ZZ (whole). LEVEL: Level/location or ZZ (whole). Allowed values and patterns of CLIENT, ORG, PROJ, VOLUME, LEVEL and TYPE: BBM-STD-93 §2.2

TYPE: Information type (e.g. M3 model, DR drawing)

ROLE: 1-letter role code from BBM-STD-93 (A, S, M, E, L, P, F, I, C, G, Q, W, Z)

NUMBER: 4-digit sequence

Example: CLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc

Legacy internal WIP alias: ORG-PROJ-DISC-PHASE-SEQUENCE, mapped one-to-one to the external ID, never issued; PHASE retired

Rules

No ad-hoc v1/v2 in filenames. Versioning is per 12.2

Exported IFC must follow the external pattern and be placed under 03-PUBLISHED/<NN-STAGE-N>/<YYYY-MM-DD-DESCRIPTION>/02-MODELS

View names (Revit examples)

Pattern: DISC-LEVEL-ZONE-TYPE-DESC

DISC: 3-letter discipline code from BBM-STD-93 (ARC, STR, MEC, ELE, LSC, PLU, FLS, INT, CIV, SUR, QTY, CON, GEN)

LEVEL: L01, L02, LRF (roof) or ALL

ZONE: Z01..Z99 or omit if N/A

TYPE: PLAN, SECTION, ELEV, 3D, DETAIL, SCHEDULE

DESC: Short Title Case description

Examples

ARC-L02-Z03-PLAN-Layouts

STR-ALL-SECTION-Framing

MEC-L01-3D-Coord

Rules

Only approved issue views are placed on sheets (4.11.1); schedules, legends, drafting details and dependent views follow their recorded exceptions

Sheet numbers and titles

Pattern: DISC-CAT-INDEX

DISC: 1-letter ROLE code from BBM-STD-93 (A Architecture, S Structure, M Mechanical, E Electrical, P Plumbing, F Fire and Life Safety, L Landscape, I Interiors, C Civil, G Survey, Q Quantities, W Contractor, Z General)

CAT: Two-digit category block, e.g., 10 Plans, 20 Sections, 30 Elevations, 40 Details, 50 Schedules, 01 General

INDEX: Three-digit sequential number (001..999)

Examples

A-10-101

S-20-201

Titles

Title Case. No trailing punctuation

Front matter sheets use “General Notes”, “Abbreviations”, etc.

Folder and pack naming

All folders NN-NAME per 12.1 A), no dots, spaces, underscores or &

PUBLISHED pack folder: YYYY-MM-DD-DESCRIPTION, inside its stage folder

Children: 00-COVERSHEETS, 01-DRAWINGS, 02-MODELS, 03-SCHEDULES, 04-REPORTS, 05-TRANSMITTAL

Metadata — minimum required fields by asset type

AssetRequired fieldsWhere setNotes
Model fileCLIENT, ORG, PROJ, VOLUME, LEVEL, TYPE, ROLE, NUMBERFilenameExternal pattern above; legacy alias recorded in the naming register
ViewsDISC, LEVEL, ZONE, TYPE, DESCView nameUsed by 7.3 audits
SheetsNumber (DISC-CAT-INDEX), Title, RnnTitle blockRnn per sheet, never recycled
IFC exportsFilename tokens + Export Preset nameFilename + TransmittalSee 11.2
COBie or CSVProject code, export date, schema versionHeaderEvidence in 04-REPORTS

Validation rules (regex snippets)

Date folder (legacy display alias): ^\d{4}-\d{2}-\d{2} –.+$; additionally parse a real calendar date

External container: ^[A-Z0-9]{2,6}-[A-Z0-9]{2,6}-[A-Z0-9]{2,6}-[A-Z0-9]{2,3}-[A-Z0-9]{2,3}-[A-Z0-9]{2}-[ASMEPFLICGQWZ]-\d{4}\.[a-z0-9]+$; then validate every token against the BBM-STD-93 code lists

Legacy internal WIP alias stem (never issued): ^[A-Z]{2,}-[A-Z0-9]{2,}-(ARC|STR|MEC|ELE|PLU|FLS|LSC|INT|CIV|SUR|QTY|CON|GEN)-[A-Z0-9]+-[A-Z0-9]+$

View: ^(ARC|STR|MEC|ELE|PLU|FLS|LSC|INT|CIV|SUR|QTY|CON|GEN)-(L\d{2}|LRF|ALL)(-Z\d{2})?-(PLAN|SECTION|ELEV|3D|DETAIL|SCHEDULE)-[A-Za-z0-9][A-Za-z0-9_-]*$; controlled Start View exception is STD00-STARTING-VIEW

Sheet: ^[ASMEPFLICGQWZ]-\d{2}-\d{3}$; validate the approved discipline and category code lists

Common pitfalls and fixes

Double separators or trailing space

Fix by renaming to single hyphens. Never use spaces around -

Mixed case tokens

Convert tokens to UPPERCASE. Keep DESC in Title Case

Missing ZONE

Omit the -ZONE token entirely. Do not use Z00

Wrong pack child names

Children must be exactly 00-COVERSHEETS, 01-DRAWINGS, 02-MODELS, 03-SCHEDULES, 04-REPORTS, 05-TRANSMITTAL

Automation and audits

Pre-issue script validates file/view/sheet names and pack structure

Report stored under 03-PUBLISHED/<NN-STAGE-N>/<Pack>/04-REPORTS/01-NAMING-VALIDATION

Acceptance criteriaQuality checksOwnerEvidence
100% of files, views, and sheets pass naming regexAutomated regex auditInformation ManagerValidation log in 04-REPORTS
All PUBLISHED packs named YYYY-MM-DD-DESCRIPTION with canonical childrenPack structure scanBIM CoordinatorFolder listing
Sheet Rnn values consistent with index and manifest; never recycled7.3 revision auditQA-QC LeadComparison report
No tokens with mixed case or illegal separatorsLint for casing and separatorsInformation ManagerLint report

Interlocks

Pack workflow and revisions per 7.3 and 12.2

IFC exports per 11.1–11.2

Roles and responsibilities for audits per 9.2–9.3 and 2.2

12.3.1 DISCIPLINE CODES#

One code register for views, sheets, folders, issues and file ROLE tokens: BBM-STD-93. Subset used in this Manual, in folder-number order; the folder form NN-CODE (for example 04-LSC) is used in the 12.1 tree:

DisciplineView / folder / issue codeSheet letter and file ROLE
ArchitectureARCA
StructureSTRS
MechanicalMECM
ElectricalELEE
LandscapeLSCL
Plumbing / public healthPLUP
Fire and Life SafetyFLSF
InteriorsINTI
CivilCIVC
SurveySURG
Cost / quantitiesQTYQ
ContractorCONW
General / multi-disciplineGENZ

Extra disciplines take the next free code in BBM-STD-93. "MEP" is an umbrella label for MEC + ELE + PLU, not a code.

12.4 CONTROLLED CDE STATES AND DECISIONS#

IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance C, edition 1 (2020, archived), distinguishes workflow from the technical platform. Native/editable models can be controlled information. A PDF is not automatically authorised. Browser Publish folders, model sync and cloud Publish do not themselves change formal suitability/state.

Check, sharing approval, delivery authorisation and receiving acceptance attach to the exact identified information set.

State / aliasPermitted use / transitionAuthority and retained evidence
WIP / 01-WIPProducer work; restricted to authorised task teamOwner, internal versions and access controls; checked before sharing
Shared / 02-SHAREDApproved limited coordination/review use; not construction merely by locationTask-team approval, requirements/rule reports, suitability, revision, date and comments
Published / 03-PUBLISHEDAuthorised/accepted use within recorded appointment workflow; formal delivery is the transition to Published after authorisation (ISO 19650-2 5.7)LAP submission authorisation; recipient acceptance and permitted-use scope; immutable manifest
Archive / 04-ARCHIVEAudit/history of superseded versions and decisionsRetain original issue identity, predecessor/successor links, permissions and retention schedule

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.

The annex maps actual authorisation/acceptance sequence to platform workflow. Staging stays restricted WIP; any submitted Published candidate awaiting acceptance must state pending acceptance / no authorised construction reliance, with review-only access.

Required transition record: container ID, revision, CDE version/checksum, source/target state, suitability and intended use, requirement/rule revisions, producer/checker, sharing approval, submission authorisation, receiving decision/date, comments/owner/due date and transmittal ID. A conditional decision may only cover non-blocking comments within explicitly permitted use. Mandatory failures require reject/correct/retest. Gate outcomes A=Accepted, B=Accepted with defined comments, C=Rejected are local decision labels; they are not suitability codes or RACI powers.

Rejection preserves the submitted set and decision; producer corrects in WIP, increments the controlled revision as required and resubmits with retest evidence. Do not overwrite an issued model, silently rename its identity, infer supersedence from a date, or remove archive evidence. Record folder aliases, migration effective date, prior/new IDs and approval in the annex. Test platform access and transition audit before live use.

12.5 HANDOVER AND AIM MAINTENANCE#

Before handover, the asset information owner confirms AIR scope, maintainable assets, receiving system/profile, required safety/O&M records and data/document update owners. Task teams reconcile as-constructed evidence with approved design and identify uncertain/unverified conditions; a model labelled as-built is not proof of survey accuracy. Link every required asset to stable ID, location, maintainable type, data source, current documents and residual-risk records. Populate values only from authorised sources, preserving provenance and uncertainty.

Recipient acceptance includes actual asset-system import, key/relationship checks, document opening/access, unit checks and a representative changed/replaced asset update. Record duplicates, missing required records and any permitted conditional scope. Transfer the update procedure, access and training evidence, not just a final ZIP or export.

TriggerProducer / update ownerUpdated informationReceiving check / record
HandoverDelivery task teams / appointed asset-data leadVerified asset set, O&M, safety records and source revisionsAIR completeness plus target-system ingestion; handover decision ID
Maintenance / replacementOperational data owner with responsible maintainerStatus, new component identity, service records and changed documentsReferential integrity, retired/replacement link and approved AIM revision
Inspection / incidentAsset/safety ownerCondition, hazard/control and action recordsCompetent review, changed-use/security controls and acknowledgment
DecommissioningAsset owner and records authorityRetired assets, retained safety/record evidenceRetention/legal-hold disposition and removal of obsolete access

Decision (BIM Manager, 2026-10-14): The appointed operational owner reviews AIM after inspection, failure, substitution, replacement, use/system/access change, incident or disposal and annually for unchanged records; office performs only appointed updates. Basis: ISO 19650-3:2020 centres operational trigger events S03.

Record operational custody and actual update responsibilities; security/safety governance continues through operation and disposal. For Dubai buildings, hand over the Law No. 3 of 2026 duty: a Quality & Safety Certificate is needed after 20 years from completion (valid 10 years, 5 years at 40+ years) (2.6; BBM-STD-75/76). The certificate procedure is DM circular 11-9-1 of 2026; when the office is appointed as the assessing engineering office it follows BBM-STD-75 §7.

13 GLOSSARY#

Purpose

Define and centralize project terminology. Use this section for manual-specific terms and point to the canonical glossary for all others.

Canonical source

Primary glossary: Office Glossary V0.3; use the approved project edition

Rule: If a term exists in the canonical glossary, do not duplicate here. Add a “Manual note” only if the meaning is narrowed for this manual.

Manual-specific terms and notes

TermDefinition or Manual noteReference
Acceptance GateFormal decision point with A, B, C outcomes and required evidence set for progression2.1 Governance and Gates
Data CompletenessValid applicable values divided by applicable required values, scoped by exchange and object class; mandatory requirements must all pass (3.2)3.2 Parameters and LOIN
Model HealthQuantitative stability and hygiene metrics benchmarked at gates9.2 Quality Control
LOINLevel of Information Need combining geometry, alphanumerics, and documentation expectations3.2 Parameters
PackFormal dated issue folder with required children and transmittal7.3 Publishing
SHAREDCDE area for approved-to-share information, distinct from WIP and PUBLISHED12.1 Folder Structure
WIPWork-in-Progress area; naming may include temporary tokens; never issued from here12.1 Folder Structure
Gate-CriticalIssue flag indicating it blocks the upcoming gate unless resolved or waived10.2 Coordination • 10.3 Issue Tracking

Abbreviations used in this manual

Discipline codes: see 12.3.1 and BBM-STD-93

ARC: Architecture

STR: Structure

MEC: Mechanical

ELE: Electrical

PLU: Plumbing / public health

FLS: Fire and Life Safety

LSC: Landscape

GEN: General

MEP: Mechanical, Electrical, Plumbing (umbrella label, not a code)

BEP: BIM Execution Plan

EIR: Exchange Information Requirements

CDE: Common Data Environment

MVD: Model View Definition

Maintenance

Owner: BIM Manager (glossary custodian, BBM-STD-00)

Changes: Propose edits to BBM-STD-00 Glossary. If a manual-specific note is needed, add here and cross-link

Evidence: Record material glossary updates in 04-ARCHIVE/01-STANDARD-UPDATES

Acceptance — 13 Glossary

Terms in this manual are either identical to the canonical glossary or include a clearly labeled “Manual note”

No conflicting definitions between this section and the canonical glossary

Abbreviations used on sheets and in schedules match this section or BBM-STD-00 Glossary

14 APPENDICES#

Spec — 14 Appendices

Use these ready-to-copy templates and curated examples to accelerate consistent authoring and issuing.

A. TEMPLATES AND EXAMPLES

A.1 Pack templates (PUBLISHED)

Folder skeleton

00-COVERSHEETS

01-DRAWINGS

02-MODELS

03-SCHEDULES

04-REPORTS

05-TRANSMITTAL

Files included

00-COVERSHEETS: README-Pack.md, Issue summary cover PDF

04-REPORTS: ModelHealth-YYYYMMDD.pdf, ClashReport-YYYYMMDD.pdf, DataCompleteness-YYYYMMDD.pdf, NamingValidation-YYYYMMDD.txt

05-TRANSMITTAL: Transmittal-YYYYMMDD.pdf, Manifest.csv

A.2 Transmittal template (Markdown)

Title line: Transmittal — ORG PROJ

Date: YYYY-MM-DD

Description: <Issue purpose>

Confidentiality: <e.g., Internal / External>

Recipients

  • Company — Contact — Role — Distribution code (A/I/R)

Files

FilenameTypeRev/VerSizeChecksum

Notes

  • Related contract instruction: <ref>
  • Export preset(s): <IFC4-RV-vNN / …>
  • CDE path: 00-PIM/03-PUBLISHED/<NN-STAGE-N>/<YYYY-MM-DD-DESCRIPTION>/...

A.3 Start View template (content blocks)

Identifiers: ORG, PROJ, DISC, Model name, Revit version, Date

Audit panel: Model Origin OK?, Workset1 elements, Warnings count, Link status, File size

Banner: Next gate name and date

Governance: View Template = QA - Audit, Default on open

A.4 View template names (canonical; no ":" in names)

DOC - Plan 1-100

DOC - Section

DOC - Elevation

DETAIL - 1-5 / 1-10

COORD - 3D Clash

QA - Audit

SHT-PREP - Parent

A.5 Schedules presets (fields)

Doors: Mark, Type, Width, Height, Fire_Rating, Fire_Rating_Standard, Classification_Code

Windows: Mark, Type, Width, Height, Glazing, Classification_Code

Equipment (MEP): Mark, Family, Type, System, Level, Classification_Code, Asset_ID

Room/Space: Name, Number, Level, Area, System, Zone

A.6 IFC export preset checklist

Coordinates = Shared

Psets = Include schedules and mapped parameters

Elements = Exclude non-issued worksets and temporary categories

File name = CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ifc

A.7 Naming quick reference

Files: CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext (legacy internal WIP alias ORG-PROJ-DISC-PHASE-SEQUENCE, never issued)

Views: DISC-LEVEL-ZONE-TYPE-DESC

Sheets: DISC-CAT-INDEX

Pack folder: YYYY-MM-DD-DESCRIPTION

A.8 README — Access Exception (template)

Title line: README — Access Exception

Exception: <describe>

Owner: <name or role>

Rationale: <why>

Effective date: YYYY-MM-DD

Expiry date: YYYY-MM-DD

Approved by: Information Manager, LAP

Review cadence: Per gate

Scope

  • Affected group/folder: <path>
  • Affected teams/users: <list>
  • Permissions delta: <from → to>

Notes

  • On expiry, remove exception; archive this README in 04-ARCHIVE

A.9 Issue pack checklist (short)

Pack folder name matches YYYY-MM-DD-DESCRIPTION

Children 00–05 present with required content

Templates locked, no per-view overrides

Each sheet's Rnn coherent across index, title block and manifest

Evidence posted within last 48 hours

Transmittal present and complete

Acceptance — 14A

Templates match the canonical names and structures in sections 2.4, 4.12, 7.3, 11.2, and 12.3

Every pack built with these templates passes all checklist items in 7.3

B. REFERENCES AND RESOURCES

Standards index and links to authoritative external specs, tools, and internal pages

Cross-reference: References section below and the BBM-STD-51 §3 edition register

AUTHORING CHECKLIST

[ ] Section purpose stated

[ ] Cross-references added

[ ] Acceptance criteria or thresholds defined where applicable

[ ] Examples or templates linked

[ ] Last reviewed date updated in 1.1

14.C REVISION ACCEPTANCE AND OFFICE DECISION REGISTER#

Review itemRevised location / inspectable evidenceDraft outcome
T02.1 office scope/leadership/improvement1.1 control register; 9.1.1 QMS/corrective-action recordPresent; office choices decided; live activation evidence pending
T02.2 organisational/project/asset trace2.5 requirements cascade/example; 12.5 AIM triggersPresent
T02.3 nine phases and usable procedures1.5 phase exit table; retained 3–12 procedures and new formsPresent
T02.4 policy/annex/software precedence1.1 hierarchy; 3.1 project naming register; 11.3 qualificationPresent
T02.5 security and lifecycle safety9.4 sensitivity, roles, incidents, HSI/risk forms; 12.5 handoverPresent
P1 bundled gap: naming/parameters/acceptance/security/safety3.1–3.3; 9.4; 11.3; 12.4Content corrected; no project test claimed
P2 bundled gap: cascade/QMS/annex adoption1.1; 2.5; 9.1.1; 11.3Content supplied; office choices recorded in BBM-STD-11 Decisions log; actual activation evidence separate
P3 mobilisation pilot11.3 representative pack and test recordProcedure supplied; actual private pilot not executed
Office decision groupDecided office valueApproval record to complete
Ownership and review;;; (full text in the sections listed in the Manual and in BBM-STD-11)Decision ID, approver/deputy, effective date and affected projects
Naming / revision / states;;; (full text in the sections listed in the Manual and in BBM-STD-11)Approved project grammar/register, alias migration and code lists
Data / worksets / QA;;; (full text in the sections listed in the Manual and in BBM-STD-11)Confirm scope and metric denominators; no waiver of binding requirements
Exchange/tools;;;;;;;;;;;;;; (full text in the sections listed in the Manual and in BBM-STD-11)Actual installed builds, controlled presets, mobilisation and receiver test IDs
Security / safety / operation;; (full text in the sections listed in the Manual and in BBM-STD-11)Named authorities, supplier controls, retention schedule and receiving responsibilities

Editorial closure of the legacy conflicts C01–C07, C09–C12 and C14–C19 is traced in the BBM-STD-11 change trace; V0.4 closes rows. The 15/5 mm conflict is resolved by the existing Clash matrix decision and section 3 table, which supersedes blanket stage values. This lane decides office defaults without asserting signed project rights or passed installed-tool/receiver tests; authority-specific requirements remain in the verified project annex.

References#

Source selection follows RESEARCH.md (14 October 2026). Publisher scope/status and archived guidance support the procedures; no unverified normative clause number is asserted. Obtain the licensed adopted standards and binding project requirements before a compliance claim. References provide authority, not permission to copy third-party manuals.

  • S01 — ISO 19650-1 — Concepts and principles. ISO; 2018, ed.1. Publisher source.
  • S02 — ISO 19650-2 — Delivery phase of the assets. ISO; 2018, ed.1. Publisher source.
  • S03 — ISO 19650-3 — Operational phase of the assets. ISO; 2020, ed.1. Publisher source.
  • S04 — ISO 19650-4 — Information exchange. ISO; 2022, ed.1. Publisher source.
  • S05 — ISO 19650-5 — Security-minded approach to information management. ISO; 2020, ed.1. Publisher source.
  • S06 — ISO 19650-6 — Health and safety information. ISO; 2025, ed.1. Publisher source.
  • S07 — ISO 7817-1 — Level of information need: concepts and principles. ISO; 2024, ed.1. Publisher source.
  • S08 — BS EN 17412-1:2020 — Withdrawn Standard; BS EN ISO 7817-1:2024 tracked changes. BSI; 2020 / 2024. Publisher source.
  • S09 — ISO 12006-2 — Framework for classification. ISO; 2015, ed.2. Publisher source.
  • S10 — Uniclass — Download tables and change history. NBS; Live; July 2026 release observed. Publisher source.
  • S11 — ISO 16739-1 — IFC: data schema. ISO; 2024, ed.2. Publisher source.
  • S12 — Industry Foundation Classes (IFC). buildingSMART International; Undated live page; 2024 ISO edition. Publisher source.
  • S13 — BCF 3.0 XML and API. buildingSMART International; final 18 June 2021; BCF 2.1 (2017) fallback; BCF-XML v3.0, checked 2026-11-04. Publisher source.
  • S15 — NBIMS-US v4 — Standard / resources, including COBie v3. National Institute of Building Sciences (NIBS); v4; COBie V3.0 published 2023 as part of NBIMS-US V4 (NIBS version history, checked 2026-11-05); COBie 2.4 (NBIMS-US V3) stays the default unless the EIR names v3. Publisher source.
  • S16 — ISO 23386 — Methodology to describe, author and maintain properties in interconnected data dictionaries. ISO; 2020, ed.1. Publisher source.
  • S17 — ISO 23387 — Data templates for objects used in the life cycle of assets. ISO; 2025, ed.2. Publisher source.
  • S20 — Information Delivery Specification (IDS). buildingSMART International; 1.0 final, June 2024 (releases, checked 2026-11-04). Publisher source.
  • S21 — RIBA Plan of Work 2020. Royal Institute of British Architects; 2020. Publisher source.
  • S37 — Information protocols supporting delivery and operational phases — Guidance. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.3, August 2022. Publisher source.
  • G-A — Guidance A — The information management function and resources. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.2, February 2021. Publisher source.
  • G-C — Guidance C — Facilitating the CDE workflow and technical solutions. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.1, September 2020. Publisher source.
  • G-D — Guidance D — Developing information requirements. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.2, February 2021. Publisher source.
  • G-E — Guidance E — Tendering and appointments. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.2, February 2021. Publisher source.
  • G-F — Guidance F — About information delivery planning. IMI Framework (formerly UK BIM Framework, renamed May 2025); archived; ed.1, September 2020. Publisher source.
  • P01 — BIM Project Execution Planning Guide — Reader's Guide. Penn State Computer Integrated Construction Research Program; v2.2, 2019. Publisher source.
  • P02 — Define Supporting Infrastructure for BIM Implementation. Penn State; v2.2, 2019. Publisher source.
  • P04 — ISO 9001 — Quality management systems: requirements. ISO; 2026, ed.6, published 16 September 2026. Publisher source.
  • P06 — Security-Minded Approach to Digital Engineering. UK National Protective Security Authority (NPSA); Undated live guidance. Publisher source.
  • A01 — Project Templates; Create a Model. Autodesk Revit Help; Revit 2026. Publisher source.
  • A02 — Workflow: Setting up a Workshared Project; Enable Worksharing. Autodesk Revit Help; Revit 2026. Publisher source.
  • A03 — Workflow: Revit Cloud Worksharing; About Revit Cloud Worksharing. Autodesk Revit Help; Revit 2026. Publisher source.
  • A06 — Create Shared Project Parameters. Autodesk Revit Help; Revit 2026. Publisher source.
  • A10 — How to set up Shared Coordinates using one Revit model as the Site or Base file. Autodesk Support; 15 August 2026. Publisher source.
  • A11 — About Graph Security and Trusted Folders. Autodesk Dynamo Player Help; Revit 2026. Publisher source.
  • A12 — Add-in Registration. Autodesk Revit API Developer's Guide; Revit 2026. Publisher source.

Sources checked 2026-11-04#

  • DM-9-1-2 — Dubai Municipality circular 9-1-2, 13 Oct 2023. PDF.
  • DM-9-1-3 — Dubai Municipality circular 9-1-3, 15 Jan 2026, effective 1 Apr 2026. PDF.
  • DBC — Dubai Building Code (Decree 45/2021). DM laws and orders; Administrative Resolution No. 225 of 2024, 13 Aug 2024. DM.
  • DUBAI-LAW-3-2026 — Law No. 3 of 2026 Concerning the Quality and Safety of Buildings, 27 Feb 2026. Dubai Legislation Portal.
  • DM-11-9-1 — DM circular (11-9-1) of 2026 applying Law No. 3 of 2026, 1 Oct 2026, and guidance manual 11-9-1-1. Circular; manual. Checked 2026-11-05.
  • UAE-FLS — UAE Fire and Life Safety Code of Practice, September 2018. DCD.
  • ADIBC — Abu Dhabi International Building Codes 2013. DMT ADIMC-2013.
  • ADM-BIM — ADM BIM Code of Practice, Oct 2020. DMT.
  • ESTIDAMA — Pearl Rating minimums, DMT news 8 Jan 2025. DMT.
  • ALSAFAT — Al Sa'fat Dubai Green Building System, 2nd ed., Jan 2023. DM.
  • DUBAI-CRS — EPSG:3997 WGS 84 / Dubai Local TM. epsg.io; DMD vertical datum FIG 2011; Ras Ghumays datum EPSG 1146.
  • PDPL — Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data. UAE Legislation.
  • CTL-2025 — Federal Decree-Law No. 25 of 2025 Promulgating the Civil Transactions Law (Art. 821–824), effective 1 Jun 2026. UAE Legislation.
  • REVIT-SUPPORT — Autodesk previous versions and support lifecycle. Previous versions; Lifecycle; Revit 2027 updates; IFC exporter releases.
  • IFC-VALIDATION — buildingSMART IFC Validation Service. buildingSMART.
  • ISO27001 — ISO/IEC 27001:2022 + Amd 1:2024. ISO.
  • ISO13567 / ISO128 / ISO7200 — ISO 13567-1/-2:2017 (ISO); ISO 128-1:2020; ISO 7200:2004 (ISO).
  • ISO9001 — ISO 9001:2026 ed.6, 16 Sep 2026. ISO.
  • E57 — E57 3D imaging data exchange format; version and registration report recorded per delivery (BBM-STD-77).

Annex W2 S1 Core procedures ownership and distinct records#

This annex implements the usable security and HSI records (traced in the BBM-STD-11 change trace) and retains Manual 9.4 as the single security/safety procedure owner; the ISO 19650-5 security triage and management plan are owned by BBM-STD-87 and ISO 19650-6 H&S information by BBM-STD-88. Original V0.2 is unchanged, SHA-256 0ed7c2659219b38baaa0a3fed211b7a58caf58368fead5a6ddd7fdf0dc27106f; the Preservation sheet distinguishes original file bytes from equal normalized before/reconstructed Unicode text after removing the documented front changes. In V0.3 only front control metadata/history and appended annexes changed. Use roles 55, requirements 54, protocol interface 56, register 51, BEP V0.5 and AIR 52.

The Security forms and HSI forms have distinct dataset access policies and custodians. They contain synthetic templates only; no production ACL is configured. Do not combine actual restricted security assessments with broadly needed safety instructions in one file. Spreadsheet hiding/protection, passwords written in a cell, worksets and CDE folder names are not verified access control. Publish approved audience-specific derivatives with independent IDs/revisions/hashes and actual allowed/denied route tests. Safety information must reach its authorised duty-holders; sensitivity is not a reason to omit essential safety controls or to disclose the full security assessment unnecessarily.

Security Lead with IT/data owners assesses sensitivity, routes, suppliers, incidents and records custody; the competent Design Safety Lead and discipline designers assess hazards/controls and residual information; the appointed operational safety owner receives maintained information. Actual named holders/delegation/competence remain in the restricted Directory and must be established before access/release. Producer, independent competent reviewer, submission authoriser and accepting recipient have separate records. This annex gives no legal advice, risk waiver or transfer of designer/duty-holder obligations.

Annex W2 S2 Restricted sensitivity access and supplier records#

Sensitivity assessment identifies dataset/object/location scope, source revision/hash, aggregation/linkage exposure, confidentiality/integrity/availability consequences, affected parties, contract/legal source references, current protection and residual uncertainty. Security Lead records triage outcome, proportionate controls, approved sharing/use, reviewer/decision/date and next review/trigger. Assessment details themselves are restricted. Record a justified low-sensitivity outcome rather than assume every model is secret or every public-looking fragment harmless. Reassess at new recipient, changed dataset/aggregation, source/tool/host change, incident and lifecycle transition.

Synthetic SEC- R01 concerns a fictional plant-control layout and aggregation with route/asset information. Consequence is misuse of detailed operational access information; the assessment remains restricted to SYN-SEC01 and authorised IT/data reviewers. No real building, control address, key or exploitable detail is supplied. SEC- R01 is a proposed reduced safety/maintenance derivative with only task-relevant hazard/control information, an exact lineage/redaction review and approved operator recipients. The derivative is not approved merely by deleting columns.

Recipient access records dataset/revision, recipient role/organisation, purpose, least-privilege read/write/upload/download/share permissions, approved route/configuration, delegation/expiry and allowed/denied test IDs. Joiner/mover/leaver or emergency suspension actions link the Directory and revoke downstream/downloaded copies as appropriate; actual revocation and audit retention require tests. Synthetic policy permits Security Lead restricted assessment access, denies the operational recipient SEC- and permits only the approved reduced HSI route after review. No actual access grant is made by these rows.

Supplier obligations are a review schedule, not operative contract clauses: approved dataset/purpose/people/subprocessors, allowed storage/tool/AI route, downstream distribution, training/access controls, incident reporting route, return/offboarding/retention and verification owner. Record the actual agreed instrument/revision and responsible contract/security decision before release. Unapproved AI/public upload, link forwarding, uncontrolled local caching or an unknown recipient holds access. Do not insert credentials or personal contact data in the workbook.

Annex W2 S3 Incident evidence recovery notification and disposition#

Use a protected incident record with IncidentID, discovery/report timestamps including UTC offset, reporter and accountable roles, affected dataset/source/output revisions/hashes/recipients, observed event and uncertainty, initial risk/consequence, containment authority/scope, evidence chain, recovery baseline/retest, notifications and closure. Users report through the approved route; IT/Security authorises proportionate containment while preserving evidence. Do not delete original logs, alter evidence or broadcast sensitive screenshots. Record custodian, collection method/time, immutable copy hash/protected URI, transfers/recipient/time and analysis copies separately. No actual evidence hash is fabricated for the synthetic exercise.

INC- is a fictional exercise: a proposed supplier link for SEC- is sent to an unauthorised role; expected denial prevents access, while any actual unexpected disclosure would trigger incident escalation and a held distribution route. The table gives a simulated discovery time 2026-10-16T12:00+04:00, not an event reported by this task. Actual platform logs, evidence, access revocation and receiver receipts are Not executed. The exercise covers an accidental disclosure attempt without supplying sensitive real data.

Legal/security notification authority decides applicability, recipient, content, timing and approval using actual requirements (including the UAE PDPL, Federal Decree-Law No. 45 of 2021, where personal data is involved; BBM-STD-90); this pack invents no statutory reporting deadline. Notification records hold source obligation, decision owner/date, approval and transmission/receipt evidence, including a reasoned decision not to notify where authorised. Recovery uses a preserved known baseline in isolation; verify identities/values/permissions and denied routes before restored service/distribution is authorised. Retain the incident's original failed evidence and corrective/retest trail.

Retention/disposal records dataset/revision/storage copies/backups, purpose, approved schedule/source/trigger/duration, legal-hold authority/status, disposal authoriser, method, copies/recipient retrieval, backup treatment and deletion/disposition evidence. Durations remain pending actual approved schedules; no universal period or instruction to destroy is supplied. A legal hold or unresolved authority blocks disposal. Remove obsolete access separately from deciding record destruction; backup expiry does not prove downloaded copies were removed. Actual restoration, notifications, access changes and disposal are outside this editorial task.

Annex W2 S4 Structured safety hazards and residual controls#

Keep HSI records separately controlled for the safety-information audience. Each HazardID links description, cause/event/consequence, lifecycle activity/exposed group, location/zone and stable object ID, source model/document revision/hash, origin/date/uncertainty and significant assumptions. Record prevention/control choice and evidence, responsible competent designer, independent competent reviewer/delegation, specialist risk method/criteria, residual risk/action/owner/due date and change triggers. An information-delivery likelihood score from BEP 10.4 cannot replace specialist design/safety assessment or determine that a hazard is safe.

HSI- R01 concerns maintenance withdrawal at AHU-001 / LOC-L01, source EIR-011-D design note R01 and fictional requirement SYN-REQ-A01. The source fixture gives 600 mm withdrawal need, 605 mm clear with ±10 mm uncertainty and conservative lower bound 595 mm: inadequate against that synthetic requirement. Proposed revised fixture 650 ± 10 mm yields lower bound 640 mm, but does not establish actual safe access. Competent designer must verify task method, other hazards and installed constraints; independent review and operational understanding remain pending. Record proposed change CH-SYN-HSI01 and source R02 separately; never rewrite the R01 hazard as if it had always passed.

HSI- records the unverified utility UT- crossing near PIPE- from BBM-STD-63: source record-only, depth/accuracy unknown. Control requires the competent utility/civil/safety owners' verification and approved work method before the affected operation. No invented depth or safe excavation clearance closes it. Record field/survey updates and source confidence before changing status. Model clash checks cannot transfer safety responsibilities or prove compliance with all applicable codes.

Each control/residual decision has scope, competent authority, date/evidence and any unresolved action. Mandatory unresolved safety information holds affected exchange/work. A reviewer may require more information or restrict use; an Information Manager cannot waive design/duty-holder obligations. Records support the responsible professionals, not a substitute certification or approval.

Annex W2 S5 Delivery operational acknowledgment and updates#

At design/coordination, construction, handover, operation, replacement and decommissioning, identify actual HSI requirements/recipients, authorised dataset/derivative version/hash, permitted purpose and access route, technical review/authorisation, exchange/transmittal and receiving evidence. Check stable asset/location/source links and retained uncertainty/control wording in both native/open/data/document representations. Source updates propagate by one ChangeID to hazard/control registers, models, instructions, AIR/AIM, relevant BEP/TIDP/MIDP and recipient notices.

Receiving acknowledgment records recipient identity/delegation, exact received version/hash/date, permitted task/use, understanding of constraints/control and remaining actions, acceptance/rejection reason, operational update owner and next review trigger. A delivered link or automatic read receipt is not understanding or acceptance. If access is denied or the wrong version arrives, keep the affected operation held and resolve an approved safe route; never make the restricted security assessment public to bypass the problem.

The synthetic HSI- delivery to SYN-OPS01 is Hold: the work method, competent review, actual source and operator acknowledgment are unexecuted. The derivative proposed in SEC- must preserve the relevant hazard/600 mm requirement/uncertainty and limits while omitting unnecessary security details; its exact redaction/content review is not completed by this text. Operational feedback, changed installation, inspection, incident, maintenance method or asset replacement reopens the record, confirms the update owner and informs affected recipients. Actual sign-off and safety adequacy are not implied by these templates.

Annex W2 S6 Adverse tests ownership and acceptance#

Security tests cover authorised read and unauthorised read/write/download/share, supplier/no-unapproved-AI route, offboarding, derivative redaction/lineage, incident evidence integrity, recovery and legal-hold disposal refusal. HSI tests cover complete ownership/source/object/location/controls, unsafe lower-bound clearance, unknown utility depth, changed/stale source links, lost safety wording in redaction, and recipient understanding/update responsibility. Reset each adverse case from its specified baseline; do not treat a favourable outcome from a different source as a retest of this failure.

Each test requires exact source/output hashes, actual route/configuration/build, role credentials checked without recording secrets, expected and observed result, operator/date, protected evidence URI, independent reviewer/disposition and separate authorisation/recipient decisions. All actual results in these two workbooks remain Not executed. Exercise outcomes are labelled expected only. No test sends data, changes live access, contacts a person, authorises work or destroys records in this task.

Acceptance requires complete accountable/technical/receiving ownership and actual evidence for the scoped dataset/task. Missing competent review, unverified disclosure/recipient, broken source, unresolved mandatory hazard/control or missing receiving acknowledgment holds affected release. Resolve security/safety access conflicts through both competent owners and the actual delegated authority, preserving essential safety information and protected security details in their separate records. No new parallel manual/risk owner or blanket waiver is created.

W2 annex references#

  • Retained Manual 9.4/12.5, BBM-STD-54/55/56/87/88, BEP V0.5 and the BBM-STD-11 change trace. Current original file hash and normalized preservation test are recorded in both forms.
  • ISO 19650-5:2020, security-minded lifecycle context. Clause 4 sensitivity/triage and clauses 5–9 security-minded arrangements are reading pointers corroborated by NPSA's indexed guidance note; full NPSA fetch returned 403, not a full-text/licensed clause audit. NPSA information disclosure triage also indexed but full fetch 403. No paid standard paragraphs copied.
  • ISO 19650-6:2025, published health/safety information concepts and collaborative lifecycle sharing; detailed normative clause interpretation requires licensed competent review. This is an information process, not legal or safety-design advice.
  • ISO 19650-1, -2 clauses 5.6/5.7 production/authorisation/receiving context, -3 operational update context and IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance Part 2 ed.5, archived; Guidance A ed.2 scoped functions, live checked 2026-10-16.
  • ISO 7817-1:2024 current LOIN concepts; BS EN 17412-1:2020 predecessor, with appointment editions changed only through controlled authority. ADM Code of Practice 4.3 sensitive-information interface; DM circular index and DDA current service remain project-specific applicability via BBM-STD-57 and BBM-STD-85. No general UAE disclosure/retention deadline inferred.
Document history
REVDATEDESCRIPTIONORIGINATED
V0.72026-11-05Standard watch no. 1: §2.6 and §12.5 cite DM circular 11-9-1 of 2026 (Building Quality and Safety Certificate) with Dubai Law No. 3 of 2026 and point to the assessment procedure in BBM-STD-75 §7; S15 COBie V3.0 published 2023Private review draft; actual approval pending
V0.62026-11-05§9.2 warnings gate: 0 blocking warnings at share, others ≤ 100 per 10,000 elements; §12.3 container token values from BBM-STD-93 §2.2Private review draft; actual approval pending
V0.52026-11-04QMS patch (BBM-STD-96..98 links): §9.1 purpose, practice-director role, office checklists in 07-QA-QC, QMS procedure links (§9.1.1); §9.3 one office NC logPrivate review draft; actual approval pending
V0.42026-11-04closure: authority BIM submissions (11.4) and local regulatory basis (2.6); CRS by EPSG code; 8-token file names everywhere; per-container revisions; Asset_ID, Classification_Code, Fire_Rating (/119/121); code pointers to BBM-STD-93; 2.5 mm text; software release policy (11.3.1); COBie per EIR; IMI Framework naming; links to BBM-STD-11 and current set versions; Notion artefacts removed; + cross-doc pointer pass (BBM-STD-86 CRS keys, 87 triage labels, 89 IDS sequence, 90 §3/§4, 91, 93 folder numbers and suitability states, 66 v2.0 assets, 67 title-block superset) + template alignment (..148) + folder names without dotsPrivate review draft; actual approval pending
V0.32026-10-16W2 security and safety record annexes; retained V0.2 proceduresPrivate review draft; actual approval pending
V0.22026-10-14Section-by-section correction of requirements, naming, acceptance, security/safety and annex controlPrepared for office review; approval pending

DOCUMENT AUTHOR

NAME & CO.ROLEEMAILCONTACT

ACKNOWLEDGED BY

NAME & CO.ROLEEMAILCONTACT

The office BIM Manual is a controlled document. This V0.5 is a review draft; revision creation does not authorise adoption or alter an appointment. The approval/effective-date fields below control release.