What data centre fit-outs demand from a coordination model that hospitals don't.
Back to Blogs
Digital Engineering 11 minJan 2025

What data centre fit-outs demand from a coordination model that hospitals don't.

Neutec Digital Engineering Team

Cooling redundancy, cable containment density, and commissioning sequencing push data centre coordination into territory most BEPs were never written for.

Data centre coordination has its own vocabulary, and a BEP written for a commercial office or a healthcare facility will not map onto it cleanly. The physical differences between a hyperscale data hall and most other building types — ceiling-to-floor heights measured in metres, cooling infrastructure that doubles back on itself for redundancy, cable containment densities that are an order of magnitude higher than standard commercial fit-outs — create coordination challenges that standard MEP workflows are not designed to handle.

Cooling redundancy is the most significant. A Tier III data centre requires that any single cooling component can fail without affecting the facility's operation. That means every cooling circuit has a parallel path, every CRAC unit has a backup, and every supply and return air path is duplicated. Coordinating that redundant infrastructure in a model without creating an unnavigable tangle of overlapping services requires a specific approach to system grouping and clash tolerance settings.

Cable containment in a data centre is another category entirely. The volume of structured cabling, power distribution, and fibre in a large data hall would be physically impractical to model at the same level of detail as MEP services in a commercial building. The coordination approach has to define which elements are modelled geometrically, which are represented as zones, and how those zones interact with the structural and architectural elements around them.

Commissioning sequencing is the third area where standard coordination practice falls short. Data centres are typically commissioned in phases — a hall that is operational before the rest of the building is complete. The federated model needs to reflect that phasing, with isolation points, temporary service connections, and commissioning interfaces modelled as explicit elements rather than left as site decisions.

We write a project-specific coordination protocol for every data centre engagement, separate from the main BEP, that addresses these three areas in detail. It is the document that the M&E contractor's site team actually uses during construction, and it is written to be read by someone who has not been part of the BIM process from the beginning.

N

Neutec Digital Engineering Team

Neutec · Jan 2025

LET'S MODEL THE BUILT WORLD ·LET'S MODEL THE BUILT WORLD ·LET'S MODEL THE BUILT WORLD ·LET'S MODEL THE BUILT WORLD ·LET'S MODEL THE BUILT WORLD ·LET'S MODEL THE BUILT WORLD ·

Have 

Tell us what you’re building. We’ll show you how we’d approach it.

Start a Project