01
Federated model
Every discipline model combined into one coordinated environment, shared-coordinate aligned and version-controlled.
02 · COORDINATION BIM Coordination.
We federate discipline models into a single coordination model, run clash detection on a fixed cadence, and chair the meeting that turns clashes into closed RFIs — before they reach site.
Typical engagement
3–18 mo
Disciplines
Federated A · S · MEP+
Clash cadence
Weekly
Standards
ISO 19650
Section 01 · The problem
Why "we'll sort it out on site" is the most expensive sentence in construction.
Three trades model in isolation, each confident their own work is correct, and the clash doesn't surface until a duct needs to pass through a beam that's already poured. By then the fix is a site instruction, a schedule delay, and a finger-pointing exercise nobody wins.
We sit in the middle of the federation — pulling every discipline's model into one coordinated environment, running clash detection before the conflict reaches a fabrication drawing, and keeping a single source of truth everyone designs against.
Coordination isn't a meeting. It's a federated model with someone accountable for what's in it.
Section 02 · Our approach
Five steps from kick-off to closed clash log.
Set the federation strategy
Shared coordinates, model breakdown structure, exchange formats, and clash matrix agreed with every discipline lead before the first federation run.
Establish the CDE
Common Data Environment configured on BIM 360 or ACC — folder structure, approval workflow, and access permissions mapped to the project's information delivery cycle.
Run the federation cadence
Weekly model pulls from every discipline, federated in Navisworks or Solibri, clash detection run against the agreed matrix.
Chair the coordination meeting
Clashes triaged live, owners assigned, RFIs raised with screenshots and viewpoint references attached — not just a spreadsheet of clash counts.
Close the loop
Track every clash to resolution, re-run detection to confirm, and archive the federated model as the as-coordinated record.
The deliverable isn't a clash report. It's a closed clash log — every conflict found, assigned, resolved, and verified before it becomes a site problem.
Section 03 · Deliverables
What you receive.
02
Clash detection report
Full clash matrix run, prioritized by severity, with viewpoint screenshots for every hard clash.
03
RFI log
Every clash traced to a raised RFI, owner, and resolution — not a static PDF that goes stale in a week.
04
Coordination meeting minutes
Weekly minutes with decisions, action owners, and due dates — distributed within 24 hours of each session.
05
CDE administration
Folder structure, permission management, and document control on BIM 360 / ACC for the project's life.
06
As-coordinated archive
Final federated model and resolution history handed off at project close, ready for FM or as-built reference.
Section 04 · Tools & standards
What we coordinate in.
Our default federation stack — matched to whatever platform the client's project team already runs.
Navisworks Manage
Autodesk BIM 360
Solibri Office
Autodesk Construction Cloud
Standards we coordinate to — happy to apply your in-house standard instead.
ISO 19650-2
BS 1192
COBie 2.4
CDE workflows
Section 05 · Recent work
A coordination engagement in practice.
Case study · 01 of 6
Central Tower
ChennaiIndiaCommercial2024
Thirty-two storeys, full BIM coordination across every discipline. Weekly federation and clash runs from week one, RFI log managed on ACC, and a coordination meeting chaired every Thursday for the life of the build. Final clash log: closed.
Read the case study
Discuss this pillar
Tired of clashes
Tired of clashes
found on site?
Send us your discipline list and federation platform. We respond within 24 hours.