We want to ensure that each clash job we define uses a set of default clash rules we define. Perhaps this could be a clash job template.

Currently, individual clashes need to be selected one by one in the clash test results list within design review. It will be much more time efficient to be able to select one clash, move up and down the list and click and hold the 'Shift' Key and ...

As we have a large dataset of clashes to manage (50 000) We start looking at the clashes and decide to assign 1000 clash to an issue. As we continue our investigation of the clashes results, we find 500 other clash that we would like to add to the...

We can probably do this if the realty mesh is imported using an iModel connector, but that workflow is not defined properly yet. Should explore if we can do this against a ContextShare model.

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 det...

User Request following a clash run, add the ability to export a PDF of all clashes in a single PDF including a thumbnail that shows the clash Requirements: Create a PDF Report generator in the export result section. Support image exports for PDF f...

It would be very useful if there was an easy way to copy Design Validation Tests across projects, or the ability to create template tests. For example, our clash detection definitions are the same across all of our projects. Although there is expo...

Given the extent and size of models that users will typically encounter with imodels, it would be good to be able to select some elements and run a quick localised clash detection for review purposes. Feeds to BCF / IRS-style reporting and Teams c...