Define the boundary between the two systems
For a liquid-to-liquid CDU using a heat exchanger, the facility water system and the technology cooling system are separate fluid circuits. The facility loop carries heat toward the plant; the technology loop serves the IT equipment under its specified temperature, pressure and fluid-quality conditions.
Show that boundary on the piping and instrumentation diagram. Define where heat is exchanged, which team owns each circuit and which parameters must be controlled. A clear boundary helps facilities, IT and controls teams work from the same assumptions.
Establish the design inputs
Record the IT cooling arrangement, design load, facility supply conditions and the limits specified by the server and cooling-equipment suppliers. Include fluid compatibility, flow, pressure and temperature requirements.
The heat-exchanger approach temperature and available facility conditions affect the technology-loop supply temperature. Setpoints should follow the selected equipment and site conditions, including condensation considerations. Generic temperature ranges are not a substitute for the project’s selection data.
Make the hydraulic and control responsibilities explicit
Identify pumps, isolation valves, filters, measurement points and any bypass paths. Explain how each circuit maintains its required flow or pressure as load changes. A bypass needs a defined purpose and operating sequence; an uncontrolled flow path can undermine the intended temperature difference.
Agree who controls the CDU and what information is exposed to BMS or DCIM. The points list should identify units, signal ranges, alarms and ownership, so that the integration can be tested end to end.
- Supply and return temperatures on the relevant circuits.
- Flow and pressure measurements required by the design.
- Pump status, speed, faults and service information.
- Leak detection, communications health and alarm routing.
Review redundancy at the relevant level
Spare pumps, multiple CDUs and alternative power supplies address different failure conditions. Define which component can be unavailable and the capacity that must remain. Include the headers, valves, controls and facility supply in that review.
Maintenance access also matters. The operating team should know how a filter, sensor or CDU can be isolated, and what the rest of the system does during that work. Include these scenarios in the project’s approved operating and test procedures.
Carry the design into acceptance
Before functional testing, verify installation, labeling, instrument calibration and the project’s cleaning, fluid-quality and pressure-test records. Functional checks then examine the selected operating modes, load changes, alarms and agreed fault responses.
Retain trend data and pass/fail observations against the acceptance criteria. Handover should include the as-built diagram, settings, alarm matrix, maintenance instructions and operator training records. These documents make the interface understandable after the commissioning team leaves.