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:

• Data Export & Import:

• Export Approved: Extracts only approved clash tests for reporting or further processing
• Import Approved: Updates clash statuses based on an external approved list.
• Detailed Tests Export: Generates a CSV with in-depth clash test results.
• Table Export: Summarizes clash status counts for easy reporting in a table format.
• Export Matrix: Creates a structured clash types matrix for analysis.
• Import Matrix: Updates clash types from an external matrix file.
• Excel Matrix:: Generate an excel clash matrix with counts of remaning active clashes.

• Clash Test & Set Management:

• Tests Builder: Quickly generates clash tests and sets from element categories.
• Export Categories: Extracts categories from all loaded NWC files with their source file to facilitate test creation.
• Renamer: Batch renames clash tests and sets based on predefined rules.
• Purge: Deletes clash tests matching specific criteria.
• Group Clashes: Organizes clash results into groups based on custom rules.
• Bulk Action: Applies batch modifications to clash tests efficiently.

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 with approved or reviewed statuses 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.

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.

Use this tool to import the filed generated using Export Approved. It will import all approved clashes, and reviewed if that option was checekd during the export.

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

Key Features:

• For the approved clashes, the import will update the Approved By value, Approval Date, and of course the Approved status.
• For the reviewed clashes, the import will update the Assigned To value and the Reviewed status.

Export the clash results in an Excel Matrix format. The showed number is the sum of active and new clashes. All approved and reviewed clashes will be excluded.

Key Features:

• Automaticcaly detect the discpline code and the seperator (example: vs) and build the matrix accordingly.
• Fill only the top part of the Matrix, thus elminitating duplicates.
• Group the headers by discpline code, and apply unique color background fill for each discipline.

Export the clash results summary in a CSV table format. This will show total number of clashes, 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.

Export all cateogies contained in the loaded NWC models to a csv. The export wil contain two columns, the source model file and the category value.
Note: The export might take couple of minutes to generates since it scans all elements in the loaded models to generate the file.
Key Features:

• Ability to gather all existing categories, thus determine what shouldn't 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.

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

Use this tool for importing back the excel matrix contaning the test types and clearances to update the test accordingly. Make sure that the excel file follows the same defined abbreviation.

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 Categories tool). It streamlines clash detection workflows and enhances productivity for BIM professionals.

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:

• 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.

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
    

Quickly rename clash tests and sets based on a defined ctriteria. The tool allows you to find a value and replace it with another, add a prefix or add a suffix to the name.
The value can be applied to the names of tests and/or sets.

Use this tool to delete clash tests matching a specific criteria, thus allowing the team to focus on the clashes relevant to their department by reducing the clash tests scroll size.

Purge options:

• Delete Tests with Zero Clashes ⇛ Use this option will delete all the tests that contains no results (zero clashes).
• Delete Tests Containing Words ⇛ Delete all tests containing specific words (comma seperated).
• Delete Tests Not Containing Words ⇛ Delete all tests not containing specific words (comma seperated).
• Example search words: HVC-,ELE-,PLU-,DRN-
  

With this tool, you can apply clash test settings changes to all or many clash test based on selected criteria. This is useful if you missed some settings in the intial clash tests preperation and an update is needed.
How it works: Apply search words (comma seperated) so all tests matching this condition will have the update applied.
Keep this value empty to apply the update to all clash tests.

Update Options:

• Update tolerance value.
• Change clash test type (Hard | Hard Conservative | Clearance | Duplicates).
• Update the checkbox for Composite Object Clashing.

Grouping clashes help the team resolve clashes quicker. With several option for grouping, the team can focus on solving clashes based on the location, element type, or areas with most clashes. This tools allows you to quickly group clashes for multiple tests at once.

Key Features:

• Prefix clash count ⇛ Checking this option will add a prefix containing the clash count included in each group. This will allow the team to sort the results by name and thus can focus on the groups containing the highest number of clashes.
  Sample group name: 7 clashes: ARC_Base Cabinet-double Sink Door.
• Keep existing groups ⇛ Uncheck this box to delete all existing groups before applying the group command.

Grouping options:

• Selection A ⇛ The test results of clashes having same component for Selection A will be grouped together.
• Selection B ⇛ The test results of clashes having same component for 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.