ArchHubBABOOMDownload

Asset information requirements template

BBM-STD-52 · V0.3 · Define asset information requirements (AIR) from operational decisions and organisational information requirements (OIR), then allocate appointment-specific exchanges.

Download WordFormsAll standards

BBM-STD-52-AIR-V0.3 | Office standard | 5 November 2026 | V0.3 | Private controlled WIP draft for office review and adoption

1 Purpose ownership and scope#

Define asset information requirements (AIR) from operational decisions and organisational information requirements (OIR), then allocate appointment-specific exchanges. AIR states what the asset owner/operator needs; the asset information model (AIM) is the maintained information satisfying those needs. A delivery handover is one trigger, not the end of AIM custody. This pack covers.

The asset-information lead maintains AIR with the appointed operator and actual asset decision owner. Use Office OIR V0.3, Glossary, BBM-STD-51, BBM-STD-55 and BBM-STD-57. The editable AIR pack contains blank forms and a coherent fictional SYN-P001 dataset. Actual appointments, systems and operating requirements remain to be populated and approved.

ControlRequired record
Scope and custodyPortfolio/facility boundaries, maintainable classes, exclusions, asset owner/operator, AIM custodian and deputies
BaselineAIR ID/revision/status, OIR/objective links, source/dictionary/profile revisions and approval/distribution evidence
OwnershipRequirement owner and decision consumer; producer, independent checker, updater, release function and receiving operator
ReviewEach relevant operational trigger and material asset, requirement, code, system or appointment change

The example includes one air-handling unit and two control valves in two locations and two systems. It excludes decorative content and non-maintainable detail, with reasons recorded. It does not assert the real portfolio contains only these classes or assets. Add all actual applicable maintainable classes and linked safety/statutory records before use.

2 OIR to AIR records#

Retain the existing Office OIR identities: OIR-007 maintenance informs AIR-007; OIR-006 statutory records informs AIR-006; OIR-008 operating information informs AIR-008. They remain separate requirements with distinct decision owners. Not every OIR produces AIR, and this template does not allocate another AIR-001 to maintenance.

RequirementDecision purpose and consumerRequired information and acceptance
AIR-007 R01 / OIR-007Prioritise maintenance and replacement; appointed maintenance decision ownerMaintainable population and stable IDs; class/system/location, condition/inspection, service interval/unit and current instructions; every applicable mandatory field valid and every relationship/document resolvable
AIR-006 R01 / OIR-006Decide whether applicable certificates/renewals permit the affected operation; competent compliance/asset ownerInstrument/approval ID, authority, scope, conditions/expiry, current evidence and renewal owner; reconcile applicability to BBM-STD-57 and do not infer permission from a file. UAE statutory records follow the sub-table below
AIR-008 R01 / OIR-008Restore or adjust service after an incident/change; operatorAffected asset/system, event, operating limits, approved procedure and source revision; authorised operator can retrieve the current record
AIR-009 R01 / OIR-006, OIR-008Operate, maintain and alter the asset safely; operator and competent H&S ownerHealth and safety information per ISO 19650-6:2025 (ED-ISO19650-6): residual hazards, safe maintenance and access, hazardous materials, as structured hazard records linked to Asset_ID/Location_ID (Manual 9.4). Requirement detail, roles and update triggers in BBM-STD-88

AIR-006 UAE statutory records. Each statutory record row names the issuer, record type, renewal interval and owner. The record types, issuers and intervals are taken from the instrument rows in BBM-STD-51 §3 and the authority profile in BBM-STD-85 for the emirate, checked at project start; none is assumed from this template.

Record classIssuer (per BBM-STD-85 profile)Instrument (BBM-STD-51 ID)Renewal / validityOwner
Fire and life safety system certificatesEmirate civil defence authorityED-UAE-FLSAs stated by the authority for the systemOperator
Authority and utility completion recordsPermit authority / utilityED-DBC, ED-ADIBC, as applicableAs stated on the recordAsset owner
Building Quality and Safety Certificate (Dubai, buildings 20+ years from completion)Dubai Municipality, on the Build in Dubai e-service, applied for by the owner's appointed engineering office under Law 3/2026 and DM circular 11-9-1 of 2026ED-DXB-LAW-3-2026; ED-DM-11-9-110 years if under 40 years from completion; 5 years if 40+; renew in the last 90 days before expiryAsset owner
Operator and occupant personal data in asset records— (legal basis)ED-UAE-PDPLPer BBM-STD-90 retention scheduleRecords owner

For Dubai buildings the AIM also keeps the evidence the circular 11-9-1 technical checklist asks for: structural records, external cladding records, windows/doors/guards, external and common-area electrical and mechanical records, and the Civil Defence and SIRA compliance certificates, with the certificate expiry date as a trigger. The assessment procedure is in BBM-STD-75 §7.

