Some of our clash tests yield very large clash count totals ranging into the tens of thousands. A lot of these clashes are acceptable clashes that can be suppressed by a combination of rule based and manual suppression. The first step in clash detection is to apply as much rule based / manual suppression as possible BEFORE sharing clash test results to the 3D models designers for clash resolution. The unsuppressed clash totals is a true representation of real issues in the design that needs to be reviewed and addressed.

Problem / Idea:

The total clashes that does not take into account the suppressed clashes is of little value to the reviewer as it does not represent the true total of clashes that is left to be reviewed and addresses. Yes it gives an overview to the ‘Validate’ iTwin users managing and running clash tests, but clash test results are aimed at the design teams who maintains the 3D Models – they are only interested in how many clashing issues is left to be reviewed and resolved.

The total in the ‘Clashes’ column can be very misleading. For example: 1,000 clashes were detected. 980 of these clashes are acceptable and have been suppressed in a combination of rule based and manual suppression. Only 20 clashing instances remain that represents a true clash in the design. The 3D Model designer has 20 clashes to review and resolve.

Having an ‘Unsuppressed clash total’ next to the ‘clashes’ will show: Clashes: 1,000, Unsuppressed clashes: 20 indicating the true number of issue that need to be reviewed.

May we please request a new column that lists ‘Unsuppressed clash total’ next to the ‘clashes’ in Infrastructure cloud clash test results as these values are what interests the 3D Model Designers.