Fluid-to-Facility™ | Data Center Water & Thermal Management Framework
The 8 Pillars of an Integrated Data Center Cooling Strategy
How an integrated water and thermal strategy can strengthen cooling reliability, resource efficiency, and long-term resilience.
AI and high-density computing are changing the demands placed on data center cooling infrastructure. Apex’s Fluid-to-Facility™ framework approaches water, fluids, cooling infrastructure, commissioning, and lifecycle performance as one connected strategy.
THE COOLING ECOSYSTEM
Data center cooling is becoming a system-of-systems challenge.
As rack densities and heat loads rise, data centers are increasingly combining evaporative, dry, or hybrid heat rejection with closed-loop water and glycol systems, heat exchangers, coolant distribution units (CDUs), and technology-side coolant loops. These components may be designed, installed, and managed by different teams, but they operate as one thermal system. Reliability depends on how effectively the interfaces between them are planned, commissioned, monitored, and maintained.
01 Capture Heat
Remove heat from IT equipment, including direct-to-chip liquid cooling and other high-density cooling approaches.
02 Transport Heat
Move heat through the facility with closed-loop water, glycol, pumps, heat exchangers, and associated controls.
03 Reject Heat
Transfer heat to the environment through evaporative, dry, hybrid, district, or other heat-rejection infrastructure.
That cooling ecosystem view is especially important for EPCs, general contractors, mechanical contractors, and commissioning teams. Decisions made during design and construction can directly affect flushing velocity, system cleanliness, drainage, air removal, sampling access, final fluid quality, controls validation, and the quality of the operating baseline handed to the owner.
FLUID-TO-FACILITY™ FRAMEWORK
Explore the 8 Pillars
Reliable AI driven data center cooling depends on far more than one cooling tower, glycol loop, or treatment program. The Apex Fluid-to-Facility™ framework connects the full water and thermal lifecycle.
01 – Design for the Entire Lifecycle
02 – Start with Source Water and Pretreatment
03 – Optimize Cooling Tower Performance
04 – Protect Closed-Loop Water and Glycol Systems
05 – Treat Water Reuse as a Strategic Resource
06 – Design Water Safety into Every System
07 – Connect Through Intelligent Monitoring
08 – Integrate Water and Thermal Management
Design for the Entire Lifecycle
The most effective cooling strategies do not begin at startup—they begin during design. Early decisions around water quality, materials of construction, cleaning and flushing provisions, filtration, sampling, controls, testing, and acceptance criteria influence whether a system can be efficiently commissioned, maintained, expanded, and optimized.
For project teams, this means commissioning requirements should not be treated as a late-stage activity. The design should anticipate how systems will be filled, drained, vented, circulated, filtered, sampled, and verified before turnover. It should also account for maintainability, isolation, equipment access, and future modifications so that the facility is not forced into costly field workarounds later.
A lifecycle approach also improves coordination among design engineers, mechanical contractors, commissioning providers, and owner representatives. When water-quality requirements, fluid specifications, system-cleanliness expectations, temporary filtration needs, and acceptance criteria are defined early, construction and startup teams have a much clearer path to delivering the system as intended.
Commissioning begins during design.
Define water-quality and coolant requirements, cleaning and passivation provisions, sampling locations, temporary filtration, controls, startup sequences, and acceptance criteria before installation begins.
Start with Source Water and Pretreatment
Every downstream water system begins with source-water quality. Hardness, silica, chlorides, iron, suspended solids, and biological contaminants can influence cooling towers, heat exchangers, closed loops, and other equipment. Municipal water can also vary seasonally, so a single historical sample may not fully represent the conditions a facility will experience over time.
Pretreatment should therefore be selected based on actual source-water conditions, cooling architecture, equipment requirements, and reuse objectives. Depending on the application, this may include multimedia or cartridge filtration, softening, reverse osmosis, ultrafiltration, activated carbon, deionization, and advanced monitoring and automation.
For EPC and contractor teams, pretreatment should be coordinated with downstream system requirements before startup. The goal is not simply to install treatment equipment, but to verify that the quality and quantity of treated water are suitable for cooling towers, closed-loop fills, technology-side systems, and any planned reuse applications.
Optimize Cooling Tower Performance
For facilities using evaporative cooling, long-term performance depends on more than mechanical operation. Water chemistry, blowdown control, biological control, filtration, instrumentation, inspection, and cleaning all affect reliability and efficiency.
A cooling tower should not be considered fully commissioned until mechanical operation, water chemistry, controls, blowdown, biological control, and baseline thermal performance have been verified together. That creates a more complete starting point for operations and makes it easier to distinguish construction or startup issues from later operating changes.
Continuous monitoring can provide earlier visibility into changing conditions, while deposit control, side-stream filtration, microbiological management, and routine physical inspection help protect heat-transfer surfaces and reduce fouling. No single treatment activity replaces the need for coordinated mechanical and water-management practices.
- Continuous monitoring
- Deposit control
- Microbiological control
- Side-stream filtration
- Routine inspection and cleaning
Protect Closed-Loop Water and Glycol Systems
Closed loops are a critical thermal bridge in modern AI and high-density data centers. Facility-side loops and technology-side loops may have different fluid requirements, with a CDU or heat exchanger transferring heat between them while keeping fluids hydraulically separated.
The facility side typically carries water or inhibited glycol between chillers, pumps, heat-rejection equipment, heat exchangers, and CDUs. The technology side circulates the manufacturer-specified coolant through racks, manifolds, and cold plates. Because each loop may have different chemistry, cleanliness, temperature, pressure, and material-compatibility requirements, the interface between them must be clearly understood.
Closed-loop reliability is often determined before the system ever reaches normal operation. Construction debris, residual cleaners, poor air removal, unverified chemistry, or contamination introduced during filling can become long-term operating problems if they are not identified before turnover.
Treat Water Reuse as a Strategic Resource
Potential sources include cooling-tower blowdown, reverse-osmosis reject, condensate, rainwater, process water, and reclaimed wastewater. The right reuse strategy depends on local conditions, treatment requirements, downstream compatibility, economics, discharge constraints, and facility objectives.
Water reuse should be considered as part of the cooling strategy rather than as an isolated sustainability project. Recovered water can affect pretreatment requirements, cooling-tower chemistry, scaling potential, biological control, wastewater volumes, and the overall balance between water and energy use.
For new campuses and expansions, evaluating reuse during planning and design creates more flexibility than adding it after the facility is operating. Space, piping, treatment capacity, storage, controls, and monitoring can then be incorporated into the original project rather than retrofitted later.
Design Water Safety into Every System
Water safety should be considered wherever operations include open recirculating systems, stored water, domestic water, or conditions that may support microbiological growth. A comprehensive program may include risk assessment, flow and temperature management, microbiological monitoring, cooling-tower hygiene, validation, and documentation.
For project teams, water-safety provisions should be coordinated with equipment access, sampling points, treatment and disinfection capabilities, operating procedures, and documentation requirements. These considerations are easier to address during design and construction than after systems are placed into service.
Water safety is also connected to broader cooling performance. Poor flow, stagnant areas, inadequate monitoring, or inconsistent maintenance can create both operational and microbiological risks, which is why the framework treats water safety as part of the overall lifecycle strategy.
Connect Everything Through Intelligent Monitoring
Integrated monitoring can combine data from cooling towers, closed-loop systems, direct-to-chip infrastructure, pretreatment, chemical feed, water-quality sensors, utility consumption, laboratory analysis, and remote equipment monitoring. Trending helps teams identify changing conditions earlier and support more informed operating decisions.
For new projects, monitoring requirements should be established before startup so that the right sensors, sampling points, meters, alarms, and communication pathways are available when the system is commissioned. BAS or DCIM integration, where appropriate, can improve visibility across mechanical and water systems.
A strong commissioning baseline is especially valuable. Recording water chemistry, coolant condition, flow, temperature, pressure, differential pressure, and thermal performance gives operators a reference point for future troubleshooting, optimization, and expansion.
Adopt an Integrated Water and Thermal Management Strategy
The largest opportunity is not optimizing one cooling tower, one glycol loop, or one CDU. It is understanding how source water, pretreatment, heat rejection, closed-loop fluids, liquid cooling, water reuse, safety, monitoring, laboratory validation, and lifecycle services work together.
When these systems are managed independently, problems can migrate across interfaces. Source-water conditions can affect pretreatment; pretreatment affects cooling towers and fill water; construction cleanliness affects closed-loop performance; fluid quality affects heat exchangers and CDUs; and monitoring determines how quickly changes are detected.
An integrated strategy gives project teams a common framework for coordinating design intent, construction practices, startup procedures, operating baselines, and long-term optimization. That can reduce project risk while supporting uptime, equipment protection, resource efficiency, and future scalability.
WHY THIS MATTERS FOR PROJECT DELIVERY
Cooling reliability is built across handoffs.
Data center cooling projects involve multiple handoffs: from design to procurement, installation, startup, commissioning, and eventually operations. Each handoff creates an opportunity for requirements to be lost, interpreted differently, or addressed too late.
A lifecycle framework helps connect those handoffs. Design teams define the water, fluid, cleanliness, monitoring, and acceptance requirements. Contractors install systems so they can be properly flushed, drained, vented, filtered, and serviced. Commissioning teams verify mechanical integrity, controls, fluid condition, and baseline performance. Operations teams then inherit a documented starting point instead of an unknown system condition.
For EPCs, general contractors, and mechanical contractors, this is where Fluid-to-Facility™ can support stronger project execution: by treating water and thermal management as a continuous scope rather than a collection of separate late-stage tasks.
MYTH VS. REALITY
Can an AI data center really be “water-free”?
Low-water and water-free cooling strategies can significantly reduce or eliminate onsite evaporative water use. However, every data center must still reject heat through dry, evaporative, hybrid, or district cooling infrastructure, and the electricity powering the facility may carry an upstream water footprint. Water use may therefore be reduced onsite, eliminated from certain processes, or shifted elsewhere in the cooling and energy ecosystem.
MYTH
AI data centers can operate without water.
REALITY
Dry and hybrid cooling can reduce onsite water consumption, but every facility must still reject heat. The more useful engineering question is how to optimize water, energy, and heat rejection together.
THE FUTURE OF DATA CENTER COOLING
The future is integrated.
There is no single cooling architecture that fits every facility. The challenge is selecting and managing the right combination of heat capture, heat transport, heat rejection, water, coolant, controls, and monitoring for each site’s climate, infrastructure, IT load, water availability, operational requirements, and growth plans.
As direct-to-chip liquid cooling expands, facility-side water and glycol systems will remain critical because the heat removed from CPUs and GPUs still has to move through CDUs, heat exchangers, pumps, and heat-rejection equipment. That makes fluid quality, system cleanliness, corrosion protection, filtration, and instrumentation increasingly important to overall thermal performance.
The most resilient facilities will manage water, energy, and thermal performance as one connected system, while keeping the flexibility to adapt to new rack densities, cooling technologies, expansion requirements, and local resource constraints.
MOVE FROM STRATEGY TO EXECUTION
Take the framework into your next project.
The Fluid-to-Facility™ Data Center Cooling Lifecycle Checklist translates the framework into practical guidance for EPCs, general contractors, mechanical contractors, commissioning teams, and engineers—supporting informed decisions from early planning and design through commissioning, ongoing operations, and optimization.
LIFECYCLE SUPPORT
Fluid-to-Facility™. One partner across the data center cooling lifecycle.
Apex supports integrated water, fluid, and thermal management from early planning through long-term operations. Our objective is to help project and operations teams connect design intent, system cleanliness, fluid quality, commissioning requirements, monitoring, and lifecycle performance across the entire cooling system.
Plan
Source-water analysis, feasibility, risk assessment, cooling-fluid strategy, water & engergy conservation, and lifecycle planning.
Design
Pretreatment support, cooling-tower strategy, fluid requirements, instrumentation, maintainability, and commissioning criteria.
Build
System-cleanliness planning, flushing, cleaning, passivation, temporary filtration, and equipment protection.
Startup & Commissioning
Final cleaning, filling, air removal, chemistry verification, controls validation, baseline analysis, and turnover support.
Operate
Water treatment, coolant management, laboratory services, remote monitoring, water safety, preventive maintenance, and field support.
Optimize
Performance assessment, reuse, treatment optimization, WUE and energy improvement, trending, expansion, and retrofit support.
FREQUENTLY ASKED QUESTIONS
Data center cooling questions
What is a closed-loop cooling system?
A closed-loop cooling system continuously circulates the same water, inhibited glycol, or engineered coolant through a contained piping network to transport heat. Because the fluid is recirculated rather than continuously replaced, maintaining proper fluid chemistry, cleanliness, corrosion protection, and filtration is essential for reliable heat transfer and long-term protection of pumps, heat exchangers, CDUs, and other cooling equipment.
Why are cooling towers still used in AI data centers?
Cooling towers are still widely used because they provide highly energy-efficient heat rejection, especially for large data centers with significant cooling loads. Even as AI facilities adopt direct-to-chip liquid cooling, the heat captured from servers still has to be transferred and ultimately rejected to the environment; in many climates, evaporative cooling towers can provide an effective balance of cooling capacity and energy performance. Dry and hybrid systems may be preferred where reducing onsite water consumption is a greater priority.
Do liquid-cooled data centers eliminate water use?
Not necessarily. Direct-to-chip liquid cooling can reduce reliance on room-level air cooling and, when paired with dry heat rejection, may reduce onsite evaporative water use. However, the heat generated by IT equipment still must be rejected through dry, evaporative, hybrid, or district cooling infrastructure, and electricity generation may also carry an upstream water footprint. The broader goal is to optimize water use, energy efficiency, and heat rejection together rather than assume liquid cooling eliminates water use entirely.
What is the difference between the facility water loop and the technology cooling loop?
The facility water loop circulates water or inhibited glycol through the building’s cooling infrastructure—including chillers, pumps, heat-rejection equipment, heat exchangers, and CDUs—to transport heat across the facility. The technology cooling loop circulates manufacturer-specified coolant between the CDU and IT equipment, including manifolds and cold plates serving CPUs and GPUs. A CDU or heat exchanger transfers heat between the two loops while keeping the fluids hydraulically separated, allowing each loop to maintain the chemistry and operating conditions appropriate for its equipment.
How often should closed-loop glycol be tested?
Testing frequency should be based on system criticality, fluid type, operating conditions, treatment program, and equipment requirements. Routine testing should monitor facility-side closed loop fluid chemistry, corrosion protection, contamination, cleanliness, and overall fluid condition, with more frequent testing when operating conditions or system history indicate increased risk.
Technology-side cooling loops should be monitored and tested according to the coolant and equipment manufacturer’s requirements, since fluid specifications can vary by CDU, cold-plate design, metallurgy, and coolant type. Testing should verify that coolant chemistry, cleanliness, contamination, and fluid condition remain within the requirements established for the liquid-cooling equipment.
What is Water Usage Effectiveness (WUE)?
Water Usage Effectiveness (WUE) is a data center sustainability metric developed by The Green Grid that measures the amount of water a facility consumes relative to the energy used by its IT equipment. WUE helps operators evaluate water efficiency and compare cooling strategies, while recognizing that water use should be considered alongside energy efficiency, cooling reliability, and local water availability.
What is the Fluid-to-Facility™ framework for data center cooling?
Fluid-to-Facility™ is Apex’s integrated lifecycle approach to data center cooling, connecting water, cooling fluids, thermal infrastructure, and operational performance across the entire facility lifecycle—from planning and design through construction, commissioning, operations, optimization, and expansion. Rather than managing cooling systems in silos, the framework brings together source water, pretreatment, heat rejection, closed-loop water and glycol systems, liquid cooling, water reuse, monitoring, and ongoing optimization to improve cooling reliability, efficiency, and long-term resilience.
Fluid-to-Facility™
Lifecycle Cooling Assurance for Data Centers.
Connect water, fluid, and thermal management from planning through long-term operations.