MEP (Mechanical, Electrical, and Plumbing) clash detection is the process of identifying spatial conflicts between building services systems before construction begins. In Australian construction, where MEP services can occupy 25–40% of a building’s volume, unresolved clashes discovered on site cause costly rework, programme delays, and compromised installation quality. BIM-based clash detection has become the industry standard for preventing these conflicts, yet many project teams still struggle with effective implementation.
This comprehensive guide covers the MEP BIM clash detection process for Australian construction projects, from model preparation and clash rules through to resolution workflows and reporting. Whether you are a BIM coordinator, MEP subcontractor, project manager, or design consultant, this resource will help you implement effective clash detection processes that reduce on-site coordination issues by 80–95%.
Clash Detection Overview
| Clash Type | Definition | Example | Tolerance |
|---|---|---|---|
| Hard clash | Two elements occupy the same physical space | Duct penetrating a structural beam | 0mm (no overlap) |
| Soft clash (clearance) | Elements too close for installation, insulation, or maintenance | Pipe within 50mm of electrical cable tray | 25-150mm (varies by system) |
| Workflow clash (4D) | Time-based conflict in construction sequence | Ductwork installed before structural opening is cast | Schedule-dependent |
The Clash Detection Process
Step 1: Model Preparation
Effective clash detection begins with properly prepared BIM models. Each MEP discipline — mechanical (HVAC), electrical, hydraulic (plumbing), and fire services — must be modelled to the agreed Level of Development (LOD), typically LOD 300 for design coordination and LOD 350–400 for construction coordination. Models must use correct categories, accurate element sizing, and consistent coordinate systems to enable meaningful clash detection.
Common model preparation issues that produce false positives include incorrect element categories (e.g., duct fittings modelled as generic models), oversized placeholder elements, unresolved design options in the model, and duplicate elements from copy-paste operations. Revit MEP provides tools for model health checking, but disciplined modelling practices are the foundation of reliable clash detection.
Step 2: Clash Rules and Tolerances
Clash rules define which element pairs are tested for conflicts and what tolerances apply. Effective clash rules avoid testing every element against every other element (which produces thousands of irrelevant results) and instead focus on meaningful conflicts:
| Clash Test | Test Between | Tolerance | Priority |
|---|---|---|---|
| MEP vs Structure | All MEP vs beams, columns, slabs, walls | 0mm hard clash | Critical |
| Duct vs Pipe | HVAC ductwork vs hydraulic/fire pipework | 25mm clearance | High |
| Duct vs Cable Tray | HVAC ductwork vs electrical containment | 50mm clearance | High |
| Pipe vs Cable Tray | Hydraulic/fire pipework vs electrical containment | 25mm clearance | Medium |
| MEP vs Architecture | All MEP vs ceilings, walls, floors | 0mm hard clash | Medium |
| Insulated elements | Insulated ducts/pipes vs all other MEP | Insulation thickness + 25mm | High |
| Maintenance clearance | Equipment access zones vs all elements | 600-1200mm (equipment-specific) | Medium |
Step 3: Clash Detection Execution
Clash detection is typically performed using Autodesk Navisworks Manage, which imports federated models from all disciplines and runs automated intersection tests based on defined clash rules. Alternative tools include Solibri Model Checker, BIMcollab, and Revit’s built-in Interference Check (suitable for single-file coordination). The MEP BIM team runs clash detection at regular intervals — typically weekly during active design phases — generating clash reports that track new, active, reviewed, and resolved clashes.
Step 4: Clash Categorisation and Prioritisation
Raw clash results from automated detection require manual review to categorise and prioritise. A typical MEP coordination model may produce 500–5,000 raw clashes, of which 60–80% are either false positives (modelling artefacts, acceptable overlaps) or duplicates (multiple clash points from the same conflict). The BIM coordinator reviews each clash and assigns status:
- Active — Genuine conflict requiring resolution by a specific discipline
- Reviewed — Confirmed as requiring design change, assigned to responsible party
- Resolved — Design change made, clash no longer exists in updated model
- Approved — Accepted as-is (e.g., pipe sleeve through slab is not a true clash)
Step 5: Clash Resolution
Clash resolution follows a priority hierarchy based on the difficulty and cost of moving each element:
| Priority | Discipline | Rationale |
|---|---|---|
| 1 (hardest to move) | Structure | Structural elements are load-bearing and extremely costly to modify |
| 2 | Hydraulic (gravity) | Gravity drainage requires specific gradients — limited flexibility |
| 3 | Fire services | Sprinkler coverage requires specific head locations |
| 4 | Mechanical (large duct) | Large ductwork has limited routing options in congested spaces |
| 5 | Electrical (cable tray) | Cable trays are relatively flexible in routing |
| 6 (easiest to move) | Hydraulic (pressure) | Pressure pipework can be routed flexibly |
Tools for MEP Clash Detection
| Tool | Strengths | Best For |
|---|---|---|
| Navisworks Manage | Industry standard, powerful clash grouping, timeliner for 4D | Large multi-discipline projects, construction coordination |
| Solibri Model Checker | Rule-based checking, code compliance, IFC support | Design quality assurance, regulatory compliance |
| BIMcollab | Cloud-based, BCF issue tracking, multi-platform | Distributed teams, issue management |
| Revit Interference Check | Built-in, no additional software, real-time | Single-discipline checking, quick verification |
| Autodesk Construction Cloud | Cloud coordination, model comparison, mobile access | Contractor coordination, field verification |
Common MEP Clash Hotspots
Experience across Australian construction projects shows consistent clash concentration in specific building zones:
- Corridor ceilings — All horizontal MEP services converge in corridors, creating the highest clash density
- Services risers — Vertical distribution spaces where multiple disciplines compete for limited shaft area (critical in high-rise buildings)
- Plant rooms — Dense equipment layouts with maintenance clearance requirements
- Penetrations — Services crossing fire-rated walls and floors (coordination with fire engineering)
- Ceiling plenums — Space between structural soffit and ceiling grid, typically 300–600mm deep
- Entry/transition zones — Where external services enter the building and branch to internal distribution
Clash Detection Best Practices
- Establish clash rules early — Define tolerance standards in the BIM Execution Plan (BEP) before modelling begins
- Run detection weekly — Regular detection catches clashes early when resolution is cheapest
- Track trends, not just counts — Monitor new vs resolved clash rates to measure coordination progress
- Use BCF for issue management — BIM Collaboration Format (BCF) links clash issues directly to model locations
- Include insulation and access zones — Hard clashes are obvious; soft clashes from insulation and maintenance access cause more on-site issues
- Coordinate with shop drawings — Verify that fabrication-level detail maintains the clearances established during design coordination
Why Outsource Clash Detection?
Effective clash detection requires dedicated BIM coordinators with cross-disciplinary MEP knowledge. Outsourcing to Meter Built provides:
- Experienced BIM coordinators — Staff who understand MEP system priorities and resolution strategies
- Dedicated coordination time — Not competing with design production deadlines
- Standardised processes — Proven clash rules, reporting templates, and resolution workflows
- Cross-project learning — Lessons from healthcare, data centre, industrial, and commercial projects
- Cost efficiency — Competitive rates for coordination services
Get a Quote for MEP Clash Detection
Meter Built provides MEP BIM clash detection and coordination services for projects across Melbourne, Sydney, Brisbane, and all Australian capital cities. From design-stage coordination to construction-phase shop drawing checking, our team ensures your MEP systems are fully coordinated before reaching site.
Contact Meter Built today for a free consultation on MEP clash detection for your project. Visit our project portfolio and learn about our BIM coordination services.
Frequently Asked Questions
What is the difference between hard and soft clashes?
Hard clashes occur when two elements physically occupy the same space (e.g., a pipe intersecting a beam). Soft clashes occur when elements are too close together, violating minimum clearance requirements for insulation, installation access, or maintenance. Soft clashes typically use tolerances of 25–150mm depending on the systems involved.
How many clashes should we expect on a typical project?
A well-managed MEP coordination model for a mid-sized commercial building typically generates 200–1,000 meaningful clashes (after filtering false positives). Healthcare and data centre projects may produce 2–5x more due to higher services density. The goal is not zero initial clashes — it is zero unresolved clashes before construction begins.
When should clash detection start?
Clash detection should begin at the end of schematic design (LOD 200) with high-level spatial checks, intensify during design development (LOD 300) with full discipline-by-discipline testing, and continue through construction documentation (LOD 350–400) as shop drawing models are developed. Starting early catches major routing conflicts when changes are cheapest.
What software is best for MEP clash detection?
Navisworks Manage remains the industry standard for MEP clash detection in Australia, particularly for Revit-based workflows. Solibri Model Checker is preferred for IFC-based coordination and rule-based compliance checking. Cloud platforms like Autodesk Construction Cloud are increasingly used for contractor-side coordination. The best tool depends on your team’s software ecosystem and project requirements.
How does clash detection reduce construction costs?
Industry research shows that resolving a clash digitally costs approximately $50–200 in BIM coordination time, while resolving the same clash on site costs $1,000–10,000+ in rework labour, materials, programme delays, and potential design compromise. Projects with effective clash detection typically see 70–90% reduction in on-site MEP coordination issues.
Can clash detection be outsourced?
Yes. Many Australian MEP consultancies and contractors outsource clash detection to specialist BIM coordination providers like Meter Built. The outsourced team receives federated models, runs clash detection using agreed rules, categorises and prioritises results, and issues coordination reports. This allows the design team to focus on resolution rather than detection.