> 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. Where two terms existed before this glossary, the entry here is the one all agents and writers should use going forward. *** ### 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 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 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. ### BMS (Building Management System) The on-site automation system that reads sensors and actuates equipment in a building. myCoreAI connects to the BMS via an [edge](#myrspoven-edge) component to read sensor values and write [setpoints](#setpoint). ### 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 protect occupant comfort and are never violated by the optimizer. See also [AI Freedom](#ai-freedom), which allows the optimizer to draw on learned bounds rather than fixed ones. ### 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. Internally called the Xindy model; "digital twin" is the preferred customer-facing label. ### 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 during cold-weather office hours (outdoor temperature below 5 °C, 07:00–17:00), 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 and cooling load away from high-price periods. ### Golden Report Myrspoven's recurring PDF performance report delivered to customers. Covers energy savings per source (district heating, district cooling, electricity), indoor-climate compliance, AI uptime, and AI insights. ### 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 never crosses, 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 are softer configured limits the optimizer typically respects. ### HDD (Heating Degree Days) A climate-normalization metric equal to the sum of degrees by which daily mean outdoor temperature falls below a base temperature. Used in [climate-compensated reporting](/evaluation-and-reporting/climate-compensated.md) to remove weather effects from energy savings calculations. ### Indoor climate baseline The per-building historical record of indoor temperatures and other comfort observables from which myCoreAI derives learned reference limits. When [AI Freedom](#ai-freedom) is active, the optimizer may use these learned limits rather than the fixed configured [comfort bounds](#comfort-bounds). ### Mixed circuit control A myCoreAI control mode for HVAC circuits that serve both heating and cooling (i.e. circuits where the supply temperature can be above or below the ambient depending on season). ### MyCap A myCoreAI feature that enforces an energy-consumption or power-demand cap for a building, limiting the optimizer's actions to prevent the building from exceeding a contracted threshold. Referred to in customer-facing prose as "energy cap". ### myCoreAI Myrspoven's AI optimization engine. myCoreAI runs in the cloud, receives sensor readings from a building 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 and cooling load in time by pre-heating or pre-cooling 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. ### Myrspoven edge The on-premise software component installed at a building that polls the [BMS](#bms-building-management-system), forwards sensor readings to Myrspoven's cloud, and applies setpoint writes received from [myCoreAI](#mycoreai). ### 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. ### RMSE (Root Mean Square Error) A model-accuracy metric myCoreAI uses to assess how well the [digital twin](#digital-twin) predicts indoor temperatures. If RMSE exceeds a threshold (nominally 1.7 for Schneider EBO sites), myCoreAI may fall back to safe mode and suspend setpoint writes. ### Safe mode The fallback operating state myCoreAI enters when it cannot reliably predict building behavior (e.g. because RMSE exceeds the threshold, 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). ### Xindy model The internal name for Myrspoven's physics-informed building model. Customer-facing documentation uses the term [digital twin](#digital-twin) instead. --- # 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/getting-started/glossary.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.