Data center scheduling: connect commissioning to acceptance
Schedule data-center commissioning against the approved acceptance plan, power prerequisites, procurement dates, retest allowances and contractual float provisions.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 8 min
- Published
On this page
- The building is the small part
- Five levels of commissioning, five sets of activities
- Commissioning is a loop, so schedule it as one
- Map the power prerequisite for each test
- Know the scope before you trust the schedule
- Close every open end
- Manage float under the contract
- Detail: stop just short of the peak
- Plan time and cost together
- The constraint the schedule doesn't show: people
- A checklist before you trust a data center schedule
- Connect the sequence with the project understanding
From the outside, a data center looks like a large warehouse: a slab, walls, a roof. The shell is only part of the scope; the project’s testing and acceptance requirements also belong in the completion logic.
Define the contractual completion and owner acceptance criteria before building the schedule. Integrated systems testing can be a major readiness milestone, but passing a test called Level 5 does not by itself establish contractual completion, permission to occupy or readiness for every operating use. Identify the systems, operating modes, records and approvals the actual acceptance plan requires.
This guide covers what that means in practice: how commissioning should appear in the schedule, how power prerequisites affect the relevant tests, and the schedule-quality habits that keep a slip visible while there is still time to recover.
The building is the small part
Substantial completion and service readiness follow the governing contract and project criteria. On a data center, installation, startup, functional testing, integrated testing and handover need their own schedule logic rather than an assumption that the last installation activity closes the job.
Identify who buys switchgear, generators, UPS systems and chillers and obtain current supplier and purchase-order dates. Owner-furnished equipment can create interfaces the GC must schedule even where it does not hold the purchase order. A published market lead time is not a delivery commitment for the selected equipment.
Five levels of commissioning, five sets of activities
The following five-level structure is an illustrative way to organize activities. Terminology and boundaries vary; use the issued commissioning plan to define the actual stages, prerequisites and acceptance criteria. Schneider Electric’s commissioning guidance discusses planning, component tests and integrated-system testing; it is not a substitute for the project plan.
| Level | Where it happens | What it proves |
|---|---|---|
| L1 | At the factory | Each piece of equipment (switchgear, generators, UPS) passes factory acceptance testing |
| L2 | On site, on arrival | The equipment arrived complete and undamaged and matches what was approved |
| L3 | On site, installed | Each component starts up and runs on its own |
| L4 | On site, functional testing in this example | Verify the system’s specified sequences and performance; use the plan’s actual stage names |
| L5 | On site, integrated in this example | Test the specified cross-system responses and operating modes under the approved plan |
Identify who develops, reviews and accepts the commissioning plan under the project agreements. Bring the responsible parties into planning early, record the approved revision and manage changes through the designated process. The schedule should reflect that plan and any authorized revisions.
Two things follow for the schedule:
- L1 and L2 belong in the schedule even though they happen off site or on delivery. A factory test that slips, or equipment that arrives incomplete, moves everything behind it. Track factory test dates, ship dates and required-on-site dates as activities, not as notes in a procurement log.
- Integrated tests need explicit readiness gates. Identify the systems, completed preceding tests, safe operating conditions, approved power source and personnel required by each test script. A test may depend on several packages; do not substitute a blanket “all systems passed L4” rule for the actual plan.
Commissioning is a loop, so schedule it as one
Tests can reveal defects requiring investigation, correction and retesting. The approved scripts and design criteria establish the required response, including any fire-detection and suppression performance; this guide does not prescribe a universal detection window. A correction in one system can require affected integrated tests to be repeated.
A single commissioning bar can conceal that work. Include a project-specific retest allowance or recovery sequence, with a stated basis and the responsible parties available. Reassess it when defects are found rather than treating an invented standard duration as a commitment.
Map the power prerequisite for each test
Identify which tests need the permanent utility service and which can proceed at the factory or under another approved arrangement. Temporary or test power is not automatically equivalent to the intended operating configuration. The commissioning authority, electrical design, safety procedures and acceptance requirements must determine whether an arrangement is suitable. A late utility connection affects the tests that depend on it, not every preceding inspection or factory test.
The industry data puts power at the top of the list. In Turner & Townsend's 2025–2026 Data Centre Cost Index, 48% of respondents named power availability as the biggest obstacle to finishing on schedule.
In the schedule, that means the energization date should not be a milestone floating on its own. Tie it to every commissioning activity it feeds, and tie the electrical gear behind it (order, factory test, delivery, set, terminate, energize) to the energization date. When the utility date moves, the effect on L5 should be visible the same day.
Know the scope before you trust the schedule
A data center schedule can have thousands of activities. Reviewing it by reading activities one by one is slow, and it misses what is not there. The faster way is to study the drawings and the scope first, then read the schedule against them. Someone who knows what the job should contain sees quickly where the schedule does not match.
The work breakdown structure (WBS) is the first check. The WBS is the scope, broken down. If it is weak, some scope is either missing or mixed in with other work, and the field cannot follow it. A WBS that does not match the drawings is a scope gap, not a formatting issue.
Close every open end
A CPM schedule is a network of activities tied by logic. One hidden flaw to check is the open end: an activity with no successor, or with only a start-to-start tie and no finish tie.
An open-ended activity can slip again and again without moving a milestone or the longest path. The schedule looks healthy month after month while real work falls behind, and the delay only appears near the end, when it can no longer be recovered. On a data center, the end of the job is a chain of commissioning tests, so that late surprise lands where the schedule has the least room.
The fix is simple to state: activities need appropriate predecessor and successor logic, except legitimate network start and finish boundaries, and finish ties where the work actually depends on finishing. A three-week look-ahead is only as reliable as the network it is pulled from. With sound logic, the weekly check becomes meaningful: of the activities planned three weeks ago, how many are done, how many are not, and why.
Manage float under the contract
Float is the most valuable thing a schedule has. It is the buffer that absorbs the problems every project has. It is also easy to use up quietly. Sometimes a party hides it, sometimes it is consumed by work that slipped without anyone deciding to spend it, and sometimes the owner never sees it at all.
The contract governs float allocation and related rights. As a management practice, make available float and its consumption visible in each update and record the cause; that reporting does not change contractual entitlement. When float disappears and nobody can explain it, the project has lost its buffer without making a decision.
Detail: stop just short of the peak
How detailed should a data center schedule be? Detail helps on a complex job, up to a point. Past that point it becomes cumbersome: updates take longer, the field sees it as micromanagement, and the activities that matter get buried among the ones that don't. A good rule is to stay a little short of the peak. Model the work at the level the team actually manages it, and put the extra detail into the look-ahead, where it is used.
Plan time and cost together
On many projects the schedule is still developed after the estimate, and then maintained separately. On a data center that split is expensive. Linesight notes that the baseline schedule is often set at 10–30% design and "rarely revisited unless a delay occurs", while the cost plan is refreshed at each design stage. Their conclusion is that you cannot control cost without controlling time.
The connection is direct. One procurement date drives escalation, storage, extended general conditions and damages exposure at the same time. When that date moves, both the schedule and the estimate should move with it. We cover the cost side in On a data center, the schedule is part of the estimate.
The constraint the schedule doesn't show: people
A schedule can run activities in parallel only if there are crews to staff them. On data centers, especially in remote markets, crews are often the real limit. Prefabrication helps, but only part of the work can move off site. Remote sites may need worker housing. Compressed deadlines lead to long shifts and fatigue, and some contracts now include minimum rest periods.
Resource-load the peak of the schedule, especially electrical and commissioning, and check it against the crews that can actually be on site in that window. That is why we treat subcontractor coverage on a data center as crews who can staff the peak, not as proposals received.
A checklist before you trust a data center schedule
- Are completion and acceptance criteria defined? Include the required commissioning stages, tests, records and approvals under the actual plan. The cost side is in our guide to pricing L1–L5 commissioning in bids.
- Is there time for failed tests? Re-test loops should be activities with durations and ties, not hope.
- Is the power date tied in? Energization should drive every commissioning activity it feeds, and the electrical gear should drive energization.
- Does the WBS match the drawings? Missing or mixed scope shows up here first.
- Are there unintended open ends? Check appropriate logic while recognizing legitimate network start and finish boundaries.
- Who is using the float? Report it, and record why.
- Do time and cost move together? When a long-lead date moves, the estimate should move with the schedule.
- Can the peak be staffed? Check the crews behind the parallel work.
When the estimate depends on staged completion, the construction-phasing review identifies repeated setup and handback work. If the proposed calendar includes restricted shifts, the night-work estimating guide separates the usable work cycle from a generic labor premium.
Connect the sequence with the project understanding
Most of the checks above start before the schedule exists: knowing the scope from the drawings, knowing which equipment is owner-furnished and when it is due, knowing which commissioning responsibilities each proposal covers. That knowledge usually sits in different documents and different people's heads, and the schedule and the estimate drift apart because nothing connects them.
Piper is the AI operating system for preconstruction. It maintains one understanding of the project across the drawings, specifications, equipment lists, proposals and the estimate. When a delivery date, a commissioning requirement or a design revision changes, Piper traces which scopes, bidders and cost lines depend on it, with the source behind each. Piper can support a draft preconstruction schedule from provided documents. Inspect the source references, missing assumptions, activity coverage and proposed logic before use; the scheduler owns the accepted logic and the team decides how to price the risk. See AI preconstruction scheduling.
FAQ
What are the five levels of data center commissioning?
The illustrative structure here is factory testing, delivery inspection, startup, functional testing and integrated systems testing. Stage names and boundaries vary. Use the actual commissioning plan to define the equipment, systems, operating modes and prerequisites tested at each stage.
When is a data center considered complete?
Apply the contract’s completion provisions and the owner’s acceptance criteria, including required tests, documentation and approvals. Integrated systems testing can be a major milestone, but its label alone does not establish completion or permission to operate.
What is an open-ended activity in a CPM schedule?
Check for unintended missing dependencies and for activity finishes left unconstrained where the actual work requires a finish dependency. Legitimate network start and finish boundaries are exceptions. Defective logic can prevent a delay from reaching the affected milestone; review the actual network rather than treating every start-to-start relationship as invalid.
Why does permanent power drive the data center schedule?
Permanent power can be a critical prerequisite for specified operating and integrated tests. Factory tests and some earlier checks can occur before utility energization. Identify the approved power configuration and readiness gate for each test instead of making every stage depend on the same date.
Where this fits in Piper
Scheduling
Draft a CPM preconstruction schedule from the project documents, with every activity linked to its source, and hand it off in P6 or Microsoft Project format.
Related reading
Commissioning is scope: pricing L1–L5 in data center bids
Data center commissioning is priced scope: crews, load banks, fuel, OEM support and re-tests at every level. How to carry it before sub bids leave it out.

On a data center, the schedule is part of the estimate
On a data center one procurement date drives escalation, storage, general conditions and damages. Why precon should price schedule and cost as one risk.

Leveling bids when the owner buys the equipment
On an OFCI data center, an electrical bid prices custody steps, not gear. How to level each owner-furnished item from receiving to integrated testing.

Before you carry a data center number: a precon checklist
Ten questions a GC precon team should answer before carrying a data center number: owner gear, redundancy, commissioning, liquid cooling, schedule and subs.

Data center precon is not commercial precon with more power
On a data center the risk leaves the building and moves into owner-furnished gear, commissioning, and a schedule set by power. What changes for GC precon.

Bid coverage when only a few subs can do the work
On data center MEP packages the subs are choosing their GCs too. Why coverage means crews at the peak, not names on a list, and how to level with two bids.

Who owns the liquid cooling connection on a data center?
Liquid cooling adds three loops and three owners. The gap sits between facility water, the CDU and the rack: hoses, valves, flushing, fluid and leak detection.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.