ArchHubBABOOMDownload

Office Master Information Delivery Plan (MIDP)

MIDP · V0.3 · The MIDP coordinates the information deliveries promised by the task teams of one delivery team.

Download WordWorkbookAll standards

Office BIM Standard · Revision V0.3 · 4 November 2026 · Controlled office method / project-population template · Owner: Lead Appointed Party

1. Purpose, scope and control#

The MIDP coordinates the information deliveries promised by the task teams of one delivery team. It is a maintained schedule of information containers, dependencies, checking/review windows and exchanges, compiled from controlled TIDPs. It is not a RACI, a list of consultants, the entire construction programme or evidence that a client has accepted the information.

This is the first explicitly versioned markdown successor to BBM-STD-MIDP.md, which supplied creation/update dates but no controlled revision number. V0.1 named the new method/template revision and V0.3 is the current one; the August 2025 source is retained unchanged privately. No client/project names, historic approvals or corrected exchange numbers are inferred from that export. The new tables are original office structures, not a reproduction of a client form.

Header fieldProject copy value / validation
PlanID / plan revision / baseline ID[stable plan ID / Rnn / immutable baseline ID]; method revision V0.3 is separate from a project plan's Rnn
Project / appointment / delivery team[project ID / appointment IDs / lead appointed party / task teams]; do not roll unrelated appointments into one undefined authority
Owner / prepared / checked / verified / approvedLead appointed party / Information Manager / independent planning checker / task-team and discipline leads / authorised delivery-team approver; record IDs, dates and evidence
Requirement and method baseline[EIR, BEP, responsibility matrix, LOIN register, naming code-list, clash rule-set and authority annex revisions]
Source TIDP register and exchange register[exact TIDP IDs/revisions/approvals; exchange register ID/revision]; no “latest” links
Working calendar / time zone[office and recipient working days, public holidays, hours/day, date cutoff, Asia/Dubai or actual zone]
Baseline approval / distribution / next review[decision ID/date, authorised use, recipients, weekly review date and change trigger]
CDE custody[private baseline and current view locations; permissions; Archive retention/legal-hold rule]

ISO 19650-2:2018 provides the delivery-phase basis (still in force; ISO/DIS 19650-2 at stage 40.93 is not); IMI Framework archived Guidance F, edition 1 (September 2020), distinguishes responsibilities from information delivery planning. ISO 19650-4:2022 provides the exchange-decision basis; ISO 7817-1:2024 informs information need; ISO 29481-1:2025 and ISO 29481-2:2025 inform purpose, actors and exchange interfaces. RIBA Plan of Work 2020 informs stage labels. These are standard-level references, not claims of audited clause compliance. [S02, G-F, S04, S07, S18, S19, S21]

2. Shared office decisions and acceptance baseline#

Use Clash Matrix V0.3, sections 2–3 as the single O3-POL-01 naming/revision/suitability and tolerance register. External default identity is CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext, internal revision is Rnn, suitability is SU-WIP/SU-COORD/SU-INFO/SU-REVIEW/SU-ISSUE, and logical CDE states are WIP/Shared/Published/Archive. Project appointment mappings override defaults through one approved code register, preserving historic issued identities. SU-ISSUE does not prove recipient acceptance. Do not create a second tolerance table or reuse S1/S2/S3 severity as suitability.

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.

These windows run sequentially after the coordinated set is ready unless a documented, resourced package split safely permits overlap. Preparation time is estimated by the actual task team; the default does not dictate design duration. Use the signed recipient review period if longer. A response deadline is a planning constraint, not deemed acceptance. A failure requires correction and retest; never consume review time invisibly or bypass L1/L2/L3 to recover a late production date.

O3-POL-02 applies: 100% valid applicable mandatory geometry/data/documentation and zero unresolved required hard-intersection or mandatory access/safety failures in the issued scope. The optional 95% non-mandatory progress target is informational with its denominator defined. O3-POL-03 supplies S1/S2/S3 escalation and exact-revision clash retests. No office manager may waive a binding safety/access requirement.

