ClashTrix is a powerful Navisworks plugin designed to enhance clash detection workflows by automating data extraction, clash test management, and batch operations. It provides an intuitive ribbon interface with a comprehensive set of commands to improve efficiency in BIM coordination.

Key Features & Commands:

• Tests & Sets:

• Export Properties: Extracts element categories and properties for checking and facilitating test and set creation.
• Tests Builder: Batch generates sets and tests using defined element properties.
• Export/Import Types: Exports a matrix containing test types and tolerances, which you can modify and import back.
• Export/Import Priority: Exports a matrix containing test priorities, which you can modify and import back.
• Flip Side: Switches Selection A and B for selected tests.

• Clash Status:

• Export Approved: Extracts approved and reviewed clash results to an XML file.
• Import Approved: Imports an XML file containing approved and reviewed clash results into your model.
• Summary Matrix: Generates an Excel clash matrix with counts of remaining active clashes.
• Summary Table: Exports clash tests with clash counts and statuses to a CSV table.
• Detailed Tests Export: Exports selected test results to an Excel file containing detailed information about clashing elements.

• Clash Management:

• Group Clashes: Organizes clash results into groups based on custom rules.
• Smart Results: Batch renames clash results from default names (e.g., "Clash1") to meaningful names.
• Auto Update: Updates result statuses based on defined property criteria. Supports OR groups and profiles.
• Clash View: Quickly generates viewpoints for every clash result within your selected tests.
• Sync Viewpoints: Synchronizes clash result statuses from their relevant viewpoint subfolders to the actual test results.
• Export Viewpoints: Exports viewpoints generated by Clash View as images matching the desired size and resolution.

• Power Tools:

• Select by ID: Quickly selects elements based on their Revit Element ID values. Isolates and generates a section box as needed.
• Annotate Pro: Annotates elements with coordinates and property data.
• Renamer: Batch renames tests, sets, and viewpoints based on predefined rules.
• Purge: Deletes tests, sets, and viewpoints matching specific criteria.
• Bulk Actions: Applies batch modifications to clash tests efficiently.

Exports selected element properties to a CSV table. Comes with predefined rules for Revit, Civil 3D, and IFC to quickly export properties that can be used with the Tests Builder to create sets and tests.

Key Features:

• Ability to gather all existing categories, allowing you to determine what should not exist in a particular model (example: Structural Columns modeled in the Architectural model).
• Use the exported CSV with the Tests Builder tool to generate tailored clash tests and sets based on the existing categories.
• Executes very fast on extremely large models. Ability to select which loaded models to export properties from.

This tool automates the creation of selection sets and clash tests using data from a CSV file (You can use the csv generated from Export Properties tool). It streamlines clash detection workflows and enhances productivity for BIM professionals.

Key Features:

• Generate sets and tests based on imported CSV file.
• Set the clash test type, tolerance and composite object options.
• Defined categories to be ingnored from the sets and tests creation.
• Combine several categories into a single set.
• Save the settings as default template to be used in future projects.
• Skip sets creation and use existing sets to generate tests.
• Create MODEL vs MODEL tests or Categories vs Categories as needed.

Example CSV File Format:

Form Guide:

• Prefix to Skip ⇛ The name part that falls before the discipline code. Value should be "ADSK-SNT-" for above table.
• Name Seperator ⇛ The seperator character between the discpline code and the element category which will be used for sets and test naming. Example value for dash "-" will result into ARC-Ceilings.
• Discipline Code Length ⇛ The character length for displines code. For above example, the value should be 3 since the code is ARC.
• Clash Separator ⇛ The seperator between the sets which will be used for tests naming. Recommended value to be " vs " including the spaces before and after the "vs" letters.
• Category 1 ⇛ In most cases, the value should be Item and it is used to determine the search condition for the search set. In some cases where RVT files are dragged into Navisworks to generate the NWC, you might need to use the value Document instead.
• Property 1 ⇛ In most cases, the value should be Source File and it is used to determine the search condition for the search set. In some cases where RVT files are dragged into Navisworks to generate the NWC, you might need to use the value PathName instead.
• Category 2 ⇛ In most cases, recommended value to be Element which is the tab contaning the category value on the second column of the CSV. This needs to be confirmed from the elements property.
• Property 2 ⇛ In most cases, recommended value to be Category which is the category value under Category 2 tab.
• Main Categories to combine ⇛ This feature allows you to combine several categories into one single set. Each group of main and sub categories should be on a seperate line.
  
  • Example: to combing Stairs,Landings ,Runs & Supports into a single set called Staircase, the format shall be:
    Staircase(Stairs,Landings,Runs,Supports)
    Note that the value outside of the brackets can be of any value and doesn't neccessary be an actual category value. Only the values within the brackets will be considered in the search set settings. The value outside the brackets will define the set name.
