The Vendor Who Installed Your BMS Ten Years Ago Now Owns Your Building

Ten years ago, a building management system felt like a modernisation win: one screen, one interface, chillers and AHUs and lighting all talking to each other. What nobody flagged at the time was the protocol underneath — a proprietary, closed communication standard that only the installing vendor's software could speak.

Today, that building owner discovers the trap only when they try to leave it: the vendor is the sole source for AMC pricing, the sole source for expansion, and effectively the sole source for the building's continued ability to control its own HVAC. This is the ELV islands problem, except worse — because a BMS isn't one island, it's the control layer meant to unify all the others.

How lock-in actually happens

• Proprietary protocol at the controller level — the field controllers on chillers, AHUs and VAV boxes speak a manufacturer-specific language, not an open standard, so no other integrator's software can read or write to them
• Closed engineering tools — even where the protocol is nominally open, the programming/configuration software required to actually change a sequence of operations is licensed and sold only by the original vendor
• Undocumented sequences — the control logic (what triggers what, in what order) lives in the vendor's project files, not in a specification the building owner holds independently
• Single point of technical knowledge — after a decade, the people who understand the specific installation are the vendor's staff, not the building's facility team

None of this is usually deliberate sabotage. It's the accumulated result of choosing the lowest-friction option at each individual purchase — the same install-by-install fragmentation described in the ELV integration article, just with higher stakes because a BMS touches every energy-consuming system in the building.

What it costs, concretely

Symptom	Real-world cost
Single-source AMC	No competitive tender possible — pricing power sits entirely with the incumbent, and renewal quotes reflect it
Expansion premium	Adding a new chiller or a new wing requires the same vendor's hardware at whatever margin they choose to set
Frozen optimisation	Energy-saving sequence changes (setback schedules, demand-controlled ventilation) require vendor engagement for even minor edits — most owners simply stop trying
Obsolescence risk	If the vendor discontinues the product line or exits the market, the building's control layer has no independent support path
No real-time cost visibility	Sub-metering and analytics remain locked inside the vendor's software, making energy audits and lifecycle cost management harder than they should be

Buying your way out: open-protocol procurement rules

For any BMS purchase — new building or a controls refresh in an existing one:

1. Specify open protocols at the field level, not just the head-end: BACnet or an equivalent open standard down to the controller, not merely at the supervisory software layer
2. Own the engineering license, or require it to transfer to the building owner on project completion — not remain the vendor's proprietary tool
3. Demand the sequence-of-operations documentation as a contractual deliverable, in plain-language form the facility team can actually read, not buried in vendor project files
4. Require the point list and controller configuration as a delivered document, so a third-party integrator can pick up maintenance without starting from zero
5. Tender the AMC separately from the installation wherever the protocol allows it — a genuinely open system can be maintained by any qualified integrator, which is the entire point

The migration path for buildings already trapped

Full BMS replacement is expensive and disruptive — usually not the first move. A more realistic sequence:

• Audit what's actually proprietary — often only the field-controller layer is genuinely closed; the network and supervisory layers may already support open integration with the right gateway hardware
• Gateway rather than replace — protocol translation gateways can expose a closed system's data to an open platform without ripping out working field devices
• Re-document as you touch each system — every AHU or chiller replacement is an opportunity to install open-protocol controllers and permanently shrink the locked-in footprint
• Negotiate from documented leverage — even partial independence (an open supervisory layer, a documented point list) materially improves the next AMC renewal negotiation

The building that starts this process today isn't free of its incumbent vendor next quarter — but it stops the lock-in from getting worse with every future purchase, which is the actual battle.

FAQs

What does "open protocol" mean for a BMS?

A communication standard (commonly BACnet, and sometimes others) that any qualified vendor's controllers and software can read and write, rather than a proprietary language only the original installer's tools understand.

Can we force our BMS vendor to open up an existing closed system?

Rarely without a contractual lever — which is why documentation and licensing terms belong in the original purchase contract. For an already-closed system, gateways and phased replacement are the realistic path.

Is a fully open BMS more expensive upfront?

Sometimes marginally, at initial purchase — but the lifecycle cost (AMC competition, expansion flexibility, avoided obsolescence risk) almost always favours open protocols once you look past year one.

Can you audit our current BMS for lock-in risk?

Yes — we assess protocol openness, documentation completeness, and migration options for existing systems. Request an audit.