Fast-track data centre programmes overlap design, procurement and construction because the energisation date will not wait. That overlap is a choice. It only works if one schedule says which design release, which factory slot and which test unlocks the hall. When several organisations each keep a date, the programme fails in a familiar way: everyone is on programme against their own file, and the building does not take power.
Three dates for one energisation
On a typical fast-track job the owner, the main contractor and the equipment vendors are not lying. They are answering different questions.
- The owner date is the megawatt commitment, often phased by hall or by data suite.
- The contractor date is practical completion of the building and the installed systems they hold.
- The vendor date is ex-works or delivered, not installed, and not tested.
Without a single schedule owner, those dates sit in three trackers. The monthly meeting subtracts them by eye. A slipped switchgear slot is described as a procurement issue until the month it becomes the critical path, which is often the month commissioning was supposed to start.
What fails when nobody owns the network
The shell can be watertight while the power path is late. Transformers, generators, switchgear, cooling plant and controls have long factory durations. They are not a lag on a construction bar. If nobody owns the logic from order, through inspection and freight, into the plant room and then into integrated systems testing, the hall is finished in the architectural sense and unfinished in the only sense the client bought.
Phasing makes this worse. The first hall consumes the commissioning team, the vendor start-up engineers and the access the second hall needed. A schedule that shows one energisation milestone for the campus hides that theft of float. Each hall needs its own path, and someone has to refuse a date that borrows resource the first hall has already used.
Design on a fast-track job is released in packages. The schedule owner is the person who ties a package to the site activity it releases, and who says when a missing release is on the path. If that link lives in an email, the contractor will install what they have and discover the clash in the plant room.
What a single schedule owner actually does
The title is not a status. It is a duty. One person, or one controls seat that cannot be split, holds the integrated file and is allowed to say that a reported date is not accepted until it is in the network.
- One data date for the owner, the contractor and the vendors that affect the path.
- Procurement activities for long-lead electrical and cooling plant, not a single procurement bar.
- Commissioning as stages: component, system, and integrated tests, each with a predecessor.
- Coding by hall, system and contractor, so a filter is not a second schedule.
- A rule that a tracker date which is not in the file is not the date.
The owner of the schedule is not required to know every lug size. They are required to know which activity moves energisation, and to make the package managers update that activity rather than a side list.
Why fast-track makes the gap fatal
On a traditional building there is sometimes time to reconcile three programmes before handover. A data centre burns that time on purpose. Design and construction overlap because the plant will not arrive sooner if you wait for a complete model. The overlap is safe only while the missing information is an activity with a date. It is unsafe when each party assumes another party is holding the logic.
Fast-track also multiplies interfaces: utility connection, landlord shell, specialist MEP, controls, and the client fit-out of the IT space. Any one of them can hold the megawatt date. A single owner is how those interfaces stay in one critical path instead of becoming a dispute about whose milestone was the real one.
How to put an owner in place before the next gate
Name the seat in the project execution plan, not in a RACI that nobody opens. Give that seat the right to reject a progress report that does not trace to the integrated schedule. Put the energisation path on one page the sponsor can read: the plant that is late, the test that cannot start, the hall that is still honest.
Then walk the path with the people who own the plant and the tests. If they cannot see their work in the file, you do not have a schedule owner. You have a planner maintaining a drawing of a programme that lives somewhere else.
EVM Solutions plans data centre programmes this way: one network from design freeze and factory slots through installation and staged commissioning, coded so each hall can be reported without a second file. The point of the owner is not more reporting. It is one date the hall can actually meet.
