ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Schneider Electric's Mark Deguara: Liquid Cooling Readiness Must Be Verified Per Row; Hall-Level Headroom Cannot Be Directly Promised to AI Tenants

Mark Deguara, Head of Technology Innovation at Schneider Electric, proposes a method for assessing liquid cooling readiness: in an existing managed data center, the ability to add high-density liquid-cooled GPU racks for AI tenants depends on the power, thermal, structural, aisle, and economic constraints of the specific target row, rather than the hall's nominal capacity. The assessment covers rack specification confirmation, electrical path tracing, summer design condition heat rejection verification, retrofit economic comparison, and acceptance boundary definition. The capacity actually written into the tenant agreement is the amount that passes actual testing.

2026-11-17 22:40 GMT+8

Imagine a new cloud tenant requesting a colocation provider in Western Sydney, Australia, to deploy a row of liquid-cooled GPU racks within an occupied data center. On paper, the site has spare floor space and backup electrical capacity. However, before quoting rack density or delivery dates, the operator must confirm whether the target row can support the new load while ensuring that existing tenants continue to receive their contracted services. In an assessment method published by Mark Deguara, Head of Technology Innovation at Schneider Electric, in November 2026, it is pointed out that liquid cooling readiness is specific to a particular rack row, not a general indicator for the entire hall.

This judgment changes the way capacity commitments are verified. Mark Deguara requires operators to confirm six dimensions per row: the sustained and peak electrical loads of the racks, the proportion of heat captured by the liquid loop versus the remaining air-cooling needs, the coolant temperature, flow, and pressure requirements, the complete electrical path from the grid connection to the rack distribution (including UPS and protection settings), floor loading and installation access (including the impact of CDU maintenance space on the number of leasable rack positions), and retrofit economics. In the Western Sydney case study, the central chiller plant may have overall headroom, but the branch serving the target row lacks sufficient flow during peak demand—a constraint that only becomes apparent through per-row verification.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Heat rejection verification must be conducted under local summer design conditions and planned maintenance states. Direct-to-chip cooling captures heat from high-power components via cold plates, while liquid-to-liquid Coolant Distribution Units (CDUs) transfer this heat to the facility water system. Operators must confirm the available temperature, flow, and differential pressure at the connection point while existing tenants are drawing cooling, and compare the CDU supplier's water quality requirements with the building-side filtration conditions. For rows without access to building cooling water, Heat Dissipation Units (HDUs) reject heat back into the room air; in this scenario, the room cooling system must simultaneously handle the heat discharged by the HDU and the residual heat from the cold plates. In mixed halls, rear door heat exchangers can intercept hot rack exhaust where the existing water system and rack configuration support them.

Retrofit economics depend on shared infrastructure and tenant deployment plans. Mark Deguara recommends comparing three options—targeted retrofit, dedicated hybrid zones, and independent expansion—using the same load and service conditions. If pipe routing, floor loading, or the outage required for grid integration makes live retrofitting unfeasible, prefabricated modular IT pods serve as an alternative option. Highly customized AI-fit facilities are difficult to repurpose after the lease expires, which impacts residual value assumptions. Acceptance records should capture the tested capacity, operational limits, and responsibility boundaries on both sides of the rack connection; the tenant agreement defines services based on this foundation rather than on the hall's nominal figures.

As a vendor methodology, this article does not provide independent verification data proving that following this process actually prevents over-commitment or reduces delivery risks. The value of Mark Deguara's argument lies in transforming liquid cooling readiness from a vague assumption of hall-level headroom into a verifiable, definite capacity for specific rack rows under normal operations and planned maintenance—enabling operators to identify constraints and price accordingly before quoting, rather than discovering bottlenecks only after delivery.

Sources

  • blog.se.comSchneider Electric Blog↗
Continue researching →