Navisworks Clash Detection (from Revit)

🔗 Related Concepts

Deepen your understanding with these related topics:

Definition

Navisworks Manage hosts coordination by importing Revit (.rvt or .nwc), AutoCAD, IFC, and other discipline models into a single navigable aggregate. The Clash Detective runs tests pair-wise: 'Mechanical ducts vs. Structural beams' returns every clash with a 3D snapshot, a coordinate, and an assignable resolution status.

The Revit side exports an NWC (Navisworks Cache); Navisworks aggregates NWCs into an NWF (federated file) which produces an NWD (published snapshot).

Why it matters

Clash detection is the single biggest construction-cost-savings mechanism BIM delivers. Without it, beams and ducts collide on site rather than on screen.

Technical Deep Dive & Core Mechanics

Navisworks Clash Detection (from Revit) operates on a federated model—a composite of separately authored discipline models merged in a neutral viewing environment. The federation process transforms each source model's local coordinate system into a shared project coordinate system, using origin offsets and rotation angles defined in the project's coordination protocol. Mismatches in these transformation parameters cause apparent model misalignments that masquerade as genuine clashes.

Clash detection algorithms evaluate Navisworks Clash Detection (from Revit) by testing spatial overlap between bounding volumes (axis-aligned bounding boxes) as a first pass, then refining with exact geometric intersection tests for candidate pairs. The first-pass AABB test is computationally cheap (O(n log n) with spatial hashing), but the exact geometry test is expensive—particularly for curved elements like pipes, ducts, and structural members with complex profiles. Tolerance settings control whether near-misses are flagged, and grouping rules collapse related clashes (e.g., all clashes between the same two pipes) into single actionable items.

Step-by-Step Professional Implementation

Deploying Navisworks Clash Detection (from Revit) in a multi-discipline coordination workflow demands structured federation and issue tracking:

1. Prepare the Federated Model: Import or link discipline models (architectural, structural, MEP) into the coordination environment. Verify that shared coordinates, project base points, and true north alignment are consistent across all source models.
2. Configure Clash Detection Rules: When running Navisworks Clash Detection (from Revit), define tolerance thresholds, clash grouping rules, and priority filters. Separate hard clashes (physical intersections) from clearance violations to streamline review workflows.
3. Issue Tracking via BCF: Export detected issues as BCF (BIM Collaboration Format) topics linked to specific viewpoints. Assign responsibilities and deadlines, then distribute to discipline leads through the project's common data environment (CDE).
4. Verify Resolution and Close Out: After modelers resolve flagged issues, re-run clash detection to confirm clearance. Archive resolved topics and generate coordination reports for milestone documentation and audit trails.

Advanced Troubleshooting & Error Diagnostics

Common issues in Navisworks Clash Detection (from Revit) coordination workflows and their resolutions:

• False clash results from coordinate misalignment: Hundreds of clashes reported between models that should be spatially aligned. Resolution: Compare the origin points and shared coordinates of all source models. Even a 1mm offset produces systematic false clashes across the entire model. Re-export the source models with corrected shared coordinates and re-run the detection.
• BCF issues not visible in authoring tool: BCF topics created during Navisworks Clash Detection (from Revit) review don't show the correct viewpoint when opened in the BIM authoring tool. Resolution: Verify that the BCF file uses the same coordinate system as the authoring tool. Some tools interpret BCF camera positions differently (local vs. shared coordinates). Test with a single known-position issue to calibrate the viewpoint mapping.
• Model performance degrades with large federated models: Navigation becomes sluggish when reviewing Navisworks Clash Detection (from Revit) in a federation with many disciplines. Resolution: Use section boxes to limit the visible scope. Convert models to optimized formats (NWC cache files for Navisworks, lightweight IFC for web viewers). Disable element categories not relevant to the current review (furniture, plumbing fixtures) to reduce rendering load.

Cross-Discipline Collaboration & Handoff

As a coordination tool, Navisworks Clash Detection (from Revit) operates at the intersection of all project disciplines. Effective cross-discipline workflows require:

• Model Federation Protocol: Establish a documented schedule for model drops from each discipline (architecture, structure, MEP, civil). Define file formats, coordinate-system conventions, and naming standards that all contributors follow when publishing to the common data environment.
• BCF-Based Issue Communication: Export clash and coordination issues as BCF topics with embedded viewpoints, screenshots, and responsibility assignments. This open standard allows issue tracking to flow between coordination software, BIM authoring tools, and project management platforms without platform lock-in.
• Resolution Verification Loop: After discipline modelers address flagged issues, re-federate updated models and re-run detection rules to confirm clearance. Maintain a living coordination log that records issue history, resolution dates, and any accepted deviations from design intent.

Common pitfalls

• Running clash without proper filtering — millions of false-positive clashes inside walls.
• Treating every flagged clash as equal — some are model-noise (e.g., a fastener inside a steel section).
• Not coordinating tolerance values across teams — different clash thresholds produce different reports.

Relevant Revit FAQs

Direct answers from our technical editorial desk concerning related workflows.

🎓 Recommended Practice Lessons

Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:

Practical Workflow Tips

From coordination meeting rooms to the model, practical tips for Navisworks Clash Detection (from Revit):

• Run clashes in batches by discipline pair: Rather than running "everything vs. everything," set up discipline-pair tests. This organizes results into manageable groups that can be assigned to specific teams.
• Time-stamp every model version: Include the export date in filenames. Stale models in the federation are the single most common source of wasted coordination time.
• Create saved viewpoints for recurring meetings: Set up navigation viewpoints that match coordination zones. Consistent viewpoints ensure no area is accidentally skipped across meetings.
• Assign BCF issues to individuals, not teams: Issues assigned to "the MEP team" tend to be delayed. Assigning each Navisworks Clash Detection (from Revit) issue to a named individual produces faster resolution.

Sources & further reading

• Autodesk Help & Technical Documentation portal · Autodesk Inc.
• Revit Product Support Portal · Autodesk Inc.