Overview of Revit and Navisworks Integration

The seamless integration of Autodesk Revit with Autodesk Navisworks has become a critical workflow in modern building information modeling (BIM) environments. As project complexity grows, so does the need to identify and resolve interferences between structural, mechanical, electrical, and plumbing systems before construction begins. This integration empowers architects, engineers, and construction managers to move beyond static clash detection into dynamic, multi-disciplinary coordination. By combining Revit's robust modeling capabilities with Navisworks' powerful aggregation and analysis tools, teams can dramatically reduce costly rework, shorten project timelines, and improve overall project quality. This article provides an authoritative, comprehensive guide to integrating Revit with Navisworks for enhanced clash detection, covering workflows, best practices, advanced strategies, and common pitfalls to avoid.

Understanding Revit and Navisworks

Revit: The Authoring Hub for BIM

Revit is a feature-rich BIM platform designed for architectural design, structural engineering, and MEP (mechanical, electrical, plumbing) systems. Unlike traditional CAD software, Revit uses parametric objects—walls, ducts, pipes, beams—that contain rich metadata and behave intelligently. Changes made in one view automatically propagate throughout the model, ensuring consistency across drawings, schedules, and 3D visualizations. For clash detection, Revit itself offers basic interference checking tools (e.g., the "Interference Check" function), but these are limited to two selected categories or linked models. Large, multi-disciplinary projects often require a more powerful, centralized review environment, which Navisworks provides.

Navisworks is a project review software that aggregates models from multiple authoring tools—Revit, AutoCAD, Civil 3D, SolidWorks, and more—into a single federated model. It offers advanced features for visualization, simulation, quantification, and, most critically, clash detection. Navisworks can run batch tests between hundreds of selection sets, produce detailed clash reports with screenshots and comments, and support iterative coordination workflows. Its native file format, NWC (Navisworks Cache) or NWD (Navisworks Document), compresses and optimizes large models for smooth navigation. The software also allows real-time selection, measurement, and annotation without altering the source files.

Why Integration Matters: The Benefits in Practice

Combining Revit with Navisworks yields tangible advantages that directly impact project success. Here are the key benefits, expanded with real-world context:

  • Enhanced clash detection accuracy: Revit models contain detailed geometry and assigned systems (e.g., supply air duct, hot water pipe). Navisworks can run tests between specific disciplines or element types, identifying soft clashes (insufficient clearance), hard clashes (physical intersection), and even time-based clashes (work sequence conflicts). For example, a pipe running through a structural beam is instantly flagged.
  • Reduced on-site conflicts and rework: According to industry studies, undetected clashes can account for 5–10% of total construction costs. By catching interferences early in design, teams avoid expensive field modifications. A mechanical contractor, for instance, can pre-fabricate ductwork knowing that clashes have been resolved in the model.
  • Improved cross-disciplinary collaboration: Navisworks serves as a neutral platform where architects, structural engineers, and MEP designers can review the same federated model. Meeting notes and clash statuses are tracked within the software, fostering transparent communication. Team members can mark clashes as "Approved," "Resolved," or "Assigned" without needing access to each other's authoring files.
  • Streamlined workflows and time savings: Instead of manually overlaying 2D drawings or running isolated interference checks in separate tools, teams can perform comprehensive clash detection in minutes. Automated reports can be generated weekly, before each coordination meeting, reducing the need for lengthy manual inspections.
  • Better decision-making with quantification: Navisworks can extract quantities from the aggregated model—such as lengths of piping or numbers of duct fittings—enabling cost impact analysis for design alternatives. This supports value engineering decisions such as routing a pipe differently to avoid a costly beam penetration.

Prerequisites and Preparation

Before diving into the integration workflow, ensure the following prerequisites are met:

  • Software versions: Use compatible releases of Revit and Navisworks (e.g., Revit 2023 with Navisworks 2023). Autodesk typically maintains backward compatibility, but using the same year avoids unexpected geometry errors.
  • Model hygiene: Clean and audit your Revit models. Remove purgeable elements, resolve warnings, and ensure that worksets and phases are correctly set. Use the "Review Warnings" tool in Revit to fix non-intersecting geometry that could cause sloppy exports.
  • Coordinate system alignment: All linked models must share a common coordinate system. Use Shared Coordinates in Revit (Manage tab → Coordinates → Acquire Coordinates or Publish Coordinates). If models are misaligned, Navisworks will display them floating apart or overlapping incorrectly.
  • Naming conventions: Agree on consistent naming patterns for model files, levels, grids, and element types. For example, structural grids should be named "Grid A-1", "Grid A-2" across all disciplines. This makes it easier to filter and query clashes in Navisworks.
  • Worksets and linked files: Decide which worksets to export. Disabling unnecessary worksets (e.g., furniture, landscaping) can reduce file size and improve performance. Keep linked models (e.g., structural link in an architectural file) as they are; Navisworks can handle nested links.

