ArchHubBABOOMDownload

Exchange information requirements and purpose-led LOIN

BBM-STD-54 · V0.2 · Define LOIN for each purpose, delivery time, actor/recipient and object scope.

Download WordFormsAll standards

Ribbon tools that apply it: IFC Class Auditor, IDS Check on IFC, Coord Views, Point Cloud

BBM-STD-54-EIR_AND_LOIN-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review and adoption

1 Scope tender and appointment control#

Exchange information requirements (EIR) specify the information to be delivered under an appointment, its purposes, timing and acceptance. This pack covers and. The appointing-party Information Manager prepares the scoped specification with its requirement owners; only the authorised appointing function incorporates it into a tender/appointment. A lead appointed party allocates relevant downstream EIR and may add its own needs while retaining upstream traceability. A BEP response does not silently amend EIR.

Use OIR, AIR, PIR, register controls, roles, BEP, MIDP, TIDP, LOIN to IDS and CRS register. The editable EIR and LOIN pack provides tender particulars, blank/populated schedules, bidder responses, property mapping, synthetic payloads and recipient tests. BBM-STD-56 is the next protocol interface, not an executed contract.

Appointment form groupRequired particulars
Identity and scopeAppointment/tender ID, parties/functions and delegated authority, EIR revision/status, applicable PIR/AIR/OIR, project/asset boundaries, uses and exclusions
Standards and methodsExact adopted editions/revisions (BBM-STD-51 §3 register IDs), information standard, container naming/metadata, CDE route, federation, quality/review and exchange methods
CoordinatesProject CRS: EPSG code and transformation, vertical datum, units, and BBM-STD-86 CRS register ID/revision (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, vertical datum Ras Ghumays)
Authority exchangeWhere BBM-STD-57 records an authority BIM permit route: the SYN-X-AUTH profile (section 4), attribute-matrix revision and portal validation evidence
DeliveryRequirement/exchange/milestone and delivery IDs, purpose-led LOIN, formats/schema/build/profile, dependencies, source/dictionary revisions, dates and role commitments
Security and rightsSensitivity assessment and security triage per BBM-STD-87, authorised recipients and downstream uses, permitted licences, denied-access tests and retention owner; no credentials in forms
Health and safety informationISO 19650-6:2025 (ED-ISO19650-6): hazard register fields, exchange points and owner, per BBM-STD-88
Bidder responseResponse/clarification dates, compliance per requirement, proposed method/resources, evidence, exceptions and priced matters handled outside this pack
AcceptanceIndependent production check, scoped submission authoriser, recipient checks/evidence, appointing-party decision, rejection/correction and change process

The fictional SYN-APP01 example is a mechanical replacement-design information appointment only. Tender clarification/response dates 2026-10-20/23, delivery 2026-11-26 and receiving review by 2026-12-01 are scenario assumptions. No fee, procurement award, software entitlement or real appointment is established. Actual commercial particulars and legal incorporation remain with their owners.

2 Requirement and exchange trace#

Keep EIR-007 as the operational AIR-007 allocation. This pack establishes proposed EIR-011 R01 as the delivery-coordination parent for PIR-007 R01 / OIR-007 in the replacement-design example. AIR-007 is a related asset interface, not transferred project ownership. EIR-011-G, EIR-011-A and EIR-011-D are unique child requirements for model, schedule and note; they map the existing EIR--M01/M02/M03 aliases without renaming them. CH-SYN-BASE01 labels the initial fictional R01 fixture, not office adoption.

Child / existing aliasExchange and delivery milestoneResponsibility and LOIN
EIR-011-G / EIR--M01EX- / DEL-SYN-ME01 / ME-01SYN-MA01 producer; SYN-MC01 checker; PR-SYN-ME01; LOIN-SYN-ME01 R01
EIR-011-A / EIR--M02EX- / DEL-SYN-ME02 / ME-02SYN-MA02 producer; SYN-MC02 checker; PR-SYN-ME02; LOIN-SYN-ME02 R01
EIR-011-D / EIR--M03EX- / DEL-SYN-ME03 / ME-03SYN-MA03 competent designer; SYN-MC03 independent designer/checker; PR-SYN-ME03; LOIN-SYN-ME03 R01

