Building Operating Systems: smart control centres for efficient buildings

A modern building can have thousands of data points. Heating and ventilation systems report their operating status, sensors measure temperature and indoor air quality, access control systems record events, and energy meters continuously provide consumption readings. Often, the problem is not a lack of data. It is that the data sits in different systems, uses inconsistent terminology and cannot readily be analysed together. This is where the Building Operating System concept comes in.

The term BOS does not describe a formally standardised system architecture. It refers to a software and integration layer that connects different technical and digital building systems. It can bring together data from heating, ventilation and air conditioning (HVAC), lighting, security systems, IoT sensors, energy management and other applications, making it available to other systems. A BOS generally builds on existing building automation rather than replacing it, connecting it with further layers of data and applications.

The main difference from conventional building management or building automation systems is this focus on integration. While those systems traditionally monitor and control specific technical installations, a BOS aims to bring together data from multiple disciplines and applications across system boundaries. Open application programming interfaces, shared data models and standardised protocols are central to this approach. It does not, however, eliminate all isolated systems. Existing buildings still contain different generations of equipment, proprietary systems and communication protocols. A BOS therefore first provides a translation layer that enables these systems to communicate, where suitable interfaces exist.

Combining a BOS with Building Information Modelling (BIM) creates a useful link between static and dynamic building data. A BIM model can describe geometry, rooms, systems and building components, for example. The BOS adds current operating data from sensors and technical systems. This allows operators to associate a technical event with a room, a system or a component, rather than viewing it simply as a measurement.

BIM is by no means limited to design and construction. What matters is which information from the model is carried forward into operation and kept up to date. A BOS can connect this information about existing buildings and assets with ongoing operational data.

What makes up a Building Operating System?

There is no universal list of components. However, several layers recur in typical BOS architectures:

APIs (Application Programming Interfaces) and connectors play a central role, enabling data to flow in both directions between connected systems and external applications. A data layer then standardises information from different sources and places it in a shared context. Dashboards and user interfaces present this data to facility managers, technicians and other users. Role and permission management determines who can view information and who can control devices or processes.

Depending on the architecture, processing takes place locally in the building, in the cloud or across both. Time-critical or particularly sensitive functions can run on edge systems on site, for example, while larger datasets for portfolio analysis or AI applications are processed in cloud environments.

Modern platforms demonstrate how far this approach can go. APIs can read sensor values and, in some cases, send commands to actuators, such as changing system setpoints or operating valves. This architecture enables large volumes of data to be collected and analysed efficiently, then used in automated or partially automated processes. Machine learning can help identify patterns and unusual operating conditions. The control logic itself must, however, be tailored to the specific use case and technical system.

Optimising facility management

A BOS has a wide range of applications that extend beyond traditional building automation. In facility management, it offers ways to connect information that was previously kept separate. For space utilisation, room and building data can be combined with current occupancy information, for example. This shows which office spaces are actually used and when rooms regularly stand empty. Such data can support space planning for flexible workplaces and desk sharing.

A BOS makes it possible to analyse energy consumption in detail and adapt control processes more closely to actual use. Lighting, heating and air conditioning can be adjusted automatically using data on the building structure, usage patterns and environmental conditions. Sensors can measure temperature, air quality and daylight levels, for example, and supply that information to building automation systems or higher-level optimisation functions.

The current EU buildings directive makes BOS more relevant

The current EU buildings directive shows the growing regulatory importance of these functions. Among other requirements, building automation and control systems must continuously monitor and analyse energy consumption, detect losses in efficiency and communicate with technical systems from different manufacturers. Since May 2026, indoor environmental quality monitoring has also been among the specified functions.

Integrating IoT sensors allows technical systems to be monitored continuously for unusual conditions. Changes in power consumption, temperature, pressure or vibration can indicate a need for maintenance. This supports condition-based maintenance and, where data models are sufficiently robust, predictive maintenance strategies.

Security and access control systems can also be connected to a higher-level platform. Alarm messages, access events or defined security states can then be combined with other building data. As these security-relevant systems become more interconnected, access controls, network segmentation and cybersecurity become increasingly important.

From individual systems to a shared data layer

The real value of a BOS therefore lies less in adding another dashboard than in creating a shared data layer. A temperature reading becomes more useful when its room and device of origin are known, along with the system serving that room and the conditions of use. This is where BOS, BIM and digital twins come together. BIM can supply the building structure and properties, while building automation provides dynamic operating data. An integration platform connects these sources and makes the information available to applications.

Current smart building platforms take this approach too. For Building X, for example, Siemens describes open APIs that make building, energy, device and operational data available to other applications. Third-party applications therefore do not need to connect to each technical subsystem separately.

From potential to practice - putting Building Operating Systems to the test

Introducing BOS technology can be an important part of digitalising real estate and facility management. It is not an end in itself, however. What matters is which operational problems it is intended to solve.

Not every building needs the same depth of integration. A well-designed building automation system may be sufficient for a small property. In complex office buildings, hospitals, airports or larger portfolios, an overarching data and integration layer becomes more valuable because many more systems and user groups interact. A BOS also offers greater flexibility when integrating new technology. Conventional building automation systems are often tailored to particular equipment and protocols. A BOS can make it easier to connect new IoT devices, software or energy management systems, provided open, documented interfaces are available.

Interoperability is also becoming more important in policy. The EU buildings directive explicitly requires building automation systems to communicate with connected technical systems and work together across different proprietary technologies, devices and manufacturers. As with BIM, implementation presents several challenges. The main difficulty remains the lack of interoperability and standardisation: building services often comprise numerous systems and sensors from different manufacturers, using different communication protocols and data formats.

Another issue is often underestimated: data must be clearly described as well as technically accessible. A system needs to understand whether a data point represents room temperature, a valve state or the power consumption of a particular installation, for example. Semantic data models and shared terminology are therefore important elements of interoperable smart buildings.

A gateway for cyberattacks

Data sovereignty and cybersecurity are further requirements. The more systems exchange data in both directions, and the more closely IT and operational building technology converge, the larger the potential attack surface becomes. Role and permission management, secure interfaces, patch management and clear data governance must therefore be part of the system architecture from the outset.

Implementing a BOS also requires investment and organisational preparation. Operators need to determine which data they actually need, which systems serve as the authoritative sources, who maintains the information and which processes should be automated. Without that preparation, a supposedly central platform can become just another system in an already complex IT environment.

A BOS is therefore not automatically a building's "smart control centre". With the right planning, however, it can connect building automation, BIM, IoT and facility management applications. Its value emerges when previously separate data supports practical operational processes: optimising energy use, detecting faults earlier, making better use of space and sharing information across system boundaries.