Retrofitting Air-Cooled Facilities for Liquid

The building you are retrofitting was sized for a different physics: 3 to 7 kW racks on a raised floor, air handlers tuned to a 1.4–1.6 PUE, an electrical bus engineered for a power density that a single GB300 NVL72 rack now exceeds by 20x. The retrofit question is never 'can liquid cool this hardware' (it can); it is 'what does this building let me do before one of its original constraints runs out.' Over 60% of enterprise data centers are more than seven years old (DCD, 2025) — air-era stock that predates AI-class power density and cooling — and many of those same halls have a decade-plus left on their leases, which is precisely why the retrofit market exists at all rather than everyone simply building new.

The decision runs in the order the building forces on you. The brownfield assessment inventories the four fixed quantities before any capital is committed. The retrofit paths then rank by disruption, because in a live hall the cost that matters is downtime per rack and risk to the racks already earning, not capex per kW. Phased migration through mixed air-and-liquid operation is where the hardest engineering sits: keeping a half-converted hall thermally and electrically stable while you commission charged piping over running equipment. Last comes the stranded-capacity math — the power-versus-cooling-versus-floor reconciliation that tells you how much of the building you actually made usable, and how much you paid to leave empty.

Every retrofit feasibility study reduces to four inventories, and a candidate building passes only if it clears all four — they are an AND, not an OR. Miss any one and that constraint becomes your density ceiling no matter how generous the other three are. The discipline is to find the binding constraint before design, because the binding constraint determines whether you are buying a liquid-capable AI hall or merely a more expensive air hall.