The exchange review and acceptance criteria follow ISO 19650-4:2022 (ED-ISO19650-4; reading pointer, as in BBM-STD-50). All three rows use SYN-LAP01 for scoped submission authorisation, SYN-RR01 for receiving review/recommendation and SYN-AP01 for information acceptance and the separate DEC- project decision. Actual delegation must be established under BBM-STD-55. The design team retains its design responsibility; information acceptance is not statutory approval or a guarantee of design adequacy. This narrow example does not purport to satisfy all project or operational EIR.

3 Purpose-led level of information need#

Define LOIN for each purpose, delivery time, actor/recipient and object scope. Specify geometry, alphanumeric information and documentation separately, including explicit exclusions, using the ISO 7817-1:2024 facets: geometry by detail, dimensionality, location, appearance and parametric behaviour; alphanumeric by identification and information content; plus documentation. Do not infer one universal LOD for a whole stage or require unused detail. The facet definitions and their mapping to IDS facets are owned by BBM-STD-89 §2/§4. ISO 7817-1:2024 (ED-ISO7817-1) is the current concepts reference; BS EN 17412-1:2020 is a withdrawn predecessor and must not be silently replaced in an existing appointment. The standards register controls adoption and licensed-text review.

LOIN row, purpose and object scopeMilestoneActor (producer → recipient)Geometry: detailGeometry: dimensionalityGeometry: locationGeometry: appearanceGeometry: parametric behaviourAlphanumeric: identificationAlphanumeric: information contentDocumentation
ME01 spatial/access coordination; Z01/L01, AHU-001 and VLV-001/002 plus routes/interfacesEX- / DEL-SYN-ME01Mechanical team → coordination/design recipientLocated equipment extents, insulated routes, connections/support interfaces and explicit task envelope; no fabrication detail3DSYN-CRS01 frame; exact source model R01Not requiredNot requiredStable native GUID/Asset_ID mapping; type, system and locationApplicable class, units and source references; three unique maintainable assetsNative/IFC manifest and known-value/count comparison; hard/access/interface outcomes and design note
ME02 equipment selection/service-planning review; same three assetsEX- / DEL-SYN-ME02Mechanical/data producer → designated design/asset reviewerNo new geometryNone (link only)Exact model identity/location linkNot requiredNot requiredAsset_ID, Class, Type, System_ID, Location_IDApplicable flow/diameter, AccessNeed_mm, instruction/source revision; valid class-specific N/AItemised CSV and readable PDF from one snapshot; key/count/value reconciliation
ME03 design-basis/access decision; same zone/assets/interfacesEX- / DEL-SYN-ME03Competent designer → independent/cross-discipline reviewersDimensioned critical viewpoints2D viewpoints taken from the 3D modelTied to source model revisionNot requiredNot requiredRequirement and source IDsAssumptions/uncertainty, residual-risk owner/action date and changed interfacesTechnical note, evidence/issue index and dispositions; required source links open

For SYN-REQ-A01 R01 only, withdrawal task envelope is 600 mm. The fictional positive clear dimension 650 mm with bounded +/-10 mm has lower bound 640 mm; negative 605 mm has lower bound 595 mm and fails. These are scenario fixtures, not a generic clash/access tolerance or surveyed/installed evidence. Required routes and interfaces remain in ME01 scope; no complete native model is created by this writing task.

4 Discipline profiles properties and applicability#

