The bridge between your model and ClashWise.

Every authoring tool Navisworks supports stores model data differently. Property Mapping is the one-time bridge that tells ClashWise where Name, Element ID, Category, Layer/Level, Type, and Discipline live in your model's properties. Six fields, six dropdowns, about ten minutes per source-file pattern. After that, every clash batch, every matrix rule, every sync, works automatically.

The six required fields

Name, Element ID, Category, Layer/Level, Type, and Discipline. Each one unlocks a specific part of the downstream pipeline — Name feeds clash titles, Element ID preserves traceability, Category drives Clash Matrix rule matching, Layer/Level adds story context, Type adds specificity, and Discipline drives discipline-aware rules and AI routing.

Works with every authoring tool Navisworks supports

Revit, Civil 3D, AutoCAD, Tekla Structures, ArchiCAD, MicroStation, OpenBuildings, Inventor, Plant 3D, SketchUp, Rhino, IFC, DGN, DWG, NWC — and every other format Navisworks loads. Each authoring tool stores Name, Category, and Discipline in a different property group with different names. Property Mapping is the bridge.

Auto-saved per document, apply to other models in one click

The mapping is stored per Navisworks document. The Apply to Other Models dialog lets you broadcast the active mapping to any subset of remaining models in the federation — each gets its own saved config, so per-model tweaks still work.

Preview against 100 sample items before you commit

Click Preview Mappings to scan up to 100 sample items from the model. The grid shows exactly what ClashWise will read for each field, so you can verify the mapping pulls the right values before running a batch.

Frequently asked questions

How long does Property Mapping take?

About 10 minutes the first time you configure a source-file pattern. Subsequent models with the same authoring tool reuse the saved configuration in seconds — via Apply to Other Models or by-document auto-load.

Does it work with Civil 3D, Tekla, or OpenBuildings?

Yes — Property Mapping is format-agnostic by design. If Navisworks can load the file, ClashWise can map its properties. Every authoring tool stores Name, Category, and Discipline in a different place; that is exactly the problem Property Mapping solves.

What happens if I skip a field?

You cannot — all six fields are required. The configurator's Start button stays disabled until every model in the document has all six mapped. Red asterisks turn green checks as each row completes.

Does my mapping sync to teammates?

Not today. Property Mapping is stored per Navisworks document on the local machine. If multiple coordinators open the same model, each runs Property Mapping once. Cloud-synced mappings are on the roadmap for the Clash Management platform.

Start free trial Download plug-in See pricing