Office BIM Standard · Revision V0.4 · 5 November 2026 · Controlled office method / project-population template · Owner: BIM Manager
1. Purpose, scope and document control#
Use this register to plan, run and evidence model coordination across the office delivery team and its supply chain. It covers physical intersections, installation clearances, operational access and model duplicates. A model test supports competent design review; it does not establish structural adequacy, accessibility, fire compliance or construction approval by itself.
This revision replaces the spreadsheet's ambiguous matrix cells with explicit test rules, a federation manifest and linked issue records. Keep the original export unchanged as private provenance. The September 2025 control label “Version: 00” is treated as the unversioned legacy baseline; the first controlled markdown revision was V0.1; this revision is V0.3 (see Revision history). It fixes the broken control formula by storing typed metadata, not a calculated banner.
| Control field | Value / entry required |
|---|---|
| Document ID / revision / effective date | BBM-STD-50-CLASH_MATRIX / V0.3 / 2026-11-04 |
| Prepared / checked / verified / approved | BIM Coordinator / independent coordination checker / discipline leads / BIM Manager; enter identifiable IDs and dates in the project copy |
| Appointment and intended use | [appointment ID; delivery team; in-scope exchange and permitted use] |
| Requirements baseline | [EIR, BEP, LOIN, design basis, authority annex, manufacturer evidence: exact IDs/revisions] |
| Matrix / rule-set baseline | [register ID, revision, rule-set hash, approval record, CDE location] |
| Tool baseline | [federator/checker product, full build, exporter build, settings/preset hash, known-result qualification] |
| Supersession and distribution | Prior export retained privately; approved rules distributed to every affected task team and supplier; historic issues keep their original identity |
ISO 19650-1:2018 informs role terminology; ISO 19650-2:2018 informs delivery arrangements; ISO 19650-4:2022 informs exchange decisions. ISO 7817-1:2024 defines purpose-led information need. BCF 3.0 bcfXML (buildingSMART final, 18 Jun 2021) is the selected issue exchange profile; BCF-API 3.0 is used only after endpoint qualification, and receivers limited to BCF 2.1 (2017) use a recorded 3.0→2.1 field map and round-trip test. RIBA Plan of Work 2020 supplies stage names; none of these references sets a universal office clash tolerance. [S01, S02, S04, S07, S13, S21]
Where BBM-STD-57 records a Dubai Municipality BIM permit route (circular 9-1-2 of 13 Oct 2023 or 9-1-3 of 15 Jan 2026, effective 1 Apr 2026; detail in BBM-STD-85), the federation manifest uses the same permit IFC export setup (the IFC schema and export setup stated in the current Dubai BIM Standard, checked at project start and recorded in the BEP) and the project shared frame from the CRS register in BBM-STD-86 (Dubai: DLTM, EPSG:3997; vertical datum DMD). Clash evidence for the permit model is retained with the submission record. [S22, S23, S24]
The lead appointed party coordinates the delivery-team rule register. The appointing party defines its exchange/acceptance requirements. Task teams produce and check their information; competent discipline designers decide changes to their design. “Lead Appointing Party” is retired. A coordinator cannot unilaterally instruct another discipline to cut structure or waive safety requirements.
2. One office decision baseline#
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.
Decision (BIM Manager, 2026-10-14; re-affirmed): 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.
| Shared O3 policy field | Controlled office value | Check / migration rule |
|---|---|---|
| Container identity | Eight uppercase hyphen-separated tokens; NUMBER is four digits; lowercase approved extension | Example CLI-OFF-P001-Z01-L01-M3-A-0001.ifc; ZZ means whole scope; validate every token against project code lists |
| Revision | R00 initial WIP, then R01, R02…; expand digits beyond R99; never recycle | Same identity for changed content; revision is metadata, not part of the identity; unchanged containers retain their actual revision |
| Suitability | SU-WIP: team work only; SU-COORD: coordination; SU-INFO: reference information; SU-REVIEW: formal review; SU-ISSUE: authorised defined use | Local codes, not ISO or UK national-annex codes; store permitted use and actual acceptance decision separately |
| CDE state | WIP / Shared / Published / Archive | SU-ISSUE does not itself prove appointing-party acceptance; Published has the explicit authorised-use/release record; preserve rejected and superseded evidence |
| Office drawing/model aliases | Preserve existing internal names with an ID-to-container mapping | Trade codes are selection aliases; ROLE codes come only from the one code dictionary BBM-STD-93. Each trade alias maps to exactly one ROLE in section 4. Do not equate trade code with role code |
| Appointment override | One project register maps client grammar, revisions and suitability to these meanings | Preserve past issued identities; apply authorised mapping to future issues; no parallel active naming lists |
The following table is the authoritative O3 tolerance table. MIDP and TIDP reference it by O3-POL-01 and rule revision, rather than restating different numbers. It supersedes legacy stage thresholds and candidate 20/25 mm pair settings for this method. Other office documents' historical candidate tables require this project rule register at use; their unrelated recommendations are outside O3.
3. Test semantics, tolerances and release thresholds#
| Rule type | Office detection setting | Required evidence and pass condition | Change control |
|---|---|---|---|
| H: hard intersection | 0 mm deliberate penetration allowance; tool contact/precision behavior recorded | No unresolved unintended physical overlap in required scope. Include insulation, fittings and relevant supports. Mere touching is reviewed against tool behavior; numeric noise is dispositioned, never silently dropped | Qualified precision fixture; any numerical epsilon is documented by tool/units and independently checked; it cannot authorise a physical conflict |
| C: installation clearance | Required separation/envelope from design, installation sequence and manufacturer requirement; no blanket 150 mm | Measured minimum distance ≥ recorded requirement or no obstruction of the explicit envelope; installation and removal sequence checked | Requirement ID, actual millimetres/envelope and competent designer required before enabling rule; missing value blocks rule activation |
| A: access / maintenance / safety | Exact access, swing, withdrawal and route envelope from applicable code/design/manufacturer; no blanket 500 mm | Required envelope free; route and activity usable in designer review; retain dimensions and source revision | Safety/access requirements cannot be waived by BIM Manager or model tolerance |
| D: duplicates | Exact coincident geometry/identity investigation; no general 10 mm merge rule | No unintended duplicate in selected population. Separate repeated elements, joins and deliberate shared-reference geometry explicitly | Never delete by proximity alone; producer corrects with before/after evidence |
| V: verified existing condition | Survey/design acceptance method and accuracy from approved evidence | Reconcile observed and modelled state with source uncertainty, deviations and owner decision | A 0 mm clash setting does not assert zero survey uncertainty or as-built accuracy |
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.
Non-mandatory information may use the Manual's 95% progress target only with a defined numerator, denominator and scope; it is not acceptance. Cosmetic/minor issues can remain only with a recorded permissible disposition, recipient notice, owner and due date. Pending required inputs or tests block affected release. Do not claim “zero clashes” for untested or excluded scope.
| Project stage | Correct RIBA 2020 term | Coordination focus / information need |
|---|---|---|
| 0 / 1 | Strategic Definition / Preparation and Briefing | Requirements, existing-condition reliability, responsibilities and test scope |
| 2 | Concept Design | Primary routes, space reservations and provisional interface evidence |
| 3 | Spatial Coordination | Coordinated object locations, interfaces, clearance/access requirements |
| 4 | Technical Design | Defined openings, sizes, installation/support detail and approved design checks |
| 5 | Manufacturing and Construction | Fabrication/install interfaces, temporary works and sequence information where appointed |
| 6 / 7 | Handover / Use | Verified delivered condition, service access, residual risks and operational triggers |
Stage 4/5 overlap can be planned by procurement package. LOD labels may be retained as descriptive legacy aliases only alongside explicit geometry, data and documentation requirements. No automatic Stage→LOD→tolerance rule remains.
4. Trades, selections and generated pair matrix#
Retain the office trade codes as stable selection aliases; the project annex records actual native categories, IFC classes and property filters. Every selection set includes a count, model/zone coverage, exclusions and checker evidence. A zero-element set requires an explained scope decision; it must not silently produce a passing test.
| Office trade | Selection scope to define in the project copy | ROLE (BBM-STD-93) | Discipline code |
|---|---|---|---|
| AR | Envelope, walls, doors/windows, floors/roofs, vertical circulation and architectural equipment | A | ARC |
| ID | Interior partitions, ceilings, finishes, interior doors and furniture | I | INT |
| ST | Primary structure, foundations, slabs, framing and structural circulation | S | STR |
| ME | Air systems, mechanical equipment, pipework, insulation, valves and supports | M | MEC |
| EL | Electrical containment, equipment, communications, security and alarm components | E | ELE |
| LI | Lighting devices and equipment; coordinate the EL/LI boundary to avoid double ownership | E | ELE |
| WS | Water services, fittings, equipment and insulation | P | PLU |
| DR | Drainage, fixtures, fittings, falls and inspection requirements | P | PLU |
| FF | Fire protection pipework, equipment, controls and heads | F | FLS |
| LS | Landscape, soil zones, planting, irrigation interfaces and hard surfaces | L | LSC |
| CI | Civil routes, surfaces, drainage structures and external constructed interfaces | C | CIV |
| DU | Dry utilities, cabinets, ducts, containment and network interfaces | C | CIV |
| WU | Wet utilities, chambers, pipework and network interfaces | C | CIV |
DU and WU are external utility networks and take the civil role C. Where a building-services team produces a utility network, the project annex records the override against BBM-STD-93. A discipline not listed is added per project at the next free code in BBM-STD-93.
The compact matrix below is a coverage index, generated from active register rows; it does not independently define an approved test. H indicates physical tests; CA indicates applicable clearance/access tests; D indicates in-team duplicate checks. U means applicability not yet determined and blocks baseline sign-off. NA requires a reason/approver; blank and “x” have no permitted meaning. One canonical unordered pair avoids A↔B double counting; directional access/sequence rules remain separate.
| Pair index (illustrative) | ST | AR | ME | EL | WS | DR | FF |
|---|---|---|---|---|---|---|---|
| ST | H,D | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA |
| AR | — | H,D | H,CA | H,CA | H,CA | H,CA | H,CA |
| ME | — | — | H,D,CA | H,CA | H,CA | H,CA | H,CA |
| EL | — | — | — | H,D,CA | H,CA | H,CA | H,CA |
| WS | — | — | — | — | H,D,CA | H,CA | H,CA |
| DR | — | — | — | — | — | H,D,CA | H,CA |
| FF | — | — | — | — | — | — | H,D,CA |
For all 13 applicable trades, generate 91 unordered trade pairs including self-pairs (13×14/2). Account explicitly for ID, LI, LS, CI, DU and WU beyond this building-services illustration. At element level, create separate rules for each meaningful object population and envelope; the trade-level index does not replace those selections. Disabled or NA rows remain visible in the coverage report.
4.1 Office baseline matrix, all 91 pairs#
Every unordered pair of the 13 trades is decided; the office baseline has no U. H = hard test; CA = clearance and access tests; D = duplicate check (self-pairs, and the EL–LI boundary so each luminaire has one owner); NA = not tested, with the reason below. The 28 pairs of the §4 illustration are unchanged; the C and A rows of AR–AR and ST–ST are NA (in-model designer checks, not federated tests). A project copy may set a pair to NA only with a recorded reason and approver, and still defines the element-level selections of §4.
| ST | AR | ID | ME | EL | LI | WS | DR | FF | LS | CI | DU | WU | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ST | H,D | H,CA | H | H,CA | H,CA | H | H,CA | H,CA | H,CA | H | H | H,CA | H,CA |
| AR | — | H,D | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H | H |
| ID | — | — | H,D | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H | NA | NA | NA |
| ME | — | — | — | H,D,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA |
| EL | — | — | — | — | H,D,CA | H,D | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA |
| LI | — | — | — | — | — | H,D | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H |
| WS | — | — | — | — | — | — | H,D,CA | H,CA | H,CA | H,CA | H,CA | H,CA | H,CA |
| DR | — | — | — | — | — | — | — | H,D,CA | H,CA | H,CA | H,CA | H,CA | H,CA |
| FF | — | — | — | — | — | — | — | — | H,D,CA | H,CA | H,CA | H,CA | H,CA |
| LS | — | — | — | — | — | — | — | — | — | H,D | H,CA | H,CA | H,CA |
| CI | — | — | — | — | — | — | — | — | — | — | H,D | H,CA | H,CA |
| DU | — | — | — | — | — | — | — | — | — | — | — | H,D,CA | H,CA |
| WU | — | — | — | — | — | — | — | — | — | — | — | — | H,D,CA |
NA reasons: ID–CI, ID–DU and ID–WU share no space (civil works and utility networks are external; building entries are tested in the services–utility pairs). ID–LS is H and may have a zero population with a recorded scope note (interior planting not in scope).
Rule owner. The lead appointed party owns the coordinated test baseline. The resolver of a clash is the discipline lead of the lower trade in the office routing precedence ST > AR > CI > DR > WU > DU > ME > FF > WS > EL > LI > ID > LS; in a self-pair it is that trade. A different resolver is a recorded coordination decision per issue.
C and A tolerances. No blanket value: each active C or A rule carries its recorded requirement (design, manufacturer, code, or utility regulation such as register row ED-UTILITY-REGS for utility separations) with the source ID and value in millimetres or as an envelope. A rule without that requirement stays inactive and blocks the pair's sign-off (§3).
5. Workbook structure and column / field specification#
Use seven linked sheets/tables. No merged headers, placeholder formula errors or duplicated authoritative values. Protect code lists and calculated views; input fields use controlled types. IDs are text, dimensions numeric in mm, dates ISO 8601 with the agreed working calendar, and evidence links resolve inside authorised private custody.
| Table / key | Fields: type and validation | Owner / relationship |
|---|---|---|
| Control / RegisterID+Revision | DocumentID, prepared/checked/verified/approved IDs and dates, EIR/BEP/LOIN references, tool/build/settings hash, effective date, distribution list, approval evidence: text/date/URI | BIM Manager; revision-specific baseline |
| Models / ModelID+Revision | ContainerID, trade, producer/team, native/source and exchange revisions, URI/hash, units/CRS/transform ID, zone/level, Shared decision ID/date, export/build/profile, IFC Schema (IFC 4.0.2.1 / IFC 4.3.2.0 / IFC2x3), MVD, ValidationReportURI, IDS result URI, included/excluded scope: typed text/URI/date | Producer supplies; coordinator validates exact approved Shared set |
| Sets / SetID+Revision | ModelID/revision, native/IFC filter, category/class/property clauses, zone, insulation/support/envelope inclusion, element count integer ≥0, exclusion ID, tester/result URI | Producer and independent checker; stable GUIDs in run evidence |
| Rules / RuleID+Revision | PairKey, SetA/SetB revisions, model/zone, H/C/A/D/V type, requirement/LOIN IDs, numeric threshold and units or envelope ID, rationale/source, tool mode, precision fixture, severity, frequency/trigger, designer, checker, enabled boolean, approval ID | Lead appointed party owns coordinated baseline; no enabled C/A without source and value |
| Runs / RunID | Rule revision, source-set manifest/hash, run timestamp/build/settings, counts selected/tested/raw/grouped/excluded/open, result URI, issue IDs, runner/checker, pass/fail/blocked | Coordinator; immutable evidence per run, not overwritten by latest export |
| Issues / IssueID | Rule/run IDs; source models/revisions; stable element GUIDs; title/description; viewpoint URI/camera/clipping/location; severity, assignee, due date, status, requirement; disposition/exception decision; corrected revision; retest run and reviewer/date; closure decision | Designer owns correction; independent checker closes; BCF topic GUID stored as external key |
| Exclusions / ExclusionID | Rule/set scope and element IDs, reason, evidence, permissible authority, start/expiry dates, review trigger, approved record; type controlled: intended join / opening / duplicate-reference / out-of-scope | Checker verifies exclusion before result; no indefinite anonymous suppression |
A row version is part of the record. Validate unique keys, required fields, foreign-key joins, positive dimensions where required, valid code membership, exact revisions, dates, links and rule coverage before importing into a clash tool. BCF XML/API custom statuses and assigned users must map to the same office meanings; round-trip a topic, elements, viewpoint and status before enabling the route. Exporting a screenshot alone is not BCF qualification.
6. Completed original examples — synthetic, not live approval#
| Rule / revision | Models and zone | Selections / test | Setting / source | Severity / owner / trigger |
|---|---|---|---|---|
| SYN-H01 / R01 | SYN-ST R02 + SYN-ME R03; Z01/L01 | Framing vs insulated ductwork; H | 0 mm; section 3; approved structural opening only via explicit exclusion | S1 if structural integrity affected; mechanical designer with structural lead; weekly and changed-source/pre-exchange rerun |
| SYN-C01 / R01 | SYN-ME R03 + SYN-ST R02; Z01/L01 | Installation envelope vs framing; C | 150 mm synthetic design requirement SYN-REQ-C01 R01; actual projects substitute verified requirement | S2; mechanical designer; changed dimensions/sequence and each comment round |
| SYN-A01 / R01 | SYN-ME R03 + SYN-AR R02; Z01/L01 | Equipment withdrawal envelope vs partition; A | 600 mm synthetic manufacturer requirement SYN-REQ-A01 R01; not an office-wide tolerance | S1 if safety/required access blocked, otherwise S2; mechanical and architectural designers; manufacturer/layout change |
| SYN-D01 / R01 | SYN-AR R02; Z01/L01 | Wall population vs itself; D | Exact duplicate investigation; same-element GUID pairs removed from comparison | S3 unless consequential defect; architectural lead; every Shared submission |
| Issue / source run | Location and elements | Viewpoint / assigned owner / due / status | Disposition and required closure evidence |
|---|---|---|---|
| SYN-ISS-001 / SYN-RUN-01 | Z01/L01; SYN-ST beam GUID ST-001; SYN-ME duct GUID ME-019; 12 mm penetration | SYN-VP-001 (synthetic ID); mechanical designer; Day 2; Open, S1 | Designer reroutes duct; structural lead confirms no unapproved opening. New SYN-ME R04; independent SYN-RUN-02 shows zero overlap and unchanged required access; then Ready for Review→Closed with dated checker record |
| SYN-ISS-002 / SYN-RUN-01 | Z01/L01; equipment ME-022 and partition AR-007; 520 mm free space vs 600 mm need | SYN-VP-002; architectural designer with mechanical lead; Day 5; In Progress, S2 | Move partition or redesign equipment arrangement under competent review; retain 80 mm shortfall in record; retest H and A with new exact models before closure |
These are fully specified planning examples and expected test outcomes. No model files, genuine element GUIDs, executed runs, designer signatures or client approvals were supplied; none are asserted. The private project copy must replace SYN values with actual evidence before rule activation.
A closed issue needs designer disposition, corrected revisions and an independent passing retest.
7. Run, triage, correct and independently close#
- Baseline the appointment, scope, information need and actual tool/build. Test a known intersection, compliant separation, access obstruction and deliberate duplicate. Confirm units, transform, precision and exclusion behavior.
- Freeze the federation manifest from approved Shared revisions. Each IFC source records schema, MVD and exporter build (office default IFC 4.0.2.1 Reference View; IFC 4.3.2.0 only by recorded approval after a passing test exchange; IFC2x3 only when an appointment or authority profile requires it) and a passing IFC validation report (buildingSMART IFC Validation Service or a qualified equivalent). IDS 1.0 results for information requirements are recorded separately, in the check sequence and record owned by BBM-STD-89 §5. A failing source is excluded and the coverage report shows the gap. [S08, S14, S15] Check coordinates against approved survey controls (at least 3 well-distributed control points plus elevation/unit probes), exact object/selection counts and scope coverage; unsupported provisional geometry is labelled and cannot certify installed accuracy.
- Execute enabled rules, including each required comment round and immediately before the affected exchange. Preserve selection/rule hashes and raw results. A changed model revision invalidates affected prior results and triggers interface regression checks.
- Group related findings by rule, unordered element pair and location. Keep one issue per design problem with child findings; preserve counts and raw IDs. Dismiss false positives only through evidenced exclusions. Never reduce the count by deleting uncomfortable issues.
- Competent designers agree the disposition and affected models/drawings/data. Raise a corrective action record if a baseline or process requirement is breached; link its cause, correction, prevention and verification to the issue.
- Producer completes L1 discipline QC: author and independent discipline checker identify themselves, close or formally withdraw every comment with evidence, and retain marked-up and clean sets.
- L2 cross-discipline review checks the revised federation, access, required information and model health. The issue owner sets Ready for Review with corrected revisions; a checker independent of the correction reruns the rule and affected interfaces.
- Only the checker records Closed after passing retest and designer approval. Reopen recurrence against the new run. A permissible accepted exception is a separate disposition with authority, expiry and residual owner; never mislabel it as geometrically resolved.
- L3 committee of discipline leads verifies L1/L2 evidence and records the gate outcome letter A, B or C (meaning per Glossary §1.5 and BBM-STD-93 §5) for the affected documents. Review tiers L1/L2/L3 and S1–S3 severities are defined once in BBM-STD-93 §8. The project manager releases after that technical decision and the required delivery-team authorisation. The appointing party's acceptance of the exchange remains a separate decision.
- Audit the record trail, not merely the model: sample closed issues, exclusions and decisions; record defects, lessons and corrective actions. Revise the next rule baseline through change control and retest.
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.
| Severity | Office response / deadline | Escalation and old-code migration |
|---|---|---|
| S1 Critical | Acknowledge within 4 working hours; target correction within 2 working days; immediately stop affected unsafe/release work | Escalate to discipline leads and project manager immediately; legacy C/priority 1 assessed for actual effect, not automatically “Low” by size |
| S2 Major | Correct within 5 working days or earlier gate | Escalate overdue or dependency-impacting issues; legacy H/priority 1 normally investigated here if not critical |
| S3 Minor | Correct or record permissible disposition before next gate | Legacy M/L/priorities 2/3 are reassessed; mandatory failures still block release regardless of severity |
A deadline extension requires a revised action plan, competent authority and affected-recipient notice; it cannot permit a binding safety/access failure. The office working calendar defines working hours/days. These S codes are issue severity, SU codes are suitability, and gate outcomes are the letters A/B/C; none are RACI responsibilities.
8. Self-check and adoption gate#
- Every applicable trade pair and meaningful object selection has approved rules or justified NA; no U, blank, empty unexplained set or missing clearance/access basis.
- Manifest IDs/revisions, units, transforms and tested builds match the delivered set. Exact rule/settings hashes and run evidence are retained.
- Exclusions have scope, approver, evidence, expiry and no forbidden safety waiver. Duplicate grouping preserves raw evidence.
- Every issue has elements, viewpoint, assignee, due date, severity, status and designer disposition. Closed records have corrected revision, independent retest and checker identity/date.
- Every applicable mandatory requirement passes; no required hard/access/safety failure remains in issued scope. Required L1/L2 and L3 decision precede project-manager release and separate recipient acceptance.
- A changed rule, model, requirement or manufacturer source is checked through impacted interfaces; suppliers receive the new baseline and acknowledge it.
Common failures: loading the most recent filesystem file instead of the approved Shared revision; excluding insulated geometry; testing empty sets; accepting the low issue count; converting every clearance into one distance; closing on a screenshot; treating priority as change authority; assuming a filename or browser Publish folder is formal release.
9. Correction trace and operational records still required#
| Research / gap / conflict | Present evidence in this revision |
|---|---|
| T10.1 | Sections 4–7: full trade scope, model/zone/revision manifest, frequency and change triggers |
| T10.2 | Section 3: separate H/C/A methods and approved requirement sources; no stage-derived tolerance |
| T10.3 | Sections 4–7: pair coverage, exclusions, duplicate grouping, severity and permissible disposition |
| T10.4 | Sections 5–6: issue/BCF IDs, GUIDs, viewpoints, ownership, dates and states |
| T10.5 | Sections 6–8: competent design disposition, independent retest, closure and recurrence evidence |
| O06 P1 / C06 / C11 | Conflicting 15/5 mm retired explicitly; correct stages; broken banner replaced; actor corrected; one rule table |
| O06 P2 / C04 / C07 | Versioned manifests, exclusions, issue links, release threshold, separate suitability/severity and acceptance |
| O06 P3 | Pair matrix generated from approved register; cardinality and NA coverage check specified |
| C02 / C03 / C08 / C10 / C12 / C16 | Shared naming/metadata; linked MIDP/TIDP; private provenance; survey/build qualification; competent safety authority |
Editorial revision is complete. Operational activation still needs the real appointment, tool qualification, approved source/selection/rule manifests, designer evidence, independent executed retests and release/acceptance records. Record them in the project copy; this method and synthetic examples are not proof those actions occurred.
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.
| Tag | Title | Publisher | Year / edition | URL / evidence |
|---|---|---|---|---|
| S01 | ISO 19650-1 — Concepts and principles | ISO | 2018, ed.1 in force; ISO/DIS 19650-1 ed.2 at stage 40.93, not in force | Catalogue; checked 2026-11-04 |
| S02 | ISO 19650-2 — Delivery phase of the assets | ISO | 2018, ed.1 in force; ISO/DIS 19650-2 at stage 40.93, not in force | Catalogue; checked 2026-11-04 |
| S04 | ISO 19650-4 — Information exchange | ISO | 2022, ed.1 | Catalogue / abstract |
| S05 | ISO 19650-5 — Security-minded approach to information management | ISO | 2020, ed.1 | Catalogue / abstract |
| S06 | ISO 19650-6 — Health and safety information | ISO | 2025, ed.1 | Catalogue / abstract |
| S07 | ISO 7817-1 — Level of information need: concepts and principles | ISO | 2024, ed.1 | Catalogue / abstract |
| S08 | ISO 16739-1:2024 — IFC 4.3.2.0 | ISO | 2024, ed.2 | Catalogue; checked 2026-11-04 |
| S13 | BCF 3.0 (bcfXML 3.0 and BCF-API 3.0); BCF 2.1 fallback | buildingSMART International | 3.0 final, 18 Jun 2021; 2.1 (2017) fallback | bcfXML v3.0 release; BCF-API releases; checked 2026-11-04 |
| S14 | IFC Validation Service | buildingSMART International | live service | Validation service; checked 2026-11-04 |
| S15 | Information Delivery Specification (IDS) 1.0 | buildingSMART International | v1.0 final, June 2024 | Releases; checked 2026-11-04 |
| S21 | RIBA Plan of Work 2020 | Royal Institute of British Architects | 2020 | Current resource page; 2020 template |
| G-C | Guidance C — Facilitating the CDE workflow and technical solutions | IMI Framework (formerly UK BIM Framework, renamed May 2025) | ed.1, September 2020; archived | Official PDF; resources; checked 2026-11-04 |
| S22 | DM circular 9-1-2 — BIM submission with new building permits | Dubai Municipality | 13 Oct 2023; applies from 1 Jan 2024 | Circular PDF; checked 2026-11-04 |
| S23 | DM circular 9-1-3 — BIM with building permits | Dubai Municipality | 15 Jan 2026; effective 1 Apr 2026 | Circular PDF; checked 2026-11-04 |
| S24 | EPSG:3997 WGS 84 / Dubai Local TM | EPSG registry (mirror) | current | epsg.io/3997; checked 2026-11-04 |
| P02 | Define Supporting Infrastructure for BIM Implementation | Penn State | v2.2, 2019 | BEP infrastructure chapter |
| B04 | OPDC BIM Guidelines | Smithsonian Institution | November 2024 | Guidelines; benchmark concepts only |
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
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-14 | First controlled markdown revision of the legacy spreadsheet |
| V0.2 | 2026-10-14 | Filename revision used by Manual/BEP links; header text not updated |
| V0.3 | 2026-11-04 | closure: header = filename version; IFC schema/MVD/validation before rules; trade alias → ROLE map via BBM-STD-93; BCF 3.0 (2021) with 2.1 fallback; DM permit route and CRS via BBM-STD-85/86; gate outcomes letters A/B/C; IMI Framework naming; references re-checked + cross-doc pointer pass |
| V0.4 | 2026-11-05 | §4.1 the full 91-pair office matrix: the 63 pairs outside the §4 illustration decided, no U left in the office baseline; rule owner by routing precedence and the C/A requirement rule |