Every Aqueduct feature, one problem at a time.
Each feature is written the same way: the problem, then the flywheel that resolves it, then what powers it. Outcomes lead, and modules appear only as powered by.

Water intelligence
Powered by WaterGuard · 9 featuresEnergy efficiency
Powered by EnergySmart · 10 featuresHealthy air
Powered by AirSafe · 8 featuresFacility operations
Powered by aQ PredictIQ on aQ Core · 14 featuresCommon questions
Aqueduct groups its features by outcome. Water covers leak detection, burst detection and non-revenue water. Energy covers weather-normalized baselining, measurement and verification, peak demand and load disaggregation. Air covers CO2, VOC and comfort per zone. Operations covers fault detection and diagnostics, predictive maintenance and asset observability.
No. Every feature reads from the same data layer, aQ Core, so a site can start with one outcome, such as water loss or HVAC energy, and add the others later. Adding a feature uses the meters and points already connected, with no new integration project.
Fault detection, leak detection and air quality features act by routing a ticket with a recommended fix into your CMMS. Smart Controls changes setpoints and schedules where control is enabled, with owner approval. Measurement and verification reports the result against the baseline, so every action has a measured outcome.
Aqueduct compares metered use with a weather-normalized baseline built from the site's own history and degree days, following IPMVP Option C and the regression approach in ASHRAE Guideline 14. Rate configuration turns the gap into money, so a saving is measured rather than estimated.
See Aqueduct on your own facility.
Bring a site, a utility bill or a question. We will show you where the loss is.