OCCUPIED-SITE PROJECT PLANNING

Retrofitting an Operating Data Center for Liquid Cooling: A Phased Plan

A final layout can look complete while the route to it remains unresolved. Plan what the room must support between today’s installation and the last liquid-cooled rack.

Airplex Mechanical resources Reviewed November 16, 2026

Start here

How should an operating data center plan a liquid-cooling retrofit?

Define each intermediate operating state before committing to a rollout. For every phase, identify the IT that remains active, the cooling it still needs, the proposed change and the evidence required to advance. Give each prerequisite and acceptance decision a named owner. A first deployment establishes evidence for its own scope; expansion needs a fresh review of the next operating state.

Start with operating states, then add dates

Write a short description of the room today, the first proposed deployment, the mixed installation and the intended expansion. A stage description should let an IT lead and a facilities lead agree on what is running and what remains dependent on existing cooling. A date alone cannot do that.

Vertiv’s retrofit roadmap calls for reviewing existing infrastructure, modeling a hybrid arrangement and considering disruption to current workloads. Schneider Electric’s brownfield article likewise describes staged deployment within existing physical and infrastructure constraints. The phase register below is an original planning aid built around those considerations; it is not either vendor’s prescribed construction sequence.

An example set of planning states; the actual project may need different stages
StateWhat the plan must describeDecision before advancing
Existing operationActive IT and its current cooling dependenciesIs the baseline understood by IT and facilities?
Enabling workWhat can be prepared while current operation continuesAre the affected systems, access and work boundaries agreed?
First liquid-cooled deploymentThe exact initial configuration plus retained equipmentWhat evidence will establish acceptance of this limited phase?
Mixed operation and expansionThe next IT configuration and all retained cooling dutiesWhich assumptions change before the next rack group is added?

References: [1] [2]

Give each phase a clear boundary

Name the racks or equipment group covered by the phase without putting confidential facility detail in a public inquiry. Record whether that group is new, replacing existing IT or temporarily overlapping it. During an overlap, a retirement planned for next month is not a reduction available today.

Beside the new work, list the cooling that the operating state retains. Include equipment serving unconverted IT and any air duty associated with the selected liquid-cooled configuration. Use the separate residual-air evidence guide to establish that duty; this phase plan records when the evidence is needed and who accepts it.

Ask the project lead to identify changes that trigger another review: a different server configuration, another rack group, a revised heat-rejection arrangement or a delayed retirement. Keep these triggers beside the phase they affect, where they can inform the schedule.

Turn assumptions into named prerequisites

A useful dependency has three parts: the information needed, the party providing it and the decision waiting on it. Replace “building water available” with a reference to the facility information requested by the responsible designer. Replace “vendor ready” with the specific submittal, review response or attendance confirmation needed for that phase.

For a leased NYC or Northern New Jersey property, add landlord-controlled systems, equipment delivery routes and permitted work windows to the discussion. Ask the building representative which arrangements apply to this site. Do not assume a tenant’s IT purchase also secures access to the building’s mechanical systems.

The Open Compute Project (OCP) liquid-distribution guidance discusses route planning, equipment placement and maintenance access. Treat delivery access and later service access as separate review questions: getting an item into position does not document how the components will be maintained or replaced.

  • IT supplier: identify the configuration and the document governing its cooling requirements.
  • Facilities and designer: identify the evidence needed for the proposed receiving system.
  • Building representative: resolve access, work-window and shared-system questions.
  • Project acceptance owner: list the records required before releasing the next phase.

References: [3]

Worked example: the second phase changes the question

Consider a fictional room with eight existing air-cooled racks. The proposal adds two liquid-cooled racks in Phase A, then adds two more and removes four original racks in Phase B. These counts explain sequencing only; they imply no heat load or cooling capacity.

Phase A’s planning state includes all eight original racks and both new racks. Its evidence package therefore cannot assume the four later retirements have already happened. Phase B must distinguish the period before removal from the period after removal if the activities do not coincide.

Suppose the retirement date moves but the second delivery remains fixed. The phase owner marks the dependency unresolved and asks for review of that revised overlap. Acceptance of Phase A is still useful evidence, but it does not establish that the changed Phase B is supported. This is the decision the register should expose before the schedule becomes a commitment.

Define what acceptance will prove

Agree on the acceptance record before the phase is procured. Ask what configuration it will cover, what conditions will be documented and who can accept the result. Keep unresolved items visible with their effect on the next decision.

At handover, preserve the phase’s actual configuration alongside its supporting records. A proposed future connection, reserved space or unopened expansion package should remain identified as future work. That gives the next project team a reliable starting point without turning the first phase into a promise about every later deployment.

Put this guide to work

Liquid-cooling phase and dependency register

Fill one row per operating state. Add a document reference and named person wherever possible. Split a phase into separate rows if the overlap state differs from its completed state. Blank fields are yours to complete.

Open each item to add your notes, then download the CSV to keep a copy. This tool does not save or submit your entries; do not rely on your browser restoring them.

Existing operation
Existing operation
Enabling work
Enabling work
First deployment
First deployment
Mixed operation
Mixed operation
Next expansion / retirement
Next expansion / retirement

Continue with a related decision

Questions & answers

Does a phased retrofit guarantee uninterrupted operation?

No. Phasing describes how the project is divided. Whether work can occur while particular systems remain active depends on the site, proposed work and authorized operating plan. Ask the project team to document each phase’s constraints and any required interruption before accepting the schedule.

What should we bring to the first planning conversation?

Bring the proposed IT configuration, the current cooling arrangement, the intended deployment stages and the decision you need to make next. Identify who controls the relevant building systems and records. Detailed facility documents can follow through the agreed project channel; the initial inquiry can describe the need without sensitive drawings.

Can a successful first rack establish the design for the full room?

It provides evidence about the configuration and conditions actually accepted. The expansion review must identify what changes, including equipment quantities, retained duties and supporting-system assumptions. Record which first-phase evidence remains applicable and which information the next phase still needs.

Sources & technical references

  1. Vertiv: How to implement liquid cooling at existing data centers

    Public roadmap reviewed November 16, 2026 for site audit, hybrid planning and operating impacts. Vendor guidance; no performance or schedule promises adopted.

  2. Schneider Electric: Brownfield data center modernization for AI

    February 26, 2026 vendor article; existing-facility constraints and phased deployment context. Reviewed November 16, 2026.

  3. OCP: Data Center Liquid Distribution Guidance & Reference Designs

    Revision 1.0, January 8, 2024; route, placement and access planning. Reviewed November 16, 2026; not a site design.

NYC & Northern New Jersey

Bring the next phase into focus

Airplex Mechanical’s Critical Cooling Division can discuss the mechanical scope for your NYC or Northern New Jersey facility. Share the proposed stage, equipment and unresolved dependency so the next conversation addresses the decision in front of you.

Discuss a liquid-cooling retrofitCall (347) 627-7146
Call Now Request Service