• Sets to Ignore ⇛ Use this field to define all the categories that need to be ignored from the sets making and tests. This will save you from the hustle of having to clean the CSV file from unwanted categories everytime. The values must be comma seperated and are case sensitive.
  
  • Example of unwanted categories: Rooms,Grids,Levels,Reveals,<Room Separation>,<Space Separation>,Reference Planes,Materials
• ACC Compatible ⇛ Check this to make sets compatible with cloud models loaded directly from ACC.
• Organize Folders ⇛ Create folders for every discipline code, and have all related sets under them.

Export the tests settings to a matrix in an excel format. Each cell will include the test type and tolerance value. The excel can be further modified and loaded again to update the clash tests.

Examples:

• HC-25 means the clash type is Hard (Conservative) with a 25mm clearance.
• H-0 means the clash type is Hard with a 0mm clearance.

Abbreviations used:

• H ⇛ Hard
• HC ⇛ Hard (Conservative)
• C ⇛ Clearance
• D ⇛ Duplicates

Import➔Types

Export all tests priorities to a matrix format. The excel can be further modified and loaded again to update the clash tests.

Compatibility: Supported in Navisworks 2026 and later. Ensure the file is already saved as version 2026 or newer before opening it in Navisworks for the priority column to appear in Clash Detective window.

Abbreviations used:

• 0 ⇛ Not-Set
• 1 ⇛ High
• 2 ⇛ Medium
• 3 ⇛ Low

Import➔Priority

Tip: Use X when importing to delete tests.

Flip Side helps you quickly swap Selection A and Selection B in clash tests. This is useful when you want a consistent responsibility logic, reporting order, or grouping behavior across tests.

Common uses:

• Make the first selection always represent the discipline under review.
• Standardize how clashes are grouped by Selection A or Selection B.
• Align test naming conventions with the selection order (example: ARC vs STR).

How it works:

• Select one or more clash tests.
• Run Flip Side to swap the search/selection sets between A and B.
• Optionally update the test name to match the new order (sample option).

Notes:

• If the test uses saved selection sets, the references are swapped, not duplicated.
• If a test has same set on both sides, no visible change occurs.
• Existing clash results will not reset or get affected.

This tool enables you to export all clashes marked as approved or reviewed, which can then be imported into another file. This ensures that the most up-to-date clash statuses across all disciplines are captured and reflected in the next clash report update.

Recommended Workflow: After sharing the NWD model containing the clashes with the team, have them mark clashes as "approved" if no action is required on the model, or as "reviewed" if action is needed from another discipline. Each team should return their NWD file with updated clash statuses. Use this tool to export all approved and reviewed clashes from the NWD models.

Key Features:

• Only clashes marked as approved or reviewed will be exported.
• Regardless of the number of clash tests containing approved clashes, all approved clashes will be exported to a single XML file.
• For approved clashes, the status will be exported along with the "Approved By" and "Approved Date."
• For reviewed clashes, the status will be exported along with the "Assigned To" value.
• Clash statuses will be updated even if clashes were grouped or ungrouped in the NWD, meaning the NWF and NWD do not need to have matching groups.
• Unified Time Zone: Navisworks stores all date and time values in UTC but displays them based on each user's local time zone and regional settings. Import and export use the UTC time zone. Example: An approved clash at 6:00 PM in Sydney, Australia will show as 12:00 PM in Dubai, UAE.
• Ability to export comments added to approved and reviewed results.
• You can include GUIDs of clashing elements in the export, which allows you to import by GUID into models that are not aligned with the clash test methodology or counts.

