LEVIATHAN SYSTEMS

Liquid Cooling_

Coolant Distribution Unit (CDU) Installation & Commissioning

·Technical content·

An educational discussion of CDU installation and commissioning topics. Leviathan does not perform CDU or cooling-loop work; the customer must identify the qualified cooling and OEM parties for the project.

Key facts

  • ASHRAE's 2019 convention calls the FWS side primary and the TCS side secondary. Supplier labels still need named endpoints. [A1]
  • A heat-transfer rating in kW, a circuit flow in L/min and an available pressure differential describe different capabilities; their conditions must belong to the same offered configuration. [V1]
  • For equal capacity units, N is the number needed for the stated duty. N+1 adds one unit; 2N duplicates the full required capacity. Counts alone do not establish independent failure paths. [V2]
  • A leak-detection indication, an alarm threshold and the authorized response are separate functions. A sensor count or quiet display does not establish their complete coverage.
  • Approach temperature compares specified temperatures across the heat exchanger. The equipment circuit's supply-to-return temperature rise is a different quantity. [O1]
  • A factory assembly test and a site interconnect test cover different objects. Neither record automatically demonstrates the installed system's thermal performance or failover behavior. [A1]
  • The separation of fluid circuits does not select either fluid. The actual equipment, wetted materials and applicable supplier requirements determine the compatibility question.

Identify the Two Circuits Before Reviewing Mechanical Integration

A liquid-to-liquid CDU transfers heat from the IT-facing technology cooling system, or TCS, to the facility water system, or FWS. Its heat exchanger keeps the liquids separate in intended operation, allowing different chemistry and hydraulic conditions on each side. Separation does not make the facility fluid suitable for circulation through the IT equipment. [V1]

ASHRAE's 2019 white paper calls the FWS side primary and the TCS side secondary. Those are the convention used by that source, rather than universal port-identification instructions. Read a supplier's drawing through its named facility and equipment endpoints; a primary or secondary label without that context is insufficient. [A1]

This changes the mechanical review. The offered CDU, its two circuit interfaces, distribution arrangement and service access must describe the same configuration. A drawing that resolves the facility connection but omits the IT-facing connection is incomplete even if its footprint fits the allocated space. The appropriate location, connections and clearances remain decisions for the selected OEM and appointed qualified cooling and facility parties; no generic distance, pipe size or fastening value follows from the CDU label.

Separate Supplied-Equipment Tests from Site Interconnect Tests

ASHRAE's 2019 discussion distinguishes the manufacturer's supplied IT assembly from site-installed interconnecting piping or hoses. These are different test objects. This historical distinction establishes neither today's applicable code nor a field method. [A1]

Consider a fictional delivery containing a tested rack assembly and a separately supplied CDU. The factory record identifies the rack assembly's internal boundary. Connections later made between that assembly and the CDU were outside that factory test. Conversely, a site record covering only the interconnecting piping cannot establish the internal condition of every supplied assembly. The records can complement one another only when their boundaries and applicability are understood.

This is why one pressure multiplier and hold duration cannot define commissioning for the whole delivery. A pressure assessment, a fluid-compatibility assessment and a thermal-performance result answer different questions. The responsible specialists establish the actual objects, methods and acceptance basis with the OEM and site requirements. A document's title cannot extend its coverage to untested connections, another fluid or a changed equipment population.

Read Capacity, Flow and Temperature on Their Own Bases

A kW rating describes heat-transfer duty under stated conditions. Vertiv's historical XDU450 data sheet, SL-07622 (R06/21), qualifies heat duty by approach temperature and flow capability by external differential pressure. These separate entries do not form an unconditional equipment promise. [V1]

OCP's liquid-to-liquid CDU performance paper defines approach temperature difference as TCS supply temperature minus FWS supply temperature. This compares two circuits; the TCS return-minus-supply temperature rise compares two points within one circuit. OCP also separates thermal performance, TCS pressure head and FWS flow impedance. A temperature difference without its named points cannot settle which capability is being claimed. [O1] An IT supply limit can also be constrained by room dew point; a fixed approach difference does not establish the equipment's full allowable temperature envelope. [A1]

