ArchHubBABOOMDownload

Asset handover and maintained asset information

BBM-STD-75 · V0.3 · Deliver usable, verified operational information and assign its continuing update custody.

Download WordFormsAll standards

BBM-STD-75-HANDOVER_AND_AIM-V0.3 | Office standard | 5 November 2026 | V0.3 | Private controlled WIP draft

1 Purpose scope and custody#

Deliver usable, verified operational information and assign its continuing update custody. This pack covers..083 and extends Manual V0.5 section 12.5 and BEP V0.5 sections 7.3.1 and 8.11; those lifecycle controls remain the procedure owners. Apply AIR, EIR and LOIN, quality, dictionary, exchange qualification and the office register. The editable handover pack supplies controlled blank forms and a filled synthetic handover specimen.

The appointed operational owner fixes required asset scope, AIR and target-system use; the delivery asset-data lead compiles verified records; responsible installers/surveyors/commissioning specialists supply condition evidence; an independent checker reconciles it; the LAP authorises submission; the delegated operational recipient tests and acknowledges the accepted AIM baseline. Record actual holders, deputies, powers, transition date and exclusions before handover. Information acceptance does not grant a permit, certify a safety system or transfer design/operating responsibility beyond the appointment.

Use ISO 19650-1:2018 clause 5.3 as an AIR reading pointer, -2:2018 clauses 5.7–5.8 for delivery/close-out, -3:2020 clause 5 for operational information-management processes, -4:2022 for the information-exchange review criteria applied at handover acceptance, -5:2020 for sensitivity-led protection and -6:2025 for structured health and safety information. IMI Framework (formerly UK BIM Framework, renamed May 2025) archived Guidance Part 3 edition 2 sections 3.3.3, 4.2 and 7 explain handover, triggers and integration. Clause references are reading directions, not a licensed audit or reproduced paid text.

2 Contractual exchange profile and COBie selection#

Before population, record appointment/EIR/AIR revisions, facility boundaries, delivery milestones, exact schema/version/release, tables/fields, allowed values and null rules, classifications, exporter/importer full builds, units/dates, document route, permitted audience and validation/acceptance method. 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). COBie v3 changes tables and field naming and must not be silently substituted for a 2.4 import, nor 2.4 for a v3 import; NIBS published COBie V3.0 in 2023 as part of NBIMS-US V4 (NIBS version history, checked 2026-11-05); a v3 EIR records the exact NIBS file and hash it names.

For this synthetic example retain BBM-STD-52's SYN-FM-CSV-01 R01 as the selected other-format profile: UTF-8 CSV, comma separator, quote embedded commas, dot decimals, ISO 8601 dates, exact field names below and Asset_ID length at most 40 characters. This is a fictional technical handover profile, not COBie compliance. Native model/IFC geometry follows BBM-STD-74 as a linked deliverable; it is not carried in the CSV. Full importer/exporter builds and real support remain Unverified. No actual operational system is named or tested.

If COBie is required, use the exact official adopted blank template/schema and record its download URI/hash, release, licence, required/conditional tables and receiver-specific constraints. Never add custom columns to standard tables and still label the result conformant; route extensions through the adopted schema's supported attribute mechanism. Do not mistake an office review workbook for a full COBie deliverable. The Profile sheet provides a version/field-migration check, including legacy Floor/ComponentNames versus selected newer Level/Component.Name where applicable; verify every actual field against its adopted publication. Official templates are linked for controlled acquisition; this pack's usable blank exchange is the explicitly selected SYN-FM-CSV-01 profile.

3 Field dictionary and relationships#

Use one Asset_ID occurrence identity within Facility_ID scope; never replace it with a physical tag, serial number, native GUID or finance reference. Preserve BBM-STD-52's AHU-001/VLV-001/VLV-002, locations LOC-101/102 and systems SYS-AIR01/SYS-HW01. The canonical BBM-STD-72 dictionary remains the owner; the handover dictionary below defines this selected exchange's transport fields, not new global parameters or invented GUIDs.

