Hand over a COBie facility export

Work through the tracked assets and fill the fields COBie reads: make, model and serial, the operational status and warranty date, the storey the item sits on and the parent system it belongs to.

Γιατί: The workbook is a projection of the register, not a document you write separately, so the sheets are only as complete as the rows behind them. A blank storey does not leave one empty cell, it removes a whole Floor row the receiving system was expecting to hang the asset on.

Before you export, read the register the way the workbook will: search and filter down to the assets with no serial, no warranty date and no parent system, and either fix them or put them back to whoever installed the plant.

Γιατί: The export falls back to n/a rather than failing, so a workbook full of holes still downloads cleanly and still looks finished. Nobody finds out until the operator tries to raise a work order against a pump with no serial and no system, by which time the fitters have long gone.

Export the register as a COBie UK 2.4 workbook. It arrives as one spreadsheet with seven sheets, Contact, Facility, Floor, Space, Type, Component and System, each projected straight from the canonical model and the asset data sitting on it.

Γιατί: A workbook generated from the model matches the building; a workbook typed into a template matches whatever the typist had in front of them that week. Exporting per model as each one is signed off also keeps the register current, instead of leaving the whole job to the fortnight before handover.

Bind the workbook into the close-out package alongside the as-built drawings, the O and M manuals and the warranties, and issue the lot as one structured set with its manifest.

Γιατί: A COBie file arriving on its own gets loaded by nobody, because the FM team cannot tell which state of the building it describes. Wrapped in the close-out package, dated and listed on the manifest, it is a deliverable the operator can accept, import and be held to.