The manuals and asset data were on the parts list from the start, collected as each escalator, lift and fan was ordered and installed.
Manuals and asset data
The back alley's bill so far: 145 weeks · See the bill
The right way
Josh's model uses the client's own numbering from the first escalator. Five months before handover, a test load: three lines fail, with time to fix them.
The import on handover day takes four minutes. Every asset, the client's numbers, manuals checked against what's installed.
Now there is: The data the owner runs on (asset information), in the client's numbers and tested. Manuals checked against what's installed.
What's going on here
The owner will run the centre for decades on what it's handed. Collecting the manuals and data as each thing is bought and installed, in the owner's own numbering, and testing the load early, means handover is an import, not a weekend.
In the town See it in the town: whose numbers will the escalators answer to for thirty years?
The data the owner runs on is the information that leaves the Site Office and moves into Client Town for good. It was asked for in the order back in the tender pack: the client's own numbering, the manuals, the facts about every escalator and fire door. Collected as each one is ordered and installed, and listed on the parts list from week one, it arrives in the client's numbers and gets a test load months ahead. Left to the last fortnight, it arrives as brochures and somebody else's numbers, and the import fails at the door.
Fix it Wrong numbers? Switch to theirs today.
- Ask the client for its asset numbering rules, in writing.
- Renumber the model now, while there are fewer assets to fix.
- Book a test load into the client's system this month.
A note for the information manager: Get the client's asset numbering into the promise and the model template on day one, because every week you use your own numbers is another weekend of pizza at the end.
What numbering does your client use for its assets? Is your model using it yet?
ISO 19650 From the client's needs to the owner's data
| ISO 19650 says | Means | In the town |
|---|---|---|
| Asset information requirements (AIR) | What the owner needs to know about its assets, in the form it needs, to run and maintain them | The order, for the data the owner runs on |
| Asset information model (AIM) | The owner's own collection of information about its assets, used through their whole working life | The data the owner runs on, in Client Town |
| Project information standard | The agreed rules for the job's information, such as how things are named and numbered | The label, and the client's numbering for every asset |
| Information model | The structured set of information, drawings, documents and data, delivered for the client to load and use | Information model |
Based on the ISO 19650 series: the ideas come from the standard; the plain-English wording, examples and advice are InfoTown's. ISO 19650 and its UK National Annex are © ISO and BSI. You'll hear the same language across the industry. Read more for free in the Information Management Initiative (IMI) Framework guidance from BSI and nima. For the full requirements, use the standard itself.