Technical guidePDF2026

Guidelines: Impact of Strategies on Data Center Energy Consumption, Carbon Footprint, and Water Consumption (March 2026)

Open Compute Project Foundation · Sean Barlett, Jaime Comella et al.

An OCP guideline on the trade-offs between energy, site and source water, carbon and water scarcity across data center cooling, siting and heat reuse strategies. It ends in qualitative summary tables and hypothetical 1 MW worked examples, not benchmarks.

CC BY-SA 4.0 — share with attribution under the same licence

On this page

Overview

The guideline argues that improving one metric often worsens another, so energy, carbon and water, including water scarcity, must be assessed together. It starts by categorising cooling. For the IT, air cooling still dominates, while liquid cooling, either direct-to-chip or immersion, is growing because AI training campuses have passed the gigawatt scale with racks above 100 kW. For the facility, heat moves through refrigerant, water or air, split into evaporative systems (direct and indirect evaporative coolers, water-cooled chillers with wet towers, chiller-less systems with wet towers) and non-evaporative ones (DX, air-cooled chillers, dry towers). Running the technology cooling loop at 40-50 °C is said to allow dry coolers almost everywhere for most of the year.

The energy and water chapter explains that non-evaporative systems use more electricity in hot weather while evaporative ones hold electricity steady but use more water as wet-bulb temperature rises, and that comparing design-day values is misleading. Economization is a mode of operation with air-side, water-side and refrigerant-based forms. Air-side economization achieves 85-95% of wet bulb depression, water-side with towers 70-75%, so air-side offers more hours. Total operational water includes on-site consumption (Scope 1) and water used to generate electricity (Scope 2). Water stress is handled through a water scarcity footprint, using the AWARE factor, and a proposed water scarcity usage effectiveness (WSUE), with facility location treated as a major factor.

Later sections cover energy and carbon for traditional and AI data centers, mitigation through reference designs, liquid cooling, strategic siting, power purchase agreements and workload optimisation, and waste heat reuse in two scenarios, unmodified heat and heat upgraded by compression. Waste heat can also support water reclamation and carbon recovery. Summary tables show each strategy as a major or minor increase or decrease in energy, carbon, water and scarcity. These are qualitative and the authors say many strategies improve one area at the cost of another. Values in the worked examples are described as illustrative, not measured.

The examples are 1 MW cases. In Phoenix, waterless CRAC cooling at PUE 1.6 (EWIF 8.3 L/kWh) is compared with evaporative cooling at PUE 1.2 and WUE 1.8 L/kWh, cutting Scope 1 and 2 water from 120 to 104 million L/yr and emissions from 3,500 to 2,700 t CO2/yr. Florida versus Colorado shows PUE 1.79 against 1.61, but water scarcity footprint of 30 versus 1,300 million L/yr and emissions of 12,400 versus 14,400 t. Heat recovery with vapor recompression and a LiBr absorption chiller (270 kW input, 510 kW cooling) and a DC distribution case (PUE 2.16 against 1.89 at 300 kW IT) complete the set.

Key points

  1. Running the technology cooling loop at 40-50 °C allows dry air coolers for most of the year almost everywhere, removing compression cooling.
  2. Air-side economization achieves 85-95% of wet bulb depression; water-side with evaporative towers 70-75%, so air-side offers more economizer hours.
  3. Non-evaporative systems use more electricity in hot weather; evaporative systems have steadier electricity but more water use as wet bulb rises.
  4. Total operational water adds on-site consumption (Scope 1) to water used in power generation (Scope 2, via the energy water intensity factor).
  5. Water scarcity footprint multiplies water footprint by a scarcity indicator such as AWARE; WSUE is proposed as scarcity-weighted water per IT energy.
  6. Phoenix example (1 MW): waterless CRAC at PUE 1.6 versus evaporative at PUE 1.2 and WUE 1.8 L/kWh cuts total Scope 1 and 2 water from 120 to 104 million L/yr.
  7. Same example: emissions fall from 3,500 to 2,700 t CO2/yr with the carbon factor of 0.26 kg CO2/kWh.
  8. Florida versus Colorado (1 MW): PUE 1.79 versus 1.61 saves 1.6 million kWh/yr, but water scarcity footprint is 30 versus 1,300 million L/yr and emissions 12,400 versus 14,400 t/yr.
  9. Waste heat recovery example: a 270 kW compressor plus LiBr absorption chiller gives 510 kW of cooling for other loads; a DC distribution example shows PUE 1.89 against 2.16.
  10. The worked examples are hypothetical and illustrative, not benchmarks; the summary tables are qualitative.

