Start from a template, never a copy. The bones get reused; the answers are new.
The promise
Before you start
In the story
The last client's name is on page 14, and the client found it.
The right way
Every section answers this client's requirements list, line by line. Anything we can't do yet is said honestly, with how and when we will.
Sam reads it end to end before it goes. So does someone who didn't write it.
The plan is a promise, so read it the way the client will. Does every section answer one of their requirements? Is anything in it something we can't actually do, or haven't priced?
Story 5: Can they actually do it?
Every firm in the team says it can manage information. The questionnaire has a tick box.
The right way, explained
The plan is our town's promise to the client's town: these roads, these rules, these deliveries. Copy the last town's promise and you've promised roads that don't exist.
If you're the client
Read the plan at tender and score it against your requirements. If you can't tell it apart from the last bid you got, neither can they.
In the town See it in the town: the bid makes a promise. What exactly is it promising?
Sam's view: the promise comes from the whole delivery team, with our firm leading it.
The client
- In the picture
- ISO 19650 calls it
- Watch out for
This is the pre-appointment BIM Execution Plan (BEP)!
The promise: which ways of working we've picked for this job, and why.
For the audit What the auditor will ask
- Show me how the plan answers each of the client's requirements.
- How was it reviewed before it went in?
For the audit What good evidence looks like
- The plan, mapped to the requirements list.
- A record of the review, by someone who didn't write it.
- No ghosts of other projects.
ISO 19650 The plan that goes with the bid
ISO 19650 calls it the pre-appointment BIM execution plan. In plain terms, it's how we propose to manage information on this job, written for this client: which ways of working we've picked, and why. Our advice: keep it short. The step-by-step how comes after award, in the project's procedures.
| It should cover | In plain words |
|---|---|
| Who | The named people from the last lesson |
| Which way, and why | The approach we've picked for each of the client's requirements |
| With what | The systems, from Lesson 2 |
| To what standard | Their standard, and anything we propose to add or change |
| Who does what, at high level | A high-level responsibility matrix: which firm produces which kind of information |
| How it comes together | How the models and drawings will be federated, and how the information is broken down |
Based on the ISO 19650 series: the ideas come from the standard; the plain-English wording, examples and advice are InfoTown's. ISO 19650 is © 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.