Win the workWin the work: Award…
Before signing
There's cake. Sam walks past it. The promise, who-does-what list and parts list are confirmed with the client and go into the deal with the neighbours: the contract.
Stage 2 · Win the work · Stop 11 of 11 · The right way
Signed, sealed
The back alley's bill so far: 42 weeks · See the bill
The right way
The signature
Helen signs. She knows what the information promises are, because somebody showed her first. The client's order goes into every subcontract too.
Helen: So we're promising asset data in their numbers. Good to know.
DesignDesign: Month four…
No surprises
The asset data is being collected, because everyone signed up to collecting it. Appendix K is dull, which is how it should be.
Appendix KSigned without reading, and nobody passed it on.
The deal, readThe promise inside the contract, and the order in every subcontract.
Now there is: The deal with the neighbours (the appointment), with the promise inside it. The order in every subcontract. The who-does-what list and the parts list, agreed.
What's going on here
Once the contract is signed, the promise is a contract term. Putting the promise, the who-does-what list and the parts list inside it, and the order inside every subcontract, is how the whole team ends up bound to the same information.
New at this stop
- The deal with the neighbours
- The contract between two firms, with the information promises inside it. (The appointment.)
- Who-does-what list
- Who makes, checks and approves each kind of work. (The responsibility matrix.)
- The parts list
- Every piece of information the job will make: what it is, who makes it, and when it's due. (The delivery plans.)
In the town See it in the town: what exactly did we sign?
The order left Client Town in the tender pack, came back as the promise, and now both go into the deal with the neighbours: the contract between Client Town and Sam's firm. Inside it go the who-does-what list and the parts list, so everyone knows who makes and checks each piece of information and when it's due. Then the order travels on again, into every subcontract, so every firm on the job is bound to the same thing.
Fix it Contract already signed? Read the information part now.
- Find where the order and promise sit in the signed contract.
- Check every subcontract has the order inside it.
- Agree the who-does-what list and parts list with the client.
A note for the information manager: The information promises are contract terms once signed, so someone who'll deliver them should read them before the cake runs out.
ISO 19650 From a promise to a deal
| ISO 19650 says | Means | In the town |
|---|---|---|
| Appointment | The agreed contract between the client and the firm leading the job, or between that firm and each firm under it, with the information requirements in it | The deal with the neighbours, Appendix K included |
| BIM execution plan, after appointment (BEP) | The bidding promise, confirmed and developed once the job is won | The promise, confirmed with the client before it goes into the contract |
| Responsibility matrix | A table of who produces and is accountable for each kind of information | The who-does-what list |
| Master and task information delivery plans (MIDP and TIDP) | The schedules of every piece of information each team will deliver, and when, combined into one for the job | The parts list |
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.