> 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/getting-started/glossary.md).

# Glossary

This page defines the meaning of every product name, feature name, and recurring technical term used across Myrspoven docs.

***

### Adaptive comfort bounds

See [comfort bounds](#comfort-bounds).

### Adaptive min/max

A per-signal constraint applied by myCoreAI that clips the upper or lower bound of a supply-temperature setpoint relative to its baseline supply curve. Used to prevent the optimizer from operating in ranges that are uneconomical (e.g. very high summer supply temperatures) or unsafe during startup.

### AHU (air handling unit)

A mechanical unit that conditions and distributes ventilated air inside a building. myCoreAI controls AHU supply-air temperatures and, where applicable, fan pressure setpoints.

### AI control status

A per-signal setting that decides what myCoreAI may do with a signal. **Controlled** signals are read and written. **Observed** signals are read and used by the model, but never written. **Disabled** signals are not used. myCoreAI writes only to signals that are enabled for AI and set to Controlled.

### AI Freedom

A myCoreAI configuration parameter that allows the optimizer to move setpoints beyond the configured comfort bounds, drawing instead on learned reference limits derived from the [indoor climate baseline](#indoor-climate-baseline). Any value greater than zero activates the feature; the customer-visible control is effectively a binary on/off toggle.

### AI ON vs. OFF

The page in myPortal 2.0 that shows how savings are calculated: daily energy use against outdoor temperature, with one curve for days without myCoreAI and one for days with it. The gap between the curves is the saving. See [AI ON vs. OFF savings](https://docs.myrspoven.com/measure-savings/ai-on-off-savings.md) and [noted savings](#noted-savings).

### AI Penalty

The objective-function weighting system inside myCoreAI that balances comfort, equipment behavior, heating sources, cooling sources, and energy price across each optimization run. Higher penalties on comfort violations force the optimizer to stay within [comfort bounds](#comfort-bounds).

### AI uptime

See [uptime](#uptime).

### Baseline

The historical supply-curve or energy-consumption reference against which myCoreAI savings are measured. For heating and cooling, the baseline captures what the building consumed before myCoreAI was activated. For setpoints, the baseline supply curve describes the pre-AI control relationship between outdoor temperature and supply temperature. The **Baseline** line in Group Control and Equipment Control is this setpoint. Not to be confused with the [indoor climate baseline](#indoor-climate-baseline), which is about room temperatures.

### BMS (Building Management System)

The on-site automation system that reads sensors and actuates equipment in a building. myCoreAI connects to the BMS directly or via the [Myrspoven edge](#myrspoven-edge) to read sensor values and write [setpoints](#setpoint).

### Building baseline

See [indoor climate baseline](#indoor-climate-baseline).

### CO₂

Carbon dioxide concentration, measured in ppm, used as an indoor air-quality observable.

### Comfort bounds

The configured upper and lower limits within which myCoreAI may move indoor-climate or setpoint values. Comfort bounds carry the highest penalty weight in optimization. See also [AI Freedom](#ai-freedom), which allows the optimizer to draw on learned bounds rather than fixed ones.

### Deviations

A page in myPortal 2.0 that compares each point's recent values with its own history under similar conditions, such as the same outdoor temperature, and flags the hours outside its normal range. A deviation is a change from the point's own normal, found without any alarm limits; it is not an alarm and not always a fault. See [Deviations](https://docs.myrspoven.com/use-myportal-2.0/deviations.md).

### Digital twin

The customer-facing term for the physics-informed model of a building that myCoreAI uses to predict how supply-temperature changes propagate to indoor temperatures.

### District cooling

A centralized cooling distribution system in which chilled water is supplied from a remote plant and metered at the building. myCoreAI controls cooling-circuit setpoints and AHU cooling to reduce district-cooling consumption.

### District heating

A centralized heat distribution system in which hot water is supplied from a remote plant and metered at the building. myCoreAI controls heating-circuit supply-temperature setpoints to reduce district-heating consumption.

### Draught control

A myCoreAI feature that raises the lower bound on heating-circuit supply temperatures on cold days between 07:00 and 17:00 (outdoor temperature below 5 °C), offsetting cold downdraughts (Swedish: kallras) near windows and facades.

### Edge

See [Myrspoven edge](#myrspoven-edge).

### ENTSO-E spot price

The day-ahead electricity price published by the European Network of Transmission System Operators for Electricity. Used by [myLoadshift](#myloadshift) to shift heating load away from high-price periods.

### Golden Report

Myrspoven's earlier monthly savings report. It is no longer sent: savings are followed with [AI ON vs. OFF savings](https://docs.myrspoven.com/measure-savings/ai-on-off-savings.md).

### Groupings

A myCoreAI mechanism that controls indoor climate by sensor group rather than by individual sensor: it holds the group average temperature inside a band defined by the averaged per-sensor bounds, acting only when the group as a whole drifts outside it. This stabilizes control by preventing a single outlier sensor from dominating. See also [comfort bounds](#comfort-bounds).

### Guardrails

Hard absolute limits on setpoint values that myCoreAI does not cross, regardless of penalty configuration or AI Freedom settings. Guardrails include crash-protection limits and rate-of-change constraints. Distinct from [comfort bounds](#comfort-bounds), which carry the highest penalty weight in optimization.

### Indoor climate baseline

Comfort limits for indoor temperature that myCoreAI learns from the building's own history, from periods when Myrspoven was not steering. When [AI Freedom](#ai-freedom) is active, myCoreAI uses them where they are wider than the configured [comfort bounds](#comfort-bounds). The Climate Baseline line in myPortal 2.0 charts is a different thing: it shows how the rooms would have run without Myrspoven and is not a limit. In [Sensor Map](https://docs.myrspoven.com/use-myportal-2.0/sensor-map.md) these limits are called the **building baseline**: a room is compared with them, one range for office hours and one for other hours, instead of with its own min and max. See [Indoor climate baseline](https://docs.myrspoven.com/how-the-ai-saves-energy/indoor-climate-baseline.md).

### Measurement week

A period of about a week when Myrspoven switches optimization off to collect [reference data](#reference-data) for a range of outdoor temperatures that the building's history does not yet cover. See [Indoor climate baseline](https://docs.myrspoven.com/how-the-ai-saves-energy/indoor-climate-baseline.md#how-reference-data-is-collected).

### Mixed circuit control

A myCoreAI control mode for a circuit that feeds both another heating or cooling circuit and at least one air handling unit (AHU), so that neither load is starved. See [Mixed circuit control](https://docs.myrspoven.com/how-the-ai-saves-energy/mixed-circuit-control.md).

### myCoreAI

Myrspoven's AI optimization engine. myCoreAI runs in the cloud, receives sensor readings from a building, directly or via the [Myrspoven edge](#myrspoven-edge), predicts indoor-climate responses using a [digital twin](#digital-twin), and writes [setpoints](#setpoint) back to the [BMS](#bms-building-management-system).

### myLoadshift

A myCoreAI feature that shifts heating load in time by pre-heating a building during low-price or low-tariff periods, and reducing load during expensive periods. Draws on [ENTSO-E spot prices](#entso-e-spot-price) or a dynamic district-heating tariff signal.

### myPortal

The customer-facing web application where building owners and facility managers monitor myCoreAI performance, review setpoint trends, check indoor-climate compliance, and upload energy data. See [myPortal](https://docs.myrspoven.com/other-interfaces/myportal.md).

### myPortal 2.0

The new customer interface, which is replacing [myPortal](#myportal). It shows a portfolio's alerts, savings, indoor climate and AI status, and lets users switch the AI on or off per building, equipment or point. Which pages a user sees depends on their role. The release notes from August 2026 call it the new customer interface. See [myPortal 2.0](https://docs.myrspoven.com/use-myportal-2.0/myportal-2.md).

### Myrspoven edge

The on-premise software component installed at a building that polls the [BMS](#bms-building-management-system) on the schedule set for the building in Myrspoven's cloud, forwards sensor readings, and applies setpoint writes received from [myCoreAI](#mycoreai).

### Noted savings

A day's saving for one energy meter, from the gap between the meter's energy curves with and without myCoreAI at that day's outdoor temperature. It is noted the morning after, or as soon as the meter's curves pass their quality checks, and is never revised afterwards. Days without a noted saving are shown as in progress and left out of savings totals. See [AI ON vs. OFF savings](https://docs.myrspoven.com/measure-savings/ai-on-off-savings.md).

### Optimization horizon

The look-ahead window over which myCoreAI solves its optimization problem. Typically 72 hours.

### Optimizer

The component of myCoreAI that solves the energy-comfort trade-off at each run.

### Reference data

Data from periods when Myrspoven was not steering the building: before the start, or during a [measurement week](#measurement-week). The [indoor climate baseline](#indoor-climate-baseline) is learned from it, and savings are measured against it. Data from a vacancy is not valid reference data, and reference data has to be renewed after rebalancing, reprogramming or a long shutdown.

### Reports API

The HTTP API partners use to read the status of their own buildings into their own systems: building states, hourly AI status, steered equipment and alerts. See [Reports API](https://docs.myrspoven.com/developers/reports-api).

### Safe mode

The fallback operating state myCoreAI enters when it cannot reliably predict building behavior (e.g. because sensor data is stale or BMS writes are failing). In safe mode, myCoreAI suspends setpoint writes; the BMS reverts to its native control strategy.

### Setpoint

A target value that myCoreAI writes to the BMS — for example, a heating-circuit supply temperature or AHU supply-air temperature.

### Signal

A named data stream from or to the BMS, identified by a signal key. Signals can be readable (sensor readings) or writable (setpoints). The set of signals for a building is captured in a signal list produced during technical survey.

### Supply curve

The pre-AI control relationship between outdoor temperature and heating-circuit supply temperature for a building. myCoreAI's [baseline](#baseline) is derived from the supply curve; [adaptive min/max](#adaptive-minmax) clips the optimizer's range relative to it.

### Tariff signal

A dynamic pricing signal — either an ENTSO-E spot-electricity price or a time-varying district-heating tariff — that [myLoadshift](#myloadshift) uses to shift building load in time.

### Uptime

The fraction of eligible optimization-run slots during a reporting period in which myCoreAI was actively writing setpoints (i.e. not in [safe mode](#safe-mode) and not manually paused). In myPortal 2.0 the 3-, 7- and 30-day uptime needs meter data; a building without meter data, or one that started recently, shows only the last 24 hours. See [Building overview](https://docs.myrspoven.com/use-myportal-2.0/building-overview.md).


---

# 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/getting-started/glossary.md?ask=<question>&goal=<user_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.
