Free guide: The IHP model explained for district heating operators
- May 14
- 3 min read
Updated: 1 day ago
The Independent Heat Producer model (IHP) lets you add a reliable, low-carbon heat source to your network – without deploying capital, building heat-pump expertise in-house, or managing a relationship with a data centre operator. This guide explains in short how data centres waste heat can be used for district heating operators.
Fill out the form to get the guide in your inbox.

What's inside "IHP model for district heating operators"
Delivery temperatures, heat volumes, and seasonal stability
The COP and what it means for the price we can offer you
Heat Purchase Agreement structure, term, and indexation
Data centre waste heat for district heating operators
Site viability criteria and the most common reasons projects don't proceed

Written by Ulrika Jardfelt – former CEO of Svensk Fjärrvärme, policy voice in the Swedish Energikommissionen, and now at Calentix Energy. Few people combine her depth on the utility side with a practical understanding of what makes an IHP arrangement actually work.
FAQ : Common questions about data centre waste heat for district heating operators and the IHP model
Common questions about the IHP model for district heating
Q1 – What is the IHP model from a district heating operator's perspective?
The Independent Heat Producer model is a commercial framework where Calentix – a specialised third party – finances, builds, owns, and operates a heat pump installation that recovers waste heat from a data centre. From the district heating operator's perspective, Calentix is simply a contracted heat supplier, equivalent in commercial terms to a biomass plant or large industrial heat recovery installation. You receive heat at your network connection point under a long-term Heat Purchase Agreement.
Q2 – What delivery temperatures can a district heating network expect from data centre waste heat?
Modern industrial heat pumps in data centre applications reliably deliver supply temperatures of 70–90 °C, and up to 95 °C in some configurations. Lower-temperature Fourth Generation District Heating networks (55–70 °C) are particularly well suited, because reduced temperature lift improves heat pump COP – and therefore the heat price.
Q3 – What heat volumes are realistic, and how stable is the supply?
A 10 MW data centre with full liquid cooling can typically supply 5–8 MW of recoverable heat to a Calentix installation. Data centre waste heat is near-continuous: 6,000–7,000 hours per year at meaningful output, with predictable seasonal variation and far higher utilisation than solar thermal or sewage heat.
Q4 – What COP is achievable and why does it matter?
A COP (Coefficient of Performance) between 3.5 and 6 is achievable in data centre waste heat recovery, depending on season and network temperature. At a COP of 5, electricity cost per MWh of heat is one-fifth of the electricity price. Compared to a gas boiler, a well-designed heat pump installation uses up to 82% less energy input per MWh of heat delivered.
Q5 – How is the Heat Purchase Agreement structured?
The HPA defines price (often a base rate indexed to electricity prices, sometimes a fixed price per MWh), minimum annual heat volumes, contract term (typically 15–20 years), independent metering at the connection point, monthly delivery reports, and dispatch arrangements where relevant. Force majeure and performance remedy clauses are included on both sides.
Q6 – How long does an IHP project take?
Typically 18–36 months from first conversation to first commercial heat delivery: 2–6 months for feasibility, 6–12 months for design and contracting, and 6–12 months for construction and commissioning.
Q7 – What makes a project viable from a district heating perspective?
The data centre must use liquid cooling, have an IT load above roughly 2–5 MW, and be located within 1–2 km of an existing network connection point. Your network's actual minimum required supply temperature and the return temperature in summer are the two most important variables on the district heating side.
Q8 – What monitoring data does the district heating operator receive?
Continuous access to a real-time dashboard showing heat pump output, supply and return temperatures, electricity consumption, instantaneous COP, and cumulative heat delivery by hour, day, month, and year. Data can be exported in standard formats for billing and regulatory reporting, and we can integrate with broader fleet dispatch arrangements.
Q9 – What are the most common reasons projects don't proceed?
Three failure modes recur: network conditions that don't match (very high mandatory supply temperatures, or summer return above 55 °C); inaccurate data centre temperature data discovered late in feasibility; and contractual misalignment between the three parties (Calentix, the data centre, and the district heating operator). Early engagement of the right decision-makers is the single most effective preventive measure.

