**NOTE:** This document is not yet complete.

## 1 Heat demand model

### 1.1 Annual demand model

Annual demand is predicted using a combination of several models:

- A support vector machine (SVM) trained on predictors that use the three-dimensional shape of a building
- A linear model (LM) trained on predictors that use the three-dimensional shape of a building
- A SVM trained on two-dimensional predictors only
- A LM trained on two-dimensional predictors only
- A separate hot water demand model

#### 1.1.1 Algorithm

If there is three-dimensional data available, then the 3D predictors are calculated and the 3D models are used, otherwise the 2D versions are used. The predictors are given later; following this the process is

- Estimate space heat demand
- Estimate normalized space heat demand with SVM; for most buildings this will produce a good result, but for buildings which are extreme cases with regard to one of the predictors the SVM kernel's smoothing behaviour will prevent extrapolation.
- If the predictors are out of range for the SVM, use the LM instead
If the LM produces a bad result (

*because*it extrapolates), go back to the SVM.A bad result is one where the space demand figure is clearly too low

De-normalize the demand; the SVM and LM both predict space heat demand

*per square root heating degree day*, so we multiply the space heat demand result by the square root of the number of heating degree days in the location.This is following the methodology in Ecoheatcool's work package 1

^{1}.

- Estimate hot water demand
- For this we use the methodology from SAP 2012
^{2}, equations (42)-(45). This method is essentially a nonlinear benchmark, as the demand is derived from the building's assumed floor area.

#### 1.1.2 Model creation

**NOTE:** This is incomplete.

The model is based on measured heat demand data from buildings in Copenhagen; for these buildings we computed both the 3D and 2D predictors described below, and used an R machine learning toolkit to train and cross-validate SVM and LMs to predict space heat demand per square root degree-day using each set of predictors.

To separate space heat demand from hot water demand in the training data, we applied a simple assumption that a constant proportion related space heat to hot water demand. It would perhaps have been more consistent to estimate hot water demand using the SAP equations, and subtract that value.

#### 1.1.4 Predictors

- Three-dimensional predictors
*External*wall area, computed by taking the length of all walls not shared with adjacent buildings and multiplying it by the building height- Height, computed by sampling LIDAR points within the building's footprint polygon
- Perimeter, which is just the perimeter of the footprint polygon
- Surface per volume, which is the ratio of the building's overall surface area (including party area) to its volume
- Volume, which is the footprint area multiplied by height

- Two-dimensional predictors
- Footprint area
- Perimeter
- Perimeter divided by footprint
- Whether the building is residential or not
- Party perimeter, as a proportion
- Party perimeter, as an absolute value in metres

- SAP predictors
- Floor area, estimated using building height and an assumed storey height to get a number of floors, or assuming a single floor if no height is known. This has some room for improvement; for example predicting floor area from the two dimensional predictors and other building attributes might be worthwhile.

Other geometric predictors which might be worth considering would include functions of building orientation (e.g. south-facing area), and the number of corners or edges on the building, but we have not assessed these. We have also not explored any further categorical information about buildings, or information about their occupancy. Whilst these features might improve the predictive power, they are harder to come by and so reduce the number of places the model can be applied.

### 1.2 Peak demand model

The peak demand in kW \(p\) is derived as a function of the annual demand in kWh \(a\), using the rule:

\[ p = 21.84 + 0.0004963 \times a \]

This rule is derived from analysis of smart meter data in the UK, relating peak to annual gas usage, with some assumed efficiencies and weather correction.

## 2 Cooling demand model

### 2.1 Annual demand model

Cooling demand is estimated using the method given by Sven Werner in *European space cooling demands*, published in Elsevier's *Energy* 110 (2016) pp148 – 156^{3}.

The model uses an empirically determined *cooling index* \(E\), which is used to produce a benchmark value of \(1.22 \times E - 43.5\) kWh/m^{2}.

The cooling index varies by region, and so incorporates some evidence about the cooling degree days that are needed.

### 2.2 Peak demand model

At the moment the cooling peak model is very basic.
The BSRIA *Rules of thumb* (5^{th} edition)^{4} gives the following indicative values for cooling capacity *in the UK* by building use:

Use | W/m^{2} |
---|---|

Residential | 70 |

Offices | 87 |

Hotels and shops | 150 |

Restaurants | 200 |

Datacenters | 1500 |

Since THERMOS doesn't usually know more than whether a building is residential or not, we have taken as representative two values: 70 W/m^{2} for residential, and 150 W/m^{2} for non-residential buildings.

To translate these values to regions other than the UK, we have related them to Werner's annual demand model to produce ratios between annual demand and peak demand for residential and non-residential buildings.

The peak demand is then calculated by applying this ratio to the annual demand estimate from Werner's method. The assumption here is that the peak-to-base ratio is the same in different regions.

We would be very interested to hear from anyone with a better idea or more evidence about this part.

## Footnotes:

^{1}

ECOHEATCOOL, Work Package 1; the European Heat Market (Final Report), by Euroheat & Power, 2005-2006.

^{2}

SAP 2012, the Government's Standard Assessment Procedure for Energy Rating of Dwellings

^{3}

^{4}

ISBN 978 0 86022 692 5