BBM-STD-58-ARCHITECTURAL_MODELLING-V0.2 | Office standard | 4 November 2026 | V0.2 | 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 rows: authority area definitions table (3.1), room authority fields, classification/IFC entity column, ADM reference scope; IMI Framework naming; links to current set versions; spacing fixes + cross-doc pointer pass. |
1 Scope ownership and element rules#
This standard consolidates guides 24, 32, 33 and 34 for, and. The architectural discipline lead owns the architectural model and space brief; the structural lead owns structural design; specialist designers retain their design responsibilities. The independent architectural checker reviews source geometry, data, drawings and receiving results. Follow the Manual V0.5, BEP V0.5, BoD, EIR and LOIN, coordinates, templates, drawing outputs and property dictionary. The editable ARC pack contains Element rules, Spaces, Measurement, Phase views, Checks and Specimens, each with a blank form.
Before production allocate a RequirementID, purpose, stage, delivery milestone, element/space scope, author, checker and recipient. Specify geometry, alphanumeric data and documents separately; RIBA stage labels alone do not define a universal LOD. Concept massing may be sufficient for an approved early decision; spatial coordination requires located interfaces and openings; technical design requires the documented layers and interfaces needed for the selected output. Do not author redundant hidden detail. Required fire/accessibility or structural decisions still need the competent designer and applicable BoD criterion.
| Element scope | Required authoring controls | Purpose-led output check | Classification and IFC entity |
|---|---|---|---|
| Envelope and curtain assemblies | Parent host, grid/bay strategy, panel/mullion/door categories, corners and embedding; retain panel IDs | Count cells and category-specific objects; check cut host and joins in plan/section; distinguish grid size from clear glass size | Uniclass Ss/Pr code; IfcCurtainWall with IfcPlate/IfcMember/IfcDoor parts |
| Walls and partitions | Base/top constraints, offsets, thickness/layers, function, fire/acoustic sources, opening wrapping and ownership | Compare sections, room boundaries, type/instance data and specification; no duplicate structural core | Uniclass Ss code; IfcWall with PredefinedType per function |
| Floors ceilings and roofs | Profile, level/offset, layers, falls, edges, penetrations and drainage interfaces | Check thickness/edges/voids and approved slope basis; a render does not establish drainage performance | Uniclass Ss code; IfcSlab (FLOOR/ROOF), IfcCovering (CEILING), IfcRoof |
| Stairs ramps and rails | Levels, run/riser/tread/landing geometry, headroom, clear widths, handrails and guards | Dimension against BoD criterion/authority source; separate architectural finish from structural body quantities | Uniclass Ss code; IfcStair/IfcRamp/IfcRailing with flights |
| Doors windows and openings | Stable occurrence/host IDs, handedness, opening dimensions, sill/head, adjacent space references and schedules | Reconcile opening, frame and clear width meanings; verify door/panel category and host cut in all affected phases | Uniclass Pr code; IfcDoor/IfcWindow with IfcOpeningElement |
Every element and space row carries Classification_Code with ClassificationTable, ClassificationTitle and ClassificationRelease (Uniclass 2015 July 2026 release: Pr v1.43, Ss v1.43, SL v1.36, Ac v1.27, unless the EIR names another release) and the IFC entity with PredefinedType (ISO 16739-1:2024; exchange schema per). Spaces map to IfcSpace and a Uniclass SL code. BBM-STD-72 owns these property definitions; the Element rules and Spaces forms carry them as columns.
The supplied sources give methods, not an adopted project/build baseline. Record exact authoring/export/receiver builds, template revisions/hashes and selected profiles before native tests. Native fixtures below are specifications only; no RVT or accepted geometry is delivered.
2 Rooms spaces and brief trace#
Use one stable SpaceID per architectural space, with room number/name as controlled display attributes and location/level keys. A duplicate room number in the same approved numbering scope fails; do not change a stable ID merely because a displayed name changes. Record brief RoomRequirementID, use/occupancy source, design capacity, level, zone, phase, option, upper/lower constraints, computation height, boundary convention and responsible designer. Occupancy classification, occupant-load method and escape design are competent design decisions under BoD and BBM-STD-57, not inferred from model room name or floor area. Each room/space still carries the authority fields the competent designer populates, each joined to its BoD criterion ID (BBM-STD-12 FL-01..FL-04, AR-09/AR-10): OccupancyClass (UAE Fire & Life Safety Code of Practice, September 2018 edition, plus the emirate Civil Defence authority's amendments current at project start, recorded in the BEP), OccupantLoadFactor_Source (table/clause and edition used) and AccessibilityRequirement (the DBC accessibility provisions for Dubai, or the accessibility instrument named in BBM-STD-85 for other jurisdictions). BBM-STD-72 owns their dictionary entries; the model carries them, it does not decide them. Spaces and elements that evidence a green-rating credit also carry Rating_Credit_Ref (Al Sa'fat or Estidama credit; statutory minimums owned by BBM-STD-57 §2 and BBM-STD-85 §7).
Place rooms in valid bounded regions; review unplaced, unenclosed, redundant, overlapping and untagged records using itemised schedules and independent plan/section views. An unplaced brief space is retained as a declared unmet requirement with an owner, never hidden from the comparison. Check vertical extents and volume settings where analysis needs them. A room boundary height may intersect different geometry than the plan cut; record both rather than correcting only the graphic.
MEP spaces are separate discipline objects with their own identities; map them to the current architectural SpaceID and revision. Do not force one-to-one mapping where one analytical zone legitimately aggregates several rooms; record the relationship and calculation owner. Linked room-bounding settings, link transform, phase mapping and By Linked View behavior require deliberate tests. A visible linked wall does not prove a boundary is recognised. Identify the owning boundary element; do not draw compensating separators to hide a missing/wrong link without a reviewed exception. Record separators and their purpose, intersections and effect on adjacent rooms.
3 Area conventions and reconciliation#
Define the measurement before taking quantities. For each intended GFA, BUA, gross, net or room-area use, enter the exact jurisdiction/appointment definition, controlled edition/clause/page, measurement plane, boundary faces, included levels, wall/column/void/stair/balcony/plant/parking inclusions and deductions, unit, rounding, exclusions and accountable measurement owner. BBM-STD-57 controls jurisdiction adoption; BBM-STD-12 carries the selected criterion. Until that definition is confirmed, label the area as an explicitly defined office test quantity, not statutory GFA/BUA. Neither Revit's Gross Building/Rentable scheme names nor a room finish-face default certifies authority compliance. Never substitute a Dubai definition for an Abu Dhabi or DDA project.
3.1 Authority area definitions#
Fill one row per jurisdiction before any statutory area is reported. Clause numbers and inclusion/exclusion lists are copied from the controlled instrument at project start, never from this table's wording.
| Jurisdiction | Instrument (BBM-STD-51 §3 register ID) | Clause | GFA/BUA inclusions | Exclusions | Verified date |
|---|---|---|---|---|---|
| Dubai (DM) | Dubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 and any DM amending resolution in force at permit submission | Enter from the controlled edition | Enter from instrument | Enter from instrument | Enter at project start |
| Abu Dhabi (DMT/ADM) | Planning regulations for the plot and the ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04); planning-regulation edition not confirmed in this revision | Enter from the controlled edition | Enter from instrument | Enter from instrument | Enter at project start |
| Free zone / other (e.g. DDA) | Authority instrument assigned through BBM-STD-57 and BBM-STD-85 | Enter | Enter | Enter | Enter |
Use separate area schemes where definitions differ and a mapping table for source spaces and exclusions. Keep unrounded source values for comparison; round only the stated display. Compare like convention, phase, option, level and revision. Sum only disjoint quantities. Wall/circulation/void differences explain a net-to-gross bridge; they do not make two unlike totals equal. For the synthetic SYN-ARC58 fixture, an outer 10 m by 8 m rectangle is an office-defined gross test area of 80 m2. With uniform 0.2 m external walls the inner rectangle is 9.6 by 7.6 = 72.96 m2. Net rooms of 30, 25 and 17.96 m2 sum to 72.96; the wall footprint bridge is 7.04 m2. There are no internal walls/voids in this arithmetic fixture. The brief target for SpaceID SYN-SP01 is 32 m2 and the expected room is 30 m2: variance -2 m2, -6.25%. REQ--A permits absolute variance <=1 m2 for this exercise only; the result fails and needs redesign or authorised requirement change. None of these inputs is a code limit or measured model result.
4 Assemblies hosting materials and quantities#
Use approved native categories/types and reference levels; constraint changes are reviewed at dependent hosts, openings, rooms, quantities and drawings. Compound layers record material IDs, thickness, function, wrapping and junction strategy. Separate finish objects are permitted where required by sequencing or information purpose, with one explicit quantity owner: a finish cannot also be counted as the same compound layer. Use approved material IDs through the material owner; appearance does not prove thermal, fire or acoustic performance. Record joins and their order where they change visible edges or calculated volumes; review before/after sections and itemised quantities, not only a join warning count.
Set use-specific tolerance from an approved criterion with value/unit/source and uncertainty where relevant. Do not import a stage-based clash tolerance. Unsupported accuracy or a missing required value holds affected use. Native opening geometry, design clear width, access envelope and schedule dimensions are distinct fields; verify their mapping with the structural and MEP owners. Copy/monitor notices are coordination prompts; the architectural author must resolve actual level/grid/host changes against the shared coordinate baseline. Maintain the original condition evidence and a controlled change record.
5 Phases options and issued views#
Construction phases are separate from RIBA stages, CDE states and training phases. Agree the ordered timeline and record Phase Created/Phase Demolished, phase mapping for links, room phase and schedule filters. Retain existing elements; mark actual removals through demolition. Fix a modelling error through a reviewed correction rather than manufacturing demolition history. Record temporary elements created/demolished in one phase. A phase-filter name is insufficient: check explicit New/Existing/Demolished/Temporary display settings with known objects.
SYN-PH58 has Existing followed by Renovation. E01 retained wall appears Existing in the Renovation existing/new plan; E02 wall is created Existing/demolished Renovation and appears on the demolition output; E03 replacement is created Renovation and appears on the new-work output. T01 temporary work is shown only on its declared temporary/coordination output. Retained E01 must not appear as demolition merely because Show Previous + Demolished is selected. Test every status in each issued view/schedule and linked-model phase mapping.
Record option sets, option IDs, primary/secondary choices, accepted design decision and applicable rooms/tags/schedules. Freeze the selected option before issue; do not mix two options into an apparently complete area total or drawing set. Duplicate a design option only with traceable purpose; preserve required option comparison evidence before final acceptance. The view register records template, discipline/detail, phase/filter, option, crop/section box, links and sheet/container mapping. COORD views stay off sheets; issued DOC views use BBM-STD-67 controls.
6 Checks specimens and release#
The workbook is a usable author/check specification. Element rules records LOIN/BoD joins; Spaces records stable identities and brief trace; Measurement fixes scope and arithmetic; Phase views supplies explicit display expectations. Checks identifies criterion, method, scope, reviewer and evidence. Specimens defines isolated positive and intentional failure/retest cases; blank tabs provide reusable forms. Actual source hashes, builds, measured values, checker/date and evidence are entered at execution, not copied from expected outcomes.
Create a representative isolated specimen containing a wall/floor/roof junction, stair/opening, linked enclosure, the six-cell curtain assembly of guide 24 and Existing/Renovation/option views. Verify six curtain cells comprising five ordinary panels and one door cell without duplicate host geometry. Test a missing linked room boundary, wrong opening/host, duplicated finish quantity, mixed phase/option and the 32-to-30 m2 area discrepancy. Reset each adverse case from the positive baseline; retain failed evidence, correction and independent retest. For example, correcting SP01 to 32 m2 gives variance 0 and expected Pass for that criterion only; it does not certify the full model.
Before release reconcile required element/space scope, every mandatory applicable value, units/sources, opening ownership and all document references. Review native model, schedules, full sheets and critical details, then agreed exchange in the recipient build against the frozen source. Producer check, independent architectural/design review, submission authorisation, receiving information acceptance and authority approval remain separate records. Required failures hold the affected package. Retain original revision and notify affected discipline/recipient owners under one ChangeID; reopen and recheck the preserved baseline if rollback is needed. Editorial pack completion never represents native, design, authority or office adoption. These actual activities remain Not executed.
References#
- Office guides 24/32/33/34, Manual §6/8.2.1/9, BEP §8, /037/038 and prerequisite drafts linked above. Guide references to older Manual/BEP editions are teaching history; this standard uses the controlled W1/W2 interface.
- ISO 19650-1:2018 clauses 5/11; ISO 19650-2:2018 clauses 5.1.4/5.6/5.7 reading pointers, ISO 19650-3:2020 operational update context and ISO 19650-5:2020 security-minded scope. Paraphrased process context; no paid paragraphs reproduced or licensed compliance asserted.
- IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance Part 2, archived edition 5, explanatory only collaborative production/review and IMI Framework Guidance Part D, archived edition 2, explanatory only purpose-led requirements. ISO 7817-1:2024 is current researched LOIN context; BS EN 17412-1:2020 BSI record is predecessor context, retained if the appointment adopts it until controlled change.
- BCA Singapore BIM Guide v2 (August 2013), historic benchmark, section 4.1 and appendices A/C: discipline authoring benchmark, not UAE statutory requirements. Autodesk room area and linked boundaries describe versioned behavior needing adopted-build tests.
- DM circular index, ADM BIM Code of Practice (October 2020), building scope to confirm under BBM-STD-57 and its BBM-STD-51 §3 register entry (the ADM infrastructure documentation guideline is cited only in BBM-STD-63), DDA Final Design Approval. Checked 2026-10-16; exact project measurement/submission profile remains to be confirmed under BBM-STD-57. No universal GFA, egress or modelling tolerance is inferred.
- Current sources, checked 2026-11-04: IMI Framework resources (formerly UK BIM Framework, renamed May 2025); Uniclass 2015 July 2026 release; ISO 16739-1:2024; UAE Fire & Life Safety Code of Practice, September 2018; DM Administrative Resolution No. 225 of 2024 amending the DBC; DMT Abu Dhabi codes, 2013 edition. UAE requirement detail: BBM-STD-85.