BBM-STD-68-QUALITY_PLAN-V0.5 | Office standard | 5 November 2026 | V0.5 | Private controlled WIP draft for office review
Revision history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | Initial controlled WIP draft. |
| V0.2 | 2026-11-04 | Closed audit rows: 1.1 ISO 9001:2026 QMS basis with clause map and certification-transition note, ISO 10005/ISO 19011, sampling rule recorded as office decision, W3-C03 pointer to BBM-STD-11, Singapore guide marked historic; discipline codes per BBM-STD-93; QA share path; IMI Framework naming; current set links; spacing fixes + cross-doc pointer pass. + folder names without dots |
| V0.3 | 2026-11-04 | QMS patch (BBM-STD-96..98 links): placed inside the office QMS: BBM-STD-96 (manual and policy), BBM-STD-97 (procedures QP-01 to QP-15), BBM-STD-98 (KPIs). This standard is QP-08 "Drawing and model issue" and the information-quality sub-system; office-wide procedures are no longer described here. BIM checklist moved to 07-QA-QC/01-BIM. Decisions,. |
| V0.4 | 2026-11-05 | §2.1 warnings gate and blocking list WRN-01..WRN-11; §2.2 automation, evidence path and guide link per check; §2.3 office default tolerances in pass criteria; checklist rows corrected to the decisions (§2.4) |
| V0.5 | 2026-11-05 | Standard watch no. 1: ISO 19011:2026 (edition 4; 2018 withdrawn) cited in 1.1 and the references |
1 Controlled QMP and audit programme#
This standard closes writing gaps /072/073/076 and extends Manual V0.5 section 9. It uses BEP V0.5, EIR and LOIN, responsibility and appointment, BoD and existing MIDP/TIDP commitments. The QA/QC Lead maintains the project QMP with the Information Manager, who owns the quality framework; discipline leads own technical content, check competence and production QC; the BIM Coordinator maintains controlled automation and trend evidence. Appoint a reviewer independent of the work checked; record competence, scope and any conflict before testing. A technical committee process does not itself confer delivery authorisation or appointing-party acceptance. Auditor competence and independence follow ISO 19011 (guidelines for auditing management systems). This standard is the information-quality part of the office QMS: BBM-STD-96 holds the policy, scope, process map and RACI; BBM-STD-97 holds the office procedures (this standard is QP-08 there); BBM-STD-98 holds the quality objectives.
Before production, baseline QMP ID/revision/approver, project scope and stages, requirements and applicable jurisdiction/edition, check/population registers, risks, roles and actual controlled procedure IDs. The Procedures form locates document control (BBM-STD-97 QP-10), supplier assessment (QP-15), competence (BBM-STD-82), nonconformity and corrective action (QP-11), audit (QP-13) and management review (QP-14) with owner/revision/location; a procedure not yet adopted by the office is an assigned gap, never a fictitious approved ID. References to generic prior art do not substitute for office procedure adoption. Supplier-origin content undergoes the same scoped checks and source/licence/security controls.
1.1 QMS basis#
This QMP applies ISO 9001:2026 (edition 6, published 16 September 2026, replacing ISO 9001:2015 including Amd 1:2024) as its reference, without a certification claim, and is structured as a quality plan per ISO 10005. The office-wide clause map is in BBM-STD-96 §11; the table below covers this QMP only. Certification transition: Global ACI (successor of the IAF role from 1 January 2026) set three years; ISO 9001:2015 certificates are invalid after 30 September 2029 and new accredited certificates are issued only to the 2026 edition from 31 March 2028. The QMS owner records the transition audit date in the management review (BBM-STD-97 QP-14).
| QMP section | ISO 9001:2026 clause (harmonized structure; confirm against the licensed text before audit use) |
|---|---|
| 1 Controlled QMP, procedures | 7.5 Documented information; 8.4 Externally provided processes |
| 1 Competence of checkers and auditors | 7.2 Competence |
| 1, 4 Audit programme and independent assurance | 9.2 Internal audit; audit guidance ISO 19011:2026 (edition 4) |
| 1, 5 Management review (quarterly and at material incident) | 9.3 Management review |
| 2 Requirement-driven checks | 8.5 Production and service provision; 8.6 Release |
| 5 Nonconformity and corrective action | 8.7 Control of nonconforming outputs; 10.2 Nonconformity and corrective action |
| Whole office QMS (all other clauses, incl. 5.1.1 i) quality culture, 6.1.1-6.1.3 risks and opportunities, 6.3 e)-g), 9.3.2 c)) | BBM-STD-96 §11 |
| Procedures for proposals, design review, specifications, sustainability, submissions, supervision, document control, feedback | BBM-STD-97 QP-01 to QP-15 |
Use Plan-Do-Check-Act: approve criteria and resources; produce on controlled WIP revisions; undertake discipline QC, coordination and independent assurance; correct, independently retest and review recurrence. Retain weekly active-design QC, every coordination comment round/affected source or rule change, pre-gate intensives at T-3/T-2/T-1/T day, and independent assurance at each stage. QMS management review is quarterly and at material incident. Programme exact dates/windows, risk, responsible auditor and evidence with TIDP/MIDP. Existing MIDP review allowances remain planning minima; this standard introduces no new response SLA. Escalate overdue/high-consequence findings before affected delivery rather than marking an incomplete audit done.
Each audit run freezes ExchangeID, requirement/check revisions, source native/export/document manifest and hashes, tool/rule/builds, full population and exclusions, sample/selection rationale, producer/checker identities, dates, actual measurements, result, issues and separate decisions. Retain failed evidence with corrected revisions and retests in the approved project report/record structure and records schedule. Apply Manual §9.4 sensitivity, least privilege, controlled transfer and retained safety information; do not put live/client data into synthetic fixtures or public services. Information risk uses the adopted Manual 1-5 likelihood by 1-5 impact scale: 15-25 escalates; any unresolved mandatory failure blocks affected scope regardless of score. Specialist safety/design assessment remains with competent holders.
2 Requirement driven discipline stage and output checks#
Use the editable QMP and supplemental forms with the office BIM checklist BABOOM-BIM-STANDARD/07-QA-QC/01-BIM/BBM-STD-68-CHECKLIST-V1.0.xlsx, which is the model QC checklist that BEP V0.5 names (QA-CHECKLIST). The design content of the same package is checked with the design review checklist of BBM-STD-97 QP-03/QP-04 (07-QA-QC/02-DESIGN-REVIEW); neither checklist repeats the other. Before each actual run, add every applicable requirement, not only these examples. Each check has CheckID, exact requirement/LOIN and source revision/clause, discipline/stage/use, population/object/view/sheet IDs, mandatory applicability, method and approved criterion/unit/tolerance/uncertainty, designer/checker, source/output hashes and tool build, actual result/evidence, defect and retest. Explain zero-applicable results against the expected population; unexplained zero is Hold. N/A requires reason and scoped approval, never a shortcut for missing mandatory information.
At Stage 2 check purpose, programme, scope, primary systems and unresolved assumptions. At Stage 3 check coordinated spatial/analytical systems and interfaces. At Stage 4 check required detailed properties, buildability/specification/drawing consistency and exchange profile. These stages do not impose universal geometry detail or fabrication duties; actual appointment, EIR/LOIN, BoD and competent discipline criteria determine scope. Maintain the discipline categories ARC, STR, MEC, ELE (including ELV), PLU, FLS, INT and LSC, plus CIV and any other appointed discipline, using the codes in BBM-STD-93 (the legacy QA tab "ID" maps to INT), each stage and required schedule type, without inventing one generic pass for them all.
Architectural checks follow BBM-STD-58: room identity/enclosure, phase/level/linked boundaries, area method/provenance and plan/schedule joins. Structural checks follow BBM-STD-59: physical/analytical alignment, supports/loads, section mapping, rebar/tolerances, openings and independently checked analysis exchange. MEP checks follow BBM-STD-60: systems/connectors, flow/load/pressure units, equipment/spaces, slopes/inverts, access, penetration and protection interfaces. Numeric model agreement is distinct from design adequacy.
Coordinates and boundary/identity/source coverage use BBM-STD-63 and BBM-STD-64 before BBM-STD-50 clash tests. Families, details and materials use BBM-STD-69, BBM-STD-70 and BBM-STD-71 respectively. Preserve valued/referenced parameters and dependencies under BBM-STD-69; Manual hygiene wording is not permission for indiscriminate purge. Model health triages warning type, affected IDs and consequences; zero warnings from the blocking warning list WRN-01..WRN-11 (§2.1) are permitted at share, and every other warning is logged with count and disposition (BEP V0.5 §5.1.2/§10.2 A). Performance targets follow Manual V0.5 §11.3. The existing 300 MB investigation trigger is not a universal rejection limit.
Validate 100% of applicable mandatory geometry/data/document requirements; an average score cannot conceal one missing or invalid mandatory value. Check unique identities, dictionary datatypes/units/bindings, classification and native-to-export-to-recipient relationships, not just nonempty strings. Missing authoritative criterion or unsupported mapping holds that check. The workbook's numbers are declared synthetic criteria only, not design or jurisdiction thresholds.
All issued sheets receive production QC and final delivered-output inspection under BBM-STD-67 and BBM-STD-66: index/container/revision and title block agreement; annotations, keynotes, units and scale; coordinated plan/section/detail/schedule/specification; extents, fonts, lineweights, crops and missing references. Review the whole sheet and nine tiles for each output revision, plus measured scale/known dimension as required. A native view or a passing export script cannot establish the final PDF/CAD output. Keep full sheet/markups and disposition for each discrepancy.
2.1 Warnings gate and blocking warnings#
At share: zero warnings from the blocking list below. All other warnings: at most 100 per 10,000 model elements (element count from the Model Checker count of model categories), and no warning type above its count at the previous gate without a recorded disposition. The total is recorded at each gate (checklist MH-15, Manual V0.6 §9.2). Above the limit is a nonconformity S3 Minor with a correction plan before the next gate, not an automatic block. Basis: Autodesk publishes no per-warning performance benchmark and advises classifying warnings by risk and resolving the high-impact types; 100 per 10,000 is an office trend trigger.
| ID | Blocking warning (leading Revit warning text) | Why it blocks |
|---|---|---|
| WRN-01 | Highlighted walls overlap | Wrong room boundaries, areas and quantities |
| WRN-02 | There are identical instances in the same place | Double counting in schedules and IFC |
| WRN-03 | Room is not in a properly enclosed region | Room has no area or volume |
| WRN-04 | Multiple Rooms are in the same enclosed region | Duplicate room data and areas |
| WRN-05 | Area is not in a properly enclosed region | Area plan reports wrong totals |
| WRN-06 | Multiple Areas are in the same enclosed region | Duplicate area data |
| WRN-07 | Space is not in a properly enclosed region | MEP space has no volume for loads |
| WRN-08 | Multiple Spaces are in the same enclosed region | Duplicate space data |
| WRN-09 | Highlighted floors overlap | Double quantities and clash noise |
| WRN-10 | Room separation lines overlap | Unstable room boundaries |
| WRN-11 | Elements have duplicate "Mark" / "Number" values | Identity and schedule errors |
The template custodian confirms each leading text on a fixture in the qualified Revit build (BBM-STD-91) before the list is loaded in the office check set; a new entry needs a decision row first.
2.2 Check attributes: automation, evidence and guide#
Automation. auto = a rule-based tool (Model Checker checkset, IDS validator, naming regex, office script) returns pass/fail without judgement; assisted = a tool, schedule or report returns the data and a person compares it with the criterion; manual = inspection.
Evidence path (inside the project tree of Manual §12.1; the pack is 03-PUBLISHED/<NN-STAGE-N>/<YYYY-MM-DD-DESCRIPTION>):
| Checklist sheet | Evidence path |
|---|---|
| Model health; ARC; ID; LSC; STR | 00-PIM/02-SHARED/06-REPORTS/01-MODEL-HEALTH |
| MEP coordination | 00-PIM/02-SHARED/06-REPORTS/02-CLASHES |
| Data & IDS | 00-PIM/02-SHARED/09-NON-GRAPHICAL/02-IFC-VALIDATION; at issue also <pack>/04-REPORTS/00-IFC-VALIDATION |
| Information container | <pack>/04-REPORTS/01-NAMING-VALIDATION |
| Drawings & sheets | <pack>/04-REPORTS |
| Authority submission | 02-REG/00-PERMITS/01-BIM-SUBMISSIONS |
| Issue sign-off | <pack>/05-TRANSMITTAL |
| The completed checklist copy | 00-PIM/02-SHARED/05-DOCUMENTS/07-QA-QC |
Guide link (one guide per check, from the BBM-STD-21..37 set in BBM-STD-82):
| Checklist sheet / section | Guide |
|---|---|
| Model health / Set-up | BBM-STD-30 Setting up a building file (URS, levels, links) |
| Model health / File | BBM-STD-31 Enhanced workflow, clean data |
| Model health / Hygiene | BBM-STD-23 Bringing in CAD cleanly |
| Model health / Worksets | BBM-STD-22 Work sharing and collaboration |
| Model health / Families; MEP coordination / Families | BBM-STD-26 Introduction to families and parameters |
| Model health / Materials; ID / Finishes, Elements | BBM-STD-33 Finishes, phases |
| Model health / Integrity; ARC and ID / Rooms, Areas | BBM-STD-32 Rooms, areas and model quality control |
| Information container; Issue sign-off | BBM-STD-25 Project initiation worked example |
| Drawings & sheets | BBM-STD-28 Documentation, overrides, view templates and filters |
| Data & IDS | BBM-STD-36 Data control with schedules |
| ARC / Elements (stairs, ramps, railings); ID / Vertical | BBM-STD-34 Railings, stairs and ramps |
| ARC / Elements (curtain walls) | BBM-STD-24 Curtain walls and curtain systems |
| ARC / Elements (other) | BBM-STD-23 Complex walls |
| ID / Furniture, Fixtures; LSC / Softscape | BBM-STD-35 Importing families from outside |
| LSC / Site model, Hardscape | BBM-STD-30 Setting up a building file |
| STR / Members, Openings | BBM-STD-27 Families and parameters in practice |
| Coordination sections; MEP coordination (other sections) | BBM-STD-22 Work sharing and collaboration |
| Authority submission | BBM-STD-82 training module "Authority submission (e-permit)" (no BBM-STD-21..37 guide teaches it) |
The per-check values are held in the office rule table (S03); a guide revision updates the link, not the check.
2.3 Office default tolerances in pass criteria#
A stricter appointment, brief or authority value governs.
| Check | Default |
|---|---|
| MH-01, MH-02 | Native and IFC read-back of each of at least three control points within 10 mm horizontally and 10 mm vertically of the surveyed value, or the surveyor's stated control accuracy where coarser (BBM-STD-86 §5) |
| LS-01 | Topography within the survey's stated vertical accuracy, recorded in BEP §8.2 |
| AR-04 | Each room within ±5% of the brief area or ±1.0 m², whichever is greater, unless the brief states its own |
| AR-13, ST-06 | Zero open H failures at 0 mm and zero open C/A failures against each active rule's recorded requirement (BBM-STD-50 §3, §4.1) |
| ST-05 | Rebar and construction tolerances as stated by the structural engineer of record for the stage, recorded in the BEP |
2.4 Checklist rows aligned to the decisions#
The published checklist BBM-STD-68-CHECKLIST-V1.0 carries these corrected rows: DS-17 plotted text ≥ 2.5 mm on all sheets; DI-11 schema per; AU-01 circulars 9-1-2 and 9-1-3; AU-07 office preset EXP-DM-PERMIT-IFC4-<rev> on the Dubai BIM Standard 1.4 setup; MH-15 warnings gate (§2.1); MH-29 the four user worksets; Read me and tool paths in the NN-NAME folder form.
3 Read only inventory and legacy reconciliation#
On 16 October 2026 the three reported QA XLSX files were opened read-only from the existing QA share (now BABOOM-BIM-STANDARD/07-QA-QC; the three files are in its 98-ARCHIVE and the current BIM checklist is in 01-BIM, with the QMS checklists in 02-DESIGN-REVIEW to 09-AUDIT per BBM-STD-97). No share was saved or rewritten. QC-LEG-01 is BBM-QC-AR-00.xlsx,13141 bytes, SHA-256 ee161c6d01fef9bf20caaeb9a642f471b85587071b94e9890ca05848052a7bd5: Sheet1 has 83 rows/3 columns, row 2 DOCUMENT/ITEM/CHECK. It is a document/concept checklist including cover/index/title-block and drawing checks, not evidence of completed project acceptance.
QC-LEG-02 BBM-QC-QA-00.xlsx and QC-LEG-03 QC-QA-00.xlsx are byte-identical at 127049 bytes each, SHA-256 5cd64939680a4f5261afa2efec67fecd5c82fd5b04da90494c735af0d910245e. Their ten tabs are BIM Uses (49x9), General (74x9), ARC(115x9), ID(97x9), LSC(98x9), STR(104x9), MEC(114x9), PLU(115x9), ELE(110x9), Attribute List (12x5). Row 22 of check tabs uses ITEM, Category, Description, PLANNED STAGE, PRIORITY, EVALUATION LEVEL, VALIDATION, ACCEPTANCE LEVEL, REMARKS. Header rows carry project/model/stage, reviewer/approver dates and document revision. Inventory metadata is not a completed checklist audit.
Preserve both published files and identities; the QA/QC Lead and document controller must nominate the authoritative controlled template and record the other as an alias/history or independently appointed variant after checking ownership/use. Do not delete a duplicate merely because its bytes match. Supplemental forms supplied here add traceability/evidence fields and fixtures, not a replacement suite of discipline checkbooks. Join a legacy row by SourceBookID+SHA-256+sheet+row+ITEM plus its description, since an ITEM alone repeats across tabs. Read-only inspection found legacy scoring formulas and A/B/C/D acceptance text in E5; an average or those labels never override mandatory failures or map automatically to office gate A/B/C, NC-1/2/3, RACI or CDE suitability. Record conflict W3-C03 in the decision log; do not patch another owner's workbook.
Preserve original presentation, formulas, tables and extended validation when a future template owner makes an authorised revision in Excel; test calculations and allowed/denied entries against known cases before adoption. openpyxl warned that an unsupported validation extension would be removed on saving in a prior structural inspection; no source was saved. Do not round-trip the legacy source through this tool. Newly authored additive forms use supported explicit validations. The Field mapping form shows retained source fields and missing requirement, criterion, scope, hash, independent evidence and correction/effectiveness joins. Every populated real source row still needs its actual mapping.
4 Independent assurance coverage and sampling#
Maintain separate full production QC, mandatory full-population validation, independent risk-based audit and competent technical design review. For each discipline/stage independently sample min(total sheets, max (10, ceiling (0.10 x total sheets))) plus every safety-critical or changed high-risk item, counting overlap once. This sampling rule is an office choice, not an ISO requirement. Retain at least one model per discipline plus the federation and at least one schedule per required schedule type. Small sets below 10 are fully sampled; no required item disappears because it is outside the sample. Record total population manifest/revision, selection IDs and method/risk, sample and additional-risk union, reviewer and findings. A failure expands the relevant scope to potentially affected objects/sheets/dependencies and triggers documented retest.
Synthetic sampling examples:6 sheets require 6; 40 require 10; 180 require 18. For 40 choose S001-S010 as a stated illustrative systematic base sample; if S025 and S032 are the only extra changed high-risk/safety-critical sheets, the independent union is 12, including both. This is an arithmetic fixture, not a risk assessment. Production whole-sheet/nine-tile QC still covers all 40 issued sheets; applicable mandatory requirements cover their complete population. Select unbiased/risk-justified samples for actual work; never choose only clean sheets.
An auditor checks evidence reliability as well as result: reproduce a known failing fixture, verify rule applicability/population and independence, inspect model/sections/schedules and actual delivered sheets, and compare exports in the named receiving system. Automated/IDS property checks do not replace geometry, calculations, safety decisions, document quality or actual recipient acceptance. Retain source/profile/version changes and repeat affected/regression tests after changes. Evidence access may be restricted, but the authorised reviewer must still be able to verify it.
5 Nonconformity correction and sustained effectiveness#
On a finding, record NCID, audit/check/requirement, failed exact revision/hash/object/sheet scope, observed versus required and units, consequence/class, containment/blocking scope, owner and due date. NC-1 blocks affected gate/exchange until resolved and independently retested or a permissible scoped exception is recorded. NC-2 permits only expressly accepted nonblocking comments with owner, due and receiving conditions. NC-3 is minor and tracked. These classes are separate from issue severity S1 Critical/S2 Major/S3 Minor and its existing Manual SLAs; do not translate automatically. Retain linked PROJECT_LOG/issue IDs and escalate disputed scope to the designated authority. Information NCs use these fields and are logged in the one office NC log of BBM-STD-97 QP-11 (with design, site, authority and client NCs); KPIs K-NC-01/02 of BBM-STD-98 report them.
Correction repairs the specific artifact; corrective action addresses the verified cause and recurrence. Keep cause hypotheses separate from substantiated findings. Preserve failed source/report, create a new controlled revision, repeat the original check and justified affected/regression scope independently, retain measured results and evidence from source/output/receiver, then record scoped closure authority/date. A coloured markup, changed script or author checkbox is not a retest. Unverified correction stays open; do not replace failed evidence or relabel an old revision.
A permissible exception needs requirement/source, exact scope/revision, consequence, alternative control, expiry/review trigger, owner, appointment-defined authoriser, recipient concurrence and competent design/safety concurrence as relevant. Mandatory legal/safety duties cannot be waived by the LAP. If permissible authority is unknown or a mandatory duty remains unsatisfied, Hold; no blanket waiver or inferred approval from a score. Separately retain sharing approval, discipline technical decision, delivery authorisation and actual appointing-party/operational recipient acceptance. Rejected downstream evidence reopens relevant findings.
For systemic/recurrent failures raise CARID linked to NCs, verify cause with evidence, plan action/owner/date and representative isolated pilot, update standards register/training/dependencies through ChangeID, preserve rollback and independently retest. Plan effectiveness method, monitoring period/population and reviewer before closure; assess subsequent controlled batches and recurrence/overdue trends at quarterly/material-incident management review. The synthetic CAR proposes two subsequent batches as a test specification only; the QMS owner must approve actual risk-based period/coverage. Successful immediate retest does not establish sustained effectiveness.
6 Blank forms and synthetic defect retest specification#
Every workbook register has a populated synthetic example and a genuinely empty Blank tab. QMP and Procedures control the programme; Inventory and Field mapping extend existing checkbooks; Checks, Sheet review and Sampling define scope/evidence; NC, Retests and CAR maintain failure-to-effectiveness lineage; Acceptance keeps decision functions separate. Entries are editable, headers frozen and filtered, and status dropdowns aid entry only. Enter actual values, IDs, hash, dates, competent holders and evidence before any real Pass or signature.
SYN-EX68 R01 has a fictional four-object asset population O1/O2/O3/O4 with required unique Asset_ID values A01/A02/A02/A04: four nonempty values but three distinct, so Q68-T01 expects Fail, NC-SYN68-01 and held affected exchange. R02 changes O3 to A03; Q68-T02 expects four distinct values and four receiver assets with source/tag/schedule joins, subject to actual native/export/receiver verification. Neither run has been executed. A checker deliberately scoped to zero assets expects Hold against the declared population 4. A duplicate may not be concealed by another optional-data score.
A separate sheet fixture Q68-T03 compares S025 R01 to its R02 issue index: expected Fail even if graphic appearance is attractive. Q68-T04 regenerates a coherent R02 sheet and index and repeats full-sheet/nine-tile/scale/tag/schedule review, expected Pass only if all stated checks succeed. Q68-T05 adds the two risk sheets to the ten-sheet independent base sample, expected 12, while mandatory/production QC stays complete. An omitted risk sheet expects Hold. Retests preserve each predicted failed and corrected attempt and separate actual unmeasured values, evidence and decisions. No actual project defect, approved correction, native execution, signed audit, office adoption or accepted receiving exchange is represented by this editorial pack.
References#
- Office Manual V0.5, BEP V0.5, Glossary V0.3, BBM-STD-51/54/55/57/63/65/67/72, BoD BBM-STD-12 and MIDP/TIDP V0.3 are controlled prerequisite owners. Synthetic IDs above create no office adoption, appointment or native acceptance.
- ISO 19650-1:2018, clauses 5/11; ISO 19650-2:2018, clauses 5.1.4/5.6.3/5.6.4/5.7, are reading pointers for requirements, container checks, content review and exchange. ISO 19650-3:2020 addresses operational update context; ISO 19650-5:2020 security-minded lifecycle context. Public catalogues/guidance support scope and pointers, not a licensed clause conformity audit; no paid paragraphs copied.
- IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance Part 2, archived edition 5, explanatory only and IMI Framework Guidance Part D, archived edition 2, explanatory only inform purpose, responsibilities and review. ISO 7817-1:2024 is the current researched LOIN concepts reference; BS EN 17412-1:2020 BSI record is predecessor context. Preserve an adopted appointment edition until controlled change.
- BCA Singapore BIM Guide v2 (August 2013), historic benchmark, section 4 and appendices A/C, is a discipline/coordination benchmark. Its foreign statutory rules are not UAE mandates.
- DM circular index, ADM Code of Practice October 2020 sections 3.2/3.3, and DDA Final Design Approval, checked 2026-10-16, are separate jurisdiction interfaces. BBM-STD-57 must establish actual plot/authority/edition/profile before use; the ADM BIM Code of Practice is recorded once, with its verified scope and issue, in the BBM-STD-51 §3 edition register and applied only as BBM-STD-57 and BBM-STD-85 assign it; Dubai permit BIM (DM circulars 9-1-2 and 9-1-3) is profiled in BBM-STD-85. No UAE-wide threshold, calculation criterion or legal advice is supplied.
- ISO 19650-4:2022 catalogue informs exchange decision/quality scope, not an executed conformity claim. UK Part 2 ed 5 pages 63-65 distinguish container checks under 5.6.3, content/sharing review under 5.6.4 and delivery-team model review under 5.6.5; these do not eliminate competent design checks.
- Existing rev 1/D06 QAQC and D16 QMP inform additive traceability, failed/retest and PDCA procedures. Manual §9 and current office prerequisites control office application. ISO 9001:2026 is applied as reference (section 1.1); no certification claim is made.
- Current sources, checked 2026-11-04: ISO 9001:2026; ISO 10005 (quality plans) and ISO 19011:2026 (auditing management systems, edition 4; the 2018 edition is withdrawn, checked 2026-11-05), editions per the BBM-STD-51 §3 register; IMI Framework resources (formerly UK BIM Framework, renamed May 2025). Codes: BBM-STD-93.
- Office QMS: BBM-STD-96, BBM-STD-97, BBM-STD-98; checklists
BABOOM-BIM-STANDARD/07-QA-QC/01-BIMto09-AUDIT. Global ACI transition requirements for ISO 9001:2026: https://sys.global-aci.org/uploads/documents/TECH-3-TR_2029-09-30_(M)_ISO_9001_2026_Transition_v1_12.pdf, checked 2026-11-04.