BIM and MEP coordination

The space between a warehouse roof deck and the top of the racking, or above an office ceiling, is where the trades fight. Sprinkler pipe, ductwork, conduit, lights and structure all want the same few hundred millimetres. BIM coordination moves that fight from the site, where it costs rework and delay, to a model, where it costs a meeting. The owner pays for both, so the owner should decide which one happens.

Learning outcomes

• Explain what MEP coordination in a federated model does, and the difference between hard, clearance and workflow clashes.
• Use the Level of Development (LOD) scale to say what a model is reliable for, especially LOD 300, 350 and 400.
• Describe the coordination cycle from clash run to zone sign-off and how it feeds shop drawings and the look-ahead.
• List what the owner must put in the tender documents and BIM Execution Plan for coordination to happen on a design-bid-build project.

The lesson

What coordination is for

On most projects the consultants' mechanical and electrical drawings are diagrammatic. They show what systems are needed and roughly where they run, not the exact route of every pipe and duct. Each trade then designs its own installation, often with its own fabrication models, and each assumes the space is free. MEP coordination is the step where those separate designs are combined and checked against each other and against the structure before anything is fabricated.

Penn State's BIM Project Execution Planning Guide (version 3.0, 2021) calls this BIM use "coordinate design models". Teams combine the discipline models into a federated model, run automated clash detection and review the result visually. The guide lists the benefits as fewer field conflicts, lower cost and shorter schedules, fewer field RFIs, less waste and more reliable prefabrication.

Three kinds of clash

A hard clash is two objects in the same space: a duct through a joist chord. A clearance clash, sometimes called a soft clash, is when objects do not touch but a required space is lost: access in front of an electrical panel, or the zone below a sprinkler head that must be clear for its spray. A workflow clash is a sequencing conflict, such as a ceiling scheduled before the services above it are tested. Clearance clashes are the ones automated tools miss unless someone has modelled the clearance zones, and they are often the expensive ones.

Raw clash counts mean little. A single duct crossing ten joists produces ten clashes. Coordinators group related clashes, discard those under an agreed tolerance and false positives, and assign each group to the trade that should move. The useful measure is open clash groups by zone, trending to zero before fabrication.

Level of Development

LOD describes how far a model element can be relied on, not how detailed it looks. The scale comes from the American Institute of Architects' digital practice documents, and the BIMForum LOD Specification, updated most recently in a 2025 edition, refines it for each building system. BIMForum added LOD 350 specifically for trade coordination. The specification does not say which LOD is needed at which milestone; that belongs in the project's BIM Execution Plan.

The coordination cycle

Coordination is a loop, run by zone. Figure 1 shows it. The rules come first: which trades model, to what LOD, in which software and file format, with what tolerances, which zones in which order, and who decides when two trades want the same space. These rules live in the BIM Execution Plan. The models are exchanged in a common data environment. ISO 19650, the international series on information management using BIM, describes information moving through four states in that environment: work in progress, shared, published and archived. A zone is signed off when all trades agree it is clash-free; only then are its shop drawings and fabrication released.

Who does what on design-bid-build

On a design-bid-build project the owner contracts separately with the Consultant and the contractor, so coordination only happens if the tender documents ask for it. The usual split is that the Consultant's models are issued for reference while the drawings and specifications remain the contract documents, and the contractor runs coordination with its trades. The tender should say which trades model, to what LOD, by which dates, who runs the clash sessions, what the Consultant reviews, and what the owner receives at the end. If it says nothing, coordination becomes informal overlay drawings, or nothing at all.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan with a 9.75 m clear height, ESFR sprinklers and a 900 m² two-level office mezzanine. The contract is CCDC 2-2020 with Halvorsen Builders Ltd. (fictional); Ridgeline Architects Inc. (fictional) is the Consultant with structural and MEP subconsultants. See the Northgate fact sheet.

Why the warehouse roof zone matters

ESFR sprinklers are less tolerant of obstructions than standard spray sprinklers, because their spray pattern is what controls a rack fire. An article in PHCP Pros on NFPA 13-2019 reports Fire Protection Research Foundation testing in which an obstruction as small as 1½ inches, directly below and within 8 inches of the sprinkler, significantly disrupted the spray. The same article names joist bridging, conduit, ductwork and lights as the obstructions that cause most problems in practice. All four live in Northgate's roof zone, shown in Figure 2. Whether a given layout complies is for the sprinkler designer and the fire protection engineer to decide; the owner's job is to make sure the process gives them the chance.

The first clash run

Northgate's Division 01 (illustrative) requires Halvorsen to coordinate the sprinkler, mechanical and electrical trades in a federated model at LOD 350 for the warehouse roof zone and the mezzanine ceilings, with zone sign-off before fabrication. Ridgeline issues its design models for reference. Halvorsen runs the first full clash test on Monday April 12, 2027, after the joist shop drawings are reviewed and before sprinkler pipe is fabricated. Figure 3 shows the grouped results.

