Chapter 4 recap

Planning and production

The key takeaways from this chapter’s 4 lessons.

Federation strategy and breakdown structure

The federation strategy says how the project's information is divided into separately produced models, and how those models are combined for coordination.
The breakdown structure turns that into volumes, levels and information types, which then appear in every container's name.
Each container has one owner; the responsibility matrix settles who models what at the boundaries (slabs, stairs, ceilings, openings).
The lead appointed party proposes it in the tender BEP and confirms it at mobilisation; changing it later means renaming and re-planning.

The name identifies the container for its whole life; status, revision and classification are metadata that change or describe it.
Status (suitability) says what the information may be used for; revision says which version it is; classification says what it is about.
Shared information uses preliminary revisions (P01, P02); published information uses contractual ones (C01). Work in progress adds a point version (P01.1).
Codes live in the CDE's metadata and must match what's printed on the drawing; the project's own list in the information standard is the one that counts.

The task team checks and reviews its own information before sharing it: names, codes, standard, then content.
The lead appointed party reviews the whole set across teams and authorises it before submitting it to the client.
The appointing party reviews the submission against the acceptance criteria in its requirements and accepts or rejects it.
Each decision is made by a person named in the BEP or the responsibility matrix, and recorded; a rejection goes back with reasons.

Mobilisation is when the lead appointed party puts in place the resources, IT and methods promised in its tender, and tests them.
It confirms the people (available, trained), sets up the CDE (workflows, metadata, access) and tests a real exchange between all teams.
Problems found go back into the BEP, the information standard and the templates, not into emails.
The tender's mobilisation plan says what will be tested, by whom and by when; mobilisation ends with a sign-off.