3. Workbook / database structure and field specification#

Store one row per planned container delivery to an exchange, not one giant row with repeated OWNER/DATE column pairs. The same stable container can occur in several exchanges with a different required information need and revision. Use DeliveryID as the unique plan row key; do not generate a new container identity for every exchange.

Table / primary keyFields / data types and validationSource / accountable owner
Control / PlanID+RevisionHeader fields in section 1; timestamps and evidence URIs; immutable BaselineIDLead appointed party; controlled plan decision
Teams / TeamIDAppointmentID, discipline/trade, lead/deputy IDs, production responsibility reference, source TIDPID/revision, scope, applicability, capacity calendar and approval evidenceTask-team lead; every appointed team represented once
Exchanges / ExchangeIDPurpose/decision, recipient/acceptor, RIBA stage, programme milestone, required use/LOIN/profile, planned submission and acceptance date, review allowance, authority route, AuthoritySubmissionID (BoD AP- ID / BBM-STD-57 SUB- ID; blank only when no authority receives the exchange), Authority BIM profile and version (e.g. DM-PERMIT R01 per BBM-STD-74 / BBM-STD-85), EIR/BEP referencesLead appointed party with appointing-party interface; unique ID, not just stage number
Deliveries / DeliveryIDContainerID, description, producing TeamID/role, source TIDP row/revision, ExchangeID, EIR/LOIN/responsibility IDs, formats/profile, required revision/suitability/state, SensitivityClass (Public / Internal / Confidential / Restricted from the ISO 19650-5 triage per BBM-STD-87 §2), H&S information flag and H&S record ID (ISO 19650-6 per BBM-STD-88), start, PrepDays, L1Days, SharedDue, L2/L3/rework windows, SubmissionDue, AcceptanceDueImported from approved TIDP; durations non-negative numeric working days, dated constraints parseable
Dependencies / DependencyIDPredecessor DeliveryID or ExternalInterfaceID, successor DeliveryID, FS/SS/FF relation, lag in working days, required input revision/state/use, actual input receipt/decision, owner, conflict/resolution evidenceTask leads agree; default finish-to-start after checked input, not a bare file arrival
Interfaces / InterfaceIDOther delivery team/appointment, provider/recipient, input requirement and exact container/revision, promised/received date, acceptance criterion/decision, latest safe input date, fallback/escalationNamed interface owner; external promises tracked explicitly
Review / ReviewIDPackage/DeliveryIDs+exact revisions, L1/L2/L3 reviewers and IDs, planned/actual dates, report/comment links, pass/rework disposition, authorisation/release and recipient decision IDsIndependent checkers, technical committee, releasing PM and appointing party retain separate authorities
Progress / DeliveryID+SnapshotDateBaseline dates, forecast dates, actual started/Shared/submitted/accepted timestamps, stage evidence, remaining duration, issue/blocker IDs, variance, next action/owner/dueInformation Manager updates from evidence, weekly and change-triggered
Changes / ChangeIDTrigger, prior baseline, proposed dates/scope/revisions, affected rows/dependencies, capacity and requirement impact, authority/decision/date, new baseline, distribution acknowledgmentsLead appointed party controls; no silent baseline overwrite

Foreign keys must resolve; required values cannot be empty. Record tool builds/presets and profile in the EIR/BEP annex and link the exact annex revision. A spreadsheet formula is a convenience; retain the computed dates with calendar/version and check against the approved programme. Non-file information containers (for example a controlled register or approved database dataset) are permitted when their identity, version, access and deliverable snapshot are defined.

Discipline block codes are the 3-letter codes of the one code dictionary BBM-STD-93; the table below is the local subset.

