Overview

myCoreAI runs on operational data from buildings and external data providers. Integrations bring those values into Myrspoven and, where the connected system supports control, return new setpoint values to the building.

This chapter covers the available integration options and the requirements on the building side.

Technical operations: confirm which signals myCoreAI needs to read and, where relevant, which setpoints it may write. Integrators: scope the API, protocol, edge component, network access, and commissioning handover. Asset managers: understand which data sources are used and how energy, sensor, IoT, and weather data are ingested.

Integration models

Myrspoven integrations use two main models.

Myrspoven integrates to external APIs

In this model, Myrspoven is responsible for writing and maintaining the integration code. myCoreAI connects to the external system, reads the configured values, and writes new setpoint values back when the connected system supports control.

Supported BMS and SCADA integrations include dedicated platform connectors and protocol-based integrations:

• Web Port
• Siemens Building X
• Ouman
• Fidelix Analytics
• ProptechOS

These integrations support both reading BMS data and writing new setpoint values.

The named platforms are not the full limit of what can be connected. Web Port is a gateway layer with driver support for many field protocols and device types, which lets Myrspoven integrate with a wider range of local BMS and automation setups than the vendor list alone suggests. See Web Port driver support and Web Port.

Myrspoven also supports smaller read-only integrations for sensor, IoT, energy, weather, and environmental data:

• Yggio
• EcoGuard
• PropEye
• Mestro
• Metry
• Radonova
• OpenMeteo
• AirThings

Most integrations in this model are HTTP/REST-based. Myrspoven also supports MQTT-based integrations where that is the right fit for the external system.

External providers integrate to Myrspoven

In this model, the external provider is responsible for sending values to Myrspoven. The provider uses the Myrspoven AI-API to send values from a BMS or other data provider, and to pick up new setpoint values when they are available.

This model is used when the external party owns the connection to the BMS or data platform and can expose the required values through the Myrspoven AI-API.

In practice, Myrspoven can onboard buildings through:

• Dedicated vendor integrations, such as Siemens and Schneider.
• Protocol-based integrations through Web Port and its driver ecosystem.
• External partners that deliver data and setpoints through the Myrspoven AI-API.

Contents

• BMS Integrations — BMS and SCADA integrations, read/write scope, protocol coverage, and connection requirements.
• Energy data — options for ingesting consumption data, including BMS pickup, Mestro, Metry, and manual upload. Higher resolution improves optimization results.
• Myrspoven API — API access for data ingestion and setpoint pickup.

Requirements on the building side

Requirements depend on the integration model and the data source. A typical project may need:

• Access to the external API, BMS, SCADA system, or data provider that holds the required values.
• BMS read and write access when myCoreAI is configured to optimize and control setpoints.
• API credentials or an agreed authentication method for read-only third-party providers.
• A virtual server in the building network when an on-premise edge component is used.
• Outbound network access from that server to the Myrspoven cloud. No inbound firewall openings.
• A technical point of contact for commissioning and signal mapping.

Signal list, data ownership, and setpoint scope are agreed during a technical survey and do not change without explicit configuration.