Step-by-Step Integration Workflow

The following expanded workflow covers the entire process from Revit model preparation through clash resolution tracking.

Step 1: Optimize and Clean the Revit Model

Begin by auditing the Revit model for any issues that might cause problems downstream. Run the "Check Interferences" tool in Revit (Collaborate tab → Coordinate panel → Interference Check) to catch obvious internal clashes first. Remove duplicate geometry, rehost misplaced elements, and ensure that all pipes, ducts, and conduits are properly connected to their systems. Rationalize parameters like "System Classification" (e.g., "Supply Air", "Return Air") because Navisworks can read these properties and use them for grouping clashes. If your project uses worksharing, synchronize with central and relinquish all owned worksets before exporting.

Step 2: Export from Revit to NWC

Use the "Export" menu within Revit: File → Export → NWC (Navisworks Cache File). The recommended format for ongoing coordination is NWC because it updates quickly when the source file changes. Avoid exporting to NWD from Revit (NWD is better for publishing snapshots from Navisworks). Click "Modify Export Setup" to control geometry conversion and property mapping.

Key export settings to verify:

  • Convert element parameters: Ensure that "Project Standard Parameters" and "Shared Parameters" are selected. This passes BIM data like "Fire Rating", "Service", or "Manufacturer" into Navisworks.
  • Export room geometry: If you need to check clearances, include rooms and spaces. Without this, clash tests for "clearance" might miss interferences with non-physical volumes.
  • Split by worksets: For large models, enable this option. It allows Navisworks to treat each workset as a layered group, making it easier to filter clashes by discipline or area.
  • Coordination model handling: If you use Revit Coordination Models (from Revit Cloud Worksharing), decide whether to export them as links or embedded geometry. Embedded is more reliable for clash detection.

After exporting, you may choose to save the NWC file in a project-accessible network location or upload it to a cloud collaboration platform (e.g., BIM 360 Design) for remote teams.

Step 3: Aggregate Models in Navisworks

Open Navisworks Manage or Simulate. Create a new NWF (Navisworks File) that references the exported NWC files. The NWF file is lightweight and stores pointers to the sources, enabling easy updates. Use the "Append" command (Home tab → Append) to load each discipline model. First, append the architectural model (which typically contains the base building geometry and grids), then the structural, then MEP, then other specialties like fire protection or IT.

After appending, verify alignment by zooming to a known grid intersection. If models are misaligned, use the "Transform" tool (Item Tools tab → Transform) to apply translation or rotation offsets. For persistent coordinate issues, return to Revit and re-establish shared coordinates.

Step 4: Define Clash Tests

Navigate to the "Clash Detective" tool (Home tab → Project Browser → Clash Detective). Create a new test. In the "Selection A" and "Selection B" dropdowns, you can choose from standard selection sets (e.g., "MEP Room Design", "Architectural Rooms") or define custom sets using the "Find Items" tool. For a typical MEP vs. structural clash test:

  • Selection A: Use "Find Items" → search for category "Structural Framing" or "Structural Columns".
  • Selection B: Search for category "Ducts" or "Pipes".
  • Tolerance: Set to 0.05 feet (15 mm) for hard clashes; a positive value for soft clashes (e.g., 0.1 feet for clearance).
  • Link: Choose "Hard" or "Hard (Soft Clearance)".

Run the test. Navisworks will enumerate all interferences, displaying them in a list with clash IDs, distances, and a visual context. Review results by clicking each clash item—the model will zoom to the interference point. Use the "Review" tab to assign statuses (New, Approved, Resolved, etc.) and add comments for the responsible team member.

Step 5: Collaborate and Iterate

