DCFR Insight 23 / Cooling + Water + AI Infrastructure

Capacity Delivery

Data Center Cooling in 2026: What Actually Works, What Is Most Efficient, and What Comes Next

Cooling now determines rack density, water exposure, energy use, site acreage, operating cost, and even whether an AI data center site is viable. A practical comparison of air cooling, rear-door heat exchangers, direct-to-chip liquid cooling, immersion, warm-water systems, and the technologies coming next.

Capacity Delivery Deep Dive

Cooling is now a site-selection and capacity-delivery decision

Data center cooling can no longer be treated as a downstream mechanical selection. AI accelerators have concentrated far more heat into each rack, while water constraints, utility prices, noise limits, equipment lead times, and campus phasing increasingly determine what can actually be delivered. The useful question is not which cooling technology wins in isolation. It is whether the complete thermal chain can capture heat at the chip, transport it through the rack and building, reject or reuse it under design-weather conditions, survive credible failures, and remain maintainable throughout the owner’s operating model. A concept that performs efficiently at nominal load may still be unsuitable if it consumes unavailable water, requires unsupported IT hardware, expands the equipment yard beyond the parcel, or cannot maintain temperatures during a utility or component event. DCFR therefore evaluates cooling as a coupled land, power, water, building, controls, acoustics, resilience, and operations problem.

Editorial diagram of the connected data center cooling chain from silicon heat capture through facility heat rejection and recovery — Cooling is a connected thermal chain: heat capture at the silicon and rack level must ultimately connect to facility heat rejection or useful heat recovery.

Start with workload, rack density, and the complete thermal chain

The design basis should define current and future rack power, diversity, utilization, heat-load ramp, supply-temperature requirements, allowable inlet conditions, liquid-cooling readiness, and the fraction of heat that must still be removed by air. A nominal megawatt target does not reveal whether the hall contains many moderate-density racks or a smaller number of extreme-density AI clusters. The team must also establish liquid quality, materials compatibility, pressure boundaries, leak detection, isolation, flushing, water treatment, controls, redundancy, maintenance bypasses, and responsibility at every handoff between the IT equipment, technology cooling system, coolant distribution unit, facility water system, and heat-rejection plant. Published equipment performance is only a starting point; final temperatures, flows, pressure drops, approach temperatures, part-load behavior, and failure sequences require project-specific MEP engineering and equipment-vendor confirmation.

Layer 1 — IT / Rack Heat-Capture Technologies

The first cooling decision is how heat leaves the silicon, server, and rack. Air cooling, rear-door heat exchangers, direct-to-chip cold plates, and immersion are heat-capture choices—not complete facility cooling systems. For planning, ASHRAE liquid-cooling W-classes provide useful context for facility-water supply-temperature capability, but the applicable class, allowable flow, pressure, chemistry, and transient limits must be confirmed for the actual IT platform. High-density AI deployments can exceed 100 kW per rack, but planning should use a rack-density distribution and vendor-qualified future cases rather than treating a headline density as a guaranteed campus-wide load. The selected capture layer must quantify the liquid capture ratio, residual air fraction, connection boundary, maintenance model, and failure response.

Air cooling still works—within a defined density envelope

Conventional CRAC or DX systems remain simple and economical for modest loads, edge facilities, legacy rooms, and sites where first cost and familiar maintenance dominate. CRAH units connected to chilled water provide more plant flexibility and can serve substantial campuses, especially when containment, blanking panels, cable management, raised-floor pressure, fan control, and supply-air reset are disciplined. Outside-air economization can reduce compressor hours in suitable climates, while evaporative or adiabatic assistance can lower fan and compressor energy at the cost of water use, treatment, plume or drift considerations, and more operating modes. Air is less capable than liquid at transporting concentrated heat; increasing airflow eventually increases fan energy, duct and plenum area, noise, recirculation sensitivity, and stranded white space. Air cooling is therefore not obsolete, but its practical rack-density limit must be validated rather than assumed.

