What is a BMS?

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 in the field, DDC controllers for local loops, and a supervisor where operators work, tied together by a network protocol. The next section walks that stack in order. For what's physically inside a controller and its control panel, see our BMS controller guide.

How does a BMS work?

A BMS works as a stack. Field sensors measure temperature, humidity, occupancy and flow; actuators open valves, dampers and relays. Local DDC controllers run the control loops that keep those points on setpoint. A supervisory head-end is where operators see live values, acknowledge alarms and change schedules. Network protocols such as BACnet, Modbus, OPC UA and oBIX stitch those layers together. Analytics, when present, sits above control: it reads the same points and ranks what to fix next. It does not replace the BMS that runs the plant. In some regions the same stack is called a building automation system.

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. For the analysis half of that stack, see Explore's energy management layer.

What is BMS software?

BMS software is the supervisory and engineering applications that run on the head-end: the operator workstation, graphics, schedules, alarm consoles and the tools used to commission controllers. It is distinct from the field controllers themselves. Controllers execute loops; the software is where people see the building and change how those loops are configured. When teams want analysis rather than another control screen, they add a layer such as BMS analytics in FrostLogic Explore that ranks faults and drift from the same points the BMS software already exposes.

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. For connecting your BMS to Explore, the path is the Edge Agent over the protocols those vendors already expose.

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. Continuous meter reads sit under Explore's continuous meter layer.

How FrostLogic reads a BMS. FrostLogic Explore reads from a BMS over standard protocols (BACnet, Modbus, OPC UA, oBIX) or vendor APIs. Write access starts off — Explore adds an analytics and decision layer on top, it does not replace your control system. For how those protocols differ, see our building integrator's guide to BACnet, Modbus and OPC UA. Scoped write-back lives under Explore Automation.