BBM-STD-89-LOIN_TO_IDS-V0.1 | Office standard | 4 November 2026 | V0.1 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-11-04 | First issue: closes rows,,, (IM-04 IDS source),,,,,, (validation report),,, (LOIN-to-IDS content; §1.2 gap 7 IDS part; §1.3 row "LOIN-to-IDS information requirements"; research R1, R2) + cross-doc pointer pass: BBM-STD-51 §3 register IDs cited (ED-ISO7817-1, ED-IDS, ED-IFC-VALIDATION); internal IDS IDs such as LSC-IDS-<rev> mapped to the issued file name |
1 Purpose ownership and scope#
Information requirements are specified in level-of-information-need (LOIN) terms per ISO 7817-1:2024 (which replaces EN 17412-1:2020; register rows ED-ISO7817-1 and ED-EN17412-1 in BBM-STD-51 §3) and checked by machine where a machine check is reliable. BBM-STD-54 owns the LOIN tables per exchange; this standard owns how each LOIN row becomes a buildingSMART IDS 1.0 file (June 2024, register row ED-IDS), how that file is named and checked, and what IDS cannot check. BBM-STD-74 §5 owns IDS authoring and audit records per profile and cites this standard for the rules below.
Research basis. IDS covers mostly alphanumeric needs; LOIN is wider (Akbas, Bolpagni, Borrmann et al., ITcon 2025, R1). Five IDS tools disagreed on classification facets, regular expressions and reporting (Cerovšek & Omar, Buildings 2025, R2). Therefore: specify in LOIN terms, use IDS for the alphanumeric checks it can express, check geometry and documentation by other named means, and name the checker and its version on every result. A pass in one tool is not proof.
2 ISO 7817-1 facets#
Every LOIN row states its prerequisites (purpose, information delivery milestone, actor sending and receiving, object) and then the information facets. Use these columns in BBM-STD-54 §3 (not RIBA stage, LOD or LOI labels).
| Group | Facet | What the row states |
|---|---|---|
| Prerequisites | Purpose / milestone / actors / object | Why, when, from whom to whom, which object type or element |
| Geometrical | Detail | How simplified or detailed the shape is |
| Geometrical | Dimensionality | 0D, 1D, 2D or 3D |
| Geometrical | Location | Absolute or relative placement and its reference (CRS record, BBM-STD-86) |
| Geometrical | Appearance | Symbolic or realistic representation |
| Geometrical | Parametric behaviour | Whether shape is driven by parameters or fixed |
| Alphanumerical | Identification | Name, type, classification code (Classification_Code), Asset_ID |
| Alphanumerical | Information content | Properties, units, allowed values, data source (e.g. Fire_Rating as integer minutes) |
| Documentation | Documents | Documents that must accompany the object (datasheet, certificate, manual), by document type |
3 One IDS file per exchange#
| Rule | Detail |
|---|---|
| I1 One file per exchange | Each exchange (EX-nnn in BEP §7.4) gets one IDS 1.0 file holding all its machine-checkable LOIN rows; one IDS specification per LOIN row, carrying the LOIN row ID in its identifier |
| I2 Version pinned | IDS 1.0 (buildingSMART, June 2024), schema file and hash recorded, unless the appointment names another release |
| I3 IFC version stated | The specification ifcVersion equals the exchange profile: IFC4 for the office default IFC 4.0.2.1 Reference View; IFC4X3_ADD2 only for an approved IFC 4.3.2.0 profile; IFC2X3 only where an appointment or authority profile requires it |
| I4 Info block | title = exchange ID and name; version = file revision; author = office role address, not a person; date; purpose and milestone = the LOIN prerequisites; description names the BBM-STD-54 table revision |
| I5 Fixtures | Each file ships with one IFC fixture that must pass and one that must fail per specification; both are kept with the file |
| I6 File check | The IDS file itself is checked with the buildingSMART IDS Audit tool before release; a file that fails the audit is not issued |
| I7 Authority profiles | Dubai permit attributes (Model Attribute Matrix of the current Dubai BIM Standard) are a separate IDS file per BBM-STD-85 §3, held until that matrix is obtained from the official source |
File naming. An issued IDS file is an information container named with the external 8-token grammar CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ids, with TYPE and ROLE codes from BBM-STD-93, revision per container and suitability per. Inside the CDE metadata it carries the exchange ID (EX-nnn) and the BBM-STD-54 table revision. Short internal IDs used in discipline standards (e.g. LSC-IDS-<rev> for landscape plant, area and irrigation checks in BBM-STD-61 §5, AIR-IDS-<rev> in BBM-STD-52) are CDE metadata aliases of the issued 8-token file, never issued names themselves.
4 Facet-to-IDS mapping#
| ISO 7817-1 facet | IDS 1.0 facet (applicability or requirement) | Machine check | Other check needed |
|---|---|---|---|
| Object (prerequisite) | entity (IFC class and predefined type), with classification or property in applicability to narrow the set | Yes: selects the objects in scope | Population count check: the expected number of objects is stated separately, because an empty selection passes silently |
| Identification | attribute (Name, Description, Tag), classification (system + code), property (Asset_ID) | Yes | Check the classification system and release against the project register; tools differ on classification matching (R2) |
| Information content | property (property set, base name, data type, value or pattern), attribute, material | Yes, for presence, data type and allowed values | Correctness of a value against the design (e.g. a true fire rating) needs competent review |
| Location | partOf (spatial containment or aggregation, e.g. in a storey or space) | Partly: containment only | Coordinates and placement: BBM-STD-86 §5 control-point check |
| Detail, dimensionality, appearance | None in IDS 1.0 | No | Model check rules and visual review in the named checker (BBM-STD-50, BBM-STD-68) |
| Parametric behaviour | None | No | Native model or family review (BBM-STD-69) |
| Documentation | Property or attribute holding a document reference, presence only | Partly | Document register check: the document exists, is the right revision and is accepted |
Cardinality: required, optional or prohibited per facet as IDS 1.0 allows. Regular-expression value patterns are kept simple and tested on the fixtures in two checkers before release, because tools disagree on them (R2).
5 Check sequence and record#
| Step | Check | Record |
|---|---|---|
| C1 IFC file validation | Each IFC file is checked for schema and normative rules by the buildingSMART IFC Validation Service (register row ED-IFC-VALIDATION, or a qualified equivalent with its version recorded) before any IDS run. A failing file holds the exchange; IDS is not run on it | Validation report per IFC file, report hash, date |
| C2 IDS check | Run the exchange's IDS file in the named checker | Checker name and exact version, IDS file name/revision/hash, IFC file name/revision/hash, pass/fail per specification, population counts |
| C3 Second checker (approval exchanges) | For contractual or authority exchanges, repeat C2 in a second named checker; any disagreement is resolved by inspecting the IFC, not by choosing the passing tool | Both results and the resolution |
| C4 Non-IDS checks | Geometry, location, documentation and parametric checks from §4 | Check IDs and results |
| C5 Decision | Producer check, independent verification and recipient acceptance stay separate records (BBM-STD-54 §6) | Decision, actor, date |
Neither the Validation Service nor IDS proves geometry, access, safety or code compliance. Sensitive models are not uploaded to an external validation service unless the triage in BBM-STD-87 allows it; otherwise use the qualified offline equivalent. Candidate checkers (each needs its version recorded and the office fixtures passed before use): IfcOpenShell IfcTester, and the IDS-capable checking functions of the office's qualified coordination tools per BEP §9.2.
References#
- ISO 7817-1:2024, edition 1 (replaces EN 17412-1:2020): https://committee.iso.org/standard/82914.html, checked 2026-11-04.
- buildingSMART IDS 1.0, final standard, June 2024 (tag v1.0.0, 3 Jun 2024): https://github.com/buildingSMART/IDS/releases; schema https://github.com/buildingSMART/IDS (Schema/ids.xsd), checked 2026-11-04.
- buildingSMART IDS Audit tool: https://github.com/buildingSMART/IDS-Audit-tool, checked 2026-11-04.
- buildingSMART IFC Validation Service: https://technical.buildingsmart.org/services/validation-service/, checked 2026-11-04.
- ISO 16739-1:2024 (IFC 4.3.2.0): https://www.iso.org/standard/84123.html, checked 2026-11-04.
- R1 Akbas, Bolpagni, Borrmann et al. (2025), Integration of LOIN and IDS, ITcon 30, 731–744: https://doi.org/10.36680/j.itcon.2025.030.
- R2 Cerovšek & Omar (2025), Ontology-based framework and IDS evaluation, Buildings 15(15) 2621: https://www.mdpi.com/2075-5309/15/15/2621.
- Office: BBM-STD-54, BBM-STD-74, BBM-STD-86, BBM-STD-93; settled decisions,,,,,,,.