A handover acceptance checklist for ownersDo not accept keys against a ZIP. Before you sign, test the asset register, O and M, warranties, as-builts, the issued set, and a named AIM owner — on the same day, with identities you can still refuse.
Learning · Handover and asset information
All LearningWarranty and spare parts data: the boring fields that save millionsWarranty dates, serials and recommended-spare part numbers never look like the job. Reconstruct a refused claim, a wrong SKU and an OEM wait from ordinary rates, and they are the cheapest fields on the register.
O and M manuals: from four hundred PDFs to a queryable datasetFour hundred vendor PDFs are a pile. The useful O and M object is a dataset keyed to the same asset tags operations will query: the unit, the action, the warranty and the spare.
The asset register: which fields actually matter to a facilities teamFacilities query location, make and model, warranty, spare and isolation. Delivery metadata, clash IDs and empty custom columns are a museum. Cut every field nobody has ever asked for.
Writing asset information requirements the supply chain can priceAn AIR a subcontractor can price names the object, the field, the milestone and the format. A novel they cannot. A reusable template for the appointment, not an appendix nobody bids.
Progressive handover: validating asset data throughout deliveryValidate tags, inspection records and O and M drafts while the installer is still on site, so the owner inherits a live register rather than a last-month dump.
COBie explained without the spreadsheet traumaCOBie is a handover schema for asset information. The trauma is what happens when that schema is applied once, at the end, as an Excel dump nobody validated and no operator can query.
