What Is a Federated Model in BIM?

A merged model would be one file everyone edits, which breaks the link between a design element and the person responsible for it. Federation keeps each discipline in its own model, with its own author, history, and review. The coordinator brings them together to look, not to edit.

It also keeps files at a workable size. A full building across all disciplines can be too heavy to open as one model. Linked models can be loaded in parts, by level or by system, depending on what the meeting needs to see.

The assembly starts with an agreed origin and coordinate system. If the structural model and the mechanical model do not share a base point and a rotation, nothing lines up and every clash is false. The BIM execution plan states the origin, the file naming, the exchange format, and the schedule for model updates.

Each author exports or links their model on that schedule, often as native files or as IFC, an open format that carries geometry and properties between tools. The coordinator loads them into a coordination tool, checks that each model is placed correctly, and publishes the combined view the meeting will use.

ISO 19650 treats the project’s information as containers delivered by different task teams. The federation strategy explains how and why the project information model is divided among those teams, and the information container breakdown structure sets out the detailed hierarchy. Together they control segregation, security, and retrieval.

This is a broader picture than a stack of 3D files. A federated information model can include documents such as drawings, schedules, and reports alongside geometry, so the coordination question is not only whether two pipes collide but whether the drawings, schedules, and models say the same thing.

Models at different levels of development sit side by side in the same view. A generic duct at LOD 200 next to a detailed structural frame at LOD 350 produces clashes that will move. Treating each one as a field condition wastes the coordination meeting.

The useful discipline is to state which LOD each discipline model is expected to meet at each milestone, and to say which clashes are space reservations and which are decisions. The federated view shows geometry. The LOD matrix says how far to trust it.

A federated model does not resolve a clash. It shows one. Someone with authority over each affected system has to decide, update the source model, and record the decision on a drawing or in the model, or the next federation will show the same clash again.

It also does not check that the model data is right. A federated view can look clean while the fire ratings, classification codes, or room names in the properties are missing. That is a separate check, against the requirements the project set.