> 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/faq.md).
# FAQ
Common questions from customers, partners, and system integrators. If you don't see your question here, talk to your Myrspoven representative or open a support case.
### Getting started
What is myCoreAI?
myCoreAI is software that continuously reads data from your building — the control system (BMS), indoor sensors, and the external factors that affect the building, such as outdoor temperature and weather. It uses that data to make small, continuous adjustments to the systems that drive temperature and comfort (supply temperatures, pressures, flows, and so on), steering them toward more efficient operation.
The goal isn't to replace your existing systems but to run them better: minimizing energy use by exploiting the building's thermal inertia, smoothing demand to avoid cost peaks, and pre-heating or pre-cooling ahead of need. The control happens automatically, within a framework agreed with you, and gets better the longer it runs.
You decide which signals myCoreAI is allowed to write to.
Does myCoreAI replace our BMS?
No. Think of myCoreAI as an application running alongside your building's control system — one focused on energy optimization. All the existing logic and frameworks in your BMS stay exactly as they are. myCoreAI works on top of them, and if it's ever disconnected, control simply returns to your BMS running on its own logic, as before.
Which BMS systems are supported?
Support isn't about brand or region — it's about whether the BMS can meet a few technical requirements. myCoreAI needs to be able to read the relevant signals from the system, write setpoints back to the signals you want it to control, and reach the system over a supported communication protocol (directly or via Myrspoven edge). A BMS qualifies when those things are possible; where they aren't yet, Myrspoven edge can often bridge the gap. The full integration requirements are covered under *Data and integrations*.
How long does onboarding take?
Onboarding runs in three stages:
1. **Read integration** — we connect and start reading data. This is the simple step; it mainly requires that we're granted access.
2. **Write integration** — we configure which signals myCoreAI will control and set up write-access to them. This is more involved: it requires agreeing which signals to steer and having the right access to change setpoint values on them.
3. **Safety logic** — fallback behavior, baselines, and the guardrails that keep the building safe if anything goes wrong.
How long each stage takes depends mostly on data access and how quickly write-access can be granted, but a building typically goes from kickoff to writing setpoints in weeks, not months.
How quickly will I see savings?
It helps to separate two things.
**Performance** — how myCoreAI's control compares against the baseline (how the building would have run without it) — can be shown within a few weeks. As long as we've received the right signal values from you, we can report the day-by-day difference between AI optimization and baseline on an ongoing basis.
**Measurable energy savings** — savings expressed in delivered energy — depend on having energy data, and the right energy data. Where that's in place, the evaluation runs continuously rather than waiting for a full season.
### Accounts and access
I can't log in, or my verification code isn't working.
myPortal uses single sign-on via Keycloak. Your one-time code comes from an **authenticator app** set up on your account — not from an email, and there is currently no email-code or magic-link option. Two things to check:
* **Have you signed in since the Keycloak migration?** You need to sign in once afterwards so Myrspoven can apply the correct access rights to your account.
* If your authenticator isn't set up yet, you've lost access to it, or sign-in still fails, contact your Myrspoven representative to restore access.
How do we add, remove, or change users?
User accounts and permissions are managed by Myrspoven — and, where enabled, by partner superusers for their own company. Request changes through your Myrspoven contact, giving the person's name, email, and which buildings or portfolio they need. A single account can be granted access across multiple companies or portfolios where the contract allows.
Why do times in myPortal look shifted by a few hours?
By default myPortal displays times in UTC, so locally set schedules can appear offset. Set your preferred display timezone in myPortal and times — including comfort schedules — will show in your local time.
### Data and integrations
What data does myCoreAI need?
To assess and onboard a building, we need to understand both what's in it and how we can reach it.
About the building's systems:
* which systems exist, and whether they can be controlled
* whether those systems already carry other control logic
* whether they're standalone or sit within the BMS
About sensors:
* whether the building has physical sensors (duct sensors alone aren't sufficient), how well distributed they are, and what they measure
* whether those sensors are available in the control system at a usable data resolution
About access:
* the communication protocol the building uses
* how we can reach it remotely (for example, via VPN)
This is the information that actually determines whether and how myCoreAI can run — more than a generic "minimum data" list.
What data resolution is required?
It depends on the type of data, so it's clearest to take them one at a time:
* **Sensor data** — ideally around 15-minute resolution or finer.
* **Signal data** — read directly, in real time.
* **Energy (meter) data** — See [Energy Data](/integrations/overview/energy-data.md#granularity-levels).
As a rule, give us the highest resolution you can: finer data unlocks better optimization and more precise reporting.
What if our energy meters aren't on the BMS?
Energy data can reach myCoreAI three ways: imported (uploaded manually), fetched directly, or pulled via a third-party provider (Mestro and Metry in Sweden). Connecting meters to the BMS is the simplest path where it's possible.
Whichever route you use, the resolution of the energy data matters — higher resolution gives more precise, climate-compensated savings reporting.
### AI behavior
What happens if myCoreAI makes a bad decision?
myCoreAI never optimizes toward an extreme. It optimizes toward the lowest energy use that still keeps the building inside the comfort bounds you've agreed — so it won't drive the building to the coldest (or warmest) state to save energy. Comfort is a hard constraint, not something it trades away.
The safeguards that protect your tenants are set during startup: comfort bounds per building, bounds on each controlled signal, and fallback behavior if anything goes wrong. If a building does drift outside its comfort bounds, myCoreAI can be paused for that building while the cause — usually a comfort bound, a sensor, or a configuration detail — is investigated.
Can we override myCoreAI?
Yes, myCoreAI doesn't take over your building. You can influence control at any time: through myPortal for the systems myCoreAI controls, and in your own BMS for everything else, exactly as before. You can step in even while myCoreAI is actively optimizing. You're never locked out of your own building.
What if we disagree with a setpoint myCoreAI has written?
On a signal myCoreAI controls, a one-off change in the BMS won't hold because myCoreAI re-applies its own setpoint on its next control cycle. To make a lasting change you have two routes: pause myCoreAI's control of that system, or adjust its configuration so it optimizes toward what you want.
Let your Myrspoven representative know what's wrong. Persistent disagreements usually trace back to a comfort bound, an occupancy assumption, or a sensor. The fix is to retune the configuration rather than fight individual setpoints.
What does myCoreAI actually control?
Typically: heating circuit supply temperatures, air handling unit supply temperature and fan pressure, cooling setpoints where applicable, and zone-level terminal units where the building has them. The exact list depends on what your BMS exposes and what's been configured during startup.
Does myCoreAI detect broken sensors or schedule maintenance?
A faulty sensor — one that has drifted, is stuck, or is reporting nonsense — is not something myCoreAI repairs.
What myCoreAI does is optimize a working system. Because its decisions are only as good as the data it reads, keeping sensors healthy is what lets the optimization stay accurate meaning unreliable input is a signal for maintenance, handled the same way as any other building fault.
### Reporting and savings
How are savings calculated?
Savings are measured against a baseline — a model of how the building would have used energy without myCoreAI — adjusted for weather and other variables.
Two timescales matter. Performance (myCoreAI versus baseline, day by day) can be shown within weeks, as soon as we have the right signal values. Energy savings expressed in delivered energy depend on having good energy data; where it's in place, that evaluation runs continuously rather than waiting for a full heating or cooling season. Reporting precision improves with the resolution of your energy data.
Where do I see savings and current operation?
In myPortal. You'll find dashboards for energy use, indoor climate, savings, and historical trends, plus a live view of current setpoints and what myCoreAI is doing right now. Performance against baseline is visible on an ongoing basis — you don't have to wait for a full season to see how the building is tracking.
Can we get raw data out for our own reporting?
Yes. Your data is yours, and it's always available to you. You can pull it for your own reporting and, where your systems support it, connect myCoreAI to your energy or follow-up systems through our integration APIs. See [Integrations](/integrations/overview.md) for what's possible; the exact exports available depend on your setup.
### Privacy and security
How is our data handled?
Your data is always yours. We process it only to operate and improve the service for your buildings, and it's encrypted both in transit and at rest.
Where is our data stored?
Your data is stored in EU-region data centers.
How is our data kept confidential?
All information for a given building or portfolio is treated as confidential. We don't share data between buildings or between portfolios. Myrspoven is ISO 27001 certified, and access is logged and scoped to the buildings a staff member supports.
Where can I read more about Myrspoven's security posture?
See [trust.myrspoven.com](https://trust.myrspoven.com/) for the current security overview.
### Billing and contracts
How is myCoreAI priced?
Pricing depends on building size, scope, and which optional features are enabled. Talk to your Myrspoven representative for a quote.
Which features are included in our contract?
It depends on your plan. The core optimization loop — myCoreAI HVAC optimization, indoor climate monitoring, energy reporting, and continuous model retraining — is always on. Beyond that, capabilities differ between Subscription and Enterprise:
| Feature / Service | Subscription | Enterprise |
| ---------------------------------------- | ------------ | ---------- |
| HVAC AI optimization (myCoreAI) | ✓ | ✓ |
| AI Dashboard & portfolio insights | Limited | ✓ |
| Load shifting & spot-price optimization | – | ✓ |
| Predictive maintenance | – | ✓ |
| Power limiting & tariffs | – | ✓ |
| Unlimited scale-up (fixed license) | – | ✓ |
| Open APIs & SDK – any vendor | – | ✓ |
| Portfolio benchmarking & CAPEX guidance | – | ✓ |
| Standardized data model | – | ✓ |
| Innovationsvalvet – roadmap influence | – | ✓ |
| Innovationsvalvet – network days (2+/yr) | – | ✓ |
| Innovationsvalvet – MVP & R\&D projects | – | ✓ |
| Innovationsvalvet – shared codebase | – | ✓ |
Check with your Myrspoven representative if you're not sure what's enabled for your buildings.
---
# 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/faq.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.