1 Introduction#
1.1 CONTROLLED BEP STATE AND REVISION RECORD#
Decision (BIM Manager, 2026-10-14): LAP owns project BEP, maintained by delegated IM with recorded deputy/project authoriser; review every exchange milestone and material team/tool/requirement change. Basis: Appointment functions determine ownership and authority S02, G-E.
This template is not a confirmed project BEP or evidence of mobilisation; commercial titles must map to appointment functions.
| BEP state | What is recorded | Exit condition / authority |
|---|---|---|
| Pre-appointment proposed | EIR response, intended uses, capability/capacity evidence, assumptions, proposed methods and deviations | Tender response reviewed; unresolved obligations and options visible |
| Confirmed delivery-team BEP | Actual appointments/teams, accepted commitments, EIR/requirements revision, responsibility matrices, TIDPs/MIDP and agreed methods | LAP confirms with task-team commitments and appointing-party review/acceptance required by the appointment; record signatures/decision IDs |
| Mobilised for defined production scope | Actual people/access/tool/workflow tests, actions and readiness decisions | Blocking tests/actions closed; LAP authorises only the tested scope; exceptions accepted by relevant authority |
| Changed / superseded | Impact assessment, approvals, revised requirements/annex/plans and communication | New controlled revision authorised; prior baseline retained read-only |
Contract award does not automatically confirm the BEP. Confirmation and mobilisation are separate decisions; the team may agree the confirmed plan while readiness actions are still open, but production release requires the appropriate gate in 6.1.1.
| Project control field | Entry / recommended value | Evidence requirement |
|---|---|---|
| Appointment / requirement baseline | [signed appointment, EIR ID/revision, AIR/PIR references] | Governing hierarchy and clarification decision IDs |
| Owner / deputy / authoriser | Decision (BIM Manager, 2026-10-14): LAP owns project BEP, maintained by delegated IM with recorded deputy/project authoriser; review every exchange milestone and material team/tool/requirement change. Basis: Appointment functions determine ownership and authority S02, G-E. | Named role holders and delegation evidence |
| BEP revision / status / effective date | Current office revision of this template (see Revision History); project revision and effective date after confirmation | No use as approved while fields are pending |
| Review cadence | Decision (BIM Manager, 2026-10-14): LAP owns project BEP, maintained by delegated IM with recorded deputy/project authoriser; review every exchange milestone and material team/tool/requirement change. Basis: Appointment functions determine ownership and authority S02, G-E. | Dated review and affected scope |
| Incorporated records | [naming/property/LOIN/security/rights annex IDs; plan/test/deviation versions] | Exact CDE URIs and immutable revisions, not unverified hyperlinks |
| Controlled distribution | Decision (BIM Manager, 2026-10-14): Distribute confirmed project BEPs only to authorised project roles with recipient/access register and acknowledgments; use role-scoped office templates and approved appointment extracts separately. Basis: Project access follows appointment scope and sensitivity S05, G-C. | Recipient/access register and acknowledgment |
| Change ID | Trigger / affected requirement and exchange IDs | Impact (time, capacity, tools, rights, security, safety) | Approval / scope / effective date | Updated documents and recipients |
|---|---|---|---|---|
| [ID] | [EIR/BEP/TIDP/MIDP/rule IDs] | [assessment and action owners] | [authoriser and recipient decision] | [revisions, notification evidence] |
1.2 SCOPE#
This BIM Execution Plan (BEP) is prepared as a direct reply for compliance with EIR requirements of this project. [The appointed party] will demonstrate the proposed approach, capability, capacity, and competence level to meet the MIDP/TIDP.
Planning basis: ISO 19650-1:2018 and ISO 19650-2:2018 (both in force; ISO/DIS 19650-1 ed.2 and ISO/DIS 19650-2 are drafts at stage 40.93 and not in force at 2026-11-04), with the project's actual Information Protocol and requirements to be recorded. This review template does not demonstrate project compliance or protocol incorporation.
Select the following discipline scope against actual appointments and EIR; do not assume every listed discipline is required:
INFRASTRUCTURE AND CIVIL
LANDSCAPE, EARTH WORKS, & ROADS
ARCHITECTURAL
STRUCTURES
MECHANICAL
ELECTRICAL
PLUMBING
FIRE FIGHTING
POWER AND UTILITIES
AUDIO VISUAL SYSTEMS
INTERIOR DESIGN
LIGHTING
VERTICAL TRANSPORTATION
KITCHEN LAUNDRY AND WASTE
THEMING
SPECIAL SYSTEMS “I.E., SECURITY SYSTEM…ETC.”
This list is not limited, and disciplines can be added/removed depending on each project.
This document records selected BIM uses, methods, tools and required information exchanges. Each use must have an intended decision/objective, producer, recipient, timing and measurable output; use NBIMS-US v4 BIM Execution Planning and Penn State BIM Project Execution Planning Guide v2.2 (2019) as planning references.
This document specifies the technology and process requirements for the BIM uses, as well as the model content requirements on the project. It introduces how model data shall be delivered, specifies the model and data management solution, and defines how project teams shall collaborate by means of BIM. Finally, the BIM organization of the project including expected roles and responsibilities is outlined.
Decision (BIM Manager, 2026-10-14): No blanket omission of cables/wires/conduits/items ≤50 mm needed for safety, coordination, quantities or assets; permitted omissions need scoped requirement, owner, alternative documentation and receiving approval. Basis: Information need is purpose-led, not blanket size/LOD S07, S06.
Legacy LOD 300 and blanket size exclusions do not establish the appointed scope.
This is a controlled live document: changes require the 1.1 impact/approval record; changed needs or resources do not silently alter agreed obligations.
1.3 PURPOSE OF THE DOCUMENT#
A successful Project requires a smart plan, lean scope, collaborative processes, team agreement, supporting technology and solid tracking, control and verification workflows.
Our project execution planning ensures that all parties are clearly aware of the opportunities and responsibilities associated with the incorporation of Building Information Modelling (BIM) into our project.
Our Plan details the correct processes for executing BIM throughout the project’s lifecycle.
On this project we will follow these four steps to ensure that all teams are meeting the project's Exchange Information Requirements:
Identify high value Model/BIM Uses that will support Exchange Information Requirements
Design and document optimal project execution processes
Define the BIM deliverables in the form of information exchanges
Develop the infrastructure in the form of contracts, communication procedures, technology and quality control to support the implementation
To gain the maximum benefits from our BIM implementation, once the Plan and Scope have been defined and appointed, the Task Teams will Schedule their own tasks, our team will Track the progress of assigned tasks and Verify task completeness before sharing the model for the described use case.
1.4 TERMS, ABBREVIATIONS AND CODES#
For any term or abbreviation used in this document refer to BBM-STD-00-GLOSSARY-V0.3; discipline/role, suitability and gate codes come from the one code dictionary BBM-STD-93-CODE_DICTIONARY-V0.1. Commercial titles used in this template map to ISO 19650 functions as follows:
| Term | Meaning in this BEP | ISO 19650 function |
|---|---|---|
| LDC | Lead design consultant | Lead appointed party (LAP) where so appointed; otherwise an appointed party |
| PMC | Project management consultant acting for the client | Appointing party's delegate, only within recorded delegation |
| CC | Cost consultant | Appointed party (task team) |
| KCP | Key contact person of an organisation | Role contact only; personal details held in the Directory |
| CLIENT | The client organisation | Appointing party |
1.5 DOCUMENT AUTHORITY#
This document defines the requirements of different stakeholders that will become part of the project delivery team at different stages of the development of the project.
The document provides a structure and specification for the development of the BIM Execution Plan and associated documents and the delivery of the Project Information Model (PIM) in accordance with the appointing party's exchange information requirements and the subsequent hand back of information to the appointing party's team.
The BEP are applicable to the entire project team and all project-related data. Project data should be stored in a secure manner and managed in a consistent and structured framework. Data must be protected against unauthorized access, alteration, disclosure, and modification and managed with relevant procedures.
1.6 BIM INTENT#
Building Information Model (BIM) or “Model” is a parametric, computable representation of the project design developed by the design task teams under the LDC (LAP where so appointed) and the construction model will be developed by the contractor. As used in this BIM specification, references to Building Information Model, BIM, or the Model, include the primary design model or models and all linked, related, affiliated, or subsidiary models developed for design, analysis, estimating, detailing, fabrication, construction, operation or maintenance of the project, or any portion or element of the project.
1.7 RIGHT OF RELIANCE#
Permitted reliance follows the signed appointment/Information Protocol, the identified exchange's intended use and its recorded authorisation/acceptance. A Design Model may support construction-model development only within that agreed scope; model transfer does not transfer design responsibility, certify all conditions or authorise fabrication from a reference-only exchange. Native editability, a BIM label and mutual exchange do not create reliance rights. Competent design review and contract duties remain with the appointed parties.
Record exact container IDs/revisions, accuracy/verification limits, permitted purposes, relying recipients and restrictions in the rights/reliance schedule. Any conflicting or missing particulars go to the contract/legal owner before the affected use. Follow the appointment-incorporated Information Protocol; office reference template: IMI Framework (formerly UK BIM Framework, renamed May 2025) Information Protocol template for BS EN ISO 19650-2 (Ed 6) and its guidance, edition 3 (August 2022). The CIC BIM Protocol 2nd edition (2018) is legacy, historical context only. The technical BEP implements contractual duties and does not replace the protocol.
1.8 OWNERSHIP AND USE OF BIM MODEL AND DATABASE#
The V0.2 blanket transfer of all copyrights and its exclusive/non-recoverable licence wording is removed from this technical template because ownership, licence and legal intent were unverified. No replacement right is deemed granted by issuing any office revision of this template. The signed appointment, agreed protocol and third-party terms control; obtain specialist legal approval of actual particulars, including delivery and operation.
Decision (BIM Manager, 2026-10-14): Use non-exclusive project-purpose licence as negotiation baseline; retain background IP, schedule project-created/background/third-party rights and defined lifecycle uses/recipients; contract owner settles duration/transfer/sublicensing/revocation/exclusivity in signed terms before reliance. Basis: Adopts a negotiation position, not rights absent a signed protocol S37 (S36 CIC BIM Protocol 2018: legacy, historical context only).
Actual licence particulars belong in signed appointment/protocol terms; no legal right is granted by this office negotiation baseline.
| Rights / reliance item | Recommended value or completion requirement | Contract check / hold point |
|---|---|---|
| Project-created / background / third-party material | Decision (BIM Manager, 2026-10-14): Use non-exclusive project-purpose licence as negotiation baseline; retain background IP, schedule project-created/background/third-party rights and defined lifecycle uses/recipients; contract owner settles duration/transfer/sublicensing/revocation/exclusivity in signed terms before reliance. Basis: Adopts a negotiation position, not rights absent a signed protocol S37 (S36 CIC BIM Protocol 2018: legacy, historical context only). | Evidence that each contributor has authority to grant specified rights |
| Permitted uses / recipients | Decision (BIM Manager, 2026-10-14): Use non-exclusive project-purpose licence as negotiation baseline; retain background IP, schedule project-created/background/third-party rights and defined lifecycle uses/recipients; contract owner settles duration/transfer/sublicensing/revocation/exclusivity in signed terms before reliance. Basis: Adopts a negotiation position, not rights absent a signed protocol S37 (S36 CIC BIM Protocol 2018: legacy, historical context only). | Signed licence/protocol IDs; no unrelated project/public/AI reuse by assumption |
| Licence scope | Decision (BIM Manager, 2026-10-14): Use non-exclusive project-purpose licence as negotiation baseline; retain background IP, schedule project-created/background/third-party rights and defined lifecycle uses/recipients; contract owner settles duration/transfer/sublicensing/revocation/exclusivity in signed terms before reliance. Basis: Adopts a negotiation position, not rights absent a signed protocol S37 (S36 CIC BIM Protocol 2018: legacy, historical context only). | Legal owner confirms actual scope, duration, transfer, sublicensing and any exclusivity |
| Model reliance | Decision (BIM Manager, 2026-10-14): Rely only on authorised accepted revisions for stated scope/use and contract accuracy/limitations; no unrelated project/public/AI reuse is implied; protect distribution, records and appointed operational custody. Basis: Rights/reliance follow signed terms and exchange decisions S37, S04. | Contract-required accuracy, limitations and designer responsibility |
| Liability / insurance / jurisdiction | Actual signed appointment particulars; no default technical waiver | Legal/insurance review ID and unresolved items |
| Confidentiality / retention / operation | Decision (BIM Manager, 2026-10-14): Use records/legal-owner-approved retention by record class and actual legal/contract duties; apply legal holds, preserve approvals/accepted evidence and revoke redundant access; no universal deletion period, and missing schedules hold affected activation. Basis: Security/protocol guidance supports proportionate records control, not invented jurisdiction-wide periods S05, S37. Decision (BIM Manager, 2026-10-14): Rely only on authorised accepted revisions for stated scope/use and contract accuracy/limitations; no unrelated project/public/AI reuse is implied; protect distribution, records and appointed operational custody. Basis: Rights/reliance follow signed terms and exchange decisions S37, S04. | Security and operational obligations aligned with licence/contract |
| Precedence / amendments | Binding appointment/protocol hierarchy; record all incorporated editions | Conflicts held; amended rights need appropriate signed approval |
| Approval | Contract/legal owner plus authorised signatories | Record names/roles, dates and exact approved particulars; pending here |
1.9 DEVIATIONS FROM STANDARDS AND EIRS#
Record proposed deviations in the tender response and change/deviation register, with requirement ID, reason, impact, alternative and approving authority under the appointment. A programme BIM manager cannot alone waive a binding client, legal or safety requirement. Keep pending deviations outside authorised delivery scope until the required decisions are recorded.
1.10 RELATIONSHIP OF BIM REQUIREMENTS TO OTHER REQUIREMENTS#
Modelling extent, materials and visual assets follow the approved LOIN (6.5) for each selected use; visualisation/VR content is produced only where that use is selected in 3.2.1. There is no blanket inclusion or size-based exclusion. Any non-modelled element is listed with its alternative documentation, owner and approval by [APPOINTING PARTY] before the affected exchange. Client-specific visual requirements (for example visitor-facing elements) belong in a project-specific EIR annex, not in this office template.
Non-modelled elements are documented and constructed in accordance with supplementary design information that has been fully coordinated with the modelled information.
1.11 STANDARDS, CLASSIFICATIONS AND SPECIFICATIONS#
Throughout this project we are adhering to the following:
RIBA plan of work 2020.
ISO 19650-1:2018 and ISO 19650-2:2018 provide concepts and delivery processes for managing the production, distribution, and quality of construction information. This method includes construction information produced using CAD systems.
Uniclass 2015 is a unified classification system developed for the UK construction industry covering all sectors of the industry. Uniclass 2015 is used for the naming of all components (content) on the [APPOINTING PARTY] Programme. Modelled elements will be populated with accurate Uniclass information throughout the design phase of the project and complete for the applicable required object/field scope at its specified exchange. This will allow for the successful export and identification of modelled elements. Uniclass codes are stored in Classification_Code with ClassificationTable, ClassificationTitle and ClassificationRelease per 8.6 (re-affirming); Revit Assembly Code and "Classification Code (Uniclass)" are not used unless mapped as aliases in the dictionary (BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2). Adopted release: Uniclass 2015 July 2026 release (Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27) unless the appointment names another; record the release in ClassificationRelease. Uniclass tables: https://uniclass.thenbs.com/download (checked 2026-11-04).
COBie (Construction Operations Building information exchange) is a structured asset-data exchange specification; choose its exact version/profile and receiving system in 7.3. Its most common use is in product data handover from construction to operations AM/FM (Asset Management and Facilities Management). COBie is delivered when the EIR requires it, in the version specified in the EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4).
1.12 APPLIED STANDARDS AND DOCUMENTS#
Editions below mirror the one edition/adoption register in BBM-STD-51-REGISTERS-V0.2 §3; where they differ, that register governs, and the appointment-incorporated edition governs a project exchange. UAE requirement detail lives in BBM-STD-85-UAE_AUTHORITY_SUBMISSIONS-V0.1. All rows checked 2026-11-04.
| RESOURCE | CATEGORY | EDITION | USED IN (BEP §) |
|---|---|---|---|
| ISO 19650-1:2018 | Concepts and principles (in force; ISO/DIS 19650-1 ed.2 at stage 40.93, not in force) | 2018 | 1.2, 6.6 |
| ISO 19650-2:2018 | Delivery phase (in force; ISO/DIS 19650-2 at stage 40.93, not in force) | 2018 | 1.1, 5.2.4, 6.1–6.4, 7.2 |
| ISO 19650-3:2020 / -4:2022 / -5:2020 / -6:2025 | Operation / exchange / security / health and safety information | 2020 / 2022 / 2020 / 2025 | 7.3, 5.2.4, 10.3, 1.13, 10.4 |
| ISO 7817-1:2024 | Level of information need (replaces EN 17412-1:2020) | 2024 | 6.5 |
| ISO 12006-2:2015 (last confirmed 2020; to be revised) / ISO 12006-3:2022 | Classification framework / object-oriented information | 2015 / 2022 | 1.11, 8.11.2 |
| Uniclass 2015, July 2026 release | Classification tables Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27 | Jul 2026 | 1.11, 8.6, 8.11.2 |
| ISO 23386:2020 / ISO 23387:2025 | Property governance / object data templates | 2020 / 2025 | 8.6 |
| ISO 16739-1:2018 (IFC 4.0.2.1, IFC4 ADD2 TC1) | Default Reference View profile EX-P01 | 2018 | 7.4 |
| ISO 16739-1:2024 (IFC 4.3.2.0) | Only via a separately approved profile row after a passing test exchange | 2024 | 7.4 |
| buildingSMART IDS 1.0 | Information Delivery Specification (final, June 2024) | 1.0 | 7.4 EX-P05, 10.3 |
| buildingSMART BCF 3.0 (BCF 2.1 fallback) | Issue exchange (BCF-XML v3.0 final 2021-06-18; BCF 2.1 2017) | 3.0 | 7.4 EX-P03, 8.12 |
| buildingSMART IFC Validation Service | Schema/normative-rule conformance check (live service) | live | 10.3 OPEN-01 |
| ISO 29481-1:2025 / -2:2025 / -3:2022 | Information delivery manual: methodology / interaction framework / data schema | 2025 / 2025 / 2022 | 3.2.1, 6.6 |
| ISO 21597-1:2020 / -2:2020 | Information container for linked document delivery | 2020 | 5.2.4, 7.1 |
| COBie | Version as specified in the EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4) | per EIR | 1.11, 7.3, 7.4 EX-P04 |
| ISO 9001:2026 | Quality management systems (ed.6, 16 Sep 2026; replaces ISO 9001:2015) | 2026 | 10 |
| ISO/IEC 27001:2022 + Amd 1:2024 | Information security management controls | 2022 / 2024 | 1.13, 10.4 |
| ISO 13567-1/-2:2017 | CAD layer organisation | 2017 | 7.1 (DWG exchange) |
| ISO 128-1:2020 / ISO 7200:2004 | Drawing representation / title-block data fields | 2020 / 2004 | 8.4 |
| RIBA Plan of Work 2020 | Stage framework | 2020 | 2.6, 5.5 |
| BBM-STD-69-FAMILY_STANDARD-V0.2 | Office object standard, aligned to ISO 23387:2025; the NBS BIM Object Standard is a historical reference only (edition not verified) | V0.2 | 8.3.3, 8.6 |
| Dubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 (13 Aug 2024) | Dubai building permits: apply the DBC plus all DM amending resolutions in force at permit submission | 2021 + amendments | 3.2.2 Code Validation |
| DM circulars 9-1-2 (13 Oct 2023) and 9-1-3 (15 Jan 2026, effective 1 Apr 2026) | Dubai BIM permit submission (BBM-STD-85) | 2023 / 2026 | 3.2.2, 6.6, 7.4 EX-P06 |
| Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings | Asset-life obligation: Building Quality and Safety Certificate after 20 years from completion, procedure in DM circular 11-9-1 of 2026 (not a design-permit rule) | 2026 | 7.3.1 |
| UAE Fire & Life Safety Code of Practice | National fire code: September 2018 edition plus the emirate authority's amendments current at project start, recorded here | 2018 + amendments | 3.2.2, 8.6 Fire_Rating |
| Abu Dhabi International Building Codes (ADIBC) | The ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04) | 2013 | 3.2.2 |
| DMT/ADM BIM Code of Practice (Oct 2020) | Abu Dhabi building work where the appointment/authority requires BIM; ADM Documentation Guidelines for Infrastructure v1.0 (Oct 2020) and Infrastructure BIM Object Catalogue v2.0 (May 2021) apply to infrastructure only; no general Abu Dhabi building-permit BIM mandate found | 2020 / 2021 | 3.2.2, 7.4 |
| Estidama Pearl Rating System (Abu Dhabi) | Permit condition: private projects min 1 Pearl, government-funded min 2 Pearl | DMT 8 Jan 2025 | 2.7, 3.2.2 |
| Al Sa'fat Dubai Green Building System, 2nd edition (Jan 2023) | Silver Sa'fa mandatory for all new buildings in Dubai | 2023 | 2.7, 3.2.2 |
| UAE PDPL, Federal Decree-Law No. 45 of 2021 | Personal data protection (effective 2 Jan 2022) | 2021 | 1.13 |
1.13 BIM INFORMATION CONFIDENTIALITY AND NON-DISCLOSURE#
Apply the signed confidentiality/NDA and security particulars to models, data, documentation, renders, reports and derived outputs. Confidentiality does not by itself determine copyright ownership; rights are settled under 1.8. Distribute only for the permitted appointment purposes to authorised recipients with a need to know. Supplier/subcontractor access and obligations must be checked before onboarding; do not upload private data to public validators, unapproved plugins or AI services.
The security owner assesses asset/information sensitivity and consequences before platform selection and at changed scope, team, sharing or operational use. Record permissions, protected transfer/storage, downloads, retention/legal holds, access removal and incident reporting in the project security annex. Test allowed and denied access, maintain induction records, review joiner/mover/leaver permissions and preserve an incident audit trail. Use ISO 19650-5:2020, ISO/IEC 27001:2022 + Amd 1:2024 controls and BBM-STD-01-MANUAL-V0.5 §9.4; the security triage and security management plan are owned by BBM-STD-87-SECURITY_MANAGEMENT-V0.1. Actual security/retention authority and reporting routes must be entered before mobilisation.
Personal data in project information (CDE, issue, RFI, Directory and site records) is processed under the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021, effective 2 Jan 2022) and any Executive Regulations listed on uaelegislation.gov.ae at project start, plus any free-zone data-protection regime that applies where a party is established there (for example DIFC or ADGM), as confirmed by the legal owner. Record the CDE hosting region and cross-border transfer basis in the security annex; personal-data handling follows BBM-STD-90-RECORDS_RETENTION_AND_PERSONAL_DATA-V0.1 §4 and retention its §3 schedule.
Decision (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.
Decision (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.
Safety records trace hazards/objects/locations to source revisions, controls, competent reviewers, residual owners and receiving acknowledgment through operation and disposal; ISO 19650-6:2025 requirements are owned by BBM-STD-88-HEALTH_AND_SAFETY_INFORMATION-V0.1.
2 General Information#
2.1 Project general information#
| TYPE | INFORMATION |
|---|---|
| PROJECT OWNER: | |
| PROJECT NAME | |
| CONTRACT TYPE / DELIVERY METHOD | |
| CONTRACT NUMBER | |
| PROJECT REF | |
| BRIEF PROJECT DESCRIPTION | |
| PM | |
| ARC | |
| STR | |
| MEP | |
| LSC | |
| INT | |
| PMC | |
| GROSS BUA | |
| PLANNED START DATE | |
| PLANNED END DATE |
2.2 Project location#
| TYPE | INFORMATION |
|---|---|
| PROJECT LOCATION AND ADDRESS | |
| CRS REGISTER KEY (CRS-DXB / CRS-AUH / CRS-OTH, BBM-STD-86 §2) | |
| HORIZONTAL CRS (EPSG CODE + NAME, TRANSFORMATION) | |
| VERTICAL DATUM | |
| SURVEY CONTROL POINT IDs (≥3 WELL-DISTRIBUTED) | |
| COORDINATE AUTHORITY / SOURCE DOCUMENT AND DATE |
Defaults (detail and register in BBM-STD-86-COORDINATES_AND_GEOREFERENCING-V0.1): Dubai horizontal CRS DLTM, EPSG:3997 "WGS 84 / Dubai Local TM"; Dubai vertical datum DMD (Dubai Municipality Datum = Port Rashid datum; no EPSG code). Abu Dhabi horizontal CRS: the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, recorded with its EPSG code and transformation here and in 8.2; Abu Dhabi vertical datum Ras Ghumays (EPSG datum 1146). Other locations: per appointment. Never hard-code EPSG:32640. The declared CRS is written into IFC (IfcProjectedCRS + IfcMapConversion) and checked in MOB-03.
2.3 Project brief#
Brief
Appointing Party Contact Details
| APPOINTING PARTY | DETAILS |
|---|---|
| CO. NAME AND APPR | |
| CO. WEBSITE | |
| CO. ADDRESS | |
| KEY CONTACT PERSON (KCP) ROLE | |
| KCP DIRECTORY MEMBERSHIP ID | |
| KCP ROLE MAILBOX (APPOINTMENT CONTACT VIEW) |
2.4 Proposed project team#
| RESOURCE | COUNT | DEPLOYMENT | RESOURCE AVAILABILITY |
|---|---|---|---|
| BIM MANAGER | |||
| BIM COORDINATOR | |||
| BIM SPECIALIST | |||
| BIM ENGINEER | |||
| BIM MODELER | |||
Map each resource to its ISO 19650 function per BBM-STD-55-RESPONSIBILITIES-V0.2 and the role definitions in BBM-STD-00-GLOSSARY-V0.3 §2–3.
2.5 Project Scope#
SCOPE
SCOPE ANALYSIS
| ITEM | DESCRIPTION |
|---|---|
| Project Justification (business need that this project is undertaken to address) | |
| Project Deliverables (summarized list of required deliverables) | |
| Out-of-scope Items (any items that will remain out of scope) | |
| Project Objectives (quantifiable criteria considered for success) | |
| Cost Objectives | |
| Schedule Objectives | |
| Acceptance Criteria | |
| Assumptions (list of assumptions governing the conduct on the project): |
2.6 Project schedule, phasing & milestones#
| MILESTONES | START DATE | END DATE | STAKE HOLDERS | STATUS |
|---|---|---|---|---|
| 0-SD (STRATEGIC DEFINITION) | ||||
| 1-PB (PREPARATION AND BRIEFING) | ||||
| 2-CD (CONCEPT DESIGN) | ||||
| 3-SC (SPATIAL COORDINATION) | ||||
| 4-TD (TECHNICAL DESIGN) | ||||
| 5-MC (MANUFACTURING AND CONSTRUCTION) | ||||
| 6-H (HANDOVER) | ||||
| 7-U (USE) |
Refer to the approved purpose-led LOIN/exchange register in 6.5; stage labels and numeric LOD do not replace it
MILESTONES FOLLOWS RIBA PLAN OF WORK 2020
2.7 Key Project Contact#
Personal contact details are held only in the restricted Directory (BBM-STD-03-DIRECTORY-V0.3); this table carries the appointment contact view.
| ROLE | DIRECTORY MEMBERSHIP ID | ROLE MAILBOX (APPOINTMENT CONTACT VIEW) |
|---|---|---|
| PM | ||
| BIM MANAGER | ||
| LEAD ARC | ||
| LEAD INT | ||
| LEAD MEC | ||
| LEAD ELE | ||
| LEAD PLU | ||
| LEAD STR | ||
| LEAD LSC | ||
| LEAD CONTRACT | ||
| LEAD SUSTAINABILITY RATING (Estidama Pearl – Abu Dhabi / Al Sa'fat – Dubai) | ||
2.8 TASK TEAMS#
Record appointment → LAP → task teams and their producers/checkers; link the responsibility matrices in 6.2 and task-team evidence in 6.1.1. The confirmation diagram in 6.1.1 identifies the decision roles.
3 BIM goals/uses & project objectives#
3.1 Main objectives#
Specific Appointing Party Requirements
| QUESTION | ANSWER |
|---|---|
| BIM INTENT | |
| BIM OBJECTIVES | |
| PROJECT OBJECTIVE | |
| CDE OBJECTIVE | |
The primary reasons we use BIM are:
Eliminating waste
Increasing productivity
Improving design quality
Reacting to industry demand
Satisfying owner/appointing party requirements
Gaining a competitive advantage
Improving corporate innovation
Candidate objectives for the design and construction phases (to be measured per BBM-STD-83-METRICS_AND_BENEFITS-V0.2; each stays an objective until a baseline and measurement demonstrate the result):
Standardize the production process and maintain uniformity across projects and regions
Create a standardized data structure that allows data to be reused, and eliminates redundant and conflicting information
Decrease waste by utilizing a virtual building process to simulate design & construction activities
Reduce CAPEX (capital expenditure) costs with better informed decision making and greater coordination & collaboration amongst project teams
Allow the Design and Construction models to be used for building operations without adding significant costs or time to the Design & Construction process
Visual communication of site conditions for planning and health/safety/risk assessment
More accurate project phasing and timelines
More accurate budgeting and cost estimating, ensuring the project is constructed with the least variations / clashes as possible
Coordinated models with all required interface rules run and blocking issues closed (8.12), aiming to reduce RFIs requesting data on object location, with an emphasis on clash avoidance
Utilize 3D models for reporting, review and decision making
Ensure that there is coordinated, quality Design documentation to estimate the build cost
Ensure that the constructability and methodology of the design have been assessed before documents are issued for construction
3.2 BIM Uses#
3.2.1 USE → DECISION → EXCHANGE WORKSHEET#
Decision (BIM Manager, 2026-10-14): Adopt Glossary sections 5–8 procedures/gates as a purpose-led menu; start project selection with Design Authoring, Design Review, 3D Coordination and required Asset Management; add 4D/5D/carbon/VR only for an evidenced decision, resources and receiving criteria. Basis: BIM uses serve outcomes rather than software availability or universal deliverables P01, S07.
Decision (BIM Manager, 2026-10-14): Adopt purpose-led worksheets recording purpose, timing, producers/receivers, objects, geometry, alphanumeric information, documentation and measurable checks; keep synthetic examples as templates and populate actual requirements before exchange. Basis: ISO 7817-1:2024 distinguishes information need from bare LOD/stage labels S07.
CAPEX, rework and delivery benefits are objectives until baseline, measurement and full costs demonstrate results.
| Use ID / selected use | Objective / upstream requirement | Producer / decision recipient | Process and inputs | Exchange ID / time / output | LOIN / acceptance / evidence |
|---|---|---|---|---|---|
| SYN-USE-01 / 3D Coordination | PIR-P01 / EIR-E01: resolve a service/structure interface before technical issue | MEP + structural task teams / competent designers and LAP reviewer | Approved Shared model revisions → federation → pair/clearance checks → disposition → retest | EX-01 at agreed coordination gate; IFC reference set, BCF issues and review report | LOIN-01: service extents/access, stable IDs/system, opening decision docs; every blocking issue resolved/retested or permissible residual decision recorded |
| SYN-USE-02 / Spatial brief review | PIR-P02 / EIR-E02: confirm room programme | Architecture room-data owner / appointing-party brief reviewer | Approved brief + rooms → schedule reconciliation → decision report | EX-02 at spatial coordination; model, CSV and PDF report | LOIN-02: space bounds, unique room IDs/use/area/unit, brief; every required space reconciled and departures decided |
| SYN-USE-03 / Asset handover | AIR-A01 / EIR-E03: plan safe maintenance | Asset-data task teams / FM and safety recipient | Approved installed-equipment/submittal data + O&M/HSI → validated profile → import/update test | EX-03 at handover; asset dataset and linked model/docs | LOIN-03: equipment/access location, mandatory asset fields, O&M/residual risks; receiver ingestion and changed-asset test pass |
| SYN-USE-04 / BIM-based building permit submission (Dubai) | Authority requirement: DM circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026) / 9-1-2 (13 Oct 2023); applicability test in 3.2.2 | ARC + STR task teams, LAP authorises / Dubai Municipality permit reviewer via the BIM portal | Approved Published ARC/STR models → export with the current Dubai BIM Standard setup → drawings extracted from the same model → portal submission | EX-P06 (7.4) at permit application, and final BIM before the completion certificate where 9-1-3 requires; zipped openBIM IFC plus drawings | Current Model Attribute Matrix fields populated; project IDS pass; authority decision recorded (BBM-STD-57 §4 status) |
| [ID / yes-no selection] | [OIR/PIR/AIR and appointment EIR IDs; decision] | [producer and recipient roles] | [input container revisions; steps] | [container IDs, agreed actual date, format/profile] | [geometry/data/docs, rule IDs, reports, acceptance owner] |
Decision (BIM Manager, 2026-10-14): Adopt Glossary sections 5–8 procedures/gates as a purpose-led menu; start project selection with Design Authoring, Design Review, 3D Coordination and required Asset Management; add 4D/5D/carbon/VR only for an evidenced decision, resources and receiving criteria. Basis: BIM uses serve outcomes rather than software availability or universal deliverables P01, S07.
Decision (BIM Manager, 2026-10-14): Adopt purpose-led worksheets recording purpose, timing, producers/receivers, objects, geometry, alphanumeric information, documentation and measurable checks; keep synthetic examples as templates and populate actual requirements before exchange. Basis: ISO 7817-1:2024 distinguishes information need from bare LOD/stage labels S07.
Rows remain synthetic and unassigned. Populate recipient/date/rules; selected carbon assessment needs boundary/stages, units, EPD source/version, assumptions and independent reconciliation under applicable RICS WLCA/ISO 22057.
| BIM USE | PRIORITY | PLAN | DESIGN | CONSTRUCT | OPERATE |
|---|---|---|---|---|---|
| Existing Conditions Modelling | |||||
| Programming | |||||
| Site Analysis | |||||
| Design Authoring | |||||
| Design Reviews | |||||
| 3D Coordination | |||||
| Structural Analysis | |||||
| Lighting Analysis | |||||
| Energy Analysis | |||||
| Engineering Analysis | |||||
| Sustainability Evaluation | |||||
| VR Design Validation | |||||
| Code Validation | |||||
| Site Utilization Planning | |||||
| Construction System Design | |||||
| Digital Fabrication | |||||
| 4D Phase Planning | |||||
| 5D Cost Estimation | |||||
| Building Maintenance Scheduling | |||||
| Building System Analysis | |||||
| Asset Management | |||||
| Space Management / Tracking | |||||
| Disaster Planning | |||||
| Record Modelling | |||||
| Building Permit Submission (Dubai, DM 9-1-2 / 9-1-3) |
3.2.2 AUTHORITY, CODE AND RATING USES (UAE)#
Requirement detail, sources and source-check dates are owned by BBM-STD-85-UAE_AUTHORITY_SUBMISSIONS-V0.1 and BBM-STD-57-CODES_AND_SUBMISSIONS-V0.2; the BEP records which apply and how the model serves them.
| Use | Applicability test (record the result per project) | Model contribution / evidence |
|---|---|---|
| BIM-based building permit submission (Dubai) | DM circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026): new buildings above G+12 or of 15,000 m² or more submit ARC and STR BIM with the permit; BIM-licensed alterations (adding/removing floors, adding 1,500 m² or more, full redesign, change of main use, relocation on the plot) submit BIM with the application; other alterations submit a final BIM model before the completion certificate. DM circular 9-1-2 (13 Oct 2023, from 1 Jan 2024): over 20 floors (ARC) / 40 floors (STR), over 20,000 m² (ARC) / 30,000 m² (STR), specialised buildings (e.g. hospitals, universities) and government projects except utility projects. | openBIM submission per the current Dubai BIM Standard (buildindubai.gov.ae/bim) via EX-P06; drawings extracted from the submitted model; submitted together with the drawings |
| Code Validation | Instruments recorded in 1.12: Dubai Building Code (Decree 45/2021 plus all DM amending resolutions in force at permit submission, including Administrative Resolution No. 225 of 2024); UAE Fire & Life Safety Code of Practice, September 2018 edition plus the emirate authority's amendments current at project start; Abu Dhabi: the ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04) | Each model check names the instrument/clause it targets (BBM-STD-51 §3 register ID) and the rule-set version; rule-based checks are advisory evidence only, competent code review and authority approval remain separate |
| Sustainability Evaluation (green-rating evidence) | Abu Dhabi Estidama Pearl: private projects min 1 Pearl, government-funded min 2 Pearl (DMT, 8 Jan 2025); Dubai Al Sa'fat 2nd edition (Jan 2023): Silver Sa'fa mandatory for all new buildings | Rating evidence (areas, quantities, materials) taken from model schedules with the rating system and version recorded; the sustainability-rating lead (2.7) signs off |
| Abu Dhabi BIM | DMT/ADM BIM Code of Practice (Oct 2020) where the appointment or authority requires BIM; infrastructure only: ADM Documentation Guidelines for Infrastructure v1.0 (Oct 2020) and Infrastructure BIM Object Catalogue v2.0 (May 2021); no general Abu Dhabi building-permit BIM mandate found | Profile row in 7.4 created only when required |
| Asset-life obligation (Dubai) | Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (issued 27 Feb 2026): Quality & Safety Certificate needed after 20 years from completion | Handover records (7.3) keep the information an inspecting engineering firm needs; not a design-permit rule |
3.3 BIM Roles#
| BIM USE | RESPONSIBLE PARTY | KCP |
|---|---|---|
| Existing Conditions Modelling | ||
| Programming | ||
| Site Analysis | ||
| Design Authoring | ||
| Design Reviews | ||
| 3D Coordination | ||
| Structural Analysis | ||
| Lighting Analysis | ||
| Energy Analysis | ||
| Engineering Analysis | ||
| Sustainability Evaluation | ||
| VR Design Validation | ||
| Code Validation | ||
| Site Utilization Planning | ||
| Construction System Design | ||
| Digital Fabrication | ||
| 4D Phase Planning | ||
| 5D Cost Estimation | ||
| Building Maintenance Scheduling | ||
| Building System Analysis | ||
| Asset Management | ||
| Space Management / Tracking | ||
| Disaster Planning | ||
| Record Modelling | ||
| Building Permit Submission (Dubai) |
3.4 TRAINING#
3.4.1 TRAINING OBJECTIVE#
The primary objective of the project's training program is to ensure that all project team members, including those from appointed parties and subcontractors, possess the necessary skills and knowledge to comply with the project's specific BIM standards, workflows, and technological requirements as defined in this BEP. The focus is on project-specific competency, not just general software skills.
3.4.2 COMPETENCY ASSESSMENT#
Before commencing work, all organizations involved in the project shall undergo a BIM Capability and Awareness Assessment. This assessment is managed by the LAP information management function; capability decisions follow 6.1.1 and Annex W2 A4 with an independent assessor. It evaluates competency in three key areas:
Software proficiency: assessed task performance with the approved exact project tool/build baseline (9.2.1), not a training example version.
Process & Standards Knowledge: Understanding of the workflows and standards defined within this BEP, including the CDE protocol, naming conventions, and QC checks.
Client Requirements Awareness: Familiarity with the [APPOINTING PARTY] Exchange Information Requirements (EIR).
The results of this assessment will identify any knowledge gaps and determine the required level of training for each team.
3.4.3 TIERED TRAINING PROGRAM#
Based on the competency assessment, a tiered training program will be implemented:
Tier 1: Project BIM Onboarding (Mandatory for All)
This session is not software training. Instead, it is a comprehensive review of this BEP, focusing on:
The project's BIM goals and objectives.
The CDE folder structure, workflows, and permissions.
Communication and collaboration protocols.
Key standards, such as file naming and model submission procedures.
Tier 2: Role-Specific Workflow Training (As Required)
These are targeted workshops for specific roles. Examples include:
For Model Authors: Detailed training on project templates, worksets, and the approved project dictionary (8.6 / BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2).
For Project Managers: Training on using ACC for design reviews, RFI management, and progress monitoring.
Tier 3: Foundational Software Training (As Needed)
If the assessment identifies a fundamental gap in software skills, the relevant party will be notified. This training addresses specific software features and functionality.
3.4.4 RESPONSIBILITY#
LDC ([APPOINTED PARTY]): The LDC is responsible for developing and delivering the Tier 1 and Tier 2 training, as these are specific to the project's established workflows.
APPOINTED PARTIES: Each individual company is responsible for ensuring their staff possess the fundamental software skills required for their role. The cost and arrangement for any Tier 3 software training are the responsibility of the individual company.
4 BIM Implementation Plan and Model Delivery Strategy#
| BIM USE | PRIMARY GOAL | KEY ACTIVITIES / PROCESS | PRIMARY SOFTWARE / PLATFORM | RESPONSIBLE PARTY |
|---|---|---|---|---|
| Design Authoring | To create accurate, data-rich, and coordinated 3D models for all disciplines that serve as the single source of truth for the design. | • All modeling begins from the approved project templates. • Models are hosted and developed collaboratively on the CDE. • Authors must model to the specified LOIN for each milestone. • Daily synchronization to the central model is mandatory. | Autodesk Revit, Civil 3D, Autodesk Construction Cloud (ACC) | |
| 3D Coordination | To proactively identify, track, and resolve geometric clashes between all disciplines before they can impact construction. | • A formal, weekly coordination cycle is followed (Submit > Federate > Clash Test > Report > Resolve). • The BIM Manager runs tests based on the agreed Clash Test Schedule. • Issues are assigned, tracked, and managed via the CDE. | Autodesk Navisworks Manage, ACC (for issue tracking) | |
| Design Review | To facilitate clear communication and create a formal, auditable record of all feedback from stakeholders during the design process. | • Formal design reviews are initiated using the "Reviews" workflow in the CDE. • Stakeholders add comments and markups directly to models/drawings. • All feedback is tracked, assigned, and managed to resolution within the CDE. | Autodesk Construction Cloud (ACC) | |
| 4D Phase Planning | To visualize the construction schedule, optimize site logistics, improve safety planning, and communicate the build sequence effectively. | • The federated 3D model is linked to the approved P6/MSP construction schedule. • The 4D simulation is updated monthly to reflect progress. • The simulation is used as a key tool in weekly construction planning meetings. | Autodesk Navisworks Manage, Synchro PRO | |
| 5D Cost Estimation | To generate more accurate and timely cost estimates by linking quantities directly to the information-rich models. | • The Cost Consultant extracts quantities from the published models at each key milestone. • Models are structured to align with the cost plan breakdown. • Any discrepancies in quantities are formally raised via RFI. | CostX, Autodesk Revit | |
| Asset Management | To progressively capture and verify all required operational data for a seamless handover to the client's Facility Management team. | • All assets are populated with data as per the approved project dictionary (8.6 / BBM-STD-72). • A formal workflow for modifying data based on approved submittals is followed. • Data is delivered in the COBie format at scheduled "data drops" for client review. | Autodesk Revit, MS Excel (for COBie) | |
| As-Built Modelling | To create a final, accurate record model that reflects the true constructed condition of the asset. | • The contractor maintains a live record of on-site changes via red-line markups on the CDE. • At project completion, the design models are updated based on the verified red-lines. • The final As-Built model is submitted as a key handover deliverable. | Autodesk Construction Cloud (ACC), Autodesk Revit | |
This candidate implementation schedule is selected and populated against the confirmed EIR and 3.2.1 use/exchange worksheet. The following schedule connects each activity to its primary goal, the process for achieving it, the tools that will be used, and the parties responsible for its execution.
5 BIM Collaboration#
5.1 COLLABORATION PROCESSES#
5.1.1 OVERVIEW PROCESS MAP#
5.1.1.1 INHOUSE COLLABORATION
[APPOINTED PARTY] team follows BBM-STD-01-MANUAL-V0.5 §8.1 (protocols) and the office standard set it indexes for internal standards, methods and quality.
5.1.1.2 OUTBOUND COLLABORATION
[APPOINTED PARTY] team follows BBM-STD-01-MANUAL-V0.5 §8.1.2 (communication protocol) and the appointment Information Protocol (BBM-STD-56-INFORMATION_PROTOCOL-V0.2) for exchanges with other parties.
5.1.2 MODEL AUTHORING#
All modeling must begin from the approved project templates. Authors are responsible for adhering to all standards defined in Section 8 (Naming Conventions, etc.) and ensuring their models comply with the Level of Information Need (LOIN) requirements for the current project stage. Before sharing, each author must perform an internal quality check: zero warnings from the blocking warning list WRN-01..WRN-nn (office check set, version/hash recorded per 8.10), and all other warnings logged with count and disposition.
5.1.3 DESIGN REVIEW#
Formal design reviews will be conducted. Review sets will be issued, and stakeholders (e.g., Client, PMC) will add comments, markups, and issues directly to the models and drawings. This creates a formal, auditable record of all review feedback, which is then assigned to the responsible discipline for action.
5.1.4 COORDINATION – 3D#
A formal coordination cycle will be run weekly by the BIM Manager.
Submission: Models are published to "SHARED" by Friday afternoon.
Analysis: Clash detection tests are run as per the Clash Test Schedule.
Reporting: A formal report and assigned issues are distributed by Monday.
Resolution: A mandatory coordination meeting is held every Tuesday to review and drive the resolution of critical issues.
5.1.5 CONSTRUCTION SEQUENCE – 4D#
The federated 3D model will be linked to the approved construction schedule (Primavera P6 / MS Project). The 4D simulation will be updated monthly to reflect progress and will be used in planning meetings to validate site logistics, identify potential safety hazards, and communicate the construction sequence to all stakeholders.
5.1.6 QUANTITY EXTRACTION – BOQ#
The Cost Consultant will extract quantities from the latest published models at agreed-upon project milestones. Model authors are responsible for ensuring elements are modeled with the necessary detail and data to support accurate quantity takeoff. Any discrepancies will be formally raised via an RFI.
5.1.7 FIELD MANAGEMENT – RFIS & ISSUES#
Formal RFIs/site issues are created, tracked and responded to in the approved authoritative workflow, and distributed only to authorised relevant recipients; retain any formal email notice and its CDE record. RFIs can be linked directly to locations in the model or drawings for maximum clarity. An official log for all RFIs shall be maintained.
5.1.8 FIELD CHANGES CAPTURING – AS-BUILT#
The contractor is responsible for maintaining a live record of all on-site deviations from the construction issue documents (SU-ISSUE, authorised use: construction). At project completion, this will be used to create an up to date As-Built model
5.2 COMMON DATA ENVIRONMENT – CDE#
The CDE combines agreed workflow and technical solutions for controlled information containers, decisions, history and revision. Access is sensitivity- and role-based; commercial party membership alone does not grant access to every project record. Configure the authoritative record and project state mapping in 5.2.4.
The CDE should contain:
Graphical Data (models, drawings, PDF’s, IFC, photographs, renders, videos, …etc.)
Non-Graphical Data (Schedules, data-bases, COBie, …etc.)
Documents (Contracts, minutes, correspondence, request for information (RFI’s), brief, Specifications, reports,
BOQ, Inspection Plans & Reports, Commissioning Certificates, Product data Sheets, user O&M Manuals, …etc.).
5.2.1 [APPOINTED PARTY] FOLDER STRUCTURE#
Folder mapping follows the approved BBM-STD-01-MANUAL-V0.5 §12.1 outline and 5.2.4 state alias register; folder discipline codes use the 3-letter codes of BBM-STD-93-CODE_DICTIONARY-V0.1. The project folder tree is defined once in Manual §12.1 (state → data type → discipline; NN-NAME folder names without dots); this BEP records only approved project deviations from it.
5.2.2 AUTODESK CONSTRUCTION CLOUD#
Decision (BIM Manager, 2026-10-14): Select Autodesk Construction Cloud as office default for agreed model/document workflows; qualify actual tenant/modules/permissions/formal transactions; appointment-mandated alternatives/bridges require one authoritative mapping. Basis: Retains office ACC method without assuming configured capability A03, G-C.
Qualify cloud/file worksharing, viewer and formal issue services separately against the actual EIR.
5.2.3 PUBLICATION AND DOCUMENT ISSUE#
2D DWG or PDF drawings and sheets shall be stored in the Published Area of the folder structure once formally checked, approved and authorized in accordance with corporate quality procedures.
Revision/Issue control shall follow the Document Control systems established for the project.
A record of all issued deliverables shall be maintained in softcopy and hardcopy were
appropriate.
Information within a BIM is inter-dependent and changes in one view may affect other views.
Native/editable models and their associated information can be controlled WIP, Shared or Published containers. State is determined by identified versions, suitability, checks, sharing approval, delivery authorisation and recipient acceptance under the appointment, not by editability. PDF and native/open exports follow the same formal governance in 5.2.4.
5.2.4 CONTROLLED CONTAINER AND TRANSITION RECORD#
Use ISO 19650-2:2018, ISO 19650-4:2022 and IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance C, edition 1 (2020, archived edition). Logical states WIP, Shared, Published and Archive map to the actual project platform in the annex; the office Published state folder is 03-PUBLISHED (Manual §12.1), not an additional state. CDE operation and platform sync/Publish are separate from formal issue decisions. Restricted staging candidates remain in WIP.
| Transition | Authority / minimum checks | Retained record |
|---|---|---|
| WIP → Shared for specified review | Producer self-check; task-team review/approval to share; identity/requirements/security checks | Container ID, revision, CDE version/checksum, suitability/permitted use, checker/date and rule reports |
| Shared → authorised submission | LAP checks agreed container set, resolved dependencies/comments and exchange rules | Exact manifest, authorisation/date, EIR/BEP/rule revisions and transmittal ID |
| Submission → receiving decision | Appointment-defined recipient checks the intended use and tests 10.3 | Accept / conditional defined use / reject; reasons, owner/due date and evidence IDs |
| Reject → correction and resubmission | Producer corrects in WIP, records changed IDs, repeats affected checks | Rejection preserved; new controlled revision with retest and new decision |
| Supersede / Archive | Approved replacement manifest and retention/access policy | Predecessor/successor identities, original approvals and immutable history |
Decision (BIM Manager, 2026-10-14): Use A = accepted for stated purpose without required changes, B = accepted for stated purpose with listed nonblocking comments, owners and dates, C = rejected/revise and resubmit with affected use held; record scope, actual acceptor, authority, evidence and permitted use; B cannot cover mandatory failure. Basis: Local gate letters differ from RACI and suitability and cannot waive binding criteria S04.
Gate outcomes are the letters A/B/C everywhere in the standard set, with meanings per Glossary §1.5; the code lists (gate outcomes, CDE states, suitability) are held only in BBM-STD-93-CODE_DICTIONARY-V0.1 §3–§5. Formal delivery is the LAP-authorised transition of the container set to Published with a transmittal (ISO 19650-2 5.7); acceptance is the separate A/B/C recipient decision. A platform Published label before recipient decision must carry pending acceptance / limited review use. A/B/C, RACI, distribution and suitability have separate legends.
| Container identity | Revision / immutable version | State / suitability / use | Source and rule revisions | Sharing / LAP authorisation | Recipient decision / evidence | Change / supersedence / retention |
|---|---|---|---|---|---|---|
| [ID + format] | [revision, CDE ID/hash] | [logical state, project code, intended purpose] | [EIR, source, preset/IDS/rules] | [roles, dates, decision IDs] | [role/date, test evidence, comment scope] | [new IDs, predecessor links, policy] |
Do not overwrite or rename historic issues or infer construction reliance from an IFC extension, browser folder, date folder or completed upload. Notify recipients of changed/superseded containers through a new controlled transmittal.
5.3 COMMUNICATION FLOW#
Communication flow follows the appointment EIR and the communication matrix of the Information Protocol in BBM-STD-56-INFORMATION_PROTOCOL-V0.2, with the office communication protocol in BBM-STD-01-MANUAL-V0.5 §8.1.2; formal records follow 5.1.7 and 5.2.4.
5.4 CLIENT E-VIEWING/E-REVIEWING#
The CDE/access owner provisions only required roles/modules and tests receiving access in the approved implementation; confirm any ACC/BIM 360/Aconex bridge with the recipient and preserve the authoritative record.
5.5 MEETINGS & WORKSHOPS#
Meetings are to be conducted periodically and whenever needed, below are some mandatory meetings and not limited to:
| Meeting Type | Project Stage | Frequency | Participants | Location |
|---|---|---|---|---|
| • BIM KICK-OFF MEETING | 0 STRATEGIC DEFINITION / 1 PREPARATION AND BRIEFING | ONCE | PROJECT TEAM | ONLINE |
| • BIM STANDARDS AND GUIDELINES REVIEW BIM ROLES AND RESPONSIBILITIES DISCUSSION | 1 PREPARATION AND BRIEFING | ONCE | PROJECT TEAM | ONLINE |
| • CONCEPT DESIGN COORDINATION MEETING | 2 CONCEPT DESIGN | WEEKLY | LDC | ONLINE |
| • SPATIAL COORDINATION BIM COORDINATION MEETING | 3 SPATIAL COORDINATION | WEEKLY | LDC | ONLINE |
| • ARCHITECTURAL, STRUCTURAL, AND MEP MODEL INTEGRATION MEETING | 3 SPATIAL COORDINATION | WEEKLY | LDC | ONLINE |
| • BIM-BASED DESIGN REVIEW AND FEEDBACK MEETING | 3 SPATIAL COORDINATION | WEEKLY | CLIENT-LDC | ONLINE |
| • BIM CLASH DETECTION AND RESOLUTION MEETING (STAGE 3) | 3 SPATIAL COORDINATION | WEEKLY | CLIENT-LDC | ONLINE |
| • BIM MODEL REFINEMENT AND VALIDATION REVIEW | 4 TECHNICAL DESIGN | ONCE | CLIENT-LDC | ONLINE |
| • BIM CLASH DETECTION AND RESOLUTION MEETING (STAGE 4) | 4 TECHNICAL DESIGN | WEEKLY | CLIENT-LDC | ONLINE |
| • BIM-BASED QUANTITY TAKEOFF AND COST ESTIMATION MEETING | 4 TECHNICAL DESIGN | WEEKLY | CLIENT-LDC | ONLINE |
| • BIM MODEL HANDOVER TO CONTRACTOR MEETING / BIM-BASED TENDER DOCUMENT REVIEW | 4 TECHNICAL DESIGN (tender) | ONCE | CLIENT-LDC-CONTRACTOR | ONLINE |
| • BIM EXECUTION PLAN (BEP) REVIEW | ANY STAGE: each exchange milestone and material change (1.1) | AT EACH TRIGGER | LAP, TASK-TEAM LEADS | ONLINE |
| • BIM MODEL COORDINATION WITH SUBCONTRACTORS AND SUPPLIERS | 5 MANUFACTURING AND CONSTRUCTION | WEEKLY | CLIENT-LDC-CONTRACTOR | ONLINE |
Meetings Agenda adheres to client’s EIR meeting methodology and subject to change as per project progress and client needs. Stages follow RIBA Plan of Work 2020 (2.6); legacy labels map as pre-concept → 1, concept/study → 2, schematic → 3, detail design → 4.
6 Data planning & documentation#
6.1 CONFIRMATION OF BEP, SUPPLY CHAIN CAPABILITY & PERFORMANCE IMPROVEMENT#
6.1.1 CONFIRMATION, CAPACITY AND MOBILISATION GATES#
Follow ISO 19650-2:2018 and IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance E, edition 2 (2021, archived edition). Confirmation follows agreement of the plan and commitments; mobilisation demonstrates readiness of the people, methods and technology before the affected production/exchange. These are different decisions. Attendance, credentials, a plugin installation or a linked test form alone does not demonstrate practical ability.
Proposed arrangements become a confirmed delivery-team plan through explicit commitments; production readiness additionally needs tested mobilisation evidence.
| Capability / capacity record | Task and requirement | People/time and tools/access | Assessed evidence / gap | Action / owner / date | Reassessment and release decision |
|---|---|---|---|---|---|
| [team / appointment ID] | [actual production/check/receiving tasks, EIR IDs] | [available people, hours/calendar, full builds, tested permissions] | [practical artifact/result; missing skill/capacity/interoperability] | [training/resource/tool action, dependency, due date] | [test result, assessor, authorised scope/date] |
Check capability (can perform the task) separately from capacity (available people/time to meet the plan). Reassess at team/scope/build/platform change or sustained failed exchange. A team with good qualifications but no available production/review time is not ready.
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.
Actual tests are NOT EXECUTED. Include rooms, maintainable equipment, known access obstruction and deliberately invalid properties with saved expected outcomes.
| Test ID | Action / accountable function | Expected result | Dependencies / due gate | Actual evidence / disposition |
|---|---|---|---|---|
| MOB-01 | IM + IT: permitted/denied upload/read/write/download | Authorised role works; unauthorised role denied; event retained | Sensitivity and role register; before team access release | NOT EXECUTED; log role, CDE configuration/date, access result and remediation |
| MOB-02 | Task-team lead: native open/edit, borrow, sync/relinquish, colleague handoff | Two authorised users can complete agreed handoff without unresolved ownership/lost data | Same full authoring build and central/cloud setup; before authoring release | NOT EXECUTED; native version and practice-test record |
| MOB-03 | BIM Coordinator: export and coordinate/property validation | Prescribed IFC schema/profile; known IDs/properties/units and approved transform preserved | Survey/control owner + dictionary + preset; before first exchange | NOT EXECUTED; source/export hashes, header, value/count/point comparison |
| MOB-04 | Receiving reviewer: actual import/reference/data/document use | Intended workflow works, known mandatory values/docs intact, deliberate faults detected | MOB-03 plus actual receiver build/profile; before affected delivery | NOT EXECUTED; expected vs actual and recipient result |
| MOB-05 | Coordinator + designers: BCF issue and retest closure | Issue ID/element/viewpoint/owner/due date exchanged; revised exact model retested | Approved clash/access rule and BCF route; before coordination use | NOT EXECUTED; returned issue and review evidence |
| MOB-06 | IT + data owner: recovery/rollback in isolated test | Backup restored to known revision; required identity/data/access checks pass | Tested retention/backup route; before production release | NOT EXECUTED; recovery evidence and release decision |
| MOB-07 | Operational recipient: asset import and update | New/changed/retired asset keys, units, relationships and document access work | AIR/profile/source docs; before handover acceptance | NOT EXECUTED; target-system ingestion/change record |
For a failure: record test ID, expected/actual, failed container/build/configuration, consequence, action owner/date and blocked scope. Correct in an isolated version, repeat affected tests, and retain both results. LAP authorises mobilisation for the defined scope only after blocking actions close; receiver acceptance is separately recorded. No timeout, contract award or sample row counts as approval.
| MOB action / test | Input versions and tool builds | Expected / observed / pass-fail-blocked | Failure cause and correction | Retest report / reviewer | LAP readiness / scope | Recipient exchange decision |
|---|---|---|---|---|---|---|
| [ID] | [native/export/configuration hashes; 9.2.1 IDs] | [measured results, actual date] | [cause, action, owner/due date] | [new evidence, role/date] | [release or defer, decision ID/date] | [accept/conditional/reject, intended use and evidence] |
Minimum confirmation pack: actual EIR response, selected-use worksheet, named appointment/functions, detailed production matrix, baseline TIDPs/MIDP, naming/property/LOIN and tool/profile annexes, risk/security/safety records and approved deviations. Mobilisation pack additionally carries actual MOB records, remaining-action scope and recovery/receiving tests. The current template contains neither real confirmation signatures nor actual MOB passes.
Confirmation of the BEP requires explicit LAP confirmation of the agreed EIR response, task-team commitments, controlled annexes and delivery plans, with appointing-party review/acceptance as required by the appointment. Contract award alone does not confirm it; mobilisation release additionally requires 6.1.1 evidence.
It is understood that the BEP is a "living document" and will be reviewed and updated at key project milestones or under the following circumstances:
The appointment of a new major supply chain partner.
A significant change in project scope, schedule, or requirements.
The introduction of new technology that impacts the agreed workflows.
Proposed revisions are managed by the LAP information management function (the LAP owns the BEP and the delegated information manager maintains it) through the 1.1 change record, reviewed by key stakeholders, and formally re-issued with an updated revision and a summary of changes.
Supply Chain Capability Assessment To ensure the successful implementation of this BEP, all appointed parties and prospective supply chain partners must undergo a formal BIM Capability Assessment prior to commencing work.
Purpose: The assessment's purpose is to proactively identify and mitigate risks related to technology, resources, and personnel skills.
Process: The assessment is commissioned by the LAP information management function and conducted by an independent assessor per 6.1.1 and Annex W2 A4; it evaluates the supply chain partner's ability to comply with this BEP and the client's EIR.
Assessment Outcomes and Performance Improvement Plan (PIP) Based on the results of the capability assessment, one of two outcomes will occur:
Successful Assessment: If the partner demonstrates full capability, they will be approved to proceed, subject to completing the mandatory Project BIM Onboarding (as per Section 3.4).
Performance Improvement Plan (PIP) REQUIRED: If the assessment identifies significant deficiencies, a formal Performance Improvement Plan (PIP) will be initiated. The PIP is a documented action plan with a defined timeline, which will detail:
The specific skill, technology, or process gaps identified.
The required corrective actions (e.g., targeted software training, hardware upgrades, appointment of specific roles).
A clear timeline for the completion of these actions.
The criteria for successful completion and re-assessment.
The supply chain partner will not be permitted to commence information authoring on the project until the terms of the PIP have been met and verified by the independent assessor and recorded by the LAP information management function (Annex W2 A4).
TIDP Submission Following a successful assessment or the successful completion of a PIP, each supply chain partner will be required to develop and submit their Task Information Delivery Plan (TIDP) for incorporation into the project's Master Information Delivery Plan (MIDP).
6.2 RESPONSIBILITY MATRIX#
Decision (BIM Manager, 2026-10-14): Adopt BEP section 6.2 production fields and 6.2.1 RACI as templates with one A/activity; map appointments/people before activation and separate production/check/authorisation/acceptance. Basis: Matrices do not replace plans or transfer statutory duties G-F, G-A.
Tender allocation and detailed production responsibilities remain distinct. Private Directory records identify actual people.
| Requirement / use / container ID | Producing task team / author | Checker / sharing approver | LAP submission authoriser | Recipient / acceptance delegate | Required exchange / date | Dependencies / TIDP-MIDP row |
|---|---|---|---|---|---|---|
| [EIR / USE / ID] | [appointment/team/person] | [competent reviewer] | [role and recorded authority] | [actual recipient and delegation] | [EX ID, real planned date] | [input row IDs, TIDP/MIDP version] |
A scope/responsibility dispute is resolved against the appointment before committing the dependent schedule. The legacy party table below must be populated only after mapping AP/LAP/task-team functions; it does not independently authorise all parties to perform/accept every BIM activity.
| BIM TASK / DELIVERABLE | CLIENT | LDC | PMC | CC | CONTRACTOR |
|---|---|---|---|---|---|
| Develop & Maintain BEP | |||||
| Model Authoring (Arch, Str, MEP) | |||||
| Federated Model Management | |||||
| Clash Detection & Reporting | |||||
| Clash Resolution (Discipline-specific) | |||||
| 4D Phasing Simulation | |||||
| 5D Cost Estimation / QTO | |||||
| COBie Data Input & Validation | |||||
| CDE Administration | |||||
| As-Built Model Delivery |
Responsibilities are subject to change as per project progress/phases, client requirements, and resources availability
Task teams submit their proposed allocation to the LAP for one reconciled appointment-based activity matrix and a separate detailed production map; conflicting standalone RACI tables are not approved by default.
6.2.1 INFORMATION-MANAGEMENT ACTIVITY MATRIX#
Decision (BIM Manager, 2026-10-14): Adopt BEP section 6.2 production fields and 6.2.1 RACI as templates with one A/activity; map appointments/people before activation and separate production/check/authorisation/acceptance. Basis: Matrices do not replace plans or transfer statutory duties G-F, G-A.
R performs; A is accountable for this activity; C consulted; I informed. AP appointing party; LAP lead appointed party; TT task-team lead; IM assigned function; P producer; RR receiver/acceptor. One A does not transfer statutory/contract duties.
| Activity | AP | LAP | TT | IM | P | RR |
|---|---|---|---|---|---|---|
| ADVISE ON CDE | C | A | C | R | I | C |
| PROVIDE A CDE | A | R | C | C | I | C |
| SET UP THE CDE | C | A | C | R | I | C |
| MAINTAIN THE CDE | C | A | C | R | I | C |
| DOWNLOAD/UPLOAD ALL PROJECT'S INFORMATION FROM/TO THE CDE | I | C | A | C | R | I |
| APPOINT CONSULTANTS, INCLUDING INFORMATION MANAGER | C | A | R | R | C | I |
| ENSURE THAT THE NECESSARY SOFTWARE AND HARDWARE ARE IN PLACE WITHIN THE ORGANIZATION TO SUPPORT EFFICIENT DELIVERY OF THE PROJECT | C | A | R | R | C | I |
| ASSESS ALL SUB-CONSULTANT ORGANIZATION ACCORDING TO THE BIM ASSESSMENT CRITERIA CONTAINED IN CAPABILITY ASSESSMENT | C | A | R | R | C | I |
| REPORT ANY EMERGING SKILL GAPS WITHIN THE TEAM | I | C | A | C | R | I |
| PROVIDE GUIDANCE TO ASSIST IN PROCURING THE RIGHT TYPE OF TRAINING FROM CREDIBLE INDUSTRY PROFESSIONAL. | C | A | R | R | C | I |
| CO-ORDINATE TRAINING FOR OWN ORGANIZATION | I | C | A | C | R | I |
| ESTABLISH BIM REQUIREMENTS FOR THE PROJECT | A | R | C | C | I | C |
| DEVELOP, IMPLEMENT AND UPDATE AS NECESSARY THE DELIVERY TEAM'S CONFIRMED BEP, WHICH ALL PROJECT TEAM MEMBERS NEED TO AGREE AND USE. | C | A | R | R | C | I |
| DEVELOP AND IMPLEMENT THE BIM IMPLEMENTATION PROGRAM | C | A | R | R | C | I |
| DEVELOP AND IMPLEMENT THE INFORMATION EXCHANGE PROTOCOL. | A | R | C | C | I | C |
| BIM GUIDANCE AND MONITORING OF THE PROJECT TEAM | C | A | R | R | C | I |
| RESPONSIBLE FOR ENSURING THAT CONSULTANT’S ORGANIZATIONS MEET THE REQUIREMENTS SET FOR THE EIR. | C | A | R | R | C | I |
| PROVIDE ANY EXISTING INFORMATION INCLUDING DATA AND EXISTING CONDITION MODEL | A | R | C | C | I | C |
| CREATE A SITE SET-UP MODEL WITH COORDINATED, MEASUREMENTS AND BEARINGS TO BE USED DISSEMINATED TO ALL DESIGN TEAM MEMBERS | I | C | A | C | R | I |
| PROVIDE AN INFORMATION MODEL ACCORDING TO THE LEVEL OF INFORMATION NEED, THE MIDP AND THE NON-GEOMETRIC REQUIREMENTS. | I | C | A | C | R | I |
| SHARE THE INFORMATION MODELS FOR COORDINATION | I | C | A | C | R | I |
| IMPLEMENT THE BEP WITHIN THE ORGANIZATION. | I | C | A | C | R | I |
| FULL COORDINATION OF THE DESIGN AND DESIGN TEAM | C | A | R | R | C | I |
| PROVIDE STRUCTURAL ANALYSIS MODEL (S) FOR EVALUATION BY THE PROJECT TEAM | I | C | A | C | R | I |
| CREATE CLASH DETECTION REPORT OF FEDERATED MODELS | C | A | R | R | C | I |
| INCORPORATE SUB CONTRACTORS’ MODELS | C | A | R | R | C | I |
| COORDINATE MODEL-DERIVED DRAWINGS AND APPROVED NON-MODEL DETAILS/DOCUMENTS | C | A | R | R | C | I |
| EXPORT AND PUBLISH FILES ACCORDING TO FILE DATA EXCHANGE SCHEDULE | C | A | R | R | C | I |
| VISUALIZATION | C | A | R | R | C | I |
| DRAWING PRODUCTION | I | C | A | C | R | I |
| 3D DESIGN REVIEW AND COORDINATION | C | A | R | R | C | I |
| SPECIFY DATA REQUIREMENTS INCLUDING PURPOSE OF INFORMATION REQUIRED AND THE TIMING OF ITS DELIVERY | A | R | C | C | I | C |
| DELEGATE ASPECT OF THE EIR DOWNWARDS TO THE NEXT TIER | C | A | R | R | C | I |
| CREATE ACQUIRE AND STORE REQUIRED INFORMATION | I | C | A | C | R | I |
| REVIEW AND APPROVE THE DATA DELIVERABLE PRIOR TO SUBMISSION | C | A | R | R | C | I |
| ADHERE TO THE QA/QC PROCEDURE CONTAINED WITHIN EIR | C | A | R | R | C | I |
| REPORT CHANGES TO BUDGET, COST, AND DESIGN. | C | A | R | R | C | I |
| REPORT ON GENERAL MODEL QUALITY IN TERMS OF GEOMETRY, MATERIALITY, AND METADATA | C | A | R | R | C | I |
| REPORT ON ADHERENCE TO THE PROJECT BEP WITH REGARDS TO MODEL LEVEL OF DEFINITION, MODEL COMPLETENESS, AND BIM STANDARDS COMPLIANCY | C | A | R | R | C | I |
| Authorise delivery-team submission | I | A/R | R | C | I | C |
| Accept received exchange for its intended use | A (or delegated RR) | C | I | C | I | R |
The last receiving row assigns accountability to AP; change it to RR only with recorded AP delegation and remove the AP A in that row. Separate the detailed container production map from this activity table.
6.3 MIDP#
Decision (BIM Manager, 2026-10-14): Maintain exact source TIDP ID/row/revision, exchange/EIR/container IDs, parties, dependencies, production dates, separate L1/L2/rework/L3/release/acceptance windows, forecast/actual evidence and ChangeID in MIDP; synchronise all affected TIDPs. Basis: O3 ownership and source-row lineage govern G-F.
Decision (BIM Manager, 2026-10-14): The task-team lead owns the TIDP commitment; the LAP owns the coordinated MIDP baseline; every approved delivery-row change must propagate by the same ChangeID before the affected new commitment takes effect. Basis: Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence G-F. Authority: TIDP section 2, ownership and change propagation.
Decision (BIM Manager, 2026-10-14): Reserve L1 discipline QC 2 working days, L2 cross-discipline review 2 working days, correction/retest contingency 2 working days, L3 technical committee 1 working day, authorisation/release 1 working day and appointing-party acceptance 3 working days per normal exchange package. Basis: A visible allowance protects checks and exchange decisions; these are office planning minima and must increase for complexity or binding recipient terms S04. Authority: MIDP section 2, sequential review allowances.
Decision (BIM Manager, 2026-10-14): Use unique stable ExchangeIDs allocated from the approved project exchange register; separate RIBA Stage 2 Concept Design and Stage 3 Spatial Coordination unless an appointment explicitly groups their outcomes. Basis: Duplicate #01 and numbering gaps cannot establish the intended historic mapping; distinct decisions and dates must remain traceable G-F. Authority: MIDP section 4, exchange identity and stage reconciliation.
The examples below use the O3 allowances and source-row lineage; no O3 file is edited by this BEP.
| MIDP row | Source TIDP row / revision | Exchange / requirement / container IDs | Producer / checker / recipient | Predecessors and required input dates | Planned production finish | LAP authorisation / receiver windows | Delivery milestone / actual date | Profile / status / change approval |
|---|---|---|---|---|---|---|---|---|
| SYN-M01 | SYN-T01 / planning R01 | EX-01 / EIR-E01 / CLI-OFF-P001-ZZ-ZZ-M3-A-0001 | Architecture / discipline reviewer / structure reviewer | Approved survey+brief available by T−20; SYN-T02 checked by T−9 before package L2 | T−15 | L1 T−14..T−13; package L2 T−8..T−7; rework T−6..T−5; L3 T−4; release T−3; acceptance T−2..T | Submission T−3 / recipient acceptance T; actual pending | IFC/RVT; planned synthetic example |
| [ID] | [team plan row/version] | [approved stable IDs] | [authorised roles] | [IDs, dates, criticality] | [actual date/calendar] | [owners/start/end] | [agreed date, actual submission/decision] | [exact profile, state, change ID] |
Field types: identifiers are stable linked keys; dates use an agreed calendar/timezone; status distinguishes planned, checked, submitted, accepted and rejected; profile links to 9.2.1/7.4; actual submission and receiving decision dates are separate. Reconcile all EIR outputs to a plan row, every input to its predecessor, and all review windows to available reviewers. Escalate infeasible or missing dependencies; revise impacted TIDPs and MIDP through 1.1 and notify teams/recipients. A source link alone earns no completeness credit.
The Master Information Delivery Plan (MIDP) is the primary plan used to manage the delivery of information during the project. The LAP compiles and owns the MIDP baseline from the task teams' committed TIDPs; see BBM-STD-MIDP-V0.3. It is part of the delivery team's confirmed BEP.
Information deliverables which may be listed in the MIDP include (but are not limited to):
Models
Drawings or renditions
Specifications
Equipment schedules
Room data sheets
Procurement packages
Reports
Schedules
Template: BBM-STD-MIDP-V0.3.
6.4 TIDP#
Each task-team manager compiles a Task Information Delivery Plan for actual planned information containers, then commits it to the LAP for MIDP coordination. Follow IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance F, edition 1 (2020, archived edition). Include models, drawings, specifications, schedules and documentation, not only graphical models. A role matrix, resource allocation or linked empty spreadsheet is not a completed TIDP.
| TIDP row / team | Container ID / title / type | EIR / use / LOIN ID | Producer / checker / recipient | Dependencies / source revisions | Duration / production start–finish | Review / authorisation / acceptance windows | Planned delivery date / milestone | Format / profile / security | State / revision / change |
|---|---|---|---|---|---|---|---|---|---|
| SYN-T01 / Architecture (synthetic planning example) | CLI-OFF-P001-ZZ-ZZ-M3-A-0001 / coordination model | EIR-E01 / USE-01 / LOIN-01 | Author / discipline reviewer / structural reviewer | Approved brief and survey by T−20 / input delivery IDs | 5 working days / T−19..T−15 | L1 T−14..T−13; package L2 T−8..T−7, rework T−6..T−5, L3 T−4, release T−3, acceptance T−2..T | T−3 submission / T recipient acceptance / EX-01 | RVT + approved IFC Reference View; restricted review | Planned; no actual release/test claimed |
| SYN-T02 / Architecture | CLI-OFF-P001-ZZ-ZZ-RP-A-0002 / room reconciliation report | EIR-E01 / USE-02 / LOIN-02 | Room-data owner / design reviewer / brief decision owner | SYN-T01 checked at T−13 plus approved room brief | 2 working days / T−12..T−11 | L1 T−10..T−9; same package L2/rework/L3/release/acceptance windows as SYN-T01 | T−3 submission / T recipient acceptance / EX-01 | PDF + CSV schema; review only | Planned synthetic relative dates |
| [row / task team] | [approved actual ID / title / type] | [requirement/use/LOIN] | [named authorised roles] | [dependency IDs, dates, versions] | [calendar/duration/start/finish] | [each decision window/owner] | [YYYY-MM-DD, exchange ID] | [exact profile, access] | [baseline revision, progress, decision ID] |
Decision (BIM Manager, 2026-10-14): Reserve L1 discipline QC 2 working days, L2 cross-discipline review 2 working days, correction/retest contingency 2 working days, L3 technical committee 1 working day, authorisation/release 1 working day and appointing-party acceptance 3 working days per normal exchange package. Basis: A visible allowance protects checks and exchange decisions; these are office planning minima and must increase for complexity or binding recipient terms S04. Authority: MIDP section 2, sequential review allowances.
Decision (BIM Manager, 2026-10-14): The task-team lead owns the TIDP commitment; the LAP owns the coordinated MIDP baseline; every approved delivery-row change must propagate by the same ChangeID before the affected new commitment takes effect. Basis: Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence G-F. Authority: TIDP section 2, ownership and change propagation.
In the synthetic rows T is recipient acceptance finish, and every offset is a working day on the agreed calendar. The model is produced T−19..T−15, L1 T−14..T−13; its report follows T−12..T−11 with L1 T−10..T−9. Package L2 T−8..T−7, correction/retest T−6..T−5, L3 T−4, release/submission T−3 and acceptance T−2..T. Actual dates, resources and input readiness must be confirmed; these are not a live schedule.
Field specification: row/container/requirement/dependency IDs are stable text keys; title/type/profile/security use controlled dictionaries; producer/checker/recipient are authorised roster references; duration includes unit and working calendar; start/finish/delivery are real dates with timezone where timed; review windows have decision owner and duration; status is planned/in-progress/checked/submitted/accepted/rejected with actual-date and evidence fields. Record baseline/version, change owner, reason and approval; preserve original planned and actual dates separately. No cell defaults to accepted merely because its date passes.
Check before baseline: unique container IDs; all required EIR outputs covered; no orphan dependency; feasible dates/resources; all review windows present; recipient and profile confirmed; no unresolved blocking assumption. After change/rejection, revise affected rows/dependencies and notify receiving teams through the controlled change record.
6.5 LEVEL OF INFORMATION NEED (LOIN)#
Use ISO 7817-1:2024. BSI has withdrawn BS EN 17412-1:2020 in favour of its ISO 7817-1 adoption; a different contractually adopted edition requires recorded review, not silent replacement. The complete worksheet contains purpose, timing, actors and objects plus geometry, alphanumeric information and documentation. Numeric LOD conventions or stage-only tables remain qualified shorthand.
| LOIN ID / EIR / exchange | Purpose / decision and timing | Producer / recipient / object scope | Geometry needed | Alphanumeric obligations | Documentation | Measurable acceptance |
|---|---|---|---|---|---|---|
| SYN-LOIN-01 / EIR-E01 / EX-01 | Coordinate opening/access before technical issue; date from TIDP | MEP+structure / competent designers; in-scope equipment/service interfaces | Approved location/extents/connectors/access envelope; agreed tolerance and units | Stable element/system/location IDs, classification table/code, required performance values | Approved opening/access decision, safety record and issue/retest report | Mandatory properties valid; approved pair rules run against exact revisions; blocking issues dispositioned/retested |
| SYN-LOIN-03 / EIR-E03 / EX-03 | Safe maintenance and asset ingestion at handover | Equipment producer / operator; maintainable assets in AIR | Verified installed location and access; provenance/uncertainty | Unique Asset_ID, approved manufacturer/model/serial, units, service/warranty fields as required | Approved O&M, commissioning and residual-risk records with accessible links | AIR required assets/values complete; recipient import/update/document tests pass |
| [ID] | [purpose, actual date/trigger] | [actors and required objects] | [dimensions, precision, representation, coordinate basis] | [property IDs/types/units/values, applicability] | [required document IDs/versions] | [rules, thresholds, evidence and recipient decision] |
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.
Synthetic LOIN rows remain examples. Freeze each actual exchange worksheet and record permitted exclusions, alternative documentation and authority; do not populate missing values with inventions.
This section defines the granularity of information required for model elements throughout the project lifecycle. The LOIN framework clarifies why information is needed and specifies the requirements for Geometry, Alphanumeric Information, and Documentation at each stage.
As per the Exchange Information Requirements (EIR), the Client (Appointing Party) is responsible for providing the initial Level of Information Need (LOIN) Matrix for the project. This matrix will serve as the primary reference and baseline for all information deliverables. The Lead Design Consultant (LDC) and the delivery team develops and delivers exactly the approved information need for its appointed scope. Clarify missing requirements with the appointing party; do not silently expand scope or substitute a stage-only matrix.
This ensures that teams produce exactly the right level of detail—no more, no less—preventing both wasted effort and information shortfalls.
The full LOIN Matrix will be developed as a key project appendix. The following is an illustrative example of its structure and content.
Example LOIN Matrix (legacy illustration only; use the SYN-LOIN worksheet above for real requirements):
| Discipline | Model Element | Purpose | Actor (producer → receiver) | Project Stage | Geometric Information Required | Alphanumeric Information Required | Documentation required by purpose |
|---|---|---|---|---|---|---|---|
| Structure | Structural Column | Concept option review | STR task team → LAP design reviewer | 2 Concept Design | Generic shape representing location and approximate size. | Grid Location, Material (e.g., Concrete) | Approved concept/design basis and review record |
| Coordination and technical issue | STR task team → ARC/MEP task teams | 4 Technical Design | Accurate dimensions, profile, and location. | Asset_ID (where a maintainable asset), Classification_Code, Concrete Strength, Reinforcement (schematic) | Approved technical specification, calculations/submittals and relevant safety records | ||
| Asset record | Contractor → appointing party / operator | 6 Handover (verified as-installed) | As-installed dimensions and location, including any deviations. | Final concrete strength, supplier information. | Verified installation/survey evidence, commissioning/O&M and residual safety records | ||
| Mechanical | Air Handling Unit (AHU) | Space and access reservation | MEC task team → LAP design reviewer | 2 Concept Design | Generic 3D box representing overall volume and required clearance zones. | Approximate Flow Rate, System Name | Approved concept/design basis and review record |
| Coordination and procurement basis | MEC task team → STR/ARC task teams, cost consultant | 4 Technical Design | Accurate 3D model with correct dimensions, connection points (duct/pipe), and maintenance access zones. | Asset_ID, Classification_Code, Manufacturer Name, Model Number, Flow Rate, Power Requirements | Approved technical specification, calculations/submittals and relevant safety records | ||
| Maintenance and asset ingestion | Contractor → operator (FM) | 6 Handover (verified as-installed) | Verified as-installed model. | Serial Number, Installation Date, Warranty Start Date (ISO 8601) | Verified installation/survey evidence, commissioning/O&M and residual safety records |
6.6 INFORMATION EXCHANGE REQUIREMENTS#
The following discipline schedule is an overview. Complete each appointment-specific response row below before confirming the BEP; a model does not automatically serve as the whole user requirements statement. Specify requirement revision, purpose, recipient, date, geometry/data/docs, method/reference inputs, security and acceptance; record tender clarifications and change authority.
| EIR response ID / appointment | Upstream OIR/PIR/AIR / objective | Producer / recipient / exchange date | Required containers / LOIN / profile | Inputs and controlled methods | Acceptance rules / capacity and security | Clarification / compliance response / change owner |
|---|---|---|---|---|---|---|
| [ID, appointment] | [decision IDs, why needed] | [actors, EX ID, date/trigger] | [TIDP rows, LOIN IDs, 7.4/9.2.1 profile] | [approved survey/brief/model/doc revisions and method] | [10.3 rule IDs, recipient capability, sensitivity/access] | [meets/proposed deviation/blocked, decision ID, responsible owner] |
| [ID] permit submission (Dubai, where 3.2.2 applies) | DM circular 9-1-3 / 9-1-2 trigger result | ARC + STR task teams, LAP authoriser / Dubai Municipality via the BIM portal / permit application date (and final BIM before completion certificate where required) | ARC and STR models + drawings extracted from them / EX-P06 | Published model revisions; current Dubai BIM Standard export setup and Model Attribute Matrix revision | Project IDS pass; portal file-format and upload limit as stated on the portal | Authority decision recorded per BBM-STD-57 §4; source check per BBM-STD-85 |
Under ISO 19650-1:2018 and ISO 19650-3:2020, OIR/PIR/AIR inform delivery and operational needs; EIR is appointment-specific, not merely historical Employer's Information Requirements. Scope only the office's appointed production/update duties and clarify missing requirements with their owner. Changes update the BEP/annex and TIDP/MIDP together.
This section defines the critical information dependencies between all project parties. The following schedule outlines the primary information that each team requires as an input to begin their work, clearly distinguishing between information provided by the Client and information that must be coordinated internally. It also defines the primary output each team is expected to deliver at key milestones.
Information Exchange Schedule:
| Discipline / Role | Information Required (Inputs) | Information to be Delivered (Outputs) | Format | Timing / Stage |
|---|---|---|---|---|
| Architect (LDC Lead) | • Project Brief & EIR (From Client) • Topographical Survey (From Client) • Existing As-Built Information (From Client) | • Architectural model plus the approved user/brief requirements record; the model is not automatically the full URS. • General Arrangement Drawings. • Room Data Sheets. | .RVT,.PDF | Concept & Technical Design |
| Structural Engineer | • Approved Architectural Model (Internal Coordination) • Geotechnical Survey Report (From Client) | • Structural Model (framing, columns, foundations). • Structural Analysis Model. | .RVT,.PDF Native Analysis Format | End of Concept & Technical Design |
| MEP Engineer | • Coordinated Architectural Model (Internal Coordination) • Coordinated Structural Model (Internal Coordination) • Client's Operational & Equipment Requirements (From Client) | • MEP Models (Mechanical, Electrical, Plumbing, Fire). • System Schematics and Schedules. • Initial asset data for COBie. | .RVT,.PDF.XLSX | End of Technical Design |
| Specialist Consultant(e.g., Façade, AV, Kitchen) | • Coordinated Architectural & Structural Models (Internal Coordination) • Specific Scope Requirements (From Client) | • Specialist Design Model (e.g., Façade System, Kitchen Layout). • Technical Specifications & Data Sheets. | .RVT /.IFC.PDF | Technical Design |
| Cost Consultant | • All discipline models at the agreed milestone (Internal Coordination) | • Quantified Take-Off (QTO) Report. • Cost Plan / Estimate. | .XLSX,.PDF | End of each major Design Stage |
| Contractor | • All construction issue models and drawings (SU-ISSUE, authorised use: construction; From LDC). | • As-Built red-line markups. • Construction progress reports. | .RVT,.NWD.PDF | During Construction |
7 Deliverables#
7.1 CONTAINER EXCHANGE FORMAT#
| DATA TYPE | FORMAT | DESCRIPTION / PURPOSE |
|---|---|---|
| 3D Graphical Models | .RVT | Native authoring format for design, data input, and creating drawings. |
| .IFC | Open format for interoperability and data exchange with non-Revit platforms. | |
| .NWC /.NWD | Autodesk Navisworks formats used for creating and distributing the federated model for 3D coordination, clash detection, and 4D simulation. | |
| 2D Graphical Drawings | The primary format for all formal drawing issuances and submissions. | |
| .DWG | Export format for 2D data exchange with other consultants or contractors as required. | |
| Non-Graphical Documents | .DOCX,.XLSX,.PPTX | Native formats for reports, specifications, schedules, and presentations. |
| The primary format for all formal document issuances and submissions. | ||
| Non-Graphical Asset Data | .XLSX (COBie) | Candidate asset format; use the AIR-approved exact COBie version/profile or another specified schema and receiving test in 7.3.1. |
7.2 PROJECT INFORMATION MODEL PIM DELIVERY STRATEGY#
The PIM comprises all graphical and non-graphical information created during the design and construction phases. The strategy for its delivery is tied directly to the project milestones.
Definition: The PIM is the developing digital representation of the project, including the federated 3D models, 2D drawings extracted from them, and all associated documentation like specifications and reports.
Delivery Milestones: The PIM will be formally delivered at the conclusion of each major project stage, as defined in the project schedule (Section 2.6). Key deliveries include:
Concept Design / Spatial Coordination: produce the use/exchange-specific geometry, data and documentation in 6.5; any adopted LOD shorthand needs its definition and scope, not an automatic RIBA mapping.
Technical Design: provide the approved detailed design/coordination and required data/documentation; do not treat LOD 300 as a complete requirement or proof of coordination.
Construction issue (SU-ISSUE, authorised use: construction): final, coordinated models and all associated construction documentation. "IFC" is never used as an abbreviation for construction issue.
CDE Workflow for Delivery: A formal delivery is the transition of an LAP-authorised container set to the Published state with a transmittal, after the review and approval gates in Section 5 (ISO 19650-2 5.7). Delivery is not acceptance: it becomes accepted only on the recipient A/B/C decision recorded under 5.2.4 and 10.3. A Published platform state alone is not delivery acceptance.
7.3 ASSETS INFORMATION MODEL AIM DELIVERY STRATEGY#
7.3.1 OPERATIONAL REQUIREMENTS AND MAINTAINED AIM#
Decision (2026-11-04,, replaces the COBie v3 default): Deliver COBie only when the EIR requires it, in the COBie version 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 confirmable from NIBS at 2026-11-04 S15, S03.
ISO 19650-4:2022 is an exchange-process basis, not a COBie schema replacement; BS 1192-4:2014 is withdrawn.
| Asset/AIR exchange field | Required particulars / recommended approach | Acceptance evidence |
|---|---|---|
| Operational decision / trigger | Maintenance, inspection, replacement, incident, disposal; confirm AIR IDs and recipients | Actual decision/use requirements, not every model object treated as maintainable |
| Maintainable scope | Asset classes, space/system links, required geometry/properties/docs and exclusions | Scope/count reconciliation and approved exclusion IDs |
| Exact receiving profile | COBie version, template/schema issue, file/encoding/units, keys and required/optional fields | Recipient-approved profile and representative import |
| Source / update owners | Approved submittal, commissioning, survey and O&M provenance; owner by property/document | ID/revision/date and validated source-to-export mapping |
| Safety / rights / security | Residual hazards and controls, permitted use, role access and retention | Competent review and recipient acknowledgment, 1.8/1.13/10.4 records |
| Ongoing AIM update | Asset owner maintains operational baseline; office only performs appointed duties | Tested changed/retired/replacement asset and document/access updates |
Decision (BIM Manager, 2026-10-14): Plan asset drops at early construction, approved procurement/installation updates and handover; plans set actual dates/windows/tests with required geometry/data/docs/safety and ongoing custody. Basis: Progressive verified receiving use establishes the AIM contribution S03, S04.
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.
Reconcile installed evidence/provenance/uncertainty with required model, data, document and safety sets; test FM ingestion, relationships, document opening and updates.
| Trigger / AIR ID | Asset IDs / properties / linked records | Source + update owner | Recipient system/build/profile | Check / decision / next review |
|---|---|---|---|---|
| [handover or operational event] | [maintainable keys, units, O&M/HSI versions] | [provenance, appointed responsible role] | [actual exact receiving build/configuration] | [10.3 evidence, acceptance, future update owner/date] |
For Dubai assets, Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings requires a Quality & Safety Certificate after 20 years from completion (valid 10 years, or 5 years for buildings 40 years or older); the accepted handover information should let the owner's inspecting engineering firm trace systems, fire rating and structure. A final COBie export cannot prove a working operational AIM, asset condition, survey accuracy or maintained document access. Transfer the approved update procedure, custody, training and review triggers with the accepted information.
The AIM is maintained graphical, alphanumeric and documentary information for the asset owner's operational decisions. Accepted delivery information contributes to it and operational triggers continue updating it (7.3.1).
Definition: The AIM is maintained operational information meeting AIR and operational trigger needs. Selected accepted PIM information contributes to it; the AIM is not simply a renamed final PIM or one COBie spreadsheet.
Progressive Handover via COBie Data Drops: The appointed asset-data contribution will be developed through scheduled, profile-approved COBie or other required exchanges; the maintained AIM also includes the required models/documents and operational updates. This ensures data is captured and validated in a timely manner. The planned drops are:
COBie Drop 1 (Beginning of construction): To include all specified assets with their unique IDs, locations (space), and classification codes.
COBie Drop 2 (During Construction): To be updated with approved submittal data, including the specific manufacturer, model number, and supplier for installed equipment.
COBie Drop 3 (Project Handover): The required asset-data contribution to the AIM, updated with all as-installed information, including serial numbers, installation dates, warranty details, and links to O&M manuals.
Verification and Final Handover: Each COBie drop will be submitted in.XLSX format for review and validation by the PMC and the Client's FM team. An approved COBie file alone does not constitute complete AIM handover: record required geometry, data, documents, safety records, ingestion tests and ongoing update ownership in 7.3.1.
7.4 EXACT EXCHANGE PROFILE REGISTER#
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 (2026-11-04,, replaces the COBie v3 default): Deliver COBie only when the EIR requires it, in the COBie version 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 confirmable from NIBS at 2026-11-04 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.
A file extension alone does not prove interoperability. The profile table below implements these qualification choices; actual build/profile decisions and test IDs are still required before live use.
| Profile ID / use | Decided qualification schema / profile | Contents and settings to freeze | Producer / receiver / tests |
|---|---|---|---|
| EX-P01 / reference coordination | IFC 4.0.2.1 (IFC4 ADD2 TC1), Reference View; geometry referenced, native editability not promised | Required entities/Psets/classification; local/shared transform; units; phase/view/links/exclusions; stable GUID policy; preset file/hash | 9.2.1 exact author/exporter/receiver records; MOB-03/04 and 10.3 |
| EX-P02 / native authoring transfer | RVT in one agreed full Revit build; required links/templates/dictionary revisions | Actual file/cloud source identity, permissions, dependent-link versions; receiver edit scope and backup route | Native open/required edit/sync/ownership test; no backward-save assumption |
| EX-P03 / issue exchange | BCF 3.0 XML default; API only after separate approved qualification | Issue ID, model IDs/revisions, element GUIDs, viewpoint, severity, owner, due date, status and retest evidence | Same route/version at both ends; MOB-05 with returned issue |
| EX-P04 / asset exchange | COBie version specified in the EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4); retain appointed alternatives until approved change | Exact recipient template/schema, units, mandatory fields/keys, relationships and O&M/HSI links | Target system/profile and MOB-07; no silent version upgrade |
| EX-P05 / information rules | IDS 1.0 where applicable to IFC information validation | Requirement/applicability IDs, file/hash, mappings, expected valid/invalid cases, checker build | Audit IDS itself then validate full applicable population; geometry/clearance separate |
| EX-P06 / Dubai building permit submission | The IFC schema and export setup stated in the current Dubai BIM Standard (buildindubai.gov.ae/bim), checked at project start and recorded in this row (: authority submissions use the schema stated by the authority); openBIM IFC, zipped, upload limit as stated on the portal | Release preset EXP-DM-PERMIT-<schema>-<rev> per BBM-STD-65-TEMPLATES_AND_RELEASE-V0.2 (schema as stated in the current Dubai BIM Standard), with export setup name/revision and hash; Model Attribute Matrix issued with the current Dubai BIM Standard, downloaded at project start with its revision recorded; drawings extracted from the submitted model; source check date | ARC/STR task teams / Dubai Municipality; MOB-03 with the permit setup, project IDS for matrix fields; requirement detail in BBM-STD-85 and BBM-STD-57 |
Per (re-affirming): IFC 4.0.2.1 Reference View is the default; IFC 4.3.2.0 (ISO 16739-1:2024) is used only by recorded approval when the sender build and receiver both pass a test exchange; IFC2x3 only when an appointment or authority profile requires it; authority submissions use the schema stated by the authority. The Revit IFC exporter 27.4.0.30 (30 Oct 2026) exports IFC4x3; use IFC 4.3 Reference View only after a test export from the project build passes the project IDS. For IFC 4.3.2.0, IFC2x3 or Design Transfer View, create a separate approved profile row with purpose, complete settings and known-data receiving tests. A schema's publication or export checkbox does not establish support. Confirm BCF XML/API capability separately. Include authoritative transmittal identity and check/receiving evidence for native, open, data and documentation containers alike.
8 Standard Methods & Procedures SMP#
8.1 VOLUME STRATEGY#
All BIM models should be divided and segregated in a proper way with alignment of project site zones and levels.
Decision (BIM Manager, 2026-10-14): Treat 300 MB as performance investigation/splitting trigger only; measure actual hardware/network/workload and preserve IDs, ownership, federation and receiver use when splitting. Basis: Size alone is not exchange acceptance or a universal limit P02, S04.
Splitting preserves identity, ownership, federation boundaries and intended receiver use.
8.2 PIM ORIGIN & ORIENTATION#
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.
Modelling near a stable local origin can coexist with georeferenced exports; never force all exports to 0,0,0.
| Coordinate record | Value / approved source | Test / authorised change |
|---|---|---|
| Survey / controls | [approved issue and uncertainty; control IDs/coordinates] | 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. |
| CRS / vertical datum | [BBM-STD-86 §2 register key CRS-DXB / CRS-AUH / CRS-OTH; EPSG code + name and transformation; vertical datum] per 2.2 and the BBM-STD-86 §6 per-project record (Dubai EPSG:3997 + DMD; Abu Dhabi per ADM/DMT guideline + Ras Ghumays); IFC georeferencing per BBM-STD-86 §4 | MOB-03: exported IFC carries IfcProjectedCRS with the declared EPSG code and IfcMapConversion matching the register |
| Local/shared mapping | [offset XYZ, rotation/unit/scale, CRS/datum] | Native, federation and receiver agree within approved survey-purpose tolerances |
| Cloud/file route | [actual supported shared-coordinate workflow/build] | Do not assume a file-based Publish Coordinates command is available in cloud workflow |
| Changed survey / transform | [change ID, affected models/exports, coordinate authority] | Protected-copy test, dependent-link/receiver retest, controlled reissue |
| Unverified existing conditions | PROVISIONAL; limited approved study use | No survey/as-built/construction accuracy claim until verified evidence and receiving approval |
PROJECT ORIGIN:
Confirm the coordinate authority, approved survey/control provenance, CRS/datum/units and transform; a received file labelled As-Built is not independent evidence
Refer to section 2.2
ORIENTATION:
Record approved rotation, elevation and shared/local mapping; treat unverified inputs as provisional with restricted permitted use
True North: project-specific surveyed/approved angle and units; the legacy 39.90 value is removed as an unverified project carry-over
Origin, CRS and transform are recorded in the coordinate register (8.2 table) and the shared-coordinates site/base model [container ID].
8.3 NAMING CONVENTIONS#
8.3.1 DOCUMENT NAMING CONVENTION#
Use a single approved Project Naming Register shared with BBM-STD-01-MANUAL-V0.5 §3.1. External containers use the 8-token CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext grammar (re-affirming); ORG-PROJ-DISC-PHASE-SEQUENCE survives only as a mapped internal WIP alias that is never issued, and the PHASE token is retired. Neither grammar is universally prescribed by ISO. Binding appointment/EIR requirements govern project exchanges within the signed hierarchy. Do not impose two grammars or rename historical issues.
Decision (BIM Manager, 2026-10-14): Use CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext when an appointment supplies no grammar; retain internal Rnn revisions and the suitability list below. Basis: Adopts the Manual/BEP external candidate and existing Rnn convention consistently; appointment requirements take precedence through one recorded mapping G-C. Authority: Clash matrix section 2, the shared naming/revision/suitability list.
The PHASE token is retired. "IFC" never abbreviates construction issue; .ifc remains a format, not construction permission.
| Token / control | Recommended value / example | Validation / required project record |
|---|---|---|
| CLIENT / ORG / PROJ | CLI / OFF / P001 in synthetic examples | Approved code lists and immutable project/appointment identity |
| VOLUME / LEVEL | ZZ / ZZ for whole model only where adopted | Project spatial division and no overlapping scope |
| TYPE / ROLE / NUMBER | M3 / A / 0001 for synthetic architectural model | Controlled document/type code list; 1-letter ROLE from BBM-STD-93-CODE_DICTIONARY-V0.1; unique number namespace |
| Valid synthetic example | CLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc | Correct tokens + actual schema/profile and metadata checks |
| Invalid example | CLI-OFF-P001-ZZ-M3-A-0001.ifc | Reject missing LEVEL; no implicit token shift |
| Internal aliases | 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. | One mapping to external container ID; preserve historic issues |
| Views / sheets | Decision (BIM Manager, 2026-10-14): Use DISC-LEVEL[-ZONE]-TYPE-DESC for views and DISC-CAT-INDEX for sheet numbers, with separate readable title and revision; register Start View/library exceptions and validate codes. Basis: Retains the shared Manual/BEP convention while separating display from identity S35, G-C. | Same Manual 3.1/12.3 baseline; Start View/library exceptions registered |
| Revision / suitability | Decision (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. | Revision sequence per changed container; unchanged issue revisions retained |
| Migration | Prior ID → new ID, reason, approver, affected links and effective date | Authorised future issue only; original identity/history retained |
| Register approval | Decision (BIM Manager, 2026-10-14): The project IM maintains one naming/code register, approved by LAP/recipient within appointment powers; validate eight uppercase hyphen-separated tokens, registered volume/level/type/role, four-digit NUMBER and lowercase approved extension; use ISO 8601 dates. Basis: Syntax, dictionaries, uniqueness and permitted use must agree across documents G-C. | Same register ID/revision referenced in BEP and Manual annex |
Decision (BIM Manager, 2026-10-14): The project IM maintains one naming/code register, approved by LAP/recipient within appointment powers; validate eight uppercase hyphen-separated tokens, registered volume/level/type/role, four-digit NUMBER and lowercase approved extension; use ISO 8601 dates. Basis: Syntax, dictionaries, uniqueness and permitted use must agree across documents G-C.
Regex alone is insufficient; dates do not automatically supersede an issue.
8.3.2 SYSTEM NAMING CONVENTION#
| XX | XX | XXX | XXX | XXX | XXX | XXX |
|---|---|---|---|---|---|---|
| ORIGINATOR | DISCIPLINE | SUB-DISCIPLINE | SYSTEM TYPE | DESCRIPTION | DATA | DATA |
| REQUIRED | REQUIRED | REQUIRED | REQUIRED | REQUIRED | OPTIONAL | OPTIONAL |
8.3.3 OBJECT NAMING CONVENTION#
The system/object tables are legacy internal authoring/library grammars, not alternative external container patterns. Register category/type abbreviations, permitted descriptors and immutable library version separately. Global/system control parameters differ from asset identity; avoid introducing a new live file ID from a family name.
| XX | XX | XXX | XXX | XXX | XXX | XXX |
|---|---|---|---|---|---|---|
| ORIGINATOR | DISCIPLINE | REVIT CATEGORY | DESCRIPTION | DATA | DATA | DATA |
| REQUIRED | REQUIRED | REQUIRED | REQUIRED | OPTIONAL | OPTIONAL | OPTIONAL |
8.3.4 NAMING CONVENTION GENERAL REF#
Code lists are held once: discipline/role, suitability and gate codes in BBM-STD-93-CODE_DICTIONARY-V0.1; project volume, level and type codes in the Project Naming Register (8.3.1). This BEP keeps no separate code table.
8.4 DRAWING SHEET TEMPLATE#
Sheets, title blocks and cover sheets follow BBM-STD-67-DRAWINGS_AND_SHEETS-V0.2: title-block data fields per ISO 7200:2004, drawing representation per ISO 128-1:2020, minimum plotted text height 2.5 mm on all sheets at paper size. An appointment-mandated template overrides through one recorded mapping.
8.4.1 DRAWINGS SHEETS#
Sheet numbers use DISC-CAT-INDEX (8.3.1) with the title block of BBM-STD-67; sheet content follows BBM-STD-67 and BBM-STD-66-CAD_STANDARD-V0.2 for CAD content.
8.4.2 COVER SHEET#
Cover sheet fields and layout follow BBM-STD-67; it carries container ID, revision, suitability and the drawing register.
8.5 MODEL SEGREGATION STRATEGY#
Decision (BIM Manager, 2026-10-14): Assign one accountable task team/source model and controlled Shared snapshot/coordination cycle; freeze IDs/revisions/transforms/profile/coverage/interfaces; boundary changes preserve aliases/IDs and trigger retests. Basis: Federation needs approved source revisions and owned boundaries G-F, S04.
Use exact approved Shared revisions, not latest filesystem timestamps; record coverage gaps and affected interface retests.
| Federation ID / model container | Scope and producer | Source revision / share decision | Transform / links / profile | Interfaces / excluded scope | Coordinator check |
|---|---|---|---|---|---|
| [ID] | [discipline/zone/system, task team] | [immutable version + suitability] | [coordinate register, dependent IDs, EX-P ID] | [handoff owners, no overlap/gap] | [counts, alignment, decision/evidence ID] |
8.6 PARAMETERS#
Apply ISO 23386:2020 and ISO 23387:2025 principles through a controlled dictionary, shared-parameter GUID/binding record and source-to-export mapping. The legacy table below is a candidate field catalogue; it is not proof that the project has populated values or correct category bindings. No all-category default or display-name match overrides the approved dictionary.
| Property ID / alias reconciliation | Recommended semantic/binding decision | Exchange and acceptance |
|---|---|---|
| Asset_ID ← Asset ID / Asset Tag / AssetTag | Decision (BIM Manager, 2026-10-14): Use canonical Asset_ID as stable text occurrence identifier for applicable maintainable assets; map AssetID, Asset ID, Asset Tag and AssetTag aliases, retaining distinct physical/finance tags where needed; preserve GUIDs and receiver mappings. Basis: Stable semantic identity matters more than display aliases or blind renaming S16, S17. | Required unique key per AIR; preserve across issue revisions; fixed-asset financial ID may be distinct |
| Classification_Code ← Classification / Classification Code (Uniclass) | Decision (BIM Manager, 2026-10-14): Use canonical Classification_Code with separate ClassificationTable, ClassificationTitle and ClassificationRelease; map ClassificationCode and legacy labels; use type binding only when valid for the entire type and verify IFC classification-reference mapping. Basis: Definition, binding and classification version require one dictionary S16, S09. | Native/shared GUID and IFC classification reference mapping; exact code validation |
| Expected_Life_Years ← Expected Life (Years) | Decision (BIM Manager, 2026-10-14): Use canonical Expected_Life_Years as numeric duration in years with source/assumptions; map ExpectedLife and legacy text only after validation; unknown is not zero and no lifespan is invented. Basis: Typed units and provenance prevent misleading conversions S16, S17. | Convert legacy text only after validation; no blind casting or invented lifespan |
| Fire_Rating ← Fire Rating / FireRating | Decision (BIM Manager, 2026-10-14): Use canonical Fire_Rating with approved units/definition and certification evidence; map FireRating/Fire Rating and bind type/instance from certification scope; verify native/IFC export. Basis: Nonempty text does not establish certified performance S16, S06. | Stored as integer minutes with Fire_Rating_Standard and Fire_Rating_Source; basis UAE Fire & Life Safety Code of Practice 2018 plus the tested assembly; binding and native/IFC property verified; non-empty text alone insufficient |
| Dates / service interval | Decision (BIM Manager, 2026-10-14): Use ISO 8601 dates (YYYY-MM-DD), access timestamps with UTC offset, and explicit units/source for service intervals; validate chronology and receiver mappings with actual calendars/time zones. Basis: Unambiguous dates/units support traceable schedules and exchanges S16, G-F. | Valid dates, chronology and receiver mapping; no mixed numeric/text units |
For every property record canonical ID, definition, version, owner, actual shared GUID, native data type, units/allowed values, categories, instance/type scope, source/update owner, applicable EIR/LOIN IDs and exact IFC/asset destination. Check representative tag/schedule and export values, then all mandatory obligations across the applicable population. Populate actual GUIDs from the approved parameter file; inventing a GUID would not reconcile existing models. Record deliberate aliases and migration decisions with before/after/retest evidence.
8.6.1 PROJECT PARAMETERS#
Apply the approved EIR and the BBM-STD-01-MANUAL-V0.5 §3.2 / BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2 dictionary baseline. These parameters support project delivery and O&M. The CANONICAL ID column governs; the PARAMETER column shows the legacy display name, kept only as a mapped alias. Date parameters use rule VAL-DATE-01: value is ISO 8601 YYYY-MM-DD and a real calendar date, Warranty Start Date ≤ Warranty End Date, and Installation Date ≤ Warranty Start Date where both exist.
| CANONICAL ID | PARAMETER (legacy alias) | TYPE | DATA TYPE | GROUP UNDER | APPLICABLE REVIT CATEGORIES |
|---|---|---|---|---|---|
| Per BBM-STD-72 dictionary | Acoustic Rating | Type | Text | Identity Data | Doors, Walls, Floors, Ceilings |
| Asset_ID (/121) | Asset ID | Instance | Text | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq, Doors |
| Per BBM-STD-72 dictionary | Asset is a system-isolating device | Instance | Yes/No | Data | All Modelled Elements |
| Per BBM-STD-72 dictionary | Certificate Identifier | Type | Text | Identity Data | Doors, and other certified equipment |
| Classification_Code + ClassificationTable/Title/Release | Classification Code (Uniclass) | Type | Text | Identity Data | All Modelled Elements |
| Per BBM-STD-72 dictionary | Department Name | Instance | Text | Identity Data | Rooms, Spaces |
| Per BBM-STD-72 dictionary | Digital O&M | Type | URL | Data | Mechanical Eq, Electrical Eq, Specialty Eq |
| Expected_Life_Years | Expected Life (Years) | Type | Number | Data | Mechanical Eq, Electrical Eq, Specialty Eq, Walls, Floors, Ceilings |
| Per BBM-STD-72 dictionary | FAR ID (Fixed Asset Register ID) | Instance | Text | Identity Data | All Modelled Elements |
| Per BBM-STD-72 dictionary | Finish | Type | Material | Materials and Finishes | Doors |
| Per BBM-STD-72 dictionary | Finish (Ceiling) | Instance | Material | Materials and Finishes | Rooms, Spaces |
| Per BBM-STD-72 dictionary | Finish (Floor) | Instance | Material | Materials and Finishes | Rooms, Spaces |
| Per BBM-STD-72 dictionary | Finish (Walls) | Instance | Material | Materials and Finishes | Rooms, Spaces |
| Fire_Rating (integer minutes) + Fire_Rating_Standard + Fire_Rating_Source | Fire Rating | Type | Integer (minutes) | Identity Data | Doors, Walls, Floors, Ceilings |
| Per BBM-STD-72 dictionary; ISO 8601, VAL-DATE-01 | Installation Date | Instance | Text (YYYY-MM-DD) | Phasing | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary | Maintenance Frequency/Year | Type | Integer | Mechanical | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary | Manufacturer Model Number | Type | Text | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq, Doors |
| Per BBM-STD-72 dictionary | Manufacturer Name | Type | Text | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq, Doors |
| Per BBM-STD-72 dictionary | Material Information | Type | URL | Data | Walls, Floors, Ceilings |
| Per BBM-STD-72 dictionary | Occupancy | Instance | Integer | Identity Data | Rooms, Spaces |
| Per BBM-STD-72 dictionary | Operational Cost | Instance | Currency | Data | Rooms, Spaces |
| Per BBM-STD-72 dictionary | Priority | Instance | Text | Identity Data | All Modeled Elements |
| Per BBM-STD-72 dictionary | Replacement Cost | Type | Currency | Data | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary | Replacement Cost (per m²/ft²) | Type | Currency | Data | Walls, Floors, Ceilings |
| Per BBM-STD-72 dictionary | Serial Number | Instance | Text | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary | Status | Instance | Text | Phasing | All Modeled Elements |
| Per BBM-STD-72 dictionary | Supplier | Type | Text | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary; ISO 8601, VAL-DATE-01 | Warranty End Date | Instance | Text (YYYY-MM-DD) | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq |
| Per BBM-STD-72 dictionary; ISO 8601, VAL-DATE-01 | Warranty Start Date | Instance | Text (YYYY-MM-DD) | Identity Data | Mechanical Eq, Electrical Eq, Specialty Eq, Doors |
| Per BBM-STD-72 dictionary | Zone Name | Instance | Text | Identity Data | Rooms, Spaces |
8.6.2 PARAMETERS SETUP#
Parameters setup is created using a Central shared parameters file and we use the previously provided table to setup the parameters.
8.7 WORKSETS#
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.
Apply active workset at placement, scoped borrowing, sync/relinquish and colleague handoff; no compulsory curtain-system user workset.
8.8 VIEWS MANAGEMENT#
Views are managed and controlled to achieve a smooth workflow, proper coordination and checked issue production, per BBM-STD-01-MANUAL-V0.5 §4.12 View templates; view names follow 8.3.1.
8.9 FILTERS MANAGEMENT#
Filters are managed and controlled to achieve a smooth workflow, proper coordination and checked issue production, per BBM-STD-01-MANUAL-V0.5 §4.13 Filters.
8.10 MODEL HEALTH MANAGEMENT#
Regular model health checks follow the office protocols for model creation and maintenance.
Run Autodesk Model Checker for Revit [exact version] with the office check set [ID / version / hash] weekly and before each share; the check set includes the blocking warning list WRN-01..WRN-nn and is frozen and tested with known valid/invalid fixtures. Log results against 10.2 A.
8.11 ASSET MANAGEMENT#
8.11.1 INITIATION, MODIFICATION & DOCUMENTATION#
Apply the approved EIR and the BBM-STD-01-MANUAL-V0.5 §3.2 / BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2 dictionary baseline. This section outlines the lifecycle of asset data from its creation to its final documentation.
ASSET INITIATION#
Trigger: Asset data is initiated when a component representing a physical, maintainable asset is placed in the model.
Responsibility: The discipline model author (e.g., Mechanical Engineer, Electrical Engineer) is responsible for the initial input of asset data.
Data Source: Initial data shall be derived from the Basis of Design (BOD) and project specifications. Placeholder values are permissible during early design stages, but key performance data must be included.
Unique Identification: Every asset will be assigned a unique Asset ID upon initiation. This ID is generated under the approved AIR/dictionary key scheme, with uniqueness and retirement/replacement rules; refer to 8.6 and the project asset-ID register
DATA MODIFICATION WORKFLOW#
Source of Truth: Asset data (e.g., Manufacturer, Model Number) shall only be modified upon the formal approval of a technical submittal or RFI via the project's CDE. The approved document is the source of truth for the change.
Process:
An RFI or Submittal is approved.
The relevant discipline lead is notified.
The discipline lead instructs the model author to update the parameter(s) in the Revit model with the approved information.
Auditing: Retain an explicit property-change log (asset/property ID, previous/new value, source approval/revision, author/reviewer/date, source/export versions). CDE/native versions alone do not prove a field-level change audit; validate exports against approved source records.
DATA DOCUMENTATION AND VERIFICATION#
Primary record: Name the authoritative system/source per asset property and document in the AIR/dictionary. The Revit model is an authoring source for assigned fields, not automatically the authoritative record for all operational or procurement data.
Deliverable Format: Where the EIR requires COBie, asset data handover uses the COBie version specified in the EIR; default COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3. Otherwise use the EIR-specified asset schema.
Verification: Prior to each major data drop or milestone, the BIM Manager will export schedules for review. Each discipline lead is responsible for verifying the accuracy and completeness of their respective asset data. The data must be validated before the official COBie file is generated and issued.
8.11.2 CLASSIFICATION#
Apply the approved EIR and the BBM-STD-01-MANUAL-V0.5 §3.2 / BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2 dictionary baseline. This section defines the standard used to categorize all assets in a structured, consistent manner. Adopted release: Uniclass 2015 July 2026 release (Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27) unless the appointment names another.
Decision (BIM Manager, 2026-10-14): Use Uniclass 2015 as office default, freezing adopted table/release/licence; preserve appointed/authority classifications through mappings and controlled upgrades. Basis: Uniclass is maintained, not a fixed release or exclusive mandate S09, S10.
Validate adopted codes consistently through the appointed asset lifecycle.
Process and Responsibility:
Selection: The discipline model author is responsible for selecting the appropriate Uniclass 2015 code for each asset type. The primary tables to be used for assets are Products (Pr) and Systems (Ss).
Data Input: The selected code is entered into the canonical shared parameter Classification_Code (alias: Classification Code (Uniclass)), with ClassificationTable, ClassificationTitle and ClassificationRelease. Bind it as a Type parameter only when the code is valid for the entire type; otherwise bind as instance (8.6).
Verification: The BIM Manager will perform regular model audits to identify any assets where Classification_Code is empty or not valid for the recorded table release. These omissions will be reported to the relevant discipline lead for correction.
Example:
An air handling unit in the model will be selected.
The Mechanical Engineer will consult the Uniclass 2015 tables and identify the correct code from the Products table.
Select and verify the AHU code/description against the frozen project Uniclass Products table/release, then bind it at the dictionary-defined scope. Do not carry an unchecked historical code into the new issue.
Classification granularity is defined by the approved use/EIR and table release; no universal Level 3 limit. Check table/code semantics and receiver mapping, not only population.
Any classification/data tool must be recorded by version/check-set/hash, tested with known valid/invalid values and reviewed; a tool name does not ensure correct data.
8.12 CLASH AND CLEARANCE ASSURANCE#
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.
Use the single Clash matrix section 3 H/C/A/D/V table for every stage; approved project rule IDs supply purpose/pair/zone/units, evidence and actual selection scope.
Decision (BIM Manager, 2026-10-14): Require 100% valid applicable mandatory geometry, data and documentation and zero unresolved required hard-intersection or mandatory access/safety failures in the issued scope. Basis: An issue count or optional-data percentage cannot average away a mandatory exchange failure S04.
Decision (BIM Manager, 2026-10-14): 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): Run weekly, every coordination comment round, on affected source/rule changes and before exchange; use Manual severity S1 Critical, S2 Major, S3 Minor. Basis: Retains the office issue-management service levels and adds revision-specific evidence and independent retest S04. Authority: Clash matrix section 7, severity and response deadlines.
The matrix owner records rule/version, selections/exclusions, geometry precision, designers and exact-revision retest; no office role may waive binding safety/access requirements.
BCF/issue fields: unique issue ID, exact source model IDs/revisions, affected element GUIDs, viewpoint/location, rule/severity, owner, due date, designer disposition, approved exception if permissible, fixed revision, reviewer and retest report. Status Open → In Progress → Ready for Review → Closed only when the required retest passes; reopen if a later model revision reintroduces it. A screenshot or decreasing total count alone does not close an issue. Severity is S1 Critical / S2 Major / S3 Minor per Clash matrix section 7. Reassess legacy C/H/M/L against actual consequence; mandatory failures block release regardless of severity. S1 acknowledges within 4 working hours, targets correction within 2 working days and immediately stops unsafe/release work; S2 corrects within 5 working days or earlier gate; S3 corrects or records a permissible disposition before the next gate.
| Priority | Test Name | Selection Set A (Left) | Selection Set B (Right) | Clash Type | Tolerance | Notes / Action Required |
|---|---|---|---|---|---|---|
| S1 Critical | STR vs. MEP Services | Structure: All Structural Framing, Columns, Floors, Foundations | MEP: All Ducts, Pipes, Cable Trays, in-scope Conduits | Hard | Rule H: 0 mm deliberate penetration allowance | Required physical conflicts must be resolved or validly dispositioned by competent structure/MEP designers; no unilateral structural change. |
| S1 Critical | STR vs. Architectural Openings | Structure: All Structural Framing, Columns | Architecture: Doors, Windows, Curtain Walls | Hard | Rule H: 0 mm deliberate penetration allowance | Ensures all openings in structural elements are correctly modelled and sized. |
| S2 Major | MEP vs. MEP (Major Services) | MEP Set 1: in-scope HVAC Ducts and Major Pipes; any size filter requires explicit approval | MEP Set 2: All other Ducts, Pipes, Cable Trays | Hard | Rule H: 0 mm deliberate penetration allowance | Primary coordination test for major services in ceiling plenums and risers. |
| S2 Major | MEP vs. Architectural Ceilings | Architecture: All Ceilings and Ceiling Grids | MEP: Air Terminals, Sprinklers, Lighting Fixtures | Hard | Rule H: 0 mm deliberate penetration allowance | Validates that all ceiling-hosted devices fit correctly within the ceiling system. |
| S1/S2 by actual consequence | Equipment Maintenance Access | Equipment: Mechanical, Electrical, and Specialty Equipment | All Other Disciplines: Structure, Walls, MEP Services | Access / maintenance | Rule A: approved access/removal envelope | Use code/design/manufacturer requirement and exact rule ID; no blanket 500 mm. |
| S1/S2 by actual consequence | Above-Ceiling Work Zone | Structure: Structural Floor Slab Above | MEP: Top of all Ducts, Pipes, and Cable Trays | Clearance | Rule C: approved installation separation/envelope | Record actual requirement and sequence; no blanket 150 mm. |
| S1/S2/S3 by actual consequence | Discipline Model Quality Check | Run per discipline: Model | Run per discipline: Model | Duplicates | Rule D: exact coincident investigation | No proximity deletion or blanket 10 mm merge; preserve deliberate references and correction evidence. |
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.
Legacy 15/5/20/25 mm settings and blanket 500/150/10 mm values are retired. No count or tolerance proves universal zero-clash or safety assurance.
SEARCH SETS AND GENERAL CLASH MATRIX — retained legacy coverage index only; legacy group labels (MEP-M, MEP-P, MEP-E, FP) map to the BBM-STD-93 codes MEC, PLU, ELE and FLS; C/H/M/L below are historical labels, not current issue severity or rule acceptance. Reassess actual active rules under Clash matrix sections 3 and 7.
| (Selection Set A) | STRUCTURE (STR) | ARCHITECTURE (ARC) | MECHANICAL (MEP-M) | PLUMBING (MEP-P) | ELECTRICAL (MEP-E) | FIRE PROTECTION (FP) |
|---|---|---|---|---|---|---|
| Str. Framing & Columns | Walls & Floors | Ducts & Fittings | Pipes & Fittings | Cable Trays & Conduits | Sprinklers & Pipes | |
| STRUCTURE (STR) | ||||||
| Str. Framing & Columns | M | C | C | C | C | |
| Walls & Floors | M | H | H | H | H | |
| ARCHITECTURE (ARC) | ||||||
| Walls & Floors | C | H | H | H | H | |
| Ceilings | H | H | H | H | H | H |
| Curtain Walls | C | H | M | M | M | M |
| MECHANICAL (MEP-M) | ||||||
| Ducts & Fittings | C | H | H | H | H | |
| Mechanical Equipment | C | H | H | H | H | H |
| Air Terminals | H | M | H | M | H | H |
| PLUMBING (MEP-P) | ||||||
| Pipes & Fittings | C | H | H | H | H | |
| Plumbing Fixtures | H | H | H | H | H | H |
| ELECTRICAL (MEP-E) | ||||||
| Cable Trays & Conduits | C | H | H | H | H | |
| Electrical Equipment | C | H | H | H | H | H |
| Lighting Fixtures | H | M | H | M | H | H |
| FIRE PROTECTION (FP) | ||||||
| Sprinklers & Pipes | C | H | H | H | H |
9 IT Solutions#
9.1 Hardware#
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.
Decision (BIM Manager, 2026-10-14): Treat 300 MB as performance investigation/splitting trigger only; measure actual hardware/network/workload and preserve IDs, ownership, federation and receiver use when splitting. Basis: Size alone is not exchange acceptance or a universal limit P02, S04.
The old hardware inventory is not a current vendor minimum or buying recommendation. The reference is the Autodesk system requirements for the frozen build in 9.2.1, plus measured PERF-01 results; measure actual OS/RAM/storage/GPU/driver/network and representative workload.
| HARDWARE CATEGORY | ITEM / ROLE | LEGACY INVENTORY (NOT A MINIMUM) | PRIMARY BIM USE(S) / PURPOSE |
|---|---|---|---|
| Workstations | Standard BIM Workstation | • Processor: Intel Core i7 (7740x or equivalent) • RAM: 64 GB • Graphics: NVIDIA Quadro/RTX (e.g., P2200) with 4 GB VRAM • Display: Dual 24-inch Monitors (1920x1080 or higher) | • Model Authoring (MA) • Design Review (DR) • 3D Coordination (3DC) • Quantity & Cost (QCC) |
| Advanced BIM Workstation | • Processor: Intel Core i9 (or equivalent) • RAM: 64 GB or more • Graphics: NVIDIA RTX/Quadro (e.g., P5000, RTX A4000) with 8 GB+ VRAM • Display: Dual 24-inch Monitors (1920x1080 or higher) | • Project Control & Monitor (PCM) • Complex simulations, animations, and analysis • Virtual Reality (VR) sessions | |
| Site Equipment | Site Coordination Tablet | • Device: Apple iPad / Microsoft Surface / Samsung Tablet • Storage: 32 GB Minimum • RAM: 8 GB Minimum • Case: Durable, ruggedized case for site conditions | • Build & Commissioning (BC) • Facility Management (FM) • On-site model review, snagging, and issue tracking |
| Meeting & Collaboration | Meeting Room Display | • Device: Large Format Smart TV (Touch enabled) or SMART Board with Projector • Size: 65-inch Minimum | • Collaborative workshops • Design review meetings • Clash detection resolution sessions |
| Office Peripherals | Plotter | • Type: A0-size Color Inkjet Plotter | • Printing large-format coordinated drawings and architectural sheets. |
| Printers / Scanners | • Type: A3/A4 Color Laser Multifunction Printer | • Printing reports, schedules, and general project documentation. | |
| Project Infrastructure | Project Server | • Type: High-performance server with high-speed read/write capability. • Purpose: Centralized storage for project files (if not exclusively cloud-based). | • Hosting project data and enabling fast local network access. |
| Internet Connectivity | • Type: High-speed, business-grade fiber optic internet. | • Facilitating real-time collaboration on the Autodesk Construction Cloud (ACC). |
Where required by the confirmed EIR
9.2 Software versions#
| CATEGORY | CANDIDATE SOFTWARE (exact frozen baseline required in 9.2.1; no version-or-later permission) | PRIMARY BIM USE(S) / PURPOSE |
|---|---|---|
| Collaboration Platform (CDE) | Autodesk Construction Cloud (ACC) | Single Source of Truth. Used for all model hosting, data management, design reviews, issue tracking, and as-built documentation. |
| Primary Authoring (Buildings) | Autodesk Revit | Core modeling tool for Architecture, Structure (concrete/steel), and MEP disciplines. Used for Design Authoring, Asset Management data input, and creating drawings. |
| Primary Authoring (Infrastructure) | Autodesk Civil 3D | Modeling for all site work, utilities, roads, and topography. Used for Existing Conditions Modelling and Site Analysis. |
| Primary Authoring (Structural Steel) | Trimble Tekla Structures | Used for detailed modeling and fabrication drawings of complex structural steel elements, if required. |
| Coordination & Simulation | Autodesk Navisworks Manage | Primary tool for 3D Coordination (Clash Detection) and 4D Phase Planning (Construction Sequencing). Used to federate all models. |
| Model Checking & Validation | • Solibri Office (only if separately qualified per 9.2.1; "Solibri Model Checker" is the legacy name) • Autodesk Model Checker for Revit | Rule-based checking within the qualified rule scope; competent design/code review and receiving acceptance remain separate. |
| Scheduling & 4D Simulation | Synchro PRO | Advanced 4D Phase Planning and construction simulation, linking the 3D model to the construction schedule in detail. |
| Quantity Takeoff & 5D Costing | CostX | Primary tool for extracting quantities from the BIM models and preparing cost estimates (5D Cost Estimation). |
| Visualisation / rendering (optional) | Production renderer registered with its exact build in 9.2.1 when the visualisation use is selected (3.2.1); Blender is a fixture-only renderer outside the office software register (see BBM-STD-80-VISUALISATION-V0.2 §2) | Renders and VR content for selected visualisation uses only; renders are not design or coordination evidence. |
| Supporting 2D & Concept Design | Autodesk AutoCAD & Trimble SketchUp | Used for 2D detailing, creating schedules, and early-stage conceptual massing. Not to be used for primary 3D model authoring. |
Where required by the confirmed EIR
9.2.1 FROZEN BUILD, PROFILE AND TRUST REGISTER#
Never use “2025 or later” as compatibility permission. Freeze and test exact authoring, exporter, federation/checker, receiving and plugin combinations. New release availability does not establish installed office configuration. Autodesk Revit Help 2026 in the References describes concepts, not the installed version; the following selected authoring/exporter qualification baselines have supplementary publisher evidence checked on 14 October 2026.
| Component / decided qualification baseline | Required actual record before use | Evidence / decision status |
|---|---|---|
| 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. | Actual About/full build per release (BBM-STD-91 record field), template upgrade test, update/OS, native/cloud compatibility, licence and receiving build; retain mandated project major version unless approved upgrade | Template BBM-ARC-TMP-R23 observed on the share; upgrade tests and office installation NOT VERIFIED |
| 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. | Actual exporter/package and binary file versions, source/licence/hash, preset/mapping hash and compatibility with authoring build | Autodesk official revit-ifc release tag IFC_v25.4.40; office installation/compatibility NOT VERIFIED |
| 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. | Receiver About/build/OS and required link/cloud access; lower major versions not assumed capable of native opening | MOB-02/04 actual result pending |
| 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. | Product/full build, rule-set ID/hash, schema/IDS capabilities and known-result tests; choose one actual route per use | Exact office build not supplied; record before readiness, no invented build |
| 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. | Exact version or cloud tenant/service configuration/date, import schema, units and document access | Recipient must provide build/profile and MOB-04/07 evidence before acceptance |
| 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. | Both endpoints/tool builds, API version/permissions or XML file profile, round-trip test | MOB-05 pending; no assumption both routes are interchangeable |
| Revit version lifecycle: Supported majors are Revit 2024, 2025, 2026 and 2027 (Autodesk previous-versions list, checked 2026-11-04). Revit 2023 is out of Autodesk support: legacy, no new projects; existing projects only with recorded risk acceptance, frozen build and an upgrade plan. The new-project baseline is reviewed at each annual Autodesk release with a qualification test before adoption (latest Revit 2027 update 2027.3, 15 Sep 2026; Revit IFC exporter 27.4.0.30, 30 Oct 2026). Full matrix: BBM-STD-91-SOFTWARE_SUPPORTED_RELEASES-V0.1 | Release, support status, qualified build, IFC exporter, seed and library save version per project | Lifecycle check recorded at project start and at each annual release |
| Scripts/plugins/AI | Provider/licence, exact version/hash/dependencies/loading manifest, approved input custody and human reviewer | Representative before/after check, known faults, rollback and access test; no unverified free/checked claim |
Supplementary sources: Autodesk Revit 2025 Product Updates (Autodesk, 2026 update listing); IFC Exporter 25.4.40 official release (Autodesk, 2026). Selected qualification pairing requires tests; publication does not prove their combined compatibility, installation or availability for this office.
Capture immutable CDE/source/export versions and actual installer/binary/configuration hashes where possible. Qualify on isolated representative content before deployment; retain backups and an approved upgrade/rollback route. A Revit major-version upgrade may not be reversible by saving backward; recovery uses the preserved original baseline. Without exact actual checker/receiver records and passing tests, mark the affected exchange BLOCKED FOR RELEASE, even though its documentation is complete.
9.3 TECHNOLOGY COMPATIBILITY#
Any compatible software/hardware that could meet the client requirements should be communicated with the responsible team and arrange Proof of Concept (POC) for the project team.
9.4 PROCESS AND DATA MANAGEMENT SYSTEM#
The official process and data management system for this project is the Common Data Environment (CDE). The CDE integrates the technology platform with the project's defined processes to create a single source of truth for all information.
Decision (BIM Manager, 2026-10-14): Select Autodesk Construction Cloud as office default for agreed model/document workflows; qualify actual tenant/modules/permissions/formal transactions; appointment-mandated alternatives/bridges require one authoritative mapping. Basis: Retains office ACC method without assuming configured capability A03, G-C.
ACC/BIM 360 names do not prove identical capability; confirm actual modules and bridge transaction authority.
Process Management: The processes governing the use of the CDE are detailed throughout this BEP. All users shall adhere to the workflows defined in Section 5 (BIM Collaboration) and the standards defined in Section 8 (Standard Methods & Procedures).
The CDE serves the following key functions for the project:
Provides a centralized and secure repository for all project information containers, including models, drawings, and documents.
Manages the information lifecycle through the formal WIP, SHARED, and PUBLISHED states, ensuring that teams are only working from approved information.
Controls access to information through a defined roles and permissions structure.
Retains the configured audit/version/approval evidence; verify actual retention, permissions and export capability rather than claiming every platform event is unalterable.
Facilitates all formal communication workflows, including Design Reviews, RFIs, and Submittals.
After appointment confirmation, participants use the approved CDE implementation and recorded exchange routes. Test configured permissions, state transitions, recipient access and audit retention; do not infer integrity or acceptance from platform selection alone.
10 Quality Control#
10.1 Overall strategy for Quality Control#
Our overall strategy for Quality Control (QC) is proactive, aiming to ensure correctness and quality at every step of the information production cycle ("right first time"). This approach is designed to minimize errors, reduce rework, and ensure full compliance with the Exchange Information Requirements (EIR). The strategy is implemented through the office review tiers L1 discipline / L2 cross-discipline / L3 technical committee (re-affirming), framed by an author self-check before and two separate decisions after. The BIM Manager is not a review tier. The tier and issue-severity codes are held in BBM-STD-93-CODE_DICTIONARY-V0.1 §8.
Self-check (author): before synchronizing work or submitting a model for review, each author performs a self-check against the checklist in 10.2 so the work is clean, correct and compliant.
L1 discipline QC: before any model or drawing set is shared to the Shared state of the CDE, the Discipline Lead or a designated competent peer reviews it against 10.2 and the LOIN; the review is formally recorded.
L2 cross-discipline (federated) review: federate the Shared discipline models and run the qualified checking route (default Navisworks Manage; Solibri Office only where separately qualified per 9.2.1) and the IDS checks where selected (10.3); verify that required data meets the exchange's requirements.
L3 technical committee: reviews the package, residual issues and permissible dispositions before authorisation.
LAP authorisation: the LAP authorises the submission and its transition to Published with a transmittal (5.2.4).
Recipient acceptance: the appointing party or delegated recipient records the separate A/B/C decision (10.3).
All QC activities, checklists and sign-offs are logged to provide an auditable quality record under the office QMS (ISO 9001:2026; BBM-STD-68-QUALITY_PLAN-V0.3).
10.2 Quality Control checks#
The following checklist must be used by all disciplines at the self-check and L1 discipline QC before any model is shared.
A. MODEL HEALTH & PERFORMANCE#
Warnings: zero warnings from the blocking warning list WRN-01..WRN-nn (office check set, version/hash per 8.10) are permitted at share; all other warnings are logged with count and disposition and the log is submitted with the model.
Purge: Review a protected staging copy; remove only demonstrably unused/non-required content after before/after checks. Preserve templates, identifiers, property mappings and licence/provenance evidence.
Audit/recovery: Follow the tested file-based or cloud workflow for the adopted build; preserve the live central/cloud model and user changes. Do not apply blanket detach/audit/compact operations to active shared work.
Links: All unnecessary or unresolved links (CAD, Revit, etc.) must be removed.
B. STANDARDS COMPLIANCE (BEP & EIR)#
Project Origin: The model must be correctly aligned with the shared coordinate system. No elements should be modelled far from the origin.
File Naming: The model file name must comply with the convention defined in Section 8.3.1.
Element Naming: All project-specific families, views, sheets, and systems must comply with the established naming conventions.
Templates: The model must have been created using the correct, approved project template.
C. GEOMETRIC ACCURACY & COORDINATION#
Internal Clashes: The model must be free of duplicate or overlapping objects within its own discipline (e.g., a pipe running through another pipe in the same model).
Visual Check: A 3D visual inspection must be performed to ensure the model represents the design intent and that there are no visibly disconnected or floating elements.
Level of Information Need (LOIN): All elements must be modelled to the geometric and informational level required for the current project milestone.
D. DATA INTEGRITY#
Required Parameters: All elements must contain the required project parameters as defined in the approved project dictionary (8.6 / BBM-STD-72-PARAMETERS_AND_CLASSIFICATION-V0.2).
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.
Spatial Data: All rooms and spaces must be correctly defined with the proper names and numbers as per the architectural plans.
Use the model QC checklists in BBM-STD-68-QUALITY_PLAN-V0.3.
10.3 MEASURABLE EXCHANGE ACCEPTANCE AND RECEIVING TEST#
Use ISO 19650-4:2022 exchange decision principles. Producer checks, task-team sharing approval, LAP submission authorisation and recipient acceptance are separate records attached to exact information identities; design/authority approval remains with its appointed competent authority. Native editable, IFC, PDF and structured data/document sets all follow this gate.
Native and open/data/document outputs converge on the same intended-use checks, authorisation and receiving decision.
| Acceptance rule / scope | Required result / recommended local value | Evidence / owner |
|---|---|---|
| ID-01: identity and metadata | All submitted containers have approved unique ID, revision, immutable version, state/suitability, intended use and transmittal | Full manifest/code-list check; IM |
| NEED-01: applicable mandatory information | 100% of mandatory geometry/data/document obligations valid for the agreed object/use scope; no averaging away failure | Full applicable property population plus scoped geometry/document checks; task-team reviewer |
| GEO-01: coordinates/units | Approved survey-purpose control/transform tolerances, units and elevation match actual receiver | Independent native/export/receiver point comparisons; coordinate owner and receiver |
| OPEN-01: open-schema/profile checks | Prescribed schema/profile/settings; schema/normative-rule validation and IDS checks where selected; approved required-object counts/mappings | IFC file validated with the buildingSMART IFC Validation Service (or a qualified equivalent, tool and version recorded) for schema/normative rules, then an IDS 1.0 audit for information requirements (checker and version named), in the sequence and record of BBM-STD-89-LOIN_TO_IDS-V0.1 §5 (one IDS file per exchange, §3); header/preset/hash, mandatory property/count/exclusion report; checker |
| NATIVE-01: native intended use | Named receiving build opens required set/links and performs any agreed edit/handoff use without data loss | Actual build, test actions, source/result versions; native receiver |
| INT-01: interfaces and safety | Required hard/access/safety issues resolved/retested; only permissible residual scope expressly approved | Pair-specific rules, BCF disposition/retest, competent design/safety review; coordinator/designers |
| DOC-01: drawings/documents | Required sheets, titles, revisions and source values coherent; legible output and required supporting evidence | Full identity/field checks; representative sheet/geometry review plus all high-risk items; discipline lead |
| ASSET-01: asset ingestion | Required AIR keys/relationships/values/docs valid; target import and changed/retired/replacement asset tests pass | Known-data comparison, import log, accessible O&M/HSI links and operational acceptance; FM receiver |
| SEC-01: protected distribution | Approved role permissions, allowed/denied checks, permitted-use rights and retention controls effective | Security/rights annex and tests; security/contract owners |
| PERF-01: practical use | 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. Decision (BIM Manager, 2026-10-14): Treat 300 MB as performance investigation/splitting trigger only; measure actual hardware/network/workload and preserve IDs, ownership, federation and receiver use when splitting. Basis: Size alone is not exchange acceptance or a universal limit P02, S04. | Timed representative test with size/element count/device/network/build; technical lead |
A schema pass checks its declared scope; IDS 1.0 checks information requirements within its scope and does not prove all geometry, access, design/code or contractual obligations. Validate the IDS file itself and retain applicability/requirement IDs and known pass/fail fixtures. A spot-check of a few required properties cannot demonstrate whole-population mandatory completeness. Document approved sample scope for geometry/visual review; always include safety-critical and changed high-risk items.
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.
The receiving-test scenario is synthetic and NOT EXECUTED: three rooms, two distinct Asset_ID equipment records, one access obstruction and one missing mandatory classification. Receiver must detect both failures and preserve keys/relationships/units/document access. Correct source revision and retest exact set, then test replacement/retirement and operational custody; save expected/actual evidence and actual decision.
| Test record | Exact source / export / configuration identity | Required checks / expected values | Actual observed result and method | Receiver/tool/build/date | Failure / correction / retest | Decision / intended use |
|---|---|---|---|---|---|---|
| [MOB or EX test ID] | [container/revision/CDE version, native/export/preset/IDS hashes] | [rule IDs, counts, coordinates/units/properties/docs and sample scope] | [measured values, logs, pass/fail/blocked] | [actual receiver and full build/configuration] | [failed identity, action owner/due date, new result] | [LAP authorisation and separate recipient accept/conditional/reject, limitations] |
Accept only the demonstrated intended use. Conditional acceptance requires defined non-blocking comments, owners/dates and authorised permitted use; missing mandatory safety/identity/required data or failed intended-use tests require rejection/correction/retest. Keep failures and rejected versions; issue new controlled revisions and replacement transmittals. Scope rights, authority and liabilities under 1.7–1.8 remain contractual matters.
10.4 PROJECT SECURITY, SAFETY AND RISK ASSURANCE#
Bind the BBM-STD-01-MANUAL-V0.5 §9.4/§12.5 procedures to actual project roles and requirement IDs. ISO 19650-5:2020 and ISO 19650-6:2025 supply the lifecycle security/safety basis; security triage and the security management plan are owned by BBM-STD-87-SECURITY_MANAGEMENT-V0.1 and health and safety information by BBM-STD-88-HEALTH_AND_SAFETY_INFORMATION-V0.1. Keep sensitive risk/survey/security details private; records are distributed proportionately to authorised recipients.
| Register / actual owner | Required project fields | Review and release gate |
|---|---|---|
| Decision (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 and consequences by dataset; access/distribution; supplier obligations; retention/legal holds/disposal; induction; incident route; allowed/denied test evidence | Before access, each milestone and changed team/tool/scope; incident containment/evidence and authorised notifications |
| Decision (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. | Hazard/cause/consequence/activity; object/location; source revision/uncertainty; controls; competent reviewer; residual action owner; exchange/recipient acknowledgment | At design/field/operational change and handover; mandatory unresolved safety information blocks affected release |
| Decision (BIM Manager, 2026-10-14): LAP/task leads own information risks and review resources/dependencies/requirements/tools/security/safety before commitment/mobilisation/exchange and material change. Basis: Risk ownership follows actual delivery functions G-E, G-F. 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. | Cause→event→consequence; resource/dependency/requirement/tool/security/safety category; evaluation method; mitigation/owner/date; residual decision; review trigger | Before plan commitment/mobilisation/exchange; escalate risks threatening schedule, integrity or safety |
| Risk / HSI ID | Requirement, location/object and source revision | Cause/event/consequence and uncertainty | Control / action owner/date | Residual assessment / competent authority | Exchange / receiving acknowledgment / next trigger |
|---|---|---|---|---|---|
| [ID] | [EIR/AIR, model/doc version and stable IDs] | [recorded assessment, evaluation method] | [preventive/corrective action and source evidence] | [residual decision, role/date, allowed use] | [EX ID, evidence, recipient/date, update owner] |
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.
Competent design/code checks remain separate. Transfer residual-risk custody/updates at handover; an export or generic waiver does not close them.
10.5 DEVIATION AND REVIEW COMPLETION RECORD#
| Deviation ID | Requirement / rule / affected containers | Reason and alternative evidence | Impact / residual risk / owner | Required approval and permitted use | Expiry / retest / resulting BEP-plan revision |
|---|---|---|---|---|---|
| [ID] | [binding requirement and exact versions] | [clarification or proposed alternative] | [schedule/resources/security/safety/rights] | [appointment authority; pending/approved/rejected] | [date/trigger; evidence and change IDs] |
No departure from a binding requirement is approved merely by adding a row; mandatory legal/safety obligations are not waived by BIM management. Separate decided office defaults from signed project decisions.
| Research / gap gate | Revised content and forms | Editorial result |
|---|---|---|
| T01.1 proposed vs confirmed | 1.1 states/revision record; 6.1.1 confirmation and mobilisation | Present; actual project decisions pending |
| T01.2 use/objective/producer/recipient/exchange | 3.2.1 selected-use worksheet; 6.6 response register | Present |
| T01.3 federation/coordinates/tools/formats/checks | 7.4 profiles; 8.2/8.5/8.6/8.12; 9.2.1 and 10.3 | Present; installed/receiving builds explicitly require actual evidence |
| T01.4 responsibilities/plans/mobilisation/deviations | Separate 6.2/6.2.1 matrices; 6.3/6.4 container schedules; 6.1.1 MOB tests; 10.5 register | Present; no executed pilot claim |
| T01.5 measurable receiving acceptance and controlled revision | 1.1; 5.2.4; 10.3 rule/test/decision forms | Present |
| P1 bundled O05 gap | Native status corrected; ISO 7817-1:2024; pseudo-TIDP separated; contract-rights schedule; same naming register as Manual | 1/1 content repaired |
| P2 bundled O05 gap | Frozen exact candidate builds/profiles; actual-build/test gates; purpose-led LOIN including docs; receiving and mobilisation forms/known-fault test design | 1/1 content repaired; operational evidence pending |
| P3 reusable use/exchange worksheets | Fresh synthetic 3.2.1/6.4/6.5/10.3 forms | Included |
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.
Companion office choices are recorded in BBM-STD-11-DECISIONS-LOG-V0.2; actual project activation/rights/tool-test evidence remains separate. O3 files and guide outputs are preserved.
Drafting crosswalk items C01–C12 (closed; decisions in BBM-STD-11) and C14–C19 are addressed where they affect BEP requirements and methods: appointed roles/requirements, coherent naming/state/property rules, real plans, source-qualified coordinates/stages/tools, private custody, practical competence, legal interface, safety checks, controlled family/library use and checked documentation. Corporate/contact and benefit claims remain subject to their own evidence; no blanket certification or national authority mandate is asserted.
References#
The office research record (14 October 2026, re-checked for V0.5 on 2026-11-04) supplies the following planning authority and editions. The UK BIM Framework was renamed the IMI Framework in May 2025 (https://ukbimframework.org/resources/, checked 2026-11-04); its Guidance Parts A–F below are archived editions. No unverified normative clause is cited. Public scope/status and archived guidance do not establish licensed-clause compliance, project installation or legal enforceability. Obtain adopted standards and binding appointment/authority requirements before a compliance claim.
- 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; BCF-XML v3.0 "Final version of BCF 3.0" published 2021-06-18; BCF 2.1 (2017) fallback. BCF-XML release; BCF-API releases. Checked 2026-11-04.
- S14 — BS 1192-4:2014 — Fulfilling employer's information exchange requirements using COBie. BSI; 2014; withdrawn 2022. 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 https://nibs.org/nbims/v3/cobie/2-7, checked 2026-11-05); COBie 2.4 is in NBIMS-US V3. Publisher source; COBie v3 draft. Checked 2026-11-04.
- 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 (repository tag v1.0.0). Publisher source. Checked 2026-11-04.
- S21 — RIBA Plan of Work 2020. Royal Institute of British Architects; 2020. Publisher source.
- S23 — NBIMS-US v4 — BIM Execution Planning: Foreword. NIBS; v4; undated. Publisher source.
- S35 — AEC (UK) BIM Technology Protocol. AEC (UK) initiative; v2.1, June 2015; historical technology guidance predating ISO 19650, used as a practical benchmark for view/sheet naming. Release announcement; document index.
- S36 — CIC BIM Protocol — Second Edition. Construction Industry Council; 2018; legacy (PAS 1192 era), historical context only. Publisher source.
- S37 — Information protocols supporting delivery and operational phases — Guidance. IMI Framework (formerly UK BIM Framework); ed.3, August 2022; Information Protocol template for BS EN ISO 19650-2 Ed 6 at https://ukbimframework.org/resources/ (checked 2026-11-04). Publisher source.
- G-A — Guidance A — The information management function and resources. IMI Framework (formerly UK BIM Framework), archived edition; ed.2, February 2021. Publisher source.
- G-C — Guidance C — Facilitating the CDE workflow and technical solutions. IMI Framework (formerly UK BIM Framework), archived edition; ed.1, September 2020. Publisher source.
- G-D — Guidance D — Developing information requirements. IMI Framework (formerly UK BIM Framework), archived edition; ed.2, February 2021. Publisher source.
- G-E — Guidance E — Tendering and appointments. IMI Framework (formerly UK BIM Framework), archived edition; ed.2, February 2021. Publisher source.
- G-F — Guidance F — About information delivery planning. IMI Framework (formerly UK BIM Framework), archived edition; 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.
- V04 — Whole life carbon assessment for the built environment. Royal Institution of Chartered Surveyors; 2nd ed., September 2023; version 3 August 2024; effective July 2024. Publisher source.
- V06 — ISO 22057 — Data templates for the use of EPDs in BIM. ISO; 2022, ed.1; published, revision underway. Publisher source.
Sources added for V0.5 (all checked 2026-11-04):
- U01 — Dubai Municipality circular 9-1-2 (13 Oct 2023), Open BIM submission with new building permits from 1 Jan 2024. DM PDF.
- U02 — Dubai Municipality circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026), BIM with building permits and alterations. DM PDF.
- U03 — Dubai BIM Standard and portal (Version 1.4, package read 2026-11-05; re-check at project start). https://buildindubai.gov.ae/bim; https://api.buildindubai.gov.ae/assets/BIM/Documents/DubaiBIMStandards.zip.
- U04 — DM Administrative Resolution No. 225 of 2024 (13 Aug 2024) amending building specifications in the Dubai Building Code (Decree 45/2021). DM page; laws and orders.
- U05 — Dubai Law No. 3 of 2026 Concerning the Quality and Safety of Buildings (issued 27 Feb 2026). Dubai Legislation Portal.
- U06 — UAE Fire & Life Safety Code of Practice, September 2018 edition. Civil Defence page.
- U07 — Abu Dhabi International Building Codes, 2013 edition (Executive Council Resolution 7C 26/2013, effective 1 Oct 2013). DMT ADIMC-2013.
- U08 — DMT/ADM BIM Code of Practice (Oct 2020) and infrastructure guidelines. DMT PDF.
- U09 — Estidama Pearl minimums (DMT news, 8 Jan 2025). DMT.
- U10 — Al Sa'fat Dubai Green Building System, 2nd edition (Jan 2023). DM.
- U11 — EPSG:3997 WGS 84 / Dubai Local TM. EPSG mirror; Dubai vertical datum DMD: FIG 2011 paper by DM authors; Abu Dhabi vertical datum Ras Ghumays: EPSG datum 1146.
- U12 — Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (effective 2 Jan 2022, Active). UAE Legislation.
- U13 — Autodesk previous-versions list (Revit 2024–2027 supported) and support lifecycle. Previous versions; lifecycle; Revit 2027 updates; revit-ifc releases.
- U14 — buildingSMART IFC Validation Service. Service.
- U15 — ISO 19650-1 revision status: ISO/DIS 19650-1 ed.2 at stage 40.93. ISO; ISO 19650-2 revision at stage 40.93: ISO.
- U16 — ISO 29481-1:2025 ISO; ISO 29481-3:2022 ISO; ISO 21597-1:2020 ISO, ISO 21597-2:2020 ISO; ISO 12006-3:2022 ISO.
- U17 — ISO/IEC 27001:2022 + Amd 1:2024 ISO; ISO 13567-1/-2:2017 ISO, ISO; ISO 128-1:2020 and ISO 7200:2004 ISO.
- U18 — IMI Framework resources (renamed from UK BIM Framework, May 2025; Information Protocol template Ed 6). Resources.
Supplementary exact-version checks (publisher evidence; not office adoption):
- Autodesk, Revit 2025 Product Updates, 2026 update listing. Release/build register.
- Autodesk, IFC Exporter 25.4.40 for Revit 2025, 2026. Official release.
Annex W2 A1 Scope and retained authority#
This annex adds tender response, confirmation, capacity, mobilisation and delivery-risk forms while preserving the existing post-appointment procedures, especially sections 6.1.1 and 10.4. It was introduced in V0.4 (body unchanged from V0.3, SHA-256 of V0.3 7764180236bc10183e4754ebd67882be0ae07363ad0ca1e02aada61d5a44b6c3); V0.5 applied the corrections listed in the Revision History. Use the editable annex forms, EIR/LOIN 54, roles 55, protocol interface 56, register 51 and current MIDP/TIDP. No parallel BEP, risk scale or mobilisation test numbering is established.
Prospective LAP coordinates the tender response; actual LAP confirms the agreed delivery-team plan; task teams commit their own TIDPs and competence/capacity; delegated recipients accept information within scope. Contract award, office draft approval, a RACI cell or a software installation does not establish any of these decisions. Actual holders, appointments, dates, legal incorporation and authority remain pending. These forms support technical/commercial owner review and give no operative legal advice or fee information. ISO 19650-2:2018 clauses 5.3.2–5.3.7, 5.4.1/2/4/5 and 5.5 are the public-guidance reading pointers; exact licensed conformity still requires review.
Annex W2 A2 Filled pre appointment response#
Tender particulars records appointment/tender IDs, EIR/LOIN and protocol revisions, purposes, boundaries, milestones, parties/functions, information standard/methods, rights/security, submission requirements, assumptions and clarification/departure decisions. Every EIR row receives Conform/Clarification/Departure with proposed method, deliverable, accountable function, evidence and decision. Silence cannot become compliance; a BEP proposal cannot amend an upstream requirement. Keep EIR-007 operational AIR allocation separate from EIR-011 delivery coordination.
The synthetic SYN-APP01/SYN-P001 replacement-design response retains BBM-STD-54's EIR-011-G/A/D and EX- deliveries DEL-SYN-ME01/02/03. Proposed production uses spatial/access coordination, equipment selection/service-planning and design-basis review. Produce model/IFC, itemised CSV/PDF schedule and design/access note from one approved snapshot using the exact registered profiles. BBM-STD-54's candidate dates and source scopes are scenario particulars only; actual commitments are not invented here. Known-value AHU-001/VLV-001/VLV-002 records, access-envelope uncertainty and permitted-use boundaries stay with that EIR/LOIN baseline.
Tender response proposes a supported Revit release created by upgrading the office template, with its recorded qualified build and IFC exporter, only for qualification, retaining any appointed mandated build until approved change. Source/native/exporter/preset/checker/receiver hashes/builds, dictionary/GUIDs, actual surveyed CRS and access remain unverified. CL- requests receiving-build/profile confirmation. DEV- proposes omitting the required note; the worked scenario rejects it because EIR-011-D would be absent. Both are synthetic dispositions, not real contract decisions. Record alternative method, downstream schedule/security/rights impacts and decision authority before any accepted departure takes effect. Assumptions expire at clarification/appointment/scope change; unknown evidence holds affected readiness.
Annex W2 A3 Transition to confirmed post appointment plan#
The Confirmation form joins actual appointment/EIR/protocol, response dispositions, named delegated role allocations, detailed production responsibility matrix, committed TIDP rows and coordinated MIDP baseline, exact standards/methods/LOIN/coordinate/tool/export/receiver/security annexes and risks. Record one actual LAP confirmation decision ID/date/scope, task-team commitments and appointing-party review/acceptance where the appointment requires it. A hypothetical label Confirmed is prohibited without this evidence.
Transition records map each tender assumption/exception to agreed value, source/delegation and exact affected version. Proposed changes use one ChangeID across BEP, EIR/LOIN/profiles, roles, TIDP/MIDP, risks and recipient notices. Preserve tender/previous versions and the decision trail; never overwrite issued baselines. Confirmation establishes the agreed plan; mobilisation release additionally needs actual people/tool/method tests. The synthetic form therefore remains Proposed/Hold with blank actual signatures/acceptance.
Annex W2 A4 Capability capacity and improvement#
Assess capability against each actual task and format, using a practical representative artifact, independent assessor and declared scope. Evidence includes competent production/checkers, native/export/receiving methods, CDE/security induction and corrective/retest ability. Separately record capacity by person/function/calendar window: available uncommitted hours, required production/review hours, conflicting commitments, deputy and dependencies. Attendance/certificates alone do not prove capability or availability. Record actual confidential holders in the Directory; publish role labels only.
Synthetic week 2026-11-16..20 requires 48 producer hours and 12 checker hours; uncommitted capacity is 40 and 6, leaving gaps 8 and 6. The improvement exercise proposes an additional competent producer 8 h and checker 6 h, with independent assessment and source-calendar reservation before commitment; it does not invent actual staffing. Revised capacity would be 48/12 only after those reservations, with no overlap/double-booking. The Capacity sheet preserves before/required/addition/after values; Improvement actions states owner, evidence needed, due date, reassessment and blocked delivery. Readiness remains Hold until the owner verifies actual people/calendar/evidence. Failed reassessment triggers scope/resource/plan correction, not a waiver of independent checking.
Annex W2 A5 Mobilisation inputs failure correction and retest#
Reuse MOB-01..07 from 6.1.1. MOB-01 proves allowed/denied CDE read/write/upload/download routes with current role/configuration; naming fixtures also validate the eight-token identity and actual revision/suitability metadata. MOB-02 proves isolated native open/edit/handoff with agreed full builds and working ownership. MOB-03 proves coordinates/north/units and mandatory property/format persistence from approved source/export; MOB-04 proves actual receiving use, data/document access and deliberate fault detection; MOB-05 proves BCF issue/change/retest identity; MOB-06 proves recovery of known source/identity/access; MOB-07 proves asset create/change/retire imports and relationships/document links. Freeze source/fixture IDs/revisions/hashes, tool/OS/plugin/configuration/preset/receiver builds, roles/rights and expected known values for each actual test.
The synthetic exercise failure MOB-03-F01 uses the BBM-STD-63 wrong-unit case (mm treated as m). Its expected observation is a 1000-fold offset and a Hold. Proposed correction selects the approved unit transform and regenerates source/export; expected retest MOB-03-R01 compares both independent horizontal controls/elevation/north and all affected mandatory data in MOB-04 receiving. Separate Exercise fields label these as simulated expected outcomes. Actual failure/retest rows remain Not executed until real evidence exists; no simulated Pass is put in a native Actual result cell. Do not replay an uncertain transfer without checking actual delivery/receipt first.
Actual failure record: TestID/run ID, exact failed source/build/configuration, expected vs observed, error/evidence hash/date, cause, consequence, blocked scope and action owner/due date. Retest record: correction ChangeID/new source/configuration hashes, original RunID link, affected regression tests, measured result/operator/date, independent reviewer and scoped release/recipient decisions. Keep both failed and retested evidence. Timeouts, screenshots of forms and file presence are not readiness. Do not discard an original failed run when a later one passes.
Annex W2 A6 Delivery risk scoped confirmation and review#
Retain 10.4's information-delivery risk method 1–5 likelihood x 1–5 impact; scores 15–25 escalate for competent residual disposition, and any unresolved mandatory failure holds affected release regardless of score. Likelihood labels for the synthetic exercise are 1 Rare, 2 Unlikely, 3 Possible, 4 Likely, 5 Almost certain; impact 1 Minor internal correction, 2 Task disruption, 3 Milestone at risk, 4 Required exchange failure, 5 Critical security/safety/integrity consequence. Project owners must define their assessed basis/exposure and calibrate labels; these are not statistical probabilities or specialist safety/structural risk ratings.
Risk worksheet separates cause/event/consequence, requirement/exchange, initial likelihood/impact/evaluation evidence, mitigation/action owner/due date, residual evaluation/evidence/decision owner, mandatory-failure flag and review trigger. RISK--01 uses unsupported receiver -> lost property -> failed EIR-011-A, initial 4x4=16, mitigation actual MOB-03/04 known-value and wrong-unit tests; proposed residual 2x4=8 remains unaccepted until measured evidence. RISK--02 covers capacity gaps; RISK--03 covers unauthorised distribution and links the restricted security owner, not sensitive details in a general tender. Risk owner and competent residual accepting authority are distinct fields.
Review at tender/appointment, before mobilisation/commitment/exchange, changed team/tools/requirements/source/dates, failed/repeated test, incident and operational handover. Risk actions propagate by ChangeID to plans and notices. The Readiness form enumerates exact permitted scope and excluded/blocked scope, each required test/dependency, LAP decision, recipient exchange decision and date/expiry. Accept only actual scoped confirmation plus actual failed/corrected/retested mobilisation evidence where a failure occurred. No blank or synthetic row grants release. This V0.5 pack is editorially usable; actual project confirmation, mobilisation, capacity reservation, risk acceptance and recipient operation are Not executed/Hold.
W2 annex references#
- ISO 19650-2:2018 catalogue, reading pointers 5.3.2 pre-appointment plan, 5.3.3/4 capability/capacity, 5.3.5 mobilisation, 5.3.6 risk, 5.3.7 response, 5.4.1 confirmation, 5.4.2 responsibilities, 5.4.4/5 delivery plans, 5.5.1–3 mobilisation. IMI Framework (formerly UK BIM Framework) Guidance Part 2, edition 5 per the archived file name provides public clause context (archived edition); Guidance E ed.2 tender/appointment guidance (archived edition), checked 2026-10-16; framework renamed IMI Framework May 2025 (https://ukbimframework.org/resources/, checked 2026-11-04). Paraphrased controls, not copied paid text or licensed conformity audit.
- ISO 19650-1, -3, -5 for requirement/lifecycle/security context; ISO 7817-1:2024 current LOIN concepts, BS EN 17412-1:2020 predecessor with controlled appointed-edition changes only.
- Abu Dhabi building work: DMT/ADM BIM Code of Practice, Oct 2020; infrastructure only: ADM Documentation Guidelines for Infrastructure v1.0, October 2020, sections 3.3/4.2/4.3 and the Infrastructure BIM Object Catalogue v2.0 (May 2021); DDA current service; DM circular index. Appointment/jurisdiction scope confirmed through BBM-STD-57-CODES_AND_SUBMISSIONS-V0.2 and BBM-STD-85-UAE_AUTHORITY_SUBMISSIONS-V0.1; no national BIM mandate or invented service timing. Checked 2026-11-04.
- NIBS NBIMS-USv4, a comparison framework referenced by the writing plan, not adopted as a competing BEP; actual tender resources remain the office's single 54/55/56/BEP/MIDP/TIDP chain. Publisher full-page availability unverified in this session; no new normative assertion relies on it.
Document history
| GENERAL SUBMITTAL | GENERAL SUBMITTAL | GENERAL SUBMITTAL | GENERAL SUBMITTAL |
|---|---|---|---|
| PROJECT LOCATION | CLIENT: | ||
| PMC | LDC/CONSULTANT: | ||
| COST CONSULTANT | CONTRACTOR: | ||
| REV | DATE | DESCRIPTION | ORIGINATED |
| --- | --- | --- | --- |
| V0.6 | 2026-11-05 | Standard watch no. 1: 1.12 ISO 12006-2 confirmed 2020 (to be revised) and Dubai Law No. 3 of 2026 row cites DM circular 11-9-1 of 2026; S15 COBie V3.0 published 2023; U03 Dubai BIM Standard 1.4 | Private review draft; actual approval pending |
| V0.5 | 2026-11-04 | closure + cross-doc pointer pass, rows: Dubai permit BIM use and EX-P06 profile; CRS/datum defaults and IFC georeferencing check; UAE code instruments and Code Validation; IMI Framework naming and protocol; LAP ownership of BEP/capability/MIDP; formal delivery wording; Classification_Code canonical and canonical parameter IDs/ISO 8601 dates; sustainability-rating lead and evidence; ADM BIM scope; applied-standards register with editions and "used in"; 1.10 purpose-led modelling extent; Revit lifecycle row; A/B/C gate letters; Directory-based contacts; PDPL; ISO 19650 vocabulary; Solibri Office/QC tiers; "construction issue" wording; RIBA 2020 meeting stages; Manual/72/68/56 links; hardware column; role definitions; objectives, model checker, blocking warnings, OPEN-01; LOIN example columns; annex scope wording; S35 reference; heading numbering; decision/source links re-pointed to BBM-STD-11 V0.2 and the References list; COBie default per + template alignment (..148) + folder names without dots | Private review draft; actual approval pending |
| V0.4 | 2026-10-16 | W2 tender, confirmation, capacity, mobilisation and delivery-risk annexes; retained V0.3 body | Private review draft; actual approval pending |
| V0.3 | 2026-10-14 | Section-by-section correction of rights interface, states, LOIN, delivery plans, naming and measurable exchange assurance | Prepared for office review; approval pending |
| V0.1–V0.2 | — | Prior revisions; held read-only in the office archive | Superseded |
Personal contact details are held only in the restricted Directory (BBM-STD-03-DIRECTORY-V0.3); BEP contact tables carry role, Directory MembershipID and role mailbox (appointment contact view) only.
DOCUMENT AUTHOR
| ROLE | DIRECTORY MEMBERSHIP ID | ROLE MAILBOX (APPOINTMENT CONTACT VIEW) |
|---|---|---|
ACKNOWLEDGED BY
| ROLE | DIRECTORY MEMBERSHIP ID | ROLE MAILBOX (APPOINTMENT CONTACT VIEW) |
|---|---|---|
The BIM Execution Plan (BEP) is a controlled document and shall be reviewed, approved and distributed under controlled conditions.