Autodesk’s BIM Duo: Why Revit and Navisworks Sail Separate Seas

Autodesk’s Revit and Navisworks emerged from distinct origins to address different phases of the building lifecycle. Revit, developed by Revit Technology Corporation (acquired in 2002), revolutionized parametric BIM design, enabling architects and engineers to create intelligent 3D models with bidirectional data flow. Navisworks, acquired in 2007, began as a clash detection and model aggregation tool, ideal for construction coordination. While both are BIM pillars, their separation reflects Autodesk’s strategy to cater to specialized workflows rather than forcing a monolithic solution.

Divergent Roles, Complementary Strengths

Revit excels in design and documentation, offering granular control over architectural, structural, and MEP systems. Its parametric families, schedules, and worksharing tools make it the go-to for detailed model creation. Navisworks, meanwhile, focuses on project review and coordination, aggregating models from diverse sources (Revit, AutoCAD, IFC) for clash detection, 4D scheduling, and stakeholder visualization.

Autodesk avoids merging them to prevent software bloat. Merging would dilute their specialized value: Revit’s precision for designers clashes with Navisworks’ lightweight agility for coordinators. Instead, they interoperate via IFC and Autodesk’s ecosystem. Revit exports IFC files (though with occasional data loss), while Navisworks uses plugins like Codemill IFC Exporter to import/export IFC, despite challenges with file size and geometry fidelity.

Why No Native Interoperability?

Autodesk prioritizes vendor lock-in over seamless interoperability. While Revit and Navisworks integrate via Autodesk formats (RVT, NWD), robust IFC support is often outsourced to third-party tools. This strategy encourages reliance on Autodesk’s ecosystem but frustrates users needing open standards.

Evolution: Divergence Over Convergence

• Revit expands into cloud collaboration (BIM 360) and advanced MEP detailing.
• Navisworks enhances clash resolution automation and infrastructure-focused workflows.
  Their paths diverge, reflecting Autodesk’s segmented approach to BIM stages.

Choosing the Right Tool

• Use Revit for:
  • Detailed design and documentation.
  • Parametric family creation (e.g., custom HVAC components).
  • Multi-disciplinary worksharing.
• Use Navisworks for:
  • Aggregating models from Revit, Civil 3D, and IFC sources.
  • Clash detection in mixed-software megaprojects (e.g., stadiums).
  • 4D construction sequencing linked to Primavera schedules.

Practical Example: A hospital project uses Revit for room layouts and MEP routing, then Navisworks to coordinate with structural steel (Tekla) and facade (Rhino) models. Clash Detective resolves pipe-beam conflicts before construction.

Adoption Strategy

Companies become candidates when:

• Projects involve multi-disciplinary teams.
• Regulatory compliance mandates clash-free models.
• Stakeholders demand 4D/5D visualization.

While some firms standardize on Revit for design-to-construction, others blend Revit with Navisworks for large-scale coordination. Autodesk’s duo remains entrenched—not by elegance, but by entrenched workflows and the absence of equally robust alternatives. For now, the BIM world sails on two ships.