BBM-STD-74-OPENBIM_PROFILES-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Purpose ownership and admission#
Use this pack to specify an exchange and prove that its intended recipient can use it. It covers, and. Manual V0.5 section 11 remains the exchange procedure owner; this standard supplies the profiles, mappings, fixtures and reports. It does not create another publishing route. Use BEP V0.5 sections 7.3 and 7.4, EIR and LOIN, federation, quality plan, dictionary and office register. The editable pack contains blank and synthetic populated records.
The exchange lead prepares the profile; discipline leads confirm scope and source truth; an independent checker checks outputs; the LAP authorises submission; the appointed receiving representative tests and accepts the scoped result. Record actual delegated functions, full builds, dates and decisions under BBM-STD-55 before production use. A validator report, file receipt or successful upload is not receiving acceptance. Native files and application tests are not executed by this editorial pack.
Use ISO 19650-1:2018 clauses 5 and 11 for requirements and collaborative production, ISO 19650-2:2018 clauses 5.1.4–5.1.5, 5.6–5.8 for methods, production, exchange and close-out, and ISO 19650-4:2022 for exchange-quality context. These are paraphrased reading pointers; check licensed editions before claiming conformity. ISO 19650-1:2018 and -2:2018 stay in force; their ISO/DIS revisions (stage 40.93 on 2026-11-04) are not in force. ISO 19650-3:2020 governs the operational interface and -5:2020 the sensitivity-led sharing context (security triage in BBM-STD-87).
Each ExchangeID is specified with the IDM method (ISO 29481-1:2025 methodology and format, ISO 29481-2:2025 interaction framework, ISO 29481-3:2022 data schema): process map, exchange requirement, actors and the IDS that checks it. Where a model must travel with linked documents (drawings, reports, certificates), ISO 21597-1/-2:2020 Information Container for linked Document Delivery (ICDD) is an optional container profile; it is used only when the receiver has qualified it. Office controls below are not asserted verbatim ISO requirements.
2 Profile and schema selection#
Allocate ProfileID/revision and link it to EIR child, ExchangeID, TIDP row, purpose, producer, recipient and object boundary. Record schema identifier including release/addendum, selected model-view/profile and its implementation reference, encoding, authoring/exporter/checker/receiver full builds, operating environment, preset hash, coordinate profile, dictionary revision, licences, security and exclusions. Do not fill unknown builds with a product year. Unverified support holds that route.
| Profile | Controlled selection | Scope and hold |
|---|---|---|
| SYN-X74-BASE R01 | IFC4 ADD2 TC1, IFC 4.0.2.1; IFC4 Reference View for reference coordination | Office default; model-view definition/version and actual tool builds must be pinned before native test |
| SYN-X01 R01 retained from BBM-STD-54 | IFC 4.3.2.0 (ISO 16739-1:2024) project candidate | Non-default; used only by recorded approval when the sender build and the receiver both pass a test exchange. The Revit IFC exporter 27.4.0.30 (30 Oct 2026) exports IFC4x3; use IFC 4.3 RV only after a test export from the project build passes the project IDS |
| Legacy or transfer route | IFC2x3 or qualified Design Transfer View, only when an appointment or authority profile requires it | Record exact schema/view/build; no promise of lossless native editing or interchangeability with Reference View |
| OPEN-4D R01 (optional) | IFC4 IfcWorkSchedule/IfcTask with IfcRelAssignsToProcess links to the scheduled objects, on the SYN-X74-BASE schema | Tool-neutral 4D schedule exchange requested by BBM-STD-79 when the programme moves between planning tools; qualified like any profile; does not replace the native programme |
| DM-PERMIT R01 | Dubai Municipality BIM permit submission (circular 9-1-2 of 13 Oct 2023; circular 9-1-3 of 15 Jan 2026, effective 1 Apr 2026) | Schema and export setup = the IFC schema and export setup stated in the current Dubai BIM Standard (buildindubai.gov.ae/bim), checked at project start and recorded in BEP; attributes = the Model Attribute Matrix issued with that standard (BBM-STD-72 DM-PERMIT mapping); openBIM IFC, zipped, upload limit as stated on the portal; validation route = the portal checks plus the §5.0 and IDS checks here. Applicability under 9-1-3: new buildings above G+12 or of 15,000 m2 or more, listed alterations (add/remove floors, +1,500 m2 or more, full redesign, change of main use, relocation on plot); other alterations submit a final BIM model before the completion certificate; drawings are extracted from the model. Owner: BBM-STD-85 and BBM-STD-57 |
Keep existing profiles distinct rather than editing a prior received header or reusing its ID with different semantics. ISO 16739-1:2024 and the buildingSMART 4.3 documentation are research references; neither mandates changing an appointment. A revision creates an impact assessment and qualification run. IFC schema identifiers in the actual header must match the adopted release; a generic IFC4 header alone does not establish every addendum or model-view requirement.
Adopt BBM-STD-63 coordinates and BBM-STD-64 link boundaries. The project CRS comes from the CRS register in BBM-STD-86 (Dubai: DLTM, EPSG:3997, vertical datum DMD; Abu Dhabi: the CRS stated in the ADM/DMT survey and CAD/BIM submission guideline for the plot, with vertical datum Ras Ghumays), recorded with EPSG code and transformation in BEP V0.5 §8.2; this standard repeats no CRS values. In IFC4 and IFC 4.3 the georeference is written as IfcMapConversion plus IfcProjectedCRS. Record model length units, property-specific units, project engineering frame, horizontal/vertical CRS and epoch where applicable, axis order, north, offsets, rotation, scale and control points. Model millimetres do not make airflow millimetres. An approved schema-specific georeferencing representation is required; IFC2x3 needs a separately agreed method and must not be assigned IFC4-only attributes. Compare multiple non-collinear control points and elevations in the receiver; do not reset the georeferenced export to zero to make it look aligned.
3 Entity property and identity mappings#
The Mapping sheet joins PropertyID, source definition/GUID, occurrence/type applicability, entity/predefined-type rule, destination property/classification path, datatype/unit/conversion, null treatment and checker. Maintain native UniqueId, IFC GlobalId and canonical Asset_ID as separate crosswalk keys. Preserve IDs for unchanged occurrences across consecutive issues; replacements get their own identity and explicit predecessor link. Duplicate IDs, silent entity fallback and omission of applicable mandatory information fail the affected exchange.
| Synthetic case | Expected source and destination | Check |
|---|---|---|
| AHU-001 | IFC4 candidate IfcUnitaryEquipment with AIRHANDLER predefined type; P72-001 Asset_ID → proposed custom BBM_Exchange.Asset_ID text | Receiver finds one AHU-001, joined to the same source identity and IFC GlobalId; entity/predefined type qualified against selected schema |
| AHU-001 design flow | P72-008 legacy AIR-FLOW text 1200 L/s → custom BBM_Exchange.DesignFlow_m3_s, IfcReal 1.2, explicit SI volumetric-flow unit m3/s | Parser rejects bare 1200; mapping records source unit and destination unit. This proposed custom property is not a standard IFC Pset |
| VLV-001 and VLV-002 | Candidate IfcValve occurrences; airflow not applicable under the narrow fixture | No invented zero airflow. Two distinct Asset_ID values and valid type/system/location joins |
| SYN-CAB01 classification | Classification_Code and SystemClassification_Code stay separate | Pr and Ss associations preserve exact table/release and verified codes under BBM-STD-72; no IFC class used as a classification code |
Actual standard IFC property mappings must be selected from the adopted schema/property documentation for the entity and value type. Use a custom property only with explicit semantics and recipient agreement. List excluded object categories, linked content, hidden internals, views, data and documentation with requirement-owner approval; omission is never inferred from visibility alone. No exclusion can waive a mandatory safety or appointment requirement.
4 Presets and model fixture specifications#
Export from a checked immutable source snapshot. Store the application-supported preset/configuration file beside its manifest, not merely a screenshot or descriptive name. Manifest fields are AssetID, kind, parent profile/revision, controlled URI, bytes/hash, author, approval, exact tools, dependencies, licence and qualification state. This workbook delivers a preset specification, not a vendor-loadable configuration. Native sender/receiver model files remain to be made in isolated approved host sessions; their specification is complete enough to reconstruct and check them.
The base fixture is the BBM-STD-54 three-asset SYN-ME01 scope: AHU-001 and VLV-001/002, same source R01 and fictional SYN-CRS01 local frame (origin 0,0,0, +X east/+Y north/+Z up, right-handed, millimetres, no geodetic tie). Specify a 1000 mm reference cube at the origin and control points (0,0,0), (10000,0,0), (0,10000,3000) mm. These added test objects are excluded from maintainable-asset counts and identified as test-only geometry. Expected cube size is 1 m in a metre-based receiver; the third point tests elevation as well as rotation. Test an asymmetric orientation marker and one approved linked-model transform separately. A successful synthetic frame does not validate real survey coordinates.
For reconstructable test geometry only, AHU-001 is an axis-aligned box with minimum corner (2000,2000,0) and dimensions (2000,1000,1500) mm; VLV-001 and VLV-002 are simplified boxes at (5000,2000,500) and (6000,2000,500), dimensions (200,100,100) mm. These envelopes do not purport to be manufacturer geometry. The asymmetric marker is an L with legs along +X 2000 mm and +Y 1000 mm, width 100 mm at (0,0,0). Linked specimen LINK74 contains a 1000 mm cube at its local origin; its fixture transform is +10000 mm X translation, +90 degrees counterclockwise about +Z viewed from above, unit scale 1. Its transformed local point (1000,0,0) is (10000,1000,0) mm. Record a separately allocated source UniqueId and valid IFC GlobalId per native object when built; these must not be invented as previously exported IDs.
Create R02 by changing AHU-001 design flow from 1.2 to 1.4 m3/s only; unchanged objects retain their crosswalk. Then reset to R01 and test a deliberate replacement VLV-002 → VLV-003, retaining predecessor relationship and issuing a new native/IFC identity. Record expected identity set, category counts, bounding extents, units, data values, document links, and exclusions before export. Preserve input/output hashes and actual comparison results. Wrong units, changed unchanged-object GUID, missing linked object, broken document and reflected/rotated origin are independent negative variants reset from the positive fixture. Do not make one broken fixture stand for every failure.
5 IDS authoring and audit#
5.0 IFC file validation. Before any IDS run, validate every IFC file for schema and normative-rule conformance with the buildingSMART IFC Validation Service or an equivalent qualified validator; record the validator, version, report and its hash in the Run report. A schema or normative-rule failure holds the exchange before the IDS run. This step proves file conformance only; project information rules belong to IDS.
Pin IDS 1.0 (buildingSMART final standard, June 2024) and its official schema release/hash unless the appointment names another; how each LOIN row becomes an IDS file is owned by BBM-STD-89. Name the IDS checker and its version in every report: independent research found five IDS tools disagreeing on classification facets, regular expressions and reporting, so a pass in one tool is not proof in another. Also pin supported IFC versions, requirement owner, linked EIR/LOIN IDs and checker/full build. Author separate applicability and requirement facets for entity, attribute, classification, property, material and part relationships only where supported by the selected IDS release. Specify cardinality and value restrictions explicitly. First validate the IDS XML against its pinned schema; then independently inspect meaning and run known positive and negative IFC cases. A syntactically valid IDS can select no objects and hide a missing population.
IDS74-01 requires a non-empty BBM_Exchange.Asset_ID on applicable maintainable AHU/valve occurrences, with a separate expected population check of three. A missing ID fails; an empty applicability population fails the independent population test. IDS74-02 targets the AHU flow requirement with explicit numeric/unit mapping qualified against the selected checker. A unique-ID cross-record check and 1200 L/s conversion comparison are independent tests, even if a checker offers extensions. Do not claim these are portable IDS functions without qualification.
The IDS asset record specifies its file URI/hash and schema audit, applicability count, expected/observed requirements, logs and independent reviewer; actual files and runs are Not executed. IDS does not establish source truth, geometric clearances, full coordination, regulatory compliance or successful FM ingestion. Run geometry, control-point, topology, mandatory access and document/use checks outside IDS. The fictional BBM-STD-54 access case requires 600 mm: 650 +/-10 has a 640 mm lower bound and passes; 605 +/-10 has a 595 mm lower bound and fails. It is a scenario criterion, not an office tolerance.
6 BCF interchange and permissions#
Select BCF XML 3.0 (final, 18 June 2021) and, only if an API route is contracted, BCF API 3.0 as separately qualified candidate interfaces; BCF 2.1 (2017) is the fallback only where a receiver cannot read 3.0. Do not treat them as the same transport or infer API support from ZIP import. Record exact extensions, endpoint/API version, authentication/permission method, client/server builds, status/type/priority vocabulary mapping, timezone convention and unsupported fields. Credentials never enter this pack. BBM-STD-50/Manual 10.3 remains issue procedure owner; BCF topic state does not independently authorise release.
| Test | Expected result | Evidence needed |
|---|---|---|
| Create and export SYN-BCF74-001 | Stable topic GUID, title, author/time, status, assigned role and source model/revision | Source record and exported package/API response hash; no completed real issue invented |
| Viewpoint round trip | Same camera type/location/direction/up, clipping planes, snapshot, selected/visible elements | Receiver screenshot and component GlobalId resolution against exact model hash; camera tolerance agreed by project purpose |
| Comment and state return | Added comment identity/time and mapped status survive return without duplicate topic | Reimport diff, server revision/conflict outcome and audit record |
| Model revision or missing component | Stale/missing GlobalId explicitly reported and reconciled | No silent reassignment to a visually similar object |
| Permission variants | Authorised participant may perform scoped edits; read-only/unauthorised role cannot write or expose restricted model/document data | Actual allowed and denied XML distribution/API route tests; redacted logs |
BCF is an issue/coordination exchange, not a complete model transfer or universal source of truth. Resolve concurrent changes, duplicate comments, unsupported extensions, missing images and unavailable models; never mark an issue resolved because a screenshot imported. Record XML/API cross-mapping losses and hold mandatory unsupported content.
7 Release evidence and open qualification#
Use the workbook Profile, Mapping, Preset, Fixture, IDS audit, BCF tests, Manifest and Run report blank forms. One RunID binds every input/configuration hash, selected builds, actual operator/date, expected/observed result, issue, independent checker, authorisation and recipient decision. Populate controls before execution, then capture logs and output hashes. The synthetic Run report describes wrong-unit failure, correction and required retest; all Actual fields remain Not executed. A planned successful retest is not an actual PASS.
Release only when every applicable mandatory geometry/data/document requirement passes, required access/safety failures are closed, dependencies resolve and the authorised recipient demonstrates the intended use. A rejected package remains immutable; corrected revision links ChangeID and prior run. No schema validation, coverage percentage, office draft review or proposed exemption substitutes for receiver acceptance. Exact tool builds, native presets/models, IDS files/checker outcomes, BCF round trips and actual adoption remain explicit activation holds.
References#
- Office source owners and gap trace: Manual V0.5 11; BEP V0.5 7.3–7.4; BBM-STD-54/63/64/68/72; matrix..080. Baselines remain drafts unless separately adopted.
- ISO 19650-1:2018, 19650-2:2018, 19650-3:2020, 19650-5:2020. Scope/edition checked 2026-10-16 and 2026-11-04; clause pointers above require licensed review. ISO 29481-1:2025, ISO 29481-3:2022, ISO 21597-1:2020, ISO 21597-2:2020, checked 2026-11-04.
- IMI Framework (formerly UK BIM Framework, renamed May 2025) resources and Guidance Part 2 edition 5, production/exchange explanation. Explanatory guidance, not UAE statutory requirements.
- ISO 7817-1:2024 and BS EN 17412-1:2020 predecessor. Purpose-led LOIN; contractual editions change only by approval.
- buildingSMART IFC 4.3.2.0 documentation, IDS specification and schema, BCF XML (v3.0 release, 2021-06-18), BCF API, IDS releases (v1.0 final, June 2024), buildingSMART IFC Validation Service, Autodesk revit-ifc releases. Live primary sources read 2026-10-16, re-checked 2026-11-04; adopt exact release/hash before execution. Research: Cerovšek & Omar (2025), Buildings 15(15) 2621 on IDS tool disagreement.
- IFC4 IfcUnitaryEquipment and predefined types: AHU entity/type candidate; actual exporter result still requires inspection.
- DM construction circulars, DMT infrastructure documentation v1.0 October 2020, DDA Circular 400 (held as a register row in BBM-STD-57; date and content not restated here); DM circular 9-1-2 and DM circular 9-1-3, checked 2026-11-04. Use BBM-STD-57 to verify current jurisdiction, submission service and exact profile; an OpenBIM workflow does not replace a required drawing submission.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: DM-PERMIT profile row in §2; IFC file validation step §5.0; CRS rule pointed to BBM-STD-86; IDS 1.0 pinned, LOIN-to-IDS owned by BBM-STD-89; IDM (ISO 29481) and ICDD (ISO 21597) in §1; optional OPEN-4D profile row for BBM-STD-79; IFC default per; BCF 3.0 (2021) with 2.1 fallback; links to Manual V0.4/BEP V0.5. + cross-doc pointer pass. |