Clashes to issues (Add-ins)
Our "Clashes to issues" feature lets you publish clashes detected by Navisworks directly to BIM Track and share them with your team. Our suggested workflow gives you the ability to quickly exchange clashes with all the users involved in the project while they're using different platforms. This eliminates the need to exchange complicated Excel sheets and clash reports by emails. Clashes information can be quickly recovered in the originating software such as Revit and Tekla, giving the user the ability to quickly review a clash in its context within a few clicks!
In Navisworks, it is possible to group multiple clashes to better organize your results. BIM Track lets you keep the same structure by creating a single issue for each group. Clashes contained in a group are appended to the issue as viewpoints. So, let's say that in Navisworks you have a group that contains 6 clashes, when this group will be published to BIM Track it will result in 1 single issue that contains 7 viewpoints (1 viewpoint for the group and 6 for the clashes).
Please check out the video below for step-by-step instructions on how to publish and group clashes detected by Navisworks directly to BIM Track:
Viewpoints & Save View State
In Navisworks’ clash detective window, you can select a clash or a group and adjust the viewpoint. Once a viewpoint has been updated, camera icon will appear next to it. Those viewpoints will be used when you export your clashes to BIM Track. Note that BIM Track records all the information pertaining to your current view, and so if you are using a perspective view, your issues/clashes to BIM Track with that information. Later, when you will review that issue/clash, the view will be restored using the same view type. So, if you publish an issue from Navisworks using a perspective camera and review it in Revit later on, the issue location will be recovered in a perspective view. As clashes are generally resolved in the authoring software (Revit, Tekla Structures, etc.) and since these software have limited support for perspective cameras, we suggest that you publish your clashes using an orthographic camera. This will make it easier for other parties to locate the flagged issues.
If you’re publishing a large number of clashes, we recommend removing the “Save view state” option in the export window. This feature records all the hidden elements in the model. On very large models where there can be hundreds of millions of elements, this option will add a lot of time in the publishing steps as hidden elements are stored in a file one by one using their IDs.
Clash Status Synchronization
When you run your tests for a second time, clashes statuses are automatically updated in Navisworks’ clash detective window. BIM Track gives you the possibility to update those statuses accordingly on our platform as well. When your clash statuses have changed in Navisworks, simply click the “Clash to Issue” button in the interface. This feature should eliminate the need to review the status of each clash published to BIM Track. To use this feature, you first need to publish your clashes to BIM Track using the “Clash to issue” feature. As the project advances, when clashes are resolved, simply run a new detection round by Navisworks to update the results returned by the clash detective. Once the clash detective results have been updated, you can update them accordingly in BIM Track by performing a new “Clash to issue” and ensuring that the option “Update BIM Track status for existing clashes” is checked.
Isolate Clash Elements
When you publish your clashes to BIM Track, the add-in records the two elements linked to the clash. When reviewing that clashes using BIM Track add-in or our 3D Viewer, it is possible to isolate the two elements linked to that clash which gives you the ability to get a quick visual cue of the issue report.
It is possible to add various properties related to your clashed directly in the description of the issue published to BIM Track. This action will only work when clashes are published for the first time. No information is added to the description of the issue when you publish the same clash test for a second time.
In the status section, you can filter out some clashes using their status. Using this feature, you can specify which clashed are going to be exported based on their status. So, if you have clashes that are already resolved, you can specify to not publish them to BIM Track by checking all the other statuses and leaving the “Resolved” check box empty.
Clash test selection
In the top of the “Clash to issues” configuration window, you can select which tests are going to be exported. So, if you’d like to export a single test instead of all of them, make sure to select the corresponding test before hitting the publish button.
Fields & attributes
Like normal issues published to BIM Track, the standard set of attributes can be configured by batch before publishing you clash tests. You can specify that the group field will be automatically filled using the name of the clash tests associated to the clash published (See the “Group Field” section below for more information).
It is possible to automatically fill the group attributes by checking the option “Automatically fill the group field with the clash test name”. This option adds the name of the selected clash tests to the group field of the corresponding clash published to BIM Track. We recommend using this option as it gives you a quick way to filter the issues related to that clash test later by filtering BIM Track issues list. So, let’s say you have published an “HVAC va Struc” clash test, you can open the filter menu in the issue list and type “Hvac vs Struc” in the group box to filter issues related to that clash test.