Technical perspective
Liquid-cooling decisions follow duty, data and validation — this article gives the engineering basis for them.
A CDU commonly provides circulation, heat exchange, filtration, air management, fill, sensing and protective controls. Selection begins by defining the loop and fault domain it serves, not by choosing the largest nameplate rating.
A liquid-to-liquid CDU transfers TCS heat to facility water and fits sites with a dependable water loop and final heat-rejection path. A liquid-to-air CDU rejects heat into room air and can support sites without facility water or phased retrofits, but room sensible capacity, airflow, fan energy, acoustics and the upgrade path must be rechecked.
CDUs may be rack, row or facility based. Rack units support modular growth and local isolation; row units balance capacity, footprint and access; facility units centralize infrastructure but expand common piping and fault domains.
Review rated and part-load conditions, secondary flow and available differential pressure, heat-exchanger approach, pump operating point, filter differential pressure, the exact redundant elements, power and controller architecture, parallel-unit logic, isolation and bypass, service clearances and BMS/DCIM communications.
Bind the final selection to operating conditions, the system curve and a validation plan. More capacity is not automatically safer: oversizing and excessive centralization can increase pumping energy, control complexity and failure impact.