A pilot can help a housing society understand whether a water-monitoring system works in its actual environment. But a single sensor showing a number on a screen is not enough to establish whether the system will be useful across the property.
A meaningful pilot tests a defined operational question. It identifies what will be installed, what evidence will be collected, who will respond to alerts and which conditions must be satisfied before the society considers expansion.
The goal is a decision based on observed results, not a demonstration that is impossible to evaluate later.
Begin with the decision the pilot should support
A committee may want to verify that a contactless sensor can monitor a particular tank, that the facility team can see historical changes, or that configured email alerts reach the right person.
Those are different objectives. Write them down before installation. If the pilot is intended to assess sensor suitability, focus on the selected tank and its measurement conditions. If it is intended to assess a multi-tower deployment, one nearby tank cannot establish radio coverage across distant towers. Use the contactless sensor installation guide when defining installation acceptance.
A useful pilot brief identifies the question, proposed scope, responsible people, duration or observation conditions, evidence to be collected and decision criteria. There is no universal pilot length that fits every tank and property.
Choose a representative tank
A pilot tank should reflect the problem the society wants to solve. Consider whether it is an underground or overhead tank, its geometry, mounting access, water type and normal fill-and-drawdown pattern.
A tank that barely changes level during the observation period may demonstrate that readings arrive, but it offers limited evidence about how the system represents a full operating cycle. Where practical, observe ordinary filling and drawdown under the site's normal operating procedures.
Do not alter water-supply operations merely to create a dramatic demonstration. Any test affecting equipment or supply should follow the property's approved procedures and be supervised by qualified personnel.
Define the decision the pilot should support
A successful tank-level pilot can support a decision about the tested sensing and software functions. It does not automatically verify every other tank geometry, mounting location or communication path.
For TownEve's current architecture, tower-level slave modules communicate by RF with one society-level master, which uploads readings through an internet connection. A pilot close to the master may not represent a tower separated by buildings or installed in a different equipment environment.
If the full project includes several towers, define a separate RF survey or coverage-acceptance step for the wider deployment. If the pilot excludes certain water types or underground tanks, list those exclusions explicitly.
Establish a baseline before installation
Record the tank identity, dimensions or available drawings, expected operating range and current observation method. Identify any existing local level indicators or physical checks that can be used safely for comparison.
Ask the facility team what problems it currently encounters. Is it difficult to see tank behavior between manual inspections? Are low levels discovered only after a complaint? Is there uncertainty about whether a displayed reading is current?
These questions help distinguish a technically functioning sensor from a monitoring system that fits the team's work.
The baseline should not invent savings, outage frequency or consumption numbers. Use existing records where available and mark missing evidence as missing.
Agree on the measurement reference
A top-mounted ultrasonic sensor measures distance to the water surface. Turning that measurement into water depth requires a correctly configured reference for the actual installation.
For a regular tank, estimated stored volume can then be calculated from verified geometry. Irregular shapes may need a more detailed level-to-volume relationship.
During the pilot, compare readings with approved independent observations at more than one operating point where feasible. Record the conditions and any limitations. Do not assume that a percentage or estimated litres figure is accurate merely because it appears plausible.
Test historical visibility, not just the current number
The pilot should demonstrate how the reported level changes over time. Review a normal filling or drawdown sequence and check whether the trend matches independently understood operations.
Historical level data can help a facility team see when a change began. It cannot independently establish the electrical state of a pump or prove why the level changed.
A flat trend can also be consistent with balanced inflow and outflow. Avoid presenting a constant tank level as evidence that no water was consumed.
Test the alert workflow
Choose a configured level condition relevant to the tank's normal operation and demonstrate that the intended email recipient understands the alert and the response.
The test should establish the tank identity, threshold, reading timestamp and ownership of the next action. A message delivered to an unattended mailbox is not an effective operational workflow.
TownEve provides configured level-based email alerts. A pilot should test the notification channels included in its agreed scope, along with recipient delivery and the operating response attached to them.
Also demonstrate the distinction between a level alert and a telemetry-freshness alert. The latter means that input has not arrived for a configured period. It does not establish that the tank is empty.
Check the communication path
The pilot should identify how readings reach the application: sensor, local tower equipment where applicable, RF path to the society-level master and the master's internet connection.
Document the actual equipment locations and power arrangements. Verify that readings are fresh during ordinary operation.
Where appropriate and safe, demonstrate what the facility team sees when telemetry stops arriving. The response should include checking the last reading time and following the site's independent level-verification procedure if a current physical condition matters.
TownEve hardware can retain up to 150 readings during a connectivity interruption and upload retained readings after connectivity returns. A pilot can test this behavior against the fixed 30-second hardware reporting cadence so the site understands the resilience window for its installation. A full buffer represents up to approximately 75 minutes at the fixed cadence, provided the hardware remains powered and all 150 entries are retained.
Assign people before testing
Name the facility representative who will observe the pilot, the person who will respond to configured alerts and the committee representative who will review the evidence.
Give each person the access appropriate to their role. TownEve supports individual accounts, role-based access and a resident-facing experience, but the pilot should not confuse viewing tank information with responsibility for operating equipment.
Set a simple incident log. Record the observation, time, reading freshness, action and independently verified finding. This helps distinguish a sensor issue from a water-system issue during review.
Use an acceptance record
At the end of the pilot, review the agreed criteria one by one. Did the sensor produce plausible readings under the observed conditions? Was the tank correctly identified? Could the team review historical levels? Were the intended email alerts delivered? Did users understand stale data? Were unresolved installation or communication issues documented?
Do not turn a pilot into a single yes-or-no verdict without recording exceptions. A pilot can support expansion while still identifying another tank type or tower location that needs a separate test.
Keep the decision grounded in the agreed evidence rather than an unverified claim of guaranteed savings, uptime or prevented outages.
Plan the next phase separately
If the society proceeds, prepare a full tank inventory and identify every tower, underground tank, overhead tank and water type within scope. Verify the communication design at the actual equipment locations.
The expansion plan should cover tank geometry, mounting, power, RF coverage, connectivity, alert recipients, role access, commissioning and handover. A successful pilot is an input to that plan, not a substitute for it.
A phased rollout may be appropriate when the property has different tank types or difficult communication paths. The phases should be defined by site requirements rather than an assumed universal sequence. A one-tank pilot should also be interpreted against the multi-tower monitoring architecture required for a full rollout.
Where TownEve fits
TownEve provides contactless ultrasonic monitoring for suitable overhead and underground tanks, current and historical levels, configured email alerts, role-based access and telemetry-freshness monitoring.
A TownEve pilot can focus on the sensing and operating questions most relevant to the property, with scope and acceptance criteria documented in the agreed proposal. Direct pump-state monitoring and remote pump operation can be treated as separate evaluation layers where they are specifically included and ready for site-specific testing.
FAQ
Is one tank enough for a pilot?
One tank can test defined sensing and software questions at that location. It cannot prove that every tank or RF path across the society will perform identically.
How long should a monitoring pilot run?
Choose an observation period that captures the operating conditions needed for the agreed objectives. There is no universal duration that guarantees a meaningful evaluation.
Can the pilot prove a pump failure will be detected?
Tank-level trends may prompt investigation, but level alone cannot establish a pump's electrical state. Direct pump-state monitoring is in development.
Should the society test alerts?
Yes. Confirm the intended email recipient, tank identity, configured condition and response responsibility.
What if the reading stops updating?
Treat the last reading as historical, investigate the telemetry path and independently verify the physical level if necessary.
Does a successful pilot guarantee the full rollout?
No. The wider project still needs a tank inventory, site assessment, communication checks and commissioning at its actual locations.
Can the pilot measure apartment-level consumption?
Tank-level monitoring measures stored-water conditions and net changes. Apartment-level consumption requires an appropriate separate measurement method.