Issues, solutions, and case studies for closed-loop-cooling
Where a community has rezoning leverage, convert it into a binding agreement with numeric terms: decibel limits at named receptor addresses, an annual water cap, disclosed load, local hire percentages with a definition of local, and payments — all with funded, non-judicial enforc
Fill the cooling loop once and reject heat mechanically instead of by evaporation, eliminating ongoing water draw. Microsoft claims this avoids over 125 million litres per facility per year. The trade is electricity, and no operator has published the PUE penalty.
City of Lancaster with the data-center developer, and a local community group · since 2026 · City
One of the first substantial community benefit agreements attached to data-center development in the United States, covering three facilities totalling roughly 2 million square feet, with a 20-year term. Financial terms…
$20.3M · Developer commitments totalling $20.25 million over 20 years · 1 source
Microsoft · since 2024 · City
Microsoft announced its closed-loop, zero-water-evaporation datacentre design in December 2024, naming Mount Pleasant, Wisconsin and Phoenix, Arizona as the first sites, with further builds coming online from late 2027.…
Microsoft · 3 sources
Google, with Uruguay's Ministry of Environment · 2023–2024 · City
Google's original Canelones facility design required approximately 7.6 million litres of potable water per day for evaporative cooling. During Uruguay's 2023 drought, Montevideo's utility blended brackish estuary water…
2 sources