
A smart building office: the network under the sensors
A smart building starts with the installer and the landlord, and then lands with IT: hundreds of sensors, controllers, readers and screens that all want a place on the network. Whatever is not agreed at that point becomes a hole in your security or a fault nobody owns. This is what the IT side has to settle.
To IT, a smart building is mostly a network full of devices IT did not choose: sensors, controllers, access readers and screens.
Give each building system its own segment, and let the installer in remotely only through one controlled route.
Heating, ventilation, electrics and the building management system belong to the installer; we do the network underneath and the link to office IT.
What a smart building means in an office
In an office, a smart building rarely means a futuristic tower. It is a set of systems that talk to each other and to the network: the building management system for heating and ventilation, occupancy and CO2 sensors, lighting that responds to presence, access control, energy meters, screens outside meeting rooms and a desk booking system. That last part, around the person at the desk, is often called the smart office.
What they have in common is that they were chosen by the landlord, the facilities manager or the installer, not by IT. They still end up on the network. That is where the IT work starts, and that is what this article is about: not which sensor to buy, but what has to be right underneath the sensors.
The benefit of a smart building lies in better use of space and energy. It disappears as soon as the data cannot be trusted, or a thermostat becomes the way into the rest of the network.
Building, tenant and installer: who owns what
In a multi-tenant building the split is often this: the landlord owns the building management system and the installations, the tenant owns its own network and workstations, and the installer maintains the plant on the landlord’s behalf. A sensor in your meeting room may therefore belong to someone else and talk over your network, or over a separate network that runs through your ceiling.
- Record for each system who owns it, who maintains it, which network it uses and who receives the data.
- Agree whether the landlord’s systems may use your network. If so, in a segment of their own and with an agreement on who reports faults; if not, the landlord provides a separate connection.
- Put it in the lease or service contracts, not in an email at handover. When you move or the installer changes, that email is gone.
The network underneath a smart building
Building systems use a mix of connections. BACnet over IP is common for building management. Sensors often talk wirelessly to a gateway, over LoRaWAN, Zigbee or a manufacturer’s own protocol, and the gateway sits on the wired network. Access readers, cameras, screens and sometimes lighting take their power from the switch over PoE.
- Count the PoE budget. A switch sized for laptops and phones runs short as soon as cameras, readers and lighting are added.
- Cable what is fixed, wireless for what moves. Sensors on Wi-Fi get their own network name and measured coverage.
- Gateways are network devices. They get a fixed address, a place in the asset register and updates, just like a switch.
- Ask what happens when the network is down. Access control and climate should keep working locally. The installer knows whether they do; ask for it in writing.
Every building system in its own segment
The rule is the same as for printers and phones, only stricter: every building system in its own segment, behind a firewall that lets through only the traffic it needs. How to set up that layout is covered in our article what is a VLAN.
- Building management, access control, cameras and sensors each separate. Never on the guest network and never in the workstation segment.
- Outbound only where needed. A sensor reporting to its manufacturer’s cloud platform needs one destination, not the whole internet.
- Default passwords changed at installation, and a list of what is connected. A device nobody knows about never gets an update.
Building equipment often runs for years without updates. On a flat network, such a device is a stepping stone to your finance system; in its own segment, it is a device that only talks to its own gateway.
Remote maintenance by the installer
The biggest risk rarely sits in the sensor itself, but in how the installer reaches it. A mobile router of their own in the plant room, or remote access that is always open, is a door next to your firewall that nobody watches.
- One controlled route for remote maintenance, with named accounts and multi-factor authentication.
- Access that is open while work is being done and closed afterwards, with a log of who was in and when.
- A clause in the maintenance contract that no outbound connections of their own are installed without agreement.
Sensors, occupancy and privacy
A sensor that only counts how many people are in a room is different from a system that records who sat where. As soon as data can be traced to a person, through a badge, a booking or a Wi-Fi connection, UK GDPR applies: a purpose, a retention period and a limited circle of people who can see it.
The ICO’s guidance on monitoring workers is the place to start if a system can track the presence or behaviour of staff. Where you can, choose counting over tracking, and fix that in the configuration rather than only in a policy.
Updates and lifespan
A building lasts decades, a sensor years and a gateway sometimes less. That rhythm clashes with IT, where a device that no longer gets updates is replaced.
- Agree for each system who updates the firmware and how often, and have it included in the installer’s reporting.
- Ask at purchase how long the manufacturer will provide updates. A sensor without updates in its own segment is a risk you can carry; on a flat network it is not.
- Put building management gateways and servers in the asset register, with an end date, like any other piece of IT.
Where our work stops
What we do. We do the network underneath the smart building: data cabling, switches with enough PoE, Wi-Fi with measured coverage, segments and firewall rules, and the controlled route for remote maintenance. We keep the list of what is connected, manage what sits on the IT side and link the building to office IT where needed. More on connecting sensors and gateways is on our IoT services page.
What we do not do. We are not a building contractor and not an installer. Heating, ventilation, electrics and lighting installations belong to the installer, as does the building management system and its controls: we do not program controllers or commission installations. The building management or sensor platform belongs to a third party; we connect it and keep the network clean, but we do not decide what the system does. We run data cabling and mount equipment; building work belongs to the contractor.
Questions we get about this
The five that come up most often.
What is a smart building?
A smart building is one in which systems such as heating, lighting, access control and sensors are connected to each other and to the network, so they can respond to how the building is used and report on occupancy and energy. In an office it is usually a collection of separate systems working together over one network and sometimes one platform.
What is the difference between a smart building and a smart office?
Smart building covers the whole building, including plant such as heating, ventilation and energy. Smart office is about the user’s workspace: booking desks and meeting rooms, seeing occupancy and the technology in the meeting room. For the network it makes little difference; both bring devices that need their own segment.
Should building systems be on a separate network?
They should at least be in their own segment, separated from workstations and the guest network, behind a firewall that allows only the traffic they need. That can be on the same physical switches using VLANs, or on a separate network if the landlord manages it. A flat network where everything sees everything is the real risk.
Can the installer log in remotely to the building management system?
Yes, but through one controlled route, with named accounts, multi-factor authentication and a log, and ideally only while work is being done. A mobile router of their own or permanently open access in the plant room does not belong there. Put that agreement in the maintenance contract.
Do you install the building management system too?
No. We are not a building contractor or an installer; heating, electrics, lighting and the building management system belong to the installer. We do the network underneath: cabling, switches, Wi-Fi, segmentation, secure remote access and the link with office IT.
Further reading
What a smart building connects to.
Is your office getting smarter? Start with the network
Send us the list of systems the installer or landlord wants to connect. We will tell you which segments, ports and access are needed, and what your network is missing today.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.