Editorial diagram of contained conventional air cooling in a data hall — Conventional air cooling remains economically rational at moderate rack densities when containment, airflow management, and economization are properly designed.

Rear-door heat exchangers provide a practical transition

An active or passive rear-door heat exchanger intercepts hot rack exhaust and transfers much of that heat to a liquid loop before it enters the room. This can raise usable rack density, reduce recirculation, and preserve familiar air-cooled servers and service practices. It is particularly attractive in retrofits where rebuilding the entire data hall or replacing the IT fleet is unrealistic. The design must account for door weight and swing, hose and manifold routing, condensate risk, water temperature, rack fan interaction, pressure drop, leak detection, isolation, access, and the remaining room-cooling load. Rear-door systems do not eliminate the facility thermal chain; they relocate heat capture closer to the rack and introduce water connections at every served enclosure. Their value is strongest when those interfaces and the owner’s maintenance procedures are deliberately planned.

Editorial diagram of a rear-door heat exchanger connected to a facility cooling loop — Rear-door heat exchangers can increase rack density while preserving conventional air-cooled IT, making them particularly useful for retrofit and transitional deployments.

Direct-to-chip is the leading current path for high-density AI

Direct-to-chip systems place cold plates on CPUs, GPUs, memory, or other high-heat components and circulate coolant through rack manifolds to a CDU. Because liquid carries heat more effectively than air, the approach can support high and extreme rack densities with lower fan energy and higher coolant temperatures. It also fits the direction of many current AI server platforms. However, direct-to-chip rarely captures every watt: power supplies, drives, networking, and other components may leave a meaningful residual air load. Designers must quantify the liquid capture ratio and provide air cooling for the balance. They must also coordinate coolant chemistry, filtration, materials, connectors, dripless couplings, pressure control, pumping, leak response, CDU redundancy, controls, and ownership of the boundary between IT and facility systems. Its strong efficiency potential does not make it universally optimal; platform compatibility and service capability remain decisive.

Editorial diagram of direct-to-chip cold plates, rack manifolds, a CDU, and facility water piping — Direct-to-chip cooling removes heat close to high-power processors through cold plates, manifolds, CDUs, and a facility water loop.

Immersion offers exceptional heat transfer with a different operating model

Single-phase immersion submerges qualified IT hardware in a dielectric fluid that remains liquid, then transfers heat through a secondary loop. It can achieve very high density, reduce server fan energy, and support low-water operation when paired with appropriately designed heat rejection, but it changes rack form, lifting and service procedures, cabling, component qualification, fluid storage, spill response, filtration, fire strategy, warranties, and the supply chain for replacement parts. Two-phase immersion boils a dielectric fluid at the component surface and condenses the vapor, offering very high heat flux but adding fluid containment, environmental, pressure, material, and commercial-maturity considerations. The thermal performance can be compelling while the overall business case remains specialized. Owners should validate fluid availability, regulatory trajectory, vendor warranties, technician training, maintenance time, hardware refresh, and end-of-life handling rather than comparing only cooling energy.

Editorial illustration of servers in a single-phase immersion cooling tank — Immersion cooling provides exceptional heat-transfer capability but changes hardware handling, fluid management, maintenance procedures, and equipment qualification.

Layer 1 — IT / Rack Heat-Capture Technologies