Office discipline block retainedPlanning treatment
GEN (BIM / information coordination)Coordination register/reports and federation outputs; production responsibility explicit
ARCArchitectural models, drawings, schedules and design records
INTInterior models, finishes, drawings and interfaces
LSCLandscape outputs, levels and external interfaces
STRStructural models, opening approvals and calculations/document links
ELEElectrical/lighting/low-current scope by appointment; boundaries mapped to EL and LI trade sets
MECMechanical model, equipment/access data and documentation
PLUWater/drainage/fire protection scope by appointment; boundaries mapped to WS, DR and FF

Appoint additional task teams for civil, dry/wet utilities, specifications, cost and specialist scope when required. A discipline block is not a substitute for an appointed producer. Mark a genuinely inapplicable team with reason and authority; do not silently omit missing TIDPs.

4. Exchange register and legacy-number reconciliation#

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.

Do not rename the old #00/#01/#01/#02/#05/#06/#07 columns by guessed sequence. Preserve them as legacy labels qualified by source block, purpose and stage. The project owner reconciles each to an approved ExchangeID and milestone with evidence. A grouped Stage 2/3 package may have one transmission, but retains two decision/LOIN records and explicit dates; grouping cannot delete a required spatial-coordination check.

Legacy source evidenceReconciliation field to completeNew method treatment
Repeated #01 for Stage 1 and Stage 2/3[source block + title + stage → approved ExchangeID; evidence; owner/date]Flag DuplicateLegacyLabel until resolved; do not join by the legacy label alone
Skipped numbering / #02 described as Stage 4[actual exchange-register mapping and programme milestone]No automatic sequential correction or assumption that exchange number equals stage
Combined Stage 2/3[appointment permits grouping? purpose/LOIN for each outcome? decision dates?]Default separate; authorised grouping documented
Old project/dates/CSI/naming fields[actual applicability and naming/classification mapping]Retain source privately; migrate only approved values, not client identity into reusable examples
ExchangeID (synthetic)Purpose / RIBA stageRecipient / milestonePlanned submission / acceptanceRequired use and need
EX-Concept option decision / 2 Concept DesignAppointing-party design reviewer / MS-2026-10-16 / 2026-10-21Separately controlled concept baseline; outside the detailed example schedule below
EX-Coordinated layout decision / 3 Spatial CoordinationAppointing-party design reviewer / MS-2026-11-26 / 2026-12-01Coordinated models, selected mandatory equipment data/access evidence, discipline notes and L1–L3 records
EX-Technical package approval / 4 Technical DesignDefined technical recipient / MS-[programme dates to agree in project copy]New LOIN and responsibility baseline; not implied by accepting EX-
EX-SYN-PERDubai Municipality BIM building-permit submission / 4 Technical Design (permit stage)Dubai Municipality via the Dubai BIM portal / MS-SYN-PER; AuthoritySubmissionID SUB-SYN-PER (BBM-STD-57), BoD AP-SYN-PER[programme dates to agree in project copy; authority review period as stated by DM]Profile DM-PERMIT R01 (BBM-STD-74): applies under circular 9-1-3 (effective 1 Apr 2026) to new buildings above G+12 or of 15,000 m2 or more and listed alterations; architectural and structural BIM submitted with the drawings, drawings extracted from the model; IFC schema/export setup and attribute matrix as stated in the current Dubai BIM Standard, recorded in BEP. Synthetic row; no real submission

EX-SYN identifiers are new synthetic examples, not repaired identifiers from the client export. Actual exchange IDs and dates require the appointing-party/lead-appointed-party record.

5. Worked coordinated baseline — original synthetic scenario#

The following complete planning subset demonstrates how three design task teams and a coordination task team roll up. Its assumed input approvals are scenario conditions, not real office signatures. Project live population is still required. Example calendar CAL-: Monday–Friday, 8 hours/day, Asia/Dubai, no holidays within the example dates; actual projects include confirmed office/recipient holidays. Start and finish dates count working days inclusively; a finish-to-start successor begins the next working day after the predecessor's checked finish unless a timed same-day handoff is explicitly agreed.

