On a data center, ready for service is decided in the last ninety days. That is where commissioning lives, and on too many schedules it is a single bar near the end called Commissioning. When the electrical work runs late, that bar gets shorter on paper. The tenant walkthrough does not move, and nobody asks how a test script that takes six weeks now takes three.
The fix is not more float at the end. It is putting every level of commissioning into the network as real activities with real logic, so the schedule tells the truth when upstream work slips.
The five levels, as schedule work
- Level 1: factory witness testing. Switchgear, UPS, generators and cooling units tested at the factory before they ship. Each test is an activity tied to the release and the ship date. Miss one and delivery moves.
- Level 2: delivery and installation checks. Receipt inspection, setting and installation verification. These tie to the area ready dates and to the crane and rigging plan.
- Level 3: startup. Vendor startup of each component. Most of it needs permanent power, so it must tie to energization, not to an assumed temporary power plan.
- Level 4: functional performance testing. Each system tested on its own against design intent. Durations come from the scripts and the count of components, not from a guess.
- Level 5: integrated systems testing. The whole hall under load, with failure scenarios and transfers. It cannot start until every Level 4 it depends on is done, and it needs load banks, witnesses and controls integration in place.
How we build it
- One commissioning fragnet per system per hall, built from the commissioning agent's script list.
- Durations derived from script count and crew capacity, so a compressed duration has to be explained.
- Load banks, test teams and owner witnesses loaded as resources, because they are shared across halls and they run out.
- Controls integration for the BMS and EPMS as its own path. It is the most common late surprise in Level 5.
- Tenant acceptance and ready for service after Level 5, with their own durations and conditions.
What to measure
Track scripts executed and passed against plan by level and by system, plus the open issues log from testing. A burn-down that flattens in Level 4 is the earliest warning you will get that the ready-for-service date is in danger. Then run a risk analysis on the commissioning durations themselves. They are among the most uncertain on the job.
A data hall is not finished when the gear is set. It is finished when it has been proven under load, and that takes the time the scripts say it takes.
Senior scheduler, AdenTurton
Data center and infrastructure construction is where our founder built his career, and it shapes how we control this market. See our data center work, or test your own ready-for-service date in Finish-Date Confidence. For a full campus, start with integrated master scheduling.