CSV fields in exact orderMeaning and validation
Asset_ID, ClassUnique stable text ID; allowed Class AHU or VALVE for this specimen only. Asset_ID max 40 is fictional profile rule
Location_ID, System_IDExisting controlled location and system keys; this narrow profile permits one primary location/system per record. Required multiple membership needs an agreed relationship extension before issue
Condition, InspectionDateApproved Good/Fair/Poor/Not inspected enumeration and verified ISO date/source. An unverified condition stays Not inspected with uncertainty recorded in issues, never Good by default
ServiceInterval, ServiceUnitPositive numeric interval and explicit unit from approved maintenance source; no invented generic interval
Document_ID, Document revisionCurrent instruction key and exact revision; Documents register adds all mandatory supporting records
DesignFlow_m3_s, NominalDiameter_mmClass-specific numeric value; AHU flow or valve diameter required for this specimen; other class field blank by applicability, never zero
Serial, StateSeparate serial reference and Active/Retired lifecycle status; never substitute one for Asset_ID
Source revision, Evidence status, Object referenceImmutable source container/revision, verification limitation and native/model join. Fictional fixture is not installed proof

The table lists the seventeen transport headers in exact order: 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. BBM-STD-52 §5 (SYN-FM-CSV-01) is the single source of this list; until it states the list, this table is the reference and any difference is a hold. Type_ID, ChangeID, event timestamps and constructed-verification statuses are separate companion relationship/event records, not silently added CSV columns. Dictionary rows state FieldID, datatype/unit, allowed/null rule, mandatory applicability, authoritative source and acceptance. Type/location/system/document tables have unique keys and facility context. Maintain many-to-many asset/document links in Records rather than concatenating uncontrolled IDs into the CSV. An explicit Exclusions form identifies decorative/non-maintainable objects, not a blanket deletion of required safety records. Distinguish unknown, not supplied, withheld and not applicable in accompanying issues; a required unknown holds acceptance.

4 Reconciliation of constructed condition and records#

Freeze the source model, approved changes, installation/survey records and handover cut-off. For each maintainable asset reconcile design identity, installed tag/serial, actual location/system, inspection/capture date, method/competent supplier, uncertainty and source revision. Record differences and their disposition; do not relabel design geometry as as-built or infer hidden services from a scan. Link changed condition to the authorised design/installation record and independent check. Actual survey and installed evidence remain Not executed here.

Required record group when applicableRequired index and check
Operation and maintenanceCurrent procedure/manual revision, applicable asset/type, language/access, provenance and operator opens the actual document
Commissioning and testsTestID, witnessed result/date, system boundary, responsible specialist, acceptance/limitations and source file; a scanned signature alone does not establish passing performance
WarrantyGuarantor/terms reference, start trigger/date, duration/unit, exclusions and responsible custodian from actual source; do not infer start from model date
Safety and statutory informationStructured per ISO 19650-6:2025 as set in BBM-STD-88: hazard, risk, control, owner and the location/object link, plus applicable certificates/conditions/expiry and jurisdiction source under BBM-STD-57; competent receiving review required
Civil Defence / fire and life safetyFire and life-safety system certificates, Civil Defence approved drawings and completion approval, maintenance-contract evidence, per the UAE Fire & Life Safety Code of Practice (September 2018 edition plus emirate amendments current at project start, recorded in BEP); the specific authority completion list comes from BBM-STD-57 and BBM-STD-85 at handover, not from this table
Constructed verificationSurvey/inspection/installation evidence with date, object/location match, accuracy/coverage and unresolved areas

