BIM for MEP Engineers: A Practical Guide to Coordinating Mechanical, Electrical, and Plumbing Models

MEP coordination is where BIM either proves its value or exposes its weaknesses. A building’s mechanical, electrical, and plumbing systems are the most spatially complex elements in any project - and the most likely to conflict with each other and with the structure. When coordination works well, you catch problems digitally before they become expensive on-site rework. When it doesn’t, BIM becomes an expensive drawing tool.

This guide covers how MEP coordination actually works in practice - the workflows, tools, common failures, and what separates effective coordination from box-ticking.

---

Why MEP Coordination Is the Hardest Part of BIM

In a typical commercial building, MEP systems can account for 40-60% of total construction cost. They route through the same ceiling voids, risers, and service corridors. A 600mm duct, a 150mm pipe, a cable tray, and a structural beam all need to fit in a 400mm ceiling void - and someone has to figure out who moves.

Traditional coordination used 2D overlay drawings. An architect would layer the mechanical plan, electrical plan, and plumbing plan on top of each other and manually look for conflicts. This catches obvious problems but misses:

• Vertical conflicts (duct at the same elevation as a beam)
• Insulation clearances (the duct fits, but the insulation around it doesn’t)
• Maintenance access (the valve fits, but there’s no room to turn it)
• Sloped services (a pipe that slopes 1:40 may clear a beam at one end but not the other)

BIM-based coordination in 3D catches all of these - if the models are built correctly and the process is managed well.

---

The Coordination Workflow (Step by Step)

Here’s how MEP coordination typically runs on a well-managed BIM project:

1. Establish the BIM Execution Plan (BEP)

Before anyone starts modelling, the project team agrees on:

BEP Item	What to Define
Software	Which tools each discipline uses (Revit, MagiCAD, Tekla, etc.)
Exchange format	Native Revit links or IFC exports
LOD requirements	What level of detail each system needs at each stage
Coordination schedule	How often models are shared (weekly, fortnightly)
Naming conventions	File names, workset names, system naming
Coordination tool	Navisworks, Solibri, BIMcollab, or similar
Issue resolution process	Who reviews clashes, who resolves, what’s the escalation path

2. Model in Discipline-Specific Files

Each MEP discipline works in their own model (or workset within a shared model):

• Mechanical: HVAC ductwork, AHUs, FCUs, grilles, dampers, plant rooms
• Electrical: Cable trays, conduits, switchboards, distribution boards, lighting fixtures
• Plumbing: Pipework (hot/cold water, waste, stormwater), fixtures, pumps, tanks
• Fire protection: Sprinkler pipework, hydrants, fire dampers

Each model links the architectural and structural models as reference - so MEP engineers can see the building envelope, floor-to-floor heights, and structural elements they need to route around.

3. Federated Model Review

At each coordination milestone, all models are combined (federated) in a coordination tool:

Navisworks is the most common choice for Revit-based projects:

• Append all Revit models (or IFC exports)
• Run Clash Detective with configured rules
• Generate clash reports

Solibri is increasingly popular, especially on IFC-based projects:

• Import IFC files from all disciplines
• Run rule-based checking (not just geometry clashes)
• Can check code compliance, clearance rules, and naming conventions

4. Clash Detection and Classification

Raw clash detection produces noise. A typical first run might flag 5,000+ clashes. Most are irrelevant:

Clash Type	Priority	Example
Hard clash	High	Duct passes through structural beam
Soft clash (clearance)	Medium	Pipe within 50mm of electrical panel (maintenance access)
Duplicate	Low/Ignore	Same clash flagged multiple times for connected elements
Tolerance clash	Ignore	Elements touching but not conflicting (wall meets slab)

Effective clash management means:

• Setting up clash rules that ignore known acceptable conditions (e.g., pipes passing through sleeves)
• Grouping related clashes (20 clashes from one duct run misrouted = 1 issue)
• Classifying by priority and assigning to the responsible discipline

5. Issue Resolution

