Strategy · published

A repeatable evidence workflow from the student projects — which metrics to calculate, with which tool or method, and the decision it led to.

SummaryA heat balance compares the waste heat of a data centre with the heat demand of possible neighbours, to choose programmes and plan heat export.
Tool or methodmanual / formula (heat output per server or rack against per-programme heat demand)
Statuspublished

The question it answers

How much heat does the data centre release, and which programmes and neighbours can use it?

How it works

  1. Estimate the heat output from the number of servers or racks and their power.
  2. Turn it into annual recoverable heat with an assumed recovery efficiency.
  3. Add up the heat demand of candidate programmes such as a sauna, greenhouse, café or food production.
  4. Choose heat-hungry programmes and plan where the surplus heat goes, for example within a radius on the city map.

In the student projects

  • Julia Godard Lombard — manual / formula. Waste heat recovery: P1 4,500 kW (300 servers), P2 17,250 kW; Heat recovery radius: P1 225 m, P2 430 m, P3 500 m. Decision: “The heat balance showed that even the small P1 data centre produces far more recoverable heat than the café, sauna and dry-food programmes need, which supported choosing heat-hungry programmes and planning to export surplus heat to neighbours and the district in later phases.”
  • Katrin Rybinskiy — not stated. Waste heat recovery: 225 GWh/year from data centres A, B and C; 11,500 MWh/year (about 5%) used for the greenhouse. Decision: “The energy and heat figures were used to justify adding a fully PV-covered data centre C and a heat-fed greenhouse, and to route remaining heat to housing through the existing power plant.”

Values and decisions as reported by the student; see each case study for the page in the portfolio.

Where it falls short

  • In Katrin Rybinskiy’s project the method behind the 225 GWh/year is not explained.
  • In Julia Godard Lombard’s project the P3 table shows a placeholder value that does not match the chart.

Where are the ambitions, metrics and tools?

They appear automatically below under Connections, and in Obsidian under the auto_ properties.

Connections


Something wrong or missing? Suggest a correction