Clash coordination
How do we find the clashes that matter — and get them fixed?
Plan the tests, run them on shared models, group thousands of clash points into a few real issues, and move them between tools with BCF.
Understand
What it is, in plain language
- Pedia · WorkflowsClash detection types (hard, clearance, duplicate)The three kinds of clash test — physical overlap, insufficient clearance and duplicated elements — and what each is good for.
- Pedia · WorkflowsModel federationCombining separate discipline models into one coordinated view without merging them, so each team keeps ownership of its own model.
- Pedia · SoftwareBCF (BIM Collaboration Format)An open format from buildingSMART for exchanging model-based issues — with viewpoints, comments and element references — between BIM tools.
- Pedia · SoftwareCoordination and model checking softwareThe tools used to federate models, run clash and rule checks, and manage issues — what they do and how they fit into the coordination cycle.
- Pedia · GlossaryTolerance (clash)The distance below which a clash test ignores an overlap, so tiny modelling overlaps are not reported.
- Pedia · GlossaryClash groupA set of related clash results treated as one coordination problem, such as one duct run crossing several beams.
- Pedia · GlossaryViewpointA saved view of a model — camera position, visible and selected elements, sections — used to show exactly where an issue is.
Do
Tools that export Excel, PDF and Word
- Tool · Excel · PDF · WordClash Test MatrixUse it at the start of coordination to decide which clash tests to run.
- Tool · Excel · PDF · WordClash Report ImporterUse it after a clash run to turn thousands of clashes into a few issues.
- Tool · Excel · PDF · WordBCF Viewer & ExporterUse it to read issues from BIM tools, or send your issues back to them.
- Tool · Excel · PDF · Word3D IFC ViewerUse it to look at a model without installing software, or to show where requirements fail.
How it works
The process, at a glance
Shared modelsFrom the CDE
Run clash testsNavisworks or similar
Clash reportXML or CSV
Plan the tests, run them on shared models, group the results and track them as issues.
Your BIM toolSolibri, Revizto, Navisworks…
.bcfzipTopics, comments, snapshots
Common mistakes
What goes wrong most often on real projects.
- Sending raw clash counts instead of grouped issues.
- Raising the tolerance until the numbers look acceptable.
- Running tests on work in progress instead of shared models.
Is it in place on your project?
Tick what is done — it counts towards the checkpoint on your learning path.
0 / 4 in place
Keep going