Liquid Cooling Responsibilities & IT Installation_

Direct-to-chip cooling moves heat from selected electronic components into liquid through cold plates. In the arrangement described by the public ASHRAE 2023 Handbook, a technology cooling system carries heat from the IT equipment back to a CDU heat exchanger associated with the facility-water system. Rack manifolds distribute the supply and return paths. This is a conceptual explanation of that arrangement, not a piping diagram or a rule that every product has the same loops. [A1]

These names describe functions, not appointments. A CDU, a rack manifold and a server cold plate are not interchangeable pieces of a single IT-cabling task. A customer must identify the actual supplied equipment, the interface drawing and the responsible party for each package. A cable installer seeing the same rack does not acquire responsibility for its liquid interfaces.

The distinction also explains why a component's cooling description does not settle the room's entire heat-removal requirement. Use the particular system's documentation to identify which components use liquid and which use air; do not infer a universal percentage or eliminate an environmental requirement from the phrase direct-to-chip. The approved OEM and facility package governs the actual design.

NVIDIA's DGX Vera Rubin hardware guide identifies rack liquid-cooling manifolds and describes cold plates on CPUs, GPUs and various networking and storage components in its compute trays. The DGX GB rack guide separately describes CPU/GPU cold plates with other compute-tray networking and storage components air cooled. Those are descriptions of the named systems, not a reason to copy a previous generation's cooling assumptions into another equipment package. [R1, G1]

For a Rubin physical-integration request, identify the complete ordered OEM system and delivered state before assigning the work. The presence of an internal manifold in the product description does not identify the site's CDU arrangement, its facility connection, cooling acceptance owner or an installer permitted to handle it. Equally, a facility cooling package does not identify which IT ports, equipment identities and permitted physical tasks belong in the IT installer’s handoff.

The buyer's coordination decision is therefore an interface decision: which supplied assembly and document revision does each party's work cover, and what return must the next party receive? Keep the OEM integration requirements, customer-appointed cooling work and separately agreed physical IT tasks visible. Leviathan's existing exclusion of all liquid-side work applies to this named context as well; a new GPU generation does not expand that offer. This guide supplies no handling, fluid, electrical, installation or operating method.

A facility capacity statement and a rack acceptance record answer different questions. A capacity statement describes a defined facility or cooling-system capability and its stated basis. It does not show that the identified installed rack configuration was examined under the agreed acceptance scope, or that the responsible party accepted its results. Ask the cooling owner for the applicable configuration, requirements and acceptance return rather than renaming a facility capacity sheet rack acceptance. The physical IT completion record remains a third, separate return.

Monitoring needs an equally explicit boundary. A device or cooling package can provide detection or measurement information without identifying who receives it, interprets it and owns the response. Name the equipment/signal owner, the monitoring recipient and the operational decision owner for the actual project. An IT installation record does not establish that this chain exists, and a reading in a dashboard is not itself a cooling acceptance result. This page gives no alarm setpoint, controls integration, leak response, sensor test or operating instruction.

Fictional EX-LC153 reviews three proposed scope lines for one supplied system. Two lines name proposed responsible parties; one leaves monitoring ownership unresolved. These are proposed assignments and requested outputs, not executed contracts, observed work or proof that the named parties are qualified. There are three lines, two proposed owners, one unassigned owner and zero completed checks or accepted results.

Use that distinction to prevent scope creep in an educational SOW discussion. Describe the actual task and its output rather than a broad phrase such as complete rack installation. If a new request adds a liquid connection, a detection-system task or responsibility for an alarm, return it to the customer and applicable specialist owner for an explicit scope decision. Do not turn coordination, a component label or the word cable into an unagreed trade duty. Actual contractual changes and acceptance remain with the authorized project parties.