01 · Understand the lock-in
Map proprietary dependencies, support risks, cost and operational pain.
Open-protocol refits
Move beyond vendor lock-in. Keep what still works.
Modernise ageing controls and applications in stages, connect open-protocol controllers from different manufacturers, and regain control of how your building evolves.
The problem
A working building can still be trapped by its controls.
Many estates rely on proprietary supervisors, controllers and applications that are expensive to maintain, difficult to extend and dependent on one vendor’s timescale.
A full rip-and-replace is disruptive and often wasteful. An open-protocol strategy creates another route: replace constraints progressively while preserving viable plant and investment.
A staged route
Modernise around operational priorities—not an arbitrary replacement programme.
02 · Create the open layer
Use iviva to connect existing systems alongside open protocols and APIs.
03 · Replace progressively
Prioritise obsolete or costly controls during planned works and equipment lifecycles.
04 · Standardise & extend
Build reusable equipment models, dashboards and workflows across the estate.
What openness means
Choice at the controller, integration and application layers.
iviva’s integration layer can communicate across common building protocols and publish data to other approved systems. That means future changes do not have to begin from zero.
BACnetModbusOPCKNXSNMPLonWorksoBIXNiagaraMQTTREST APIsOpen SDK
Protocol support alone does not guarantee interoperability. Omnee360 assesses the available points, data quality, control permissions and equipment behaviour as part of discovery.
Why refit this way
Reduce dependency without increasing operational risk.
- Avoid discarding serviceable plant simply because its control layer is dated
- Create competitive choice for future equipment and integration work
- Plan changes around lease events, refurbishments and asset lifecycle
- Keep existing BMS supervisors operating during transition where appropriate
- Introduce portfolio standards across buildings with different underlying brands
- Retain the option of cloud or on-premise deployment
Start with the part of your estate that costs you most.
We can map proprietary dependencies and identify a low-risk first phase towards open controls.