Engineering guide 02 / 08
Liquid Cooling Commissioning and Clean Loop Readiness
The pipework holds pressure and the coolant distribution unit (CDU) is ready to start, but can you safely connect the racks? Commissioning answers that question with evidence of cleanliness, correct fluid, cooling performance and tested responses.
On this page
Commission the facility water system (FWS) and technology cooling system (TCS) against their separate requirements. Before connecting sensitive equipment, accept the pipework integrity, cleaning records and final fluid; then verify cooling duty, alarms and recovery, and hand operators a documented baseline.
- For
- Commissioning agents, contractors and startup engineers
- Scope
- New or modified single-phase, water-based TCS distribution and liquid-to-liquid CDUs serving direct-to-chip equipment. Apply approved OEM procedures and project requirements for pressure tests, cleaning chemistry and discharge.
Key decisions
- Protect cold plates and other sensitive equipment from construction flushing and unapproved test pressures.
- Verify particles, fluid chemistry and performance separately; one passing measurement cannot prove all three.
- Turn over the baseline, exceptions and operating procedures together with the physical system.
- 01Approve the test boundary
Requirements, equipment isolation and witnessed hold points
- 02Prove clean-loop readiness
Integrity tests, branch coverage and approved cleaning records
- 03Verify the final fill
Fluid identity, laboratory results, air removal and preservation
- 04Test operating performance
Flow, heat transfer, point checks and specified fault response
- 05Release to operations
Baseline, procedures, training and signed disposition of defects
Each release applies to a defined system boundary. New connections or rework can invalidate previous acceptance and require an agreed retest.
What evidence allows the racks to connect?#
Rack delivery is approaching. The pipework passed its pressure test, and the contractor reports flushing complete. Yet the record shows neither branch coverage nor final samples against rack requirements. Before connection, the team needs to establish what evidence is missing.
List the served racks, permanent components and temporary equipment on the test drawing. Keep FWS and TCS acceptance separate: a passing facility-water result does not prove the technology coolant is ready. Name who releases each gate and who witnesses it.
Use the approved design, original equipment manufacturer (OEM) and coolant requirements to set limits. Record the units, method, revision and reviewer. Allow for laboratory turnaround in the schedule. ASHRAE highlights the consequences of inadequate preparation in liquid-cooled facilities; cleanliness belongs in the release sequence.
| Gate | What must be demonstrated | Record before release |
|---|---|---|
| Mechanical readiness | Construction and integrity meet requirements | Boundary, instruments, test results and witnesses |
| Clean distribution | Cleaning and flushing reach every relevant branch | Valve lineups, flows, filter records and samples |
| Final-fluid readiness | Filled coolant meets requirements | Batch, fill record and laboratory report |
| Hydraulic and thermal duty | Required flow and heat transfer | Aligned load, temperature, flow and pressure trends |
| Functional readiness | Specified monitoring and protective responses | Point checks, fault tests and reset verification |
| Operational handover | Operators can maintain the accepted system | Baseline, training, procedures and open-item decisions |
References: ASHRAE: Commissioning and Performance Validation
What could contaminate the loop before startup?#
Inspect pipe ends, manifolds, hoses and connectors before assembly. Record missing caps, wet storage and dirty interiors. Keep cleaned parts identifiable and close open work with compatible caps. Prevention reduces what cleaning must remove.
Rental skids, tanks, hoses and transfer pumps can introduce debris or residual fluid. Confirm their materials, cleanliness and intended flow path before connection.
A load bank must suit the fluid circuit as well as the test kilowatts. Vertiv's XDU1350 guidance addresses secondary-pipework cleanliness and load-bank protection. Obtain approval for the actual test-load connection, rather than treating it as an interchangeable accessory.
- Assign a cleanliness owner for each installation zone and record changes in custody.
- Approve joining materials and prevent fragments or excess compounds entering the fluid path.
- Inspect the temporary filtration arrangement and verify its rating and installation.
- Plan collection, containment and authorized disposal for every test and flushing fluid.
References: Vertiv: XDU1350 Coolant Distribution Unit Application and Planning Guide
Which equipment must stay outside the test circuit?#
Trace the connected test boundary before applying pressure. Its lowest approved component test pressure constrains the test. Review gauges, temperature effects and relief provisions with the design authority. A pipework procedure does not automatically permit the same test pressure on a connected CDU, rack or expansion device.
Use the agreed isolation and bypass for construction cleaning. Open Compute Project (OCP) row-manifold guidance calls for flushing secondary pipework with the CDU disconnected. Obtain supplier approval for variations.
Mark every isolation on the field drawing and verify valve positions. After testing, account for temporary spools, blanks, caps, hoses and instruments, then sign off restoration before filling. Gas and hydrostatic pressure tests require their own procedures; one cannot casually replace the other.
References: Open Compute Project: Guidelines for Pre-Commission Preparation of Technology Cooling System Row Manifolds
How do you know every branch has been flushed?#
Cleaning targets the contamination identified in the treatment plan. Flushing removes loosened debris and treatment residue. Agree the compatible chemistry, procedure-water quality, flow and disposal first. Use passivation only where the materials and approved plan require it.
Total header flow can look correct while a closed branch receives none. Keep a branch schedule with valve lineup, achieved flow, duration, filter checks and samples. Identify dead legs, high points and future connections. If a section cannot be reached, resolve it before claiming full coverage.
Define the endpoint first. Clear appearance, stable conductivity and elapsed time answer limited questions. Combine the specified chemistry, residue and particle assessments. Retain failed results with corrections and retests so the record explains acceptance.
| Evidence | What it can establish | What it cannot establish alone |
|---|---|---|
| Branch flow record | Required circulation reached that branch | All debris has left it |
| Filter inspection and differential pressure | Collected debris and loading at recorded conditions | Absence of particles below capture capability or in isolated volumes |
| Conductivity trend | Ionic response under a defined temperature basis | Particle count or complete chemistry |
| Turbidity or particle assessment | The sample's measured optical or particle property | Dissolved chemistry or the condition of internal surfaces |
| Laboratory chemistry report | Requested analytes in the submitted sample | Every contaminant or hydraulic performance |
| Sample-location record | Collection point and operating conditions | Branches excluded from circulation |
When a branch is missing from the flush record
If header conductivity meets its limit but a future rack branch has no circulation record, keep that branch's release open. Verify its valve lineup, complete the approved flushing procedure and collect the required evidence before release. Record the branch identity and results in the acceptance package.
Is the fluid in the loop the fluid you approved?#
Check supplier, formulation, batch and concentration at the final fill. Obtain compatibility approval for factory-filled equipment before its fluid joins the loop. Residual test water can alter the mixture, so verify concentration after circulation rather than relying only on the delivery certificate.
Follow the equipment fill and vent procedure, recording completed vent locations and stable circulation. OCP's modular TCS guidance addresses air and contamination when information technology (IT) equipment is added. Each connection needs a defined fill and verification method.
Collect final-fluid samples at agreed points under recorded circulation. Follow laboratory instructions for containers, preservation, transport and holding times. Label the loop, point, time, operating state and recent additions. Side-stream observations represent fluid reaching that location, not a disconnected branch.
For delayed startup, use the approved preservation plan and restart checks. Storage conditions, standing-water risks and additive distribution depend on the selected fluid. Retain the plan with the fill records.
Does the loop deliver cooling under a known load?#
Agree the load cases and stabilization periods with the design authority. Cover minimum stable load, intermediate load, design duty and specified equipment-unavailable cases. If production IT is absent, use an approved clean test load and protect the accepted fluid condition.
Record branch flow, differential pressure, supply and return temperatures, fluid, load, valve lineup, pump speed and filter condition on one timeline. Retain instrument verification and accuracy details. The heat balance below provides a cross-check.
Later pressure changes need comparison at similar flow and conditions. Valve position, flow, air and fouling can all change the reading. Commissioning provides the starting evidence for that investigation, rather than a single diagnosis.
Cross-checking the heat transferred
At a steady water flow of 600 L/min and a density of 1,000 kg/m3, mass flow is 10 kg/s. With a specific heat of 4.18 kJ/(kg K) and an 8 K temperature rise, the loop transfers about 334 kW of heat. If the expected liquid load differs materially, check stability, instruments, sensor placement and load allocation before acceptance.
heat transferred = mass flow x specific heat x temperature rise = 10 x 4.18 x 8 = 334.4 kWUse the approved fluid properties at test temperature and account for instrument uncertainty. Electrical test-load input can include heat that leaves through air cooling and other paths; compare the calculation with the heat allocated to the liquid loop.
Will the right person see and respond to an alarm?#
Follow each point from field device to screen, history and notification. Check units, sign, scaling, timestamps, priority, invalid-data handling and asset identity. A correct CDU display cannot prove a gateway has mapped the point correctly.
Use approved simulations or safe test methods for loss of flow, sensor faults, pump unavailability, leak indications and communication loss. Verify the authorized response, recovery conditions and reset. Test the sequence without creating an actual hazardous event.
ASHRAE recommends bringing monitoring into commissioning early enough to capture baselines. Retain the event timeline, acknowledgments, actions and operator observations so the team can review what happened.
References: ASHRAE: Commissioning and Performance Validation
What will operators need on the first service call?#
Record unresolved findings with their boundary, consequence, operating restriction, owner and due date. The designated authority decides whether the system can enter production. Putting an item on a punch list does not resolve it.
Deliver the as-built piping and instrumentation diagram (P&ID), limits, fluid inventory, test and cleaning records, laboratory reports, instrument checks, trends, alarms and procedures. Train operators at the actual valves and sample points, including filter service and sampling.
Agree which changes require review or partial recommissioning: pipework rework, added branches, changed fluids, controls or equipment. Link each change to its tests and revised baseline. The release record below makes the accepted boundary and remaining limitations clear.
Boundary release record
SYSTEM AND BOUNDARY: [loop, valves, racks and drawing revision]
APPROVED REQUIREMENTS: [documents and acceptance matrix revision]
CLEANING AND TEST RECORDS: [record identifiers and dates]
FINAL FLUID: [supplier, formulation, batch, concentration and sample report]
OPERATING BASELINE: [load, flow, temperatures, pressure and trend reference]
OPEN ITEMS: [item, consequence, restriction, owner and disposition]
RELEASE DECISION: [accepted, conditionally accepted or held]
AUTHORITY AND WITNESSES: [names, roles and date]
RETEST TRIGGERS: [changes requiring review before operation]Common questions
When is a liquid cooling loop ready to connect to servers?
When the designated authority accepts that boundary against its mechanical, cleanliness and fluid requirements, with the connection procedure ready. A passing header sample alone cannot establish branch readiness.
Can the CDU and server cold plates be used to flush construction pipework?
Construction flushing can expose sensitive components to debris, chemistry and unsuitable pressure or flow. Use the approved isolation and bypass, with written supplier approval for any variation.
Is a stable conductivity reading enough to accept a clean loop?
No. Conductivity does not prove particle cleanliness, identify all constituents or show branch coverage. Apply the complete acceptance matrix, including the specified chemistry and debris assessments.
What must be repeated after adding a new cooling branch?
Review the changed boundary with the design authority and OEMs. Agree its integrity, cleanliness, fill, performance and functional tests, then update the as-built record and operating baseline.
Sources and further reading
- Commissioning and Performance ValidationASHRAE
- Guidelines for Pre-Commission Preparation of Technology Cooling System Row ManifoldsOpen Compute Project
- Modular Technology Cooling System for Cloud Scale: Design and Delivery of Liquid to Rack Distribution Systems, Version 1.0Open Compute Project
- XDU1350 Coolant Distribution Unit Application and Planning GuideVertiv
Reliability Engine
Connect coolant condition to operating decisions
Reliability Engine supports commissioning investigations by combining side-stream coolant-condition information with available loop, CDU and GPU context. Establish a baseline that operations can reuse, while retaining laboratory testing and the project's witnessed acceptance process.