BMS Connectivity

We speak BACnet, Modbus, and most proprietary protocols your BMS already uses.

No middleware appliance. No IT change request. Direct API or BACnet/IP connection to your existing BMS.

Connect a Building Security model
Supported connection types
BACnet/IP (ASHRAE 135) Primary
REST API (vendor-specific) Primary
Modbus TCP/IP Supported
OPC-UA (gateway) Enterprise
Connector Library

Eight pre-built connectors. Any ASHRAE 135-compliant BMS works out of the box.

Honeywell Forge / EBI
BACnet/IP + Honeywell REST API
Setup time: under 2 hours
Zone temps Setpoints Occupancy AHU status
Siemens Desigo CC
BACnet/IP native
Setup time: under 2 hours
Zone temps Setpoints VAV positions Occupancy
JCI Metasys
JACE/N4 BACnet bridge
Setup time: 2–4 hours
Zone temps Setpoints Occupancy Historical logs
Trane Tracer SC+
BACnet/IP
Setup time: under 2 hours
Zone temps Setpoints AHU supply/return
Niagara N4 / Workbench
BACnet/IP + REST
Setup time: 1–2 hours
Zone temps Setpoints Occupancy Event logs
Schneider EcoStruxure
REST API
Setup time: 2–4 hours
Zone temps Setpoints Occupancy
Automated Logic WebCTRL
BACnet/IP
Setup time: under 2 hours
Zone temps Setpoints VAV positions
Generic BACnet/IP
ASHRAE 135 compliant
Setup time: varies
Any BMS with standard BACnet/IP support. If it implements ASHRAE 135, Celaxis can connect. Contact us with your BMS brand and version.
Data Access

What Celaxis reads — and what it sources independently.

From your BMS (read-only)
Zone air temperature (all active zones)
Cooling and heating setpoints, current and scheduled
Occupancy sensor state (PIR, CO2, or presence bit)
AHU supply and return temperature
VAV damper position logs
Historical setpoint event log (last 30 days)
Sourced independently by Celaxis
Weather forecast — NOAA API, 48h hourly
Utility tariff schedule — uploaded or API from PGE, Pacific Power, NV Energy
Building calendar occupancy — Exchange or Google Cal, optional
Historical degree-day data for weather normalization
Security Model

Read-only by default. Write-only within approved setpoint bounds.

Celaxis uses a credentials pattern with minimum-necessary permissions. BACnet connections use a dedicated operator device instance with read permissions on zone data and write permissions limited to setpoint objects within declared min/max bounds.

REST API connections use a service account token scoped to BMS data endpoints only. Your IT/OT team reviews and approves the permissions before Day 15 control begins.

Full security documentation
1
No admin credentials
Celaxis never requires BMS admin-level access. Operator-level read/write is sufficient.
2
Outbound-only connectivity
Celaxis connects outbound from your BMS network. No inbound ports opened, no VPN required.
3
Setpoint bounds enforced at API level
Write permissions are capped at the min/max setpoint bounds your team approves. The API will reject any command outside these bounds.
Custom Integration

Don't see your BMS?

We've connected to 14 different BMS platforms. If yours isn't listed, tell us the brand and version — we'll let you know the connection path within 24 hours. If a Niagara N4 gateway is required, we'll tell you that too; we don't hide the complexity.

Previously connected BMS platforms
Siemens Apogee TAC Vista Andover Continuum Delta Controls ORCAview Invensys EcoStruxure KMC Commander

If it speaks BACnet, we can almost certainly connect to it. Proprietary-only systems may require a Niagara N4 gateway — we'll tell you if that's the case.