Explore a federated model the way a coordination team does. Toggle disciplines on and off, step through the hard clashes between structure, mechanical, hydraulic, electrical and fire, and drive each one to resolution, the same multi-discipline coordination we run in Navisworks and Revizto.
What this demonstrates
Multi-discipline BIM coordination. The same federated coordination workflow we run in Navisworks and Revizto, deployed as an in-browser proof-of-concept for owners and delivery teams.
Supply duct passes through transfer beam
6
Open
2
In review
1
Resolved
How these demos relate to the systems we build for clients.
Federating the structural, mechanical, hydraulic, electrical and fire models into one coordinated model and testing where elements from different disciplines occupy the same space. Each hard clash is logged with the disciplines involved, its location and a severity, then tracked to resolution.
No, the services and clashes here are a synthetic illustration. In client work the clashes come from Navisworks or Revizto tests on the real federated model, and each one is issued as a BCF item and tracked in the common data environment.
Detection is only useful if every clash is driven to closure. Select a clash here and mark it resolved to see the count fall; in production the same status flows through a coordination workflow with responsible parties, due dates and sign-off, which is what the companion Clash Resolution Dashboard reports on.
These are the most services-dense projects in the industry. Resolving clashes in the model, discipline by discipline, before they reach site is one of the highest-leverage things a coordination team does for programme and cost certainty.
Everything in the Playground is built with the same stack we deploy for clients: configurators driven by real product masters, planners connected to BIM data, and AR experiences served straight from the product catalogue.
Start a Conversation