BIM

Clash Detection

Automated process of finding spatial conflicts between BIM models. Hard clash (overlap), soft clash (clearance), 4D clash.

Also calledclash checkinterference check
Related on InfraLens
Definition

Clash detection is the automated process of identifying spatial conflicts between BIM model elements. Three types of clashes are typically identified: (1) Hard clashes — solid elements physically overlapping (a beam passing through a column, a duct intersecting a slab). (2) Soft clashes — elements that don't intersect but violate clearance requirements (a duct closer than 50 mm to a beam, blocking maintenance access). (3) 4D clashes — temporal conflicts where elements would be in the same place at the same time during construction (a duct installed before the slab is structurally adequate). Tools: Autodesk Navisworks Manage, Solibri Model Checker, BIMcollab, Trimble Connect.

Clash detection workflow: (1) Federate models — combine architectural, structural, MEP, and other discipline models into a single coordinated model. (2) Run clash detection — software identifies all hard, soft, and 4D clashes per defined rules. (3) Categorise — by severity (critical, major, minor) and discipline (structural-MEP, MEP-MEP, architectural-MEP). (4) Resolve — design teams modify their respective models to eliminate clashes. (5) Re-run — verify clashes are resolved. (6) Document — clash report for project record. Modern Indian projects routinely run clash detection at LOD 300+ models, with major federations performed at design milestones (50%, 75%, 90% design).

Real-world impact: clash detection finds 1,000-10,000+ clashes in a typical mid-rise office tower at LOD 300. Without resolution, each clash potentially requires field rework. Cost per field rework is 5-50× the cost of resolution at design stage. For a typical Mumbai high-rise: design-stage clash resolution costs ₹4-8 lakh; equivalent field rework would cost ₹2-4 cr. The most-overlooked aspect of clash detection: post-resolution verification. Many projects run initial clash detection but skip the verification step after resolution; clashes that were 'thought to be resolved' often re-emerge during construction. Verified clash-detection workflow with iterative federation is essential for genuine value.

Where used
  • Design coordination — primary value of BIM in modern construction
  • Pre-construction quality assurance — eliminating field rework
  • Construction documentation — clash-free drawings produced from federated models
  • Sub-contractor coordination — across architectural, structural, MEP
  • 4D scheduling — temporal clash analysis during construction sequencing
Acceptance / threshold
Per project BEP (BIM Execution Plan) + ISO 19650: clash detection rules defined; federated model produced; clashes categorised and resolved; verification re-run; clash report archived.
Site example
Site reality: a Bengaluru airport terminal project's clash-detection workflow identified 8,400 clashes at LOD 300, of which 1,200 were 'critical' (HVAC ducts intersecting structural elements). Resolution cost ₹4.8 cr in design effort. Estimated field rework if uncaught: ₹28 cr in concrete demolition, MEP re-routing, schedule slip. Clash detection ROI: 5.8× for this project; common range 3-10× for major Indian construction.
Frequently asked
What is clash detection in BIM?
Clash detection is the automated process of identifying spatial conflicts between BIM model elements. Three types: hard (physical overlap), soft (clearance violation), 4D (temporal conflict). Tools: Navisworks Manage, Solibri Model Checker. Run on federated models combining architectural, structural, and MEP. Resolution at design stage is 5-50× cheaper than field rework.
How is clash detection performed?
(1) Federate discipline models in single coordinated model. (2) Define clash detection rules (hard clash, soft clearance, etc.). (3) Run software (Navisworks, Solibri) to identify clashes. (4) Categorise by severity and discipline. (5) Assign to responsible designer for resolution. (6) Modify model. (7) Re-federate and re-run. (8) Verify resolution. (9) Archive clash report. Iterative through design milestones.
What is the cost benefit of clash detection?
Clash detection at design stage typically costs 1-3% of project value. Field rework cost is 5-50× the design-stage cost — typically 5-20% of project value if uncaught. ROI of clash detection: 3-10× for Indian projects. The cost benefit is highest for: complex MEP-intensive projects (airports, hospitals, malls), high-rise construction, and prefabricated elements where field adjustments are difficult.
Related bim terms