Structured, prioritised clash detection using Navisworks Manage — with a proper clash matrix, filtered reports by discipline, and a real resolution workflow that stops the same clashes coming back.
Raw Navisworks reports with 8,000 clashes are useless. Half are duplicates, most are minor, and none tell the contractor what to fix first. I set up a proper clash matrix, tune clash tolerances per discipline pair, and produce filtered reports each team can action.
For active projects I run rounds — clash test, issue distribution, tracked resolution in BIM 360 / BCF, retest — until the model is genuinely coordination-ready. Not just tested.
Collect the latest .rvt / .ifc / .dwg from each discipline; confirm alignment origin.
Aggregate in Navisworks with appearance profile, saved viewpoints, selection sets.
Define which discipline pairs to test and with what tolerance (e.g. 25 mm hard, 100 mm soft).
Execute clash tests, group by element, filter duplicates and false positives.
Issue BCF/PDF reports to each discipline; track resolution round by round.
Any .rvt / .ifc / .dwg model can be federated. BCF workflow supports round-trip issue resolution with the original design authors.
For an uncoordinated multi-storey commercial project — thousands. That's normal. My job is to filter them down to the 100-200 that actually matter.
Yes — I can chair coordination meetings in your time zone, drive the resolution list, and issue minutes with tracked actions.
Yes. Full support for BIM 360 Coordinate / ACC clash workflows including in-app issue creation and status tracking.