Technology	Typical role	Density suitability	Key advantage	Primary constraint	2026 DCFR view
Conventional air cooling	Transfers IT heat into data-hall air for removal by room or facility cooling systems	Low–Medium	Mature, familiar, broadly serviceable and economical at moderate densities	Airflow volume, fan energy, recirculation, noise and usable space become increasingly restrictive as rack density rises	Economically sound where rack density remains modest and airflow management can be controlled effectively
Rear-door heat exchanger	Captures rack exhaust heat at the rear of the enclosure and transfers it to a liquid loop	Medium–High	Raises usable rack density while retaining conventional air-cooled IT equipment and familiar service practices	Rack-level liquid connections, door weight, hose/manifold routing, isolation, leak management and maintenance access	Strong retrofit and transition strategy
Single-phase direct-to-chip cold plate	Captures heat directly from CPUs, GPUs, memory or other high-heat components and transfers it through rack manifolds and CDUs	High–Extreme	High liquid heat-capture efficiency and strong compatibility with current high-density AI platforms	Residual air load, coolant chemistry, CDUs, connections, leak response, IT-platform compatibility and service procedures	Leading current solution for new high-density AI where the selected IT platform supports liquid cooling
Single-phase immersion	Submerges qualified IT equipment in dielectric fluid and transfers heat through a secondary loop	Extreme	Exceptional heat-transfer capability and major reduction or elimination of server fan energy	Specialized hardware handling, fluid management, maintenance procedures, warranties and vendor ecosystem	Thermally powerful specialized solution rather than a universal default
Two-phase direct-to-chip	Uses phase change at or near the cold plate to absorb very high silicon heat flux	Extreme+	Potentially high heat-flux capability with lower coolant flow and pumping requirements	Commercial maturity, refrigerant selection, seals, pressure control, qualification, service procedures and supplier ecosystem	Important emerging next-generation technology; validate delivery-date maturity and vendor support
Two-phase immersion	Uses boiling dielectric fluid and condensation to remove heat from immersed electronics	Extreme+	Exceptional potential heat-transfer capability	Fluid containment, environmental considerations, service model, hardware qualification and commercial maturity	Emerging specialized technology; do not assume bankability without detailed vendor validation

Heat-Capture Technology Decision Matrix

Heat-capture technology	Rack-density fit	Thermal efficiency potential	Site water implication	CapEx	O&M complexity	Retrofit fit	AI / HPC readiness	DCFR planning view
Conventional air	Low–Medium	Moderate	Facility heat-rejection dependent	Low	Low	Excellent	Limited at extreme rack density	Economically sound where rack density remains modest and airflow can be controlled effectively
Rear-door heat exchanger	Medium–High	Good	Heat-rejection dependent	Moderate	Moderate	Excellent	Good	Strong retrofit and transition strategy
Single-phase direct-to-chip	High–Extreme	Excellent; total-system performance depends on facility architecture	Heat-rejection dependent; can approach zero routine cooling-water use with appropriately designed dry rejection	Moderate–High	Moderate	Moderate	Excellent	Leading current choice for new high-density AI where the IT platform supports liquid cooling
Single-phase immersion	Extreme	Excellent	Heat-rejection dependent; immersion itself does not determine site WUE	High	High / specialized	Poor	Excellent thermally	Thermally powerful specialized solution; validate hardware compatibility, fluid ecosystem, maintenance model, warranties and vendor support
Two-phase direct-to-chip	Extreme+	Potentially exceptional	Heat-rejection dependent; the two-phase technology loop itself does not determine site WUE	Emerging	Emerging	Limited	Next-generation	Important emerging technology; validate refrigerant, vendor qualification, commercial maturity and field service
Two-phase immersion	Extreme+	Potentially exceptional	Heat-rejection dependent	High / emerging	High / specialized	Poor	Emerging	Specialized emerging architecture requiring detailed fluid, hardware, environmental, service and warranty review

Heat capture and heat rejection must be evaluated separately. Direct-to-chip, rear-door heat exchangers and immersion do not independently determine site water use. A liquid-cooled IT system can still consume significant site water when connected to evaporative heat rejection, while the same heat-capture architecture may approach zero routine cooling-water use when paired with appropriately designed dry rejection.
No cooling technology is universally optimal. DCFR evaluates viable cooling architectures against the site's rack density, climate, water availability, electrical cost, land availability, noise sensitivity, redundancy strategy, phasing, maintenance model, and IT-platform compatibility.

Layer 2 — Facility Heat-Rejection Technologies

