The IoT in commercial buildings offers a way to make building systems more responsive by connecting sensors, controls, software, and potentially occupant-provided information. The opportunity is not simply to add more connected devices. Commercial properties already contain extensive building automation and control equipment; the challenge is making data from those systems accessible and useful across applications, without losing sight of comfort, energy use, privacy, and operational reliability.
What IoT could bring to commercial buildings
Internet of Things (IoT) technologies combine network connectivity, embedded computing, sensors, and software to monitor and influence the physical environment. In a building, that could mean using information about occupancy, temperature, lighting, equipment status, or user preferences to adjust services more appropriately.
For example, more detailed occupancy information could help operators provide lighting and conditioning when spaces are in use and reduce unnecessary operation when they are empty. Connected data could also support the management of shared resources, including conference rooms and flexible workspaces. The practical aim is to better align building operation with actual needs rather than relying on limited or indirect signals.
Occupant feedback could add another useful input. A request through a mobile application, for instance, may indicate that a workspace feels too warm or too cool even when a centrally located thermostat suggests otherwise. Personal comfort devices, such as chairs with heating or cooling elements, could also provide information about individual preferences. These inputs may help distinguish occupantsâ needs from what a conventional sensor can measure.
IoT in commercial buildings depends on integration
Many commercial buildings, particularly medium and large facilities, already have building management systems (BMSs), sensors, and actuators. But having many data points does not automatically make a building an integrated, data-driven system. HVAC, lighting, and other equipment may use separate networks and vendor-specific implementations, making it difficult to combine information or add new applications.
Legacy communications standards illustrate part of the problem. BACnet is used by many building control systems, but the source paper describes limitations in how systems implement it, including inconsistent vendor practices and a lack of metadata that clearly identifies what a data point represents. Without consistent descriptions, an application may struggle to interpret readings from different equipment or deploy reliably across multiple sites.
Proprietary systems can create additional barriers. Custom changes may require approved contractors and can be costly; in some cases, adding control points may affect warranties. A system that is difficult to customize or extend can restrict access to new sensor types and limit the development of applications that use data across building systems.
Building data platforms and common conventions
A more interoperable approach requires a common way to organize and access building information. The UC Berkeley work described in the paper used sMAP, an open-source framework intended to bring together metadata, time-series information, and other data in a common architecture. The framework was designed to accept information from varied sources, including building management systems, BACnet devices, thermostats, lighting systems, and weather data.
The important principle is separation between the data platform and the equipment that produces the data. When sources can be represented consistently, developers and building teams have a clearer foundation for visualization, analysis, and control applications. That can support efforts to understand system performance and improve control sequences without assuming that every building uses identical hardware.
The paper also describes OpenBAS, an open-source building automation effort aimed at small and mid-sized buildings that may not have conventional building automation systems. Together, these examples point to two related needs: practical access to building data in existing facilities and appropriate automation options for buildings with less extensive controls.
Balancing occupant benefits with energy goals
Connected building controls can be useful only if they account for the people using the space. Occupant preferences vary, and conventional inputs such as thermostat readings may not capture factors that influence comfort, including air movement, solar exposure, and activity. Systems that combine environmental measurements with occupant feedback could offer a more complete picture.
Research described in the paper explored personal comfort systems, including battery-powered chairs that provide localized heating or cooling. The longer-term concept was to use information from those devices alongside building data to inform HVAC operation. Similarly, research with ceiling fans examined how fan speed, temperature, humidity, and individual preference relate to comfort. These examples show how local, occupant-focused adjustments might complement central building controls rather than relying on one setting for everyone.
More granular occupancy information may also help avoid conditioning unoccupied areas. The potential benefit is a closer match between service delivery and use, with comfort and energy efficiency considered together. These outcomes depend on sound implementation; connectivity alone does not guarantee better control or lower energy consumption.
Privacy, security, and data quality matter
Collecting information about location, occupancy, activity, or personal preferences raises questions about security and confidentiality. Building owners and operators need to consider what information is gathered, how it is used, and whether occupants understand the exchange. The source paper notes that people may be more willing to share data when they receive a useful service in return, but acceptance should not be assumed.
Data reliability is equally important. Occupant reports can provide valuable context, but sensor readings and feedback may be incomplete or inaccurate. A building should not rely uncritically on any single input. Operators need to understand the limits of the available information before using it to make control decisions, particularly when those decisions affect comfort or building operation.
Practical implications for building teams
For engineers, integrators, and facility leaders evaluating connected-building projects, several priorities follow:
- Inventory existing systems: Identify available sensors, controls, networks, and data sources before selecting an application.
- Check interoperability: Examine how equipment represents data and whether metadata is consistent enough for systems to work together.
- Define the use case: Start with a clear operational or occupant need, such as understanding occupancy or improving comfort feedback.
- Assess data quality and governance: Determine whether information is reliable and establish how sensitive data will be handled.
- Connect controls to outcomes: Evaluate comfort and energy objectives together, rather than treating connectivity as a result in itself.
The IoTâs promise in commercial buildings rests on turning fragmented equipment data into information that people and control applications can use. Better integration could support more responsive comfort strategies, more informed operations, and reduced operation when spaces are unoccupied. But progress depends on addressing legacy-system constraints, inconsistent data conventions, privacy, and reliability. For building teams, the practical starting point is not deploying the most devices; it is identifying a meaningful need and building a dependable path from data to decisions.
Access Official Technical PDF