SYN-X01 R01 is the existing fictional native.rvt plus IFC 4.0.2.1 (IFC4 ADD2 TC1) Reference View building-coordination profile, the office default (ED-ISO16739-1). IFC 4.3.2.0 (ISO 16739-1:2024) may replace it only by a recorded approval ID when the sender's exporter build and the receiver both pass a test exchange (Revit: IFC 4.3 RV only after a test export from the project build passes the project IDS; supported releases in BBM-STD-91). IFC2x3 is used only when an appointment or authority profile requires it. SYN-X02 R01 is the schedule profile: UTF-8 CSV, comma delimiter, quoted strings when needed, exact Dictionary field order/names, dot decimal, exported dates ISO 8601 if added by an approved extension; readable PDF from the same snapshot. SYN-X03 R01 specifies the PDF design/access note with linked issue records. Actual native full build, exporter/preset, recipient application/build, IFC support, document/issue schema and round-trip behavior remain Unverified and hold actual issue. A schema name or an expected positive fixture is not installed support.

The workbook dictionary defines every field in its Design payload. It reuses AIR stable identity and class-specific flow/diameter meanings while adding design-purpose type, GUID mapping, access requirement and source fields. SYN-X02 is a project mapping, not an approved BBM-STD-72 global dictionary/shared-parameter file. Every EIR property references its BBM-STD-72 dictionary ID, carrying the ISO 23386:2020 definition attributes (ED-ISO23386), and a bSDD URI where one exists; data templates follow ISO 23387:2025 (ED-ISO23387). Classification is excluded from this narrow fixture because no decision requires it; where required by actual EIR, use Classification_Code with ClassificationTable/Title/Release, the exact table/release (ED-UNICLASS) and validated codes before issue. No invented classification code fills a gap.

SYN-CRS01 is a fictional local engineering frame: origin (0,0,0), +X east/+Y north/+Z up, right-handed, geometry millimetres; no geodetic tie or existing-condition/survey claim. An actual EIR names the project CRS in the Coordinates particular (EPSG code, transformation, vertical datum, units and the BBM-STD-86 register ID/revision) and reconciles survey/CRS transformations, linked models and units with their owning lane before exchange; survey control uses at least 3 well-distributed control points plus elevation/unit probes. Data flow is m3/s and diameter/access length mm, independent of model storage units. GUID strings and IFC IDs in the mapping are synthetic syntactically shaped identifiers, not exported/native-tested values.

SYN-X-AUTH R01 is the authority permit exchange profile, activated only when BBM-STD-57 records a DM BIM permit route (circulars 9-1-2 and 9-1-3; ED-DM-9-1-2, ED-DM-9-1-3; detail in BBM-STD-85). It uses the IFC schema and export setup stated in the current Dubai BIM Standard (buildindubai.gov.ae/bim), checked at project start and recorded in the BEP; attributes follow the Model Attribute Matrix issued with that standard, with its revision recorded; the deliverable is openBIM IFC, zipped, within the portal upload limit; portal validation evidence is retained. Authority submissions use the schema stated by the authority.

The example excludes fabrication detail, detailed fasteners, hidden proprietary internals, texture/render content, verified installed conditions and operational condition/serial updates. These exclusions cannot override an actual required safety, code, appointment or decision need. Record applicability/mandatory conditions per property rather than inserting zero for inapplicable valve airflow. Exact source/hash and variant relationships belong in the exchange manifest.

4.1 Machine-readable requirements (LOIN → IDS)#

Each alphanumeric LOIN row is published as an IDS 1.0 file (ED-IDS) with ID, revision, hash, applicability facets and valid/invalid IFC fixtures; one IDS file per exchange. Bidders confirm the IDS checker name and build they will use; a pass in one checker is not proof, so the recipient's named checker and version govern. Schema conformance is checked first with the buildingSMART IFC Validation Service or a qualified equivalent (ED-IFC-VALIDATION); geometry and access checks stay separate because IDS covers mainly alphanumeric needs. The facet mapping, IDS authoring and checker qualification method are owned by BBM-STD-89.

5 Response clarification deviations and controlled changes#

