Scope

What we automate first.

VRV / VRF HVAC (primary)

Existing multi-zone air-conditioning fleets are the core AmbiAutomation use case: centralised scheduling, setpoint policy, zone-level visibility, and alarms.

HVAC plant interfaces

Where chillers, AHUs, VAVs, FCUs, or meters expose BACnet IP or MODBUS, the on-site server brings them into the same supervisory view.

Energy visibility

HVAC run-hours, zone consumption, and meter data exposed for tenant attribution, sustainability reporting, and audit.

Existing-BMS coexistence

Where a head-end BMS is already in place, AmbiAutomation operates as an HVAC-focused sub-system, exposing data northbound over HTTPS / JSON.

Integration model

South-side protocols. North-side cleanliness.

On the equipment side, the on-site server communicates with HVAC equipment over BACnet IP and MODBUS RTU. On the operator side, it presents a secure supervisory application — never exposing field protocols to the public internet. North-side integration with existing facility-management or analytics platforms uses HTTPS / JSON with authenticated webhooks.

  • BACnet IP, MODBUS RTU, and MODBUS TCP/IP on the equipment side
  • HTTPS / JSON north-side API for analytics or BMS coexistence
  • Webhooks for alarms and audit events
  • Encrypted backhaul over Wi-Fi, Ethernet, GPRS / CAT 1, or NB-IoT
  • No inbound holes in the building's firewall
Engage AmbiAutomation

Talk to us before you scope a full BMS replacement.

Most commercial and institutional buildings get more from a focused HVAC automation deployment than from a multi-year BMS project. Send a short site brief and our engineering team will return a deployment shape and timeline within one business day.