At a glance
| Site | Building | Scale | What AmbiAutomation does there | Status |
|---|---|---|---|---|
| A | Large residence (owner not named) | About 23 indoor AC units | AmbiAutomation supplied for the HVAC system | Live |
| B | Ambimat's own office space | Office air-conditioning | Schedules switch the air-conditioners on and off by time of day | Live |
Why multi-unit air-conditioning needs a supervisory layer
In general, a building with many indoor air-conditioning units tends to end up with as many independent controls: a wall controller or remote per unit, each set by whoever was last in the room. Nobody sees the whole system at once, units are left running in empty rooms, and switching the building on in the morning and off at night is a manual walk-round. Replacing the HVAC equipment to fix that is rarely justified when the indoor and outdoor units still work.
AmbiAutomation is a retrofit layer for that general problem: it adds central supervisory control to the air-conditioning a building already has, without replacing indoor or outdoor units. This section describes the product category; it is not a description of either site below.
Site A: a large residence with about 23 indoor units
The first site is a large residence whose HVAC system has approximately 23 indoor air-conditioning units. AmbiAutomation has been supplied for this installation and is live today.
Site B: Ambimat's office, on a time-of-day schedule
The second deployment is in Ambimat's own office. AmbiAutomation runs schedules there that switch the air-conditioners on and off according to the time of day.
How AmbiAutomation connects to an existing system
AmbiAutomation's on-site automation server connects to the HVAC system's own controller or OEM gateway on the equipment side, over BACnet/IP, Modbus RTU or Modbus TCP, depending on what the installed system exposes. Scheduling and control logic run on the on-site server; operators use the supervisory application. A site survey confirms the interface and any gateway needed for each installed base.
Where a building already has a head-end BMS, AmbiAutomation can run as the HVAC sub-system below it; see VRV / VRF integration and BMS coexistence. Neither deployment on this page is presented as a BMS integration.
What this case study does not claim
- We do not name the residence owner, its location, the HVAC manufacturer or model, or the interface used at either site.
- We publish no energy-saving percentage, payback, ROI, commissioning date or uptime figure for these sites. Savings depend on each building's measured baseline, and none is published here.
- AmbiAutomation has other customer deployments. They are not described here until their details are documented and cleared for publication.
Is your building like one of these?
Tell us how many indoor units you have and who makes the system. We will scope a site survey.
Discuss a deployment