Table of Contents
The Clash Manager for Navisworks® is a Procore BIM Plugin component that speeds up coordination. It syncs seamlessly with Procore’s Coordination Issues tool to help your team find and fix issues early.
Key benefits include:
Link your Navisworks® model to a Procore project using the Procore BIM Plugin. The Procore BIM Plugin is required to publish models for mobile viewing and manage coordination issues directly from your Windows®-based design software. Ensuring all stakeholders have access to the most current model data helps reduce RFIs and keeps the project on schedule.
Create 3D areas to include dynamic location data in your clash group names automatically. You can verify these areas directly in the 3D view. Distill handles configuration flexibly: it assigns clashes in overlapping areas to the smallest zone, or it can combine names to describe multiple locations. This approach lets you sort groups by name, making it easy to isolate clashes within a specific area.
You can customize how Clash Manager automatically names your clash groups to match your company's preferences. Defining a standard naming template provides clear, consistent tracking across your project coordination workflows.
When a clash group spans multiple nested areas, you can concatenate area names to include multiple area descriptions in the title. This gives your team better context and visibility into the exact locations of model clashes.
Distill is an automated clash grouping algorithm. It processes the multitude of clashes from Navisworks® and organizes them into intelligent groups that represent specific, actionable issues within your model.
Distill lists every active Navisworks® clash test. You can customize settings for each test, and changes save directly to the model for team-wide consistency.
Focus / Global Slider: Controls grouping density:
Focus creates tight clusters.
Global gathers clashes over a wider area.
Model Most Likely to Move: Sets the coordination hierarchy.
Select the more flexible model (e.g., plumbing vs. structure).
Distill groups clashes around the element that needs fixing.
Default Behavior: New clashes are added to Active or Reviewed groups.
Protected Groups: Distill will not change groups marked Approved or Resolved.
After Distill processes the clashes, it creates a list of groups.
By default, groups are named "Group" followed by a unique number (e.g., Group 69). This number is never reused within that clash test, even if you delete or rename the group, ensuring clear communication with your team.
The list of groups is sorted in descending order of the number of clashes within each group, providing a priority list for review.
Distill groups all related clashes that make up a single problem in an area that can be addressed together. For example, one group for a ductwork problem includes hanger hits, insulation hits, and duct hits.
Use the Heatmap to quickly find high-priority clashes in your model. It provides a central location to review and track these critical areas so you can focus your coordination efforts where they matter most.
Procore recommends running the Heatmap:
Clean up the Heatmap to reduce the number of clash groups and viewpoints on the model.
Use the Orient tool to isolate specific objects by hiding surrounding systems. This focused view makes it easier to inspect clashes, share precise locations, and navigate in 3D. You can select single or multiple objects across different models.
Visibility: Choose which object sets remain visible during orientation.
Direction: Define the 'top' direction for 2D plan views.
Cut Plane: Adjust the vertical offset of the Cut Plane.
Use the Isolate feature to analyze specific model areas, providing a focused perspective on selected clashes or individual model items against the backdrop of the surrounding model. This tool allows you to resize the isolated area, zoom in for details, and add clashes to the section box. You can also add clashes the section box.
Use the Bulk Rename feature to update the names of multiple clash groups. By applying custom naming conventions or utilizing standardized templates, you can ensure consistency across your coordination issues and streamline project tracking.
Use Viewpoints to effectively organize and communicate model clash data during coordination. By providing immediate location context, Viewpoints streamline the note-taking process. Users can generate multiple viewpoints per clash test, choosing from 3D, Orient Plan, or Isolate view types to best capture the necessary details.
You can automatically create viewpoints for each clash to provide consistency and streamline your workflow. You can create viewpoints for specific clash statuses, so that you can focus on the most important issues. Viewpoints are saved to a time-stamped folder, creating a clear record in time. You can create 3 different types of viewpoints: 3D View, Orient Plan View, and Isolate View.
You can create one or more coordination issues directly from your clashes or clash groups in the Procore Clash Manager for Navisworks® feature, which is a component of the Procore BIM Plugin. A separate coordination issue is created for each item selected.
Did you know you can create, edit, and view coordination issues from a variety of different Procore tools and products? To learn more, see What are the different tools I can use to create a coordination issue?
|
Field Name |
Description |
Required? |
Notes |
|---|---|---|---|
|
Snapshot |
Displays a thumbnail image of the current view to illustrate the issue. |
No |
|
|
Title |
Enter a concise, descriptive name for the issue to help collaborators identify it. |
Yes |
|
|
Description |
Provide a detailed summary of the issue. This text is also saved as a viewpoint comment in the final NWD file. |
No |
When creating an issue from Clash Manager, you can also select Append Clash Comments or Append Redline Text. |
|
Location |
Select the primary project location where the issue occurs. |
No |
|
|
Due Date |
Set the target deadline for issue resolution. |
No |
|
|
Priority |
Select the level of urgency: Low, Medium, High, or Critical. |
No |
|
|
Assignee |
Select the person responsible for resolving the issue. |
No |
This list only includes users with 'Standard' or 'Admin' level permissions for the Coordination Issues tool. |
|
Watchers |
Select team members to receive email updates. |
No |
Watchers must have at least 'Read Only' permissions for the Coordination Issues tool. |
|
Trade |
Identify the discipline involved (e.g., Mechanical, Electrical). |
No |
|
|
Type |
Categorize the issue for reporting and tracking. |
No |
Options include: Building Code, Clash, Client Feedback, Constructability, Coordination, Design Review, Existing Condition, Requirement Change or Other. |
|
Private |
Select this checkbox to limit issue visibility. |
No |
When checked, the issue is only visible to the Creator, Assignee, Watchers, and users with 'Admin' level permissions on the Coordination Issues tool. |
|
Source File |
Displays the name of the source file. |
No |
Automatically generated if the source file name exists. |
|
Created From |
Displays the name of the originating source tool. |
No |
Automatically generated. |
|
Date Created |
Displays the creation date and the creator's name. |
No |
Automatically generated. |
|
Attachments |
Upload up to 20 relevant images, PDFs, or documents to provide additional context. |
No |
Maximum of 20 files. |
|
Custom Fields |
Displays any company-specific fields configured for the Coordination Issues tool |
Varies |
Click Create.
Procore creates a new coordination issue in the Open status for your selections.
Sync coordination issues to keep both Procore and Navisworks® up-to-date. The smoother workflow reduces errors and manual work. When both systems are updated, the responsible person is clear and accountable.
Learn which user permissions are required to take the described actions in this tool.
Permissions for the actions below are managed in the Coordination Issues tool.
| | The action is available on Procore's Web, iOS, and/or Android application.
Users can take the action with this permission level.
Users can take this action with this permission level AND one or more additional requirements, like granular permissions.
|
Action |
None |
Read Only |
Standard |
Admin |
Notes |
|---|---|---|---|---|---|
|
Associate a Navisworks® Model with a Procore Project |
|
Users also need 'Admin' level permissions on the Models tool. |
|||
|
Bulk Rename Clash Groups |
|
|
|||
|
Clean Up a Heatmap |
|
|
|||
|
Concatenate Area Names |
|
|
|||
|
Create Areas to Name Clash Groups |
|
|
|||
|
Create Bulk Viewpoints |
|
|
|||
|
Create Coordination Issues |
|
|
|||
|
Create Viewpoints |
|
|
|||
|
Isolate Model Items |
|
|
|||
|
Orient to the Model |
|
|
|||
|
Run a Heatmap |
|
|
|||
|
Run Distill |
|
|
|||
|
Set Group Naming Templates |
|
|
|||
|
Sync CI Changes |
|
|