Smart Building IoT Integration: A Guide for IT Managers 2026
Smart building IoT integration has moved from a facilities management speciality to a core IT responsibility. As organisations deploy occupancy sensors, air quality monitors, desk booking systems, and building automation, the data and the infrastructure all land with IT. This guide covers how to approach smart building integration pragmatically – starting from what is already in place, identifying high-value additions, and connecting the data without creating a sprawling, unmanageable infrastructure project.
Quick verdict
Most organisations do not need a “smart building platform” in the enterprise sense – a complex IoT middleware that connects every sensor and system to a single dashboard. What they need is targeted sensor deployment for specific business decisions (occupancy data to right-size real estate, air quality data to support hybrid work productivity), integrated with the one or two tools staff already use. Start with the use case, not the platform.
The four domains of smart building IoT
Smart building technology covers four distinct domains, each with different data types, integration requirements, and business owners:
1. Space utilisation and occupancy
Sensors that measure whether spaces are in use: meeting rooms, desks, floors, building entry points. The primary data consumer is facilities management (space right-sizing, cleaning scheduling) and IT (desk and room booking system integration). Sensors range from simple passive infrared (PIR) motion detectors to computer vision-based people counters that distinguish individuals and direction of travel.
2. Environmental quality
CO2 monitors, temperature sensors, humidity sensors, and air quality sensors (VOC, PM2.5 particulates). The business case here is productivity: high CO2 levels are associated with cognitive performance reduction; uncomfortable temperature ranges reduce staff satisfaction scores. Data consumers are HR, facilities, and increasingly, employees via real-time displays or apps.
3. Building infrastructure and energy
Lighting control, HVAC integration, smart metering, and energy management. These systems typically belong to facilities and building management rather than IT, but increasingly share the same network infrastructure and require IT involvement for connectivity, security, and data management.
4. Access and security
Access control systems, CCTV, visitor management, and physical security. These are often managed by security or facilities teams but generate data that overlaps with IT (user provisioning for access control) and HR (time and attendance in some deployments).
Sensor technology overview
| Sensor type | What it measures | Accuracy | Privacy considerations | Typical cost |
|---|---|---|---|---|
| PIR motion | Motion in space (binary) | Medium (false positives/negatives) | Low – no image data | Low (30-80 EUR per unit) |
| People counter (infrared beam) | Entry/exit count at doors | High for counting, no occupancy detail | Low | Medium (150-400 EUR) |
| Desk sensor (ultrasonic/PIR) | Desk occupancy, activity detection | High for occupancy | Low – no image data | Medium (60-150 EUR per desk) |
| CO2 / air quality monitor | CO2 ppm, VOC, temperature, humidity | High (calibrated sensors) | None | Low-medium (80-250 EUR) |
| Computer vision camera | People count, occupancy, anonymised flow | Very high | High – requires GDPR/employee consent process | High (400-1200 EUR per unit) |
Connectivity protocols and network architecture
IoT sensors use a range of connectivity protocols, each with different IT infrastructure implications:
Wi-Fi and Ethernet
Standard Wi-Fi and Ethernet are straightforward from an IT perspective but require powering each sensor and managing devices in the enterprise network infrastructure. Suitable for sensors that require frequent data updates or higher bandwidth (cameras, real-time air quality). Requires VLAN segmentation – IoT devices should never share a network segment with corporate IT infrastructure.
PoE (Power over Ethernet)
The preferred deployment method for sensors that need reliable power (always-on occupancy monitors, room displays). PoE eliminates separate power runs and simplifies installation. Requires PoE-capable network switches at each deployment area – a meaningful infrastructure investment for a greenfield deployment.
Sub-GHz wireless (Zigbee, Z-Wave, LoRaWAN)
Low-power wireless protocols suitable for battery-powered sensors at scale. Zigbee and Z-Wave use mesh networking and require gateway hardware in each area. LoRaWAN has longer range (entire building from a single gateway) but lower bandwidth. These protocols significantly reduce installation costs for large desk sensor deployments but add gateway management overhead.
Bluetooth Low Energy (BLE)
Used in some desk and room sensors, particularly those that integrate with smartphone apps for wayfinding or desk booking. BLE range is limited (typically 10-30 metres) and requires gateway infrastructure for cloud reporting. Increasingly used in visitor flow and indoor positioning solutions.
Integration architecture: connecting building data to workplace tools
The highest-value integration for most organisations is connecting occupancy and room availability data to the tools staff already use – Microsoft 365, Google Workspace, or dedicated desk booking platforms. The integration architecture typically looks like this:
- Sensor data flows to a gateway (hardware or cloud)
- Gateway aggregates and forwards data to the sensor vendor’s cloud platform via HTTPS
- The sensor platform exposes an API (REST or MQTT) for downstream integration
- The workplace platform (Microsoft Places, Robin, Condeco, or similar) consumes the sensor API to show real-time occupancy alongside booked availability
The practical integration challenge is at step 4 – most sensor vendors have documented APIs, but the quality and coverage of pre-built integrations with workplace platforms varies significantly. Before selecting sensors, verify that they have a documented integration with your specific workplace platform, or that your platform supports custom API connections.
Data privacy and GDPR considerations
Smart building sensors that collect data about individuals require careful handling under GDPR (EU/UK) and similar frameworks. The key distinctions:
- Non-identifiable aggregate data (room occupied: yes/no; floor headcount: 42) – low GDPR risk, typically does not require explicit consent if not linkable to individuals
- Identifiable presence data (specific named desk is occupied) – requires a legitimate interest or consent basis; covered under employment data provisions in most EU jurisdictions with appropriate works council or DPIA process
- Computer vision / facial recognition – high sensitivity, requires explicit consent, DPIA mandatory, generally not advisable for standard workplace IoT
Before deploying any occupancy sensing, complete a Data Protection Impact Assessment (DPIA) with your DPO. The investment in a proper DPIA at the start prevents enforcement issues later and builds staff trust in the deployment.
Where to start: three high-value quick wins
For organisations beginning their smart building journey, these three deployments deliver measurable value with manageable complexity:
- Room occupancy sensors in meeting rooms: Connect to your existing room booking system to show real-time occupancy vs booked status. Immediately reveals booking ghost meetings and no-shows. Most room booking platforms (Robin, Condeco, Microsoft Places) support sensor integration. Sensor cost per room: 60-150 EUR.
- CO2 monitors in meeting rooms and open plan areas: Display CO2 levels on a screen or app. High CO2 is a visible, actionable signal for ventilation improvement. Engages staff in the data and builds buy-in for the broader programme. Sensor cost per location: 80-200 EUR.
- Floor-level people counting at building entry: Provides accurate occupancy data by floor without desk-level surveillance. Input to cleaning schedules, catering planning, and real estate utilisation reporting. Sensor cost per entry point: 150-400 EUR.
Bottom line
Smart building IoT integration is not a single project – it is a programme of incremental deployments, each adding data that improves a specific operational decision. Start with the use cases that have clear business value and existing platform support, deploy the minimum sensor footprint that delivers the required data, and build integration to the tools your teams already use. For a related look at occupancy data in the context of room booking, see our best room booking systems guide. For workplace technology strategy, see our hybrid office setup checklist.