A tank-level graph is often more informative than a single percentage. It can show how monitored storage changed before a complaint, during an expected supply window or after a facility team investigated a problem.
But a line on a chart is still a record of measurements, not a complete account of everything happening in the water system.
To read it responsibly, begin with the tank identity, the measurement scale and the timestamps. Then separate what the line actually shows from possible explanations that need verification.
Start with three questions
Which tank does the graph represent? A housing society may have underground and overhead storage, several towers and separate drinking, domestic and recycled-water systems. The label must correspond to the correct physical asset.
What is the vertical axis? The graph may show a measured level, a configured percentage or an estimated stored volume. These quantities are related but not interchangeable.
How recent is the latest reading? A chart can continue displaying its last known value after the device stops reporting. Check the actual timestamp before using it to describe the present condition.
TownEve provides current and historical level visibility for suitable monitored tanks. Its readings should be interpreted in the context of the configured tank and data freshness.
A rising line means net storage increased
When a valid level reading rises, the monitored water surface has moved upward relative to the configured reference.
That is consistent with net replenishment. It does not, on its own, identify the source. A tank may receive municipal supply, a tanker delivery, water transferred from another tank or a combination of inflows.
The rise also does not directly measure the total amount that entered if water was leaving at the same time.
Where a stored-volume estimate is used, the relationship between level and volume depends on the verified tank geometry. Do not treat a percentage-point increase as the same number of litres in every tank.
A falling line means net storage decreased
A valid downward trend indicates that the monitored water surface fell.
This may be expected during normal drawdown. It can also be operationally important if replenishment is delayed or the tank approaches a configured low-level threshold.
The slope does not automatically establish water consumption. Water could be transferred elsewhere, drained for approved maintenance or affected by other outflows.
A falling overhead-tank level also does not prove that a pump failed. The facility team must verify the physical cause independently.
A flat line can have several explanations
A nearly constant level may mean that the tank's net stored volume changed very little during the observed period.
It does not prove that no water entered or left. Inflow and outflow can balance. A graph may also look flat because the changes are small relative to the displayed scale or measurement interval.
Before interpreting a flat line, check whether readings were actually received throughout the period. A last-known value displayed during a communication interruption is different from a series of fresh, similar readings.
If the physical system is expected to be changing but the line remains unchanged, the facility team may need to check the data and operating conditions. The graph alone cannot decide which explanation is correct.
A repeated rise-and-fall pattern
Some tanks show repeated increases and decreases as water is replenished and drawn down.
This pattern can help a team understand how monitored storage behaves over time. It may be useful when comparing similar days or identifying a change from a familiar operating pattern.
Do not assume that each upward segment proves a pump started or that each downward segment proves it stopped. The property may have several inflows and outflows, and direct pump-state monitoring is a separate measurement.
A repeating pattern is an observation. Its operational meaning depends on the verified plumbing and control arrangement.
A sudden step or jump
A sharp change in the plotted line may represent a real rapid change in the water surface. It may also reflect a data gap, an incorrect configuration, a measurement issue or a change in the chart's presentation.
Check the time interval between the points. A line connecting two readings does not prove that the level changed instantaneously between them.
Review whether the tank or sensor configuration was modified, whether the relevant data is fresh and whether the operating record documents a corresponding event.
Do not label an abrupt change as a leak, overflow or pump fault without independent evidence.
A missing section of the graph
A gap can mean that readings were not available for the period shown. Its significance depends on how the particular application presents missing data.
Missing readings should not be silently interpreted as an unchanged water level. Nor should a straight line drawn between observations be mistaken for measurements taken throughout the interval.
TownEve can alert the responsible team when input has not arrived for a configured period. This telemetry-freshness condition is distinct from a low-water condition.
TownEve hardware can retain up to 150 readings during a connectivity interruption and upload the retained entries after connectivity returns. This supports historical recovery within that buffer but does not provide live remote visibility during the outage.
Why the graph scale matters
A line can look dramatic when the vertical axis shows a narrow range. The same change may look modest when the entire tank depth is displayed.
Similarly, a short time window emphasizes individual changes while a longer window may make them appear smaller.
Read the actual values, units and timestamps rather than judging severity from the steepness of a picture alone.
If comparing two tanks, check whether their dimensions, percentage references and chart scales are comparable. Equal percentage changes do not necessarily represent equal volumes.
Level, volume, flow and pressure are different
Level describes the observed water surface at the monitored point. Estimated stored volume uses the tank's geometry to translate that level into an amount.
Flow describes water moving through a particular path over time. Pressure describes a condition at a particular point in the distribution system.
A level chart generally shows net storage behavior. It does not directly measure individual inflows, outflows or tap pressure.
If the society needs source-specific quantities or distribution-pressure evidence, the appropriate additional measurement must be defined separately.
Compare related tanks without inventing causation
A society may observe an underground tank rising while an overhead tank falls. That combination describes the net movement of two monitored storage assets.
It may prompt the team to check the transfer path, but it does not prove that a particular pump is off or a valve is closed.
Likewise, several overhead tanks declining together can justify checking a shared supply dependency. The trend alone cannot identify the precise cause.
Use the verified tank map, operating records and approved physical checks to interpret relationships.
How to review an incident timeline
First identify when the reported issue occurred and which tanks are relevant. Then examine the readings before, during and after the event, noting any data gaps.
Record observations in neutral terms: “The monitored level fell during this interval” or “No fresh reading was available after this time.”
Separately record facts confirmed by the facility team, such as a supplier's revised delivery schedule or an independently verified equipment issue.
This separation makes the incident record more useful than a narrative that treats every change in the chart as proof of a cause.
What the graph cannot certify
A tank-level chart does not establish water quality, prove that a valve is open, verify a pump's electrical state or certify the quantity unloaded from a tanker.
It cannot guarantee how many hours of usable water remain. That depends on usable storage, demand, incoming supply and the distribution arrangement.
A dashboard may still be valuable without performing those functions. Its value is a timestamped view of monitored storage that the team can combine with other verified information.
A simple reading checklist
Before drawing a conclusion, confirm the tank identity and water type. Check the units and scale. Verify the latest timestamp and identify any gaps.
Describe whether the valid observations rise, fall or remain broadly stable. Ask which inflows and outflows could have been active, then check those conditions independently.
Finally, state what is known, what is inferred and what remains unresolved. That discipline is especially useful when sharing a chart with committee members or residents.
Where TownEve fits
TownEve provides current and historical readings for suitable monitored overhead and underground tanks, configured email alerts and telemetry-freshness monitoring.
The historical chart can help users see net storage changes and review the timing of events. It should not be described as an automatic explanation of why a change occurred.
Direct pump-state monitoring and remote pump operation remain in development or testing. Consumption estimation, however, can be derived from level and volume history when the operating boundary is deliberately controlled, such as a verified no-inflow period. That calculation is distinct from simply inferring consumption from an uncontrolled level chart.
Frequently asked questions
Does a rising line prove the municipal supply arrived?
No. It shows net replenishment of the monitored tank; the source needs independent confirmation.
Does a falling line measure residents' consumption?
Not directly. The level reflects net storage change, potentially including multiple inflows and outflows.
Why does the line look flat while water is being used?
Inflow and outflow may balance, changes may be small on the chart scale or the data may need verification.
Can a chart show whether a pump was running?
A level trend may suggest a reason to investigate, but it does not directly establish pump state.
What does a gap in the chart mean?
It indicates that the displayed history lacks observations for that period or presents them differently. Check the application's data-freshness information.
Can a sudden jump prove an overflow?
No. A jump needs interpretation and verification. Tank-level data alone does not certify physical overflow.
Can two tanks with the same percentage have the same litres?
Not necessarily. Their geometry and configured volume relationships may differ.