■ MEP BIM INSIGHTS — BIM GUIDES

What Is a Federated BIM Model

On any project with more than one discipline, the term “federated model” comes up in the BIM Execution Plan, the coordination meetings, and the deliverables list. It is one of the most important concepts in multi-discipline BIM — and one of the most commonly misunderstood, often confused with simply merging files together.

This article explains what a federated model is, how it differs from a combined or merged model, and why the distinction matters for coordination.

---

The Definition

A federated BIM model is a single coordination model assembled by linking separate discipline models together — architectural, structural, mechanical, electrical, plumbing, fire protection — without merging them into one file. Each discipline keeps ownership of its own model. The federated model references them all in a shared coordinate space so conflicts between them can be found and resolved.

The key word is linked, not merged. The discipline models remain separate, editable files. The federated model is the assembly of those links — a place to see everything together, not a new master file that replaces the originals.

---

Federated vs Merged: Why It Matters

Aspect	Federated (linked)	Merged (combined)
File ownership	Each discipline owns its model	One combined file, unclear ownership
Updates	Relink to get the latest — automatic	Re-merge manually every time
Editing	Each team edits its own source	Edits risk overwriting others
Coordinate system	Shared, enforced across links	Must be reconciled at merge
Best for	Live multi-discipline coordination	Static snapshot / archive

The federated approach is what makes ongoing coordination possible. Because the models are linked rather than merged, each team continues working in its own file, and the federated model reflects the latest version of each discipline every time it is refreshed. A merged file, by contrast, is a snapshot — accurate only at the moment it was combined, and stale the moment any discipline updates its work.

---

How a Federated Model Is Assembled

The mechanics depend on the platform, but the workflow is consistent:

• Shared coordinate system. Every discipline model must use the same origin and coordinate reference. Without this, links load in the wrong position and the federation is meaningless. This is the single most important setup step.
• Linking, not importing. In Revit, disciplines are brought in as linked models. In Navisworks, models are appended into a single scene. In BIM 360 / ACC, models are aggregated in the cloud.
• A defined update cadence. The BEP specifies how often the federated model is refreshed — typically weekly for active coordination.
• Clash detection against the federation. The federated model is where clash detection runs, checking each discipline against the others.

Platforms

Different tools play different roles: Revit links are used for discipline-to-discipline work within the Autodesk environment; Navisworks federates everything into one scene for deep clash detection; BIM 360 / ACC aggregates models in the cloud for team-wide coordination. On most projects, more than one of these is used together.

---

Why the Federated Model Is the Coordination Backbone

A single discipline model, on its own, cannot reveal conflicts with other disciplines — it only contains its own elements. The federated model is the only place where a duct can be checked against a beam, a pipe against a conduit tray, a sprinkler main against a structural penetration.

This is why the federated model, not any individual discipline model, is the reference for:

• Clash detection and clash resolution tracking
• Coordination meeting reviews
• Design review and constructability checks
• Progress verification across disciplines

---

Common Federation Problems

• Coordinate mismatch. One discipline set up on a different origin — its model loads offset from everything else. Every clash is false; real clashes are hidden.
• Inconsistent update cadence. One discipline links a three-week-old version while others are current. Coordination happens against stale geometry.
• Version drift. Discipline models on different Revit versions, causing link failures.
• Unmanaged link ownership. No one is responsible for maintaining the federation, so it silently falls out of date.

Our Approach at GEOMETRY-S

Every multi-discipline project we work on is coordinated through a federated model with an enforced shared coordinate system and a defined weekly update cadence. Whether the federation lives in Revit links, Navisworks, or Autodesk Construction Cloud depends on the project’s BEP — but the principle is constant: discipline models stay owned by their teams, and coordination happens where they overlap.