> 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/integrations/overview/bms-integrations.md). # BMS Integrations ## Overview myCoreAI connects to a building's existing Building Management System (BMS) to read sensor and meter values and to write the setpoints it has been configured to control. The BMS keeps operational control; only the agreed signals are touched. **Asset and facility management:** myCoreAI improves user comfort and energy efficiency on the BMS already installed — no controls-hardware replacement. **Technical operations:** myCoreAI exposes setpoint behavior, bounds, and overrides as auditable signals. The BMS remains the single source of operational truth. **Integrators:** myCoreAI connects over standard protocols (REST, OPC UA, BACnet, Modbus, or a vendor SDK), with a Myrspoven edge available where direct access isn't viable. ### How the integration works The communication flow between Myrspoven and the building can happen in one of two main ways: 1. **Direct BMS connection.** myCoreAI connects to the BMS over a network-reachable interface — This is most common when the building can be controlled via a cloud platform or when the local BMS is reachable from the internet through the local firewall. Data flows in both directions on the agreed signal list. 2. **Via Myrspoven edge.** Where direct access isn't viable — closed networks, legacy protocols, segmented IT environments — a small edge application runs on a virtual server inside the building's network and bridges the BMS to the Myrspoven servers. The edge application polls the Myrspoven servers and sends data/retrieves setpoint updates, so no inbound firewall rules are required. In both scenarios the BMS keeps operational control. myCoreAI reads only the signals it has been configured to read, and writes only the setpoints it has been configured to write. ### Read and write Reads run continuously — typically every minute, and at most every five minutes, depending on the integration. (Reporting and the UI dataset are sampled down to hourly.) Common reads include data from indoor sensors (temp, CO₂ and humidity), outdoor temperature, energy meters, current setpoints, and equipment status. Writes are limited to the setpoints agreed during startup. Typical setpoints are heating-circuit supply temperature setpoints, air handling unit (AHU) supply temperature and fan setpoints, cooling setpoints, and zone-level terminal unit setpoints where the BMS exposes them. Write operations occur whenever an optimization run has successfully produced new setpoint values. Each writable setpoint has minimum and maximum bounds agreed up front; myCoreAI cannot push a setpoint outside those bounds. Manual overrides from the BMS take effect immediately, and myCoreAI adapts on the next read. Writes can also be paused per building — reads and reporting continue, but actuation stops. ### Supported BMS platforms and protocols The platforms below are in production today. They are common delivery paths, not a hard limit on what Myrspoven can connect to. | Platform | Vendor | Connection | Status | Detail | | ---------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | --------- | | **Web Port** | Kiona | Local Web Port server (Windows) → Myrspoven Web Port-Cloud; Modbus / BACnet / industrial protocols on the local side | In production | Web Port | | **EcoStruxure Building Operation (EBO)** | Schneider Electric | On-premise via Myrspoven edge, or cloud via Schneider SmartConnector; dedicated Read / Write / Overwrite-Bindings folders on the EBO side | In production | Schneider | | **Building X (BPCloud)** | Siemens | JSON:API over HTTPS, OAuth2 client credentials. Semantic mapping of tagged equipment/points → Myrspoven components and signals | In production | Siemens | | **Desigo CC** | Siemens | Legacy on-prem path; requires manual virtual-signal setup in the BMS | In production (legacy) | Siemens | ### Broader protocol coverage through Web Port Web Port acts as a protocol gateway. It supports a broad set of drivers for building automation and industrial protocols. That expands the practical integration surface well beyond the named vendors on this page. If a building exposes the required signals through a Web Port-supported driver, Myrspoven can often integrate without needing a dedicated vendor-specific connector. Final fit still depends on signal availability, write scope, network access, and project requirements. See [Web Port](/integrations/overview/bms-integrations/web-port.md) and [Web Port driver support](https://kiona.com/products/web-port/driver-support). For platforms not listed here, contact Myrspoven to assess the best path — direct connector, Web Port, or Myrspoven AI-API. ### What's needed to onboard a new building The building owner or integrator typically provides: * A **signal list** for reads and an allowed-setpoint list for writes. Produced together during the technical survey. * A **point of contact** at the BMS integrator for commissioning. For a building with a Local BMS behind firewall that needs Myrspoven edge, the additional requirements are: * A **virtual server** in the building's network for the Myrspoven edge (when the Myrspoven edge solution is used). * **Outbound network access** from that server to the Myrspoven cloud. * **BMS access** — read and write — on a supported protocol. * **Temporary VPN access** during edge installation and configuration. No operational traffic uses the VPN. ### Updates/maintenance of Myrspoven edge To streamline updates of the Myrspoven edge installations we use [Octopus Deploy](https://octopus.com/). We install an Octopus tentacle on the virtual machine in your network that checks regularly with our Octopus server if there is a new version to download and install. It will make outbound requests using https and download updated software when available. It can also update itself when needed. ### Security All BMS connections are encrypted. Write scope is restricted to the agreed setpoint list and cannot be widened without explicit configuration. The edge polls outbound only — no inbound ports are opened on the building's network. *** --- # 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/integrations/overview/bms-integrations.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.