How to Run Automated Clash Detection in Navisworks: Search Sets, Rules & BCF Export
Master multi-disciplinary BIM coordination in Navisworks Manage: build dynamic Search Sets, configure hard and clearance clash tolerances, group composite clashes, and export BCF 3.0 issues.
⚡ Quick Answer / Key Takeaway
Append architectural, structural, and MEP models into an .NWF federated file, create XML Search Sets by discipline/system, configure a Clash Detective matrix with a 5mm–10mm hard clash tolerance (or 50mm clearance tolerance), group clashes by grid/host element, and export via BCF.
Step-by-Step Instructions & Commands
Step 1: Build Dynamic Search Sets (Never Use Manual Selection Sets)
In Navisworks, open Find Items (`Shift+F3`) and build rule-based Search Sets (e.g., Category = Ducts AND System Classification = Supply Air). Save and export these sets as an XML template so they automatically capture newly added elements when weekly NWC/IFC models are refreshed.
Step 2: Configure the Priority Clash Matrix & Tolerance Thresholds
Open Clash Detective and create ordered test pairs following the construction hierarchy: (1) Structural vs Gravity Drainage, (2) Structural vs Pressurized Mains & Large HVAC Ducts, (3) HVAC vs Cable Trays. Set Hard Clash tolerance to 10mm to filter out harmless surface grazing.
Step 3: Group Related Clashes & Sync via BCF 3.0
When a single 30-meter duct runs through 12 structural steel joists, Navisworks reports 12 separate clashes. Group all 12 under the parent duct GUID as a single actionable coordination issue, assign it to the MEP lead, and export via a BCF 3.0 connector.
Common Issues & Troubleshooting Guide
| Common Failure / Problem | Root Cause & Recommended Solution |
|---|---|
| Clash Detective reports 15,000 clashes on day one | You are testing raw entire models against each other with 0.00mm tolerance. Apply Ignore Rules for 'Items in same group/composite object', set a 10mm tolerance, and test system-by-system using Search Sets. |
| Resolved clashes turn back to 'New' after weekly model update | The authoring team deleted and redrew the element instead of moving it, generating a brand-new Element ID / IFC GUID. Instruct teams to modify existing elements rather than deleting and recreating. |
Cross-CAD Compatibility & Alternatives
Exporting BCF 3.0 reports allows engineers using Revit, Archicad, Tekla, or GstarCAD Architecture to jump directly to the exact 3D clash camera coordinate without owning a Navisworks seat.
Engineering Best Practices Checklist
- Always verify Shared Coordinates and project base points before running clash tests.
- Include a soft Clearance Clash test (e.g., 500mm) around electrical switchgear and VAV access doors.
- Save your federated coordination workspace as an .NWF file (referencing external .NWC/.IFC files) and publish weekly frozen .NWD snapshots.
Related Concepts & Further Learning
Underlying Kernel Mechanics & Automated Prevention Protocol
To permanently prevent recurrence of How to Run Automated Clash Detection in Navisworks: Search Sets, Rules & BCF Export across enterprise project directories, CAD managers must understand how the underlying DWG object database (AcDbDatabase / GcDbDatabase) and graphics display pipeline manage entity handles, symbol tables, and external dependencies:
| Diagnostic Command / Variable | Recommended Production Value | Engineering Function & Impact |
|---|---|---|
| AUDIT / RECOVERALL | Fix Errors = Yes (Y) |
Validates B-tree symbol tables, repairs orphaned dictionary handles, and heals nested Xrefs. |
| -PURGE → Regapps (R) | Verify Each = No (N) |
Strips thousands of unreferenced third-party Registered Application IDs that bloat DWG memory. |
| GRAPHICSCONFIG | Hardware Acceleration = ON | Verifies DirectX 11/12 or OpenGL GPU driver allocation and clears corrupted display cache buffers. |