Wired & Wireless Networks

If sensors are the building's senses and actuators its muscles, the network is its nervous system's wiring - the paths every signal travels. It sits directly above the devices in the smart-building stack and below the BMS, the platform and the twin, and everything above depends on it. A twin can only be as live as the network feeding it.

Three properties describe any network link, and you will weigh them constantly. Bandwidth is how much data it can carry per second - a security camera needs megabits, a temperature sensor needs a few bytes a minute. Latency is the delay before data arrives - irrelevant for a daily energy total, critical for a safety interlock or a control loop. Reliability is how often it actually delivers - a link that works 99 percent of the time drops one reading in a hundred, which may be fine for trends and fatal for alarms.

Buildings are unusual networks because they mix wildly different traffic on the same infrastructure: chatty video and voice, bursty human devices, and thousands of tiny, slow, patient sensor messages. A good design does not force them all down one pipe; it matches each kind of traffic to a suitable path, and keeps the critical operational traffic separate from the general office network.

One more property matters for control: determinism - the promise that a message will arrive within a bounded time, not merely on average. A dashboard tolerates jitter; a control loop or an interlock does not. And unlike an office network refreshed every few years, a building network is expected to run for decades, so it must be documented, labelled and generous enough to absorb sensors nobody has thought of yet. Designing for that longevity and headroom is as important as raw speed.

The wired backbone of almost every commercial building is structured cabling - a disciplined, standardised way of running cable so it is documented, testable and future-proof rather than an ad-hoc rat's nest. Copper twisted-pair (Cat6, Cat6A) runs from equipment to a floor communications closet, the IDF (intermediate distribution frame); IDFs link back over fibre to a central MDF (main distribution frame). Copper Ethernet runs are limited to roughly 90-100 metres - a hard physical constraint that shapes where closets must sit, which is why architects should reserve riser and closet space early.

On top of this runs Ethernet, the dominant wired protocol, moving data as packets through switches that direct traffic. The feature that transformed smart buildings is Power over Ethernet (PoE) - the standards 802.3af, 802.3at (PoE+) and 802.3bt (PoE++) let one cable carry both data and power, up to around 90 watts at the source with bt. A single cable now feeds a Wi-Fi access point, an IP camera, a door controller, an occupancy sensor or even a light fitting - no separate electrician run, no local power supply. PoE quietly made dense, cabled sensing affordable, and it is why so much building IoT now lives on the IT network.

Structured cabling is also a discipline of testability. Every run terminates on a labelled patch panel, is certified against its category (Cat6A supports 10 Gbps to ~100 m), and is recorded so a fault can be traced rather than hunted. Higher-wattage PoE++ also carries a real power budget: a switch has only so many watts to share, so a floor full of PoE lights, cameras and access points must be planned so the switch and its power supply are not overrun. These are unglamorous details, but they are exactly what separates a backbone that quietly works for twenty years from one that becomes an intermittent, undocumented nightmare.

Not everything can - or should - be wired. Retrofits, movable furniture, battery sensors and hard-to-reach points call for wireless, and buildings use two broad families for very different jobs.

Wi-Fi (802.11) is the high-bandwidth workhorse for human-facing devices - laptops, phones, tablets, room panels, cameras - and for gateways that aggregate other traffic. It is fast but relatively power-hungry, so it is a poor fit for a coin-cell sensor meant to last years. For those you drop to low-power wireless: sub-GHz radios and mesh protocols like Zigbee, Z-Wave, Thread and Bluetooth Low Energy, plus long-range LoRaWAN (Lesson 2.3). Lower frequencies penetrate walls and floors better and reach further for the same power, which is exactly what a distributed set of battery sensors needs.

Wireless buys flexibility but costs you control. Radio is a shared, invisible medium: it suffers interference (other networks, microwaves, dense concrete and steel), congestion as device counts climb, and security exposure because the signal does not stop at the wall. The honest rule of thumb: wire what is fixed, powered and critical; go wireless for what is mobile, battery-powered or a retrofit - and design the wireless deliberately, with a site survey, not by hope.

Topology is the shape of the connections, and it drives both reliability and cost. In a star, every device connects back to a central switch or hub - simple, easy to manage, and the standard for Ethernet - but the centre is a single point of failure and every device needs its own run. In a bus (the classic shape of older field buses like BACnet MS/TP and Modbus), devices share one common line, which is cheap in cable but means one break or one noisy device can disturb everyone.

A mesh is the shape most low-power wireless prefers: devices relay for each other, so messages hop node-to-node to reach a gateway. Mesh is self-healing - if one node drops, traffic reroutes - which makes it resilient and easy to extend, at the cost of more complexity and some latency per hop. A ring passes data around a loop and is used in resilient industrial backbones because it can survive a single break.

Real buildings are hybrids: a fibre-and-copper star Ethernet backbone; field buses in a line to plant; a wireless mesh of sensors hanging off gateways. The skill is reading which shape is used where, and why - and spotting the fragile single points of failure that a resilient design should have engineered out.

There is no perfect network, only a deliberate balance of bandwidth, reliability and cost for each job. A safety-critical control link should be wired, redundant and low-latency even if it is expensive. A field of ambient sensors can ride a cheap, lossy mesh because an occasional dropped reading barely dents a trend. Spending camera-grade bandwidth on a thermostat, or trusting a life-safety interlock to flaky Wi-Fi, are both engineering errors - one wasteful, one dangerous.

The other discipline is segmentation. Building operational technology (OT) - controllers, meters, actuators - should live on its own logical network, separated from the general office (IT) network using VLANs and firewalls. This is partly performance (keep bursty office traffic off control links) and heavily security: a connected building is an attack surface, and you do not want a compromised laptop able to reach a chiller. Treat network security and any life-safety wiring as work for qualified specialists and formal sign-off, not a DIY afterthought.

For a twin, the practical takeaway is blunt: your data is only as good, timely and trustworthy as the network beneath it. Before you promise live insight, look down the stack and ask whether the backbone can actually deliver it.