Integrations

Integrations: the protocols Aqueduct speaks and the systems it works with.

Aqueduct connects to devices over LoRaWAN, BACnet and Modbus, and to the systems of record you keep: CMMS and EAM for work, SCADA and historians for networks, AMI for customer meters.

Built on aQ Core
Control panel switches
Device health
ERS-CO2 · Level 2, Zone 4
Connection reliability99.2%
Battery3.61 V
Last reading1 min ago
Demo data
Command history · RTU-2
Occupied mode07:00 · executed
Economizer on07:12 · executed
Lockout active07:13 · held
Demo data

Open protocols to the equipment, systems of record kept in place.

Devices

How equipment connects

  • LoRaWAN sensors and meters

    Battery-powered devices report through LoRaWAN gateways.

  • LoRaWAN relay switches

    For simple loads such as exhaust fans and lighting circuits.

  • Field device network controller

    Speaks BACnet or Modbus to air handlers, rooftop units, chiller plants and VAV boxes, and reads their telemetry back.

Breakers and wiring in a panel
Systems

Which systems stay, and how they connect

  • CMMS and EAM

    Receive work orders with the diagnosis and recommended fix. Aqueduct does not replace them.

  • SCADA and historians

    Read alongside the network. Control stays with SCADA.

  • BMS and BAS

    Read over BACnet or Modbus, then kept or replaced; equipment commands run only where control is enabled, with owner approval.

Pipework and valves in a plant room
Replace or integrate

Replace or connect, by category.

Replaces or works with your
  • BMS and BAS
  • EMS
  • Water management systems
  • IAQ monitoring tools
Integrates with your
  • CMMS and EAM
  • IWMS and CAFM
  • SCADA
  • AMI
  • Historians

Device agnostic: make and model are chosen per site.

By the numbers

Both device protocols are open standards.

135-2024

is the current BACnet standard from ANSI and ASHRAE, published at the end of 2024 with 17 addenda to the 2020 edition.

Source: BACnet International
Y.4480

is the ITU-T recommendation that made LoRaWAN an international standard in December 2021.

Source: LoRa Alliance

Limits

Aqueduct does not replace a CMMS, SCADA or historian. Devices that send no telemetry, such as analog meters without a pulse output, need a retrofit or replacement. Each CMMS connection is scoped with the project.

Trusted at scale
Read the case studies
Deployed275+

sites in 21 countries run on Aqueduct.

Healthcare22 hospitals

and 9 clinics in one of India’s top hospital chains.

AirportsA top 25

US airport running water intelligence on Aqueduct.

Real estate20M+ sq ft

of commercial real estate under Aqueduct.

Manufacturing300 acres

FMCG manufacturing campus.

Food and dairyMajor dairy

operations run on Aqueduct.

Questions

Common questions

Yes. Aqueduct connects to BMS and BAS controllers using the two open building protocols, BACnet and Modbus, via a gateway on site. You can keep the BMS running its sequences or move functions to Aqueduct over time. See keeping your BMS.

Aqueduct connects to the CMMS or EAM you already run, scoped per project. Work orders arrive with the diagnosis, the affected component and the recommended fix, so technicians do not retype alarms. See fault detection and diagnostics.

Yes, if they send telemetry. Smart meters connect over LoRaWAN, Modbus or BACnet, and older meters with a pulse output can be read through a pulse counter. See pulse counters.

No. Valves and pumps remain under the utility's own SCADA. Aqueduct takes a read-only copy of SCADA, AMI and historian data and adds district balances, loss analysis and reporting on top. See utilities.

See Aqueduct on your own facility.

Bring a site, a utility bill or a question. We will show you where the loss is.