VitruAI + Navisworks
The VitruAI + Navisworks integration reads federated NWD/NWF model state, existing clash test results, selection sets, and saved viewpoints through the Navisworks .NET API for Navisworks Manage 2023–2026 on Windows. It powers the Clash Review Agent prioritisation pass so thousands of raw clashes collapse into the three issues the team resolves today, available now as a Labs engagement under MSA + Appendix.
- Reads federated NWD/NWF state — clash test results, selection sets, view-states, and saved viewpoints from Navisworks Manage 2023–2026.
- Drives Clash Review Agent prioritisation so coordinators focus on the few clashes that drive cost-of-late-discovery and suppress noise.
- Available now as a Labs engagement; productised VitruAI for Navisworks release sits on the Roadmap and scopes against each firm’s coordination workflow.
Install, requirements, and what runs through the integration.
-
Navisworks Manage 2023, 2024, 2025, 2026 on Windows
The VitruAI plug-in installs into Navisworks Manage 2023–2026 on Windows and uses the public .NET API to read federated NWD and NWF files. Navisworks Simulate and Freedom are not supported because they do not expose the plug-in API needed for read/write access. Typical deployments pair this desktop integration with VitruAI + Revit so coordination issues can be traced back to authoring models for rapid fix cycles.
-
Clash test results read, not rewritten
The integration reads existing Navisworks clash tests, clash groups, and rule-based filters; it does not overwrite or regenerate the team’s clash testing setup. Coordinators keep their existing test naming, tolerances, and batch structure for MEP, structural, and architectural passes, including setups used in MEP clash review. VitruAI then layers prioritisation on top, so firms keep their current federation discipline while gaining ranked queues.
-
Saved-viewpoint output inside Navisworks
Prioritised clashes are written back as labelled saved-viewpoint sets in the active NWF, grouped by trade or system so coordinators can step through them in Navisworks itself. Each viewpoint carries metadata tags for priority, discipline, and likely root model, which ties cleanly into downstream structural–architectural coordination workflows. Teams can export these prioritised sets to NWD for issue review meetings or share them with external partners who do not run the plug-in.
-
Available now as a Labs engagement
VitruAI for Navisworks is available as a Labs engagement under MSA + Appendix, with productised release on the Roadmap once the first cohort stabilises the feature set. Labs scopes the integration against each firm’s federation rules, naming standards, and priority weighting across MEP, structural, and architectural models. Many teams also connect the Navisworks Labs work with VitruAI + BIM 360 / ACC to keep desktop clash review aligned with cloud-hosted coordination spaces.
-
Clash Review Agent prioritisation across federated models
The integration feeds the Clash Review Agent with full clash test outputs, selection sets, and view states so it can rank issues by cost-of-late-discovery rather than raw count. It flags patterns such as repeated penetrations through the same beam family or stacked pipe clashes along a corridor, which matter more than isolated hits. This prioritised list then directs fixes in authoring tools like VitruAI + Revit, closing the loop between federation and model editing.
Navisworks integration FAQs
-
Does this replace our Navisworks clash testing setup?
No, the integration reads your existing Navisworks clash tests and groups; it does not replace them or change tolerances. You keep your current clash test templates for architectural, structural, and MEP passes, including any setups tuned for MEP clash review. VitruAI adds a prioritisation layer on top so coordinators work through the highest-impact clashes first without rebuilding their test library.
-
Does it work with cloud-hosted Navisworks (BIM 360 / ACC)?
Yes, it works with models coordinated through BIM 360 / ACC as long as the federated NWD or NWF is opened in Navisworks Manage on Windows. The integration reads the local federated file, including models aggregated from cloud-hosted Revit or IFC sources, and then writes prioritised saved viewpoints back to that session. For teams who coordinate primarily in the cloud, VitruAI + BIM 360 / ACC provides the parallel path for issue tracking and model review in the browser.
-
Can we prioritise by our firm’s own rules?
Yes, the Labs engagement scopes priority-weighting rules against your firm’s federation conventions, clash naming, and trade breakdowns. You can weight clashes by system (e.g., primary duct vs. branch), location (e.g., risers vs. open office), or phase, and adjust those weightings as your standards evolve. These rules align with how you already structure Navisworks tests and with how you route fixes back into tools such as VitruAI + Revit.
-
When is the productised release?
VitruAI for Navisworks is available now as a Labs engagement under MSA + Appendix, with productised release on the Roadmap. Ship-by dates depend on the first productisation cohort and the volume of feedback from early Navisworks Manage 2023–2026 deployments. Firms that join the Labs cohort help set defaults for prioritisation patterns, including those used in structural–architectural coordination and cross-tool workflows that touch VitruAI + BIM 360 / ACC.