Data Centre Commissioning Levels Explained: L0 to L6
Every commissioning programme moves through the same five levels, in the same order, for the same reason — each one catches a category of problem the level before it couldn't. Here's what actually happens at each stage.
Why levels exist at all
A data centre isn't tested once. It's tested repeatedly, at increasing scale, from the smallest component through to the whole facility operating under failure conditions. That progression exists because problems are dramatically cheaper and safer to catch early — a fault found on a single piece of equipment in a factory is an inconvenience; the same fault found for the first time during integrated testing, with the whole facility live, is a serious problem.
The levels are the structure that enforces this. You don't move to the next level until the current one is genuinely complete — that discipline is exactly what a hold points matrix exists to enforce. Most frameworks use a seven-stage structure running from Level 0 through Level 6, with a colour-coded tag physically attached to equipment at each of the five tested stages.
The levels
Design & Planning
Before any physical testing begins, Level 0 establishes the Owner's Project Requirements (OPR) and reviews the foundational design against them. Nothing is tagged at this stage — it's a documentation and design-review gate, not an equipment test.
Factory Acceptance Testing (FAT)
Major equipment — generators, UPS modules, switchgear, transformers — is tested at the manufacturer's plant before it ever ships to site. Confirming it performs to specification here is far cheaper than discovering a fault after installation.
Site Acceptance & Pre-Installation
Once equipment arrives on site, Level 2 inspects it for shipping damage and verifies correct physical installation, wiring, and piping — without power applied. This is the gate that confirms equipment is safe to energise for the first time.
System Start-up (Smoke Test)
Equipment is energised for the first time. Motor rotations are checked, basic interlocks and alarms are verified, and the system is confirmed safe to move beyond a simple start-up condition. This is a lighter-weight check than full functional testing — it's specifically about proving the system starts up safely, not that it performs correctly under load.
Functional Performance Testing
Now the system is tested dynamically, under real operating conditions — load banks simulate full capacity, and component failure scenarios are run to confirm the system performs correctly, not just that it starts safely. This is the level with the most individual test scripts, since every distinct piece of equipment across electrical, mechanical, controls, fire & life safety, and security gets its own functional test.
Integrated Systems Testing (IST)
Systems that passed individually at Level 4 are now exercised together, executing a full-facility "black building" test — simulating total utility power loss to prove generators and UPS systems maintain operations seamlessly. This is where a facility's actual resilience gets proven, not assumed.
Closeout & Handover
Documentation is finalised, the operations team is trained, and outstanding items are closed or formally deferred. This culminates in a signed handover certificate — the formal record that the facility is ready for operational responsibility to transfer.
Worked example: where a fault gets caught, by level
The same underlying problem looks different depending on which level catches it:
| Level | What might be caught | Cost/risk if missed here |
|---|---|---|
| L1 — Factory | A UPS module with an internal wiring fault | Cheap — corrected before it ever leaves the factory |
| L2 — Pre-Installation | A loose cable termination on a switchboard | Moderate — caught before energisation, no equipment damage |
| L3 — Start-up | Incorrect motor rotation on first energisation | Low — caught immediately, before any load is applied |
| L4 — Functional | A generator that doesn't reach rated voltage under load | Moderate — caught in isolation, doesn't affect other systems |
| L5 — Integrated | A cooling system that doesn't fail over correctly under real load | Severe — this is the resilience the whole facility depends on |
| L6 — Handover | Missing as-built documentation the ops team needs | Operational — facility works, but is harder to run and maintain |
Frequently asked questions
What are the commissioning levels L0 to L6?
L0 to L6 describe the progressive stages a data centre goes through before handover: L0 is design and planning, L1 is factory acceptance testing, L2 is site acceptance and pre-installation, L3 is system start-up, L4 is functional performance testing, L5 is integrated systems testing, and L6 is closeout and handover. Colour-coded tags — red, yellow, green, blue, and white — are physically attached to equipment at levels 1 through 5.
What is Level 4 commissioning?
Level 4, functional performance testing, tests a system dynamically under real operating conditions — load banks simulate full capacity and component failure scenarios, confirming the system performs correctly, not just that it starts up safely.
What is the difference between Level 3 and Level 4 commissioning?
Level 3 is a lighter-weight check confirming a system starts up safely — correct motor rotation, basic interlocks and alarms. Level 4 goes further, testing the system dynamically under real load and failure scenarios to confirm it actually performs to its design intent, not just that it switches on correctly.
Can you skip a commissioning level?
No, not without real risk. Each level exists to catch a specific category of problem before it becomes expensive or dangerous to fix. Skipping site acceptance and going straight to system start-up, for example, risks energising equipment that was never confirmed correctly installed in the first place.
A full Level 4 test script library, ready to use
Hold Point includes 28 functional performance test scripts across electrical, mechanical, controls & monitoring, fire & life safety, and security — each with a worked example, not just a blank form. Sits alongside the hold points matrix and the CIP that ties the whole programme together, in the same folder structure throughout.
See the toolkit