Export clash reports as HTML or XML to share with the team. For ongoing coordination, adopt a regular cadence—weekly clash runs after each model update. Use Navisworks' "Clash Tracking" integration with BIM 360 or Autodesk Construction Cloud to synchronize statuses across the project. When a clash is resolved in the source model (e.g., an architect moves a column), re-export the NWC and refresh the NWF in Navisworks (Home tab → Refresh). The clash list will update; previously resolved clashes that reappear indicate a regression that needs attention.

Advanced Clash Detection Strategies

Once the basic integration is in place, teams can employ advanced techniques to handle complex scenarios:

  • Multi-level clash tests: Run a hierarchical series of tests. First test architectural vs. structural for gross interferences, then MEP vs. structure for detailed duct/pipe clashes, and finally MEP vs. MEP for conduit/duct conflicts. Each test can have a different tolerance.
  • Time-based clash detection (4D): Link the model to a construction schedule in Navisworks Timeliner. You can then run clash tests limited to elements that are installed concurrently. This prevents false positives where two elements are shown in the same location but installed at different times.
  • Clearance and access clashes: Beyond physical intersection, test for insufficient clearances around equipment (e.g., 3 feet in front of an electrical panel). Use soft clash tolerances or create geometric proxy objects in Revit representing clearance zones.
  • Rule-based clash grouping: Use the "Group Clashes" feature to organize results by system type, floor level, or priority. For instance, group all clashes that involve fire-suppression piping into a dedicated "Fire Protection Review" set.
  • Automation with scripting: Navisworks .NET API allows you to write C# or Python scripts (using Dynamo or Python in Navisworks via third-party plugins) to batch export clash reports or run tests on a schedule.

Best Practices for Long-Term Success

To maintain an effective integration throughout the project lifecycle, adhere to these best practices:

  • Establish a BIM Coordination Plan: Document the clash detection strategy in a formal plan—who runs tests, what tolerances to use, frequency of reports, and escalation procedures. This plan should be approved by all stakeholders early in design.
  • Standardize on file naming and versions: Avoid ambiguity by including discipline, model version, and date in the filename (e.g., "ARC-Model-R23_2025-01-15.nwc"). This prevents accidental rollback.
  • Perform incremental exports: Do not export the entire building at once if the project is massive. Instead, export by wing, floor, or trade. Use Navisworks' "Append" to combine them. This speeds up refresh times.
  • Verify geometry on import: Occasionally check that elements like structural beams or pipe fittings appear correctly. Some Revit families may not export fully—use the "Navisworks Geometry Viewer" to inspect complex shapes.
  • Train all team members: Engineers and designers should understand basic Navisworks navigation (Viewpoint, Section view, Measure). They can then review clashes assigned to them without needing full Navisworks licenses (Navisworks Freedom free viewer reads NWD files).
  • Track clash resolution metrics: Graph the number of open clashes over time. If unresolved clashes are increasing, it may indicate a design freeze issue or lack of enforcement. Use this data in project meetings to guide decisions.

Common Pitfalls and Troubleshooting

Even experienced teams encounter issues. Here are frequent problems and their solutions:

IssueCauseFix
Models do not align in NavisworksIncorrect shared coordinates or insertion pointRe-acquire coordinates in Revit; use "Move" tool in Navisworks as temporary fix
Clash detection is too slowOverly large models or too many elements in testNarrow selection sets (limit to specific levels or systems); use LOD 200 geometry for early stages
Missing elements in exportFiltered out by worksets or visibility settingsCheck export setup "Include All Worksets" and ensure elements are visible in Revit view
Clash results false positivesDuplicate geometry from linked modelsUse "Switchback" to identify source; merge or delete duplicate elements in Revit
NWC file fails to updateNWC cached by NavisworksDelete NWC cache file (same folder as NWC) and re-export

External Resources and Further Reading

To deepen your understanding, explore the following authoritative sources:

Conclusion

Integrating Revit with Navisworks for enhanced clash detection is not merely a technical exercise—it is a foundational process that drives construction efficiency, reduces risk, and fosters interdisciplinary collaboration. By following the comprehensive workflow outlined in this guide—starting with model preparation, continuing through precise export and aggregation, and concluding with systematic clash review and tracking—teams can achieve a fully coordinated digital project. Advanced strategies such as time-based clash detection and automation further refine the process. Ultimately, the integration moves the project from reactive problem-solving to proactive prediction, saving time and money while delivering higher quality outcomes. As BIM technology evolves, the synergy between Revit and Navisworks will only grow stronger, making this integration an essential competency for every project participant.