A federated model brings separate discipline or authoring models together for coordination without forcing every team to work inside one giant native file.
For MEPF projects, this approach makes ownership, performance and information exchange easier to manage.
Why federation, not one file
Each team owns its model
Discipline ownership stays clear instead of everyone editing inside one shared file.
Lighter, more manageable
Separate models avoid the size and performance issues of one giant multidisciplinary file.
The real dependency
Federation only works with clear naming, revision control and publish rules underneath it.
Why not put everything in one file?
A single file sounds simple. In practice, large multidisciplinary models become heavy, difficult to manage, and harder to assign responsibility for — and different teams have different update cycles and authoring responsibilities that one file can't cleanly separate.
What gets federated
- Architectural model
- Structural model
- Mechanical model
- Electrical model
- Plumbing model
- Fire protection model
The models are linked or aggregated into a coordination environment. Each team maintains its own source model while the wider project sees the combined building.
Federation doesn't mean less coordination — it makes the coordination relationship clearer, but the team still has to agree priorities, tolerances, responsibilities and issue-closure rules.
How federation actually runs, week to week
- Publish current models
- Federate the latest approved versions
- Run coordination and clash tests
- Create issues
- Assign responsibility
- Update source models
- Republish
- Verify closure
A federated model is only as useful as its version control
Teams need clear file naming, revision control, publish rules and a reliable common data environment — without that, federation just moves the confusion from one file to several. Benefits for MEPF specifically include preserving discipline ownership, more controlled model exchange, less unnecessary cross-team editing, and a clearer answer to which model is responsible for a given coordination issue.
Efficient by discipline, coordinated as a whole
For MEPF, that's often the real advantage: each discipline works efficiently on its own model, while the project still gets a coordinated view of the whole building. This is the model structure we define in every BIM Execution Plan and run through BIM coordination.