The synthetic baseline has 3 active assets, 2 locations, 2 systems and 2 types. AHU-001 uses T-AHU01 at LOC-101/SYS-AIR01; VLV-001 is LOC-101 and VLV-002 LOC-102, both T-VLV01/SYS-HW01. Existing instruction IDs DOC-SYN-AHU01/DOC-SYN-VLV01 remain unchanged. Proposed record IDs COM-AHU01/COM-VLV01, WAR-AHU01/WAR-VLV01 and SAFE-01 are fictional index placeholders with no document bytes or tests behind them. Their statuses remain Required evidence absent; they cannot be accepted because the index is populated. A negative case maps VLV-002 to LOC-999 and loses a warranty source: reject both relationships/evidence, correct by the responsible source owner and independently retest.

5 Receiving tests and handover decisions#

Package acceptance applies the ISO 19650-4:2022 information-exchange review criteria, read from the licensed text and recorded per package in the Receiving form. Where assets must stay linked to their documents across systems, an ISO 21597-1/-2:2020 ICDD container is an optional package format, used only when the receiver has qualified it. Run an authorised sandbox ingest against exact approved profile and builds. Preserve pre-import snapshot/recovery route, input/output hashes, operator/time, allowed permissions, log and independent query/diff. The receiver must open required current documents through actual operational permissions and verify values/units/relationships and record history. Test denied access without exposing sensitive records. Retry only after reconciling an uncertain import to avoid duplicate creation.

Each case starts independently from the three-asset baseline. Create AHU-002 with a new ID and valid existing type/location/system/document: expected 4 active assets. Change AHU-001 Condition from Good to Poor with inspection 2026-12-03: expected same 3 IDs and only authorised changed fields. Replace VLV-002 with VLV-003: expected 3 active and 4 retained historical identities, predecessor preserved. Retire VLV-002 without replacement: expected 2 active and 3 retained historical identities. Replaying the same accepted ChangeID must not duplicate an asset/event; the agreed importer behavior is tested rather than presumed. Duplicate AHU-001, wrong m3/s unit, orphan LOC-999 and inaccessible current O&M must fail the affected use.

Handover review checks all applicable mandatory asset/data/document requirements, every reconciliation issue and scope restriction, source accuracy limits, native/IFC consistency, actual recipient use and continuing custody. Authorisation, receipt, information acceptance, safety/authority approval and operational readiness are separate records. Do not average away an applicable mandatory failure. A conditional decision identifies permitted scope and outstanding owner/date and cannot waive safety/statutory requirements. Record rejected package unchanged, corrected revision/ChangeID and recipient reacceptance.

6 AIM update triggers and continuing custody#

The operator's AIM custodian takes charge only at the documented handover transition. Record authoritative AIM URI/revision/hash, system owner, authorised updater/deputy, support/escalation route, security roles, record-retention owner and actual receiving acknowledgement. Delivery parties update only their appointed scope. Keep the annual unchanged-record review and event-driven review in Manual 12.5; no new universal response SLA is introduced. For Dubai buildings the AIM must also serve the asset-life obligation of Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (issued 27 Feb 2026; in force from 11 May 2026): after 20 years from completion a Building Quality and Safety Certificate is needed, issued by DM under circular 11-9-1 of 2026 on a licensed engineering office's assessment, valid 10 years (5 years once the building is 40 years old), and younger buildings need periodic maintenance. This is an owner obligation for existing buildings, not a design-permit rule; the AIM keeps the records the §7 checklist needs.

TriggerControlled updateReceiving closure
Inspection or failureCondition/date, source and interim restrictions; notify competent safety/service owner where relevantVerified changed fields, history, affected procedures and operator acknowledgement
Replacement or substitutionNew identity, predecessor retained, relationships/serial/warranty/commissioning/documents reconciledActive/historical count check and actual replacement-query test
Use/system/access change or incidentRevalidate AIR, operating limits, roles and related risk/instructionsApproved affected model/data/documents and access tests
Retirement or disposalMark inactive, preserve mandated evidence/holds, remove obsolete access and update connected systemsRecords owner authorises disposition under BBM-STD-76; no automatic erase

