ArchHubBABOOMDownload

Organisational Information Requirements

BBM-STD-02 · V0.4 · Use this OIR to identify why information is collected, who uses it, what decision it supports and how reliable it must be.

Download WordAll standards

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

1 Introduction#

Scope and purpose#

Use this OIR to identify why information is collected, who uses it, what decision it supports and how reliable it must be. It covers strategic business operation, portfolio planning, delivery oversight and the use/maintenance of asset information. It does not demand a model for every decision. A checked report, structured register, drawing, model or combination may satisfy a requirement if its decision criteria are met.

The standards basis is ISO 19650-1:2018 (concepts and principles; the ISO/DIS 19650-1 second edition is under development and not in force), ISO 19650-2:2018 (delivery; ISO/DIS 19650-2 is at stage 40.93 and not in force), ISO 19650-3:2020 (operation), ISO 19650-4:2022 (exchange checks), ISO 19650-5:2020 (security) and ISO 19650-6:2025 (health and safety information). ISO 7817-1:2024 supplies the level of information need approach. Requirements development follows IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance D, edition 2 (2021, archived edition). Property and code-list governance follows ISO 23386:2020 and ISO 23387:2025, and classification follows ISO 12006-2:2015 with Uniclass 2015 (office baseline: July 2026 release; the release is frozen per project). Information security follows ISO 19650-5:2020 with ISO/IEC 27001:2022 (+ Amd 1:2024) controls where the office ISMS applies; the security triage and plan are in BBM-STD-87. These are scope-level references; licensed clause compliance has not been audited. The office review/change procedure is informed by ISO 9001:2026 (edition 6, published 16 September 2026, replacing ISO 9001:2015), without claiming certification or an audited transition from an earlier edition.

Where the office or the appointing party operates an asset management system, OIR for asset and portfolio decisions (sections 4.2–4.5) trace to its asset management objectives and strategic asset management plan (SAMP) under ISO 55001:2024 (edition 2; ISO 55001:2014 is withdrawn). ISO 19650-3 assumes this context; the OIR does not create an asset management system where none exists.

2 General: objectives and the requirements hierarchy#

2.1 Vision, mission and values#

Decision (BIM Manager, 2026-10-14): Adopt the objective: make timely, traceable decisions using minimum sufficient checked information; use OBJ-01 safety, OBJ-02 environment, OBJ-03 investment/resources, OBJ-04 lawful dependable operation and OBJ-05 space/capacity only where scope applies. Basis: OIR support authorised business decisions, not invented corporate mission claims G-D, S01.

The office director reconciles applicable needs with actual business strategy; this objective does not assert a new corporate mission.

Objective IDOffice business outcomeDecision consumerDecision supportedAM objective / SAMP reference (ISO 55001), where an AM system applies
OBJ-01Protect people through usable safety informationSafety duty holder and decision authorityAct on a significant risk before design, work or operation proceeds[SAMP objective ID or N/A with reason]
OBJ-02Reduce environmental impact with traceable evidenceSustainability decision authoritySelect an option and monitor its consequences[SAMP objective ID or N/A with reason]
OBJ-03Allocate capital and resources on a comparable basisInvestment authority / office directorFund, defer or stop an option[SAMP objective ID or N/A with reason]
OBJ-04Sustain lawful, dependable portfolio operationAsset/portfolio authority where appointedPrioritise compliance, maintenance and operational interventions[SAMP objective ID or N/A with reason]
OBJ-05Match space and capacity to business demandPortfolio and service-planning authorityReconfigure, retain or change capacity[SAMP objective ID or N/A with reason]

2.2 OIR, AIR, PIR and EIR#

OIR describe organisational decision needs. Asset information requirements (AIR) define information required for managing/operating assets. Project information requirements (PIR) define information supporting project decisions. Exchange information requirements (EIR) specify information for each appointment and its exchanges. OIR inform AIR and relevant PIR; AIR and PIR inform appointment-specific EIR. This is a linked derivation, not a rule that every OIR row must generate all three documents.

Downstream documents: BBM-STD-52 AIR, BBM-STD-53 PIR, BBM-STD-54 EIR and LOIN, BBM-STD-10 BEP V0.5, MIDP V0.3 and TIDP V0.3. The AIR-nnn, PIR-nnn and EIR-nnn IDs in the derivation cells of sections 3–4 resolve in BBM-STD-52, BBM-STD-53 and BBM-STD-54 respectively; publication of LOIN rows as IDS files is in BBM-STD-89.

The BIM execution plan (BEP) responds to applicable exchange requirements; task information delivery plans (TIDPs) plan task-team information, and the master information delivery plan (MIDP) coordinates them. A RACI allocates activities but does not replace delivery plans. The project information model (PIM) is the managed delivery information; selected checked information contributes to the asset information model (AIM) for operation. Operational EIR can update the AIM at trigger events, not only at initial handover. AIR is never an alternative acronym for AIM.

Decision trace: organisational needs inform asset and project requirements, then appointment-specific exchanges and recorded decisions.

2.3 Requirement record: fields to complete#