Clashes are assigned to the responsible party using BCF (BIM Collaboration Format) or the coordination tool’s built-in tracking:

• Architect moves: When MEP routing needs a ceiling height change or bulkhead
• Structural moves: Rare - usually MEP routes around structure, not the other way
• MEP reroutes: Most common - the MEP engineer finds an alternative path
• Design change required: When no routing works within the current design - escalate to the design team

6. Iterate

The cycle repeats. Each coordination round should produce fewer clashes as issues are resolved. On a well-run project, you might see:

• Round 1: 3,000 clashes (mostly noise, ~200 real issues)
• Round 2: 800 clashes (~80 real issues)
• Round 3: 150 clashes (~30 real issues)
• Round 4: <50 clashes (detail-level items)

---

LOD Requirements for MEP Coordination

Level of Development determines how much detail is in each model. For coordination to work, MEP models need sufficient detail - but not too much:

Project Stage	Recommended LOD	What’s Modelled
Concept design	LOD 200	Main plant rooms, primary risers, approximate routing
Developed design	LOD 300	All ductwork/pipework routed with correct sizes, equipment placed
Technical design	LOD 350	Insulation, supports, access panels, connections
Construction	LOD 400	Fabrication-ready detail, hangers, brackets, exact lengths

The sweet spot for coordination is LOD 300-350. Below LOD 300, models don’t have enough spatial accuracy for meaningful clash detection. Above LOD 350, you’re coordinating installation details that are better resolved on site.

---

Software Choices for MEP BIM

Tool	Discipline	Notes
Revit MEP	All MEP disciplines	Industry standard, strong integration with architectural Revit models
MagiCAD	HVAC, Electrical, Piping	Runs inside Revit or AutoCAD, adds MEP-specific automation
AutoCAD MEP	Legacy workflows	Still used but declining - no 3D coordination capability
Plancal Nova	HVAC, Plumbing	Popular in German-speaking markets
Trimble Nova	Electrical	Specialist electrical design and routing
Stabicad	MEP (all)	Strong in Netherlands and Belgium

For most projects: Revit MEP is the default choice if the architect is using Revit. The native linking between Revit Architectural and Revit MEP models is seamless - no IFC conversion needed for coordination.

---

Common Coordination Failures

1. Late MEP Involvement

MEP engineers brought in after the architectural design is frozen have no room to manoeuvre. Ceiling voids are too shallow, risers are too small, and plant rooms can’t fit the required equipment. Early involvement (from concept stage) is essential.

2. Coordination Without Authority

Running clash detection is pointless if nobody has the authority to make decisions. A common failure mode: clashes are identified, reports are generated, meetings happen, but nobody resolves anything because the design team won’t adjust ceiling heights and the MEP team can’t reroute without more space.

Fix: The BEP must define who has decision authority for coordination conflicts.

3. Modelling at Wrong LOD

If ducts are modelled as single-line placeholders (LOD 200) while structural beams are at LOD 350, clash detection produces meaningless results. All disciplines need to be at comparable LOD for coordination to work.

4. Ignoring Insulation and Clearances

A duct that fits between two beams with 10mm clearance won’t fit once you add 50mm insulation to both sides. Always model insulation (or use soft clash tolerances that account for it).

5. “We’ll Sort It on Site”

The whole point of BIM coordination is to avoid this. If the coordination process regularly defers problems to site resolution, the process has failed.

---

Measuring Coordination Success

How do you know if your MEP coordination is working?

• RFI count drops compared to similar past projects
• On-site clashes are rare (not zero - some detail-level conflicts are normal)
• Coordination meetings get shorter over the project lifecycle
• Contractors trust the model enough to pre-fabricate from it
• No emergency ceiling drops or bulkhead additions during construction

The ultimate test: can the contractor install MEP systems in the sequence planned, without ripping out and rerouting? If yes, coordination worked.

---

Want to build MEP coordination skills? The Archgyan Academy offers BIM courses covering coordination workflows, Revit MEP, and practical clash detection processes.