ClashWise
Name
The descriptive element name used in generated clash titles, labels and search.
Property Mapping
Give ClashWise the right model context.
Tell ClashWise where six useful fields live in your Navisworks models. Verify the values once for each source-file pattern, then reuse the mapping as you name, publish and coordinate clashes.
Allow about ten minutes for your first source-file pattern. Always check the preview before running a batch.
Choose which model properties ClashWise uses.
In Navisworks, open Update Clash Titles on the ClashWiseAI ribbon, then choose Property Mapping. Select a model file and choose a property group and property name for each field. Editable dropdowns also accept the exact names used in your model.
The preview shows the values ClashWise extracts from model elements. Use selected elements to check an unfamiliar source before you apply its mapping elsewhere.
Open the configuration guideExample source: mechanical model
- Name
- Element / NameSupply duct
- Element ID
- Element / Id458921
- Category
- Element / CategoryDucts
- Layer/Level
- Element / LevelLevel 02
- Type
- Element / Type600 × 300 mm
- Discipline
- Item / DisciplineMechanical
Six fields with a job to do.
These fields make titles readable, elements traceable and your project matrix useful. Verify the meaning of the extracted data as well as the property name.
Element ID
The identifier assigned by the source application, keeping the clash traceable to its original element.
Category
The classification group, such as Walls or Ducts. Use the same category vocabulary when defining your Clash Matrix rules.
Layer/Level
The storey or CAD layer that supplies location context for grouping, rules and clash titles.
Type
The specific element type, giving naming and analysis more detail than the category alone.
Discipline
The trade or domain used in matrix rules and the context for responsible-contact recommendations. Check that the extracted values match your project vocabulary.
From the first source to the federation.
Configuration is saved for the Navisworks document on the local machine. Apply it to other source models that use the same property pattern, then check any differences.
Select a model file
Choose a source in the open Navisworks document. A saved mapping is loaded when one exists for that source.
Map the six fields
Select or type each property group and property name. Treat automatic configuration as a starting point to verify.
Preview model elements
Check the extracted names, IDs, categories, levels, types and disciplines against elements you know in Navisworks.
Apply to other models
Use Apply to Other Models for compatible sources. Each model keeps its own configuration, so you can adjust exceptions and preview again.
Use the mapping where the work starts.
Coordination Setup maps the class, discipline and source properties used to build a matrix and managed tests. Search Sets can combine source-property conditions with computed grids and levels. Check the preview in each workflow before applying it.
In the browser, IFC inspection reads the attributes, property sets and quantities contained in an IFC source. It does not edit IFC data or replace the mapping used by the Navisworks plug-in.
Use the model inventory to build the matrix.
Coordination Setup lets you map class and discipline properties for each source before any clashes exist. Select the physical classes to include, review their discipline names and reuse the mapping when the federation changes.
Property Mapping questions.
Troubleshoot a mappingHow long does setup take?
Allow about ten minutes for the first source-file pattern. Reusing a verified mapping is quicker, but check sources that use different standards.
Do I need to map every new project?
Consistent source standards can reuse the same property pairs. Configuration is saved per Navisworks document; verify the first sources in a new document before processing clashes.
What if my property names are unusual?
Type the exact group and property names into the editable dropdowns. The property must exist in the source model; confirm it in the preview.
Can I leave a field unmapped?
The workflow requires all six fields for every source model before starting. Check the mapping validation for the model that still needs attention.
Does my mapping sync to teammates?
Mappings are stored locally for the Navisworks document. Each coordinator should configure and verify their own mapping; cloud synchronisation is not part of this workflow.
Why do Category and Discipline matter?
They connect model data to the vocabulary used in your project matrix. Check the extracted values before defining rules or reviewing recommendations.
Does this work beyond Revit?
Yes. Property Mapping works with the properties exposed by formats Navisworks loads, including Civil 3D, Tekla, OpenBuildings and IFC. The available fields depend on the source file.
What about different languages?
Choose property names as they appear in the source model, including localised names. Verify again when a language change alters those names. The plug-in interface is available in eleven languages.
Start with a model you know.
Install the plug-in, verify the extracted properties and see how useful context changes the next clash review.