The smart buildings industry did something genuinely impressive over the last decade. Faced with fragmented supply chains, overlapping scopes, and technologies falling between trades, it created a delivery construct that mostly worked. The Master Systems Integrator brought clarity to capital projects. It defined accountability, reduced chaos, and made it possible to deliver increasingly complex smart buildings without relying on heroics.
But then, we kinda just left it there.
The MSI, by design, is a delivery mechanism. It exists to get a project over the line. At handover, it steps back. Soft landings may extend its influence for a short while, but eventually the project team disappears and the building is left to operate for the next twenty or thirty years. That is where the industry has been remarkably casual.
Operations carry the majority of smart building value. Energy performance, occupant experience, resilience, data reuse, regulatory reporting, optimisation. None of these are capital outcomes. They are operational ones. Yet there is no equivalent operating model to MSI. No clear owner of the live integration layer. No role accountable for the performance of the smart building once the ribbon is cut.
Instead, responsibility fragments. IT owns the network but not the systems. FM owns the systems but not the data. Asset management wants outcomes rather than another vendor relationship. Vendors maintain their own platforms, optimised for warranty, not performance. Everyone is involved. No one is accountable.
This is not a technology problem. The tools are largely good enough. The problem is structural.
Buildings change continuously after handover. Tenants move. Space is reconfigured. Systems are upgraded piecemeal. Cyber requirements evolve. Sustainability targets tighten. Data expectations expand. Every one of these changes stresses the original integration architecture, yet no one is explicitly responsible for maintaining coherence over time.
What’s missing is an operational equivalent of MSI. Something with a clearly defined function with a long-term mandate. Someone who owns the integration layer in life, not just at birth. Someone accountable for the digital performance of the asset, not merely its availability.
This role would not “run” the building in a traditional sense. It would curate it. Maintaining the data model. Managing change. Translating operational pain into technical priorities. Deciding when to integrate, when to simplify, and when to remove systems that no longer earn their keep. Crucially, it would be judged on outcomes. Energy performance. Reliability. Adaptability. Value retention.
The absence of this role explains much of the industry’s frustration. Smart buildings that slowly lose capability. Platforms that become brittle. Data lakes that turn into data swamps. Innovations that looked compelling at handover but quietly atrophy over time. These are not failures of intent. They are failures of ownership.
The industry has spent years perfecting how to deliver smart buildings. Far less effort has gone into designing how they should be operated as digital assets. That imbalance is now the limiting factor.
The next phase of smart buildings will not be defined by smarter technology. It will be defined by operational clarity. By explicit decisions about who owns integration in life, beyond capital projects. Until operations are designed with the same rigour as delivery, we will continue to install intelligence into organisations that are structurally unable to sustain it.
In Dr Marson’s monthly column, he’ll be chronicling his thoughts and opinions on the latest developments, trends, and challenges in the Smart Buildings industry and the wider world of construction. Whether you’re a seasoned pro or just starting out, you’re sure to find something of interest here.