> 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/report-metrics.md).

# Report metrics

This page explains the main metrics used in the Golden Report and in myPortal.

Use it to understand what each reported metric measures and how to read it.

## Reported metrics

Customer-facing metrics fall into three groups: energy used and saved, control reliability, and indoor climate.

### Energy and savings

* **Total consumption** — energy used during the reporting period, broken down per source (district heating, district cooling, electricity).
* **myCoreAI-controlled share** — portion of consumption falling within hours myCoreAI was actively running, weighted by uptime.
* **Savings at uptime** — measured savings against a baseline of how the building would otherwise have been operated, over the hours myCoreAI was in control.
* **Potential savings** — the same figure scaled to 100% uptime. Shows the gap between realized savings and what is available.
* **Energy efficiency** — normalized efficiency per energy source. Enables comparison of a building against itself over time and against reference data.
* **Auxiliary consumption** — energy use that is not heating or cooling, reported separately so it does not mix into the source breakdown.

### Control reliability

* **Uptime** — share of the reporting period during which myCoreAI was actively controlling the building. Savings only describe the hours covered by uptime.

### Indoor climate

* **Temperature compliance** — share of time indoor temperatures stayed inside the building's configured comfort bounds.
* **CO₂ compliance** — same, for CO₂ where measured.

Comfort bounds are configured per building. Compliance figures are reported alongside savings: savings at the cost of comfort are not savings.

## Calculation

Methodology differs per energy source. District heating, district cooling, and electricity each carry their own assumptions, default splits, and fallback constants. The per-source pages under the Golden Report document each calculation.

* **Baseline** — myCoreAI measures savings against a model of how the building would otherwise have been operated, not against the prior year's meter reading. The baseline accounts for weather and occupancy where data allows.
* **Uptime weighting** — "myCoreAI-controlled share" and "savings at uptime" are weighted by the hours myCoreAI was in control. The "potential" variant strips that weighting.
* **Defaults vs. building data** — without a building-specific figure for inputs like the heating-circuit / air handling unit (AHU) electricity split or tap-water consumption, myCoreAI uses a default. Supplying the real figure replaces the default and tightens the report. Confirm with Myrspoven.


---

# 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/report-metrics.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.
