A liquid-cooling installation can be assembled correctly and still need substantial work before it is ready for an IT load. The handover must show that the completed fluid path is clean, balanced and operating within the conditions agreed for the connected equipment.
Vertiv's October 16 announcement offers a concrete example. The supplier reports delivering a direct-to-chip high-density cooling deployment at CapitaLand India Trust's CLDC Mumbai 01 facility in Navi Mumbai. It says the secondary fluid network supports 30 MW of AI workloads for a hyperscale customer.
The release describes customized technology-loop skids, installation procedures intended to limit dust ingress, loop balancing and Level 4 testing before go-live. Those are supplier-reported delivery and testing statements. The published material does not include the underlying acceptance results, a measurement of customer utilization or an independently verified energy saving.
The useful operational detail is the attention to what happens between manufacturing and live service. My assessment is that buyers should make the condition of the installed loop an explicit handover deliverable, with a traceable record connecting factory work, site installation and acceptance.
Preserve the equipment's condition through installation
Factory testing describes equipment at a particular point in its journey. Transport, storage, site handling and connection work introduce additional stages that the operating team needs to understand.
Ask who owns the equipment at each stage and how its condition is recorded. The installation plan should define the approved handling and connection procedures, the inspections required before work proceeds and the response if a protective measure is disturbed.
The purpose is to create a usable history. When an issue appears during commissioning, engineers should be able to identify which sections were opened, which work was completed and what checks followed. A record assembled during the job is more useful than a general assurance written after it.
Agree on acceptance criteria before the test
A commissioning label does not tell a customer everything that was exercised. Ask for the specific test scope, instruments, limits and configuration behind the proposed acceptance process.
Define the required fluid conditions using the requirements of the actual equipment and suppliers involved. Identify the sampling or inspection method, who evaluates the result and what happens when a result falls outside the agreed limits. This article does not prescribe a universal threshold: the supported system configuration should determine it.
Keep corrective work in the same record. If a section needs further cleaning, adjustment or inspection, document the action and the evidence required before that section is accepted. That makes a conditional handover visible instead of allowing an unresolved item to disappear into a completed checklist.
Relate balancing to the connected load
A balanced loop needs a defined operating condition. Record the connected equipment, valve settings, measured flow and other parameters required by the agreed test procedure.
Then establish which changes can invalidate that record. Adding equipment, changing a branch or revising an operating setpoint may require a review. The facilities and IT teams should know when to involve the cooling supplier before a planned change becomes a live performance question.
For staged deployments, keep the acceptance boundary clear. The record should identify the part of the installation released for use and the assumptions attached to that release. A site-level capacity description should not substitute for evidence about the phase receiving a workload.
Hand over a maintainable record
The operating team needs more than a passing result. It needs the approved configuration, test data, open items and procedures for isolation, service and return to operation.
Assign ownership of that record after commissioning. A maintenance intervention should leave enough information for the next engineer to see what changed and whether any acceptance checks need repeating. Keep the escalation route clear when a symptom could involve the facility loop, distribution equipment or server-side cooling.
For infrastructure suppliers, this is a practical service to build around liquid-cooling deployments: maintain continuity of evidence from delivery through operation. Vertiv's Mumbai announcement reports the physical installation, but its most transferable detail is the sequence connecting contamination control, balancing and testing. Buyers can use that sequence to ask for a handover their own operators can work with.
Top comments (0)