Source TIDP / revisionProducer / scenario scopeScenario input state / roll-up source
TIDP-SYN-AR / R01Architectural task team; coordinated layout modelAssumed approved planning row AR-01; actual approval evidence not supplied
TIDP-SYN-ST / R01Structural task team; coordinated framing modelAssumed approved planning row ST-01; actual approval evidence not supplied
TIDP-SYN-ME / R01Mechanical task team; model, equipment schedule and design noteRows ME-01/ME-02/ME-03 in TIDP V0.3 section 5; same dates, dependencies and delivery keys
TIDP-SYN-IM / R01Coordination task team; coordination reportAssumed approved planning row IM-01; actual approval evidence not supplied
DeliveryID / source rowContainerID and descriptionTeam / preparation start→finish / daysL1 window / days / Shared dueDependenciesExchange
DEL-SYN-AR01 / AR-01CLI-OFF-P001-Z01-L01-M3-A-0001; architectural modelAR / 2026-10-26→2026-10-30 / 52026-11-02→2026-11-03 / 2 / 2026-11-03IF- requirements receipt 2026-10-23EX-
DEL-SYN-ST01 / ST-01CLI-OFF-P001-Z01-L01-M3-S-0001; structural modelST / 2026-10-26→2026-10-30 / 52026-11-02→2026-11-03 / 2 / 2026-11-03IF- requirements receipt 2026-10-23EX-
DEL-SYN-ME01 / ME-01CLI-OFF-P001-Z01-L01-M3-M-0001; mechanical modelME / 2026-11-04→2026-11-10 / 52026-11-11→2026-11-12 / 2 / 2026-11-12DEL-SYN-AR01 + DEL-SYN-ST01 checked Shared, FS+0EX-
DEL-SYN-ME02 / ME-02CLI-OFF-P001-Z01-L01-SH-M-0002; equipment scheduleME / 2026-11-11→2026-11-11 / 12026-11-12→2026-11-13 / 2 / 2026-11-13DEL-SYN-ME01 prepared model 2026-11-10; FS+0 at preparation interface, not early releaseEX-
DEL-SYN-ME03 / ME-03CLI-OFF-P001-Z01-L01-RP-M-0003; design/access noteME / 2026-11-11→2026-11-11 / 12026-11-12→2026-11-13 / 2 / 2026-11-13DEL-SYN-ME01 prepared model; separate author/checker capacity from ME-02EX-
DEL-SYN-IM01 / IM-01CLI-OFF-P001-Z01-L01-RP-Z-0001; coordination reportIM / 2026-11-16→2026-11-16 / 12026-11-17→2026-11-18 / 2 / 2026-11-18All five checked Shared inputs; FS+0 after last 2026-11-13EX-

Model formats: agreed native plus IFC; schedule: controlled dataset/CSV plus human-readable PDF; notes/report: PDF and approved issue/BCF links. Exact native format/schema/profile and model Rnn are frozen in the package manifest and LOIN table in the TIDP; filenames have the specified extensions. Z is the synthetic coordination role only if included in the project code list. IDs shown without extension are stable logical identities; each planned format variant has an explicit extension and mapping, not ambiguous anonymous copies.

EX- package phasePlanned windowEvidence / owner and constraint
Last input discipline QC / report preparation+L1Through 2026-11-18Individual L1 records and report checked; named independent staff capacity confirmed in the scenario
L2 cross-discipline review2026-11-19→2026-11-20 (2 days)Exact six-container set and revisions; design leads / coordinator; matrix runs and comment log
Correction/retest contingency2026-11-23→2026-11-24 (2 days)Preserve reserve even if no defects; corrected revision triggers L1 affected scope and independent L2 retest
L3 technical committee2026-11-25 (1 day)Release or Resubmit affected containers; verify L1/L2 complete
Delivery-team authorisation / PM release2026-11-26 (1 day)Authorisation, immutable manifest and formal submission record
Appointing-party review/acceptance2026-11-27→2026-12-01 (3 days)Recorded acceptance/rejection and permitted use; no deemed acceptance

