| Aquana Platform |
The Aquana Platform is a comprehensive term for the cloud and mobile based software in the technical infrastructure that supports the Aquana product set. |
| Platform Account |
The customer's account for a specific property. or utility in the Aquana system is called the Platform Account. This is to accommodate a customer who may represent multiple properties or utilities. All devices for the specific property/utility will beset up to operate with the Platform Account |
| Device |
Device refers to devices that are managed by the Aquana platform. They are:
- Valve
- Meter
- Water Sensor
- Gateway
|
| Location |
Each device in a Platform Account is placed within a specific "Location". The Location refers to something like an apartmenr number or a street address where the device is located. Multiple devices may exist at a Location. For example, a valve and a meter within an apartment. |
| Rule |
Activity in the Aquana Platform is governed by Rules. The Rules tell the system how to react to different conditions detected by the valve. Rules are individually configured for each Platform Account. There is a set of default rule configurations that are used when creating a Platform Account, and these can be modified for specific requirements as necessary. |
| Command |
"Command" is the term for an instruction sent to a valve from the Aquana Platform. A command can be sent to change the valve position, schedulke a sediment turn, change valve configuration settings, and restart the valve. A command issued to a LoRa Class C device will be received by the valve in real time. Commands from all other devices will be received by the valve based on the current check-in interval settings. For these devices, the command will be issued to the valve at the next scheduled check-in |
| Alert |
Alerts are sent to the Aquana Platform by the valve to indicate different conditions that have been detected by the valve. Alerts typically require a response or intervention. A full list of Alerts can be found in the Aquana Web App in Settings/Rules. The actions taken in response to Alerts are notifications are sent to individuals managing the Platform Account and/or the position of the valve is changed. |
| Check-in |
A Check-in occurs when the valve reaches out to the Aquana platform to share current information, such as meter data or detected valve conditions (burst, constant flow, dry pipe, reverse flow, etc.). Pending commands are also received by the valve when it checks-in. |
| Check-in Interval |
Aquana refers to the time interval between valve-to-cloud communication events as the “Check-in Interval”. Essentially, the valve “checks in” with the Aquana Platform on a regular basis to upload pertinent status data such as meter data or valve conditions, and to check for issued commands that contain instructions for activating the valve. The interval is dependent upon communications protocol and power source. |
| Check-In Boost |
Check-In Boost is a feature designed to temporarily increase the frequency with which a valve will check-in with the Aquana Cloud. This is intended for valves running exclusively on battery power set to other 8 or 12-hour check-in intervals. The check-in boost is used primarily to support a more prompt reconnect for a property or utility conducting dissconnect/reconnect transactions for delinquint payers. When a disconnect (Close) command is issued, the check-in boost temporarily decreases the check-in interval to 1-hour so the reconnect (Open) command can be prompt;y received after customer payment. |
| Sediment Turn |
A Sediment Turn is a 180-degree turn of the valve. This is done through a command issued from the Aquana platform for the purpose of mitigating the risk of any corrosion or sediment buildup inthe valve that may compromise the valve's ability to function properly. Note that if the valve is already closed, it will ignore the Sediment Turn command to prevent any unexpected water flow in that situation. |
