BACnet, Modbus, KNX, LonWorks, M-Bus, energy meters, HVAC, lighting, charging stations, air quality sensors: a smart building has no shortage of data; what it often lacks is an architecture to connect them. Eziwan aggregates building management (BMS), building control (LCS), and building IoT protocols into a multi-site monitoring system that is easy to read, actionable, and aligned with the energy goals of the commercial sector.
Why Smart Buildings Remain Difficult to Manage
Modern commercial buildings are equipped with numerous technical systems: heating, ventilation, air conditioning, lighting, metering, access control, elevators, charging stations, solar power generation, chillers, boilers, pumps, air handling units, room temperature sensors, and indoor air quality sensors.
On paper, everything is automated. In reality, however, each technical system often has its own protocol, integrator, interface, and maintenance history. As a result, the facility operator ends up with a fragmented view of the building.
The most common difficulties are practical:
- multiple software interfaces for managing HVAC, lighting, energy, access, and maintenance;
- lack of a multi-site view to compare the performance of a building portfolio;
- inability to correlate occupancy, temperature, CO2 levels, lighting, and energy consumption;
- hidden energy waste: heating on weekends, cooling of vacant areas, and nighttime lighting;
- Metering data scattered across electricity, gas, water, heat, and tenant sub-metering;
- Legacy equipment using BACnet MS/TP, Modbus RTU, or LonWorks that is difficult to integrate into the cloud;
- Maintenance interventions initiated too late due to a lack of consolidated alerts;
- difficulty documenting energy efficiency measures for ISO 50001, the Tertiary Sector Decree, or the BACS Decree;
- electric vehicle charging stations controlled separately, without load shedding in coordination with the building;
- indoor air quality monitored separately from ventilation.
IoT connectivity for smart buildings is therefore not just about adding sensors. It involves enabling existing systems to communicate with each other, standardizing data, and providing actionable insights.
Target Architecture for Multi-Site Building Management System (BMS) Monitoring
A robust architecture places an Eziwan gateway in the utility room of every building. It collects local data via BACnet, Modbus, KNX, M-Bus, or specialized gateways, then transmits it to a centralized platform. Operators then have a shared dashboard to monitor energy usage, comfort levels, alarms, and maintenance.
This structure eliminates the need to replace the entire existing building management system. It creates a layer of interoperability on top of the systems already in place, which is often a more realistic approach in a heterogeneous commercial building portfolio.
Building Management Systems (BMS), Centralized Building Control (CBC), Building Automation (BA), and Building IoT: Clarifying Their Roles
The terms are sometimes used interchangeably, even though they do not cover exactly the same scope.
| Term | Primary Role | Examples of Equipment |
|---|---|---|
| BMS | Building Management System | HVAC, metering, technical alarms, setpoints |
| GTC | Centralized Technical Management | Monitoring of a specific technical scope |
| GTL | Technical System Management | Lighting, access control, subsystems by system |
| Building IoT | Sensors and connected devices | IAQ, occupancy, temperature, sub-metering |
| EMS | Energy Management System | Metrics, action plans, ISO 50001 reporting |
The value of a connectivity platform like Eziwan lies in its ability to connect these layers without locking users into a single vendor. It collects, translates, logs, and presents data for energy, maintenance, operations, and property management teams.
Supported Building Protocols
A smart building is rarely homogeneous. The gateway must therefore handle both field protocols and application protocols.
| Protocol | Common Uses | Points to Watch |
|---|---|---|
| BACnet/IP | Modern building management systems, HVAC, building controllers | Clearly name objects and properties |
| BACnet MS/TP | HVAC controllers on serial bus | Data rate, bus termination, addressing |
| Modbus TCP | Meters, controllers, energy | Registers must be precisely documented |
| Modbus RTU | Legacy RS-485 equipment | Cabling quality and addressing plan |
| KNX IP | Lighting, blinds, ambiance | Group addresses must be mapped |
| M-Bus | Water, gas, heat, sub-metering | Reading frequency and meter reading quality |
| LonWorks | Older installations | Dedicated gateway often required |
| OCPP | EV charging stations | Power control and billing |
tip: Good practice Before connecting a building, map out the key data points: name, protocol, unit, collection frequency, criticality, business use, and person in charge. Data without context quickly becomes unusable.
Normalize the data to make it usable
The challenge isn’t just reading a Modbus register or a BACnet object. You have to transform technical data points into understandable business data.
Useful examples of standardization:
- Convert units: Wh, kWh, m³, degrees Celsius, ppm, percentage;
- Distinguish between measurement, setpoint, status, fault, and command;
- Associate each data point with a building, floor, zone, usage, or tenant;
- consistently time-stamp values;
- detect outliers or static values;
- document the rules for calculating indicators;
- maintain a history to compare data before and after an action.
Without this step, a multi-site dashboard risks comparing data that does not measure the same thing.
Multi-site Dashboard: Managing a Portfolio, Not Just a Single Building
A facility manager who oversees ten, fifty, or several hundred buildings does not need to open a separate building management system for each site. They need a consolidated view.
The priority indicators are generally:
- total electricity consumption;
- HVAC consumption;
- lighting consumption;
- consumption per square meter;
- deviation from a baseline;
- average temperature by zone;
- CO2 levels;
- active technical issues;
- status of critical equipment;
- connection availability;
- sites with anomalies;
- energy rating of the facility portfolio.
Effective multi-site monitoring helps answer simple but critical questions: Which building is deviating from standards? Which area is consuming energy when unoccupied? Which equipment is failing too often? What action actually yields results?
Energy: Detecting Hidden Energy Waste
Energy savings don’t come solely from major projects. A significant portion comes from adjustments, scheduling, and detecting deviations.
Typical cases of excessive consumption that can be detected:
- Heating and air conditioning running simultaneously;
- HVAC system restarting too early in the morning;
- Setpoints remaining active on weekends;
- Lights left on when the space is unoccupied;
- Ventilation set too high in an empty area;
- air handling unit malfunctioning without a visible alert;
- sub-meter drifting;
- charging station triggering a power spike;
- setpoint temperature changed locally and then forgotten.
Energy savings vary significantly depending on the building’s initial condition, the quality of the existing building management system, occupancy, and building uses. The ranges of reduction must therefore be validated through measurement, using a reliable baseline and a consistent monitoring method.
Tertiary Decree, BACS, and ISO 52120-1
IoT connectivity in buildings directly supports regulatory and energy initiatives, but it does not replace the regulatory analysis specific to each building portfolio.
The Tertiary Sector Decree applies to buildings, parts of buildings, or groups of buildings used for tertiary purposes with a floor area of at least 1,000 m². It mandates a trajectory for reducing energy consumption, with annual reporting via OPERAT.
The BACS Decree requires the installation of building automation and control systems in commercial buildings equipped with heating or air conditioning systems that exceed the power thresholds defined by regulations.
The EN ISO 52120-1 standard, which is gradually replacing the previous EN 15232-1 standard, provides a framework for evaluating the contribution of building automation, control systems, and technical building management to energy performance.
| Table | Objective | Useful Data |
|---|---|---|
| Tertiary Sector Decree | Monitor and reduce energy consumption | annual consumption, floor area, usage patterns, baseline |
| BACS Decree | Automate and control technical systems | building management systems (BMS), setpoints, schedules, faults, monitoring |
| ISO 50001 | Manage energy over the long term | Energy Performance Index (EPI), action plans, measurements, and verifications |
| EN ISO 52120-1 | Assess the impact of automation | Building Management System (BMS) functions, control, performance classes |
Key Takeaway Compliance isn’t just about installing a building management system. It also requires generating reliable, historical, comparable, and actionable data to guide actions over time.
Indoor Air Quality and Comfort
Energy efficiency should not compromise comfort or indoor air quality. IAQ sensors allow ventilation to be controlled based on actual occupancy rather than a fixed schedule.
Useful data for IAQ:
- CO2;
- volatile organic compounds;
- temperature;
- relative humidity;
- fine particulate matter, if required by the situation;
- actual or estimated occupancy;
- ventilation flow rate;
- filter condition;
- air handling unit (AHU) malfunctions.
The purpose of integration is to link measurements to actions. High CO2 levels in a meeting room should trigger an alert, increase the ventilation airflow, or indicate a problem with the HVAC system. Conversely, an unoccupied area can reduce its ventilation airflow in accordance with the building’s applicable regulations.
Controlling Charging Stations with OCPP
Electric vehicle charging stations place a significant load on a building. Without proper coordination, they can cause costly power spikes or compete with the site’s technical systems.
The OCPP integration allows you to control charging based on:
- available power;
- rate schedules;
- required charging levels;
- vehicle priority;
- solar self-consumption;
- load shedding constraints;
- billing requirements by user or department.
The building is then able to balance comfort, energy, charging, and pricing constraints.
Useful Automation Scenarios
Scenarios should be simple, testable, and reversible. The goal is not to make the building unpredictable, but to automate repetitive decisions.
Examples of relevant scenarios:
- HVAC standby mode when the space is unoccupied;
- lights turned off after closing;
- gradual startup in the morning;
- temporary load shedding during peak hours;
- Lowering setpoints in areas with low occupancy;
- Increased ventilation if CO2 levels are high;
- Alert if heating and air conditioning are running simultaneously;
- Automatic CMMS ticket in case of a recurring fault;
- Comparison of energy consumption between similar buildings;
- Dynamic limitation of EV charging stations.
Note: Point to Watch A scenario must always define its exit conditions: return to normal, timeout, manual override, failure alert, and logging of the decision.
Maintenance: Moving from Reactive to Data-Driven Management
Building maintenance is often broken down into separate categories: HVAC, electrical, security, plumbing, building management systems, and EV charging stations. A unified monitoring system allows maintenance tasks to be prioritized based on their actual impact.
The signals that are useful for maintenance are:
- equipment malfunction;
- temperature or pressure drift;
- abnormal consumption;
- excessive on-off cycling;
- stuck valve;
- clogged filter;
- frozen meter;
- lost communication;
- recurring alarm;
- discrepancy between setpoint and measured value.
Integration with a CMMS allows certain events to be automatically converted into tickets, including the building, equipment, alarm, recent history, and severity level. This helps teams avoid making diagnoses without sufficient information.
Integration of CMMS, EMS, ERP, and Energy Platforms
Eziwan can feed into existing tools rather than creating another silo. The collected data can be integrated into an energy management system, a CMMS, an ERP, or an analytics platform.
| Destination | Data Sent | Usage |
|---|---|---|
| EMS | consumption, IPE, baselines | energy management and ISO 50001 |
| CMMS | faults, alarms, equipment | tickets and maintenance tracking |
| ERP | costs, rebilling, sites | financial consolidation |
| Data platform | time series, events | advanced analytics and reporting |
| Eziwan dashboard | KPIs, alerts, maps | day-to-day operations |
Exports can take the form of APIs, scheduled files, webhooks, or connectors, depending on the client’s environment.
Building Connectivity Security
Building management systems (BMS) become a critical entry point as soon as they are connected. A smart building architecture must therefore incorporate cybersecurity from the very beginning.
Recommended best practices:
- Outbound VPN tunnel from the gateway;
- No direct exposure of the building management system (BMS) controllers to the Internet;
- Segmentation between the office network, BMS, security network, and EV charging stations;
- Strong authentication for administrative access;
- Connection logging;
- Filtering by protocol and address;
- Controlled updates;
- Configuration backups;
- Revocation of service provider access;
- Monitoring of connection status.
For organizations that operate multiple sites, consistency in policies is just as important as local security. A policy applied consistently reduces errors and facilitates auditing.
Example of Point Mapping
Here is a simplified example of mapping that is useful before integration.
| Item | Protocol | Unit | Frequency | Use |
|---|---|---|---|---|
| Meeting room temperature | BACnet | degrees Celsius | 5 min | comfort and IAQ |
| Meeting room CO2 | Modbus RTU | ppm | 1 min | demand-based ventilation |
| Main meter | M-Bus | kWh | 15 min | commercial building regulations |
| Set lighting | KNX | status | event | turn off when unoccupied |
| HVAC fault | BACnet | Boolean | event | CMMS ticket |
| EV charging station power | OCPP | kW | 1 min | dynamic load shedding |
This scoping process helps avoid collecting too much unnecessary data and missing the truly critical points.
Typical Deployment with Eziwan
An IoT building connectivity project typically unfolds in several stages.
1. Technical Inventory
Identify the systems in place: building management systems (BMS), HVAC controllers, meters, lighting, indoor air quality (IAQ) systems, EV charging stations, CMMS, EMS, fire safety systems, and existing interfaces.
2. Protocol Mapping
Identify BACnet/IP, BACnet MS/TP, Modbus TCP, Modbus RTU, KNX IP, M-Bus, LonWorks, OCPP, and any necessary gateways.
3. Selection of Relevant Points
Choose the metrics that truly support operations: energy, comfort, alarms, faults, occupancy, maintenance, and compliance.
4. Installing the gateway
The Eziwan gateway is installed in the equipment cabinet or near the building management system (BMS). It collects data locally and transmits it via a secure connection.
5. Standardization and Dashboards
The points are named, converted, and categorized by building, zone, use, and criticality. Multi-site dashboards can now be compared.
6. Alerts and Scenarios
Thresholds, anomaly rules, hourly scenarios, load shedding, and CMMS tickets are being configured gradually.
7. Field Verification
Every important measurement must be validated: unit, direction, frequency, and consistency with the meter or actual equipment.
Use Cases by Building Type
| Building | Primary Need | Value of Monitoring |
|---|---|---|
| Offices | comfort, energy, occupancy | reduction of energy waste during non-occupancy |
| Retail | HVAC, lighting, schedules | consistency across multiple sites |
| Healthcare Facility | continuity, alarms, IAQ | visibility into critical equipment |
| Campus | multi-building complex | comparison and prioritization of actions |
| Logistics | energy, loading docks, EV charging | load shedding and targeted maintenance |
| Municipal | regulatory reporting | consolidation of consumption data |
| Hotel | comfort and energy costs | zone-based and occupancy-based management |
The challenge remains the same: linking technical data to the operational context.
Common Pitfalls
Several mistakes are slowing down smart building projects.
- collecting all data points without a strategy;
- forgetting about units and conversion factors;
- comparing buildings without adjusting for usage patterns;
- neglecting serial protocols such as Modbus RTU or BACnet MS/TP;
- creating a visually appealing dashboard that is unusable by operations;
- automating without providing a manual mode;
- connecting the building management system without network segmentation;
- ignoring maintenance needs;
- failing to test alarms under real-world conditions;
- neglecting to document data points and scenarios.
Effective monitoring must remain understandable to field teams. If only the integrators know how to explain it, it will become vulnerable.
How Eziwan Fits Into Your Smart Building
Eziwan acts as a connectivity and monitoring layer between the building’s technical equipment and business tools. The Eziwan gateway collects field data, the cloud platform centralizes dashboards and alerts, and connectivity solutions secure multi-site data exchanges.
This approach is particularly well-suited to heterogeneous facilities, where multiple generations of building management systems, meters, sensors, and controllers coexist. It allows for the modernization of operations without immediately replacing all existing equipment.
Conclusion
IoT connectivity for smart buildings is not just a matter of installing sensors. It is an architecture that enables interoperability between building management systems (BMS), lighting management systems (LMS), metering, indoor air quality (IAQ), electric vehicle charging, maintenance, and energy performance.
By centralizing BACnet, Modbus, KNX, M-Bus, LonWorks, and OCPP within a multi-site monitoring system, Eziwan helps facility operators detect deviations, manage scenarios, prioritize maintenance, and generate reliable data for their energy management initiatives. The building becomes easier to understand, more controllable, and more consistent across an entire portfolio of properties.
Further Reading
- Remote BMS Monitoring — Control your BMS and LMS systems from a centralized interface
- Industrial HVAC Monitoring — Monitor and optimize your HVAC systems in real time
- BACnet Cloud — upload BACnet data from your building equipment to the cloud
- Industrial Connectivity — choose the right connectivity for your multi-site buildings
- Industrial Solutions — discover our solutions tailored for commercial and industrial buildings