The workbook's Trigger event, Reconciliation, Receiving and Handover forms record requirement/source revisions, ChangeID, requested/accepted baseline, affected IDs, updater/checker, actual due date, evidence and decision. Synthetic events specify expected results only. Open activation conditions: actual contract/profile selection, complete issued document set, verified constructed condition, supported full builds, scoped permissions, successful actual ingest/change/replace/retire and assigned acknowledged AIM custody. No real operational acceptance or learner/installation evidence is invented.

7 Existing-building assessment: Building Quality and Safety Certificate (Dubai)#

Dubai Law No. 3 of 2026 is applied by DM circular (11-9-1) of 2026, dated 1 October 2026, and its guidance manual "Building Quality and Safety Certificate" (attachment 11-9-1-1, May 2026). Register rows ED-DXB-LAW-3-2026 and ED-DM-11-9-1 are in BBM-STD-51 §3; the authority detail is in BBM-STD-85 §4. The owner of a building completed 20 or more years ago, including in free zones and special development areas, must obtain a Building Quality and Safety Certificate when DM notifies them. It is valid 10 years for a building under 40 years since completion and 5 years for one of 40 years or more, and is renewed in the last 90 days before expiry by the same procedure. DM applies it in phases, first to multi-storey buildings over 40 years old; an owner with several buildings is scheduled by structural condition, age and area importance. The owner appoints an engineering office licensed in Dubai, with an active DM registration and a classification category that matches the building height. The office does this work only under a signed appointment that names it as that engineering office.

Roles: owner, A (appoints the office and the remediation contractor, agrees the remediation duration and signs the undertaking); office project director, A for the office's work; assessing engineer, R (site assessment and technical report); discipline leads, R for structure, facade and MEP items; a specialist cladding firm where needed (the manual allows the consultant to use one; QP-15); supervising engineer, R (remediation supervision); authority liaison, R (Build in Dubai applications); DM, review, permit to start remediation, inspection and the certificate.