The package phases above are the governing worked dates: MS- is therefore 2026-12-01, with submission on 2026-11-26. Section 4's exchange row uses these same dates. All six deliveries are submitted together on 2026-11-26 for decision by 2026-12-01; earlier Shared dates are input handoffs, not final client deliveries.

6. External interfaces, dependency resolution and capacity#

Interface / provider→receiverRequired input / agreed statePromised / latest safe dateFailure response / accountable owner
IF- / appointing party→AR/ST/MEEIR/design basis R01 and coordinate controls; reviewed for appointed useScenario 2026-10-23 / 2026-10-23Missing/changed requirements: hold affected preparation, assess all downstream dates, log change; LAP interface owner
IF- / equipment supplier (another delivery team)→MEDimensions, connection/withdrawal envelope and source revision valid for selected equipmentScenario 2026-11-03 / 2026-11-03Late manufacturer evidence blocks affected access rule and ME estimate; no assumed 500 mm fallback; mechanical lead
IF- / delivery team→appointing partyComplete authorised EX- manifest plus technical records2026-11-26 / milestone 2026-12-01Rejected/missing container: affected resubmission, impact and receiver record; LAP and recipient acceptor

For each dependency, store whether the input must be Prepared, checked Shared, authorised or accepted, and which decision makes it usable. The ME model requires checked Shared AR/ST; schedule/note production can use the controlled prepared ME model internally, but release requires the model's L1 and all interdependent checks to pass. Record these distinct dependency events instead of forcing every link to the final client acceptance date.

Resolve missing predecessors, cycles, conflicting revisions, holidays, reviewer availability, discipline resource overload and external input promises before baselining. Check parallel model review, schedule production and note production against named people/hours; the scenario assumes separate mechanical model checker, schedule author/checker and note author/checker. If the actual team lacks that capacity, stagger the tasks and reforecast the package. Do not assert feasibility from dates alone.

Calculate latest required input dates by working backward from the acceptance milestone through recipient review, release, L3, correction reserve, L2, L1 and preparation/dependencies. The scenario serial review tail after 2026-11-18 is 9 working days: L2 2 + reserve 2 + L3 1 + release 1 + acceptance 3. Negative float or threatened latest input dates require an explicit resolution, not a hidden compression of QA.

7. Establish, maintain and change the baseline#

  1. Confirm the appointment, EIR/exchange register, container breakdown and detailed production responsibilities. Assign task-team leads and interface owners; verify capability, capacity and practical tool/CDE readiness.
  2. Obtain every appointed task team's checked and approved TIDP, with exact version and approval evidence. Import its delivery rows and preserve source keys. Missing approvals mean Draft/Hold, never Approved.
  3. Reconcile exchange IDs, stages and milestones with the project programme and recipient. Reconcile legacy duplicate labels via section 4. Resolve dependency/capacity conflicts with task leads and other delivery teams.
  4. Allocate the review/rework/release/acceptance windows and real reviewers. Confirm requirements, output profiles, closure rule IDs, permitted use and mandatory thresholds for every exchange.
  5. Independent planning checker verifies dates, calendars, joins, scope coverage and resource assumptions. Task leads sign their commitments; the authorised lead-appointed-party approver baselines the MIDP. Appointing-party agreements are recorded where required by the appointment.
  6. Store an immutable approved baseline and distribute its ID/revision to producers, reviewers and recipients. Preserve the separate current forecast; actual progress evidence never overwrites the baseline dates.
  7. Update weekly and immediately for approved changes, late inputs, rejection, revised requirements, source/tool changes or safety/security impacts. Record blockers and actions even when no date change has yet been approved.
  8. Raise ChangeID, assess affected containers/requirements/dependencies/resources and receiver decisions, propose new dates, obtain the appropriate approval, revise all affected TIDPs and the MIDP, and retain before/after records and recipient acknowledgments.
  9. Freeze the exact exchange manifest. Verify three-level QC and required retests, authorise, release and collect the actual recipient decision. Rejected outputs return to a controlled WIP revision; unaffected accepted containers keep their identities/revisions unless the coupled package requires retest.
  10. Audit whether approvals, checks and changes actually followed the method. Link corrective actions and lessons to the next planning baseline; QA plans means and criteria, QC checks outputs, audit checks the process, and PDCA closes corrective improvement.