View the data

Discipline pair	Clash groups (illustrative)
Sprinkler vs joists and bridging	146
Sprinkler vs high-bay lights	92
Duct vs joists	58
Duct vs sprinkler	41
Conduit and cable tray vs sprinkler	27
Plumbing vs structure (mezzanine)	19

The largest group, sprinkler against joists and bridging, is mostly solved by moving branch lines and heads to the joist spacing, which is cheap now and expensive after the pipe is cut. The second group shows a dependency outside the model: the high-bay light layout follows the aisles, and the aisles follow the owner's racking layout, which is not final. The coordination team signs off the roof zone in stages but holds the lights in area A open, and that open item becomes the RFI that shows up as a constraint in Halvorsen's August look-ahead in lesson 20. The owner's fix is to freeze the racking layout, not to ask the trades to work faster.

Owner's move

• Write coordination into the tender. Name the trades that model, the LOD, the zones, the sign-off rule and the dates, in Division 01 or a BIM requirements section.
• Require a BIM Execution Plan early. Ask for it within a few weeks of award, and check it sets tolerances, clash rules and who decides.
• Feed the model the owner's inputs. Racking layouts, equipment and tenant fit-out decisions shape the services; late owner inputs cause late coordination.
• Track open clash groups by zone. Ask for the trend monthly, and link zone sign-off to fabrication release in the schedule.
• Decide what you want at the end. Specify whether you receive coordinated models, record drawings or both, and in what format.

Common mistakes

1. Assuming the design model is coordinated. Diagrammatic MEP design at LOD 300 is not ready for fabrication.
2. Reporting raw clash counts. Without grouping and tolerances, the numbers rise and fall for reasons that mean nothing.
3. Testing only for hard clashes. Sprinkler spray zones, access space and maintenance clearances need modelled clearance zones.
4. Fabricating before sign-off. Pipe cut to an uncoordinated layout is rework waiting to happen.
5. Leaving the owner's inputs open. Racking, equipment and fit-out decisions made late force the trades to re-coordinate.

Quick quiz

1. A high-bay light hangs inside the clear zone below an ESFR head but touches nothing. What kind of clash is it?

   1. Hard clash
   2. Clearance clash
   3. Workflow clash
   4. Not a clash

2. Which LOD was added by BIMForum for trade coordination?

   1. LOD 200
   2. LOD 300
   3. LOD 350
   4. LOD 500

3. When should a zone's sprinkler pipe be released for fabrication?

   1. When the design model is issued
   2. After the zone is signed off as coordinated
   3. When the pipe is needed on site
   4. After the first clash run

4. In ISO 19650's common data environment, which state is information in when it is available for coordination and review?

   1. Work in progress
   2. Shared
   3. Published
   4. Archived

5. On a design-bid-build project, what makes the contractor responsible for BIM coordination?

   1. Industry custom
   2. The Consultant's design model
   3. Requirements written into the tender documents
   4. The building permit

Show answers and explanations

1. B. Nothing intersects, but a required clear space is lost.
2. C. LOD 350 adds interfaces with other systems, which is what coordination needs.
3. B. Fabrication follows sign-off, so pipe is cut to a layout every trade has agreed.
4. B. Shared information is available to others for coordination; published is approved for use.
5. C. Without written requirements, the contractor has no obligation to model or coordinate in BIM.

Key terms

Federated model

Separate discipline models combined in one view for coordination, each still owned by its author.

Clash detection

Automated testing of a federated model for objects that intersect or break clearance rules.

Clearance clash

A conflict where objects do not touch but a required space, such as access or a sprinkler's spray zone, is lost.

Level of Development (LOD)

A scale for how far a model element can be relied on, from 100 (conceptual) to 400 (fabrication).

BIM Execution Plan

The project document that sets BIM uses, LOD, software, exchange, tolerances and responsibilities.

Common data environment (CDE)

The shared platform where project information moves through work in progress, shared, published and archived states.

Zone sign-off

Agreement by all trades that a zone is coordinated, which releases its shop drawings and fabrication.

References

1. Penn State Computer Integrated Construction, BIM Project Execution Planning Guide v3.0: coordinate design models (2021).
2. BIMForum, Level of Development (LOD) Specification (2025 edition).
3. Building Design + Construction, Level of Development: will a new standard bring clarity to BIM model detail? (August 2013).
4. Novatr, Your guide to BIM clash detection: types, tools and best practices.
5. Thinkproject, ISO 19650: a practical guide to BIM information management.
6. PHCP Pros, Are ESFR sprinklers OK? Part II: obstructions (May 2020).

Verified on November 6, 2026.

Next lesson in this trackMunicipal and third-party inspections (coming soon)