A federated model combines the architectural, structural and building-services models into one coordinated environment. Each discipline keeps authoring its own model; the federated model brings them together so the team can see — and fix — where they conflict.
Why federate?
A duct that runs through a beam, a pipe that blocks a door swing, a cable tray with no access clearance: problems like these are cheap to fix in a model and expensive to fix on site. Federation makes them visible early, so they can be resolved before construction.
How coordination runs
- Model federation — discipline models from Autodesk Revit are combined in Autodesk Navisworks.
- Clash detection — agreed tests run between disciplines (for example structure vs. HVAC) with agreed tolerances.
- Review and assignment — genuine clashes are grouped, captured as viewpoints and assigned to the responsible discipline.
- Coordination meetings — the team reviews open issues and agrees resolutions.
- Coordinated updates — models are updated, re-federated and re-tested until issues are closed.
What you receive
- Federated NWD/NWC model
- Clash report with viewpoints
- Issue register
- Coordinated discipline models
A note on promises
Good coordination identifies and resolves clashes before construction and reduces avoidable site conflicts. Be wary of anyone promising a “100% clash-free” building — coordination depends on model completeness, agreed tolerances and timely design decisions.
