What you will learn
- What MEP coordination covers across mechanical, electrical, and plumbing
- How services models, risers, and plant spaces are coordinated
- What clash resolution workflows look like for services
- How installation drawings are produced from coordinated models
- How to phase a platform from one service to full coordination
What an MEP design coordination platform is
MEP coordination software brings building services models together and resolves them into a buildable design. Mechanical, electrical, and plumbing engineers each model their systems — ductwork, pipework, cable routes, plant — and the platform federates those models with architecture and structure, runs clash detection, and tracks each clash and coordination issue to a resolved, modelled solution. The output is installation drawings that installers can actually build from.
Services coordination is where clashes concentrate, because services compete for the same ceiling voids, risers, and plant spaces. A platform that only reports clashes without a resolution workflow — proposed fix, modeller, approval — leaves the hardest work, deciding who moves, to corridor conversations.
Core features
Resolution workflow, not just clash lists, defines the product.
- Services model federation with architecture and structure
- Clash detection tuned for services: clearances, access, and maintenance space
- Issue and clash resolution workflows with ownership and approval
- Riser, ceiling void, and plant-space coordination views
- Installation drawing production from coordinated models
- Change tracking when models update after coordination
How it is built
Start with one service's coordination, then add services and drawing production.
- Federation: services models with architecture and structure for one project
- Clashes: detection tuned for services, with grouping and prioritisation
- Resolution: issue workflows, proposed fixes, and approvals
- Spaces: riser, void, and plant-space coordination views
- Drawings: installation drawing production and change tracking
Technology choices
The platform should accept services models in their native formats and federate them, rather than requiring remodels. Services engineers work in specialist tools, and a coordination platform that demands rework will be bypassed.
Clearance and access rules should be configurable. Maintenance access, installation clearance, and service zones differ by project and system, and the platform should let coordinators set and document those rules.
Challenges to plan for
Late design changes undo coordination. When architecture or structure changes after services coordination, the platform should re-run clash detection and flag affected services areas, rather than leaving coordinated work silently invalid.
Ownership disputes slow resolution. When a clash needs one service to move, the workflow should assign ownership and a decision route — coordinator decision where needed — instead of leaving the clash open indefinitely.
Who it is for, and its limits
MEP coordination fits services engineering consultancies, MEP contractors' design teams, and multi-discipline firms coordinating services-heavy projects. It fits projects where ceiling voids and risers are contested space.
The platform does not design services systems. System sizing, selection, and engineering design stay with services engineers; the platform coordinates their models into a buildable whole.
What a first release looks like
A first release should federate services models and run clash resolution for one project, with issue ownership and approval. Installation drawing production and space-specific coordination views come later, once a coordination cycle has closed real clashes through the workflow, including a clash where one service had to move and the decision was recorded. The release must be proven on a services-heavy floor — ceiling voids and risers contested — because simple projects hide coordination difficulty.
Take a floor where ductwork, pipework, and cable routes compete for one ceiling void. Clash detection groups the conflicts, the coordinator assigns each to an owner, and the mechanical team reroutes one run with the change modelled and approved. The updated model is rechecked, the clash closes, and the installation drawing for the void reflects the coordinated layout. When architecture later moves a wall, the affected services areas are flagged for rechecking rather than left silently invalid. If the reroute decision lives only in a meeting note, the workflow is incomplete.
A mistake worth avoiding
The mistake worth avoiding is coordinating services models once and assuming they stay coordinated. Architecture and structure change after services coordination — a wall moves, a beam deepens, a riser shifts — and coordinated services work silently becomes invalid unless clash detection re-runs and affected areas are flagged. The discipline is continuous re-coordination: model updates triggering fresh clash detection, affected services areas listed for review, and installation drawings regenerated from the current coordinated model, not from the last coordinated snapshot. A coordinated model is a moment in time, not a permanent state.
Frequently asked questions
Why do services clash so often?
Because mechanical, electrical, and plumbing systems compete for the same ceiling voids, risers, and plant spaces, and each system is designed by a different team.
What is a resolution workflow?
The process from clash to modelled solution: proposed fix, responsible modeller, approval, and verification in the updated model.
Why model maintenance access?
Because a system that fits but cannot be maintained fails in use. Coordination should check access and clearance, not just physical fit.
What happens when architecture changes late?
Clash detection re-runs and affected services areas are flagged, so coordinated work is rechecked rather than left silently invalid.
How much does it cost to build?
Cost depends on service count, project size, and drawing production depth. One service's coordination is far smaller than a full MEP platform, so confirm with a scoped quote.