The second layer transfers captured heat from the facility loop to the atmosphere or a useful heat sink. Dry coolers, fluid coolers, cooling towers, evaporative or adiabatic systems, chillers, and heat-recovery connections each create different power, water, land, noise, temperature, and resilience outcomes. Water use is heat-rejection-dependent: direct-to-chip or immersion does not inherently make a site water-free, and an air-cooled data hall may still be connected to a water-consuming central plant. DCFR therefore reports water logic for the complete architecture under normal, peak, drought-curtailment, and degraded operating modes.

Heat rejection determines energy, water, land, and noise

A liquid-cooled rack is not the end of the cooling system. Heat must still move to dry coolers, cooling towers, fluid coolers, chillers, evaporative systems, a district-energy connection, or a useful heat sink. Dry rejection can greatly reduce operational water demand but may require more coil area, fan power, site acreage, and acoustic mitigation, particularly at high ambient temperature. Evaporative rejection can improve thermodynamic performance and reduce equipment size while consuming water and requiring treatment, blowdown management, drift control, and a reliable water source. Chillers can preserve supply temperature during extreme weather but add compressor energy and refrigerant considerations. Planning must use appropriate hourly climate and design-weather data—not annual averages—and test normal, peak, degraded, maintenance, and water-curtailment conditions.

Layer 2 — Facility Heat-Rejection Technologies

Technology	Energy / temperature logic	Water-use logic	Land / noise implication	Planning application
Dry cooler / air-cooled fluid cooler	Strongest with warmer loop temperatures; fan energy and approach increase at peak ambient	Very low routine process-water use	Larger coil area and acoustical exposure	Water-constrained sites where climate and IT temperatures permit
Dry cooler with limited adiabatic assist	Assist preserves capacity or approach during selected hot hours	Low–Medium; depends on control hours, weather, cycles, and water quality	Can reduce dry-coil size but adds treatment and operating modes	Hybrid option where a defined water budget is supportable
Open cooling tower	Low condensing temperatures can reduce compressor energy	High; evaporation, blowdown, drift, and treatment must be quantified	Compact thermally, with plume, drift, and acoustical considerations	Water-secure sites where efficiency benefit outweighs water risk
Air-cooled chiller	Maintains lower supply temperatures with compressor and fan energy	Low routine process-water use	Equipment-yard and noise impacts can be material	Platforms requiring cold water or sites prioritizing low water exposure
Water-cooled chiller + cooling tower	Stable cold-water production with compressor, pump, and tower energy	High and heat-load-dependent	Plant, tower, treatment, and plume provisions required	Mixed legacy loads or low-temperature requirements with secure water
Hybrid dry + adiabatic + mechanical trim	Maximizes dry operation while using limited assist or mechanical cooling only when design conditions require it	Low–Variable depending on control strategy, climate and assist hours	More equipment and controls complexity but greater flexibility across operating modes	Strong candidate for high-density AI sites balancing water reduction, peak capacity and resilience
Useful heat recovery / district-energy connection	Value rises with loop temperature and coincident demand	Depends on the backup rejection architecture	Requires piping route, customer interface, and usually backup rejection	Credit only with a nearby, durable, contractable heat customer

Liquid heat capture does not by itself determine site water use; the facility heat-rejection selection does.
Final comparison must use hourly weather, design extremes, water chemistry, curtailment cases, redundancy, and part-load controls.

Warm-water architectures can unlock dry cooling and heat reuse

Higher coolant supply temperatures increase the number of hours when heat can be rejected without compressor operation. A warm-water direct-to-chip system may connect rack manifolds to CDUs, a closed facility water loop, and dry coolers, with adiabatic assistance or mechanical backup only when climate and resilience require it. This can reduce water exposure and improve energy performance, but the achievable temperature depends on the approved IT platform, cold-plate approach, liquid capture ratio, approach temperatures, fouling allowance, and design ambient conditions. Higher loop temperatures also make recovered heat more useful, although data-center waste heat is still often too low-grade for an economic customer without heat pumps. Heat reuse should be supported by a nearby, coincident, contractable demand; it should not be credited merely because a pipe connection is technically possible.