For steady single-phase heat transport with approximately constant specific heat capacity, heat-transfer rate equals mass flow times specific heat capacity times temperature rise. Using kg/s, kJ/(kg K) and K yields kW. A volumetric-flow expression also needs density and consistent unit conversion; L/min cannot silently replace kg/s. This explains the calculation's basis without sizing equipment. [O2]

In a fictional proposal, 30 parallel branches assigned 10 L/min each imply 300 L/min through that branch set. A separate 100 L/min entry cannot describe the same combined branch flow under the same conditions. Resolving that contradiction does not establish the required flow or heat duty: the branch assignments themselves are stipulated, unvalidated values. Likewise, a supply-to-return temperature rise alone cannot distinguish changed heat load from changed flow.

Distinguish Redundancy Capacity from Independent Failure Paths

N+1 describes one additional capacity unit beyond the number required for the stated duty; it does not always mean two CDUs. Vertiv's cooling-redundancy explanation also distinguishes full-system duplication and warns that a shared dependency can defeat the value of a spare CDU. [V2]

Suppose a fictional duty requires two equal units at an already established operating point. N is two; N+1 has three capacity units, leaving two if one unit is unavailable. The capacity count for 2N is four, representing two full-duty sets of two. Two half-duty units together supply only N in this example. Two full-duty units would instead be the special case where each unit alone supplies the entire duty, so N is one.

These counts assume equal applicable unit capability. They do not specify how liquid reaches the equipment or whether a fault can affect multiple units. For example, if all counted units depend on one shared facility-water service, loss of that service is outside the protection demonstrated by counting spare CDU capacity. A claim of independent paths requires examination of the actual shared dependencies, including distribution, heat rejection, power and controls.

A failover result is another distinct claim. Installed capacity does not demonstrate transition behavior under an identified fault and load. The appointed specialists must establish the applicable system assessment and actual evidence. No valve position, standby speed, switching protocol, breaker operation or transition time is prescribed here.

Interpret Observations Without Turning Them into Diagnoses

A displayed temperature above a stated target is an observation at a particular point and time. It does not, by itself, establish a failed valve, fouled exchanger or insufficient branch flow. Before interpreting the comparison, establish whether the target and observation concern the same circuit, equipment configuration and operating condition. A facility inlet value cannot be substituted for an IT supply value simply because both are temperatures.

Thermal and hydraulic evidence also have different boundaries. A total-flow reading does not identify how that flow divides among branches. A pressure differential belongs to its two measurement points; it is not the same quantity as pressure at one point. Comparing records with different measurement boundaries can produce an apparent change that has not been shown to describe the same object.

For a fictional example, a report says 'supply temperature high' but omits the circuit and applicable equipment limit. That statement supports a need for clarification by the responsible OEM or cooling specialist. It supports neither a component diagnosis nor a repair decision. Its usefulness improves when the observation is tied to the actual equipment, time, conditions and applicable requirement.

The same reasoning applies to alarms. A configured threshold defines a trigger; an indication records an event or state within the detection function's scope. Neither establishes the complete response chain or a universal instruction to shut down cooling. Coverage, recipients and authorized operational decisions belong to the actual system's defined arrangements.

Baseline Documentation and Handover

A useful baseline connects the supplied equipment identity and revision with the applicable operating basis and actual recorded conditions. Retain the CDU serial number and relevant configuration information so that later evidence can be compared with the same system. A setpoint records an intended target; a measured value records an observation; an acceptance disposition records a responsible decision. These should remain distinguishable even when one report contains all three.

For example, a factory record may cover the supplied assembly, a site record the interconnections, and a separate commissioning return the assessed system behavior. If an assembly changes after one record was issued, the record still describes its original boundary and configuration. The responsible owner must determine its continued applicability. Relabeling it as the current baseline does not resolve the change.