Export Options:

• Export approved clashes for all tests containing a specific keyword.
• Export all approved clashes in the file.
• Export only those approved after a specific date (default is the last run of the clash tests).
• Checkbox to include reviewed clashes.
• Checkbox to export comments.
• Checkbox to include GUIDs of clashing elements.

Use this tool to import the XML file generated using Export Approved. It will import all approved and reviewed clashes along with their related comments.

Recommended Workflow: After exporting all approved clashes from the NWDs, open the NWF and import the approved clashes before updating the status of the clash tests.

Key Features:

• For approved clashes, the import will update the Approved By value, Approval Date, and the Approved status.
• For reviewed clashes, the import will update the Assigned To value and the Reviewed status.
• Import across models originating from different sources by using the Element GUID option.

Exports clash results in an Excel matrix format. The displayed values represent the total number of Active and New clashes. Approved and Reviewed clashes are excluded.

Key Features:

• Automatically detects the discipline code and separator (for example: "vs") and builds the matrix accordingly.
• Supports two matrix layouts: Top Right or Bottom Left.
• Groups headers by discipline code and applies a unique background color for each discipline.
• For Navisworks 2026 and later, cells can be color-coded based on the clash test Priority value.

Exports a clash results summary in CSV table format. The report includes the total number of clashes, as well as counts for Active, New, Reviewed, Approved, Resolved, and Total Active (New + Active).

Export detailed result of selected clash tests to a specific folder, each test as a seperate excel file. The export will include properties of the clashing elemente such as family name, type, material..etc
Note: only tests containing clash results will be exported.

Grouping clashes helps the team resolve issues more efficiently. With multiple grouping options available, the team can focus on clashes based on location, element type, or areas with the highest concentration of clashes. This tool allows you to quickly group clashes across multiple tests at once.

Key Features:

• Prefix clash count ⇛ When enabled, a prefix showing the number of clashes in each group will be added to the group name. This allows the team to sort groups by name and prioritize those with the highest number of clashes.
  Sample group name: 7 clashes: ARC_Base Cabinet - Double Sink Door.
• Keep existing groups ⇛ Uncheck this option to remove all existing groups before applying the new grouping command.

Grouping Options:

• Selection A ⇛ Clashes that share the same component in Selection A will be grouped together.
• Selection B ⇛ Clashes that share the same component in Selection B will be grouped together.
• Status ⇛ Clashes will be grouped based on their status (Active | New | Reviewed | Approved | Resolved).
• Grid Title ⇛ Clashes will be grouped based on their nearest grid.
  The active grid system will be used (can be changed from View ↣ Grids & Levels).
• Level Name ⇛ Clashes will be grouped based on their nearest level.
• Assigned To ⇛ Clashes will be grouped based on the Assigned To value.
• Approved By ⇛ Clashes will be grouped based on the Approved By value.

Smart Results offers fast and flexible tools to enhance clash result readability and improve reporting quality. It allows you to batch rename clash results from default names (for example, "Clash1") to clear and meaningful descriptions.

Typical Capabilities:

• Rename results based on clashing element properties using a custom-defined naming pattern.
• Rename individual results and group names, including the main clashing element ID.
• Apply Find/Replace to the final names for additional customization.
• Save settings for future use, and export or import naming profiles to improve consistency and collaboration across teams.

Quickly mark clash results as Approved or Reviewed based on clashing element properties and clash location. The tool allows you to define multiple criteria to control the update logic.

Key Features:

• Select custom properties to match against defined values (example: Diameter greater than 150 mm).
• Update results based on clash location (example: Pipes clashing above 2.5 meters from the base of the wall).
• Define the Approved By value for clashes marked as Approved.
• Define the Assigned To value for clashes marked as Reviewed.
• Add a Comment to each updated result.
• Generate a detailed summary report of all applied checks and extracted values for every result within the test. One Excel file is created per selected test.