Decision (BIM Manager, 2026-10-14): Use stable OIR-nnn, AIR-nnn, PIR-nnn and EIR-nnn IDs with separate revision, derivation links and preserved issued aliases; these are requirement keys, not filename tokens. Basis: Requirement lineage must survive change and appointment conventions G-D.

An appointment-specific convention uses a controlled alias/change map; issued requirement IDs are preserved.

Exchange sub-IDs use one grammar across this OIR, BBM-STD-54 and BEP Annex W2 A2: EIR-nnn-X, where X = G (geometry), A (alphanumeric information) or D (documentation), and exchanges are EX-nnn (EX-SYN-nn in synthetic examples). Numeric suffixes such as EIR-007-01 are retired; any issued numeric alias is mapped once in the alias/change map.

FieldDefinition / completion rule
ID, revision, statusUnique stable ID; draft/approved/superseded status with approval evidence
Objective and decisionObjective ID, specific decision/question and consequence of inadequate information
Scope / consumerPortfolio/project/asset set, exclusions, appointment role and authorised decision consumer
Requirement owner / deputyFunction and confirmed person accountable for definition, currency and resolution
Information neededData fields, geometry where needed, documents, scope and source lineage; no “BIM model” alone
Source / producer / receiverAuthoritative source and revision; production, checking and receiving roles; system/profile
Frequency / trigger / deadlineReporting cut-off, submission date, decision date and exceptional trigger
Quality / check methodRequired completeness, accuracy/uncertainty, validity, currency and reconciliation evidence
Sensitivity / permissionsConsequence-based restriction, authorised audience, channel and retention schedule reference
Downstream linksAIR/PIR/EIR IDs, LOIN/exchange IDs, TIDP/MIDP references or reason not applicable
Acceptance / use recordChecker, authoriser, acceptor, result, exception authority, actual decision and date

3 Strategic business operation#

Decision (BIM Manager, 2026-10-14): Adopt OIR-001–010 with sections 3–4 owner/consumer functions, triggers and acceptance rules wherever applicable; expand into section 2.3 records and approve explicit not-applicable scope; actual holders/source systems remain activation particulars. Basis: Decision records derive relevant AIR/PIR/EIR without invented portfolio facts G-D, S03.

Owner → consumer denotes adopted functions, not confirmed staff or contractual authority. Where outside scope, record not applicable, reason and approver.

3.1 Health and safety#

Decision (BIM Manager, 2026-10-14): Adopt OIR-001: safety lead supplies significant-risk records before affected work/change and in monthly exceptions; every significant unresolved risk has owner/disposition and no safety-critical record is missing. Basis: Safety information serves affected decisions/activities S06.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-001 / OBJ-01Decide whether an affected activity may proceed. Significant-risk ID; affected asset/location; hazard, consequence, design/operational control, residual risk, action owner, review date and source revisionSafety information lead → actual safety duty holder / activity authoriserBefore affected work or change; monthly portfolio exception reportEvery significant unresolved risk has an owner and disposition; no safety-critical missing record may be hidden by a summary score. Link AIR-001 operational precautions and PIR-001 design/work decisions to EIR-001 safety exchange

Use ISO 19650-6:2025 for structured safety-information context. Information acceptance does not discharge the relevant designer's or duty holder's safety responsibilities. Restricted hazard/security information needs an authorised audience and a usable operational handoff.

3.2 Environmental management#

Decision (BIM Manager, 2026-10-14): Adopt OIR-002: environmental data owner reports energy/water/waste monthly and at meter/occupancy/boundary change; reconcile each included site to source evidence and identify missing periods/estimates. Basis: Comparable measures need units, boundaries and provenance G-D, S04.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-002 / OBJ-02Prioritise environmental actions. Energy, water and waste quantities, measurement period, units, floor-area/occupancy basis, source and limitationsEnvironmental data owner → sustainability authorityMonthly monitoring; new meter, occupancy or reporting-boundary changeReconcile each included site to meter/bill/register evidence; identify missing periods and estimates separately. AIR-002 meter/asset links; PIR-002 option comparison; EIR-002 performance report

3.3 Sustainability and carbon#