Editorial diagram of a warm-water direct-to-chip architecture with CDUs, dry coolers, adiabatic assist, and backup cooling — A warm-water direct-to-chip architecture can combine CDUs, facility water loops, dry heat rejection, optional adiabatic assist, and mechanical backup according to climate and resilience requirements.

ASHRAE Liquid-Cooling Temperature Classes — Planning Context

ASHRAE class	Nominal upper facility-water supply temperature	Planning implication
W17	17°C / 62.6°F	Relatively cool facility water; mechanical cooling may be required for substantial portions of the year depending on climate and system approach
W27	27°C / 80.6°F	Greater waterside-economizer and compressor-reduction opportunity
W32	32°C / 89.6°F	Strong warm-water and dry-cooling potential in many climates when approved by the IT platform
W40	40°C / 104°F	Significant opportunity for compressor-free heat rejection depending on climate, approach temperature and vendor-approved operating envelope
W45	45°C / 113°F	High-temperature liquid architecture with strong potential for dry heat rejection and improved useful-heat recovery
W+	Above 45°C / 113°F	Emerging high-temperature cooling and heat-recovery territory requiring project- and platform-specific validation

ASHRAE W-class capability is planning context, not permission to operate every server at the class limit. The selected IT platform, cold plates, coolant, rack manifolds, CDU approach temperature, controls, reliability margin and vendor-approved operating envelope determine the actual facility-water design temperature.

Efficiency is a system outcome, not a product label

Cooling efficiency must be evaluated across fans, pumps, CDUs, chillers, tower fans, water treatment, controls, and the effect of partial load and redundancy. PUE can help track facility overhead but can hide water impacts, local climate, IT utilization, and the energy embodied in external water or district systems. WUE likewise needs a clear boundary and should distinguish site water consumption from withdrawal and source stress. A low cooling-energy design may consume more water; a water-free concept may need more fan energy and land; an exceptionally dense solution may reduce building area while increasing operational specialization. Comparative modeling should use consistent loads, weather files, redundancy, setpoints, and boundaries, then test sensitivity to future rack mixes and utility rates. Claims of universal superiority usually indicate that a boundary or constraint has been omitted.

Illustrative site cooling scenarios

A cool, water-constrained site with qualified warm-water AI servers may favor direct-to-chip capture, a residual-air system, and dry coolers with limited mechanical trim. A hot, arid site may find that fully dry rejection protects water availability but increases coil area, fan energy, acoustical work, and peak electrical demand; carefully limited adiabatic assist may be evaluated if water can be secured. A dense retrofit may use rear-door heat exchangers and an existing chilled-water plant while reserving routes for a future liquid loop. These are planning-grade scenarios, not prescriptions: hourly weather, design conditions, platform qualification, redundancy, water quality, parcel geometry, utility capacity, and the owner operating model can change the result.

Resilience and controls must be designed together

Thermal ride-through is shorter at high heat flux, so the team must model loss of utility power, pump or fan failure, CDU failure, valve misoperation, controls or network failure, maintenance outages, rapid workload changes, and restart. The architecture may require redundant pumps, distributed CDUs, dual liquid paths, thermal storage, backup power, mechanical trim, or workload management. Leak detection must locate and isolate faults without turning nuisance alarms into broad shutdowns. Controls should coordinate server telemetry, CDU operation, facility loops, economization, heat rejection, water availability, and capacity limits while retaining safe local modes. Commissioning must verify sequences under real transitions and representative loads. Redundancy labels such as N+1 are incomplete unless the actual common paths, controls, power supplies, maintenance states, and repair times have been traced.

What comes next: two-phase cooling, smarter loops, and useful heat

Two-phase direct-to-chip systems use evaporation at a cold plate or similar device to absorb high heat flux with small temperature differences. They may reduce pumping demand and address next-generation silicon, but commercial readiness depends on refrigerant selection, seals, pressure management, controls, service procedures, qualification, and a durable vendor ecosystem. Other development paths include microfluidic or silicon-integrated cooling, higher-temperature secondary loops, advanced cold plates, improved thermal-interface materials, predictive controls, and campus-scale heat networks. None should be treated as automatically bankable because it performs well in a laboratory or pilot. Procurement maturity, field service, warranties, code acceptance, component availability, environmental requirements, and credible operation at scale must be confirmed for the delivery date—not presumed from a roadmap.