Floor loading is the constraint that fails most retrofits, and the one that is least negotiable, because it is structure, not equipment. A legacy raised floor is commonly rated around 150 lb/ft² (≈730 kg/m²); a GB200 NVL72 weighs about 1.36–1.50 t (3,000–3,300 lb wet; HPE's filled profile is 3,245 lb) over the 0.64 m² of a 600 × 1,068 mm cabinet. Dividing mass by cabinet area gives an ~2,100–2,300 kg/m² footprint-average screen, not a point load and not an access-floor acceptance comparison. Obtain the OEM foot/wheel and rolling reactions, then verify them like-for-like against the complete panel, pedestal, stringer, slab, and move-route ratings. The fixes — steel load-spreading plates, removing the raised floor and landing racks on the structural slab, or post-tensioned slab reinforcement at roughly $200/ft² with facility downtime — are costly and slow precisely because they are civil work in an occupied building. Wet weight (coolant-filled cold plates, manifolds, charged in-rack piping) and the seismic restraint of charged pipe push the number higher still. → the structural basis is engineered in Chapter 6.2.

Plenum and distribution volume is the second. A raised-floor plenum that was an air path is now a contested corridor: it must carry coolant supply/return mains, CDU connections, and leak-zoning drainage, while it is often already congested with decades of legacy power and data cabling. A slab-on-grade hall with no plenum forces overhead pipe racks and a different leak-containment geometry. The plenum question decides where the CDU lives (in-row, end-of-row, perimeter gallery), how the secondary loop is routed, and whether liquid distribution competes with the residual air cooling you still need for the ~10–20% of rack load that stays air-cooled. → spatial planning for liquid in Chapter 6.1.

Electrical headroom is the third, and it is frequently the true ceiling. A hall sized for 5 kW racks has a bus, transformers, switchgear, and PDU topology to match. Liquid does not reduce the IT load — it removes the chiller and CRAH penalty, but the racks themselves draw 20–100x more. If the upstream feed, the busway ampacity, or the available UPS capacity caps out at, say, 8 MW, then you can cool far more density than you can power, and your retrofit is power-bound the moment the cooling works. The worst version of this is the retrofit that succeeds thermally and then strands half the floor because there is no megawatt left to energize it. → the power chain in Chapter 4.5; the binding-constraint framing in Chapter 1.1.

Viable heat rejection is the fourth, and its plant envelope is a site constraint. A full liquid-to-liquid retrofit needs a facility-side liquid loop and heat-rejection plant sized to the new load. Dry coolers and air-cooled chillers avoid process-water consumption but must clear ambient-bin capacity, electrical, acoustic, and space constraints; evaporative rejection also gates on water supply, treatment, and discharge. → water sourcing and climate-driven rejection in Chapter 3.7 and Chapter 5.8.

There are three real paths from an air hall to liquid, and the right way to rank them is by how much they disturb a building that is already running revenue, not by peak density. In a live hall, the dominant cost is downtime per rack and risk to the neighbors, not dollars per kW. The paths form a disruption ladder: closed-loop liquid-to-air sidecars at the bottom (drop-in, no facility plumbing), rear-door and air-assisted paths with their actual interfaces in the middle (RDHx can retain air-cooled servers; cold-plate AALC changes them), and full direct-to-chip liquid-to-liquid at the top (facility-side liquid loop, CDUs, in-rack manifolds, the works).

L2A — closed-loop liquid-to-air (the drop-in). The cold plates and in-rack loop are real direct-to-chip liquid cooling, but the heat is rejected back into the room air through a liquid-to-air heat exchanger inside the rack or an adjacent sidecar, with no facility water piping at all. Google's Brazos sidecar (announced June 2026; design being open-sourced through OCP) is the canonical example: a sidecar rack that cools an adjacent ~60 kW rack inside an existing air-cooled hall, rejecting into the hot aisle, letting an operator add dense racks incrementally without re-plumbing the building. The trade is a hard ceiling — you can only reject as much heat to the room as the room's air handlers can ultimately carry away — and it pushes the air-side harder, but it can avoid facility-water replumbing, which is why it occupies the early, low-disruption end of the retrofit market.

RDHx / AALC — rear-door and air-assisted liquid (the bridge). Rear-door heat exchangers replace the rack's back door with a water (or refrigerant) coil that intercepts the hot exhaust, carrying roughly 10–30 kW per rack passive in typical practice (to ~50 kW on current product) and ~50–100 kW with active fans — the fan-state split behind the fan-agnostic 30–40 kW typical / >50 kW active band the SemiAnalysis/nVent citation carries elsewhere in this guide (Chapter 5.3 holds all three bands side by side). This needs a room-level water loop and a CDU, but it leaves the servers themselves untouched — no cold plates, no quick-disconnects at the chip — so it is the natural bridge for a hall ramping density gradually, or for a mixed fleet where some racks are dense and some are not. It is the brownfield-friendly middle: more capacity than L2A, far less surgery than L2L. → engineered in full in Chapter 5.3.

L2L — full direct-to-chip, liquid-to-liquid (the destination). Cold plates on the hot silicon, in-rack manifolds, ~150–200 quick-disconnects per rack, a CDU isolating the technology-cooling loop from the facility-side loop, and heat rejection sized to the new load. This is the only path that supports the 132 kW nominal rack TDP of HPE GB200 NVL72, the up-to-142 kW facility design basis of GB300 NVL72, and higher-density successors, and it can earn its cost in a training-shaped hall when the supported equipment, installation, service and operating brief repay that disruption. It is also the most disruptive: it requires a facility-side liquid loop and heat-rejection plant sized to the load; site water supply and discharge are additional gates only when that plant uses evaporation, plus the largest civil and electrical works. → engineered in Chapter 5.4; CDUs and the secondary loop in Chapter 5.6.

The table is a disruption ladder with a density tax attached at the bottom. L2A buys you incremental, drop-in liquid with no negotiation with the building's water and slab. The ~60 kW figure is the Brazos-class sidecar's, not the architecture's: Vertiv rates a CoolChip CDU 350 L2A at 350 kW at 15 °C ATD (Chapter 5.6). Every L2A variant still pushes the air system, so a hall that goes all-L2A is ultimately air-reject-bound. RDHx buys headroom for a door swap and a room water loop, but stops where its air/water and capture schedule no longer clears the rack duty. A supported L2L path serves racks whose cold-plate heat cannot fit the room budget, and it demands exactly the facility water and structural capacity the brownfield assessment told you the building may not have. In practice the binding constraint chooses the path, not your ambition. If the slab and the water are there, you can reach for L2L; if they are not, L2A and RDHx are the ceiling, not lesser versions of the same thing.

You almost never convert a live hall in one outage; you convert it in phases, and for a long, awkward middle period the hall runs mixed — some rows on air, some on liquid, sharing a room, a power chain, and an air-handling plant that was balanced for neither. The engineering difficulty of a retrofit lives here, in the mixed state, not at either endpoint.

The first problem is thermal balance. As liquid rows come online, they pull heat out through water instead of dumping it into the room — which sounds purely good, but it changes the air-handling load non-uniformly. The remaining air-cooled rows still need their full airflow and supply temperature; meanwhile the room's total air heat load drops, CRAH units that were sized for the old load now short-cycle or over-cool, and hot/cold-aisle containment that was tuned for a uniform air hall now has to cope with rows that contribute almost no exhaust. Containment, airflow rebalancing, and CRAH/CRAC setpoint changes have to track the conversion row by row, or you get hot spots on the surviving air rows even as the liquid rows run cold. → hybrid containment in Chapter 5.2.

The second problem is electrical sequencing. Each liquid row is a step-change in rack power on a bus that was provisioned for far less, and the conversion order has to respect the upstream feed, PDU loading, and UPS capacity so that energizing a new dense row does not starve or trip the rows already running. This is where the electrical-headroom inventory from the assessment becomes an operational schedule, not just a feasibility number.

The third — and the one that keeps facility managers awake — is commissioning charged piping over live equipment. Flushing, filling, and pressure-testing a coolant loop a few feet from running, revenue-bearing racks means a first-fill leak is not a maintenance event, it is an incident with the potential to take down neighbors. The mitigations are procedural and physical: leak-zoning so a failure is contained to its row, leak detection wired to fast-acting shutoffs, blind-mate and quick-disconnect couplings that minimize open-fitting time, hydrostatic acceptance done on isolated sections before they go near live load, and a commissioning sequence that proves each loop dry-then-wet before any GPU depends on it. The retrofit's defining risk is that you are doing wet work in an occupied building. → leak detection, containment, and the commissioning sequence are engineered in Chapter 5.11 and accepted in Chapter 13.5.

The deliverable of a retrofit is usable megawatts of IT load on the floor, not 'liquid cooling installed.' A retrofit reshuffles the three quantities that gate usable load — power capacity, cooling capacity, and floor area you can structurally and physically populate — and they almost never line up. Whichever is smallest is your real capacity; the gap between it and the others is stranded capacity you paid to create and cannot use.

Work it as three independent budgets for the same hall, then take the minimum:

• Power-limited load = the megawatts the upstream feed, busway, switchgear, and UPS can actually deliver to IT after the new density. Liquid frees the chiller/CRAH share of the electrical budget, but the racks consume the freed headroom many times over.
• Cooling-limited load = the heat the chosen path can reject. For L2A this is bounded by what the room air system can carry away; a water-fed RDHx sends its captured heat to the facility loop, so the room plant carries only the uncaptured share and the door-failure case; for L2L it is bounded by the facility water loop and heat-rejection plant you installed.
• Floor-limited load = the racks you can structurally place (slab/floor rating after reinforcement) and physically fit once CDU galleries, pipe racks, leak-zoning, and service clearance consume white space.

Usable load = min(power, cooling, floor). The other two are stranded. A hall that retrofits cooling to 12 MW but is fed 8 MW has 4 MW of stranded cooling; a hall powered to 12 MW whose reinforced slab only carries dense racks across 60% of the area has stranded power sitting over a floor it cannot load. The pre-retrofit hall was typically cooling-bound (air ran out first); a successful liquid retrofit usually moves the binding constraint to power or floor — which is exactly why the assessment has to inventory all four quantities up front, and why the stranded number, not the density headline, is the figure that decides whether the retrofit earned its capital.

Counts are floor(7,000/100) = 70 electrical, floor(5,200/80.0) = 65 liquid, floor(1,400/20.0) = 70 air and 80 positions. Select 65 complete racks, 6.50 MW IT. Unused resources are 0.500 MW electrical, 0.100 MW air and 15 positions. Rack 66 requires 5.28 MW liquid and fails.

The first crossover is 5.28 MW liquid for rack 66. Adding 0.400 MW yields 5.60 MW and permits 70 racks at 7.00 MW IT and 1.40 MW air; power and air now bind. More liquid alone buys no rack. Price that discrete outcome using 1.8; 13.5 accepts migration states and 6.2 verifies structure. The ASHRAE/NEMA/PNNL framework supports consistent resource boundaries.

A retrofit earns its return by increasing the minimum complete-rack count while paying disruption and capital across the affected systems. In the assumed case, liquid capacity binds at 65 racks; expanding that branch can reach 70, where power and residual air become simultaneous constraints. Beyond that point, more liquid capacity alone buys no additional rack. Commit the upgrade that clears the next binding limit, reserve irreversible substrate for the funded ramp, and include the cost of taking a live hall through the work. Choosing otherwise buys installed cooling and reinforced floor that cannot host another rack, after the disruption has already been paid.

Choose the retrofit’s sellable rack count from the first binding power, liquid, air, structure or installation-route constraint. Expand the binding subsystem to release the next increment, and price the live-site work and outage before comparing that increment with new construction.