StepWhat the office doesEvidence (record)QMS procedure and tracker
A1 Notice and appointmentRead the owner's DM notice (plot, deadline, service link). Confirm the office's Dubai licence, active DM registration and classification category against the building height. Contract review; scope: assessment, technical report, applications, remediation supervisionNotice copy, classification check, go/no-go, signed appointmentBBM-STD-97 QP-01; QP-15 for a cladding specialist or laboratory
A2 Existing recordsCollect the as-built drawings, previous permits and the completion certificate (completion date gives the age and the validity), maintenance records, Civil Defence and SIRA certificates and the AIM if one exists (§6)Records list with source and date; missing items recorded as limitsQP-10 incoming register
A3 Site assessmentInspect against the DM technical checklist (manual annex 1): (1) structural safety: slabs, beams, columns, basement walls, foundations and ties, reinforcement condition (rust, corrosion), steel structures, pool walls and slabs, waterproofing; (2) external cladding: fixing to the main structure, material condition, joint sealant without voids, no services or AC units on the facades spoiling the appearance; (3) windows, doors and guards in the facades and common areas: no breakage or defects, locks close tightly, balcony, terrace, roof and stair railings fixed and sound; (4.1) electrical in external and common areas: distribution boards, breakers, earthing, cable insulation and terminations, cable trays and their fixing, emergency lighting, lightning protection; (4.2) mechanical: AC units, fans, filters, duct insulation, tanks, water and drainage piping, pumps, leaks, basement submersible pumps and ventilation, roof rainwater drainage, fixing of equipment; (5) Civil Defence requirements; (6) SIRA requirementsSite visit report per visit, photographs, checklist filled per itemQP-09 sheets IP and SOR; findings logged in the BBM-STD-99 tracker TRK-IR
A4 Laboratory testsWhere the assessing engineer's judgement or the building's condition needs them: concrete cores, Schmidt hammer, ultrasonic pulse velocity, chloride content, sulphate content, half-cell potential, other tests as neededTest requests and results linked to element and locationQP-09; TRK-IR
A5 Technical reportOne report per building against every checklist item: the condition found, each defect, the remediation methods and material specifications based on the findings and test results, and the remediation duration agreed with the ownerSigned report revision, checklist, photographs, test resultsQP-03 review per discipline; QP-10 issue
A6a No defectsWith the Civil Defence and SIRA compliance certificates (both mandatory), apply on the Build in Dubai e-service "Issue Building Quality and Safety Certificate" within the notice deadline: building selected from the system list (or added), checklist fields filled, report and evidence attachedApplication reference, attachments, submission dateQP-07; TRK-NOC
A6b Defects foundApply on the same e-service with the technical report, the remediation proposals and their documents, the agreed duration and the owner's undertaking to finish the remediation within it through a contractor licensed in DubaiApplication reference, report revision, owner undertakingQP-07; TRK-NOC
A7 DM reviewDM approves, returns the application with comments for resubmission within the set time, or visits the site first. Where defects exist, approval is the permit to start remediation works, with its conditionsComments and responses, permit to start worksQP-07; TRK-NOC
A8 Remediation supervisionThe owner appoints a contractor licensed in Dubai whose specialisation matches the remediation. The office supervises fully, to the approved methods, engineering practice and the conditions of DM and other authorities (DEWA, RTA, Civil Defence), within the agreed duration: hold-point inspections, NCRs closed only after re-inspection, written instructionsSupervision plan, inspection requests and results, NCRs, site instructions, submittals, test resultsQP-09; TRK-IR, TRK-NCR, TRK-SI, TRK-SUB
A9 Final applicationConfirm completion to the report, attach the remediation records and photographs and the Civil Defence and SIRA compliance certificates, name the main contractor, declare that the works followed engineering practice under the office's supervision, and applyApplication with the declarationQP-07; TRK-NOC
A10 Inspection and certificateDM inspects the building (the manual also allows approval without a site visit) and issues the certificate, downloadable by the owner and the office on Build in DubaiCertificate with issue and expiry datesQP-10; AIM update (§6, trigger "Inspection or failure")
A11 Expiry and renewalRecord the expiry date; the renewal window is the last 90 days before expiry and needs a new assessment and appointmentExpiry entry in the AIM and AIR-006 (BBM-STD-52)AIR-006 trigger

Exemption: an owner who chooses demolition may be given up to one year after DM confirms no structural danger (a further period of up to two months for reasons beyond the owner's control); a DM demolition decision for unsafe structure removes the duty. Limits: the certificate is DM's decision. The office's report states the visible and tested condition on its date, with its limits and access restrictions recorded; it does not certify fire or security systems (those are the Civil Defence and SIRA certificates) and does not move the decennial liability of the original designer and contractor (BBM-STD-90). An error found in the office's own report is a nonconformity under QP-11. The records are kept to the BBM-STD-90 office minimum.

References#

Document history
VersionDateChange
V0.116 October 2026First controlled draft.
V0.24 November 2026closure: COBie selection per; NIBS references relabelled; ISO 19650-6:2025 safety record structure via BBM-STD-88; Civil Defence / FLS record group; seventeen headers listed here and flagged for BBM-STD-52 §5; ISO 19650-4 acceptance and ICDD; Dubai Law No. 3 of 2026 asset-life obligation in §6; links to Manual V0.4/BEP V0.5; spacing fixed. + cross-doc pointer pass. + template alignment (..148)
V0.35 November 2026Standard watch no. 1: new §7 existing-building assessment for the Building Quality and Safety Certificate (DM circular 11-9-1 of 2026): steps A1–A11, evidence, QMS procedures and trackers; §6 updated to the circular and the in-force date; §2 and references: COBie V3.0 published 2023