A residential society may have several water systems operating within the same property. Drinking water, domestic-use water and treated or recycled water can be stored in different tanks and distributed through different infrastructure. The exact arrangement varies by property.
A monitoring dashboard can bring these tank levels into one operational view while preserving the identity, purpose and response process for each water type. Good monitoring makes those distinctions explicit.
Why the tank label matters
Imagine an alert that says “Tower 4 tank low.” The facility team still needs to know which tank is affected and what that tank serves.
A low drinking-water tank may require a different response from a low domestic-water tank. A change in recycled-water storage may have implications for the services supplied by that particular system. A generic label leaves room for mistakes during an incident, especially when a new staff member is responding. For the underlying storage architecture, see underground and overhead tank monitoring.
Use a consistent naming convention that identifies the tower or shared location, the water type and the tank's role. Keep the same name in the dashboard, tank inventory, alert register and maintenance record.
Monitoring is not a water-quality test
A level sensor answers a storage question: how much water is present, or how high is the surface? It does not, by measuring level, establish whether the water is safe to drink or whether treated water meets the applicable quality requirements.
TownEve uses contactless ultrasonic sensing for suitable overhead and underground tanks to provide level and historical storage visibility. Water-quality assessment remains a separate measurement discipline using the appropriate chemical, microbiological or compliance methods.
Societies should continue their applicable water-quality sampling, treatment, inspection and compliance procedures independently of level monitoring. A full tank can still require quality checks, and an empty tank can still require a supply investigation.
Map each water type from source to storage
Before commissioning, identify the tanks included in each system. Record the source or incoming path, underground storage where present, transfer arrangements and relevant overhead tanks.
This map should reflect the actual site. Some properties have shared underground storage and multiple overhead tanks. Others use different layouts. A monitoring proposal should not assume that every building has three overhead tanks or a uniform distribution design.
For each monitored tank, record its water type, geometry, operating role and the people responsible for it. Identify tanks outside the monitoring scope explicitly.
Keep alerts specific to the system
A low-level threshold is not necessarily appropriate across all tanks. The response window depends on the storage volume, normal demand, refill pattern and operational role of that particular tank.
A high-level alert also needs context. It can prompt the team to investigate the filling process, but it does not independently prove physical overflow or automatically stop equipment.
TownEve currently supports configured level-based email alerts. The society should define the recipient and escalation path for each relevant tank. A recipient needs to know not just that a threshold was crossed, but which water system requires attention.
TownEve's monitoring layer provides storage visibility and alerts across the relevant water systems. Direct pump-state monitoring and remote pump operation are separate development layers being tested for site-specific operational use.
Interpret trends within the right network
Historical readings can help show whether a tank's level is rising, falling or remaining stable. The most useful comparison is usually between tanks connected through the same relevant supply and transfer process.
For example, a decline in one overhead tank can be reviewed alongside its corresponding upstream storage where both are monitored. If several tanks on a shared path change together, the facility team may investigate that common infrastructure.
Do not casually combine drinking, domestic and recycled-water volumes into a single “available water” figure. Such a total can obscure the fact that the water types serve different uses and may not be substitutable.
Tank-level trends guide investigation. They cannot, on their own, prove a pump failure, identify a valve condition or establish a water-quality problem.
Distinguish volume from usable supply
For a tank with verified geometry, measured water level can be converted into an estimated stored volume. But the existence of stored litres does not automatically establish how much usable water can reach each outlet.
Usable supply depends on the tank's practical operating range, the distribution arrangement, equipment conditions and the relevant water type. A percentage may be based on configured geometry or an operating reference, so its meaning should be documented.
Likewise, a drop in stored volume is not necessarily direct consumption. If inflow and outflow occur together, the change in storage reflects their net effect. Separate consumption measurement needs an appropriate method.
What residents should see
Residents may benefit from visibility into the water system relevant to their building. Clear labels and explanatory language are especially important when the property has multiple water types.
TownEve supports individual accounts, role-based access and a resident-facing experience. The society should decide which information is appropriate for each role and who is responsible for explaining a disruption.
A dashboard reading should not be turned into an unverified announcement. A low tank level does not automatically mean all homes have lost supply. A stale reading does not confirm the present level. Operational updates should distinguish what was measured from what the facility team has verified.
How to handle a missing reading
A communication issue can affect a tank's data without changing the physical water level. Check the reading timestamp first.
TownEve can alert the responsible team if input stops arriving for a configured period. Its multi-tower architecture uses RF communication from tower modules to one society-level master, followed by an internet connection to the application backend.
A freshness alert does not automatically identify whether the problem is the sensor, tower equipment, RF, power, master or internet. The facility team should use the site's troubleshooting process and independently verify an urgent physical condition when necessary.
Commissioning across water types
A commissioning record should list each tank's actual water type and location. Verify that the dashboard identity matches the physical asset and that alerts reach the correct recipients.
Where appropriate and safe, compare reported levels with independent observations. Confirm the configured dimensions or volume model and demonstrate historical trends and reading timestamps.
The team should also rehearse an incident involving one water type. Who receives the alert? Which upstream or downstream tanks should be reviewed? Who performs the physical investigation? Who communicates the verified impact to residents?
Do not let a successful demonstration on one tank stand in for commissioning every water system in the agreed scope.
A practical operating record
Keep a simple record for each monitored tank: identity, water type, location, geometry, associated infrastructure, alert settings, primary responder and support contact.
This helps prevent a change in committee or facility staff from turning a known system into a collection of unexplained labels. It also makes future expansion easier because new tanks can follow the same naming and responsibility convention.
The record should remain separate from water-quality certificates and other compliance documents. Monitoring supports operational visibility; it does not replace those records.
Where TownEve fits
TownEve provides contactless level monitoring of suitable overhead and underground tanks, historical trends, configured email alerts and role-based access. A deployment can cover different tank types and water systems within the agreed monitoring scope.
The first step is to map the property's actual storage and distribution arrangement. From there, the monitoring design can preserve water-type distinctions while giving the facility team and committee a coherent view of the site.
FAQ
Can the same monitoring platform display drinking, domestic and recycled-water tanks?
TownEve can monitor suitable overhead and underground tanks within the agreed deployment scope. Each tank should retain a clear water-type identity.
Does a tank-level sensor test drinking-water quality?
No. Level monitoring measures a storage condition, not microbiological or chemical water quality.
Can the society add all tank volumes to calculate usable water?
A combined geometric volume may be arithmetically possible, but it can be operationally misleading when the water types are not interchangeable.
Should every tank use the same low-level alert threshold?
Not automatically. Thresholds should reflect each tank's role, volume, refill pattern and response requirements.
Does a high-level alert mean a tank has overflowed?
No. It indicates a configured monitored level condition, not proof of physical overflow.
Can TownEve automatically switch pumps between water systems?
TownEve currently provides monitoring and alerts around the storage system. Remote pump operation is a separate development layer being tested with the safety integration and commissioning required for physical control.
What happens if one tank stops reporting?
Check the reading timestamp and investigate the monitoring path. A missing reading does not establish that the tank is empty or that its water is unsuitable.