aQ Core: the data model every Aqueduct product reads from.
aQ Core locates every site, floor, zone and device, collects each device's readings at the interval it needs, and stores them in a single model. Water, energy, air, maintenance and the assistant all read from that store, so a reading is collected once and used everywhere.
Site, floor, zone, device.
Site
A pin on the portfolio map with its status and the normalizers used for comparison, such as floor area and visitors.
Floor
Real CAD floor plans. A multi-floor building is one site with several floors, not several sites.
Zone
The area one sensor speaks for. Zones exist because an air sensor covers a radius, not a building.
Device
A meter, sensor or controller with its own readings, health and event history.
Four tabs on every device.
| Tab | What it holds |
|---|---|
| Data | Every reading over the device's life, with a date range picker. A year of air readings fits in one view. |
| Health | Connection reliability and battery or capacitor voltage are continuously monitored for each device, enabling predictive maintenance to avoid data loss. |
| Events | Threshold crossings and alerts raised on this device. |
| Event groups | Related events grouped for review. |
Anything that sends telemetry can be onboarded.
Shared services the products draw on.
Rate configuration
Tariffs taken from utility bills, used everywhere a difference in use is turned into money.
Occupancy
Detected by sensors or set as a schedule per building, floor or zone.
Billing management
Tenant bills from sub-meters, bill validation against supplier invoices, and cost recovery.
Why the data model comes first.
data at minimum from advanced meters, required in US federal buildings by 1 October 2022 under the Energy Act of 2020.
Source: DOE FEMPbuildings in DOE's Smart Energy Analytics Campaign, where information systems alone delivered median savings of 4%.
Source: US DOE Smart Energy Analytics CampaignRelated
Common questions
No. aQ Core holds the sites, devices and readings; control belongs to Smart Controls, which acts through LoRaWAN relay switches or a field device network controller speaking BACnet or Modbus. Core supplies the data those commands rely on and stores what each device reports back. See integrations.
aQ Core accepts anything with a telemetry output, from utility-grade flow meters to battery room sensors and vibration units on rotating plant. Brands are picked site by site, and a new device starts building its own reading log and health record the moment it reports. Browse supported hardware.
Your own team can edit layouts, create zones and place devices in aQ Core without a developer. During installation, technicians do it in the field with aQ Atria as each device is commissioned, so readings attach to the right room. See aQ Atria.
aQ Core flags it on the device health record. Falling connection reliability or a sagging battery or capacitor voltage points to one device in one zone, so a technician replaces that sensor before its readings drop out. See asset observability.
Yes. aQ Core stores normalizers such as floor area and visitor counts for each site, so water and energy are compared per square foot or per visitor rather than as raw totals. Sites can then be ranked across a portfolio. See portfolio benchmarking.
See Aqueduct on your own facility.
Bring a site, a utility bill or a question. We will show you where the loss is.