US Liquid Cooling editorial · Reviewed · 4 min read
Heat reuse can turn an unwanted output into a useful input, but a nearby building is not enough to establish a viable project. The source and the customer must match in temperature, timing, quantity, location, and reliability expectations. A feasibility discussion should expose those dependencies before a project uses heat reuse as a headline benefit.
Alfa Laval’s heat-recovery guidance notes the challenge of matching data-center cooling temperatures with heating needs. DOE design guidance includes heat recovery within the broader design picture. The following questions are an editorial planning framework, not a substitute for a thermal or commercial feasibility study.
Identify a real heat customer
Describe the proposed use and who controls it. Space heating, process heating, and other applications can have different demand patterns. Obtain a realistic view of when heat is needed, what temperature is required, and how interruptions are handled.
Avoid assuming that all nearby demand is available to the project. The customer may already have contractual commitments, seasonal limits, equipment constraints, or redevelopment plans. A credible study needs direct engagement with the prospective recipient, not only a map showing short distance.
Characterize the available heat
Ask the engineering team to describe the recoverable heat at the relevant interface and operating conditions. Distinguish total IT power from heat available at a useful temperature after system losses and other requirements. Record what changes at low load and during maintenance.
A temperature quoted at one component may not be the temperature delivered to the customer. Include the intervening heat exchangers, piping, and any equipment needed to raise the temperature. The receiver’s requirements and the data center’s cooling needs must both be satisfied.
Compare timing across the year
Place the expected heat supply and customer demand on the same calendar. Examine daily variation, seasonal variation, planned outages, and the possibility that either party changes its operation. A project that works during a cold month may have a very different annual utilization pattern.
Ask where heat goes when the customer cannot take it. The data center still needs a reliable cooling path. Heat reuse should be integrated with the site’s operating strategy rather than treated as a customer whose availability is assumed to be constant.
Define the commercial boundary
List the infrastructure required to connect the parties and assign ownership. Clarify who funds, operates, maintains, and eventually replaces each component. Include metering, access rights, responsibility for interruptions, and the process for resolving quality or delivery disputes.
The business case should distinguish avoided cost from revenue, and forecasts from committed arrangements. Do not count the same benefit twice across the data center and the heat recipient. Ask qualified advisors to review contracts and applicable local requirements before commitments are made.
Test sensitivity to change
Explore what happens if the IT load grows more slowly, the customer reduces demand, energy prices change, or additional equipment is needed. These scenarios do not need to predict the future precisely; they should reveal which assumptions dominate the decision.
Include a case where the planned reuse connection is unavailable for an extended period. The team needs to understand the operating and financial consequences without relying on a best-case relationship between two independent organizations.
Make the result auditable
A useful feasibility summary states the heat source, recipient, required interfaces, annual assumptions, fallback cooling arrangement, and remaining decisions. Keep supporting calculations and the parties’ confirmations with the summary.
If the result is not attractive today, preserve the information that could make it viable later. A future customer, a different temperature requirement, or a planned building upgrade may change the case. The objective is a well-supported site decision, not a universal promise that every liquid-cooled facility can profitably reuse its heat.
Sources & further reading
- Alfa Laval heat recovery discussion ↗
- Alfa Laval data center cooling and heat reuse ↗
- DOE data center design guide ↗
Explore the company directory → · All liquid-cooling guides →