Skip to content
BIMpedia
Chapter 4 · Lesson 1 of 4Topic: Naming and the CDE

Federation strategy and breakdown structure

Before anyone models, agree how the project is split into models and containers, who owns each one, and how they come back together. That split shapes naming, planning and coordination for the rest of the job.

4 min read3 quiz questions
Skip to the quiz
  • Watch out
  • What it costs
  • Experienced readers
  • Remember
  • In BIMpedia
Mayainformation manager
Even if you do this every day, watch for this: Split by ownership, not by convenience. Every container needs exactly one task team that is responsible for it; an element that two teams think is theirs gets modelled twice, and one that nobody thinks is theirs gets modelled by no one.

A project is never modelled as one file by one person. It is split into many models and documents, produced by different teams, and brought together again to coordinate. The federation strategy is the agreement on how that split works. The information container breakdown structure turns it into the volumes, levels and types that every team uses to name and plan its work.

Basics

In a federated approach, the architect, the structural engineer and the MEP engineer each produce their own model and stay responsible for it. The models share a coordinate system, so they can be overlaid in a coordination tool. Nobody edits anyone else's model. See model federation for the general idea.

What the strategy decides

How a project is split into containers
The projectone federated model
Volumes
Buildings or blocks
Zones and phases
Site and external works
Disciplines
One owner per model
From the responsibility matrix
Levels and locations
Agreed level names
Shared coordinates
Information types
Models
Drawings and schedules
Documents
Rules
Nothing modelled twice
File size limits
What links to what
DecisionTypical answerWhy it matters
VolumesOne per building, plus site works; large buildings split into zones or phasesFiles stay workable and can be issued separately
DisciplinesOne model per task team per volumeOne owner per container
Levels and locationsOne agreed list of level names and heightsEveryone's level 02 is the same level
CoordinatesOne project base point and survey point, shared by allModels line up without manual moves
BoundariesWho models slabs, stairs, ceilings, openings, MEP supportsNothing twice, nothing missing
Size and linksA target file size; what each model links inPerformance and fewer broken links

One owner per container

The test of a good breakdown is simple: for any element or document, can you name the single task team responsible for it? Where two teams have a claim (the architect's floor finish and the engineer's structural slab, the architect's ceiling and the MEP engineer's services in it), the responsibility matrix decides, and the other team references the owner's element instead of modelling its own.

Story · The hospital in one file
How it goes wrong

The architect models a four-wing hospital in a single file. By stage 4 it is several gigabytes, takes ten minutes to open and has fifteen people working in it at once. Wing C needs to be issued early for a planning condition, but the file can only be shared as a whole, with unfinished wings in it.

How it goes right

The federation strategy splits the hospital into one volume per wing plus the central plant and site works. Each wing is a separate container per discipline, named with its volume code. Wing C is checked, authorised and issued on its own date while the others carry on.

Where it lives, and when it is set

The lead appointed party proposes the federation strategy and breakdown in the tender BEP, so the client can see how the work will be organised. It is confirmed during mobilisation, before the first model is shared. From then on, its codes appear in every container name (naming) and its containers are the rows of the TIDPs and MIDP.

Mayainformation manager
Your turn. Give it about 20 min and work it out on your own before you open the model answer: that is where it sticks.
Exercise: Split a school 20 min

A new school has a four-storey teaching block, a single-storey sports hall, a shared basement plant room under the teaching block, and external works (car park, pitches, drainage). The task teams are architect (AR), structural engineer (ST), MEP engineer (ME) and landscape architect (LA).

  1. Propose the volumes and their codes.
  2. List the models (containers) you expect, by volume and discipline.
  3. Decide who models: the basement slab, the stairs, the suspended ceilings and the drainage in the car park.

Key takeaways

  • 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.

Your notes

Related tool

Plan every information deliverable per task team, with document numbers and milestones, and roll up the MIDP.

Open TIDP / MIDP Planner →

Check yourself

3 questions · 2 right to complete
  1. 1. The architect wants one model for a three-building campus to avoid managing links. What is the main problem?
  2. 2. Both the structural engineer and the architect have modelled the floor slabs. What should the information manager do?
  3. 3. Where does the breakdown structure show up day to day?
0 of 3 answered