Chapter 5.9
Heat Reuse & Waste-Heat Recovery (Engineering)
Whether your waste heat sells as a district-heating commodity or gets dumped depends on its temperature grade, which the facility-water setpoint fixes upstream before construction.
What you'll decide here
- Whether to capture heat at all — and if so, at which grade: the air-side ~30–40 °C low-grade stream, the DLC return at ~45–55 °C, or a heat-pump-lifted ~70–90 °C district-heating supply.
- Where the heat-reuse heat exchanger sits in the loop — pre-CDU on the warmest technology-cooling water, or post-rejection on the facility return — because that placement caps the grade you can ever sell.
- Who owns the heat pump and who owns the pipe: the operator-buys-pump / utility-buys-connection split (the Stockholm Open District Heating model) versus a vertically integrated capture-and-sell stack.
- How to engineer around the offtake chicken-and-egg: the heat sink (district network, greenhouse, industrial process) and the data center rarely arrive on the same schedule, and the loop must be designed to run profitably with zero offtake on day one.
- Whether a 2026 EU/national mandate (EED Article 26, Germany's EnEfG ERF floor, France's valorization law) has already converted heat reuse from an optional sustainability play into a permit condition you must engineer to.
A 100 MW IT load rejects very close to 100 MW of heat — essentially all the electrical energy that enters the building leaves it as low-grade warmth. That continuous, year-round source sits next to cities that burn gas to stay warm, so the pull to sell it is obvious, and in 2026 it is increasingly a legal obligation rather than an option. The binding constraint is grade, not quantity: heat at 30 °C is worth almost nothing, while the same joules delivered at 80 °C are a tradable commodity. And the grade you can deliver was largely decided one chapter upstream, when you set the facility-water supply temperature in Chapter 5.7.
The engineering falls into four questions: how the grades are defined and what each is good for; how a heat pump upgrades a sub-usable return temperature to a district-heating supply, and what that lift costs in COP and electricity; where the reuse heat exchanger ties into the loop, and why warm-water DLC is what makes the exercise viable at all; and the offtake chicken-and-egg, the scheduling and counterparty problem that kills more heat-reuse projects than any thermodynamic limit. Economics, contract structures, carbon-accounting, and regulatory treatment are deferred to Chapter 15.5; here we engineer the heat.
Grades of waste heat: what each is good for
Waste heat is graded by temperature because temperature, not energy content, is what an offtaker's distribution network and emitters require. A district-heating network has a supply-temperature spec set by its generation: legacy 2nd/3rd-generation networks run 70–90 °C (and some older systems higher), modern 4th-generation networks run 30–70 °C, and emerging 5th-generation (ambient-loop) networks run 10–30 °C and put a heat pump at every building. Your captured stream is only useful if it can meet the network it is feeding, directly or after a lift. Everything below follows from that one matching condition.
The grade you can capture is dictated by the cooling modality, which is why the cooling-architecture chapters are upstream of this one. Air cooling and rear-door heat exchangers (Chapter 5.2, Chapter 5.3) hand you a diffuse, low-grade stream — return air or RDHx water around 30–40 °C — spread over large flow rates and large surface areas, which is expensive to concentrate. Direct-to-chip liquid (Chapter 5.4) concentrates almost all the heat into a single small-flow, high-temperature stream: a warm-water loop returns coolant at roughly 45–55 °C off the cold plates, single-phase D2C systems commonly returning in the 35–50 °C band depending on inlet and delta-T. That concentration, not any extra heat, is what makes DLC the enabler of credible reuse — it delivers usable grade in a form a heat exchanger can grab cheaply.
| Grade | Source modality | Capture temp | Direct offtake (no lift) | Heat-pump lift to DH supply |
|---|---|---|---|---|
| Low-grade | Air return / CRAH coil / rear-door HX | ~25–40 °C | 5th-gen ambient loop; greenhouse soil; pool warming | Large lift (to 70–90 °C); COP ~2.5–3.5 — the economics are marginal |
| Mid-grade | Warm-water DLC return (W40/W45 loop) | ~45–55 °C | 4th-gen low-temp network directly or near-directly | Small lift to legacy DH; COP ~4–6 — the viable band |
| High-grade | DLC return after heat-pump upgrade | ~70–90 °C | Legacy 2nd/3rd-gen network supply directly | Already lifted; electricity cost is in the COP you paid to get here |
| Process-grade | Hot-water buffer + cascaded HP / two-phase | >90 °C (rare for AI) | Industrial process heat, absorption chilling | Requires high-temperature HP cascade; specialist, project-specific |
The table sorts halls by cooling modality. If your hall is air-cooled, you are in the top row — a large heat pump, a marginal COP, and an offtaker who must be either very close or very forgiving. If your hall runs warm-water DLC, you are in the second row — the only row where the numbers reliably work, because a modest lift from ~50 °C to a 4th-generation network's 60–70 °C supply runs at a COP of 4–6 and the captured heat is worth selling. This is the quiet reason that the cooling decision in Chapter 5.4 and the loop-temperature decision in Chapter 5.7 are the real heat-reuse decisions. By the time you reach this chapter, the grade is mostly already set.
The heat-pump upgrade: lift, COP, and the electricity penalty
A heat pump moves heat from a cooler source to a warmer sink and consumes electricity to do it. For waste-heat upgrade, the source is your DLC or RDHx return and the sink is the district-heating supply. The governing number is the coefficient of performance (COP): useful heat delivered per unit of electrical work. COP falls as the temperature lift (sink temperature minus source temperature) rises — this is Carnot's tax, and it is unavoidable. A heat pump lifting a 50 °C source to a 65 °C sink (a 15 °C lift) might run at a COP of 5–6; the same pump lifting a 30 °C air-side source to an 80 °C legacy network (a 50 °C lift) drops toward a COP of 2.5–3.5. Industrial high-temperature heat pumps for district heating typically span a COP of roughly 2.5–6 across this range.
The COP sets both the electricity you burn and the carbon you account for, which is why it dominates the economics. At a COP of 5, you deliver 5 MW of heat for 1 MW of electricity; the captured 4 MW of waste heat plus 1 MW of pump work leave as sellable heat. At a COP of 3, you deliver 3 MW of heat for 1 MW of electricity — the same offtake now costs you 67% more parasitic load, and on a power-bound site that 1 MW is megawatts you could have spent on accelerators. A low-COP heat-reuse scheme is a tax on the IT capacity of the building — the clearest POWER-BOUND consequence in the cooling stack — and the warmer the source water, the smaller that tax. Designing the DLC loop warm (Chapter 5.7) is therefore the biggest lever on heat-reuse economics, because it shrinks the lift before the pump ever runs.
Deep dive: why the heat exchanger placement caps your grade forever
The reuse tie-in is a heat exchanger, and where you put it in the loop is an irreversible grade decision — you cannot capture heat warmer than the warmest water you tap. There are three candidate tie-in points, each capping the grade differently.
Pre-CDU, on the technology-cooling loop: tapping the warmest water in the building, straight off the cold-plate return at ~50–55 °C, before the CDU's plate-and-frame exchanger hands it to facility water. This is the highest grade you can reach without a pump, but it intrudes into the warranty-sensitive primary loop and complicates the CDU's job of holding a tight inlet to the GPUs. On the facility-water return, post-CDU: the pragmatic default — the reuse HX sits on the warm facility return before it reaches the dry coolers or tower, capturing ~45–50 °C without touching the technology loop. You lose a few degrees of grade to the CDU approach but keep the reuse circuit cleanly isolated from the IT. Post-rejection, on a dedicated heat-recovery loop: the lowest grade and worst idea — you are scavenging heat the plant has already started throwing away.
So the grade you can ever sell is set the day you fix the tie-in point: every component between the chip and the HX subtracts degrees no pump can hand back for free. Place the reuse HX as far upstream (warm) as the warranty and control envelope allow, and plumb a future tie-in stub even before an offtaker exists — retrofitting a tap into a live primary loop is a one-way door, irreversible once the loop is charged and running. Loop topology and the CDU isolation it interacts with are engineered in Chapter 5.6 and Chapter 5.7.
Loop integration and the on-site / district interface
Heat reuse adds a third thermal domain to the building. The technology-cooling loop (chip to CDU) and the facility-water loop (CDU to heat rejection) already exist from Chapter 5.6 and Chapter 5.7. Heat reuse interposes a third loop — the heat-recovery loop — that runs from the reuse HX, optionally through a heat pump, into a hot-water buffer, and across an isolation heat exchanger to the offtaker's network. The interface point — the boundary where your water meets the district utility's water — is a hydraulically and contractually critical plane, and it is almost always a plate heat exchanger that keeps the two networks chemically and pressure-isolated. Neither side wants the other's water, the other's chemistry, or the other's pressure transients; the HX is the demarcation.
The integration's hardest engineering problem is that the data center's heat output is constant and the city's heat demand is not. An AI hall rejects near-baseload heat 8,760 hours a year; district-heating demand swings seasonally by 5–10x between a January peak and a July trough, and the summer trough can fall below the heat the data center produces. The plant must therefore be designed to reject the heat anyway when there is no buyer — the dry coolers and towers of Chapter 5.8 never leave the building, because heat reuse is an opportunistic heat sink layered on top of a mandatory one, never a replacement for it. A common mistake is to size the rejection plant assuming the offtaker absorbs the load; the offtaker disappears every summer and on every demand dip, and the GPUs do not stop. Warm-water DLC is the enabler not only because it produces usable grade, but because it lets the same dry cooler that rejects heat in summer also pre-warm the reuse loop in winter — the warmer the loop, the more both jobs are done by simple, compressor-free equipment.
The offtake chicken-and-egg as an engineering constraint
Most data-center waste heat is still dumped for want of coordination, not for want of thermodynamics. Heat reuse requires two parties with very different planning horizons to arrive at the same place at the same time. The data center is built in 18–36 months against an interconnection slot and a depreciation clock. A district-heating network expansion, a new greenhouse, or an industrial-process tie-in is a multi-year municipal or industrial capital project with its own permitting, its own financing, and its own committee. Each side is reluctant to commit capital before the other has: the utility will not lay pipe to a heat source that may never deliver; the operator will not buy heat pumps and reuse HXs for an offtaker that may never connect. That is the offtake chicken-and-egg, and it is an engineering constraint, not just a commercial one, because the loop you build must survive the period when one side exists and the other does not.
The engineering responses are concrete. Plumb for reuse without committing to it: install the tie-in stubs, reserve the plant-room footprint and electrical headroom for a future heat pump, and route the pipe-rack so a reuse HX can drop in — because the irreversible substrate (loop taps, space, power) is cheap at construction and expensive to retrofit, exactly the reversible-vs-irreversible discipline from Chapter 1.1. Design the plant to run profitably with zero offtake on day one: the mandatory rejection plant must stand alone, so the reuse loop can sit dormant for a year or three until the offtaker materializes. Decouple the capital split contractually so neither party fronts the other's risk — the model that broke the deadlock at scale is Stockholm Exergi's Open District Heating, where the operator invests in the heat pumps and the utility invests in the network connection, and the heat trades as a standardized, temperature-indexed product. That platform now connects 30-plus data centers across 16 providers, and a single site can earn on the order of SEK 2M per MW per year for the heat it would otherwise have thrown away (Stockholm Exergi / Eurelectric, 2025).
The 2026 regulatory floor: reuse as a permit condition
For much of the industry's history, heat reuse was a discretionary sustainability gesture you did if the economics happened to align. In the EU as of 2026, that framing is obsolete. Under the recast Energy Efficiency Directive (EU) 2023/1791, Article 26, data centers with a total rated energy input above 1 MW must carry out a cost-benefit analysis of waste-heat recovery, and member states have gone further: Germany's Energy Efficiency Act (EnEfG) mandates a minimum energy-reuse factor (ERF) of 10% for new data centers commissioned from July 2026, rising to 15% from July 2027 and 20% from July 2028, and France's Law 2025-391 requires heat valorization for facilities above 1 MW. An EU-level data-center energy-efficiency package was expected in Q2 2026 to build further requirements on the EED's monitoring data.
The engineering consequence is that, for a European greenfield over 1 MW, the heat-reuse tie-in is no longer an optional bonus loop — it is a permit and compliance condition that must be in the design basis from day one, and a hall plumbed for cold air with no reuse provision may simply not be permittable. This is the strongest argument for warm-water DLC and a pre-installed reuse HX: a mandate that requires you to deliver a measurable ERF is far cheaper to meet from a 50 °C concentrated stream than from a 35 °C diffuse one. The detailed regulatory, contractual, and carbon-accounting treatment — including how ERF is measured and how heat sales interact with PUE and emissions claims — is the subject of Chapter 15.5; the point here is that the regulation reaches back into the mechanical design and removes "do nothing" as an option.
Deep dive: the all-air retrofit that cannot meet an ERF mandate
Consider an existing 30 MW air-cooled colocation hall in Germany, facing the EnEfG's 10% ERF floor for the expansion it wants to permit. Its waste heat is a ~35 °C return-air stream spread across the whole white space. To deliver even 3 MW of reuse heat at a usable district-heating grade, it must (a) concentrate the diffuse air-side heat through coil exchangers, losing grade at every step; (b) install a large heat pump to lift ~35 °C to the local network's ~75 °C supply — a 40 °C lift at a COP near 3, meaning roughly 1 MW of parasitic electricity to deliver the 3 MW of heat; and (c) find an offtaker willing to take low-confidence, seasonally interrupted heat. The parasitic load alone strands IT capacity on a power-bound site, and the project may still fail the cost-benefit test the directive requires.
The same mandate against a warm-water DLC hall is a different problem entirely: the ~50 °C concentrated return needs only a ~15–20 °C lift (COP 4–6, ~0.7–1 MW of pump electricity for the same offtake), the reuse HX taps a single small-flow pipe, and the ERF is comfortably exceeded. This is the density-and-cooling cascade from Chapter 5.1 reappearing as a regulatory cost: the cooling modality you chose for the GPUs has already decided whether the heat-reuse mandate is a footnote or a capacity-stranding tax. So for any new European build over 1 MW, plumb warm and concentrate the heat at source, since the alternative is unpermittable or uneconomic — virtue does not enter into it.
Cite this chapter
Fehn, J. (2026). Heat Reuse & Waste-Heat Recovery (Engineering) (Chapter 5.9). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-5-cooling-and-thermal-management/5-9-heat-reuse-and-waste-heat-recovery-engineering (accessed 2026-08-13).
@misc{aidc-5-9,
author = {Fehn, Jacob},
title = {Heat Reuse & Waste-Heat Recovery (Engineering) (Chapter 5.9)},
howpublished = {The Definitive Guide to AI Data Centers},
year = {2026},
url = {https://aidatacenterguide.com/part-5-cooling-and-thermal-management/5-9-heat-reuse-and-waste-heat-recovery-engineering},
note = {Accessed 2026-08-13}
}