Require a bidder response against every EIR child and profile, with Conform/Clarification/Deviation, method, proposed evidence, responsible function and decision record. Silence is not acceptance. Clarify unknown builds, missing sources and rights before committing. The appointing function decides whether an exception is acceptable; designers/authority owners decide matters within their own scope. A bidder's BEP cannot amend upstream criteria by itself.

The worked response conforms in principle to the three purpose-led products but raises CL- for unverified receiving build/export support. DEV- proposes omitting the current source/access note; its synthetic decision is Rejected because EIR-011-D evidence would be absent. Both remain drafting exercises, with no real bid decision or native test.

The separate simulated accepted change CH-SYN-EIR01 adds source-review responsibility to the delivery evidence index. Its propagation table records EIR/LOIN/profile/evidence-index and project BEP/TIDP/MIDP R01-to-R02 impacts, one simulated decision and exact notified functions/acknowledgment fields. It does not modify the current R01 fixture or the existing office documents. Real accepted changes require signed/scoped authority, all affected baselines and actual recipient acknowledgment before effective use; preserve history and assess derived exports and dates.

6 Worked exchange and recipient acceptance#

The Type register resolves all three selected types to their class and fictional design source. The Note example supplies a populated ME03 assumption/source/uncertainty/risk/interface/issue slice and expected authorised/denied link outcomes. Actual source/file hashes, receiving build, operator/date and evidence references have separate editable fields in Recipient tests; unmeasured results remain Not executed. The Design payload has three assets, two location keys, two system keys, two instruction references and stable source/model IDs. Geometry cases give a reproducible arithmetic fixture; manifest rows specify five format variants across the three logical containers. Source/hash/build/access evidence remains explicitly Not executed rather than inventing file hashes. ME01 tests cover schema/opening, coordinates, known-value/counts, hard/access/interfaces; ME02 tests reconcile every applicable dictionary field and N/A; ME03 tests check source/uncertainty/risk/issue evidence and actual authorised access.

Worked caseExpected recipient outcome
Positive specificationAll declared three assets/keys/required values and current sources agree; 650-10=640 >=600; all five variants trace one R01 source snapshot; actual native/profile/access checks still needed
Missing mandatory valueAHU-001 DesignFlow_m3_s blank: reject affected product; optional fields cannot compensate
Wrong unitAHU flow payload 1200 with source-unit L/s in target m3/s field: reject until approved conversion/source mapping, never silently relabel
Duplicate or broken mappingSecond AHU-001 or model/schedule GUID mismatch: reject; count three alone is insufficient
Access/source failureDOC-SYN-AHU01 R01 denied to SYN-RR01, or SYN-REQ-A01 superseded: Hold affected acceptance
Geometry failureClear 605 +/-10 gives 595<600: return for design correction; missing uncertainty holds
Version driftIFC/model R02 paired with schedule/note R01 without authorised mapping: reject and regenerate/recheck derived products

Recipient acceptance follows the ISO 19650-4:2022 review and acceptance steps (ED-ISO19650-4). Record each recipient test ID, input, method, expected result, actual result, exact file/source hashes, receiving build/operator/date and evidence. Distinguish independent check, authorisation, submission, review recommendation, scoped information acceptance and project decision. All actual results in this pack remain Not executed. The blank forms require completion and competent owner review before mobilisation; no native IFC, FM/COBie, issued model, receiving proof or appointment is delivered by these templates.

References#

Document history
VersionDateChange
V0.12026-10-16First controlled draft
V0.22026-11-04closure: §4.1 LOIN→IDS pointer to BBM-STD-89; SYN-X-AUTH authority permit profile; LOIN table split into ISO 7817-1 facets; property definitions via BBM-STD-72 (ISO 23386/23387, bSDD); SYN-X01 aligned to IFC 4.0.2.1 RV default; project CRS particulars via BBM-STD-86; ISO 19650-4 acceptance; H&S information particular; BEP V0.5 link; references re-checked + cross-doc pointer pass