Profiles:

• Save commonly used settings as profiles per project or client.
• Export and import profiles to run on selected tests and maintain consistent BIM coordination.

Clash View enables users to generate viewpoints for all results within selected clash tests. Results are automatically organized into subfolders based on their statuses.

Key Features:

• Define colors for each of the clashing elements.
• Set colors for items similar to each clashing element.
• Adjust transparency and color for surrounding elements.
• Add descriptive markups extracted from the properties of the clashing elements.

Tip: Use Clash View together with Annotate Pro for faster and more effective reporting.

This tool allows you to update clash result statuses simply by moving their corresponding viewpoints into the appropriate status folder (New, Active, Approved, or Reviewed).

Export Viewpoints enables you to export viewpoint images for reporting and sharing with the coordination team. The exported images include all added markups and are organized into a main folder named after the clash test, with subfolders arranged by result status.

A dock pane that allows you to quickly select elements based on their Revit Element ID value.


Key Features:

• Multiple elements selection by having comma separated element IDs.
• Hide others allows you to isolate the selected elements.
• Selection Box creates a section box around the selected elements.

This tool allows you to quickly access detailed information about elements simply by hovering over them. With a single click, you can convert the displayed information into a markup.

Key Features:

• Spot Coordinates: Retrieve the X, Y, and Z values for any element.
• Custom Properties: Define any required property and extract its value from the selected elements.
• Common Properties: Select frequently used properties such as Element ID, Source Model, Category, Family & Type, Mark, System Classification, and Pipe Diameter.
• Viewpoints: Automatically generate viewpoints as you place your markups.
• Set Reference Point: Define a custom reference point and display coordinates of other elements relative to it.
• Copy to Clipboard: Copy the displayed properties to the clipboard, useful when preparing clash reports.

Quickly rename clash tests, sets, and viewpoints based on defined criteria. The tool allows you to find and replace text, add a prefix or suffix, trim names, or apply automatic numbering.

Key Features:

• Find and Replace: Search for specific text and replace it with a new value.
• Add Prefix/Suffix: Add custom text before or after the name.
• Numbering: Quickly add sequential numbers as a prefix (example: 0001, 0002, 0003, etc.).
• Trim Names: Remove text before or until a specific character, or trim a defined number of characters.
• Import Names: Rename tests or sets by importing an Excel file containing two columns: current names and corresponding new names.

Use this tool to delete clash tests, selection sets, and viewpoints based on defined criteria. It helps streamline the model by removing unnecessary items, allowing the team to focus only on relevant data.

Purge Options:

• Clash Tests:
  • Delete all tests.
  • Delete tests where the sum of selected statuses (Active, New, Approved, Reviewed) equals zero.
  • Delete tests with zero clashes.
  • Delete tests containing specific search words (comma-separated).
  • Delete tests NOT containing specific search words (comma-separated).


• Selection Sets:
  • Delete all sets.
  • Delete sets containing specific search words.
  • Delete sets NOT containing specific search words.
  • Delete empty folders.


• Viewpoints:
  • Delete all viewpoints.
  • Delete viewpoints containing specific search words.
  • Delete viewpoints NOT containing specific search words.
  • Delete viewpoints inside folders containing specific search words.
  • Delete viewpoints NOT inside folders containing specific search words.
  • Delete empty folders.

Search Words: Enter comma-separated keywords (example: HVC, ELE, PLU, DRN).

This tool allows you to apply configuration changes to one or multiple clash tests at once. It is especially useful when updates are required after the initial clash test setup.

How It Works: Select tests from the Available Tests list and move them to Tests to Modify. Use the search box to filter tests by keywords. Leave the search field empty to target all clash tests.

Update Options:

• Update Tolerance (mm): Modify the tolerance value for selected tests.
• Update Clash Type: Change the test type (Hard | Hard Conservative | Clearance | Duplicates).
• Update Composite Object: Enable or disable Composite Object Clashing.
• Update Test Priority: Assign or override test priority values (requires Navisworks 2026 or later).

Note: You can optionally override existing priority values when updating test priorities.