Clash Coordination
Group thousands of raw clashes into a workable number of real issues, prioritised by consequence.
A clash report is not a coordination problem, it is a list. The same duct crossing the same beam produces forty clashes, and the work is deciding which of them matter.
Clash Coordination groups the raw list into issues, then prioritises those issues by what they will cost on site.
Getting clashes in
Two routes, and the module behaves the same either way.
- Import a BCF file. Any tool that exports BCF or BCFZIP works. No installation needed.
- Sync live from Navisworks. Needs the Bridge running with the model open. Live sync also lets Bimiq render a clash viewpoint on demand rather than relying on the snapshot in the file.
Grouping
Raw clashes group into issues first, deterministically, on the elements involved and where they are. This step is free and it is where the count collapses: one duct through one beam becomes one issue rather than forty rows.
Everything after this point works on issues, not clashes.
Triage
Triage assigns each issue a priority, which is Bimiq's read of consequence rather than the geometric severity your clash tool reported.
| Priority | Meaning |
|---|---|
| Critical | Will stop work or force rework if it reaches site |
| High | A real coordination problem needing a decision |
| Medium | Should be resolved, but not urgent |
| Low | Minor or likely tolerable |
Geometric overlap and consequence are not the same thing. A 3 mm overlap between a structural member and a primary duct run matters more than a 200 mm overlap between two items that will be resolved on site as a matter of course.
Dismissing noise
Issues can be set aside with a reason: duplicate, tolerance, temporary, and similar. Dismissal is a category, not a delete, and dismissed issues stay reviewable. When most of a report is noise, the reason you dismissed something is worth more later than the dismissal itself.
Working an issue
Each issue carries its own workflow status, separate from whatever status the clash had in the source tool.
| Status | Meaning |
|---|---|
| New | Not yet looked at |
| Acknowledged | Seen, accepted as real |
| In progress | Being resolved |
| Resolved | Done |
From an issue you can raise an RFI, and the elements, location and priority travel with it.
Re-triage keeps your judgement
When the model moves and you sync again, re-triage does not overwrite what you decided. An issue whose priority, status or dismissal you changed by hand keeps your value. Re-syncing updates the rest idempotently rather than resetting the board.
This matters because coordination runs weekly for months. A tool that forgets your triage every Monday is worse than no tool.
Cost
Triage is metered on AI-triaged issues, not on raw clashes, and it is capped: beyond 800 issues in a run the cost stops rising. Grouping is free, so importing a large report and looking at the issue count costs nothing. See How credits work.