Water, gas, and power have always been treated as utilities. They are designed in from the first sketch, sized for capacity at peak load, and never reconsidered as optional. No architect or engineer would suggest otherwise.
Connectivity has now joined that list. A modern building cannot operate, lease, comply, or compete without it. The network carries the lighting, the climate controls, the access systems, the cameras, the sensors, and the analytics platforms that turn all of that data into a building that can manage itself. Connectivity is the fourth utility.
Most projects still treat it as an afterthought. The reason is structural. Procurement is set up to keep the layers apart, and that is where every smart building project actually begins.
The Problem Lives in the Contract
Electrical and network scopes are bid separately because owners want competitive pricing on each, because standard contract templates separate them, and because lender underwriting treats them as different cost categories. Even when both teams are at the same table on day one, the contract structure pulls them apart. This is the structural reality behind every smart building project that misses its targets.
Owners who split scopes have legitimate reasons for doing so. Competitive tension lowers cost, single-vendor dependency creates risk, and a coordinated team of specialists is sometimes preferable to one party trying to be excellent at everything. The harder question is who owns the integration plan when scopes are split, and the contract usually does not name that party.
Get that question answered before the trades are awarded, and the rest of the project gets easier. Leave it open, and every smart building decision downstream becomes a negotiation.
What Changed
Three forces moved connectivity into the utility category. Power-over-Ethernet (PoE) matured to the point where 90W per port can run lighting, motorized shades, certain HVAC controls, security cameras, access readers, sensors, and digital signage from the same cable plant. Sensor and analytics platforms turned occupancy, air quality, temperature, and asset location into measurable data the business can act on. Energy and emissions reporting became a regulated number in the markets that matter most for new construction and major retrofits.
PoE has real limits, and an honest design accounts for them. High-draw HVAC actuators still need traditional power. Distance is capped at roughly 100 meters per run before signal and power degradation become issues. Heat dissipation in dense switch closets requires planning, and code treatment varies by jurisdiction. Where PoE fits, it removes parallel systems and gives the building a single management plane the moment a device powers on. Where it does not, traditional electrical scope is still the right answer.
Three Project Types, Three Sequences
New construction is the easiest project type to get right and the most expensive to get wrong. Drawings are still on paper and decisions are reversible at low cost. This is the moment to converge information technology (IT) and operational technology (OT) planning into a single design package, with building management, energy management, lighting, climate, security, and network architecture sized together.
Tenant build-outs are the moment to converge the operational environment, reduce power consumption, and improve the occupant experience. The structure is fixed. The question is how much of the operational layer can run off the same cable plant the tenant is already paying for.
Retrofits are the most constrained type of project and often the most rewarding. The cabling is in place and the wireless coverage exists. The switching infrastructure is the constraint. Upgrade the switching to power modern endpoints, fill the wireless gaps, layer the security platform across IT and OT traffic, and the endpoints come last and come fastest.
Centralized Intelligence, Edge Intelligence, Or Both
There is a real architectural debate happening in this space. Centralized observability platforms give the operations team a single view across network performance, OT events, security incidents, energy use, and digital experience. Edge architectures push intelligence to the device, reduce latency, and keep safety-critical decisions running when the network does not.
The right answer depends on what the building does. A commercial office benefits from a centralized model because the use cases are scheduling, energy, and experience, none of which are millisecond-sensitive. An industrial environment with safety-critical controls needs intelligence at the edge, because a network event cannot be allowed to take a process offline. Most real buildings use both, and the design decision is where to draw the line. The conversation should start there, not at a vendor's reference diagram.
The Technology Has Outpaced the Operating Model
The hardest problem in a converged building is what happens after it opens. Who owns the OT network, who patches it, who responds to an incident at 2 in the morning, and how the IT and OT teams coordinate on a shared incident response. The technology has matured faster than the organizational model that has to run it, and most projects are still working through that gap.
This is where the value of an early integration plan becomes obvious. A building designed by an accountable team in the design phase arrives with a documented operating model, defined ownership, and a runbook for when something goes wrong. A building stitched together at commissioning has to invent those things under pressure.
Connectivity is no longer a feature. It is infrastructure. Recognize that, name an integration owner before the trades are awarded, and you have a building design and implementation plan that actually works.
