Navisworks Coordination Issues Add-In

The Navisworks Coordination Issues Add-In allows you to open models and views from Model Coordination, combine models into aggregated views with associated NWFs, and work with Model Coordination-based issues in Navisworks. Issues created in Navisworks, either directly on a model, or from clash tests, can be synced back into Model Coordination for review. Any subsequent changes made to these issues in Model Coordination are reflected back in Navisworks.

Note: The add-in supports both Autodesk Forma and BIM 360-based projects. For BIM 360 projects, models must be stored in the Project Files folder in the BIM 360 Document Management module. For Autodesk Forma projects, models must be stored in Forma Data Management. Models must also be included in an active coordination space in Model Coordination.

You can download the add-in from the Autodesk App Store, and it's also available to subscribers in the Autodesk Desktop App.

This topic provides details about working with clash issues from Navisworks in Model Coordination. For more information about working generally with issues between Model Coordination and Navisworks, see the Navisworks Coordination Issues Add-In help.

Navisworks Clash Issues in Model Coordination

Navisworks Clash Issues in Model Coordination

Can I view Navisworks clash highlighting in Model Coordination?

Yes. Navisworks clash issues, created with the Navisworks Coordination Issues Add-In version 5.0.0 or later, display clash highlighting with a dimmed background when viewed in Model Coordination, subject to the following limitations.

Navisworks clash issues created with older versions of the add-in can still be viewed, but do not display clash highlighting.

Can I view clash highlighting in Model Coordination for Navisworks issues that reference files without stable IDs?

No. Generally, Model Coordination requires that each model element has a stable and unique ID across file versions. This ensures that clashes and other data remain associated with the correct elements when models are updated. For this reason, clash highlighting is not supported for files without stable IDs.

For a full list of supported file formats, see the Supported Files in Model Coordination help.

Can I tell which clash test generated a Navisworks clash issue?

No. Model Coordination doesn't indicate which Navisworks clash test type was used to generate a clash issue.

Specifically, you can't determine whether a Navisworks clash issue originated from:

Hard clash tests
Clearance clash tests
Duplicate clash tests

As a result:

For clearance clash tests, you may see clash highlighting even when objects are not physically touching. This is expected behavior.
For duplicate clash tests, clashes may not be visually obvious, which can make interpretation less clear.

Can I identify generic issues created in Navisworks?

No. Generic issues created in Navisworks do not display an identifying icon or visual indicator in Model Coordination.

Can I identify legacy Navisworks clash issues created in an add-in version older than 5.0.0?

No. Navisworks clash issues created with a version of the Navisworks Coordination Issues Add-In older than 5.0.0 are not identified as Navisworks-created issues in Model Coordination.

Navisworks clash issues created with an add-in version 5.0.0 (released April 2025) or later, display a Navisworks icon in the UI. Hovering over the icon shows a tooltip with a link to help documentation. This applies to all identifiable Navisworks clash issues, including those that reference files without stable IDs.

Note: Navisworks clash issues with unstable IDs are identifiable with the Navisworks icon, but do not display clash highlighting.

How are Navisworks clash groups handled when some files have stable IDs and others do not?

Navisworks clash issues can contain multiple clashes grouped into a single issue. Clash highlighting is evaluated per clash, not per group, meaning that:

Clash highlighting is shown for individual clashes where all involved objects come from files with stable IDs.
Clash highlighting is not shown for individual clashes where at least one object comes from a file without stable IDs.

Therefore single clash groups might display only partial clash highlighting. In these cases, a banner is displayed to indicate that only partial highlighting is being shown.

What happens when I resolve a Navisworks clash issue in the authoring model and then republish the model into Model Coordination?

Resolved Navisworks clashes continue to display clash highlighting in Model Coordination after republishing. This is a known behavioral difference from native Model Coordination clashes:

Model Coordination clashes: Once resolved, objects no longer clash and no longer display clash highlighting.
Navisworks clash issues: Objects may no longer clash, but clash highlighting remains visible.

This is important to understand because it can be confused with clashes from a clearance clash test, where objects may not be touching but are still considered a clash. Currently, there is no notification displayed to indicate this scenario, as the difference between a resolved clash and an active clearance clash test can't currently be distinguished.

Review the issue status and take care when clash highlighting is visible on objects that appear not to be touching, as this may indicate a clearance clash test result rather than an unresolved hard clash.

Can I see clash information for Navisworks clash issues in Model Coordination?

Yes. Navisworks clash issues can be viewed and tracked in the Clashes tab of an issue's Details panel in Model Coordination.

Can I see clash information for Navisworks clash issues that reference files without stable IDs?

No. Clash information is not shown in the Clashes tab for clashes that reference files without stable IDs.

If all files referenced by a Navisworks clash issue lack stable IDs, no clash data is available in the Clashes tab.
If a clash group contains a mix of files with stable and unstable IDs:
- Clash information is shown only for clashes that reference files with stable IDs.
- Clash information is not shown for clashes that reference files without stable IDs, even if only one object in the clash references a file without stable IDs.

As a result, a single clash group can display partial clash information in the Clashes tab.

Can I filter out Navisworks clash issues from Model Coordination clash issues in the Issues tool?

Yes. In the Issues tool, clash issues can be filtered based on the originating application. The issue categories filter separates issues into three categories:

All issues. This includes:
- All Navisworks clash issues (created with any add-in version)
- Model Coordination clash issues
- Navisworks generic issues
- Model Coordination generic issues
Model Coordination clash issues
Navisworks clash issues (created with an add-in version of 5.0.0 or later)

Note: Navisworks clash issues can be viewed in both clash on and clash off coordination spaces.