AmbiAutomation supplies and deploys
AmbiAutomation runs the full lifecycle: site survey through commissioning and AMC. Customer contracts AmbiAutomation directly. Suited to single-site retrofits and pilot deployments.
For integrators & consulting engineers
Integration & deployment services.
An overview for systems integrators, MEP consulting engineers, and facility-management organisations evaluating AmbiAutomation as the HVAC-automation layer in commercial and institutional buildings — including OEM compatibility, protocol coverage, BMS coexistence, north-side API, and the full engineering-services scope.
Engagement model
One engineering organisation, end-to-end.
AmbiAutomation contracts as a single engineering organisation responsible for hardware, firmware, supervisory application, and field deployment. Integrators and consulting engineers can either resell AmbiAutomation as a complete sub-system, or co-deliver field work under a defined RACI.
AmbiAutomation as a sub-system
Integrator owns the master MEP / BMS contract. AmbiAutomation supplies on-site servers, firmware, supervisory application, and commissioning support; integrator handles field installation and customer interface.
Shared scope, defined RACI
Suited to portfolio rollouts. RACI defines who survey, design, install, commission, and AMC against. AmbiAutomation typically retains responsibility for firmware, supervisory plane, and Site Acceptance Test.
HVAC OEM compatibility
Supported HVAC OEMs and protocol surfaces.
AmbiAutomation integrates with any HVAC OEM exposing BACnet IP or MODBUS RTU — natively on the indoor / outdoor units, or via the OEM-supplied gateway. A site survey confirms protocol exposure and gateway requirements for the specific installed base.
| OEM & generation | BACnet IP | MODBUS RTU | OEM gateway | Notes |
|---|---|---|---|---|
| Daikin VRV (II / III / IV / 5) | Yes | Yes | Often required (DTA116, DCM601) | Wide deployment in Indian CRE; gateway model depends on generation. |
| Mitsubishi Electric (City Multi VRF) | Yes | Yes | Required (BAC-HD150, AE-200) | BAC-HD150 most common. AE-200 is supervisory + gateway in one. |
| Hitachi (VRF / IVX) | Yes | Yes | Required (CSNET Web / KNX-BACnet) | CSNET Web bridge typically present in larger installs. |
| LG (Multi V series) | Yes | Yes | Required (PACS4B000, ACP) | ACP Plus is supervisory + gateway; PACS4B000 is BACnet-only. |
| Toshiba (SMMS / SHRM) | Yes | Yes | Required (BMS-IFBN1280U-E) | BMS-IFBN1280U-E is the standard BACnet IP interface. |
| Samsung (DVM S / DVM S2) | Yes | Yes | Required (MIM-B17 / B19) | MIM-B19 supports BACnet IP and MODBUS TCP on newer DVM S2 lineage. |
| Chillers (any OEM) | Often native | Often native | Varies | BMS-ready chillers typically expose BACnet directly. |
| VAVs / FCUs (any OEM) | Rare | Common | Rarely needed | VAVs and FCUs are typically MODBUS RTU on RS485 trunks. |
| Energy meters | Some | Most | None | MODBUS RTU is the default for sub-metering; readings exposed northbound via the on-site server. |
OEM gateway part numbers above are reference examples and may change with OEM product revisions. Site survey deliverable includes the confirmed gateway requirement for the specific installed base.
BMS coexistence
Operate stand-alone or as a sub-system.
Where a head-end BMS is already deployed in the building, AmbiAutomation operates as an HVAC-focused sub-system below it. The on-site server exposes operational state and accepts supervisory commands over a north-side HTTPS / JSON API; alarms route via authenticated webhooks. Where no head-end BMS exists, AmbiAutomation is the supervisory layer.
- HTTPS / JSON API for state, schedules, setpoints, and alarms
- Authenticated webhooks for alarm and audit events
- Optional BACnet IP republishing of supervisory state to head-end BMS
- Time-series export for analytics platforms (CSV / JSON / scheduled webhook)
- SSO available on request for the supervisory application
North-side API surface
Documented API for analytics and BMS coexistence.
The on-site server exposes a documented north-side API. Read-side endpoints cover device inventory, zone state, schedule definitions, alarms, and historical telemetry. Write-side endpoints cover schedule push, setpoint adjustment, mode change, and acknowledgement of alarms.
- OAuth 2.0 client-credentials authentication; scoped tokens
- Idempotent write operations with operation-id headers
- Rate limiting and audit log on every authenticated call
- Read-only role for analytics integrations
- API documentation supplied under integration agreement
Engineering services
Six engineering stages, documented deliverables.
Every AmbiAutomation deployment follows the same six-stage lifecycle. Deliverables are documented and signed off at each stage. Integrators can own one or more stages under a defined RACI.
Site survey & HVAC audit
Walk the building. Inventory zones, indoor units, OEM and generation, exposed protocols, control-panel locations, network availability, and target outcomes. Deliverable: site survey report.
Control-architecture design
Zone mapping, schedule templates, setpoint policy, alarm thresholds, role-based access matrix, backhaul plan, BMS coexistence approach. Deliverable: as-designed architecture document.
Hardware & gateway sourcing
HVAC Bridge Board(s) sized to building, plus OEM-side BACnet / MODBUS gateways where required. Deliverable: bill of materials with lead times and per-line drawing references.
Field installation
Mount on-site server in HVAC control panel; wire BACnet / MODBUS; configure backhaul (Ethernet, Wi-Fi, or cellular). No HVAC downtime required. Deliverable: as-built record.
Commissioning & Site Acceptance Test
Device discovery, address mapping, schedule push, alarm test, user provisioning, walk-through of every zone. SAT against documented acceptance criteria. Deliverable: SAT sign-off.
Operations & AMC
Training handover, post-install observation period, baseline measurement, schedule tuning. Annual Maintenance Contract (AMC) covers remote diagnostics, firmware updates, on-site response, and spare-parts stocking. Deliverable: operations runbook.
Documents for procurement
What we provide to integrators and procurement teams.
Datasheet
HVAC Bridge Board datasheet — electrical, mechanical, protocol, and isolation specifications. Supplied on request.
Compliance documentation
Compliance and conformance documents applicable to the region of deployment. Confirmed per project on request.
API documentation
North-side API reference — authentication, endpoints, schemas, rate limits. Supplied under integration agreement.
Sample RFP response
Reference RFP / tender response covering technical, commercial, and lifecycle dimensions. Supplied to qualified procurement teams.
Engage AmbiAutomation
Open an integration discussion.
Whether you are scoping a single retrofit, planning a portfolio rollout, or evaluating AmbiAutomation as a sub-system to an existing BMS — our engineering team will respond within one business day.