Integrations
A BMS — Building Management System — is the control system that runs a building's HVAC, lighting, and energy infrastructure. It's also the largest underused source of operational data in modern facilities.
A building management system (BMS, sometimes called a BAS, building automation system) is the network of controllers, sensors, and actuators that operate a building's heating, ventilation, air-conditioning, lighting, and increasingly its electrical, water, and access systems. It senses conditions, applies control logic, and drives equipment to keep a building comfortable, safe, and efficient.
What a BMS controls. A typical BMS supervises HVAC — air-handling units, chillers, boilers, heat pumps — along with lighting schedules, energy and submetering, and often access control, fire, and lifts. Field controllers run the local logic; a head-end supervisor pulls them into a single operator interface.
The core components. Sensors and actuators sit in the field. Programmable controllers (DDC) run the control loops. A supervisor layer is where operators see values and change setpoints. Tying it together is a network protocol — usually BACnet, with Modbus and OPC UA where older or industrial gear is involved.
BMS vs BAS vs BACS vs EMS. The acronyms overlap and trip people up. BMS (building management system) and BAS (building automation system) are used interchangeably. BACS (building automation and control system) is the term EU regulation uses — it's the wording in the EPBD. An EMS (energy management system) is narrower: it focuses on metering and energy optimisation rather than running the plant. In practice, if it runs the building's HVAC and controls, people call it a BMS.
| Term | Stands for | Scope |
|---|---|---|
| BMS | Building Management System | Runs HVAC, lighting, energy and controls. The general term. |
| BAS | Building Automation System | Same thing; used interchangeably with BMS. |
| BACS | Building Automation and Control System | The regulatory term (EU EPBD). |
| EMS | Energy Management System | Narrower — metering and energy optimisation, not plant control. |
The vendors you'll meet. Most Nordic buildings run one of Siemens (Desigo), Schneider Electric (EcoStruxure), Honeywell (Niagara), Trend, or Bastec. A large portfolio usually has several, of different generations, which is exactly why a vendor-neutral layer on top is useful.
Why the data matters. Every modern BMS logs telemetry — supply-air temperatures, energy use, valve positions, alarm states — and most of it is never read. A BMS is built to control, not to analyse. BMS analytics is the layer that turns that telemetry into operator decisions: which fault to fix first, which drift will become a tenant complaint by Friday, which floor is dragging the energy bill.
How FrostLogic reads a BMS. FrostLogic Explore reads from a BMS over standard protocols (BACnet, Modbus, OPC UA) or vendor APIs. The connection is read-only by default — Explore adds an analytics and decision layer on top, it does not replace your control system.
Before you ask
Building management system. Some vendors say BAS (building automation system); EU regulation calls it BACS. They mean the same thing: the system that runs a building's HVAC and controls.
None worth arguing about. BMS and BAS are used interchangeably. BACS is the regulatory term in the EPBD. If it runs the building's plant, people call it a BMS.
Most often BACnet, with Modbus on older meters and plant and OPC UA on industrial gear. One building frequently runs more than one.
Yes, but not from the BMS itself — it's built to control, not analyse. A read-only analytics layer like FrostLogic Explore turns its telemetry into a ranked list of what to act on.
Siemens (Desigo), Schneider (EcoStruxure), Honeywell (Niagara), Trend, and Bastec are the ones we see most across Nordic buildings.
Related terms
See it in product
This is the engine that ships sensor intelligence as a product. Anomaly detection across six methods, forecasting with explicit confidence bounds, continuous compliance, and what-if simulation — all grounded in your own telemetry, all explainable, all auditable.
See FrostLogic Explore in action