> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/evaluation-and-reporting/golden-reports/headline-figures.md).

# Headline figures

This page explains the headline figures at the top of the Golden Report.

Use it to understand report coverage, active AI control, and what the summary numbers do and do not include.

For shared report concepts like uptime, baseline, efficiency, and savings, see [Golden reports](/evaluation-and-reporting/golden-reports.md).

## Portfolio coverage

**Total building area.** The combined floor area of every building included in this report. This is the denominator behind any per-m² figure you see later on.

**Complete energy data per energy type.** The share of total building area for which we have usable energy data, broken down by energy source (district heating, district cooling, electricity). A building only counts toward this figure if its data for that source is complete enough to feed the report's calculations.

If complete coverage for a given energy source is low, the consumption and savings figures in that section of the report are based on a smaller subset of buildings than the headline total area suggests. Read those numbers with that caveat in mind.

## AI coverage

**Active systems.** The number of building systems — typically air handling units, but also other controllable subsystems — that myCoreAI is actively writing setpoints to, compared to the total number of systems integrated with Myrspoven. The integrated total is the upper bound: it covers everything we can see, including systems that are connected for monitoring only.

A gap between "active" and "integrated" usually points to systems that are connected for monitoring but have not yet been handed over for control. It's a useful starting point for a conversation with your Myrspoven representative if you'd like to expand myCoreAI's footprint.

## Per-energy-source figures

Headline figures that are specific to a single energy source — consumption, the myCoreAI-controlled share, savings at uptime, and potential savings — are explained on the energy-source pages, because the methodology differs slightly between them:

* [Heating](/evaluation-and-reporting/golden-reports/heating.md)
* [Cooling](/evaluation-and-reporting/golden-reports/cooling.md)
* [Electricity](/evaluation-and-reporting/golden-reports/electricity.md)

## A note on assumptions

Several headline and per-source figures rely on default assumptions — the share of electricity that powers ventilation, the split of district heating between heating circuits and AHUs, the tap-water estimate, and so on. The energy-source pages list the defaults they use. If you have building-specific figures for any of these, share them with your Myrspoven representative and we'll use yours instead of the defaults.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.myrspoven.com/evaluation-and-reporting/golden-reports/headline-figures.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.