Using it in design

  • Evaluate cooling and siting options on energy, carbon, site water and water scarcity together, not on PUE or WUE alone.
  • Use the EWIF (for example 8.3 L/kWh at Phoenix in the paper) with PUE to add source water to site WUE when comparing waterless against evaporative cooling.
  • Compare economization options by their share of wet-bulb depression and local climate, and select IT inlet or liquid temperatures that allow dry cooling for most hours.
  • Add water scarcity weighting for the actual location before concluding that a cool, dry site is better.
  • Explore waste heat reuse and its effect on mechanical cooling hours in the energy and water comparison.
  • Run a worked 1 MW comparison with the paper's method before committing to a site or cooling concept, and replace its illustrative inputs with project data.

Monthly newsletter · free

Keep your reading list current

Once a month: new library sources, changes to Turkish regulations and upcoming data centre events.

SoSo CAD

Check cooling capacity alongside your design

Review zone heat loads, available capacity and the capacity balance after the largest unit is lost in SoSo CAD.

Request a demo
Zone heat loads and capacity balance in the SoSo CAD cooling workspace

Who should read it

Planners, sustainability leads and mechanical designers comparing cooling, siting and heat reuse strategies against energy, carbon and water goals.

Document contents

  1. Executive Summary
  2. 1. Overview of Cooling Strategies
  3. 1.1 Cooling the ITE
  4. 1.1.1 Air-Based ITE Cooling
  5. 1.1.2 Liquid ITE Cooling
  6. 1.1.3 Other Cooling Strategies
  7. 1.2 Facility Cooling
  8. 2. Interplay Between Energy, Water, and Carbon
  9. 2.1 Relationship Between Energy and Water
  10. 2.1.2 Economization of Site Cooling Systems
  11. 2.1.4 Water Stress
  12. 2.1.5 Facility Location
  13. 2.2 Relationship Between Energy and Carbon Footprint
  14. 2.3 Relationship Between Waste Heat Reuse and Energy, Water, and Carbon
  15. 2.4 Summary Tables of Interplay
  16. 3. Examples to Illustrate Interplay
  17. 4. Compliance with Open Compute Project Tenets
  18. 5. Conclusion
  19. 6. Glossary

Read the document

ocp-dcf-water-heat-energy.pdf

PDF · 2.8 MB · English

CC BY-SA 4.0 — share with attribution under the same licence

The document is provided unaltered because its licence permits redistribution.

Publication details

Authors
Sean Barlett; Jaime Comella; Cosimo Pecchioli; Kially Ruiz; Aaron P. Wemhoff; Joel Zemanek
Publisher
Open Compute Project Foundation
Year
2026
Document language
English
Source type
Industry body
Access
Open licence — downloadable
Licence
CC BY-SA 4.0 — share with attribution under the same licence
Licence evidence
www.opencompute.org
Original licence note

License section of the document states Creative Commons Attribution-ShareAlike 4.0. Attribution required; derivatives/adaptations must stay CC-BY-SA.

Citation

Sean Barlett; Jaime Comella; Cosimo Pecchioli; Kially Ruiz; Aaron P. Wemhoff; Joel Zemanek (2026). Guidelines: Impact of Strategies on Data Center Energy Consumption, Carbon Footprint, and Water Consumption (March 2026). Open Compute Project Foundation. https://www.opencompute.org/documents/dcf-water-heat-energy-2026march-pdf

All content and rights belong to the respective authors and publishers. SoSo CAD provides only the citation, its own summary and a link to the source, and is not responsible for the sources' content.