8. Progress and controlled change templates#

DeliveryID / baselineBaseline Shared / submission / acceptanceForecast Shared / submission / acceptanceActual stage / evidenceBlocker / action / owner / due
DEL-SYN-ME01 / BL- (example)2026-11-12 / 2026-11-26 / 2026-12-01Same baseline in unchanged scenarioPlanned only; no actual model/test/approval suppliedNone assumed in scenario; live evidence required
[row ID / baseline][immutable dates][latest forecast dates][Prepared/Checked/Shared/Authorised/Submitted/Accepted/Rejected; exact record URI][issue/change ID; next action; role; due]

Do not invent completion percentages. Report counts of containers in evidenced stages, overdue deliveries and affected gates. AcceptedOnTime = accepted containers with actual acceptance date ≤ baseline acceptance date / containers requiring acceptance by the reporting cutoff; show denominator, exclusions and rejected/pending cases. Submission on time is a different metric. A weekly “100%” claim cannot override a mandatory failure in one container.

ChangeIDTrigger / prior baselineAffected delivery/dependency / proposed impactDecision / propagated records / notice
SYN-CHG-01 (hypothetical)Supplier access envelope changes; BL-ME-01/02/03, IM-01, access rule and EX-; re-estimate production, repeats and acceptance milestone before approvalPending example; no changed date is approved. Record decision authority, revised TIDP/MIDP IDs, manifest/rule changes and receiving-party acknowledgment
[ID][requirement/input/rejection; previous baseline][scope, old/new dates, float, capacity, risks and justification][approve/reject; approver/date/evidence; all affected records and distribution]

L1 retains marked-up and clean sets, independently checked comments and author/checker IDs. L2 retains cross-discipline/clash/model-health records and issue closure evidence. L3 retains committee comments and Release/Resubmit decision. The project manager transmits only after technical release and delivery-team authorisation. The appointing party decides acceptance; separate evidence supports all four decisions.

9. Acceptance criteria / self-check#

  • Every appointed task team is represented by an approved exact-revision TIDP or a justified inapplicable-scope decision; every MIDP row maps back to a real source row.
  • Container identity, description, producer, LOIN/requirement IDs, format/profile, exchange, preparation duration and delivery/acceptance dates are populated and validated.
  • Exchange IDs are unique and reconciled; Stage 2 and 3 outcomes are explicit; no guessed legacy renumbering remains.
  • Every dependency and external interface has required revision/state, provider, input date and resolution evidence; no missing keys, cycles, calendar errors or unresolved capacity conflicts.
  • L1/L2/L3, correction/retest, authorisation/release and recipient windows are funded and resourced; binding recipient terms prevail; safety checks cannot be sacrificed to a milestone.
  • Baseline approval, current forecast, actual evidence and controlled changes are distinct. Linked TIDPs use the same approved dates and exchange meaning.
  • Mandatory information/rule checks pass before affected issue; exact manifest/revisions, release evidence and separate recipient decision remain auditable privately.

Common mistakes: declaring RACI a delivery plan; aggregating unapproved rows; using stage number as exchange identity; collapsing preparation/Shared/submission/acceptance into one date; ignoring external promises or reviewers; accepting a platform upload as formal acceptance; changing baseline dates to hide delay.

10. Research coverage, correction trace and live-population boundary#

