From cold plate to facility: defining TCS and FWS boundaries

Direct liquid cooling is not a cold plate connected to a pipe. It is a heat path made of the source interface, server branches, rack distribution, the technology cooling system (TCS), a coolant distribution unit (CDU), the facility water system (FWS) and final heat rejection. Temperature, flow, pressure, fluid, materials and service boundaries must be defined at every layer.

The TCS sits close to IT equipment and delivers stable coolant to cold plates. The FWS receives heat from the CDU and carries it to chillers, dry coolers, towers or heat-reuse systems. A CDU heat exchanger normally separates the two so that fluid chemistry, water quality and pressure boundaries remain controlled.

Useful project inputs include heat load and liquid-capture ratio, server branch count, supply and return temperatures, total flow, allowable pressure drop, facility-water conditions, residual air load, redundancy, controls and service space. Rack power alone is not enough for a dependable selection.

Review the complete path: cold-plate hotspot coverage, branch flow balance, CDU pumping and heat exchange, year-round facility rejection, and alarm, derating and recovery behavior during abnormal conditions.

Reference framework: Open Compute Project cold-plate cooling-loop requirements and ASHRAE data-center liquid-cooling guidance. This article explains engineering method and does not replace OEM requirements, project specifications or test evidence.