A commercial building typically exposes several hundred controllable data points, yet only a fraction ever reaches the SCADA platform. That gap shows up twice: in energy bills nobody can account for, and in faults detected days too late. An effective BMS SCADA project therefore starts with one question, which assets should be mapped, and in what order.
This guide lists the equipment families worth supervising and sets out a method for prioritising their integration.
Key takeaways
- A BMS SCADA scope covers eight asset families, from HVAC to safety-security.
- BMS controls a single building, FM centralises several BMS installations across a site or an estate.
- Each asset speaks its own protocol (BACnet, Modbus, KNX, M-Bus), so all of them must converge into one open platform.
- Mapping means prioritising by criticality, energy weight and regulatory obligation.
BMS and FM: two complementary scopes to distinguish
A BMS (Building Management System) controls the assets of a single building: heating, ventilation, lighting, energy. FM (Facility Management) federates several BMS installations and technical systems at site or portfolio level. This distinction structures the mapping exercise: you inventory assets building by building, then decide which data points deserve to be centralised.
Blurring the two levels produces two failures we see repeatedly in practice: pushing local data with no operational value up to the central layer, or siloing information that would gain from being correlated. A single operating logic across both scopes settles that split.
BMS SCADA: mapping assets discipline by discipline
Mapping assets means listing every technical system in the building, its measurement points and its communication method. In a commercial building, eight families concentrate most of the BMS SCADA workload:
- HVAC (heating, ventilation, air conditioning): air handling unit control loops, temperature and humidity sensors, pumps and valves. The first driver of both occupant comfort and consumption.
- Lighting: zone commands, presence detection, time schedule management, fault reporting.
- Electrical distribution: main low voltage switchboards, sub-metering by end use, power circuit measurement.
- Backup power: UPS units and generator sets, whose status and remaining autonomy condition service continuity.
- Lifts and lifting equipment: availability, alarms, maintenance call-outs.
- Access control and safety-security: readers, CCTV and intrusion panels, usually handled at FM level.
- Fire detection: status and alarm reporting to the SCADA platform, within the constraints imposed by the fire safety system.
- Fluids and water: metering, sanitary networks and hot water thermal control to prevent legionella risk.
Federating heterogeneous protocols in one BMS SCADA platform
Protocol interoperability is a platform’s ability to exchange data with assets from different vendors running different protocols. A commercial building routinely combines BACnet for HVAC, Modbus for energy, KNX or LON for lighting and M-Bus for metering, alongside more recent connected devices.
The difficulty is not reading one protocol, it is bringing them all together without a proprietary gateway. An open platform makes legacy controllers and connected sensors converge into a single application, avoiding a rebuild of the map every time the estate evolves. That is the condition for a BMS SCADA deployment to stay usable over time.
Prioritising the BMS SCADA map by criticality and energy
Prioritising the map means ranking assets by criticality, energy weight and regulatory obligation. A BMS SCADA project is not about pushing everything up to the operator, it is about pushing up what counts.
Three criteria drive that arbitration. Criticality comes first: safety-security assets and anything guaranteeing service continuity take priority. Energy comes second: the French Tertiary Decree, in force since 2019, mandates a 40% cut in final energy consumption by 2030 against a reference year, which makes granular sub-metering unavoidable. Compliance closes the list: the BACS decree, published in 2020 to transpose the European EPBD directive, requires automation and control functions in buildings whose HVAC systems exceed 290 kW of rated output, a threshold falling to 70 kW in 2027.
From asset register to BIM for Operation
BIM for Operation cross-references real time SCADA data with the digital model of the building. The asset map then becomes a live map, where every measurement point is located in its actual environment.
This approach turns a static register into an operating tool. An operator spots the faulty asset on the floor plan, opens its maintenance history and documentation, and saves time on intervention. BMS SCADA moves up a level here, from a flat point list to a spatialised view of the estate.
Mapping assets is the prerequisite for any effective BMS SCADA deployment: without a structured inventory of technical systems, their measurement points and their protocols, operation stays partial and reactive. The method holds in three steps: list, prioritise by criticality and energy, then federate into an open platform. To build that register across your own portfolio, talk to CODRA’s building supervision experts.
