Chapter 2 recap
Getting the data right
The key takeaways from this chapter’s 3 lessons.
Asset tags and registers that work
- A tag is for people: readable, stable, unique across the estate, short enough to engrave.
- The tag, the GUID and the serial number do three different jobs; keep all three.
- Use the owner's asset type codes and tag rule; don't invent a new scheme per project.
- Check tags before handover: duplicates, missing labels, tags that don't follow the rule.
COBie that loads into the CAFM
- 'COBie compliant' and 'loads into our system' are different tests; do both.
- Get the CAFM or CMMS import format at the start, and map classification and fields to it in the requirements.
- Test-import a partial data drop at technical design, not at handover.
- Fix problems at the source (the model or the installer's data), not in the spreadsheet.
From asset data to maintenance work
- A regime is a set of tasks with frequencies, skills and criticality, often from a standard library such as SFG20.
- Each asset needs a type and classification that map to its regime.
- Statutory tasks (fire, emergency lighting, lifts, gas) must never get lost among optional ones.
- Asset counts multiply: small data errors become hundreds of wasted or missed visits a year.