Blog

How Do You Commission a Data Centre? The Five Levels Explained

Data center projects don’t fail in the slab pour or the steel frame. They fail in the last 20%. Roughly 76% of data center builds face construction delays, and only around 12% finish on time. The reason is rarely a single bad decision. It is the slow compounding of small commissioning dependencies that no one mapped early enough.

So, how do you commission a data center? At its core, commissioning is the structured process of testing, validating and documenting every system in the facility against the owner’s design intent – from factory acceptance through to integrated systems testing under simulated failure. It is the gate between construction and energisation.

The industry has settled on a five-level framework to govern it. But the framework is not the hard part. This article covers what each level requires, and what the Mechanical Completion gate, the one most teams get wrong, actually means.

What is data center commissioning?

Data center commissioning is the technical assurance process that proves a facility performs as designed, under load and under failure conditions, before the operator takes the keys. ASHRAE defines it as the quality-oriented process for achieving, evaluating and documenting that the performance of buildings, systems and assemblies meets defined objectives and criteria.

In a commercial office, commissioning is a checklist. In a data center, it is the project. A typical hyperscale build will spend more time and budget on commissioning than on the entire structural package. Every component is tested, then every system is tested, then every system is tested in concert with every other system, under fault. The output is not a punch list. It is a defensible technical record that the asset works.

Visibuild’s commissioning management software is built specifically for this environment, connecting the quality evidence captured throughout construction to the record commissioning teams need when it counts.

The five levels of data center commissioning

The industry standard framework, broadly aligned with ASHRAE Guideline 0 and used across BCxA and BSRIA practice, breaks commissioning into five sequential levels, commonly labelled Cx1 through Cx5. Each is a gate. Work cannot move forward until the previous gate is signed off.

 

Level Activity Lead Outcome
Cx1 Factory Acceptance Testing (FAT) Vendor + CxA witness Equipment proven at the manufacturer before shipment
Cx2 Site delivery and pre-installation inspection General Contractor & Subcontractor Equipment received, inspected, installed per drawings
Cx3 Pre-commissioning and energisation General Contractor & Subcontractor Static checks, point-to-point, first power-up, SAT
Cx4 Functional performance testing CxA-led, General Contractor support Each system tested under load and across operating modes
Cx5 Integrated Systems Testing (IST) CxA Owner All systems tested together under failure scenarios

 

The colour-tag system most major operators use – red, yellow, green, blue, white, is a visual overlay of these gates. A piece of equipment carries its tag from Cx1 through to Cx5. If a Cx4 fault throws it back, the tag comes off and the gate is reopened. Every reopened gate costs days.

Mechanical Completion: the gate inside the gate

What sits between Cx2 and Cx3, but rarely gets named clearly on a programme, is Mechanical Completion (MC). MC is the formal handover gate at which the General Contractor declares a system statically complete, safe to energise, and ready for the commissioning team to take care, custody and control. It is signed off through:

  • ITR-A check sheets: installation and static checks signed by the trade

  • ITR-B check sheets: pre-energisation checks signed jointly with the Cx team

  • MCSSAC: the Mechanical Completion Sub-System Acceptance Certificate that formally transfers the system

It carries a three-tier punch list: A-list items must be closed before MC is granted, B-list before commissioning is complete, C-list items can roll into the defects period after handover.

Two distinctions matter here.

1. MC is not the same as Substantial or Practical Completion.

MC is a technical gate inside the construction-to-commissioning interface. Substantial Completion (US) and Practical Completion (UK, Ireland, Australia) are contractual milestones tied to beneficial occupation, retention release and start of defects liability, they sit downstream of Integrated Systems Testing. Conflating the two is what causes the “we’ve reached PC but the BMS is still alarming” arguments at handover.

2. MC must be granted system-by-system, not facility-wide.

Best practice is to break MC down by sub-system – each generator string, each chiller line, each UPS module, each electrical room, so the Cx team can start Cx3 on the first chiller while the last generator is still in Cx2. Treating MC as a single facility-wide milestone is one of the most common causes of late commissioning starts on hyperscale projects.

This is exactly the kind of complexity that Visibuild’s commissioning workflows are built to handle, tracking readiness by system and sub-system, not by location alone.

The framework looks linear. It isn’t.

The thing that makes commissioning hard is not the sequence within a single system. It is the dependencies between systems, the way power has to be at Cx4 before mechanical can leave Cx2, the way the BMS has to be substantially live before chillers can complete Cx3.

Those dependencies are covered in depth in the next article in this series: “The Data Center Systems That Derail Commissioning, and Why Controls is the Real Risk”.

For a broader view of how Visibuild supports data center construction teams across every stage of the build, see how teams like Kapitol manage QA across live hyperscale projects.

Ryan Treweek

Co-founder & CRO

With 17 years of experience at Tier 1 contractors like Multiplex and Icon, Ryan has worked on landmark projects including Upper West Side, Prima Tower, Epworth Hospital, and Australia 108. Having seen how quality directly impacts project outcomes, margins, and client relationships, he recognised that improving quality isn’t just a site issue, it’s a business imperative. As a co-founder of Visibuild, Ryan brings a commercial lens to quality management, helping construction companies turn process reliability into stronger performance, profitability, and trust across every project.

Frequently Asked Questions

The five levels of data center commissioning

What is data center commissioning?

Data center commissioning is the structured process of testing, validating and documenting every system in a facility against the owner’s design intent, from factory acceptance through to integrated systems testing under simulated failure. It is the technical gate between construction and energisation.

What are the five levels of data center commissioning?

Cx1 is factory acceptance testing of equipment before delivery. Cx2 is site delivery and pre-installation inspection. Cx3 is pre-commissioning and first energisation. Cx4 is functional performance testing of each system in isolation. Cx5 is integrated systems testing, where every system runs together under load and under simulated failure.

What is Mechanical Completion in a data center?

Mechanical Completion (MC) is the formal, system-level gate between construction and pre-commissioning. The Contractor certifies that a system is statically complete, ITR-A and ITR-B checks are signed, and the system is safe to be energised for Cx3 pre-functional testing. It transfers care, custody and control from the Contractor to the commissioning team via a Mechanical Completion Sub-System Acceptance Certificate (MCSSAC). MC is not the same as Practical or Substantial Completion, which are contractual milestones tied to handover and retention release.

Why does MC need to be granted system-by-system?

Granting MC as a single facility-wide milestone forces the commissioning team to wait for the slowest sub-system before starting work on anything. Sub-system MC, per generator string, chiller line, UPS module and electrical room, allows the Cx team to begin Cx3 on completed systems while others are still in Cx2, protecting the commissioning schedule.