Editorial diagram of future high-temperature liquid loops, two-phase cooling, controls, and heat recovery — Future thermal architectures are likely to combine higher-temperature liquid loops, two-phase cooling, intelligent controls, and useful heat recovery.

Choose the architecture site by site and phase by phase

The defensible 2026 strategy is often hybrid: conventional air for support and moderate-density loads, direct-to-chip for qualified AI racks, rear-door exchangers for transition areas, and a heat-rejection system selected for the actual climate, water position, acoustic envelope, land plan, and resilience requirement. Phasing matters because an ultimate warm-water campus may begin with mixed IT generations and a much smaller initial load. Reserve routes, plant area, electrical capacity, water connections, structural support, and controls interfaces for credible future states without overbuilding every phase. Final selection requires coordinated MEP engineering, equipment-vendor confirmation, utility and water-provider confirmation, climate/weather design data, acoustic analysis, environmental and AHJ review where applicable, and alignment with the owner’s staffing, maintenance, spares, commissioning, and IT refresh strategy.

Current Technical Basis — August 2026

Planning context should be reconfirmed against the current editions, vendor data, project requirements, and authority interpretations at the time of design.

AI Data Center Energy Performance Framework — Energy and Thermal Efficiency — ASHRAE / NEMA / PNNL (2026)
AI Data Center Energy Performance Framework — Integrated Design Principles — ASHRAE / NEMA / PNNL (2026)
Dry cooling energy performance can rival evaporative cooling — Uptime Institute (2026)
Investments back two-phase cooling as water cold plate successor — Uptime Institute (2026)
NVIDIA GB300 NVL72 — NVIDIA (2026)
Thermal Guidelines for Data Processing Environments, Fifth Edition — ASHRAE Technical Committee 9.9 (2021)
ASHRAE TC 9.9 Datacom Encyclopedia — Water-Cooled Servers — ASHRAE
Advanced Cooling Solutions — Open Compute Project
Best Practices Guide for Energy-Efficient Data Center Design — U.S. Department of Energy
Data Center Metering and Resource Guide — Lawrence Berkeley National Laboratory

DCFR decision support

How DCFR would select a cooling architecture

DCFR converts the cooling discussion into a traceable feasibility decision. Each gate tests whether the proposed heat-capture and heat-rejection layers remain compatible with the workload, site, utilities, delivery program, resilience target, and operating organization.

13 Cooling Architecture Decision Gates

1Define workload, rack-density distribution, ramp, diversity, and credible future IT generations.
2Confirm IT-platform air and liquid requirements, including applicable ASHRAE W-class planning context.
3Quantify liquid heat-capture ratio and the residual air-cooling load.
4Establish chip, rack, CDU, facility-loop, and vendor responsibility boundaries.
5Screen climate and hourly design conditions against achievable loop temperatures.
6Confirm water source, quality, allocation, treatment, discharge, and curtailment conditions.
7Compare total electrical demand for fans, pumps, CDUs, chillers, and heat rejection.
8Reserve plant area, pipe routes, structural capacity, access, setbacks, and acoustic mitigation.
9Trace redundancy, common modes, thermal ride-through, maintenance states, and restart sequences.
10Validate leak detection, isolation, drainage, chemistry, materials, and fluid-management strategy.
11Test phasing, mixed IT generations, temporary states, and conversion without stranded capacity.
12Confirm vendor maturity, qualification, warranties, lead times, spares, and technician capability.
13Define metering, integrated controls, commissioning, acceptance criteria, and performance verification.

DCFR Cooling Decision Output

