BIM & takeoff
Get 6D carbon from a BIM model
Turn a converted BIM model into an embodied carbon footprint. Auto-enrich reads quantities…
5 steps12 minOpen
Cases / BIM & takeoff
BIM & takeoff
Coordinate models and resolve clashes
Bring the discipline models together on one coordinate base, run the clash test, clear the noise, and push the conflicts that matter to the people who can fix them.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
1
Federate the models
FederationsLoad the architectural, structural and MEP models into a single federation and confirm every one lands on the same project origin, the same shared grid and the same level naming.
Why: If one model sits a metre off the others, the clash engine reports the whole building colliding with itself. Getting the coordinate base right is the quiet work that makes everything after it meaningful.
InArchitectural modelStructural modelMEP modelOutFederated modelAligned coordinate base
2
Run and triage the clash test
Clash detectionRun the tests between the disciplines that actually interfere, group the hits by system, and strip out the tolerance touches, insulation overlaps and duplicates so a workable list remains.
Why: A raw run returns thousands of hits and nobody opens it twice. Triage is what turns that dump into the handful of real conflicts a coordination meeting can actually decide on.
InFederated modelClash test rulesOutTriaged clash listConflicts by system
3
Drive the conflicts to closure
Non-conformanceRaise each surviving conflict as a tracked issue, assign it to the discipline that owns the fix, and follow it through re-issue until the corrected model clears the re-run.
Why: A duct clashing a beam is a ten-minute model edit today. Discovered on site with the steel already up, it becomes a rework order, a variation and a hole in the programme.
InTriaged clash listDiscipline ownersOutTracked clash issuesCleared re-runCorrected models
Modules in this playbook
3 / 184 platform modules
