A Megawatt of Data-Center Heat Is Not Yet a Megawatt of Useful Heating

Heat quantity and temperature answer different questions

A thermal power figure tells you how quickly heat crosses a defined boundary. Temperature describes the thermal condition at that boundary. Two streams can carry the same thermal power while being useful to different heating applications. A large quantity of heat at a temperature below the recipient's requirement does not satisfy that requirement merely because the MW total is large.

This is the distinction behind low-grade waste heat. Oak Ridge National Laboratory's July 2024 publication abstract describes thermodynamic models of high-temperature heat pumps that upgrade data-center waste heat for district heating. The mechanism matters here: recovering heat and making it available at a higher temperature are separate tasks. The abstract supplies a modeled research context, rather than evidence that a particular recipient is being served.

Consider a fictional recipient whose required heating temperature exceeds the temperature available at a proposed recovery interface. Stipulate that the offered heat quantity is sufficient. The temperature mismatch still remains; increasing the stated quantity alone does not resolve it. No temperatures or actual equipment are selected in this example. The buyer needs to understand the proposed temperature upgrade, if any, before treating the recovery figure as useful heating.

References: [O1]

A heat pump adds an energy input

A heat pump takes in heat from a source and transfers heat to a receiving system, using external energy to make the transfer possible. In the electrically driven arrangement considered here, electricity is a separate input. The IEA's 2022 explanation describes source and receiving heat exchangers and a compressor-driven cycle; it also identifies data-center waste heat as a possible source for large-scale applications.

For the buyer, this creates three distinct quantities: recovered thermal input, electrical input and thermal output. Calling the output recovered data-center heat without separating the electrical contribution changes what the number means. Likewise, an output at the heat pump is still upstream of any downstream distribution and recipient boundary.

The source temperature and required output temperature belong with the proposed performance information. A general explanation of heat pumps does not establish the electrical input or achievable output for an actual temperature lift. Those values need the selected equipment and its applicable conditions. No heat-pump type, refrigerant, operating temperature or plant arrangement is selected here.

References: [H1]

Follow four thermal megawatts through a fictional example

Fictional example EX-HEAT-01 is an idealized energy balance around a hypothetical heat pump. Stipulate steady operation with 4 MW of recovered thermal input and 1 MW of electrical input. Stipulate no other energy inputs or outputs, no losses across this boundary and no change in stored energy. Under those assumptions, thermal output at the heat-pump outlet is 5 MW: 4 MW plus 1 MW.

For a stipulated one-hour interval at those constant rates, the corresponding quantities are 4 MWh of recovered thermal energy, 1 MWh of electrical energy and 5 MWh of thermal output. MW describes the rate; MWh describes the energy over the stated interval. The one-hour result cannot be extended into a yearly supply forecast without additional operating assumptions.

The 5 MW output contains the 4 MW recovered contribution plus the electrical contribution. It is therefore not 5 MW recovered from IT. Nor are the 4 MW input and 5 MW output two separate heat supplies totaling 9 MW: the recovered contribution appears inside the output.

All values are invented for accounting only. Their relationship supplies no product COP claim, achievable operating point, equipment rating, design or measurement. Downstream distribution and its energy requirements are outside this example. Most importantly, nothing in the arithmetic establishes that a recipient can accept 5 MW at its required temperature or during that hour.

Annual totals can hide a timing mismatch

Heating demand follows the recipient's use. Space heating can fall in warmer weather even while an IT workload continues producing heat. A year-round process recipient would have a different demand profile. Neither profile can be assumed from the size of the data center.

An annual source total and an equal annual heating-demand total can conceal different schedules. Consider a second, entirely fictional comparison: one recipient needs most of its heat in winter, while a proposed source's available recovery is concentrated in summer. Stipulate no storage or other arrangement that moves heat between those periods. Matching annual MWh totals leaves that timing mismatch unresolved.

Even when heat production is ongoing, a recipient may not require its full rate at the same time. Conversely, a recipient's highest heating demand need not coincide with the source's highest recoverable output. Compare the relevant periods and source availability with the recipient's demand; an annual sum has discarded that information.

Thermal storage can change timing, as the IEA discusses in its district-energy executive summary. Its presence, usable scope and supporting infrastructure would be additional project facts. The existence of storage technology does not allow a comparison to assume that a seasonal mismatch has already been solved.

References: [D1]

The recipient boundary determines delivered heat

The 2026 IEA district-energy executive summary identifies proximity to demand and temperature compatibility among the local conditions affecting waste-heat deployment. A nearby building is a possible recipient to investigate; its location alone establishes neither a usable connection nor an agreed heat supply.

Compare where an offer stops. One might describe heat available at a data-center recovery interface. Another might describe heat-pump outlet capability. A third might describe heat supplied at a named recipient interface under defined conditions. Those descriptions can concern different parts of the same energy path. Their thermal power figures are not automatically interchangeable.

In EX-HEAT-01, the stipulated 5 MW stops at the heat-pump outlet. A recipient-side figure would need its own basis, including the intervening distribution and the recipient's acceptance conditions. No downstream loss value is supplied, so the example cannot assign a delivered figure. It also says nothing about who owns the connection or whether the recipient has agreed to take heat.

A public study can explain potential without establishing an operating network or a buyer for the output. Keep the physical question—can the heat reach this use under the required conditions—alongside the commercial question of whether this recipient will take it. Neither a research result nor an annual energy match answers both.

References: [D1]

Buy the thermal result you actually need

Component cooling removes heat from the equipment. Heat recovery makes a defined heat stream available for reuse. Temperature upgrade addresses a mismatch between source and use. Useful delivery reaches the recipient under its required conditions and schedule. A proposal may cover one or several of these results; the word cooling does not establish the whole chain.

If the objective is useful heating, compare offers at the recipient boundary. An offer limited to component cooling may be complete for its stated purpose while leaving recovery, temperature upgrade and distribution to other parties. An offer including a heat pump answers an additional question, but still needs the intended recipient and delivery scope. This distinction determines what remains to be bought.

Cooling, heat-recovery and heat-network design, equipment selection, implementation and acceptance belong with the customer's appointed qualified specialists. Leviathan's separate physical IT scope does not include liquid-side work, its coordination or subcontracting, or thermal approval. The linked cooling responsibility guide explains that boundary.

For surrounding equipment mounting, IT cabling, labels and physical handoff records, use Leviathan's existing rack-and-stack service and its project inquiry. Share a nonconfidential outline of the equipment, released rack and cable package, requested physical tasks and customer-defined facility prerequisites. Identify the appointed cooling and facility contacts so the physical IT discussion refers to the right dependencies. Our team can discuss that scope, requirements and availability.

References: [L1][L2]