Dave: Area 2 drainage… there it is.
On the site app. Thirty seconds, including the tea.
Can I find it, trust it and use it?
The copy in the van won, and it was out of date. This lesson follows the person using the information: need it, find it, trust it, use it, prove it.
Same trench, found and trusted first
Dave: Area 2 drainage… there it is.
On the site app. Thirty seconds, including the tea.
Dug once, to revision C02.
The Clerk of Works: Built to C02, with the photo linked. Lovely.
Smiling. Rare.
How did you find the last thing you used, and how did you know it was the right version?
Rex's diary. One year on. A new starter turned up today with nobody to show them round. I drew them the town. Then I remembered my year.
Information only matters when somebody uses it, and every use runs the same line: need it, find it, trust it, use it, prove it. Dave's van copy was handy but couldn't be trusted. The site app gave him the right revision in thirty seconds, and the proof to go with it.
Everything so far was about getting information onto the shelf. This line runs the other way: it starts with someone who needs something. Dave needs to know which drain goes in Area 2. He has to find it, trust it, use it, and be able to prove it later. Pick a stop to ride along.
Need
Getting the right information to the person who needs it, in a form they can find, trust, use and prove later.
Read this way, everything ISO 19650 asks for, from requirements and labels to checks and acceptance, is there so information can be used with confidence. Using it well means working from published, current information and keeping a record of what was used. That record becomes part of the information the client keeps for the life of the asset: the thing you built.
A note for the Coordinators (that's IM): start from the need! Watch how people on site actually look for things, then make the right version the easiest one to grab. If the back alley is quicker, people will use it.
Because the right one is three clicks away and the wrong one is in their hand.
Until it's out of date, which is almost immediately.
Because the labels are rubbish. See Lesson 7.
So people download it once and never again.
We build routes around what we make, not around who has to find it.
| Code | State | What that means to you | Build from it? |
|---|---|---|---|
S2 | Shared | Shared for information. Read it, refer to it, plan with it. | No |
S3 | Shared | Shared so people can comment on it. If you've been asked to review it, now's the time to speak up. | No |
A1, A2… An | Published | Authorised and accepted, with no comments outstanding. The number is the work stage: on this site A5 is construction and A6 is handover and the as-built record. | Yes, for that stage, if it's the latest |
| Code | When | What that means to you |
|---|---|---|
P01, P02… | Shared | A shared draft. The number goes up every time it's shared again, so check you've got the highest one. |
C01, C02… | Published | The published version, authorised and accepted. Higher is newer. Build from the latest C, with an A status. |
Every status and revision code, and the naming rules, are in one place: Lesson 7, The labels.
Based on the UK National Annex to BS EN ISO 19650-2. Your project's information standard can add to it. ISO 19650 and its UK National Annex are © ISO and BSI. InfoTown explains the ideas in its own words, for learning; 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.