Asset Management & FM (6D)
Quản lý tài sản & Bảo trì (6D/FM)
Use COBie data and model properties in a CMMS/CAFM system to plan maintenance, track assets, and manage space across the asset lifecycle.
Common tools
Archibus, IBM Maximo, Planon
Value delivered
Operations cost 60–80% of lifecycle total — BIM data significantly optimizes maintenance
Adoption in Vietnam
Not yet common in Vietnam — most AIM is abandoned post-handover. High potential for large commercial real estate.
Level of Information Need (LOIN)
G = Geometry · A = Alphanumeric · D = Documentation (ISO 7817-1:2024 method). A blank cell means this use sets no specific requirement for that discipline/stage.
| Discipline | Concept | Schematic | Developed | Technical | As-built / Operation |
|---|---|---|---|---|---|
| Architecture | — | — | — | G3·A2·D2 | G3·A3·D3 |
| Structure | — | — | — | — | G3·A3·D2 |
| Mechanical | — | — | — | G3·A2·D2 | G4·A3·D3 |
| Electrical | — | — | — | G3·A2·D2 | G4·A3·D3 |
| Plumbing | — | — | — | G3·A2·D2 | G4·A3·D3 |
Critical stages: Technical · As-built / Operation
Rationale: 6D FM / asset management. A3 is the defining driver (COBie, asset ID/GUID, maintenance schedule, warranty, spare-parts list). FM geometry minimum ~LOD300 (G3) except maintainable MEP equipment (G4 for field identification & maintenance access modelling). ST4 entries exist to trigger progressive data capture during construction handover — selecting any OPERATE use should cascade A3/D3 obligations into ST4 authoring. D3 for O&M documentation packages. STRU gets D2 only (structural docs, less FM-active).
What it really is
Asset Management & FM (6D) is the use of structured asset data from the as-built BIM model — typically organised as COBie — loaded into a CMMS/CAFM system to plan preventive maintenance, track equipment lifecycles and manage space through the operational phase. Unlike Record Modelling — which stops at PRODUCING a model reflecting actual as-built conditions — this use picks up exactly where Record Modelling ends: taking that as-built data and turning it into a tool actually used day to day. This is not a one-off task: equipment fails, gets replaced and goes out of warranty continuously across the asset's life, so the model and the CMMS need a standing two-way update process, not a single handover event. To be blunt: in Vietnam, most as-built BIM models are abandoned right after handover and never loaded into any operating system — so this use only pays off when the appointing party or the operating unit genuinely commits to maintaining the AIM (Asset Information Model), rather than treating it as a box-ticking exercise.
When to use
Only worthwhile when the appointing party or operating unit already has a CMMS/CAFM in place (or a committed investment in one), with budget and staff to sustain the AIM after handover — not every Grade-II-and-above project should pursue 6D. Best suited to large commercial real estate, hospitals, airports and industrial parks with large equipment inventories and operations costs that matter over the full lifecycle. If the appointing party will sell shortly after handover or has no FM organisation, stop at Record Modelling and do not invest further in this use.
Prerequisites
- •Record Modelling completed, at a Level of Information Need (LOIN) sufficient to carry asset metadata — this use cannot start without a trustworthy as-built model
- •OIR and AIR defined clearly by the appointing party per ISO 19650-3 from the project outset, not added at the last minute at handover
- •A CMMS/CAFM platform already selected, configured and budgeted for operation — without one, stop at the data-handover duty under Art. 8(5)(đ) rather than forcing a 6D exercise
- •An operating/FM organisation that exists and commits to maintaining the AIM long-term
- •A unified asset classification system, mappable between the design classification and the CMMS coding scheme
Inputs
Lead appointed party · native + IFC
Appointing party · .pdf / .docx
Lead appointed party · BIM Coordinator · .xlsx (COBie) / IFC
Appointing party · operating unit · hệ thống CMMS/CAFM
Equipment supplier · subcontractor · .pdf
Lead appointed party · .xlsx
Outputs
COBie dataset checked and confirmed to meet the AIR
.xlsx / IFC → Operating unit (FM team)
Accepted when: No mandatory AIR field missing; every record's GUID matches the correct model object
Asset register loaded into the CMMS/CAFM
hệ thống CMMS/CAFM (xuất .csv / .xlsx) → Operating unit
Accepted when: Every asset carries a code, location, warranty end date and maintenance cycle; traceable back to the source model object
Preventive maintenance (PM) plan
.xlsx / báo cáo CMMS → Operating unit
Accepted when: Maintenance cycles match manufacturer recommendations; every equipment group has a clearly assigned owner
Model-and-CMMS update procedure for equipment replacement
.pdf (tài liệu quy trình) → Operating unit · appointing party
Accepted when: States who updates what, which system is updated first, and how often the model and CMMS are reconciled
General workflow
Define the OIR/AIR at project outset
The appointing party defines the Organisational Information Requirements (OIR) and Asset Information Requirements (AIR) per ISO 19650-3 and writes them into the EIR. Doing this at handover is already too late — a finished model cannot retroactively acquire properties that were never planned for.
Appointing party · OIR/AIR template per ISO 19650-3 → OIR/AIR embedded in the EIR
Check the as-built model and the COBie set
Check the as-built model and the COBie file received from the lead appointed party against the AIR checklist: fields complete, format correct, GUIDs matching the right model objects.
BIM Coordinator (on the operator's side or an appointed consultant) · Revit (COBie extension) · Solibri (IDS checking) → COBie-versus-AIR check report
Map classification codes to the CMMS/CAFM
Build a mapping table between the design classification (Uniclass, OmniClass or an internal scheme) and the CMMS/CAFM asset codes — done before loading data, not fixed by hand afterwards.
BIM Coordinator · operating unit · Classification mapping table (no dedicated software needed) → Classification mapping table
Load asset data into the CMMS/CAFM
Import the checked COBie set into the asset management platform, using a model-linked asset data hub so every record stays traceable to its source object instead of drifting into a standalone spreadsheet.
Operating unit (FM team) · Autodesk Tandem · CMMS/CAFM (Archibus, IBM Maximo, Planon) → Asset register in the CMMS/CAFM
Build the preventive maintenance plan
Configure maintenance cycles per manufacturer recommendations and O&M records, and assign a clear owner to each equipment group instead of leaving one unowned list.
Operating unit (FM team) · CMMS/CAFM → Preventive maintenance (PM) plan
Update on equipment failure or replacement
When equipment is replaced, update both the BIM model's properties/GUID and the CMMS record before closing the work order — one-way updates are the most common reason the two systems drift apart after a few replacement cycles.
Operating unit · BIM Coordinator · Autodesk Tandem · Forma Data Management (CDE storing the as-built model) → Model and CMMS kept in sync
Track operational KPIs and review periodically
Extract quarterly maintenance KPI reports and the share of assets still being updated from the CMMS, checking back against the original AIR to catch data drift before it becomes another abandoned AIM.
FM Manager · Periodic CMMS reporting → Quarterly operational KPI report
Diagram
↺ This update loop must run for the whole operating life — stop the loop and you are back to "handed over, then abandoned"
Common pitfalls
The AIM is abandoned right after handover; the operator reverts to spreadsheets or paper
Cause: No CMMS ready, no budget or staff to run the AIM — the appointing party hands over data only to satisfy Art. 8(5)(đ), with no intention of using it further
Fix: Only commit to this use once the operator's CMMS and budget commitment is confirmed in advance; otherwise stop at Record Modelling
The COBie file is handed over but the CMMS cannot ingest it, or mandatory fields are missing
Cause: The AIR was never defined at project outset; COBie is only checked at the last minute before handover
Fix: Define the AIR from the EIR stage onward and check COBie completeness at every stage gate, not only at handover
The model and CMMS drift apart after just a few equipment replacement cycles
Cause: No two-way update procedure exists for equipment failure or replacement
Fix: Define the update procedure explicitly — who, when, which system first — in the operational-phase BEP
Asset classification codes in the model do not match the CMMS codes
Cause: The design classification system and the CMMS coding scheme were chosen independently, with no mapping table
Fix: Agree the classification mapping table before loading data, not by hand-fixing afterwards
Measuring effectiveness
Compare cumulative operating and maintenance cost with the initial investment total over the building's lifecycle
Benchmark: About two-thirds (2/3) of total project investment — a SECONDARY citation via Otranto et al. (2025, ITcon), who cite Amorim (2022); not independently verified against the original study, useful only to illustrate the order of magnitude
Count mandatory AIR fields with a valid value, divided by the total required fields, measured with a COBie-checking tool
Benchmark: no independent benchmark — set an internal target
Count asset records that still receive status or maintenance-schedule updates against the total initially loaded, measured quarterly
Benchmark: no independent benchmark — set an internal target
Legal basis
Decree 217/2026/NĐ-CP does NOT require operating an AIM or running BIM-based FM — no provision imposes that duty. The only directly relevant statutory duty sits in Art. 8(5)(đ): after project completion, the appointing party must update the as-built BIM model and hand over all BIM data to the operating/management unit. That duty STOPS AT HANDOVER — the law does not require the receiving party to load the data into a CMMS/CAFM, does not require a model-based maintenance plan, and imposes no sanction if the AIM is abandoned afterwards. Art. 8(1)(a) remains the general basis making BIM mandatory for Grade II and above works across the lifecycle, but not specifically for the operational phase. Art. 8(2) assigns scope and information requirements for operations to the contract — the only place an AIM-operation obligation could be created, and it only takes effect once written into the EIR/BEP. The practical consequence: asset_management_fm is the appointing party's VOLUNTARY choice, triggered by the mandatory data-handover duty under Art. 8(5)(đ), not an independent statutory obligation.
Sources
Only official sources (legislation, standards) and peer-reviewed academic work are cited. No vendor marketing figures or press sources. Reference only — does not replace legal advice.