Each AIR register row records requirement revision, operational question, OIR/decision owner, objects/classes, required fields/units/documents, authoritative source/provenance, trigger/timing, updater, receiving profile, sensitivity/retention, acceptance method, EIR allocation and change/approval evidence. Preserve source ownership when several AIR records share a property. A field being available does not make it required without a purpose.

ISO 19650-1:2018 clause 5.3 is the AIR reading pointer. ISO 19650-3:2020 addresses operational information management; Guidance D edition 2 sections 1.4.2 and 1.5 explain AIR and operational exchanges. Public guidance supports these pointers; formal compliance needs the licensed adopted texts.

3 Identity property and document schedule#

Asset_ID is immutable within the declared facility namespace; Location_ID and System_ID resolve to controlled registers. Preserve previous IDs and replacement/retirement links. Do not reuse an old ID for a replacement asset. A manufacturer serial, displayed tag, model element reference and system ID are separate properties, with explicit mappings rather than silent substitution.

The provisional SYN-DICT-01 R01 worksheet covers all 17 Assets form columns, including five administrative provenance/lifecycle fields. It defines property ID/name, meaning, data type, units/allowed values, applicability, source, mandatory condition and acceptance. BBM-STD-72 is the property and classification dictionary owner, a draft dependency pinned at its current draft revision. The property curator must reconcile this project schedule with that owner before adopting actual shared-parameter GUIDs, classification codes or production mappings. No native shared-parameter file or authoritative global dictionary is created here.

Field groupExample and rule
Identity and relationshipsAHU-001, VLV-001, VLV-002; locations LOC-101/LOC-102; systems SYS-AIR01/SYS-HW01; unique active IDs and existing foreign keys
Condition and servicingFictional Good condition and inspection date; positive interval with explicit month unit and source instruction. Example intervals are not office maintenance policy
Class-specific dataDesignFlow_m3_s applies to AHU; NominalDiameter_mm applies to valves. Inapplicable values remain blank with dictionary applicability, never misleading zeroes
DocumentationCurrent document ID/revision, title, authorised access route, source/rights and link-test owner; master Documents worksheet provides coherent fictional references
ProvenanceSource container/revision, survey/designed/installed/verified status, author/update event, check/evidence and timestamp. Synthetic rows do not establish installed truth

3.1 Property and class definitions#

Each AIR property carries the ISO 23386:2020 definition attributes (GUID, name, definition, unit, data type) and a bSDD URI where one exists (ED-ISO23386, ED-ISO12006-3). Data templates follow ISO 23387:2025 (ED-ISO23387). Each maintainable class carries Classification_Code with ClassificationTable/Title/Release, using Uniclass 2015 Pr or Ss tables and citing the release used (July 2026 release: Pr v1.43, Ss v1.43; ED-UNICLASS) within the ISO 12006-2:2015 framework (ED-ISO12006-2). Asset_ID is canonical; AssetTag is a mapped alias only.

The workbook's three asset rows reconcile to its location, system and document rows. Serial labels and source tokens are explicitly fictional. Real handover requires verified installed identity, commissioning and mandatory document evidence; geometry and a plausible serial value alone are insufficient.

4 Operational triggers and AIM custody#

TriggerUpdater and timingRequired control
Initial accepted handoverDelivery asset-data lead prepares; operator receives at the agreed handover exchangeCheck selected PIM information against AIR and tested receiving profile; record acceptance and new AIM baseline
Inspection or condition changeAuthorised maintenance updater at the agreed inspection/event cut-offRetain previous value, inspection evidence, date and ChangeID; check before using a changed priority
Failure/emergency or operating-limit changeAuthorised operator, with competent safety/service owner where requiredRecord the event and controlled interim restrictions; validate the affected information before the next dependent operation
ReplacementAuthorised asset updaterRetire the old ID with history; create a new unique ID and replacement relationship; update system/location/documents and related procedures
Retirement or disposalAsset owner/custodian within appointmentMark inactive, preserve required records/legal holds, revoke redundant access and retain provenance; never erase history as a default

Record event ID/type/date, affected asset IDs, ChangeID, responsible updater, requested/accepted exchange, actual agreed due date and receiving decision. The actual operator fixes notification and response windows; this template invents no universal operating SLA. Delivery team custody ends only at the agreed handover/transition; maintained AIM custody remains with the appointed operator/custodian through later events.

5 Receiving system security and retention#

Select the actual FM/asset application, version/build, import API/file profile, field names/order, datatypes, identifiers, units, date/decimal conventions, length/null/enumeration rules and relationship/document handling. Test create, update and retirement behavior using a representative authorised dataset and rollback. A product name, workbook export or schema-valid file is not import acceptance.