Preserve actual results and exceptions with the requirements they address. A report containing a thermal result supplies no missing failover result, and an accepted interconnect test supplies no missing fluid-compatibility assessment. This makes the handover useful for later comparison without inventing a mandatory test programme, service interval or live maintenance demonstration.

Identify the customer's qualified cooling provider and its agreed support contact; Leviathan provides no CDU or cooling-loop service. This exclusion includes liquid-side coordination, subcontracting, measurements and commissioning. Its separately agreed physical IT work does not include facility electrical, cooling-controls or software commissioning. The cooling-responsibility guide at https://www.leviathansystems.co/services/liquid-cooling explains the surrounding IT boundary. For an inquiry about customer-supplied rack equipment and IT cabling, use https://www.leviathansystems.co/contact?service=gpu-assembly&from=/articles/cdu-installation-commissioning to discuss scope, requirements and availability.

Standards referenced: A1 — ASHRAE TC 9.9, Water-Cooled Servers: Common Designs, Components, and Processes (2019; 10 October 2019 errata incorporated), printed pages 11–12 and 32–33. Historical terminology/test boundaries; no current code or field-method authority. https://www.ashrae.org/File%20Library/Technical%20Resources/Bookstore/WhitePaper_TC099-WaterCooledServers.pdf · O1 — OCP, Liquid to Liquid CDU Test Methodology and Performance Rating, Revision 1.0, header August 2024, pages 15–19. Temperature points and thermal/hydraulic rating bases only; no example fluids, numerical requirements or test methods adopted. https://www.opencompute.org/documents/ocp-wp-l-lcdu-test-methodology-performance-rating-r1-pdf · O2 — OCP, Data Center Liquid Distribution Guidance & Reference Designs, Revision 1.0, 8 January 2024; page 7. Single-phase heat-transport relationship only; no pipe-sizing table or reference design is selected. https://www.opencompute.org/documents/ocp-acf-reference-design-guidance-white-paper-r1-pdf · V1 — Vertiv XDU450 data sheet, SL-07622 (R06/21), pages 1–2 and 4. Historical circuit separation and qualified heat/flow capability; no current specification, availability or project suitability asserted. https://www.vertiv.com/49cb75/globalassets/shared/vertiv-xdu450-cdu_datasheet_en-na.pdf · V2 — Vertiv, How N+1 redundancy supports continuous data center cooling, displayed date 12 August 2025. Capacity definitions and shared-dependency distinction only; no universal redundancy minimum, topology or operating method is adopted. https://www.vertiv.com/en-us/insights/articles/educational-articles/how-n1-redundancy-supports-continuous-data-center-cooling/

Frequently asked_

Does a factory test record cover the installed CDU loop?

Only its identified test object and conditions are covered. Later site interconnections and any equipment outside that object require their own applicable assessment. Read factory and site records together without extending either boundary; neither alone establishes complete thermal or failover performance.

Does a quoted total flow prove that every GPU receives enough coolant?

No. A circuit total does not identify individual branch flows or establish the actual equipment requirement. The fictional 30-branch example checks addition only. Establishing sufficient flow requires the selected system's applicable thermal and hydraulic basis and the responsible specialist's evidence.

Can alarm thresholds be copied from another CDU or GPU generation?

A threshold belongs to a defined equipment function, configuration and response arrangement. Another product's value does not establish the applicable trigger or authorized response for this system. A quiet display also cannot demonstrate detection coverage or a completed commissioning assessment.

Does N+1 or 2N prove that failover will preserve GPU operation?

No. With equal units and a duty requiring two, N+1 counts three capacity units and 2N counts four. Independent failure paths, remaining capability and transition behavior require separate system evidence. A unit count supplies no failover method, time limit or operating permission.

What does supply-temperature drift establish?

It establishes a reported change only when the measurement point and comparison basis are known. It does not identify a component cause. Preserve the equipment, circuit, time and conditions for the responsible OEM or cooling specialist's assessment; no repair or operating action follows from the symptom alone.

Discuss Your Infrastructure Project_

Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.

Discuss a ProjectEmail Project Scope