BMS-grade outcomes without a multi-year BMS project.
AmbiAutomation gives commercial and institutional buildings the supervisory outcomes of a BMS — centralised control, scheduling, zone-level visibility, alarms, energy reporting — focused on the highest-impact subsystem first: the existing VRV / VRF HVAC fleet. The on-site server integrates over BACnet IP and MODBUS RTU; the supervisory application is the operator interface.
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.
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. For deployments that require controller-level authenticated identity — government buildings, healthcare facilities, regulated industrial sites — Ambimat's hardware-rooted device identity platform is the in-group reference for that trust layer.
- 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
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.
Common questions.
How is AmbiAutomation different from a full BMS project?
A traditional BMS is a multi-year engineering programme with new controllers, panels, and cabling — often replacing the existing HVAC control layer. AmbiAutomation is a retrofit: it speaks BACnet IP or MODBUS RTU to whatever is already installed, delivering BMS-grade centralised control and reporting without ripping out equipment or shutting down operations.
Do I need to shut down operations during installation?
No. The HVAC system continues to operate throughout the retrofit. Commissioning of 30–80 indoor units typically takes 5–10 working days depending on building access and OEM gateway availability.
Can AmbiAutomation coexist with an existing BMS?
Yes. AmbiAutomation exposes a north-side API (BACnet IP or REST) that a parent BMS can consume, and it consumes south-side data from HVAC. For sites with a BMS that covers non-HVAC (lighting, access), AmbiAutomation runs alongside as the HVAC automation layer.
What outcomes should I expect compared to a traditional BMS?
Comparable centralised control, scheduling, alarms, and reporting — at a fraction of the cost and installation time. Where a full BMS may take 12–24 months and 3–8× the capex, AmbiAutomation is typically live in weeks.