The open layer for the buildings you already run.
CMS Buildings sits alongside your BMS and the proprietary systems already running your portfolio — connecting to them, not replacing them. Your team gets a governed, familiar interface for day-to-day operations, while an AI-native layer underneath keeps adding capability as your portfolio changes. Governed and tested at every step.
Your BMS isn't closed. It's open one system at a time.
Most building management systems speak BACnet or Modbus, and the modern ones ship an API. That openness is real — and it stops at the point level. You can read AHU-2's supply-air temperature; you can't ask a portfolio-wide question, because every vendor models its points differently, every site names them differently, and every governed change still routes back through the vendor's engineering tool and their integrator. So integration stays project-shaped, and teams paper over the gaps with spreadsheets and one-off scripts no one governs.
- Open at the wire, proprietary above it — points and values, not portfolio semantics
- Open per system, not across them: each vendor's model, version, and license
- Reads are easy; governed change still goes through the vendor's tooling
- No shared record of who changed what and why, across every system
An industry-wide problem, not a one-off.
- ~40%
- Of global energy use runs through buildings
- Dozens
- Of siloed, vendor-specific systems in a typical portfolio
- Months
- To integrate a new building system with the BMS
- Little to none
- AI-native extensibility in incumbent BMS platforms
Sources: independent industry research on building operations and facilities management.
Connect, operate, and extend — on one open platform.
Connect without replacing
CMS Buildings speaks BACnet, Modbus, OPC UA, SCADA, and MQTT out of the box, so it sits alongside your BMS and proprietary systems instead of ripping them out.
Operate the full lifecycle
Commissioning to decommissioning: guided intake, asset tagging, tracking, transfers, reconciliation, and work-order management — every change attributable and auditable.
Extend with AI
Powered by OpenX: Azi and any MCP-native AI can propose new dashboards, queries, and automations over your governed building data. You approve before anything goes live.
Three layers. One governed platform.
Smart buildings are converging on a three-layer shape. Discovery is being solved at the field layer, control is settled, and composition across systems is the layer still up for grabs.
Field
Thread and SRP let sensors register themselves onto the network — self-discovering deployment, no proprietary hub in the middle.
Control
BACnet, Modbus, KNX, and DALI run the systems you already own, carrying deterministic control and object semantics.
Orchestration
Governed composition across every silo — access-scoped, audit-tracked, and open to AI that proposes rather than acts. This is where CMS Buildings sits.
Everything a modern building operations team needs.
Operations
Asset intake, a guided commissioning workflow, tagging, tracking, transfers, reconciliation, and end-of-life decommissioning.
Connect
A governed integration layer over your BMS and proprietary systems — discover points and devices, control access, and extend without a rip-and-replace.
Compliance & Governance
Governance by construction, immutable audit trail, and feature-locked, access-rights-controlled dashboards for every role on your team.
AI & MCP
Azi the assistant and a governed MCP server let Claude, GPT, Copilot, or your own models operate on building data — propose, approve, act.
The audit trail your ops and compliance teams expect.
Not a checklist bolted on after the fact. Every action is attributable and timestamped, every change captures a reason, and the audit trail is immutable and append-only.
“Your stack, your way. CMS Buildings connects to anything — and extends everything.”
CMS Buildings connects to the BMS, meters, and proprietary systems you already run, then extends and enhances them — no rip-and-replace, no lock-in. And you choose how it runs.
Fully hosted & managed
We run and operate the platform end to end, so your team can focus on operations.
Self-hosted & self-managed
Deploy inside your own environment, owned and operated entirely by your team.
Internally hosted & co-developed
We build alongside your team in your environment, then hand off as far as you want.
Bring your portfolio onto one governed layer, in months.
See CMS Buildings connect to your BMS and run operations with governance your team can read.