> 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/electricity.md). # Electricity This page covers the source-specific heuristics and assumptions behind electricity in the Golden Report. ## What gets measured Electricity powers many loads in a building. This report only breaks out the share assumed to power **air handling unit fans**. The rest stays outside the myCoreAI-controlled electricity calculation. ## How energy is distributed across uses The default assumption is: * **50%** of total electricity goes to AHU fans * **50%** goes to everything else The second half includes lighting, plug loads, tenant equipment, and other non-controlled loads. If you have a better building-specific split, Myrspoven uses that instead. ## What myCoreAI controls The myCoreAI-controlled share is the electricity used by air handling units. That total is then weighted by uptime for the period. ## Source-specific calculation details Electricity calculations are performed at the AHU level. They use hourly averages, then aggregate across relevant components and time stamps. This methodology only covers **ventilation electricity**. It does not separately break out electricity used for heating or cooling, such as heat pumps or electric chillers. ## Improving accuracy The biggest improvement is a real **ventilation-electricity split** for the building. If you have sub-metered ventilation electricity, share it with your Myrspoven representative to replace the default. --- # 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/electricity.md?ask=&goal= ``` `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.