SYN-FM-CSV-01 R01 is a fictional receiving profile for this pack, and the single source of the asset transport header list (BBM-STD-75 §3 cites it). The seventeen headers, in exact order, are: Asset_ID, Class, Location_ID, System_ID, Condition, InspectionDate, ServiceInterval, ServiceUnit, Document_ID, Document revision, DesignFlow_m3_s, NominalDiameter_mm, Serial, State, Source revision, Evidence status, Object reference (as in the Assets blank and Assets example worksheets, checked 2026-11-04). Type_ID, ChangeID and event records are companion relationship/event records, not extra CSV columns. The profile uses UTF-8 tabular exchange, exact headers/IDs, dot decimal values, ISO 8601 exported dates and explicit property units; maximum Asset_ID length 40 is a scenario assumption. Importing product/build, actual permissions and import behavior remain Unverified. The workbook itself is an editable requirements form, not a native FM export or a COBie file. COBie is delivered when the EIR requires it, in the version the EIR specifies; the default is COBie 2.4 (NBIMS-US V3) unless the EIR names COBie v3 (NBIMS-US V4) (ED-COBIE). The receiving FM mapping is recorded in this profile. BS 1192-4 COBie is withdrawn (ED-BS1192) and is mapped only for legacy receivers.

Apply ISO 19650-5:2020 proportionately, using the security triage and SensitivityClass in BBM-STD-87: assess sensitivity and aggregation, authorise receiving roles, restrict detailed operating/security/safety records, confirm supplier/downstream access and test denied as well as allowed routes. Do not copy credentials into AIR. The records owner specifies retention by class and legal/contractual duties, including holds and permitted disposal; no universal retention period is invented. Handover and records follow the draft dependencies BBM-STD-75 and BBM-STD-76; the retention schedule and personal-data basis are owned by BBM-STD-90. No live import is claimed.

6 Receiving checks and worked adverse cases#

CaseFixture and expected resultEvidence needed before real acceptance
CreateAdd AHU-002 with new ID and valid class/location/system/document keys; expected new active population fourImport log, receiver query and source-to-receiver key/value reconciliation
ChangeAIR-007 inspection updates AHU-001 condition/date under CH-SYN-A01; identity and unchanged fields retainedBefore/after values, updater permission, history and receiving acknowledgment
RetireRetire VLV-002, preserving identity/history and required references; expected active population twoReceiver inactive/history query and retained required-document access
DuplicateA second AHU-001 in one active populationReject ambiguous identity; never silently overwrite or count it twice
Wrong unit or broken relationshipAHU flow supplied in L/s under a field requiring m3/s, or nonexistent LOC-999Reject until explicit approved conversion/mapping or corrected source; do not relabel a value
Document failureRequired current instruction missing, superseded or inaccessible to the operatorHold affected operational use until current authorised access is demonstrated
IDS checkIFC AIR payload validated by IDS 1.0 file AIR-IDS-Rnn (rule IDs, hash, valid and invalid fixtures; ED-IDS) after schema validation (ED-IFC-VALIDATION) and before the receiver import test, following the file naming and check sequence in BBM-STD-89 §3/§5; CSV/COBie payloads use separate field checksIDS checker name and build, report URI; a pass in one checker is not import acceptance

The Mutation inputs worksheet supplies a complete 17-field target row for each positive create/change/retire case, with its operation, TestID and ChangeID. Create AHU-002 uses the registered AHU instruction and keys; change sets AHU-001 to Poor on 2026-12-03; retire marks VLV-002 Retired. The unchanged values in change/retire rows must also reconcile. Tests start independently from the same three-asset baseline, not cumulatively. The positive outcomes are expected results of synthetic specifications, not executed FM imports. The Tests worksheet records actual result/evidence as Not executed. Class applicability avoids treating an inapplicable valve flow as a missing AHU requirement. Never accept required data by averaging a completeness score across optional fields.

Release requires a scoped AIR owner/consumer, source and dictionary baselines, stable asset/location/system joins, every mandatory applicable field/document, authorised updater/recipient and actual create/change/retire receiving evidence. Changes propagate to affected EIR, delivery plans and maintained AIM by one ChangeID. Office adoption, actual rights, installed FM behavior, operational acceptance and physical-asset verification are NOT EXECUTED here.

References#

Document history
VersionDateChange
V0.12026-10-16First controlled draft
V0.32026-11-05Standard watch no. 1: §2 AIR-006 certificate row names the Building Quality and Safety Certificate of DM circular 11-9-1 of 2026 (validity, renewal window, issuer route) and the records its technical checklist needs
V0.22026-11-04closure: COBie default per EIR; §3.1 property/class definitions; AIR-009 H&S information; IDS 1.0 check; BBM-STD-72/75/76 linked; UAE statutory records via BBM-STD-85; BEP V0.5 link; references re-checked + cross-doc pointer pass