HVAC&R monitoring and control, from the chiller plant to the cold room

Measure pressure, temperature, condenser water flow and the electrical input of each compressor group, then compare energy against cooling output under similar conditions. Aqueduct flags rising energy with flat cooling as poor heat removal and recommends condenser and cooling tower checks before compressors fail.

Yes. Aqueduct tracks cold room temperature and humidity continuously, records each excursion with its time and duration, and links it to the refrigeration plant serving the room. Major dairy operations run on Aqueduct.

Through a field device network controller that speaks BACnet or Modbus to the equipment, and LoRaWAN relays for simple loads. Control runs only where it is enabled with owner approval, with lockouts against short cycling and a command history for every change.

Predictive maintenance looks for early signs of failure before a fault happens, such as rising compressor vibration, a new sound signature or energy drift. In Aqueduct, aQ PredictIQ reads these signals and schedules maintenance first, routing the work into your CMMS.

No. Aqueduct supplies the measured evidence: a continuous temperature record, deviations with their closure, and exports for any assessment period through aQ Assurance. Your team or your consultant files and certifies.

Yes. Aqueduct can read beside an existing BMS and plant manager without writing anything, take over control where the owner chooses, or be built into new construction. Its recommendations can be carried out through the systems you already run.

Yes. A hospital chain with 22 hospitals and 9 clinics is an Aqueduct client. In hospitals, Aqueduct tracks chiller plant efficiency, air handler states and critical room pressure, and can run read-only so existing validated control strategies stay as they are.

Yes, where the supply is metered with BTU or energy meters. Consumption is baselined against weather like any other utility.

Discharge pressure and compressor power rise for the same cooling output under similar conditions. That trend is flagged before efficiency loss turns into a trip.

Yes. Read-only deployments use an outbound data path and write nothing to existing controls. Control can be enabled later, with owner approval, if the hospital chooses.

A continuous temperature and humidity record per room, every excursion with its time and duration, and its closure. Your team or auditor uses the export; Aqueduct does not certify the room.

For cooling-heavy sites, kW per ton or energy per unit of cooling, because it shows efficiency loss as it develops. For cold storage, excursion minutes per room come first.

Floating head pressure lets condensing pressure fall with cooler ambient conditions instead of holding a fixed setpoint, which reduces compressor lift. Aqueduct shows discharge pressure against ambient so the opportunity is visible, and a change can be made through the rack controller or, where control is enabled, with owner approval.

No. Room temperature and humidity are the core record. Door contacts add the cause behind many excursions and are installed through partners where the site wants that detail.

Each excursion is set against the defrost status, door events and rack data for the same period. An excursion that starts and ends with a defrost reads very differently from one where the rack lost capacity.

Where the controller exposes data over BACnet or Modbus, the field device network controller reads it. Where it does not, pressure, temperature and power sensors are added through partners.

Because many plant faults are caused somewhere else. Low delta T at the chillers is usually caused at the coils, and a coil that cannot hold supply air is often a chilled water problem. One data layer lets the trace follow the cause.