Operating Principle: Seasonal Cycles
Why seasonal cycling is the whole point of ATES
A facilities manager gets a call in late August: the building’s cooling costs are spiking during afternoon peaks, and the chiller plant is running harder than expected. Six months later, that same building struggles to heat efficiently on cold mornings—despite having “a seasonal storage system” underground. When this happens, the root issue is often not a broken pump or undersized heat exchanger. It’s that the seasonal cycle—the predictable rhythm of charging and discharging warm and cold storage—has become fuzzy, leaky, or unbalanced.
ATES only pays off when it behaves like a seasonal thermal battery. That means it needs a repeatable operating pattern: store useful cold from winter to spend in summer, and store useful heat from summer to spend in winter. If you don’t run the cycle cleanly, the aquifer gradually becomes “lukewarm everywhere,” and the mechanical plant quietly takes back the work (and the electricity bill).
This lesson explains the operating principle behind that seasonal rhythm: what “charging” and “discharging” actually mean in an open-loop groundwater system, why balance matters across a full year, and how real buildings handle messy shoulder seasons without destroying storage quality.
The core seasonal logic: charge, store, discharge—without mixing
Three terms drive almost every operating discussion in ATES:
-
Charging: operating the system so the aquifer is intentionally loaded with heat (warm well) or cold (cold well) for later use.
-
Discharging: operating the system so the aquifer’s stored warm or cold is withdrawn to meet building loads.
-
Annual balance (thermal balance): keeping the net heat stored and net cold stored over a year from drifting too far in one direction, which protects long-term performance.
The underlying principle stays simple: ATES is an open-loop system where you extract groundwater, pass it through a heat exchanger (HX) to interact with the building loop, then reinject it—usually into the opposite well to “deposit” the season’s byproduct. In summer cooling mode, you typically extract from the cold well, absorb building heat across the HX, then reinject that warmed groundwater into the warm well. In winter heating mode, you reverse: extract from the warm well, deliver heat (directly and/or via a heat pump), and reinject cooler water to the cold well.
A useful mental model is the “two-account seasonal bank” from the previous lesson: you have a warm account and a cold account. Charging is making deposits; discharging is making withdrawals. The bank works only if deposits land in the right account and you avoid accidental transfers between them—underground, that “accidental transfer” shows up as thermal breakthrough / mixing, where warm and cold zones blend and your usable temperature difference shrinks.
How the seasonal cycle actually runs (and what can quietly derail it)
1) Summer operation: spending cold, banking heat
In summer, the building’s main job is rejecting heat. ATES turns that problem into a storage opportunity by treating the aquifer as the heat sink—but with a memory. Operationally, you extract groundwater from the cold well and run it through a heat exchanger that isolates groundwater from building water. On the building side, that HX can provide substantial cooling directly if the cold-well temperature is low enough, reducing compressor runtime and cutting peak electrical demand.
After the HX picks up building heat, the groundwater leaves warmer than it arrived. Instead of “dumping” that heat away, you reinject it into the warm well, intentionally charging warm storage for winter. This is why ATES is especially valuable where cooling loads are meaningful: summer cooling doesn’t just cost energy—it can also create winter-grade input heat if stored cleanly.
Two things commonly derail summer cycling. First is chaotic switching—frequent toggling between wells during mild days or mixed-mode operation, which encourages subsurface mixing and erodes the distinct warm/cold zones. Second is treating “free cooling” as unlimited; if you spend cold storage aggressively early in the season without a plan, you can hit late-summer heat waves with a warmed-up cold well, forcing chillers to carry the peak anyway. Best practice is to operate with predictable seasonal intent and manage cold storage as a constrained asset, not a free utility.
2) Winter operation: spending heat, rebuilding cold
Winter reverses the logic: the building needs heat, and ATES aims to deliver it from the warm well as efficiently as possible. You extract warmer groundwater and transfer that heat across the HX to the building loop. Where building systems can accept low-temperature heating, you can cover part of the load directly. When the supply temperature required by the building is higher than the warm well can provide, a heat pump typically stages in to “top up” temperature—crucially, starting from a warmer source than winter air, which improves efficiency.
After heat is removed, the groundwater is cooler. Reinjection now goes to the cold well, which is not just “where the water returns,” but how you deliberately rebuild cold storage for the next summer. This is a key beginner insight: winter heating is not only about meeting heating demand—it is also the primary mechanism for restoring the cold side so direct cooling remains available next year.
A major misconception shows up here: “Reinjection means the aquifer is unchanged.” In ATES, temperature is the stored product, so returning water at the wrong temperature (or to the wrong well) is changing the storage state. If winter operation under-delivers cold reinjection—because the system relies too heavily on boilers or because flow strategy is inconsistent—the cold well gradually warms year over year, and summer performance degrades even if nothing “breaks.”
3) Shoulder seasons: where good systems are made (or ruined)
Real buildings rarely have clean “summer-only cooling” and “winter-only heating.” Spring and autumn bring partial loads, simultaneous heating and cooling in different zones, and frequent setpoint changes from occupants. Shoulder seasons are where operators accidentally destroy seasonal storage value by running the system like an instant, daily source rather than a seasonal one.
A common pitfall is short-cycling wells based on momentary demand: a few hours of cooling triggers cold-well extraction, then the next morning’s heating triggers warm-well extraction, and back again. Each switch reshapes the subsurface plumes and can increase the risk of thermal breakthrough—the warm and cold zones “see” each other sooner and extracted temperatures drift toward each other. Controls can reduce this by enforcing operating windows, minimum run times, and temperature-based logic that preserves storage integrity.
The best practice is to treat shoulder seasons as a storage stewardship period. You still meet comfort needs, but you prioritize stable operation: choose a dominant mode for a day (or week), limit unnecessary reversals, and watch key indicators like well temperatures, flow rates, and HX approach temperature (a practical fouling signal). That discipline is what keeps the seasonal cycle clean enough that the aquifer remains a reliable battery instead of a slowly blending reservoir.
[[flowchart-placeholder]]
Seasonal modes compared (what changes, what stays the same)
| Dimension | Summer: cooling-driven cycle | Winter: heating-driven cycle | Shoulder seasons: mixed conditions |
|---|---|---|---|
| Typical extraction well | Cold well (spend cold) | Warm well (spend heat) | Depends on strategy; frequent switching is risky |
| Typical reinjection well | Warm well (bank summer heat) | Cold well (rebuild cold) | Must be managed to avoid “smearing” both zones |
| Primary building-side outcome | Direct cooling via HX where possible; chillers/HPs supplement | Direct low-temp heating + heat pump topping when needed | Comfort requires nuance; storage quality requires discipline |
| Main performance benefit | Lower peak electricity demand; reduced compressor work | Better heat pump efficiency (lower lift) than air-source in winter | Opportunity to “fine-tune” balance without major loads |
| Main operational risk | Overspending cold early; chaotic switching that blends storage | Under-rebuilding cold if relying on other heat sources | Thermal mixing and drift from frequent reversals |
What “balance” really means—and why drift is a slow failure mode
Annual balance is the idea that over a year, you roughly “pay back” what you take from each side of storage. If you reject far more heat in summer than you use in winter, the warm side can creep hotter and the cold side can weaken. If the building is heating-dominant, you may drain warm storage without adequately recharging it, and winter supply temperatures slip over time. This is thermal drift: nothing fails catastrophically, but temperatures trend in the wrong direction and efficiency erodes.
Drift is easy to miss because the system still runs—often with heat pumps and chillers quietly compensating. That’s why the previous lesson emphasized monitoring: well temperatures, flow rates, pressures, and HX performance help you distinguish “normal seasonal change” from “long-term loss of usable temperature difference.” When ATES is treated as set-and-forget, operators tend to discover drift indirectly through rising compressor hours, larger peak bills, or complaints during extremes—after the underground storage has already degraded.
Balance is not always “perfectly equal heating and cooling.” Many sites can’t achieve that naturally. But good operation acknowledges the imbalance and manages it deliberately: stable seasonal operation, avoiding unnecessary mixing, and using plant controls so the aquifer remains a controlled asset rather than an uncontrolled sink. The key is to keep the warm and cold reservoirs distinct enough that each season starts with a meaningful temperature advantage.
Common misconceptions to clear up early
-
“The aquifer will self-correct.” Aquifers move heat slowly and predictably, which is exactly why ATES works—but it also means poor cycling can persist and accumulate rather than disappear.
-
“Heat pumps can fix any temperature.” Bigger heat pumps can mask storage problems, but they increase electricity use and hide drift until performance becomes expensive.
-
“Reinjection just returns water.” Reinjection returns state (temperature), not just volume; wrong-temperature reinjection is lost storage value.
Two real operating stories, step by step
Example 1: Mixed-use block chasing lower summer peaks and better winter COP
A mixed-use block has office cooling loads in summer and apartment heating in winter—the classic profile where ATES can thrive if the seasonal cycle is kept clean. In early summer, operators extract from the cold well, use the HX to provide direct cooling to the building loop, and reinject warmed groundwater into the warm well. The immediate impact is twofold: chillers run less during peak afternoons, and the system “banks” heat that would otherwise be rejected to ambient.
As autumn arrives, the building enters mixed-mode. A disciplined operator avoids flipping wells every few hours. Instead, they run longer blocks of operation, choosing a dominant mode based on weather and load forecasts, while tracking cold-well temperature to preserve late-summer capacity. This prevents the warm and cold plumes from blurring and reduces the risk of thermal breakthrough that would show up later as rising supply temperatures.
In winter, extraction switches to the warm well. Low-temperature heating loads are met directly through the HX when possible, and a heat pump stages only to lift temperature for higher-demand periods. The cooled groundwater returns to the cold well, rebuilding cold storage. Benefits show up as better heat pump efficiency (starting from a warmer source than outdoor air) and a strong return of cold storage for next summer. The limitation is operational: if the building’s tenants change schedules or internal gains shift, seasonal balance can drift—so the team treats well temperatures and annual energy balance as KPIs, not afterthoughts.
Example 2: Hospital campus optimizing reliability and keeping cold in reserve
A hospital campus values resilience and faces steep demand charges during heat events. In summer, the operating priority is not “maximum free cooling every day,” but cold preservation for the hottest hours. The campus extracts from the cold well to cool critical loops through the HX and reinjects the warmed water into the warm side. Chillers are still present, but they are staged strategically so the cold well isn’t exhausted early—this is a deliberate “save the battery for peak” philosophy.
During shoulder-season weeks, the hospital often has simultaneous heating and cooling across wings. The risky move is frequent mode switching that smears warm and cold zones underground. Instead, the operating plan sets minimum run times and limits reversals, using the BMS to coordinate valves and pumping so storage remains distinct. Monitoring focuses on well temperatures and HX approach temperature; a rising approach can signal fouling and reduced transfer, which forces higher flows and can unintentionally accelerate mixing and drift.
In winter, the campus extracts from the warm well to support low-temperature heating where possible, and uses heat pumps where lift is required. The cooled water goes back to the cold well, rebuilding capacity for summer reliability. The benefits are reduced peak electrical stress and a more stable cooling strategy during extreme events. The limitation is procedural: hospitals can’t tolerate “set-and-forget,” so maintenance access, redundancy planning, and disciplined monitoring become part of the operating principle—not optional extras.
The seasonal-cycle mindset to carry forward
-
ATES succeeds when it runs like a deliberate seasonal battery: extract from one side, reinject to the other, and protect the temperature difference.
-
Shoulder seasons are the danger zone: frequent switching and mixed-mode operation can accelerate mixing and cause thermal breakthrough.
-
Annual balance protects future performance: unmanaged imbalance leads to thermal drift, where efficiency erodes quietly and mechanical plant work creeps back in.
This sets you up perfectly for Storage Context, Terms & Risks [20 minutes].