Decision (BIM Manager, 2026-10-14): Adopt OIR-003: sustainability lead reports at option selection/substitution and quarterly portfolio review; link quantities/model revision, assessment boundary/stages, dataset/EPD version and exclusions to the adopted methodology. Basis: Quantity extraction alone is not an environmental assessment V04, V06.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-003 / OBJ-02Select an option against the adopted sustainability brief. Quantities and units, assessment boundary, life-cycle stages, material/product IDs, dataset/EPD source and version, assumptions and uncertainty; applicable green-building rating system and version (Abu Dhabi: Estidama Pearl; Dubai: Al Sa'fat), statutory minimum and target level, and credit evidence IDsSustainability lead → option decision authorityAt option selection and material/design substitution; quarterly portfolio reviewEvery reported result links to a quantity/model revision and assessment version; missing data and exclusions are explicit. PIR-003 carbon option and rating-evidence decision, AIR-003 relevant operational and rating-verification records and EIR-003 assessment inputs/results and credit evidence

Follow the adopted assessment methodology. ISO 22057:2022 concerns EPD data templates; it does not itself calculate whole-building carbon. Where adopted, RICS Whole life carbon assessment, second edition (effective 1 July 2024), provides assessment context. A quantity extraction alone is not an approved carbon assessment.

Green-building ratings are statutory minima, not options: Abu Dhabi Estidama Pearl requires at least 1 Pearl for private projects and 2 Pearl for government-funded projects (DMT, 8 January 2025); Dubai Al Sa'fat (second edition, January 2023) requires Silver Sa'fa for all new buildings. Edition rows are in the BBM-STD-51 §3 edition register and requirement detail in BBM-STD-85. Rating evidence links through PIR during delivery and AIR for operational verification.

3.4 Capital investment and business performance#

Decision (BIM Manager, 2026-10-14): Adopt OIR-004 before funding, quarterly forecast and material scope/cost change with ledger reconciliation/no double-counted benefits; adopt OIR-005 monthly and before new appointments with actual capacity, plan revisions and scoped metrics. Basis: Investment/capacity need comparable baselines and full cost/resource evidence P03, G-D.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-004 / OBJ-03Fund, defer or stop an option. Base case/alternatives; capital and operating costs; benefits; programme/resource demand; risk; currency, price base, assumptions and sensitivityFinance/business-case owner → investment authorityBefore funding commitment; quarterly forecast and material scope/cost changeReconcile total to source ledger/estimate revision; distinguish forecast, committed and actual cost; no double counting of benefits. PIR-004 funding decision and EIR-004 option/business-case pack; AIR link only if ongoing asset data is required
OIR-005 / OBJ-03Reallocate delivery capacity. Appointment obligations, planned/actual resources, exchange dates, lateness, rejected packages and corrective actionsDelivery performance owner → office director / delivery authorityMonthly and before accepting a new appointmentEvery metric identifies denominator, cut-off, exclusions and source plan revision; no “95% complete” without scoped required items. PIR-005 resourcing decision and EIR-005 delivery dashboard; no automatic AIR derivation

4 Portfolio planning#

4.1 Statutory approvals#

Decision (BIM Manager, 2026-10-14): Adopt OIR-006: compliance lead verifies approvals/conditions/expiry before submission/use, at monthly expiry review and changed rules; overdue/unverified mandatory approvals hold affected decisions. Basis: Authority annex applicability and verified status establish readiness S28, G-D.

Decision (BIM Manager, 2026-10-14): Keep jurisdiction authority, building/fire code, rating and submission particulars in appointment annexes verified from current official sources for the actual UAE jurisdiction/project; core abbreviations and historic lists do not prove compliance. Basis: RESEARCH.md distinguishes local applicability and evidence limits S26, S27, S28, S29.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-006 / OBJ-04Prioritise statutory actions and decide readiness for the relevant submission/use. Applicable instrument, authority, applicability, permit/certificate ID, conditions, expiry, action owner and official evidenceCompliance lead → appointed compliance / asset decision authorityBefore submission/use; monthly expiry review; changed rule or conditionEvery required approval has verified status and conditions; overdue/unverified items are explicit blockers for the affected decision. AIR-006 certificates/renewal triggers, PIR-006 approval decisions and EIR-006 submission evidence

Maintain a project/asset jurisdiction annex using current official instruments. The office works in Dubai and Abu Dhabi; the annex for OIR-006 lists at least the instruments below. The edition, date and source-check date of each are held once in the BBM-STD-51 §3 edition register under the ED-IDs shown; the requirement detail is in BBM-STD-85.

JurisdictionInstruments to verify for OIR-006Evidence field
DubaiDM circular 9-1-2 (ED-DM-9-1-2; 13 October 2023): Open BIM submission per the Dubai BIM Standard with new building permits from 1 January 2024 for buildings over 20 floors (architectural) / 40 floors (structural), over 20,000 m² (architectural) / 30,000 m² (structural), specialised buildings and government projects. DM circular 9-1-3 (ED-DM-9-1-3; 15 January 2026, effective 1 April 2026): architectural and structural BIM with the permit for new buildings above G+12 or of 15,000 m² or more and for listed alterations, with drawings extracted from the model. Dubai BIM Standard (ED-DUBAI-BIM-STD; Version 1.4 at 2026-11-05, re-checked at project start). Dubai Building Code (ED-DBC; Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 and every later amending resolution in force at permit submission. Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (ED-DXB-LAW-3-2026; periodic inspection and certificate obligation over the asset life), applied by DM circular 11-9-1 of 2026 (ED-DM-11-9-1; 1 October 2026): a Building Quality and Safety Certificate for buildings completed 20 or more years ago, valid 10 years (under 40 years) or 5 years (40 years or more), on an engineering office's assessment against the DM technical checklist. UAE Fire & Life Safety Code of Practice (ED-UAE-FLS; September 2018 edition) plus Dubai Civil Defence amendments current at project start. Al Sa'fat second edition (ED-ALSAFAT; Silver Sa'fa minimum)Official source URL + date checked
Abu DhabiAbu Dhabi International Building Codes (ED-ADIBC): the ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04). ADM BIM Code of Practice (ED-ADM-BIM; October 2020) where the appointment or authority requires it; no universal building-permit BIM threshold was found. UAE Fire & Life Safety Code of Practice (September 2018 edition) plus ADCDA amendments current at project start (ADCDA Circular No. 3 of 2026, 12 March 2026, is reported by secondary sources; it applies from the ADCDA text obtained at project start). Estidama Pearl (ED-ESTIDAMA; minimum 1 Pearl private, 2 Pearl government-funded)Official source URL + date checked
UAE federalNo federal BIM mandate found (checked 2026-11-04). Personal data: Federal Decree-Law No. 45 of 2021 (ED-UAE-PDPL), see section 6Official source URL + date checked

Do not infer a nationwide BIM mandate from promotional material or a single appointment. The office does not select a jurisdiction by default and does not assert permission to operate: the annex is completed for the actual plot and authority.

4.2 Maintenance#

Decision (BIM Manager, 2026-10-14): Adopt OIR-007: maintenance data owner reports monthly backlog and inspection/failure/replacement/handover events; require unique Asset_ID, system/location links and safety-critical action owner/date. Basis: Operational information supports prioritisation at trigger events S03, S06.

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

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-007 / OBJ-04Prioritise work and replacement. Maintainable asset IDs, system/location, condition and inspection dates, criticality, defects, service intervals, cost, warranty and manual linksMaintenance data owner → maintenance / asset authorityMonthly backlog; inspection, failure, replacement and handover triggersUnique active asset IDs; valid system/location relationships; every safety-critical defect has an action owner/date. AIR-007 maintainable-asset data and trigger rules; EIR-007 update exchange; PIR-007 only for a related replacement project

4.3 Operations#

Decision (BIM Manager, 2026-10-14): Adopt OIR-008: operations data owner reports incident/change events and monthly service review, linking incidents to affected services/assets/current documents and reconciling source counts. Basis: Operational records remain traceable to current affected services S03.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-008 / OBJ-04Restore/adjust service and evaluate performance. Service scope, downtime/incident record, affected assets, operating limits, tested procedures and current document linksOperations data owner → operations decision authorityIncident/change driven; monthly service reviewAll reported incidents link to affected service/asset and current operating documentation; reconcile incident counts with source register. AIR-008 operating information and EIR-008 event update; project PIR only when intervention creates a project

4.4 Space utilisation#

Decision (BIM Manager, 2026-10-14): Adopt OIR-009: space data owner reports quarterly and at use/reconfiguration change; reconcile SpaceID, measurement/model revision, report uncertainty and aggregate occupancy. Basis: Space/capacity needs comparable measures and minimal personal data S03, S05.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-009 / OBJ-05Retain, reassign or change space. Stable space IDs, use, agreed area basis, capacity, observed occupancy/time period, access restrictions and model/survey provenanceSpace data owner → portfolio planning authorityQuarterly and at change of use / major reconfigurationReconcile space register to adopted measurement basis and model/drawing revision; report sample coverage and uncertainty. Use aggregated occupancy; no unnecessary individual tracking; personal data per section 6 (UAE PDPL). AIR-009 space baseline, PIR-009 options and EIR-009 space/occupancy report

4.5 Portfolio modifications#

Decision (BIM Manager, 2026-10-14): Adopt OIR-010: portfolio change owner supplies options/cost/risk and affected asset/space evidence before approval/handover and after verified completion; distinguish assumed/surveyed/designed/installed/verified information and update AIM. Basis: Changed assets/services need reviewed operational information and provenance S03, G-D.

ID / objectiveDecision and information neededOwner → consumerFrequency / triggerAcceptance and derivation (AIR → BBM-STD-52, PIR → BBM-STD-53, EIR → BBM-STD-54)
OIR-010 / OBJ-03/04/05Approve an acquisition, disposal, refurbishment or service change. Affected asset/space IDs, scope, condition, surveys, constraints, risks, options, costs, dependencies and required AIM changesPortfolio change owner → portfolio / investment authorityBefore approval; before handover; after verified completionTrace decision to option evidence; distinguish assumed, surveyed, designed, installed and verified information. AIR-010 updated operational baseline, PIR-010 change decision and EIR-010 staged change/handover exchanges

5 From requirement to usable exchange#

5.1 Worked trace: maintenance prioritisation#

Decision (BIM Manager, 2026-10-14): Adopt synthetic OIR-007/AIR-007/PIR-007/EIR-007-A/-D maintenance trace as office example; pilot a structured UTF-8 table with controlled document links and confirm actual receiver schema/build and known-record reconciliation before activation. Basis: An adopted example does not assert live holdings or successful ingestion G-D, S04.

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.

This remains a synthetic example, not a claim about office holdings. Actual EIR/profile/receiver particulars must be populated before use.

Trace elementWorked entry
Objective / decisionOBJ-04 / decide which maintainable systems need priority intervention next month
OIR-007Consumer needs asset criticality, current condition, defect severity and forecast cost, with provenance
AIR-007Asset_ID (legacy AssetID alias), SystemID, SpaceID, condition code/date, defect ID, criticality, action owner, next service date, cost/currency and linked inspection/manual
PIR-007If replacement is commissioned, compare repair/replacement options at the actual project investment gate
EIR-007-A / EIR-007-D (exchange EX-007)Maintenance task-team appointment supplies the scoped asset update and inspection evidence before the planning meeting; asset data owner is recipient
Information needGeometry: asset location/space relationship sufficient to find the item; alphanumeric: fields above with units/code lists; documentation: inspection and maintenance instruction IDs. Do not demand fabrication detail
Delivery / operationIn a delivery project, plan via BEP/TIDP/MIDP and select accepted PIM information for AIM. During operation, update the AIM on inspection/replacement triggers
Exchange profileStructured UTF-8 table plus controlled document links for the pilot; exact receiving platform, import schema and versions must be recorded before use. COBie only if the appointment requires an exact version/profile
Receiving checksCheck unique IDs, mandatory fields, permissible codes, resolvable links, agreed scope count and known-record import/reconciliation in the actual receiving system
Decision recordAcceptor records accepted/rejected scope and exceptions. Decision authority records priority, reason, date and follow-up owner

ISO 7817-1:2024 requires a purpose-led approach to information need; a stage number or bare LOD label cannot substitute for geometry, alphanumeric information and documentation requirements. IFC versions, classification releases and COBie profiles must be agreed for each actual exchange; do not upgrade existing appointments automatically.

5.2 Quality and acceptance rules#

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

Decision (BIM Manager, 2026-10-14): Apply OIR section 5.2: 100% required scope accounted for, every mandatory value valid, zero duplicate IDs, required references/codes valid, units/method/source stated, critical results traced and receiver use/permissions demonstrated; accuracy is purpose-specific. Basis: O3 mandatory acceptance covers geometry, data and documentation S04.

ISO 19650-4:2022 supports defined checks, not office-set percentages or reporting deadlines.

Quality dimensionDecided measurable ruleCheck / evidence
Scope100% of the explicitly required in-scope records accounted for; exclusions approved and listedExpected ID list versus received list, with additions/omissions
Critical information100% applicable mandatory fields valid, including every decision-critical field; other findings individually dispositionedCritical-field list fixed before exchange; field validation report
Identification / validityZero duplicate stable IDs; 100% required references resolvable and code values from the agreed listUniqueness, foreign-key, code-list and document-link checks
CurrencyReport states cut-off and source revisions; recurring report delivered within 5 working days after cut-off and before decisionTimestamp, source snapshot and late/update exceptions; urgent triggers use the affected decision deadline
Accuracy / uncertainty100% of reported measures state units, measurement/estimate method and source; numerical tolerance set to the decision's risk and receiving useReconcile critical values to authoritative records; record sampling population/method for other values. No invented universal survey or clash tolerance
TraceabilityEvery decision-critical result traces to accepted source revision and responsible ownerFollow a result back through report, query/calculation and source
Usability / securityReceiver demonstrates import/read/use and required permissions; no unauthorised sensitive contentRepresentative receiving-system test and approved distribution record

Producer checking, delivery-team authorisation and receiving/appointing-party acceptance are separate actions. Assign the actual roles from the appointment and Directory; “BIM manager” does not automatically have any of these powers. Native editable files can be controlled containers. CDE state and revision metadata plus workflow evidence govern authorisation; PDF conversion or a browser “Publish” folder does not establish acceptance.

If a mandatory check fails, reject or hold the affected exchange with a correction owner/date and resubmission reference. Record any permitted noncritical exception with scope, consequence, approving authority, expiry and compensating control. Do not waive a statutory, contractual or safety duty through an OIR exception. Keep accepted source evidence immutable; revision and archive history remain available under the approved retention schedule.

5.3 Portfolio reporting template#

Decision (BIM Manager, 2026-10-14): Issue monthly requirement-by-requirement exceptions within 5 working days of cut-off and before the supported decision; review usefulness/benefits quarterly and full OIR annually; urgent triggers follow the earlier decision deadline. Basis: Explicit timeliness/review prevents averages hiding critical exceptions G-D, S04.

Report each requirement separately; a green average cannot mask a failed critical item.

Period / cut-offOIR ID / scopeSource revision / refreshRequired / received / valid recordsCritical failures / uncertaintyDecision / action owner / due dateAcceptance / controlled link
[complete][ID; population][ledger, register or model IDs][counts and explicit denominator][IDs and consequence][actual decision or hold][acceptor, date, record]
Example only: Month 01OIR-007; 120 scoped assetsMaintenance register revision 04120 / 118 / 1162 missing IDs; 2 invalid criticalitiesHold affected priorities; owner corrects before planning meetingRejected affected scope; resubmission required

6 Responsibilities, security and controlled review#

  1. Business owner states the decision, information consumer and risk of wrong/missing evidence. Record whether the office owns the decision or responds to another party's requirements.
  2. Information management lead coordinates stable requirement IDs, dependencies, formats and source systems. Security lead assesses sensitivity and sharing consequences before collecting or aggregating data.
  3. Requirement owner works with producers and receivers to derive AIR/PIR/EIR, the information need and acceptance tests. Check that resources, timing, appointments and receiving tools can deliver the request.
  4. Producer and independent checker run the agreed checks. The authorised delivery role releases the exchange; the receiving acceptor records its scope/result. The business authority then records its actual decision.
  5. Monitor rejected exchanges, stale evidence, critical-field failures, missed decisions and unnecessary production. Propose changes with cost/benefit, security, appointment and plan impacts.
  6. Approver records the decision and effective revision. Notify affected requirement, appointment, BEP, plan, model/AIM and reporting owners; retain the previous baseline and any explicitly agreed transition. A new research edition does not silently change a contract.

Reporting and review cadence: see (section 5.3).

Review additionally on strategy change, new appointment/service, acquisition/disposal, incident, regulation or receiving-system change and failed exchange; every active requirement has deputy/review date.

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.

Retention classes and the legal-owner retention schedule are owned by BBM-STD-90.

Personal data (occupancy, contact and incident records) follows the PDPL rules in BBM-STD-90 §4. It is processed under the UAE Personal Data Protection Law, Federal Decree-Law No. 45 of 2021 (effective 2 January 2022), and any Executive Regulations listed on uaelegislation.gov.ae at project start, and under the DIFC or ADGM data protection regime where a party is established there. Each requirement record that holds personal data states the lawful basis, purpose, retention class and the data-subject request route (BBM-STD-90).

Continue proportionate sensitivity, supplier, incident and aggregation controls above; prefer aggregate measures and restricted custody for personal/security details.

7 Adoption and change register#

Adoption status: see (section 1).

Decision IDDecided value / actionDecision owner to confirmEvidence required
OIR-D01(section 2.1)
(section 3)
Office director and business ownersApproved applicable list, exclusions and confirmed decision consumers
OIR-D02(section 1)Office directorNamed holder/deputy, authority and Directory record IDs
OIR-D03(section 5.3)Business ownersCalendar, first cut-off/decision dates, resource capacity
OIR-D04(section 2.3)
(section 1)
Information leadApproved ID list, cross-reference/alias rules and controlled master location
OIR-D05(section 5.2)
(section 5.2)
Business acceptors / quality ownerScoped test criteria, exception authority and receiving-system pilot
OIR-D06(section 1)
(section 6)
Security / records ownersSensitivity, permission tests, retention/disposal schedule and incident route
OIR-D07Decision (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): Every exchange needs current EIR, verified recipient/actual acceptor, decision deadline and recorded accepted/rejected scope; verify powers through appointment and private Directory. Basis: Exchange decisions require defined requirements and empowered recipients S04, G-E.
(section 1)
Information lead / receiving asset authorityValidated derivation matrix and real receiver acceptance evidence
Change ID / dateRequirement / old revisionDecision need / reasonAIR/PIR/EIR and appointment/plan impactsCost / security / risksApproval / effective date / notifications
[complete][ID and baseline][why evidence must change][affected records and owners][assessment][authority and controlled evidence]

Release self-check and research trace#

Research / gapWhere addressedRelease evidence to record
I01.1 objectives, decisions, consumers2.1 and all section 3–4 requirement rowsConfirm scope and decision authority
I01.2 portfolio needs, responsibilities, frequency3–4, 5.3 and 6Owners, reporting cut-offs and first review
I01.3 AIR/PIR and relevant project links2.2–2.3 and 5.1Approved trace into actual exchanges
I01.4 measurable quality tied to decisionPer-row criteria and 5.2Critical-field tests and receiving pilot
I01.5 ownership and change review1, 6 and 7Approval, review calendar and change log
O03 P1 / P2; P3 reporting examplePopulated OIR, downstream criteria/owners/frequency, 5.3 exampleDraft content complete; office decisions and live evidence remain pending
Drafting crosswalk items C01/C03/C04/C07/C08/C11/C13 (closed; decisions in BBM-STD-11)2.2, 5 and 6Correct terms, separated plans/authority, private custody and decision-led metrics

References#

References used from RESEARCH.md; publisher abstracts establish edition/scope, not verified normative clauses. Guidance editions below are the researched editions, retained as guidance rather than a claim to be the latest issue. Entries were checked 2026-11-04 unless marked otherwise.

  • S01 — ISO, ISO 19650-1:2018 — Concepts and principles, 2018. https://www.iso.org/standard/68078.html
  • S02 — ISO, ISO 19650-2:2018 — Delivery phase of the assets, 2018. https://www.iso.org/fr/standard/68080.html
  • S03 — ISO, ISO 19650-3:2020 — Operational phase of the assets, 2020. https://www.iso.org/standard/75109.html
  • S04 — ISO, ISO 19650-4:2022 — Information exchange, 2022. https://www.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/82/78246.html?browse=tc
  • S05 — ISO, ISO 19650-5:2020 — Security-minded approach to information management, 2020. https://committee.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/42/74206.html
  • S06 — ISO, ISO 19650-6:2025 — Health and safety information, 2025. https://www.iso.org/standard/82705.html
  • S07 — ISO, ISO 7817-1:2024 — Level of information need: concepts and principles, 2024. https://www.iso.org/standard/82914.html
  • G-A — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance A — The information management function and resources, edition 2, February 2021, archived edition. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-A_The-information-management-function-and-resources_Edition-2.pdf
  • G-D — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance D — Developing information requirements, edition 2, February 2021, archived edition. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-D_Developing-information-requirements_Edition-2.pdf
  • G-E — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance E — Tendering and appointments, edition 2, February 2021, archived edition. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-E_Tendering-and-appointments_Edition-2.pdf
  • G-C — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance C — Facilitating the CDE workflow and technical solutions, edition 1, September 2020, archived edition. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf
  • P04 — ISO, ISO 9001:2026 — Quality management systems: requirements, edition 6, 16 September 2026 (replaces ISO 9001:2015). https://www.iso.org/standard/9001
  • P06 — NPSA, Security-Minded Approach to Digital Engineering, undated. https://www.npsa.gov.uk/security-best-practices/build-it-secure/security-minded-approach-digital-engineering
  • V04 — RICS, Whole life carbon assessment for the built environment, second edition 2023, updated 2024. https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/construction-standards/whole-life-carbon-assessment
  • V06 — ISO, ISO 22057:2022 — Data templates for the use of EPDs in BIM, 2022 (under revision). https://www.iso.org/standard/72463.html
  • P02 — Penn State Computer Integrated Construction Research Program, Define Supporting Infrastructure for BIM Implementation, BIM Project Execution Planning Guide v2.2, 2019. https://psu.pb.unizin.org/bimprojectexecutionplanningv2x2/chapter/define-supporting-infrastructure-for-bim-implementation/
  • P03 — European Commission study (RINA Consulting / B1P), Calculating costs and benefits for the use of BIM in public tenders — User handbook, 2021. https://www.eubim.eu/wp-content/uploads/2021/05/Cost-Benefit-Analysis-for-the-use-of-BIM_user-handbook.pdf
  • S16 — ISO, ISO 23386:2020 — Methodology to describe, author and maintain properties in interconnected data dictionaries, edition 1, confirmed 2025. https://www.iso.org/standard/75401.html
  • S17 — ISO, ISO 23387:2025 — Data templates for objects used in the life cycle of assets, edition 2, September 2025. https://www.iso.org/standard/85391.html
  • S26 — Dubai Municipality, Building circulars 196 (2013) and 207 (2015), historic BIM circulars. https://www.dm.gov.ae/
  • S27 — Dubai Municipality, Circular 9-1-2 — Mandatory BIM models with specified building-permit applications, 13 October 2023. https://dmpmedia.dm.gov.ae/uploads/2023/10/تعميم-BIM-9-1-2.pdf (checked 2026-11-04)
  • S28 — Dubai Municipality, Circular 9-1-3 — Expansion of mandatory BIM model submissions, 15 January 2026, effective 1 April 2026. https://www.dm.gov.ae/wp-content/uploads/2026/02/Circular-9-1-3.pdf (checked 2026-11-04)
  • S29 — DMT / Abu Dhabi City Municipality, BIM Documentation Guidelines for Infrastructure, v1.0, October 2020; with the ADM BIM Code of Practice, October 2020. https://www.dmt.gov.ae/adm/-/media/Project/DMT/ADM/E-Library/0001-Jan-2022-Doc/ADM-BIM-002Documentation-Guidelines-for-Infrastructure-projects.pdf (checked 2026-11-04)
  • S37 — IMI Framework (formerly UK BIM Framework), Information protocols supporting the delivery phase (BS EN ISO 19650-2) and the operational phase (BS EN ISO 19650-3) of assets — Guidance, edition 3, August 2022; Information Protocol template for BS EN ISO 19650-2 Ed 6. https://ukbimframework.org/resources/ (checked 2026-11-04)
  • ISO 55001 — ISO, ISO 55001:2024 — Asset management: requirements, edition 2, July 2024 (ISO 55001:2014 withdrawn). https://www.iso.org/standard/83054.html (checked 2026-11-04)
  • ISO 12006-2 — ISO, ISO 12006-2:2015 — Framework for classification, edition 2, last reviewed and confirmed 2020; to be revised (ISO/DIS 12006-2.2 under development). https://www.iso.org/standard/61753.html (checked 2026-11-05)
  • UNICLASS — NBS, Uniclass 2015, July 2026 release (Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27). https://uniclass.thenbs.com/download (checked 2026-11-04)
  • ISO 27001 — ISO/IEC, ISO/IEC 27001:2022 — Information security management systems, edition 3, with Amd 1:2024. https://www.iso.org/standard/82875.html (checked 2026-11-04)
  • DBC — Dubai Municipality, Dubai Building Code (Decree 45/2021) as amended by Administrative Resolution No. 225 of 2024 (13 August 2024). https://www.dm.gov.ae/?p=352286 (checked 2026-11-04)
  • DUBAI-LAW-3-2026 — Government of Dubai, Law No. 3 of 2026 Concerning the Quality and Safety of Buildings, issued 27 February 2026, in force 60 days after Official Gazette publication. https://dlp.dubai.gov.ae/Legislation%20Reference/2026/Law%20No.%20%283%29%20of%202026%20Concerning%20the%20Quality%20and%20Safety%20of%20Buildings.html (checked 2026-11-04)
  • DM-11-9-1 — Dubai Municipality, Circular (11-9-1) of 2026 applying Law No. 3 of 2026, 1 October 2026, with guidance manual 11-9-1-1 (May 2026). https://dmpmedia.dm.gov.ae/uploads/2026/10/11-9-1.pdf; https://dmpmedia.dm.gov.ae/uploads/2026/10/11-9-1-1.pdf (checked 2026-11-05)
  • UAE-FLS — UAE Civil Defence, UAE Fire and Life Safety Code of Practice, September 2018 edition. https://www.dcd.gov.ae/portal/preventive-safety/uae-fire-and-life-safety-code-of-practice.jsp (checked 2026-11-04)
  • ADIBC — DMT, Abu Dhabi International Building Codes, 2013 edition (Executive Council Resolution 7C 26/2013, effective 1 October 2013). https://www.dmt.gov.ae/-/media/Project/DMT/DMT/Codes/3-ADIMC-2013_1-12-2013.pdf (checked 2026-11-04)
  • ESTIDAMA — DMT / Abu Dhabi City Municipality, Sustainable green building implementation (minimum 1 Pearl private, 2 Pearl government-funded), 8 January 2025. https://www.dmt.gov.ae/en/adm/Media-Centre/News/08Jan2025 (checked 2026-11-04)
  • ALSAFAT — Dubai Municipality, Al Sa'fat — Dubai Green Building System, second edition, January 2023. https://www.dm.gov.ae/municipality-business/al-safat-dubai-green-building-system/ (checked 2026-11-04)
  • PDPL — UAE, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, effective 2 January 2022, Active. https://uaelegislation.gov.ae/en/legislations/1972 (checked 2026-11-04)
Document history
RevisionDateDescriptionOriginated / checked / approved
V0.1Source date not recordedOutline containing topic headings; no approved requirements suppliedSource attribution not recorded
V0.214 October 2026Decision-led OIR; portfolio requirements, cascade, quality checks and change controlPrepared in lane O1; office checker and approver to be recorded
V0.32026-11-04Closes rows: UAE jurisdiction annex list (4.1), statutory green-building ratings (3.3), UAE PDPL personal data (6), IMI Framework naming, ISO 55001/23386/23387/12006-2/27001 basis, links to BBM-STD-52/53/54, one exchange sub-ID grammar, decision links to BBM-STD-11 V0.2, duplicated decision text removed, references completed + cross-doc pointer pass (BBM-STD-51 §3 ED-IDs in §4.1, BBM-STD-90 §4 PDPL pointer)Prepared in standards-closure batch B3; office checker and approver to be recorded
V0.42026-11-05Standard watch no. 1: 4.1 Dubai row cites DM circular 11-9-1 of 2026 (Building Quality and Safety Certificate) under Dubai Law No. 3 of 2026 and the Dubai BIM Standard version 1.4; Abu Dhabi row notes the reported ADCDA amendments circular; references: ISO 12006-2 confirmed 2020, DM-11-9-1 addedPrepared for office review; office checker and approver to be recorded

This is the office's Organisational Information Requirements (OIR), rather than the generic TBP manual. It defines the information needed to run the organisation and make portfolio, service and asset decisions. It applies to the office's own business information and, only within its actual role and authority, the assets or portfolios it manages. Where the office is a consultant rather than an asset owner, the relevant appointing party owns its OIR/AIR/PIR. The office must elicit and respond to those requirements; it cannot approve them on that party's behalf.

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.

No live portfolio records, named role holders or receiving-system results were supplied. Blank implementation particulars remain controlled completion fields, not facts to invent.

Control fieldRecommended entry / required completion
Accountable document ownerDocument owner and business-function owners: see (row above).
Business approverDecision (BIM Manager, 2026-10-14): The office director approves office standards and business requirements after relevant QMS, security, safety and business-owner reviews; project departures require the actual appointment authority and recorded scope/date. Basis: Office governance does not transfer contractual or statutory powers G-A, G-E.
Contributors / checkersDecision (BIM Manager, 2026-10-14): The BIM Manager acts as office information management lead and owns the OIR document; each business function owns its applicable requirement and authorised business decision. Basis: Document maintenance and business authority are distinct functions G-A, G-D.
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.
Controlled masterDecision (BIM Manager, 2026-10-14): Keep controlled masters in the restricted office standards CDE with document ID, revision, approval and exact URI; distribute read-only approved office views and retain superseded editions without overwriting issued project baselines. Basis: Controlled identity, access and history must survive publication and change G-C, S05.
DistributionDecision (BIM Manager, 2026-10-14): Give office users role-based approved views and external recipients only sensitivity-reviewed appointment-relevant extracts; authorise and audit access and export separately. Basis: Distribution follows purpose and sensitivity S05, P06.
Effective date / next reviewDecision (BIM Manager, 2026-10-14): Adopt office policy choices on 2026-10-14; review controlled standards every 12 months and at material standard, appointment, requirement, tool, authority, incident or ambiguity change; record actual implementation approval and first-use date separately. Basis: A policy review cadence does not prove that live records or tools are ready P04.
Approval recordApprover, authority reference, revision, date, decisions accepted/rejected, effective date and controlled link