Tutorial Videos

Clashes to Issues (Add-ins)



The Clashes to issues feature publishes clashes detected by Navisworks directly to BIM Track. The suggested workflow gives the ability to quickly share clashes with all the users involved in the project possibly using different platforms. This eliminates the need to exchange complicated Excel sheets and clash reports sent by email. Clash information can be quickly recovered in any connecting software such as Revit and Tekla, giving the user the ability to quickly review a clash in its context with just a few clicks!

Group Clashes

In Navisworks, it is possible to group multiple clashes to better organize your results. BIM Track keeps the same structure by creating a single issue for each group. Clashes contained in a group are appended to the issue as separate viewpoints. For example: In Navisworks when a group that contains 6 clashes is  published to BIM Track it will result in 1 single issue that contains 7 viewpoints (1 viewpoint for the group and 6 for each individual clash).

 

Viewpoints & Save View State

In the Navisworks clash detective window, it’s possible to select a clash or a group and adjust the viewpoint. Once a viewpoint has been updated, a camera icon  will appear next to it. Those viewpoints will be used when exporting clashes to BIM Track. Note: BIM Track records all the information pertaining to the current view, and so if a perspective view is used, the issue/clash is sent to BIM Track with that information. Then, when reviewing that issue/clash, the view will be restored using the same view settings. For example: If an issue is published from Navisworks using a perspective camera and reviewed in Revit later on, the issue will be recovered in a perspective view. It is suggested to publish clashes using an orthographic camera because there are limitations in various softwares surrounding the perspective camera mode. This will make it easier for other parties to locate and view the issues.

The Save view state from clashes option has been added in the settings window. This feature records all visual information for all elements in the model. On very large models where there can a large number of elements, this option will add a lot of time in the publishing process and also when recovering these views using the View in Model function.


Isolate Clash Elements

When a clash is published to BIM Track, the add-in records the two elements linked to the clash. When reviewing that clash using BIM Track add-in or the online 3D Viewer, it is possible to isolate the two elements linked to that clash which gives the ability to get a quick visual of the issues elements.

Clash Properties

Various properties related to the clash can be added directly in the description of the issue published to BIM Track. This only works when clashes are published for the first time. No information is added to the description of the issue if the same clash test is published for a second time.

Clash Status to Export

In the Clash Status to Export section, it is possible to filter clashes using the status. Using this list to help specify which clashes are going to be exported based on the status.

Clash Test Selection

At the top of the Clashes to Issues configuration window, select which tests are going to be exported. Any number of tests can be published, simply make sure to select the proper test(s) prior to publishing.

Fields and Attributes

A standard set of attributes can be configured prior to publishing a clash test. Remember all the attributes set at this stage in the process will only be transferred for new issues being created and will not apply to exist issues being updated.

Group Attribute

The group attribute can be automatically filled by checking the option. This option adds the name of the corresponding clash test to the group where it originated directly to BIM Track. 

BIM Tracker Hint: This option gives a quick way to filter the issues related to that clash test later by filtering BIM Track issues list.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.