BMS integration, CMMS integration and every protocol in between
Aqueduct integrations connect meters, sensors, building systems and business systems to one data layer. Aqueduct reads LoRaWAN, BACnet IP and MS/TP, Modbus TCP and RTU, MQTT, M-Bus, pulse outputs and REST APIs. It replaces or works with your BMS, BAS and EMS, routes tickets into your CMMS, reads SCADA, AMI and historians, and runs on AWS or on-prem.
One data layer for every meter, sensor, controller and system of record you run.
LoRaWAN, BACnet, Modbus and MQTT on the same platform
- Long-range wireless
LoRaWAN sensors and meters reach a gateway across a building or campus on battery power.
- Building equipment
A field device network controller speaks BACnet or Modbus to AHUs, RTUs, chillers and VAV boxes.
- Any backhaul
Gateways connect over Ethernet, Wi-Fi or an independent LTE link that avoids the customer network.
Your CMMS, EAM and SCADA keep their jobs
- Tickets with evidence
Findings route into your CMMS with the asset, the evidence and a recommended fix.
- Closures read back
Closed work orders are read back and the result is verified in the data.
- SCADA alongside
Network data from SCADA, AMI and historians is read, while control stays with SCADA.
Approved commands out, confirmed results back
- Owner approved
Commands go out only where control is enabled and the owner has approved it.
- Shadow confirmed
Each device reports its state back, so the platform knows the command took effect.
- Logged every time
The command log records every command and whether it executed on the device.
Integrations, before and after Aqueduct
- Every system has its own screen, login and data format.
- Meters feed the BMS and nowhere else.
- Alarms end at an inbox nobody owns.
- Network data sits in SCADA, separate from buildings.
- Nobody can prove a remote command actually ran.
The Aqueduct way- Meters, sensors and systems share one data layer.
- Pulse splitters share meters between the BMS and Aqueduct.
- Findings route into your CMMS with a recommended fix.
- SCADA data is read alongside, with control left in place.
- The command log shows whether each command executed.
Everything Aqueduct connects to
Device agnostic by design. If it emits telemetry, it can be onboarded.
| Category | Integrations | How it connects |
|---|---|---|
| Protocols | LoRaWAN, BACnet IP, BACnet MS/TP, Modbus TCP, Modbus RTU, MQTT, M-Bus, pulse outputs, REST API | LoRaWAN and IP gateways for sensors and meters; a field device network controller translates BACnet and Modbus to MQTT |
| Backhaul | Ethernet, Wi-Fi, LTE | Gateways reach the cloud over the customer network or an independent LTE connection |
| Building systems | BMS, BAS, EMS; AHUs, RTUs, chillers, VAV boxes | BACnet or Modbus through a field device network controller, reading points and acting where control is enabled |
| Simple control | Relay switches and water valves | LoRaWAN relays for fans and on or off loads; LoRaWAN valves for open, closed or partial positions |
| Metering | Water, electricity and gas meters and sub-meters; utility bill uploads | LoRaWAN meters, pulse counters, Modbus and M-Bus bridges, CT clamps, camera meter readers and uploaded bills |
| Work management | CMMS and EAM | Tickets routed in with a recommended fix; closures and asset context read back |
| Utility and network systems | SCADA, AMI, historians | Data read alongside; control stays with SCADA |
| Cloud and AI | AWS cloud, AWS Marketplace, on-prem AI on NVIDIA infrastructure | Runs on AWS or on your premises; available through AWS Marketplace |
| Notifications | Email and SMS | Alerts and findings delivered by email and SMS to the people who own them |
| Identity | Single sign on style sign-in with signed JWT tokens | Each session carries a signed token tied to your organization; every API call is checked against it |
Protocols and connectivity
Standard paths that integrators already know.
Systems and equipment
What Aqueduct reads, works with or routes work into.
Replace or work with. Integrate with.
- BMS
- BAS
- EMS
- BEMS
- Water management
- IAQ
- FDD
- M&V
- CMMS
- EAM
- IWMS and CAFM
- SCADA
- AMI
- Historians
Replace or work with means Aqueduct can take over the category or run across what you have. Integrate with means the system stays your system of record, and Aqueduct feeds it actions and reads its data.
How data and commands flow
Solid lines carry telemetry in. Dashed lines carry approved commands out.
Devices and gateways
LoRaWAN sensors and meters reach a LoRaWAN gateway; IP devices reach an IP gateway; equipment reaches a field device network controller over BACnet or Modbus.
Secure uplink
Gateways forward data over Ethernet, Wi-Fi or LTE, encrypted and mutually authenticated, into AWS IoT Core.
Decode and store
Vendor payloads are decoded, mapped from sensor to asset, and stored as raw and derived time series.
Analyze and route
The event engine raises findings, notifications go out by email and SMS, and tickets route into your CMMS.
Command and confirm
Where control is enabled, with owner approval, commands queue to the device, the device reports back, and the command log records the result.
Integration rules we keep
Stances matter more than logos.
Your CMMS manages the work
Aqueduct routes tickets and reads closures. Technicians, inventory and work orders stay in your CMMS.
SCADA keeps control
For water and energy networks, Aqueduct reads alongside SCADA. Control stays with SCADA.
Control needs approval
Aqueduct acts only where control is enabled, with owner approval, and logs every command.
Hardware through partners
We do not sell hardware as our core business. Devices are specified or reused and installed by partners.
Learn moreExisting meters stay
Pulse splitters let your BMS or EMS keep its meter signal while Aqueduct reads the same pulses.
Products confirmed in scoping
Which CMMS, BMS or historian products and versions apply to your site is confirmed during scoping.
Where teams put it to work
Work across the systems you have
Sites with a working BMS keep it. Aqueduct reads its points, adds meters and sensors, and acts where control is enabled.
Learn more
Take over where controls have aged out
Where a BMS has aged out, Aqueduct connects equipment directly through a field device network controller and takes over the category.
Learn more
SCADA and AMI read alongside
Utilities connect SCADA, AMI and historians to Aqueduct for loss detection by district, while network control stays with SCADA at all times.
Learn moresites in 21 countries run on Aqueduct.
and 9 clinics in one of India’s top hospital chains.
US airport running water intelligence on Aqueduct.
of commercial real estate under Aqueduct.
FMCG manufacturing campus.
operations run on Aqueduct.
Related
Common questions
Yes. Aqueduct reads BMS and BAS points over BACnet or Modbus through a field device network controller, and can act through schedules and setpoints where control is enabled with owner approval. It can also replace the BMS where controls have aged out.
Aqueduct supports LoRaWAN, BACnet IP, BACnet MS/TP, Modbus TCP, Modbus RTU, MQTT, M-Bus, pulse outputs and REST APIs. Gateways connect over Ethernet, Wi-Fi or LTE.
No. Aqueduct integrates with your CMMS and EAM, sending tickets with a recommended fix and reading verified closures back. Your CMMS keeps managing technicians, inventory and work orders.
Yes. Aqueduct reads SCADA, AMI and historian data alongside your systems. Control of the network stays with SCADA.
Yes, where they emit telemetry. Aqueduct reads pulse outputs, Modbus and M-Bus meters through bridges, and camera meter readers can read the face of older meters. Pulse splitters keep your BMS signal intact.
Yes. Aqueduct runs on AWS and is available through AWS Marketplace. It can also be deployed on-prem, with on-prem AI on NVIDIA infrastructure.
Aqueduct is device agnostic and onboards anything that emits telemetry, from water and energy meters to air quality, vibration and acoustic sensors. See the hardware page for capabilities, and installation runs through partners.
Aqueduct users sign in and receive a signed token tied to their organization, and every API call is checked against it. Specific identity provider options are confirmed during scoping.
See Aqueduct on your own facility.
Bring a site, a utility bill or a question. We will show you where the loss is.