Selected Layer 1 heat-capture architecture by hall, zone, and phase
Selected Layer 2 heat-rejection architecture and operating modes
Design temperature, flow, power, water, land, noise, and resilience basis
Residual-air, trim-cooling, backup, and ride-through requirements
Interfaces, owner/vendor responsibilities, enabling works, and decision holds
Risks, confirmations, sensitivities, and alternatives carried into the next gate

Illustrative DCFR Cooling Recommendation

For an illustrative new high-density AI campus with vendor-qualified liquid servers, constrained water, and suitable climate, DCFR may carry forward warm-water direct-to-chip cooling with a quantified residual-air system, distributed redundant CDUs, and dry heat rejection with limited peak trim. The recommendation would remain conditional on IT supply-temperature approval, hourly design-weather modeling, 100 kW+ rack distribution, water and acoustic confirmation, degraded-mode performance, parcel fit, commissioning, and an operable phased transition plan.

“The cooling decision is not Air versus Liquid. The real decision is the complete architecture from silicon to atmosphere.”

DCFR system flow

Workload + silicon

Server heat capture

Rack manifold

CDU / technology loop

Facility water loop

Heat rejection or reuse

Atmosphere / heat customer

Cooling Feasibility Red Flags

• A campus-wide average density masks the 100 kW+ rack population.
• Liquid cooling is specified without an approved IT platform or W-class basis.
• Residual air heat is omitted from room and plant capacity.
• A water-free claim ignores evaporative or water-cooled heat rejection.
• Peak ambient, drought, smoke, fouling, or degraded modes are not modeled.
• CDU or facility-loop boundaries and ownership are undefined.
• Plant area, pipe routes, structure, access, or acoustics do not fit the site.
• Efficiency comparisons use inconsistent loads, redundancy, or system boundaries.
• Phasing strands plant capacity or cannot support mixed IT generations.
• Vendor warranty, service, spares, fluid, and hardware qualification are unconfirmed.

Capacity-delivery review checklist

What to verify before the next release gate.

Rack-density distribution and future IT generations defined
Liquid capture ratio and residual air load quantified
IT-platform coolant and temperature requirements confirmed
Complete chip-to-ambient thermal chain modeled
Hourly climate and extreme design conditions tested
Heat-rejection land, setbacks, and service access reserved
Water source, quality, treatment, and curtailment exposure confirmed
Electrical energy and peak-demand impacts compared
Acoustic performance evaluated at sensitive receptors
CDU, pump, valve, and control failure modes tested
Leak detection, isolation, drainage, and response procedures defined
Materials compatibility and water chemistry requirements assigned
Phasing and mixed air/liquid operation coordinated
Maintenance bypasses, lifting, spares, and technician training planned
Vendor warranties and equipment qualification confirmed
Commissioning and integrated load-testing strategy established

What DCFR would flag

Delivery risks that should be visible early.

DCFR would flag a cooling concept selected from average rack density rather than the actual density distribution; liquid cooling without a defined IT platform, capture ratio, CDU boundary, or residual air load; water assumptions unsupported by provider confirmation; heat rejection sized without design-weather and degraded-mode analysis; plant that exceeds available land or acoustic limits; and efficiency claims that omit pumps, fans, chillers, redundancy, partial load, water treatment, or maintenance states.

Professional confirmation required

Items requiring project-specific validation.

Final cooling selection requires project-specific MEP engineering, equipment and IT-vendor confirmation, utility and water-provider confirmation, current climate/weather design data, acoustic and environmental analysis, controls and commissioning development, applicable AHJ review, and approval by the owner’s operations organization. Planning-grade comparisons are not final equipment selections, performance guarantees, or water and utility commitments.

Final takeaway

The most efficient cooling architecture is the one that reliably serves the actual workload within the site’s climate, power, water, land, noise, phasing, and operating constraints. In 2026, that answer is increasingly liquid-assisted—but it remains site- and platform-dependent.

Surface site, code, utility, and delivery risk before it becomes expensive.

DCFR converts early assumptions into planning-grade flags, confirmation registers, and decision-ready feasibility outputs.

Order Report View Pricing

All insights Next capacity-delivery insight