■ MEP BIM INSIGHTS — TOOLS & SOFTWARE

Navisworks vs. BIM 360: Which Tool for MEP Clash Detection?

If you work in MEP BIM coordination, you use both Navisworks and BIM 360 (now Autodesk Construction Cloud, or ACC). They are not competing tools — they solve different problems at different points in the coordination workflow.

But teams that don’t understand the distinction end up running clash detection in the wrong tool, missing issues that the right tool would have caught, and spending time in coordination meetings re-establishing which platform is the source of truth.

This article explains what each tool does, where each one performs better, and how they work together in a functional MEP coordination workflow.

---

Navisworks Manage: The Coordination Engine

Navisworks Manage is a desktop application that aggregates model files from multiple disciplines into a single federated view. It is the primary tool for running clash detection, reviewing interference results, and producing clash reports.

What Navisworks does well

• Clash detection depth: Navisworks runs hard clash, clearance (soft clash), and duplicate detection with configurable tolerances. You can set clearance rules per system type — 6” maintenance clearance around fan coil units, 2” around ductwork — and run them simultaneously against the entire federated model.
• Clash grouping and filtering: Navisworks allows you to group clashes by discipline pair, by space, by level, or by element type. You can suppress known acceptable clashes and focus the report on unresolved issues. This level of control is not available in BIM 360’s clash detection.
• Saved clash sets: Every clash run is saved as a named set with a timestamp. You can compare clash counts between model updates to verify that issues are being resolved, not just hidden.
• Offline performance: Large federated models — 500MB+ NWD files — run faster in Navisworks than in any cloud-based viewer. For complex mechanical room coordination with dense geometry, Navisworks remains the faster tool.
• NWF files: The Navisworks File Set (.nwf) references the original model files without importing them. When discipline models are updated, reloading the NWF reflects all changes instantly without recreating the federated model.

What Navisworks does not do

• No cloud access — files must be shared manually or via a network location
• No multi-user simultaneous access to the same session
• Clash comments and status updates exist only in the local NWF file, not in a shared database
• No model version control — tracking which version of each discipline model was used requires manual file management

---

BIM 360 / ACC: The Collaboration Platform

BIM 360 (now Autodesk Construction Cloud) is a cloud platform for project document management, model coordination, and issue tracking. Its Model Coordination module runs automated clash detection against published model versions and tracks issue resolution across the project team.

What BIM 360 does well

• Team-wide issue tracking: When a clash is identified in BIM 360, it becomes an issue assigned to a responsible party with a due date and status. Every team member sees the same issue list. Resolution is tracked in a shared database, not in a local file on the BIM coordinator’s desktop.
• Model version management: Every time a discipline publishes a new model version to BIM 360, the platform runs clash detection automatically against the current model set and compares results to the previous version. New clashes are flagged; resolved clashes are closed.
• Access from anywhere: Architects, engineers, contractors, and owners can view the coordination model and issue log from a browser or mobile device without a Navisworks license.
• Audit trail: Every issue has a full history: who created it, when it was assigned, what comments were added, when it was resolved, and who verified the resolution. This is the documentation that owners and CMs increasingly require at project closeout.

What BIM 360 does not do as well

• Clash grouping rules are less granular than Navisworks — you cannot define clearance rules per system type with the same precision
• Large model performance in the browser viewer is slower than Navisworks for dense MEP coordination
• Clash detection runs automatically on publish schedule, not on-demand mid-session
• The coordination module requires a BIM 360 Coordinate subscription, not just the base Document Management tier

---

Side-by-Side Comparison

Capability	Navisworks Manage	BIM 360 / ACC
Hard clash detection	Yes — full control	Yes — automated
Clearance (soft clash)	Yes — per-system rules	Limited
Clash grouping & filtering	Advanced	Basic
Multi-user issue tracking	No	Yes
Model version control	Manual	Automated
Audit trail / history	No	Full
Offline use	Yes	No
Performance on large models	Better	Slower in browser
Access without license	No	Yes (viewer)

---

How They Work Together in Practice

On well-run MEP coordination projects, Navisworks and BIM 360 are used at different stages of the same workflow — not as alternatives to each other.

A typical weekly coordination cycle

• MEP team updates discipline models in Revit
• Internal clash check in Navisworks — resolve within-discipline issues
• Publish updated models to BIM 360
• BIM 360 runs automated clash detection, flags new issues
• Weekly coordination meeting: review BIM 360 issue list, assign resolutions
• Responsible parties update models; cycle repeats

Which Tool Should You Use for Your Project?

The honest answer is: both, if the project scale justifies it.

For smaller projects — under 50,000 sq ft, single discipline contractor, short schedule — Navisworks alone with manual file sharing is often sufficient. The overhead of setting up and managing a BIM 360 project is not justified for a 3-month MEP scope.

For larger projects — multi-discipline, multiple subcontractors, owner requiring issue log documentation — BIM 360 provides the collaboration infrastructure that Navisworks cannot. Navisworks still runs the detailed clash detection; BIM 360 tracks the resolutions.

How We Use Both at GEOMETRY-S

Our standard MEP coordination workflow uses Navisworks Manage for internal clash detection and report generation before model issue. For projects hosted on BIM 360 or ACC, we publish to the platform and participate in the team coordination workflow using the client’s CDE setup.

We deliver the Navisworks .nwf file with saved clash sets as a standard deliverable alongside the coordination model, so clients have a full record of the coordination process independent of the platform.