Run a clash profile audit
Define a clash profile - which element sets test against which, and at what tolerance - run it against the federation, triage the hits down to the real clashes and push them out as issues to fix.
How it works, step by step
4 steps across the platform - what you do at each one, and why it matters.
Define the clash profile
Clash ProfilesSet up the profile: which element sets test against which - ducts against structure, pipes against ducts - and the tolerance that counts as a real hit.
Why: The profile decides whether the run is useful or noise. Pairing the right sets and setting a real tolerance is what keeps the result to clashes a person actually needs to resolve.
Run it against the model
Clash DetectionRun the profile against the federated model and let it list every hit that breaks the tolerance you set, ready to be worked through.
Why: Running to a defined profile makes the result repeatable: the next run after a design update is comparable, so you can see whether coordination is getting better or worse.
Triage the hits
Clash DetectionGroup the hits, drop the duplicates and the harmless brushes, and keep the genuine clashes that need a design change, so the review works a short real list.
Why: A team that has to wade through a thousand false clashes stops reading the report. Triaging to the real ones is what keeps clash detection trusted rather than ignored.
Push them out as issues
Model IssuesTurn each real clash into a BCF issue with its viewpoint and owner, so it is tracked to resolution and does not reappear on the next run.
Why: A clash that is not assigned is a clash that stays. Pushing the real ones out as owned issues is the difference between an audit and a solved problem.