Coordination between MEP and architecture is critical to avoid cost overruns, delays, and rework. Effective BIM workflows, grounded in ISO 19650 and LOIN principles, ensure every model element is accurate, usable, and ready for the next project stage.
“Coordination is not about prettier models—it’s about delivering actionable information that drives decisions and prevents costly errors.” – Senior BIM Manager
Section
Why MEP-Architecture Coordination Matters
- ▹Prevent Clashes: Hidden conflicts between ducts, pipes, and walls can cause major delays.
- ▹Increase Efficiency: Streamline decision-making and reduce RFIs.
- ▹Lifecycle Benefits: Coordinated models enable FM and long-term asset management.
- ▹Compliance: Align with ISO 19650 and contractual requirements.
Section
Common Challenges
- ▹Spatial conflicts between MEP systems and architectural elements.
- ▹Misaligned data: parameters and attributes not synchronized.
- ▹Late clash detection, discovered only during construction.
Section
Authoritative Strategies for Coordination
1. Define Authoring Zones
- ▹Assign model responsibilities per discipline and building zone.
2. Use a Common Data Environment (CDE)
- ▹Maintain a single source of truth with version control and audit trails.
3. Adopt Level of Information Need (LOIN)
- ▹Define geometry, parameters, and documentation per phase rather than relying solely on LOD.
4. Implement Clash Detection Protocols
- ▹Schedule automated clash detection at key milestones.
- ▹Prioritize high-risk clashes for early resolution.
5. Conduct Regular Coordination Workshops
- ▹Weekly or biweekly sessions to review models and resolve conflicts collaboratively.
6. Link Parameters to Documentation
- ▹Embed specs, O&M manuals, and COBie-ready metadata directly into MEP objects.
Section
Measurable Outcomes
- ▹60% reduction in clashes detected late in construction.
- ▹80+ hours saved in manual coordination across multiple disciplines.
- ▹Optimized Revit performance by reducing unnecessary geometry.
- ▹Improved decision-making: LOIN ensures every modeled element serves a purpose.
Section
Lessons Learned / Pitfalls
- ▹Equating LOD with LOIN: Detailed models aren’t always useful.
- ▹Ignoring metadata: Models must support FM and lifecycle management.
- ▹Delaying coordination: Early integration prevents costly errors downstream.
- ▹Overcomplicating models: Only include information relevant to each phase.
Section
Internal Links
Section
External References
- ▹UK BIM Framework Guidance
- ▹ISO 19650-1: Concepts & Principles
- ▹BS EN 17412-1: Level of Information Need
End of technical report.
Return to Index