Preconstruction — Design Coordination

Federated Model

Separate discipline models linked into one coordinated whole, each author still in control.

Quick Answer

A federated model is a single combined view assembled from the separate discipline models — architectural, structural, MEP, civil — linked together without merging into one file. Each author keeps ownership of their own model, while the federated model gives the team one coordinated whole to review, run clash detection on, and coordinate against.

The Full Picture

A federated model exists to solve a governance problem as much as a technical one: how do multiple firms coordinate one building without any of them owning or editing another's work? Federation links each discipline's model into a combined view by reference, so the whole can be seen and checked while each part stays under its author's control.

Mechanically, the discipline models are linked — not merged — into one environment on a shared coordinate system, typically within a common data environment. Because they're referenced rather than combined into a single file, updating any source model updates the federated view, and no one accidentally edits another discipline's geometry. That separation of ownership is the defining feature of federation.

In practice, the federated model is where coordination happens. It's the model clash detection runs against, the view coordination meetings look at, and the source coordination drawings are extracted from. It's also the single reference that keeps the team from working off mismatched versions — everyone coordinates against the same current whole.

For preconstruction and VDC, the federated model is the backbone of a BIM coordination workflow. Its quality depends on discipline: consistent coordinates, agreed level of detail, and current source models, all typically governed by the BIM execution plan. A federated model built from stale or inconsistent parts produces coordination results no one can trust.

Real Examples

→Linked, not merged: The architectural, structural, and MEP models are linked into one federated model on a shared coordinate system; each firm keeps editing only its own file.
→Single source for clash: Clash detection runs against the federated model rather than pairwise files, so the team checks all disciplines against each other in one coordinated view.
→Live updates: The MEP engineer reroutes a duct and republishes; the federated model reflects the change automatically, so the next coordination meeting works from current geometry.

Common Misconceptions

People assume: A federated model is one merged file.

Actually: Federation links separate discipline models by reference; it doesn't merge them into a single editable file. That's deliberate — each author retains ownership and control of their model, and updating a source model updates the federated view without anyone editing someone else's geometry.

People assume: Federating the models is the same as coordinating them.

Actually: Federation just assembles the models into one view — it doesn't resolve anything. Coordination is the work that follows: running clash detection on the federated model, triaging conflicts, and resolving them. A federated model is the platform for coordination, not coordination itself.

Does MeltPlan Solve This?

Not directly

A federated model is a 3D BIM artifact — the linked combination of each discipline's model, assembled and hosted in BIM coordination software. MeltPlan works from 2D PDFs and DWGs, not 3D models, so it doesn't assemble, host, or coordinate against a federated model. If your workflow is model-based, you'll federate and clash-check in a dedicated BIM tool; MeltPlan reviews the drawings and specs instead.

Frequently Asked Questions

What is a federated model in BIM?

It's a single combined view assembled by linking the separate discipline models — architectural, structural, MEP, civil — on a shared coordinate system, without merging them into one file. Each author keeps ownership of their model, while the federated model gives the team one coordinated whole to review and coordinate against.

What's the difference between a federated model and a merged model?

A federated model links models by reference, so each stays a separate, author-controlled file and updates flow through automatically. A merged model combines geometry into one file, which loses that separation of ownership. Federation is preferred precisely because it preserves who controls what.

Why use a federated model?

It lets multiple firms coordinate one building without editing each other's work, gives the team a single current view to run clash detection and coordination meetings against, and keeps everyone working from the same source instead of mismatched versions.

How does a federated model relate to clash detection?

Clash detection runs against the federated model. Because all disciplines are linked into one coordinated view, the software can compare their geometry against each other at once and produce a clash report the team resolves during coordination.

Related Terms

BIM CoordinationCombining discipline models and resolving conflicts in 3D before they hit the field.Clash Detection ReportThe ranked list of geometric conflicts a model check finds, ready for the team to resolve.Coordination DrawingsComposite drawings that prove every trade physically fits before anything is installed.BIM Execution Plan (BEP)The plan that defines how BIM will actually be delivered on a project.Design CoordinationMaking every design discipline's work fit in the same physical space before it's built.Design ReviewA structured check of drawings and specs to catch problems before they reach the field.

More Preconstruction — Design Coordination Terms

Sources

  1. ISO 19650-1:2018 — Information management using building information modelling — Concepts and principles
  2. buildingSMART International — openBIM
MELTPLAN