ItemPresent section / evidence
T12.1Sections 3, 5 and 7: task-team source register, source row/revision keys and approval-controlled consolidation
T12.2Sections 4–6: unique exchanges, linked dates, working calendar and resolved scenario dependencies
T12.3Sections 3 and 5: responsible producer, stable container, preparation duration and dated deliveries
T12.4Sections 2, 5–6: explicit review/rework/release/recipient windows and other-team interfaces
T12.5Sections 7–8: immutable baseline, current forecasts, evidence and controlled changes
O07 P1 / C03Usable coordinated baseline method plus complete synthetic roll-up; legacy exchange ambiguity retained for evidence-based reconciliation, not invented historical correction
O07 P2Field specification, durations, dependency events, review/acceptance windows, progress and change templates
O07 P3Generated dependency/milestone view from deliveries/exchanges; diagram below explains the controlled roll-up
C02/C04/C06/C07/C08/C11/C12Shared O3 policy, controlled states and acceptance, rule references, private original examples, stage/LOIN correction and actual tool qualification

This editorial revision is complete as an office method and original worked template. No approved actual task-team TIDPs, project exchange register or genuine dates/approval receipts were supplied. Therefore an operationally approved office/project MIDP and historical exchange reconciliation are not claimed. Project owner must populate the live records and pass section 9 before activation; a synthetic planning baseline is never presented as client approval.

One approved baseline; separate forecast, actual progress and recipient acceptance evidence.

References#

RESEARCH.md source tags below identify editions actually used. References establish scope and practice; no unverified ISO clause is asserted. Office defaults are local decisions, not ISO-mandated numerical limits.

TagTitlePublisherYear / editionURL / evidence
S01ISO 19650-1 — Concepts and principlesISO2018, ed.1Catalogue / abstract; published, revision underway
S02ISO 19650-2 — Delivery phase of the assetsISO2018, ed.1Catalogue / abstract; publisher result exposes English abstract and status
S04ISO 19650-4 — Information exchangeISO2022, ed.1Catalogue / abstract
S05ISO 19650-5 — Security-minded approach to information managementISO2020, ed.1; confirmed 2025 (checked 2026-11-04)Catalogue / abstract
S06ISO 19650-6 — Health and safety informationISO2025, ed.1Catalogue, checked 2026-11-04
DM-9-1-3Dubai Municipality circular 9-1-3 (BIM with building permits)Dubai Municipality15 Jan 2026, effective 1 Apr 2026Circular PDF, checked 2026-11-04; earlier circular 9-1-2, 13 Oct 2023
S07ISO 7817-1 — Level of information need: concepts and principlesISO2024, ed.1Catalogue / abstract
S18ISO 29481-1 — Information delivery manual: methodology and formatISO2025, ed.3Catalogue / abstract
S19ISO 29481-2 — Information delivery manual: interaction frameworkISO2025, ed.2Current publisher record; withdrawn 2012 edition; detailed requirements not audited
S21RIBA Plan of Work 2020Royal Institute of British Architects2020Current resource page; 2020 template
G-AGuidance A — The information management function and resourcesIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 2, February 2021Official PDF; archived Guidance Parts A–F listed on ukbimframework.org/resources, checked 2026-11-04
G-CGuidance C — Facilitating the CDE workflow and technical solutionsIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 1, September 2020Official PDF; archived guidance
G-FGuidance F — About information delivery planningIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 1, September 2020Official PDF; edition actually verified. Its federation section is a placeholder; use other sources for technical federation guidance.

Internal concept source: office QMS concept notes (working record), 14 October 2026; the controlled QMS is BBM-STD-96; original procedures here use concepts only. Immutable office spreadsheet export remains private evidence; no third-party template wording is reused.

Document history
VersionDateChange
V0.114 October 2026First versioned markdown successor to BBM-STD-MIDP.md.
V0.2not recordedFile re-issued as V0.2 (header text still read V0.1).
V0.34 November 2026closure: header equals filename version and link texts point to Clash Matrix V0.3 / TIDP V0.3; authority-submission fields and synthetic EX-SYN-PER row (Dubai BIM permit); IMI Framework naming with archived Guidance editions; SensitivityClass (ISO 19650-5) and H&S information fields (ISO 19650-6); discipline blocks use BBM-STD-93 codes. + cross-doc pointer pass.