Navigating Clash Resolution Workflows in Navisworks Manage

# Navigating Clash Resolution Workflows in Navisworks Manage

Running an automated clash test in Navisworks is easy. Resolving the resulting 15,000 conflicts is where projects fail. General Contractors and VDC Leads need a systematic approach to group, prioritize, and resolve clashes before they reach the job site.

The Hierarchy of Clash Prioritization Not all clashes are created equal. A 5mm pipe penetrating a drywall partition is a field tolerance issue. A 600mm HVAC duct colliding with a primary structural steel beam is a major design failure.

1. **Hard Clashes (Gravity vs. Gravity):** Structural steel vs. Concrete. These are resolved first. 2. **System Clashes (MEP vs. Structural):** HVAC ducts, large bore piping, and cable trays vs. Primary structure. 3. **Clearance Clashes (Soft Clashes):** Failing to leave the required 600mm maintenance access space around an AHU unit. 4. **Trade vs. Trade (MEP vs. MEP):** Ductwork vs. Fire Sprinkler piping.

Establishing Custom Clash Rules & Tolerances By utilizing Navisworks XML clash rules, VDC coordinators can automatically ignore irrelevant clashes (e.g., ignoring any pipe-to-wall clash where the pipe diameter is under 50mm). Setting a 15mm clearance tolerance prevents the system from flagging minor field-adjustable discrepancies.

The Weekly Coordination Cadence Successful enterprise coordination runs on a tight schedule: - **Tuesday:** Subcontractors upload updated NWC models to the CDE. - **Wednesday:** VDC Lead runs automated Navisworks Batch Utility, grouping clashes by grid intersection. - **Thursday:** The live ICE (Integrated Concurrent Engineering) Coordination meeting. High-priority clashes are assigned a status of *Active* or *Reviewed*. - **Friday:** Issue viewpoints are synced back to Revit via plugins like Revizto or BIMTrack for the modeling team to fix.