Home / Guides / Data centers

Data-Center Liquid Cooling: Flush-and-Fill Planning

Plan cooling-loop preparation with clear boundaries, compatible fluids, acceptance tests and handover records before connecting liquid-cooled IT equipment.

US Liquid Cooling editorial · Reviewed · 4 min read

Flushing a new data-center cooling network is not the same task as filling it with final coolant. Preparation removes construction residue and establishes a clean, compatible fluid path. Filling introduces the specified operating fluid under controlled conditions. Both need acceptance criteria before IT equipment is exposed to the circuit.

Treat this as a coordinated facilities-and-IT activity, with responsibilities agreed among the piping contractor, CDU supplier, fluid supplier and server OEM.

Define exactly which circuit is being prepared

Mark facility piping, technology cooling-system row manifolds, rack manifolds, hoses and IT assemblies on a boundary drawing. Identify which are new, factory-prepared, transported wet or dry, and already in service.

The Open Compute Project's TCS row-manifold pre-commissioning guidelines address preparation of that infrastructure. A document covering row manifolds should not be treated as approval to flush every server cold plate using the same method.

Confirm the equipment that must be isolated or bypassed during each stage. Include instruments and filters that could be damaged by the preparation process.

Agree cleanliness before choosing a cart

Ask the relevant suppliers to define what a prepared system must achieve. Depending on the installation, the acceptance schedule may cover particulate condition, fluid chemistry, concentration, appearance, approved materials and documentation.

The target should specify the test method, sample locations and the party authorized to accept the result. A statement such as “flush until clean” leaves too much room for disagreement at handover.

OCP's chemical-perspective webinar treats flushing, commissioning and ongoing fluid analysis as connected subjects. That is a useful reminder that a clear-looking sample does not answer every chemistry question.

A flush-and-fill cart is part of a procedure

Evaluate the cart against the approved process: compatible wetted materials, available flow and pressure, filtration, sampling, draining and connection arrangements. Include the complete temporary circuit in the pressure and cleanliness review.

Do not select a high-flow pump and assume that more flow is always better. The piping, hoses, valves and any connected equipment have limits. A preparation procedure that exceeds them creates a new risk while trying to remove contamination.

Record which carts, hoses and containers are dedicated to the specified fluid. Uncontrolled reuse can introduce a different chemistry into an otherwise prepared loop.

Keep a staged record

Use a project-specific sequence rather than a generic field recipe:

StageEvidence to retain
Boundary and compatibility reviewApproved drawing, isolated equipment and supplier requirements
Cleaning or flushingApproved fluid or cleaner, process conditions and waste handling
Rinsing where requiredMethod and evidence that cleaner residue meets acceptance criteria
Final fill and air removalFluid batch, concentration, amount added and completion checks
Sampling and acceptanceResults, sample points, instruments and sign-off
Operational handoverBaseline measurements, maintenance plan and outstanding actions

The exact order and parameters must come from the approved design and equipment procedures. This table is a documentation framework, not a chemical cleaning specification.

Watch the interfaces between factory and site work

A factory-tested rack may arrive with residual fluid, transport protection or specified storage conditions. Those details affect what happens when it joins the site network.

OCP's liquid-cooling integration and logistics white paper discusses integration across those stages. Obtain the supplier's shipping and site-connection requirements rather than assuming a delivered assembly is ready for immediate circulation with any site coolant.

For mixed-vendor deployments, close disagreements about fluid type, preparation and acceptance before connecting the systems. “The other contractor normally handles it” is an unresolved interface, not a handover plan.

What should the final acceptance establish?

It should establish that the defined circuit meets the agreed preparation criteria, contains the specified fluid, has completed the required checks and is authorized to enter the next stage. Keep any temporary strainers, bypasses or sampling arrangements visible in the handover record.

Capture the initial pressure, flow, temperatures and fluid-analysis results under known conditions. Those baselines help distinguish a later change from a problem present at startup.

Read our cold-plate coolant-quality guide for ongoing monitoring and the commissioning handover guide for responsibility and operational records.

Sources & further reading

Use the manufacturer’s instructions for your exact equipment. Read our editorial policy or suggest a factual correction.

Explore the company directory → · All liquid-cooling guides →

01
Data centers

Plan a liquid-cooling commissioning handover

Define acceptance evidence, operating checks, documentation, and ownership before a liquid-cooled installation enters service.

↗
02
Data centers

CDU Approach Temperature: Read the Capacity Rating

Learn what CDU approach temperature means, separate it from loop temperature rise, and compare capacity quotes using the same fluids and design conditions.

↗
03
Data centers

Data-Center Liquid Cooling: Leak Detection and Response

Plan leak sensing, containment and isolation together. Compare pressure architectures and define alarm responses, fault tests and cooling continuity.

↗

Directory matches are starting points for research. Confirm product fit and availability with the company.