HandbookBIM Clash Detection Workflow

BIM Clash Detection Workflow

ISO 19650-2:2018 · ISO 19650-2 — Delivery Phase of Assets; Clash Detection as part of Model Coordination
Comprehensive guide to BIM clash detection covering hard clashes, soft/clearance clashes, and workflow clashes. Includes the discipline coordination matrix, priority classification, resolution workflow, and common clash rules used in Indian construction projects.
ISO 19650
27 items shown
Clash Categories
Three fundamental types of clashes detected in federated BIM models
Clash TypeDisciplinesTolerancePriority
Hard ClashAny two physical elements occupying the same space0 mm (physical intersection)Critical
Soft Clash (Clearance Clash)Element violating required clearance or maintenance access zone around another element25–300 mm depending on element type and code requirementsHigh to Medium
Workflow Clash (4D/Time Clash)Scheduling conflict — two trades or activities requiring the same space at the same timeN/A (time-based)Medium
Duplicate Element ClashSame element modeled twice — from linked models or copy errors0 mm (exact or near-exact overlap)Low
Design Intent ClashElement violates design standards or code requirements (not physical intersection)Varies by code requirementHigh
Priority Classification
Classify each clash by severity to prioritise resolution — typical project classification
Clash TypeDisciplinesTolerancePriority
Priority 1 — CriticalStructural vs MEP (major services)0 mmCritical — resolve within 48 hours
Priority 2 — MajorArchitecture vs Structure, MEP vs MEP (different services)0–50 mmHigh — resolve within 1 week
Priority 3 — ModerateClearance violations, maintenance access issues25–150 mmMedium — resolve before construction of that zone
Priority 4 — MinorCosmetic or non-structural items50–300 mmLow — resolve before finishing works
Priority 5 — Acceptable / ApprovedKnown conditions accepted by design teamN/ANone — approved exception
Clash Resolution Workflow
Step-by-step process from detection to sign-off
Clash TypeDisciplinesTolerancePriority
Step 1 — Federated Model SetupAll disciplinesN/AN/A
Step 2 — Define Clash RulesBIM CoordinatorSet per ruleN/A
Step 3 — Run Clash DetectionBIM CoordinatorPer ruleN/A
Step 4 — Filter False PositivesBIM CoordinatorN/AN/A
Step 5 — Classify and AssignBIM Coordinator + Discipline LeadsN/AAssign P1–P5
Step 6 — Coordination MeetingAll discipline leadsN/AFocus on P1 and P2
Step 7 — Model Update and Re-checkAssigned disciplineN/AN/A
Step 8 — Sign-off and CloseBIM Coordinator + Project ManagerN/AN/A
Common Clash Rules
Standard discipline-vs-discipline clash tests used in building projects
Clash TypeDisciplinesTolerancePriority
Hard ClashStructural vs HVAC Ducts0 mmCritical
Hard ClashStructural vs Plumbing Pipes0 mmCritical
Hard ClashStructural vs Electrical Conduits/Trays0 mmHigh
Hard ClashHVAC Ducts vs Plumbing Pipes0 mmHigh
Hard ClashHVAC Ducts vs Electrical Cable Trays0 mmHigh
Soft ClashHVAC Equipment vs Maintenance Access600–900 mm clearanceMedium
Soft ClashArchitecture (False Ceiling) vs MEP Services50–100 mm below lowest serviceMedium
Hard ClashArchitecture (Walls/Doors) vs Structure (Columns/Beams)0 mmHigh
Soft ClashFire Protection (Sprinkler) vs All ServicesVaries — sprinkler deflector clearance per NBCHigh
Notes
False positive management is critical — poorly configured clash rules generate thousands of irrelevant results. Invest time in refining selection sets and exclusion rules before the first coordination meeting.
Clash batching: group related clashes by zone/floor/system rather than reviewing individually. A single routing change may resolve 20+ related clashes at once.
Sign-off process: every resolved clash must be verified in the updated federated model and signed off by the responsible discipline lead. Verbal agreements are not sufficient under ISO 19650.
Establish a service zone hierarchy at project kickoff: typical order from ceiling down is (1) HVAC ducts, (2) cable trays, (3) plumbing pipes, (4) sprinkler pipes, (5) electrical conduits.
Run clash detection at minimum fortnightly intervals during design development; weekly during construction documentation phase.
For Indian projects, clash detection reports should be part of the BIM Execution Plan (BEP) deliverables per IS 19650 adoption guidelines.
← Previous
BIM-Based Quantity Takeoff
Generated by InfraLens · infralens.in