Tools · clash explorer · EI-WEB-004.2
Find a clash. Move the run. Watch it resolve.
The sample model as it was received: 14 crossings of a system and a structural member, computed from the geometry at real sizes. Select one, move its run up or down, and the overlap is recomputed as you go. Resolved rows stay in the list.
Four sample buildings, generated, not real projects. The office is the sample model counted above; the villa, the residential block and the industrial hall are checked the same way. G moves to the next.
- System
- Member
- As received
- Now
Select a clash in the list or in the model. J jumps to the next open one.
| ID | Clash | Overlap | State |
|---|
Indicative
What the open clashes would cost, found later.
The multipliers are the 1-10-100 rule of thumb from quality management, usually credited to Labovitz and Chang (1992): a fault costs more the later it is found. It is illustrative, not measured on construction. Put in your own figures.
How it is computed
Boxes at real size, checked against every member.
Each duct, pipe and tray is a chain of boxes at its size; each beam, column and slab is a box at its section. A hard clash is an intersection. For a horizontal run its overlap is the smallest move up or down that clears it; for a riser, the depth of the slab it passes through. A clearance clash is two elements closer than the clearance you set. The same computation counts the clashes on the first screen, and the build checks it before the site is published.
The export is BCF 2.1, checked against buildingSMART’s schemas. Each issue selects its two elements by IFC GlobalId and carries a viewpoint looking at it.
Your model has its own count.
Request a model audit. We return every clash with its overlap and its state, as a report and as BCF.
Request a model audit