---
title: How Society Water Monitoring Works
description: See how TownEve measures tank levels with contactless ultrasonic sensors, moves data over RF to a society master, and provides live and historical visibility.
---

[Skip to content](https://www.towneve.com/resources/how-it-works#main)

[![TownEve](https://www.towneve.com/hs-fs/hubfs/raw_assets/public/Towneve-Theme/assets/logo.png?width=164&height=70&name=logo.png)](https://www.towneve.com/)

Menu

- [Water Management](https://www.towneve.com/water-management)
  
  ⌄
  
    - [How It Works](https://www.towneve.com/resources/how-it-works)
- Solutions ⌄
  
    - [For Builders](https://www.towneve.com/resources/builder-water-monitoring)
- [Resources](https://www.towneve.com/resources)
  
  ⌄
  
    - [Case Studies](https://www.towneve.com/resources/tag/case-studies)
- [About](https://www.towneve.com/about)
- [Contact](https://www.towneve.com/contact)

[Log in](https://water.towneve.com)[Request an Assessment](https://www.towneve.com/contact/)

1. [Home](https://www.towneve.com/)
2. [Resources](https://www.towneve.com/resources)
3. How Society Water Monitoring Works

How It Works

# How Society Water Monitoring Works

A clearer view of your water system, from sensing to action.

[Request an Assessment](https://www.towneve.com/contact/)

A housing society water system is distributed by nature.

Water may be stored underground, transferred through pumps, and distributed to overhead tanks across several towers. The people responsible for operations need to understand what is happening across that network without physically checking every tank.

TownEve creates that visibility through a simple chain:

**Tank sensor → tower slave module → RF communication → society master module → internet → TownEve application → human response**

Each layer has a different job. Understanding those layers helps a society evaluate what it is actually buying when it installs a water monitoring system.

## 1. Measuring the water without immersing the sensor

TownEve uses contactless ultrasonic sensors mounted above the water surface.

An ultrasonic sensor emits a pulse toward the water and measures the returning echo. From the measured distance between the sensor and the water surface, the system can determine the level in the tank based on the configured tank geometry.

Because the measurement is contactless, the sensing device does not need to remain immersed in the stored water.

Sensor placement still matters. Tank shape, mounting position, obstructions and site conditions have to be considered during installation. The monitoring system therefore needs to be commissioned for the actual tank rather than treated as a generic plug-and-play reading.

## 2. Connecting the tanks within each tower

A multi-tower society can have many monitored tanks distributed over a large property.

TownEve does not require every tank to maintain its own independent internet connection. Sensors within a tower connect into a tower-level slave module.

The slave module provides the local communication layer for that tower and sends its data onward to the society-level master.

This separates local sensing from society-wide internet connectivity and allows the monitoring network to follow the physical layout of the property.

## 3. Sending tower data to one society master

Tower slave modules communicate with the society master over radio frequency, or RF.

The society master is the central aggregation point for the monitoring network. There is one master module per society in the current TownEve architecture, while slave modules are distributed by tower according to the installation design.

This distinction matters. The master is not repeated for every tank or every tower.

The actual RF design, antenna placement and any signal-boosting requirement depend on the property. Buildings, distance and site layout can affect radio communication, so the final installation is planned around the society rather than assumed from a standard diagram.

## 4. Connecting the society master to the internet

The master module sends the aggregated monitoring data to the TownEve application backend through an internet connection.

The architecture is designed to support practical connectivity choices at the society level. The exact connection used for a deployment is selected based on site availability and reliability requirements.

If internet connectivity is temporarily unavailable, that is different from a tank-level measurement problem. Connectivity health therefore needs to be treated as part of operating the monitoring system, rather than assuming that a missing cloud update means the water level itself has changed.

TownEve continues to develop its connectivity and resilience options as part of ongoing R&D.

## 5. Turning measurements into a live operational view

Once the data reaches the backend, the TownEve application presents it in a form that authorized users can understand.

The current production system provides live tank-level visibility, historical information, individual accounts and role-based access.

A live view answers the immediate question: what is the tank level now?

History answers a different set of questions: Was the tank filling? How quickly was it depleting? Did a change begin before the team noticed the operational problem?

That historical context is one of the main differences between continuous monitoring and a manual inspection. A manual check records a moment. Continuous data shows the sequence that led to that moment.

## 6. Giving the right people the right view

Water operations involve different responsibilities.

A society committee may need an overall view of the society. Facility or maintenance teams need operational visibility for the infrastructure they manage. Resident-facing experience is also a current capability. Individual accounts and role-based access allow the information shown to follow the responsibility and access model adopted for the deployment.

TownEve therefore uses individual accounts and role-based access rather than assuming every user should see or change the same information.

The principle is straightforward: access should follow responsibility.

## 7. From visibility to human response

Monitoring is useful only when the information leads to an appropriate response.

A falling overhead-tank level can have several causes. Incoming supply may be insufficient. Water may be available in underground storage but not reaching the overhead tank. A transfer pump may have stopped. Or demand may simply be higher than expected.

Tank-level monitoring provides evidence of what is happening to storage. It does not automatically prove the cause.

The operational team uses that information together with its knowledge of the water system to investigate and act.

This has already mattered at [Park Astra in Pune](https://www.towneve.com/resources/park-astra-case-study). On two reported occasions, TownEve monitoring helped surface falling tank levels associated with pump trips early enough for the maintenance team to respond before the affected tanks ran empty and residents experienced an interruption.

The monitoring surfaced the condition. The maintenance team took the action.

## 8. Monitoring versus automatic control

TownEve's monitoring layer creates the data foundation for increasingly connected water operations, including pump information and control.

Monitoring observes the system and provides visibility. Automatic control actively operates equipment.

TownEve is actively developing direct pump-state monitoring and remote/automated pump control, with initial control tests already completed. These capabilities extend the existing monitoring layer: water-level conditions that trigger alerts today can, once control is released, support defined pump actions. Production deployment will still require the necessary permissions, electrical integration, safeguards, manual override and fail-safe behaviour.

Reliable visibility is an operational layer in its own right and creates the information foundation for progressively deeper automation.

## 9. Overhead and underground tanks

The same monitoring architecture can be applied to relevant [overhead and underground storage points](https://www.towneve.com/resources/underground-overhead-tank-monitoring), subject to installation conditions.

This is important because many societies have a water journey rather than a single storage point.

A simplified fresh-water route might include:

**Water source → underground/raw storage → treatment where applicable → treated storage → transfer pump → overhead tank → homes**

Not every society follows the same topology, and not every element needs to be instrumented.

The correct monitoring design begins by mapping the actual water network and identifying which storage points provide useful operational visibility.

## 10. What happens when the system evolves?

TownEve's monitoring system is live at Park Astra and continues to evolve through real operating experience.

The product architecture is designed around progressive improvement. Connectivity options, operational intelligence, alerts, integrations and control capabilities can mature over time without redefining the basic principle of the monitoring system.

That principle remains:

Measure the infrastructure reliably.   
Move the data through a resilient society network.   
Present it to the people responsible for action.   
Preserve history so operations can be understood rather than guessed.   
Automate only when the control path is sufficiently safe and reliable.

## What a society should map before installation

A useful site assessment should establish the tanks to be monitored, their geometry and location, which tanks serve which towers, the relationship between underground and overhead storage, the location of pumps, suitable sensor mounting positions, RF paths between towers and the society master, available power, internet options at the master location, and the people who need access to the data.

That map determines the deployment.

The result should not be a collection of isolated sensors. It should be a monitoring layer that reflects how water actually moves through the society.

## Review your society's tank layout

If your society is evaluating water monitoring, the first useful step is to map the water journey and the storage points that matter operationally.

TownEve can review the tank layout and determine how sensors, tower modules, RF connectivity and the society master would fit the property.

## FAQ

Does every TownEve sensor connect directly to the internet?   
No. In the current architecture, sensors connect through tower-level slave modules. Those modules communicate over RF with one society-level master, and the master provides the internet connection to the TownEve backend.

How many master modules does a society need?   
The current TownEve architecture uses one master module per society. Tower-level slave modules connect the distributed tank sensors to that master over RF. Final deployment design still depends on site conditions.

Why use RF between towers and the master?   
RF provides a local communication layer between distributed tower equipment and the central society master without requiring an independent internet connection for every tank or tower. Actual radio performance is validated for the site.

What happens if the internet connection goes down?   
TownEve monitors the freshness of incoming telemetry. If the software stops receiving input for a configured period, it can alert the operating team that the communication path or device needs investigation. Manual troubleshooting is currently required to determine whether the cause is internet connectivity or another issue. TownEve hardware can retain up to 150 readings and upload retained entries after connectivity returns. At the fixed 30-second hardware reporting cadence, a full buffer represents up to approximately 75 minutes when the hardware remains powered and all 150 entries are retained. Remote readings are not live during the interruption.

Does TownEve automatically start or stop pumps?   
The released platform currently provides monitoring and alerts. Direct pump-state monitoring and remote/automatic pump control are in development and testing. Once released, control will require separate site-specific electrical integration, safety logic and commissioning.

Can the same system monitor underground and overhead tanks?   
Yes, subject to tank geometry and installation conditions. The useful monitoring points are selected from the society's actual water network.

Why keep historical tank data?   
History helps users understand how a condition developed. It can show filling and depletion patterns that a one-time manual inspection cannot reveal.

## Related resources

- [Water Monitoring for Housing Societies](https://www.towneve.com/water-management)
- [Park Astra Case Study](https://www.towneve.com/resources/park-astra-case-study)
- [Water Monitoring Vendor Checklist](https://www.towneve.com/resources/society-water-monitoring-checklist)
- [Underground and Overhead Tank Monitoring](https://www.towneve.com/resources/underground-overhead-tank-monitoring)

Explore further

## Understand your water system. Plan the next step.

Browse more practical resources or discuss your property's monitoring needs.

[Request a Water Monitoring Assessment](https://www.towneve.com/contact/)[All resources →](https://www.towneve.com/resources)

TownEve · CyberGrove Solutions Private Limited  
Water monitoring for residential communities.

[About](https://www.towneve.com/about/)[Contact](https://www.towneve.com/contact/)[Privacy](https://www.towneve.com/privacy/)[support@towneve.com](mailto:support@towneve.com)

 ​

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "TownEve Editorial Team",
    "url" : "https://www.towneve.com/resources/author/towneve-editorial-team"
  },
  "dateModified" : "2026-10-04T15:43:19.632Z",
  "datePublished" : "2026-09-28T12:28:36.000Z",
  "headline" : "How Society Water Monitoring Works",
  "mainEntityOfPage" : {
    "@id" : "https://www.towneve.com/resources/how-it-works",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.towneve.com/hubfs/TownEve%20logo%20(1).png"
    },
    "name" : "TownEve"
  }
}
```