
| Asset tag | Description | System | Warranty to | Source object |
|---|---|---|---|---|
| AHU-L03-01 | Air handling unit | Mechanical | 2031-04 | Equipment: AHU-03 |
| CHP-B1-02 | Chiller, water-cooled | Mechanical | 2032-09 | Equipment: CH-02 |
| PMP-B1-07 | Chilled water pump | Mechanical | 2029-11 | Equipment: P-07 |
| SWB-L01-01 | Main switchboard | Electrical | 2033-02 | Equipment: SWB-01 |
| GEN-EX-01 | Standby generator | Electrical | 2034-06 | Equipment: GEN-01 |
| FAP-L01-01 | Fire alarm panel | Fire | 2030-08 | Equipment: FAP-01 |
| LFT-CR-03 | Passenger lift | Vertical | 2035-01 | Equipment: LFT-03 |
| BMS-L02-01 | BMS controller | Controls | 2031-12 | Equipment: BMS-01 |
| TNK-RF-01 | Cold water tank | Plumbing | 2036-03 | Equipment: TNK-01 |

We reconcile the model against what was actually installed and structure the asset data into COBie for the FM or CAFM system — so handover is a database, not a folder of PDFs.
We work in your stack
Three things go to the owner. Each one is attached to the object it describes, so the FM team can query it rather than read it.

The coordinated model is checked against site records, mark-ups and installed conditions, so the as-built is a record of the building rather than a copy of the design intent.
Delivered as the model the owner keeps — the one a future fit-out or renovation starts from, instead of paying to re-survey the building.
Where site and model disagree, the difference is listed. It is never resolved by quietly moving the model to match an assumption.

Identifiers, manufacturers, serial numbers, warranty dates and maintenance intervals are attached to the objects rather than listed in a spreadsheet beside them.
Exported to COBie schema and validated before handover, so the CAFM system ingests it without a round of rework.
Asset parameters are populated to the owner's own convention, so the register matches the system it is going into.

O&M documents are linked to the equipment they describe, so finding the manual for a pump is a query rather than a search through a folder.
The package is checked for missing serials, missing documents and unlinked assets before it goes out, not after the FM team reports them.
The record model, the asset register and the O&M set delivered together, as one thing the owner's system can actually receive.
Reconcile the model against site records
Enrich assets to the owner's naming
Structure to COBie and validate
Hand over with a completeness report

Tell us what your client's FM team needs to receive.
Nothing here asks the FM team to adopt a new tool. Their naming, their schema and their CAFM system are captured at intake and delivered into.
Reconcile, enrich, structure, hand over
Every asset linked to the object it describes.
Asset identifiers as the owner already writes them.
Revit, Navisworks, COBie, IFC, Excel.
Archibus and Maximo-ready output.