A federated model combines separate discipline-specific BIM models — architectural, structural, and MEP — into one coordinated view without merging them into a single file. Each model keeps its own authorship and data integrity. The ConsensusDocs 301 BIM Addendum defines a federated model as one consisting of linked but distinct component models that do not lose their identity or integrity by being so linked — a change to one component model does not create a change in another. 

Large construction projects involve multiple teams working across different BIM platforms. Coordination tools such as Navisworks Manage, Solibri Model Checker, and Autodesk Construction Cloud bring these separate models together for review. BIM Level 2 maturity — the standard for many government-mandated projects — requires managed, discipline-separated models uploaded to a Common Data Environment. The federation process, the distinction between federated and integrated approaches, and the direct impact on construction coordination each shape how project teams use BIM at scale.

How Federated BIM Models Work

Each discipline team builds their model in their preferred BIM authoring tool — Revit for architecture, Tekla Structures for steel, ArchiCAD for design. These individual models upload to a Common Data Environment (CDE), the single repository that holds all project data. A BIM integration tool then imports every model into one unified view.

The process follows a clear sequence. The architectural model comes first. Structural and MEP teams develop their discipline portions based on the architectural reference. All models upload to the CDE. A coordination tool — Navisworks Manage, Solibri Model Checker, or Revizto  — imports each file and assembles the federated view. This view is read-only. Edits must return to each model’s original platform, then re-import into the federated environment. When one discipline updates their model, that updated file re-imports into the federated view. Other discipline models stay unchanged. This one-directional workflow protects each team’s work from unintended edits by other parties.

ISO 19650 requires a CDE as the foundation for information management across a project’s lifecycle. The Information Manager — a role defined by the CIC BIM Protocol — manages the federated model within the CDE and ensures that all submissions follow the project’s BIM protocol. This position is procedural, not design-oriented. It is separate from the BIM coordinator who handles clash resolution. On a hospital project, for example, 5 discipline models (architecture, concrete structure, steel structure, HVAC, and plumbing) federate in Navisworks for weekly coordination meetings, giving the entire team a single spatial reference.

Federated Model vs Integrated Model

The federated approach imports discipline models from different platforms into a BIM integration tool. The single platform (integrated) approach manages all discipline models within one BIM platform. In a federated model, edits return to the original authoring tool before re-import. In an integrated model, disciplines edit and coordinate within the same software environment.

The BIM Execution Plan determines which approach a project uses. Most large-scale commercial, healthcare, and infrastructure projects rely on the federated method because teams across different firms use different modeling platforms. The BIM Handbook notes that the single platform model approach is rarely used in large projects. Both approaches enable clash detection. The federated approach handles complex multi-platform scenarios with more flexibility. The integrated approach allows faster iteration cycles since edits happen in one environment.

Why Federated Models Matter for Construction Coordination

Federated models enable 3 coordination functions from one unified view: clash detection between building systems, 4D construction sequencing, and 5D cost estimation.

Clash detection catches spatial conflicts before construction. A hard clash means two objects occupy the same space — a beam passing through a duct. A soft clash (clearance clash) means objects sit too close for access, insulation, or maintenance. LOD 200 works for major building parts. Piping, structural steel, and ductwork need LOD 300. Thermal insulation around piping may require LOD 400 to catch soft clashes that lower detail levels miss. The BIM Collaboration Format (BCF) tracks each issue between the coordination tool and authoring platform in XML, so teams fix conflicts in their native software.

4D links model elements to the construction schedule for visual sequencing. 5D enables quantity takeoff (QTO) and cost estimation directly from the coordinated model. When teams apply these coordination functions together — clash detection, scheduling, and cost tracking,  the cost impact becomes measurable. 

Lease Crutcher Lewis demonstrated this on a 6,960 m² (75,000 sq ft) University of Washington science and technology building:

Source: BIM Handbook, 3rd Edition — Sacks, Eastman, Lee, Teicholz

These coordination benefits depend on how well the project team structures its federation approach from the start.

How to Build a Federation Strategy

A federation strategy defines how project models are segregated, named, and assembled. It forms a required section of the BIM Execution Plan (BEP).

Model segregation follows a hierarchy. Start by separating each building as its own set of models. Then divide by discipline — architecture, structure, and MEP for each building. Further split by task team when in-house and sub-consultant teams work on the same discipline. File size matters too: individual Revit files that exceed 300–500 MB or IFC exports above agreed thresholds should split into smaller segments to keep coordination tools responsive. Naming conventions must mirror these segregation layers so every team member can locate the right file. The resulting hierarchy runs from individual models to discipline-federated models to building-federated models to one master federated model. Delivering federation-ready models requires specific coordinate system alignment, workset setup, and LOD compliance from every modeling team involved.

Delivering Federation-Ready BIM Models

Discipline-specific models must meet specific requirements before federation works properly. Every Revit model needs a shared coordinate system — either through Shared Coordinates or Project Base Point alignment — so models stack correctly in the federated view. Workset structures must stay consistent within each discipline. LOD compliance matches the BEP requirements for each project phase. Clean model geometry — no overlapping or duplicated elements within a single discipline — prevents false clash results that waste coordination time.

The quality of each discipline model determines the accuracy of the federated result. Teams that specialize in converting point cloud data to discipline-specific Revit models — architecture, structure, MEP — produce the components that make federation possible. ViBIM delivers discipline-specific Revit models from laser scan data through our point cloud to BIM services, structured for direct integration into federated coordination workflows. Each model follows shared coordinate alignment, consistent workset standards, and LOD compliance — the same requirements that federation demands. 

Explore our 3D BIM modeling services to see how these discipline models support your coordination process.