Skip to main content

MEP checklist

MEP BIM Coordination Checklist for Data Center Projects

Coordination is not a single event. It is a staged process with different checks at different milestones.

Ardaron editorial · Updated 3 September 2026 · Named technical review pending

This is a delivery-method resource, not project-specific design. Electrical protection, cable sizing, cooling capacity, fire strategy and structural loads require the appointed designers and the applicable codes. Technical review of this cluster by a named senior BIM/MEP lead is pending; do not treat it as sealed guidance.

MEP coordination on data-center projects involves electrical power distribution, cooling systems, plumbing, fire protection, and controls — all competing for space in corridors, risers and plant rooms. A checklist structures the coordination effort by stage, ensuring that early-stage decisions about routing and zoning are made before late-stage detail makes them expensive to change.

Purpose of an MEP coordination checklist

Checklists do not replace engineering judgement. They ensure that standard checks are not forgotten, that coordination happens at the right stage, and that issues are documented. A checklist also provides evidence of due diligence — important when coordination disputes arise.

Stage-based coordination

Different checks apply at different stages. Running detailed clash detection on a concept model wastes time. Ignoring routing strategy until detailed design creates unresolvable conflicts. Typical stages:

Coordination focus by stage

StagePrimary focusMEP coordination activity
ConceptSpace allocation, major routing strategyZone assignment, riser positions, plant-room sizing
Developed designSystem routing, clearance validationContainment routes, main duct/pipe runs, envelope reservations
Technical designDetailed coordination, clash resolutionFull clash detection, hanger/support positions, fabrication interfaces
ConstructionInstallation sequence, as-built updatesField coordination, RFI resolution, model updates

MEP coordination checklist

Electrical — all stages

Mechanical — all stages

Plumbing

Fire protection

Cross-discipline — concept stage

Cross-discipline — developed design

Cross-discipline — technical design

Common coordination failures

Routing strategy decided at detailed design

Why it happens. Early stages focused on single-discipline work.

Impact. Major re-routes when systems collide.

Mitigation. Cross-discipline routing workshop at concept stage.

Clearance envelopes not modelled

Why it happens. Seen as optional coordination aids.

Impact. Zero clashes but equipment cannot be maintained.

Mitigation. Envelopes are mandatory coordination objects.

Checklist used once at project end

Why it happens. Treated as QA sign-off, not staged process.

Impact. Issues found too late to resolve cheaply.

Mitigation. Stage-appropriate checklist runs at each milestone.

FAQ

Who owns the MEP coordination checklist?
Typically the BIM coordinator or MEP lead. Each discipline completes their section; the coordinator verifies cross-discipline items.
How does this relate to clash detection?
Clash detection is one check within the coordination process. The checklist ensures clash detection happens at the right stage and that non-geometric coordination (routing strategy, clearance policy) is also addressed.
Should we customise this checklist?
Yes. The checklist should reflect project scope, client requirements and local codes. Use this as a starting point, not a final document.

Sources

  1. 1. ISO, ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Part 1: Concepts and principles (2018). https://www.iso.org/standard/68078.html. Accessed 2026-09-03.
  2. 2. ISO, ISO 19650-2:2018 — Information management using building information modelling — Part 2: Delivery phase of the assets (2018). https://www.iso.org/standard/68080.html. Accessed 2026-09-03.
  3. 3. Autodesk, Overview of Clash Detective Tool (2026). https://help.autodesk.com/cloudhelp/2026/ENU/Navisworks-Clash-Detective/files/GUID-36D9904E-12F3-4F82-8DD3-C2103DB0BC29.htm. Accessed 2026-09-03.
  4. 4. CIBSE, KS18: Data Centres: An Introduction to Concepts & Design (2012). https://www.cibse.org/knowledge-research/knowledge-portal/ks18-data-centres-an-introduction-to-concepts-design/. Accessed 2026-09-03.
  5. 5. ASHRAE, ASHRAE Data Center Resources / TC 9.9 Datacom Series (2024). https://www.ashrae.org/technical-resources/bookstore/datacom-series. Accessed 2026-09-03.

Continue

Have a delivery constraint?

Three ways to start a conversation.

Engineering capacity issue?

Tell us the discipline, the software environment and the capacity you need.

Procurement bottleneck?

Tell us where the team is constrained — enquiries, follow-up, comparison or reporting.

Difficult sourcing requirement?

Send us the specification, the quantity and the date you need it on site.