> 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 two groups: energy used and saved, and control reliability. Indoor climate is followed in myPortal Insights, not in the report. ### 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. ## 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.myrspoven.com/evaluation-and-reporting/golden-reports/report-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.