Resources

How to Measure Municipal Water Supply to a Housing Society

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:26:18 GMT

QUICK ANSWER

To know how much municipal water a society receives, identify the supply entry point, record the volume passing a suitable verified meter over a consistent period, and reconcile that record with the receiving tank's level history and any simultaneous withdrawals.

A municipal supply schedule tells you when water may arrive. It does not tell you how many litres entered the property.

If no suitable incoming meter exists, a change in tank volume may help estimate net storage change. It cannot independently separate municipal inflow from simultaneous pumping, withdrawal or another source.

WHY RECEIVED VOLUME MATTERS

A society may receive municipal water for a shorter window than usual, experience a reduced flow rate, or receive supply at an unexpected time. Without quantity records, the committee may see only the downstream symptom: falling tank levels.

Recording the received volume creates a useful supply baseline. It helps answer whether supply has changed, how much additional water might be needed and whether a storage or transfer problem is masking the situation.

The goal is not to predict municipal policy from a sensor graph. It is to make the property's own water balance more reliable.

STEP 1: DEFINE THE SUPPLY BOUNDARY

Start with an approved plumbing diagram and a site walk-through by authorized facility personnel.

Identify the municipal entry point, any branch lines, the receiving tank or service, and whether other sources enter the same tank.

Check whether a meter measures all municipal water entering the property or only one branch. A reading at a branch cannot automatically be described as the society-wide municipal total.

Keep drinking, domestic and treated recycled-water services separate where the installed system requires it.

Do not open, alter or interfere with a utility-owned meter or supply connection. Any meter installation or modification must be carried out by authorized personnel under applicable rules.

STEP 2: USE AN APPROPRIATE VOLUME MEASUREMENT

A correctly selected, installed and maintained incoming flow meter can measure the volume passing its defined point.

Record the meter identity, units, reading timestamp, installation boundary, any known calibration or verification information and the responsible operator.

If a cumulative meter reads 1,250 kL at the start of a period and 1,290 kL at the end, the difference is 40 kL over that period, assuming the reading is valid and no meter rollover or reset has occurred.

This is an illustrative calculation, not a reported result from any society.

Do not assume every meter reports in litres; some display cubic metres or kilolitres. One cubic metre equals one kilolitre, or 1,000 litres.

Meter selection, pipe conditions and installation requirements should be reviewed by a qualified engineer or authorized provider. This article does not prescribe a meter specification for every site.

STEP 3: RECORD WHEN WATER ARRIVES

A daily total alone may conceal an operational problem.

Record the start and end of a verified supply window where possible. Compare it with the volume received and the resulting storage trend.

If the municipal connection delivers water for two hours, the total received still depends on the actual flow over those two hours. Duration is not a substitute for volume.

Where supply is intermittent, a dated event ledger is useful:

Use “unknown” for missing values. Do not invent a start time from an overhead tank graph if the tank has other inflows or withdrawals.

STEP 4: RECONCILE THE RECEIVING TANK

For a single tank and a defined period:

Closing stored volume = opening stored volume + municipal inflow + other inflow − withdrawals or transfers ± documented adjustments.

Suppose an underground tank begins with 80 kL, receives 40 kL of measured municipal water and transfers 25 kL to overhead storage. With no other flows or adjustments, its expected closing volume is 95 kL.

If the observed closing volume differs, investigate the timing, meter record, other sources, transfers, tank configuration and measurement uncertainty before assigning a cause.

The receiving tank's level change alone would be only 15 kL in this example. It would be incorrect to report that the municipality supplied just 15 kL.

STEP 5: AVOID DOUBLE COUNTING

For a property-wide boundary including both underground and overhead tanks, pumping from the underground tank to the overhead tank is an internal transfer.

It is not additional municipal supply.

For an overhead-tank-only boundary, that same pumping is an inflow to the overhead tank. The distinction is the accounting boundary, not a contradiction.

If municipal and tanker water both enter an underground tank, record them as separate source inputs. A rise in the shared tank cannot, by itself, prove how much came from each source.

STEP 6: HANDLE SITES WITHOUT AN INCOMING METER

A society can still begin with a source ledger and verified storage readings.

Record official or supplier-reported supply windows separately from observed tank changes. Note whether pumping, resident withdrawals or other inflows were occurring during each observation period.

A carefully selected period with no other inflows or outflows may permit a constrained volume-change estimate. It should be labeled as an estimate, with the assumptions stated.

Do not extrapolate an estimate from one quiet interval to every day. Do not present a nominal supply duration as a measured volume.

Where incoming volume is important to procurement, tanker planning or dispute resolution, consider the feasibility of an appropriately installed independent meter.

STEP 7: CONNECT SUPPLY RECORDS TO USABLE STORAGE

The amount of water received is not the same as the amount currently available to residents.

Tank geometry, dead-water height, current level and the transfer arrangement affect usable storage.

TownEve directly senses water depth and derives tank-specific level and volume from configured geometry. Tank-specific 0% and 100% reference levels define the usable range, allowing unusable or dead-water portions to be excluded from usable-water calculations.

This supports accurate volume calculations across different sizes and shapes when the geometry configuration and measured level are correct.

Use these storage observations alongside verified incoming records. They complement, rather than replace, an incoming flow meter.

STEP 8: CREATE A COMMITTEE REPORT

A useful weekly report can show:

When comparing weeks, align the reporting boundary and period. A shorter supply window does not necessarily mean a lower received volume, and a lower received volume does not automatically establish a municipal fault.

Report what the evidence supports.

WHAT TO DO IF MUNICIPAL SUPPLY FALLS

First verify the incoming record and confirm that the apparent change is not a meter, timestamp or plumbing issue.

Then review usable storage and a clearly labeled demand scenario. Identify when the society might reach its response reserve if the shortfall continues.

Check the responsible authority's current notices and contact channels. For Pune and PCMC, do not assume the same schedule, restrictions or cause applies to every locality.

If tanker supplementation is considered, calculate the required volume from projected demand, usable opening storage, expected non-tanker supply and a chosen closing reserve. A booked tanker is not verified received water.

WHERE TOWNEVE FITS

TownEve currently offers contactless ultrasonic level monitoring for suitable underground and overhead tanks, current and historical readings, configured email alerts, telemetry-freshness monitoring and tank-specific usable-volume calculations using configured dimensions and dead-water height.

This provides visibility into the storage response to changing supply. Where source-specific municipal receipt is required, an incoming meter or a suitably controlled estimation method supplies that source evidence; uncontrolled simultaneous inflow and outflow remain a net storage observation.

Flow-meter integration is app-capable, although flow-meter hardware has not yet been deployed. Direct pump-state monitoring is in development; remote pump operation is in development and testing. These are development layers extending the current tank-monitoring platform.

The practical progression is to combine verified incoming measurements with verified usable storage, then improve the water balance as more independently measured data becomes available.

FAQ

Does a water supply schedule show how much water a society received?

No. It indicates an expected or reported window; actual volume requires an appropriate measurement or a clearly qualified estimate.

Can I calculate municipal inflow from a rising tank level?

Only under documented conditions. Simultaneous withdrawals, pumping and other sources can make level change different from municipal inflow.

Does an overhead tank reading measure municipal supply?

Not directly. It measures that tank's level, which can reflect transfers and withdrawals.

How do I convert a meter reading in cubic metres to litres?

Multiply cubic metres by 1,000. One cubic metre is one kilolitre.

Should tanker water be counted as municipal water if both enter the same tank?

No. Maintain separate source records; the shared tank's level does not identify the source contribution.

What if the incoming meter and tank balance disagree?

Check units, timestamps, boundary, meter condition, other flows and geometry configuration before drawing conclusions.

Can TownEve replace an incoming municipal flow meter today?

No released direct incoming-flow measurement capability is claimed here. TownEve's current verified capabilities concern tank-level and usable-storage visibility.

Water Budget Data Quality: How to Keep a Housing Society Water Balance Trustworthy

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:25:20 GMT

Water Budget Data Quality: How to Keep a Housing Society Water Balance Trustworthy

A water budget is only as useful as the evidence behind each number. A spreadsheet can balance perfectly and still mislead a committee if an unknown quantity has silently been entered as zero, if readings come from different timestamps, or if a calculated quantity is presented as though it were directly measured.

The practical goal is not to make every number equally precise. It is to make the quality and origin of every important number visible.

1. Unknown is not zero

Zero means the quantity is known to be zero for the defined period and boundary. Unknown means the quantity has not been established.

Examples:

• No tanker arrived during the period, verified from the operating record: zero tanker inflow.

• Tanker records were not available for the period: unknown tanker inflow.

• No meter exists on an incoming source: incoming quantity may be unknown or estimated, but it is not automatically zero.

Replacing unknown values with zero can create a false water-balance residual and lead to the wrong operational conclusion.

2. Use explicit evidence classes

TownEve’s water-budgeting method should keep evidence classes visible. The useful classes are:

Measured — obtained directly from an appropriate sensor, meter or verified quantity measurement.

Calculated — derived mathematically from measured/configured inputs using a stated method.

Observed — a directly observed operating condition that is not itself a quantity measurement.

Estimated — a quantitative approximation based on incomplete measurement or a stated estimation method.

Supplier-declared — a quantity stated by a supplier or external party but not independently measured by the society.

Assumed — an input deliberately chosen for planning or scenario analysis rather than observed as fact.

Planned — a future quantity, event or operating condition expected or scheduled but not yet observed.

Testing — a method or capability being evaluated and not yet treated as a released or universally validated operating measurement.

Unknown — the quantity or condition has not been established.

A report may simplify these labels for its audience, but the underlying record should preserve the distinction.

3. Match the accounting boundary

The same physical movement can have different accounting treatment at different boundaries.

A UGT-to-OHT transfer is internal at a whole-society boundary. Counting it as new external supply would double-count water already inside the property.

At a tower or OHT boundary, however, that same transfer can legitimately be recorded as inflow to the selected tank or tower.

Every balance should therefore state:

• boundary type;

• boundary name;

• water service;

• period start and end;

• included storage assets;

• included external sources and withdrawals.

4. Align timestamps before comparing storage

Storage is a stock at a particular time. Supply and withdrawal are flows over a period.

Opening storage and closing storage should use clearly defined timestamps. Source and outflow records should cover the same period. If a tank reading is stale or communications are missing, the record should show that rather than silently using it as though it were current.

TownEve tank readings are reported every 30 seconds by hardware design. During connectivity loss, hardware can retain up to 150 readings and upload retained data after reconnection. At the fixed 30-second cadence, the full buffer represents up to approximately 75 minutes of retained readings when the hardware remains powered and all 150 entries are available. Historical continuity can therefore be preserved across shorter communication interruptions, while remote visibility resumes after connectivity returns.

5. Keep measured depth separate from derived volume

TownEve directly senses water depth. Level and stored volume are derived from the configured tank geometry. Tank-specific 0% and 100% reference levels define the usable range.

This distinction matters because a depth reading can be measured while the resulting usable volume is calculated. The calculation also depends on correct tank geometry and configuration.

6. Do not confuse net storage change with gross flows

When inflow and outflow occur simultaneously and neither is independently measured, tank-level change shows the net effect. It does not uniquely reveal gross inflow and gross outflow.

Under a suitable controlled boundary, one side can sometimes be constrained so that storage change supports a derived estimate of the other side. TownEve has tested manually controlled no-inflow and valve-isolation methods and continues to refine them. Observation duration is deployment-specific.

A controlled-window estimate should remain labelled as calculated or estimated as appropriate. It is not automatically representative daily consumption and is not automatic leak detection.

7. Record configuration and unit quality

A defensible dataset should identify:

• unit of measure;

• tank geometry/configuration version where relevant;

• 0% and 100% usable-water references;

• meter/sensor identity;

• reading timestamp;

• calibration or verification status where applicable;

• source document or operational record;

• person responsible for manual entries.

Unit conversions should be explicit. Litres, kilolitres, cubic metres and percentages should not be mixed without a stated conversion.

8. Treat reconciliation differences as investigation triggers

A water-balance difference can arise from many causes: timing mismatch, unrecorded supply, unrecorded withdrawal, measurement uncertainty, configuration error, internal transfer treatment, overflow, drain-down, maintenance use, or a physical loss.

Therefore:

Reconciliation difference = observed closing storage − expected closing storage

A non-zero result is a prompt to investigate. It is not, by itself, proof of leakage, theft, excess resident consumption or equipment failure.

9. Use a minimum data-quality check before decisions

Before using a water budget for an operational or committee decision, verify:

□ The boundary and water service are explicit.

□ Opening and closing storage use compatible timestamps.

□ Unknown values have not been replaced by zero.

□ External supply is separated from internal transfers.

□ Measured and calculated quantities are distinguishable.

□ Units are consistent.

□ Tank geometry and usable-water references are current where volume is derived.

□ Planned supply is not presented as received supply.

□ A residual is not presented as a diagnosed cause.

□ Material data gaps are disclosed beside the decision.

10. A simple confidence statement

Instead of inventing a universal numerical confidence score, a society can state whether the record is:

Decision-ready — material quantities and boundaries are sufficiently evidenced for the stated decision.

Usable with limitations — the record supports directional planning but contains material estimates or gaps.

Investigation-only — the data identifies an issue or question but is not sufficient for a quantitative conclusion.

Insufficient — material boundary, timestamp or quantity information is missing.

The classification should be accompanied by the reason. It should not hide the underlying evidence classes.

Frequently asked questions

Should a missing meter reading be entered as zero?

No. Zero is a known quantity. A missing or unavailable quantity should remain unknown, estimated or otherwise classified according to the evidence available.

Is tank volume directly measured by TownEve?

TownEve directly senses water depth. Stored level and volume are derived from measured depth and configured tank geometry.

Can tank-level data measure consumption?

It can support derived withdrawal or consumption estimates under suitable operating boundaries. If unknown inflow and outflow occur simultaneously, level change alone cannot uniquely separate them.

Does a water-balance discrepancy prove a leak?

No. It is an investigation trigger. The cause should be recorded only after supporting evidence establishes it.

Should planned water supply be included in actual supply?

No. Planned or expected supply belongs in forecasting until receipt is verified.

Underground and Overhead Tank Water Balance: Count Transfers Once

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:24:52 GMT

How do you reconcile a housing society's underground and overhead tank levels without double-counting water? Draw a separate accounting boundary around each tank or hydraulically connected group, record verified transfers between those boundaries, and count external municipal, borewell and tanker receipts only when they enter the society-wide boundary. Pumping water from an underground tank (UGT) into an overhead tank (OHT) changes where water is stored; it does not create a second water receipt.

Two different questions, two different boundaries

A tank-level dashboard shows storage at monitored points. A water balance asks which water volumes crossed a defined boundary during a stated period. For an individual UGT, incoming municipal or tanker water and outgoing pump transfers can change storage. For an individual OHT, pump transfers and resident draw can change storage. For a whole-society boundary containing both tanks, UGT-to-OHT pumping is an internal transfer. Its volume should cancel rather than inflate the society's total external supply.

Simple two-tank equations

Let ΔUGT be UGT closing stored volume minus opening stored volume for the same period. Let I be independently established external inflow into the UGT, T the independently established UGT-to-OHT transfer, and X any other independently established UGT outflow. Then ΔUGT = I - T - X, subject to measurement uncertainty and any additional paths.

Let ΔOHT be the corresponding OHT storage change, D the independently established OHT distribution outflow and Y any other OHT outflow. Then ΔOHT = T - D - Y, subject to uncertainty and other paths.

Adding the equations gives ΔUGT + ΔOHT = I - X - D - Y. The transfer T cancels. These equations are accounting identities under their stated boundaries; tank-level observations alone do not measure all the individual flows.

Worked example, hypothetical only

At the start of a matched interval, the UGT stores 80 kL and the OHT stores 20 kL. During the interval, an independently measured 30 kL of external water enters the UGT, an independently measured 25 kL is pumped to the OHT, and an independently measured 15 kL leaves the OHT for distribution. Assume no other paths and negligible measurement error for this illustration. Closing UGT volume is 80 + 30 - 25 = 85 kL. Closing OHT volume is 20 + 25 - 15 = 30 kL. Combined storage rises from 100 to 115 kL, a 15 kL increase. The whole-system balance is 30 kL external inflow minus 15 kL distribution. Counting the 25 kL pump transfer as additional external supply would incorrectly report 55 kL of intake. These figures are invented to illustrate the arithmetic, not actual TownEve customer measurements.

When transfer flow is not metered

If the pump transfer T is unmetered, two tank traces can show when the UGT fell and the OHT rose. They cannot uniquely determine the gross transfer while municipal inflow, resident draw or other flows occur simultaneously. Even equal-and-opposite storage movements do not prove the transfer volume if other paths were active. A verified pump-off or no-inflow observation can sometimes narrow an investigation, but it does not automatically provide a measured transfer or resident consumption figure. Log the unknown rather than forcing the equations to close by inventing a flow.

A practical boundary map

For each storage asset record: tank ID, service category, physical capacity, configured geometry, dead-water or minimum usable level, monitoring coverage, source connections, pump inlet and outlet, overflow, bypass, distribution lines and known isolation points. Identify which flows are inside the chosen reporting boundary and which cross it. Confirm physical connectivity with the facilities team. A diagram based only on labels in a dashboard can miss a shared manifold, bypass or an independent compartment.

Service categories and compartments matter

Drinking, domestic and treated/recycled water should be reported separately when their uses, treatment and distribution networks differ. Do not treat a rise in a treated-water tank as a replenishment of drinking-water reserve. A divided UGT may contain hydraulically independent chambers; one sensor cannot be assumed to represent all compartments. Connected chambers may equalize, but the actual connections, valve positions and sensor placement require site validation. If an OHT serves only one tower or service, do not count inaccessible storage elsewhere as available to it.

Storage volume versus usable volume

Use configured tank dimensions and the appropriate level-to-volume geometry to estimate stored volume. A displayed usable percentage can exclude configured dead-water height, so confirm whether the operational zero already excludes unavailable storage before subtracting it again. Volume conversion depends on correct tank geometry, level readings and installation assumptions. This is a stored-volume calculation, not a direct flow-meter reading or a certified water-quality measurement.

Monthly reconciliation table

Use identical start and end times for the same balance. Keep separately identified meter totals, supplier-declared receipts and estimated volumes rather than silently combining them as measured values. A pump log may confirm operation timing without measuring transferred kilolitres.

Six checks before interpreting a mismatch

1. Are the start and end timestamps aligned across UGT, OHT and source meters?

2. Were tank dimensions, dead-water configuration, sensor freshness and units verified?

3. Is the transfer route known, and is transfer volume independently measured or only assumed?

4. Were external receipts counted once, and were internal transfers excluded from whole-society intake?

5. Are all relevant overflow, bypass, maintenance and distribution paths represented?

6. Could simultaneous inflow and outflow explain why the observed net level movement differs from an assumed gross flow?

A remaining discrepancy is an investigation item, not automatic evidence of a leak or excessive resident consumption.

What TownEve contributes today

TownEve currently supports contactless ultrasonic UGT and OHT monitoring, historical levels, configured level-based email alerts, role-based visibility, telemetry-freshness monitoring and stored-volume calculations based on configured tank geometry. This lets operators see storage at multiple points, reconcile changes across defined boundaries and investigate transfer timing. Pump-transfer volume, incoming-source flow, resident demand and physical leakage use the corresponding measurement or investigation evidence. Direct pump-state monitoring and remote pump operation are in development and testing. A sensor-assisted controlled valve-isolation investigation has been tested and continues to be refined; automatic flow measurement is a separate capability.

Frequently asked questions

If the UGT loses 10 kL while the OHT gains 10 kL, did the pump move exactly 10 kL? Not necessarily. Simultaneous external inflow or distribution draw can change either tank's net storage.

Should a tanker unloaded into a UGT be counted again when that water reaches an OHT? No. The receipt is external once; pumping is an internal transfer.

Can two level sensors replace a flow meter? They provide storage observations, but cannot generally separate concurrent inflows and outflows without additional verified conditions or instrumentation.

Does the OHT's percentage represent the whole society's reserve? No. It represents a configured storage boundary and may exclude other tanks or inaccessible supply.

What if the UGT has multiple chambers? Validate hydraulic connections and sensor coverage; report independently operating compartments separately.

Related resources and CTA

Request a TownEve water-visibility assessment to map tank boundaries, monitoring coverage and the additional measurements needed for defensible flow reconciliation.

Monthly Water Budget Report Template for Housing Society Committees

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:24:23 GMT

A monthly water budget report should tell a housing society committee how much water was verifiably received, what is known about storage and use, which services are at risk, what the society spent, and which numbers remain estimates. The report should use the same definitions and boundaries as the society's water budgeting method. It should support decisions without presenting tank-level movement as a direct measurement of all incoming water or consumption.

Copy-and-fill committee report

Executive summary

Supply received: [verified volume and units, or “not independently measured”]. Current storage: [measured level / estimated volume, tank and timestamp]. Reliability: [verified interruptions and affected services]. Cost: [actual invoiced amount, accrual or estimate, clearly labeled]. Main risk: [evidence-supported statement]. Decision requested: [specific action, owner, cost and deadline]. Material unknowns: [missing meters, stale readings, supplier confirmation, etc.].

1. Source ledger

Use one line per independently evidenced delivery or source-period. Fields: source (municipal, borewell, tanker or other); water category; source record ID; receipt date/time; volume; unit; measurement method; confidence; supporting document; verified by. Separate a booked tanker from an arrived tanker. Where an incoming meter is absent, enter “unmeasured,” not a number inferred solely from a tank-level increase. If a transfer moves water from an underground tank to an overhead tank, record it as an internal transfer, not a second external supply receipt. Do not mix drinking, domestic and treated/recycled water as if interchangeable.

2. Storage snapshot

For each tank record: tank ID; water category; timestamp; sensor reading and freshness; usable capacity if validated; estimated stored volume where tank geometry is configured; operating reserve; current restriction or maintenance; source of verification. A tank reading is a point-in-time snapshot. Summing volumes across connected tanks requires avoiding duplicate reporting of transferred water as new supply. Flag readings from different timestamps and inaccessible tanks.

3. Demand and reconciliation

If independently metered demand exists, record the meter, coverage and period. Otherwise describe the net storage change and known supply/transfer records without claiming to know total consumption. The physical accounting relationship for a defined system boundary is: closing storage minus opening storage = external inflow minus external outflow, adjusted for known internal boundary transfers and measurement error. A level fall while supply continues does not reveal consumption alone. Distinguish a confirmed no-inflow observation from an assumed pump-off period. A short controlled observation is not automatically representative of the month.

Illustrative reconciliation only, not Park Astra or another customer result: a hypothetical tank starts with 100 kilolitres, receives 40 kilolitres of independently metered inflow and ends with 90 kilolitres. With no other transfers, measured losses or errors, the implied outflow is 50 kilolitres (100 + 40 - 90). If the 40-kilolitre inflow is not independently known, the same 10-kilolitre net storage decline does not establish 50 kilolitres of outflow. Record uncertainty instead of filling a balancing difference with a guessed leak volume.

4. Service and operational reliability

Record the number of verified interruption incidents, affected towers and water categories, opening and restoration times, physical checks, notices issued, and unresolved causes. Distinguish a pump-trip finding, a supply restriction and unusually high resident demand. A graph can direct investigation, but physical checks establish equipment or pipe defects. Do not assign a cause to residents based on tenancy or an unadjusted depletion trend.

5. Financial report

Separate water purchases by source; transport; energy where attributable; maintenance; sensor/monitoring subscription; emergency costs; and one-off capital works. Show actual paid, invoiced but unpaid, and estimated costs separately. Cost per kilolitre = comparable total cost divided by verified volume for the same boundary and period; if volume is unavailable, mark this KPI “not available.” Avoid counting the same invoice in both purchase and emergency totals. Report changes from the prior period only when the periods, service mix and measurement methods are comparable.

6. Risk register and actions

For each issue state: evidence; affected service; likelihood or severity as assessed by the committee; immediate mitigation; owner; due date; approval needed; next review. Examples of risk categories are unreliable incoming supply, inadequate refill, stale telemetry, an unverified tanker receipt and missing flow measurement. Do not state that every abnormal trend indicates a leak.

7. Resident-facing summary

A short committee-approved version may state: “During [period], we recorded [verified service facts]. Current tank readings show [tank-specific snapshot and timestamp]. [Supply volumes or consumption] remain [measured / estimated / unavailable]. The facilities team is [verified action]. Our next update is [time/channel].” Exclude private resident information, speculative causes and unverified restoration promises.

Committee dashboard: six useful indicators

Verified external water received: measured receipts only, with source and units.

Storage status: level or estimated volume by tank, with timestamp and freshness.

Supply reliability: verified interruption count and duration by service.

Source cost: actual comparable cost, with exclusions and accounting period.

Data completeness: proportion of required records actually available, where a documented denominator exists.

Open decisions: owner, due date, approval and evidence needed.

Do not publish a numerical KPI merely because a dashboard can display a calculated value. A blank or “not independently measured” entry is more informative than false precision.

Reporting cadence and sign-off

Facilities should close the operational log after the reporting period, reconcile supplier and invoice evidence, flag gaps and send a provisional report for committee review. The committee approves any public summary and records its decisions. A correction should preserve the earlier version and identify the revised figure, reason and approver. There is no universal monthly statutory reporting format asserted here; adapt this example to applicable local rules and society policy.

TownEve capability boundary

Current TownEve production provides contactless ultrasonic overhead and underground tank monitoring, live and historical levels, configured email alerts, role-based visibility and tank-specific stored-volume calculations derived from measured depth and configured geometry. Tank-specific 0% and 100% reference levels define the usable range, and telemetry freshness can be monitored. Direct pump-state monitoring, pump control, automatic leak detection and automated valve operation are not released capabilities. TownEve has tested its sensor-assisted manual branch-isolation investigation and continues to refine it; it is not an automatic consumption report.

FAQ

Can the committee calculate daily per-person consumption from tank levels alone? Not reliably when inflow and outflow overlap and source records are missing. Use independently measured flow or a carefully qualified estimation method with known operating conditions.

Should we total all tank-level increases as supply? No. Internal transfers can cause double-counting and level changes are net of simultaneous outflow.

How do we report an uncertain number? State the observation, source, assumption, coverage and confidence; use “not measured” where necessary.

Is a lower storage level always a shortage? No. Interpret it against refill schedules, usable reserve, service category and verified demand.

Can a monthly report diagnose a pipe restriction? It may highlight unequal refill trends, but a physical investigation is needed to identify the actual restriction.

Discuss water monitoring for your society

Request a TownEve water-visibility assessment to understand which storage observations your society can monitor and which source or consumption measurements require additional instrumentation.

Water Management SOP for Housing Societies

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:23:49 GMT

A housing society water-management standard operating procedure (SOP) should define who verifies supply and storage, which measurements are trustworthy, when to escalate, who approves operational changes and how residents are informed. It should operate within the society's broader water budgeting framework. It is a locally adapted governance document, not a substitute for qualified plumbing, electrical, water-quality or fire-safety procedures.

Quick-start SOP

1. Maintain a current map of water sources, underground tanks, overhead tanks, pumps, distribution zones and the responsible operator for each.

2. Record a time-stamped daily storage and supply snapshot. Mark missing, stale and physically unverified readings.

3. Compare changes against the society’s own operating baseline and confirmed delivery schedules. Do not equate net tank-level change with independent inflow or consumption.

4. Assign an owner to investigate unusual patterns, check equipment and confirm affected services.

5. Apply only approved, site-specific operating changes through authorized personnel.

6. Communicate verified resident impact and the next update time.

7. Log closure evidence and review recurring problems.

Purpose, scope and ownership

This example applies to drinking, domestic and recycled-water storage where separately present. Keep their records, distribution rules and quality requirements distinct. The committee approves policy, budgets and exceptional service decisions. The facility manager owns the daily operating record and directs authorized staff. Technical contractors inspect and repair equipment within their qualifications. A named communications owner and backup issue resident notices. Identify the person who can approve alternative water procurement and the person authorized to make emergency decisions under the society’s governing rules.

Document-control fields to complete before adoption

Society and revision: [name / version]. Effective date: [approved date]. Approved by: [committee authority]. Facility lead and backup: [names and contacts]. Applicable water systems: [inventory]. Local official directions checked on: [date / source]. Review trigger: [periodic review or material system change]. Emergency contacts and after-hours coverage: [verified details].

Daily operating record

For each source or tank, capture tank ID, water category, observation time, measured level, estimated volume if configured and valid, sensor freshness, physical inspection if performed, confirmed incoming delivery, known pump or valve action, operator and follow-up. A separate event log records complaints, supplier updates, tanker receipts, repairs and resident notices. Do not fill missing readings by interpolation and label estimates as estimates.

Measurement and decision rules

TownEve currently provides contactless ultrasonic tank-level monitoring, historical level visibility, configured email alerts and tank-specific level-to-volume conversion. Sensors report readings every 30 seconds by hardware design. A reading timestamp and communications freshness matter before operational use. TownEve directly senses water depth and derives level and stored volume from configured tank geometry; tank-specific 0% and 100% reference levels define the usable range. This is not direct pipe-flow measurement.

The accounting identity for a defined observation period is: change in stored volume = inflow minus outflow, adjusted for any other known transfers. When both inflow and outflow are unknown, a falling or rising level does not separately quantify either. A period with confirmed no inflow may support an estimate of outflow from storage decline, provided other paths and measurement limitations are considered. Do not extrapolate a short observation to a representative daily total without an appropriate sampling basis. Direct pump-state monitoring, pump control, automatic leak diagnosis and automatic valve operation remain development or roadmap layers beyond the current monitoring deployment.

Site-specific trigger register

Rather than copying universal percentages, the facility manager and committee should approve trigger levels for each tank, considering usable storage, demand variation, refill lead time, essential reserve and the consequences of an interruption. Record the threshold, observation source, required confirmation, primary responder, backup, escalation deadline and approved action. A low-level email alert prompts investigation; it is not a definitive cause diagnosis or an instruction to start a pump automatically. A stale-telemetry alert requires communication-path and device checks, plus physical verification when necessary.

Routine operating sequence

At shift handover, check monitoring freshness, unresolved alerts and the latest verified supply information. During the shift, compare the latest levels with historical patterns, planned transfers and the source delivery log. If a tank changes unexpectedly, confirm the reading and affected service, review other tanks for shared patterns and ask the authorized technician to inspect relevant supply equipment. Record the outcome before changing operating assumptions. At handover, pass on open issues, owner, next action and next review time.

Shortage response and escalation

When supply risk is suspected, the facilities lead first confirms the affected water category, tanks and freshness of readings. The team checks known source delivery, transfer equipment and physical conditions. The designated decision-maker then selects any permitted mitigation under the site’s existing safety and service procedures. Inform residents using confirmed facts and explicitly unknown causes or restoration times. Keep a next-update commitment. After service returns, verify restoration physically where appropriate, close the incident and document the root cause only to the extent supported by inspection.

Alternative supply and water budgeting

Maintain a rolling budget that separates confirmed source deliveries, documented tanker receipts, estimated stored volume and measured flow where independent meters exist. Use the society’s actual unit conversions and tank geometry. A purchase order is not evidence that a tanker arrived, and a tank-level increase alone does not identify which source supplied it. Forecast scenarios should state assumptions about delivery, demand and available usable storage; they are not guarantees. The committee should approve procurement authority, supplier checks and record retention before an incident.

Controlled investigations and safety

Qualified personnel may sometimes compare storage trends during a carefully planned operating window, subject to site safety and service constraints. Do not recommend ad hoc isolation of drinking-water, essential or fire-safety lines. TownEve has tested a sensor-assisted branch-isolation method for abnormal withdrawal and continues to refine it: authorized staff manually isolate branches during controlled no-inflow periods and compare depletion trends. Observation duration is deployment-specific. A timer-guided app workflow and solenoid valves are possible future stages, not current features. Abnormal withdrawal does not itself establish a leak.

Resident communications

Use a verified observation, named affected service, approved action, uncertainty statement, responsible contact and next update time. Do not attribute a shortage to residents, municipal authorities or a pump without corroboration. If a claim concerns official restrictions, water safety or statutory requirements, check the applicable current primary source before repeating it. The designated communication owner should prepare resident messages using the verified service facts and the next update time.

Weekly and monthly review

Weekly: reconcile missing readings, unresolved alerts, supplier records, equipment faults and open resident issues. Monthly: review source reliability, storage trends, verified purchase and operating costs, trigger effectiveness and unresolved measurement gaps. The committee should distinguish observed facts from estimates and proposed improvements. Record actions, owner, due date and approval. Update the SOP after a significant system change or incident.

Example incident log fields

Incident ID; opening time; affected water category and tanks; observed trend and reading freshness; physical verification; confirmed supply status; competing explanations; actions and approver; resident notice times; restoration check; final finding; unresolved uncertainty; closure owner. Keep personal resident information out of public case studies without permission.

Frequently asked questions

Is this SOP a statutory standard? No. It is a configurable operational example; applicable local rules and site-approved safety procedures govern.

Does tank monitoring replace physical inspection? No. It improves visibility and provides history, while staff verify causes and execute interventions.

Can a tank graph prove excess consumption? No. Unknown simultaneous inflow and outflow cannot be separated from level alone.

What should happen if data stops arriving? Investigate telemetry freshness, connectivity and device conditions and use an appropriate physical check.

Who sends alerts to residents? TownEve’s current configured email alerts are operational inputs. The society’s designated communications owner approves resident notices.

Discuss water monitoring for your society

Request a TownEve water-visibility assessment to map the tanks, monitoring requirements and response responsibilities at your society.

Water Consumption per Capita in Housing Societies: Calculate LPCD

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:23:16 GMT

Water Consumption per Capita in Housing Societies: How to Calculate LPCD

A housing society’s water consumption per capita is the volume of water used over a defined period divided by the number of people served and the number of days. The result is usually expressed as litres per capita per day (LPCD). It is useful for comparing like-for-like periods, identifying unexplained changes and planning supply. But it is only as reliable as the water-volume boundary, occupancy count and measurement period behind it.

THE FORMULA

Measured LPCD = verified water volume attributable to the defined population and services (litres) ÷ (people served × days).

If a society records 600,000 litres of attributable withdrawal over four days and 1,000 residents were served throughout, the observed average is 150 LPCD. That is an illustrative calculation, not a standard, target or statement about typical Indian housing-society use.

If occupancy changes during the period, use person-days rather than a single headcount: LPCD = attributable litres ÷ sum of daily people served. For example, 600,000 litres across 4,000 person-days is 150 LPCD. Report whether the occupancy count is verified, estimated or assumed.

WHAT EXACTLY COUNTS AS CONSUMPTION?

Define the accounting boundary before calculating. Water delivered to domestic flat supply may be an appropriate numerator for domestic-distribution LPCD if the resident population is the denominator. Do not silently mix domestic, drinking, recycled/STP, landscaping, construction, commercial, fire-system testing or common-area use into one residential figure. If a society wants an all-services figure, label it explicitly and explain which users and services are covered. Water supplied to a tank is not necessarily the same as water consumed by residents during that period: storage can rise or fall, water can be transferred internally, and losses can occur.

A source ledger should distinguish municipal, tanker and borewell deliveries from water withdrawn for use. Pumping from an underground tank to an overhead tank is an internal transfer, not new water. Do not add the same water twice merely because it appears at two measurement points. A supplier invoice, tanker capacity or design assumption is not equivalent to a verified delivered volume.

A PRACTICAL CALCULATION WORKFLOW

1. Choose a reporting period, preferably multiple representative days, and identify which services and population are included.

2. Verify occupancy for the same period. Use daily person-count estimates if occupancy varies; record the method.

3. Collect meter readings at the chosen withdrawal boundary, or use a documented and validated water-balance estimate. Check units, timestamps, missing data, meter resets and abnormal events.

4. Reconcile opening storage + external inflow − external outflow ± documented adjustments = closing storage. Internal transfers must cancel when both ends are inside the society-wide boundary.

5. Subtract separately measured, out-of-scope uses only when there is evidence to support the subtraction. Otherwise label the result as a broader or uncertain estimate.

6. Divide attributable litres by person-days. Retain the raw numerator, denominator, time window and exclusions with the reported LPCD.

7. Compare against comparable prior periods, rather than assuming a difference is a leak.

ILLUSTRATIVE COMPARISON

Period A: 1,000 residents × 7 days = 7,000 person-days; attributable withdrawal 980,000 litres; measured average 140 LPCD.

Period B: 900 residents × 7 days = 6,300 person-days; attributable withdrawal 945,000 litres; measured average 150 LPCD.

Total water withdrawal fell, but observed per-person withdrawal increased. Occupancy normalization exposes a change that a simple total-volume chart could hide. The figures are hypothetical.

MEASURED, ESTIMATED AND ASSUMED LPCD ARE DIFFERENT

Measured LPCD uses a verified flow or withdrawal record and a defensible person-day count. Estimated LPCD uses an explicitly documented indirect volume method or uncertain occupancy. Assumed LPCD uses a chosen planning input, often in a demand calculator, without claiming to observe actual usage. A planning-demand calculation can use occupancy × assumed LPCD; this article instead explains how to calculate an observed figure and assess its limitations.

Where incoming and outgoing flows occur simultaneously, a tank-level change shows their net difference, not each flow independently. With verified no-inflow conditions, tank-specific level-to-volume conversion can instead estimate withdrawal during that controlled interval. Such an interval is not automatically representative of an entire day. Confirm geometry, usable reference, timestamps, sensor freshness and any additional outlets.

HOW TO INVESTIGATE AN UNUSUAL LPCD RESULT

First check occupancy, service mix, data freshness, meter boundaries, changes in replenishment and storage, maintenance draining and known operational events. Compare similar days and seasons. An elevated average is a signal for investigation, not proof of leakage or excessive resident use. A high result can arise from genuine demand, a running fixture, common-area withdrawals, inaccurate records or losses.

TownEve has tested a sensor-assisted manual valve-isolation method for investigating abnormal overhead-tank withdrawal and continues to refine it. With incoming replenishment stopped, its 30-second level readings can support controlled depletion-rate comparisons. Authorized facilities personnel can isolate independently operable distribution branches one at a time, compare suitable observation windows and repeat at smaller subdivisions. At Park Astra, the described branching arrangement can support a narrowing sequence from a 68-flat tower to a 17-flat series and then a smaller group of flats. This is not a validated guarantee of diagnostic precision, a released automated leak detector or a substitute for representative society-wide LPCD measurement. Observation duration is deployment-specific. A timer-guided app workflow is proposed to assist manual SOPs; solenoid-valve operation is a possible later stage. Valve operation requires safe procedures and coordination with affected residents. Elevated withdrawal may be legitimate use rather than a leak.

WHAT TOWNEVE DOES TODAY

TownEve provides contactless ultrasonic monitoring for suitable overhead and underground tanks, historical level visibility, configured alerts and tank-specific level-to-volume conversion using recorded dimensions and geometry. Its sensors transmit readings every 30 seconds. These capabilities establish stored-volume trends and support carefully controlled observations. Incoming and outgoing source quantities, occupancy and physical leak confirmation use the corresponding records, instrumentation or investigation evidence. Direct pump-state monitoring and pump control are in development. App-guided isolation and solenoid actuation are proposed future stages.

FAQ

What is LPCD?

Litres per capita per day: volume attributable to a defined group and set of water services, divided by person-days.

Can I calculate LPCD from the number of flats?

Only as an assumption-driven estimate if residents per occupied flat and a chosen LPCD input are supplied. Flat count alone is not measured consumption.

Can tank levels alone measure daily household consumption?

Not generally when unknown inflow and outflow overlap. A verified no-inflow interval can support a withdrawal estimate, but representative daily consumption requires suitable coverage and boundary reconciliation.

Is higher LPCD evidence of a leak?

No. Check occupancy, services, measurement quality and legitimate demand before investigating losses.

Does a short valve-isolation test establish daily LPCD?

No. Controlled observation windows can help narrow abnormal withdrawal, but a single short test is not a substitute for a representative daily average. The suitable observation duration is deployment-specific.

What is the difference between planning demand and observed LPCD?

Planning demand estimates future requirements from occupancy and an assumed LPCD. Observed LPCD is calculated and interpreted from water records and person-days, with the evidence quality stated clearly.

Incoming Water Flow Meter Guide for Housing Societies

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:22:48 GMT

QUICK ANSWER

An incoming water meter measures volume passing a defined pipe location. For a housing society, the useful starting point is to map each external source—municipal, borewell and tanker—and determine where an appropriate meter can independently record water entering the chosen accounting boundary.

Meter technology and placement depend on the pipe, flow conditions, water characteristics, site constraints and applicable authority requirements. A meter installed at the wrong boundary can produce a precise number that answers the wrong question.

A tank-level sensor answers a different question: how much water is stored at a point in time. Both measurements can contribute to a stronger water balance, but neither automatically replaces the other.

THE FIRST DECISION IS THE ACCOUNTING BOUNDARY

Draw the physical route from each external source to the relevant underground or overhead tank. Mark branches, bypasses, treatment lines, recirculation paths, overflow paths and internal transfers.

A meter on the municipal inlet measures volume passing that inlet. A meter downstream of a manifold carrying municipal and borewell supply may measure combined flow and cannot identify each source's contribution.

A meter on the pump line from underground to overhead storage measures an internal transfer. It should not be counted as new external supply in a property-wide water balance.

Where drinking, domestic and treated recycled-water services are physically distinct, establish separate accounting boundaries. Do not assume the same meter or volume record covers all services.

WHAT DOES THE SOCIETY NEED TO KNOW?

Different decisions call for different measurement points:

- Municipal receipt: measure the authorized incoming municipal line at a defined boundary.

- Borewell contribution: measure the relevant groundwater delivery line, while separately verifying applicable permissions and reporting obligations.

- Tanker receipt: measure the actual delivery path when feasible, or use another documented verification method.

- Pumped transfer: measure the line moving water from one storage stage to another, if transfer volume is needed.

- Distribution withdrawal: measure the relevant outlet or zone to understand water leaving that boundary.

One meter cannot identify every source and destination in a branched network. A metering plan should match the questions being asked.

METER OPTIONS: A NON-PRESCRIPTIVE OVERVIEW

Common water-flow measurement approaches include mechanical meters, electromagnetic meters and ultrasonic technologies. Their suitability depends on the application; no type is universally appropriate.

Mechanical meters may be familiar in water distribution, but installation conditions, wear, debris, maintenance and operating range matter.

Electromagnetic meters can be suitable for appropriate conductive liquids and installation conditions; they are not a universal solution for every fluid, pipe or site.

Ultrasonic flow measurement may use inline or externally mounted arrangements depending on the product and site. Its applicability and performance depend on the actual technology, pipe and flow conditions. Do not assume that a contactless ultrasonic tank-level sensor is the same instrument as an ultrasonic pipe-flow meter.

The engineering decision must consider the manufacturer's documented operating range, accuracy conditions, pipe size and material, straight-run or other installation requirements, power, data interface, environmental protection, maintenance and lifecycle cost.

The purpose of this article is to define a good procurement question, not to specify a model without site data.

INSTALLATION AND OWNERSHIP MATTER

Before any installation, determine who owns the existing meter and pipe segment and whether permission is required to inspect, modify or instrument it.

Do not alter, bypass, break a seal on or interfere with a utility-owned meter. Any work on a supply line, pressure system or electrical installation should be planned and performed by authorized qualified personnel.

Check the site's applicable utility and local authority requirements, including whether a proposed meter is for internal operational monitoring or an officially recognized billing or compliance measurement.

An independently installed operational meter is not automatically a substitute for a statutory or utility-approved meter.

PLANNING THE MEASUREMENT POINT

An engineer should verify:

1. Pipe route and all branches before and after the proposed point.

2. Whether the pipe normally runs full, and whether air, intermittent flow or reverse flow is relevant.

3. Expected minimum, typical and maximum flow, including short supply windows.

4. Pipe size, material, pressure and accessible installation space.

5. Water characteristics, debris, treatment and service suitability.

6. Straight-run, orientation, grounding or other manufacturer-specific conditions where applicable.

7. Power, telemetry and local data-retention needs.

8. Safe isolation, maintenance access and approval requirements.

9. The exact volume the reading is intended to represent.

This is a site-survey checklist. It does not override a manufacturer's installation instructions or a competent engineer's assessment.

INTERMITTENT SUPPLY: CAPTURE VOLUME AND TIME

A supply window is not a volume measurement.

A cumulative meter can support the calculation:

Received volume = closing cumulative reading − opening cumulative reading.

If an appropriate meter reads 2,410 kL before a supply window and 2,438 kL after it, the difference is 28 kL, assuming valid units, no rollover or reset, and that the boundary corresponds to the intended supply.

This is illustrative arithmetic, not a TownEve installation result.

Record both timestamps. A two-hour supply window could deliver different volumes on different days; duration alone does not establish litres received.

Where supply is intermittent, consider whether the chosen instrument and installation can reliably capture the site's actual flow conditions. The manufacturer and installer must establish this, not a generic article.

A SOURCE-EVENT RECORD WORTH KEEPING

Retain the raw readings alongside the calculated difference. Record any reset, rollover, suspected fault or missed observation.

Do not treat a blank meter reading as zero supply. If a reading is unavailable, show the gap.

If several meters cover mutually exclusive source lines, their verified volumes may be summed for a property-wide external inflow total. If one meter sits downstream of another on the same path, summing both can double count the same water.

HOW TO RECONCILE A METER WITH TANK LEVELS

For a receiving tank over a defined period:

Closing stored volume = opening stored volume + metered incoming water + other incoming water − withdrawals and transfers ± documented adjustments.

Example: an underground tank opens with 60 kL. A verified municipal inlet meter records 35 kL and a separately verified tanker delivery adds 10 kL. A transfer to overhead storage removes 25 kL. With no other flows, the expected closing inventory is 80 kL.

If the observed closing volume is 77 kL, the 3 kL discrepancy needs investigation. It is not automatically a 3 kL leak.

Check timestamps, units, geometry, sensor configuration, meter status, bypasses, unrecorded withdrawals and measurement uncertainty before attributing a cause.

For the property-wide boundary including both underground and overhead tanks, the 25 kL transfer cancels internally; it is not an external supply input.

MEASUREMENT QUALITY: WHAT A NUMBER DOES NOT PROVE

A displayed reading is not proof of a valid measurement.

Record the manufacturer's stated accuracy conditions and the site's verification or calibration process. Do not transfer a laboratory accuracy specification to every field installation without qualification.

Investigate unusual results by checking installation, operating range, time synchronization, missing pulses or telemetry, power interruptions and data processing.

Distinguish measured, estimated, planned and unknown volumes. A tanker invoice, expected municipal window or pump runtime is not automatically a measured incoming volume.

Use consistent units: one cubic metre equals one kilolitre, or 1,000 litres.

A SENSOR-BASED ALTERNATIVE: ESTIMATING RAW-TANK INCOMING FLOW THROUGH CONTROLLED WTP OBSERVATION

In a suitable raw-water → water treatment plant (WTP) → domestic-water tank configuration, tank-level sensors can provide a viable, lower-instrumentation alternative to a dedicated incoming flow meter for estimating incoming volume. This is a conditional estimation method, not a universal substitute for a flow meter or a claim that TownEve currently ships a fully automated incoming-flow measurement feature.

The relevant arrangement is: external supply enters the raw tank; the raw tank feeds the WTP; treated water enters the domestic tank; a separate distribution pump sends domestic water onward. Backwash may also withdraw water from the raw tank. Tank-level sensors observe the raw and domestic tank volumes.

FIRST CALIBRATE A CONTROLLED WTP INTERVAL

Choose a documented interval when the domestic distribution pump is off, no external source is filling the raw tank, and backwash is not occurring. Keep the WTP operating in its normal known configuration. Confirm that no other inflow or outflow affects either tank during the observation.

Over that interval, measure the raw tank's decrease and the domestic tank's increase using synchronized timestamps and valid tank-specific level-to-volume conversions.

Raw tank volume lost = estimated raw-water withdrawal into the WTP, if backwash and all other raw-tank flows are absent.

Domestic tank volume gained = estimated treated-water output, if domestic withdrawal and all other domestic-tank flows are absent.

These two quantities need not be equal: treatment losses, reject water, internal storage or other process behavior can account for differences. Calibrate the RAW-TANK WITHDRAWAL rate for the incoming-flow correction; do not automatically use the domestic-tank gain as an identical substitute. Comparing the two observations is valuable for understanding the process and detecting an unexplained mismatch.

Illustration: during a 30-minute controlled interval, the raw tank falls by 6 kL and the domestic tank rises by 5.5 kL. Under the stated conditions, the estimated raw-tank withdrawal rate is 12 kL/hour and treated-water output is 11 kL/hour. The 0.5 kL difference over the interval needs an operational explanation; it must not be silently discarded.

THEN ESTIMATE AN INCOMING-SUPPLY EVENT

For an observation window with one identifiable incoming source, known WTP operation and no unaccounted backwash:

Estimated incoming volume = change in raw-tank stored volume + estimated WTP withdrawal from the raw tank.

Use signed change: closing raw-tank volume minus opening raw-tank volume. For example, if the raw tank rises by 8 kL while the calibrated WTP withdrawal over that window is estimated at 12 kL, estimated incoming supply is 20 kL.

If backwash draws from the raw tank during the event, add its independently known or estimated withdrawal to the right-hand side, or preferably control the operation so that the measurement window excludes backwash:

Estimated incoming volume = raw-tank storage change + WTP raw-water withdrawal + other known raw-tank withdrawals.

This equation assumes no unaccounted raw-tank flows. It is a water-balance estimate, not a direct flow-meter reading.

WHEN THE METHOD WORKS, AND WHEN IT FAILS

The method is particularly useful where staff can create repeatable observation windows: hold domestic distribution pumping off for calibration, avoid or separately account for backwash, and observe the WTP over a known period. Only authorized personnel should operate pumps and treatment equipment, with service and safety constraints respected.

If municipal supply and a tanker fill the raw tank simultaneously, raw-tank sensors cannot attribute the combined incoming estimate to each source. Isolate source windows or use independent source measurements. If the source identity cannot be established, report combined inflow rather than claiming tanker-specific or municipal-specific receipt.

If WTP throughput changes with operating conditions, treating a past rate as a permanent constant adds error. Recalibrate at representative operating states and periodically; record the date, conditions and uncertainty. Do not claim a fixed accuracy percentage without site validation.

Backwash, other raw-tank withdrawals, unobserved pump activity, invalid geometry, stale or unsynchronized readings and a changed treatment configuration can invalidate an interval. Exclude it or explicitly model the additional flow. Controlling these operations reduces uncertainty; it does not prove that uncertainty is zero.

If incoming water is mixed from multiple sources during the same window, this method can at most estimate their combined volume under otherwise valid assumptions. A dedicated meter remains useful when source-specific independently measured volume, continuous measurement or a particular regulatory or contractual standard is required.

WHAT TOWNEVE CONTRIBUTES

TownEve's existing tank-level sensors and configured geometry provide the raw and domestic storage histories needed for this method. The controlled operating procedure, calibration, flow isolation, calculations and verification are additional site-specific work; the article does not claim that an automatic virtual-flow feature has been released.

This is a practical sensor-based measurement approach to evaluate and validate at suitable installations, alongside conventional flow-meter options. It may reduce the need for additional instrumentation where the site can maintain the required conditions. Any cost comparison must use actual site quotations and operating effort, not a guaranteed saving.

WHAT IF A FLOW METER CANNOT BE INSTALLED YET?

Begin with a mapped source ledger, verified tank configuration and reliable level-history records.

Under a documented no-other-flow interval, the tank's usable-volume change can estimate received quantity. Where a calibrated WTP withdrawal is independently estimated under controlled operating conditions, raw-tank storage change plus that withdrawal can instead estimate incoming volume even while the WTP runs. State the assumptions and uncertainty.

When a tank is simultaneously filling and draining, net level change alone cannot separate the unknown inflow and outflow. A controlled, calibrated estimate of the known outflow can support an incoming-volume estimate, but cannot distinguish simultaneous incoming sources.

Avoid extrapolating from a quiet interval to every operating day. A good first-phase record can explicitly mark incoming volume unknown while still improving storage visibility.

FLOW DATA AND TANK DATA ANSWER DIFFERENT QUESTIONS

Incoming flow: How much water crossed a source boundary during a period?

Stored volume: How much usable water was in the configured tank at a given time?

Outgoing flow: How much water crossed a withdrawal boundary?

Pump-state data: Was a pump in a particular independently measured or reported state?

These are distinct measurements. Inferring one from another requires explicit assumptions and may be impossible under simultaneous unknown flows.

Combining independent measurements can make water budgeting more useful, but it does not automatically establish the cause of every discrepancy.

HOW TOWNEVE FITS TODAY

TownEve currently provides contactless ultrasonic level monitoring for suitable underground and overhead tanks, current and historical level visibility, configured email alerts, telemetry-freshness monitoring and tank-specific level-to-volume calculations using configured dimensions and dead-water height.

The configured geometry supports accurate usable-volume calculations across tank sizes and shapes when the inputs and level readings are valid.

TownEve's app can integrate flow-meter data, while flow-meter hardware has not yet been deployed as part of the current installation base. Existing tank-level measurements can also support the controlled, calibrated raw-tank/WTP incoming-flow estimation method described above at suitable sites. This method is an operating analysis technique rather than a released automatic virtual-flow feature.

Direct pump-state monitoring is in development, remote pump operation is in development and testing, and tanker-management workflows are in development. These are development layers beyond the current monitoring deployment.

A practical phased architecture is to establish reliable tank inventory first, then add independently measured source and withdrawal data where the site's operating and business case justifies it.

FAQ

Is a bulk water meter the same as a tank-level sensor?

No. A meter measures water passing a defined point; a tank-level sensor observes stored level, which can be converted to volume using appropriate tank configuration.

Where should a society install a municipal incoming meter?

At a technically suitable and authorized point that represents the intended municipal supply boundary. A site survey and applicable utility requirements determine the actual location.

Can one meter separate municipal and borewell water in a shared line?

Not if the flows are already combined and there is no independent source measurement or valid isolation method.

Can tank-level monitoring replace an incoming meter?

It can support qualified estimates under constrained conditions, but simultaneous unknown inflow and outflow prevent independent source-volume measurement from level change alone.

Does pump runtime equal pumped water volume?

No. Runtime can support a documented estimate only when a relevant flow relationship is established and verified.

Can a meter prove a tanker delivered its nominal capacity?

A suitable meter at the correct receiving boundary can provide volume evidence, subject to installation and measurement validity. Nominal vehicle capacity alone does not.

What should the committee ask a vendor?

Ask which exact volume is measured, the operating range and installation conditions, how readings are verified, who owns the meter and data, what maintenance is required, and whether the measurement is for internal operations or officially recognized use.

Is TownEve's current ultrasonic tank sensor an ultrasonic pipe-flow meter?

No. These are different measurement applications; direct flow instrumentation is a future layer.

Borewell Water Accounting for Housing Societies

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:21:50 GMT

QUICK ANSWER

Record borewell water as a separate incoming source in the society's water budget. The strongest quantity record is a suitable, verified meter at a defined delivery point. If a meter is unavailable, use a transparently labeled estimate supported by operating records, not an assumed fixed number of litres per hour.

A borewell's pump runtime does not, by itself, prove the quantity extracted. Actual delivery can vary with groundwater conditions, equipment performance and the plumbing arrangement.

For water budgeting, separate three questions: Is extraction and use authorized under the rules applicable to this site? How much water was actually received? How reliably can the source contribute to future supply?

WHY A BOREWELL NEEDS ITS OWN LEDGER

A society may receive water from several external sources into the same underground tank. Groundwater can arrive from an on-site borewell where applicable, or indirectly through tanker suppliers that draw from their own borewells. The tank level reveals the combined net change after other inflows and withdrawals, while source-specific accounting requires separate evidence for each contribution.

If a society treats a borewell as a guaranteed daily quantity without measuring it, its water runway and tanker planning may be overly optimistic.

Separate source accounting also makes it easier to see whether a change in total storage reflects reduced groundwater delivery, a municipal interruption, a transfer problem or higher withdrawal.

FIRST: CHECK THE SITE'S PERMISSIONS AND WATER SERVICE

Before changing extraction, adding equipment or publishing claims about lawful use, identify the applicable authority, existing permissions and any current restrictions for the particular property and source.

Requirements can differ by location, groundwater category, use, project type and current directions. Do not assume that a rule for one Pune or PCMC property applies to another, or that a statewide drought announcement is itself the exact instruction for a particular borewell.

The facility team should retain the relevant approvals and verify current obligations with the competent authority or qualified adviser. This guide is an accounting method, not a legal determination or permission to drill, extract or change groundwater use.

Identify the receiving tank and the water service. Do not assume untreated borewell water is suitable for drinking or any other specific use; water quality and treatment are separate questions requiring appropriate assessment.

STEP 1 — MAP THE BOREWELL SUPPLY PATH

Document the borewell identifier, pump and delivery line, any meter, receiving tank or branch, and whether another source can enter the same line or tank.

Record whether the meter is upstream or downstream of any diversion, recirculation or treatment-related flow. A meter reading represents volume passing its actual measurement point, not automatically all water extracted or all water delivered to residents.

If multiple borewells share a manifold, establish whether the measurement is per source or combined. Never allocate a combined reading to individual borewells without independent evidence.

Use an approved site diagram and authorized personnel for physical inspection. Do not modify electrical or pressurized equipment as an informal measurement experiment.

STEP 2 — MEASURE RECEIVED VOLUME WHERE POSSIBLE

For a cumulative volume meter, the basic calculation is:

Volume over the period = closing meter reading − opening meter reading.

Suppose a verified meter records 3,420 kL at the beginning of the day and 3,444 kL at the end. The recorded passage through that meter is 24 kL, provided the meter, units and reading sequence are valid.

This is an illustrative example, not a TownEve installation result.

Record the meter ID, location, units, timestamp, verification status, operator and any reset or rollover. One cubic metre is one kilolitre, equal to 1,000 litres.

Meter selection and installation must suit the pipe, operating conditions and local requirements. Have qualified personnel assess them rather than applying a universal specification from an article.

STEP 3 — TREAT RUNTIME AS AN OPERATING RECORD, NOT A VOLUME METER

A pump may run for two hours without delivering the same quantity on every occasion. Actual flow may change with source conditions, pump performance, head, restrictions and system operation.

Runtime × an assumed flow rate is therefore an estimate, not independently measured extraction.

If the site has a properly established and periodically checked flow-rate relationship, it may use a documented estimate for planning. Label the estimate, record the test conditions and revalidate it when the system changes.

Do not silently turn motor-on time, electricity consumption or a tank-level change into a verified groundwater volume.

STEP 4 — RECONCILE THE RECEIVING TANK

For a single receiving tank over a consistent period:

Closing stored volume = opening stored volume + borewell inflow + other inflows − withdrawals and transfers ± documented adjustments.

Example: a domestic underground tank opens with 70 kL. A verified borewell meter records 20 kL delivered to the tank, and 15 kL is transferred to overhead storage. If no other flows occur, expected closing storage is 75 kL.

The observed net tank increase is only 5 kL, even though 20 kL entered from the borewell. Reporting the 5 kL change as the borewell's output would understate the measured delivery.

If municipal water also enters the tank, its volume belongs in a separate source column. A tank graph alone cannot distinguish simultaneous source contributions.

For a property-wide boundary including underground and overhead tanks, the transfer between those tanks is internal, not additional external water.

STEP 5 — KEEP EXTRACTION, RECEIPT AND CONSUMPTION DISTINCT

These quantities may differ depending on the physical boundary:

Extraction: water taken from the groundwater source, as measured or estimated at an appropriate point.

Received supply: water delivered into the society's defined storage or supply boundary.

Consumption or external outflow: water leaving that defined boundary for its intended uses or other destinations.

Storage change: the net difference between opening and closing inventory.

Do not equate these numbers unless the system configuration and measurement evidence support doing so.

If a borewell feeds a tank that is simultaneously filling from municipal supply and draining through a pump, the tank's net level change cannot independently identify borewell inflow, municipal inflow and withdrawal.

STEP 6 — BUILD A BOREWELL EVENT LEDGER

Use one line per verified event or accounting interval:

For daily reporting, retain the source-event evidence and aggregate compatible records into one borewell-supply total.

Measurement status should distinguish measured, estimated, planned and unknown. An unknown value is not zero. A pump that was scheduled to run is not proof that it ran or delivered water.

If multiple sources are used, the daily society water-balance template should preserve distinct municipal, borewell and tanker columns.

STEP 7 — ASSESS RELIABILITY WITHOUT MAKING GROUNDWATER PREDICTIONS

A useful planning record includes days when supply was unavailable, measured volumes when available, maintenance events and any verified change in operating conditions.

Use observed historical performance as context, not a guarantee of future extraction. Groundwater availability can change, and an individual property's well performance cannot be inferred solely from regional rainfall or a news headline.

For scenario planning, show a no-borewell case alongside a documented baseline rather than assuming the borewell will always contribute its usual quantity.

If a future supply assumption is uncertain, mark it uncertain. Do not inflate a water-runway estimate by treating it as confirmed replenishment.

STEP 8 — CONNECT BOREWELL SUPPLY TO TANK STORAGE

Tank inventory should include verified dimensions, geometry, normal withdrawal arrangements, dead-water height and the current measurement timestamp.

This supports accurate tank-specific calculations across different sizes and shapes when the entered geometry and measured level are correct.

Those readings help establish the storage side of the budget. They do not directly identify how much water the borewell produced when other flows occur simultaneously.

STEP 9 — USE THE RECORD FOR TANKER AND RUNWAY PLANNING

For a planning period:

Supplemental volume = projected demand + chosen closing reserve − opening usable storage − expected non-tanker supply.

Borewell supply should appear in expected non-tanker supply only with its measurement status and uncertainty visible. Use a lower-supply or no-supply scenario where that risk matters.

A booked tanker is likewise planned supply until delivery and quantity are verified.

For conditional runway, divide usable stored water by a stated withdrawal rate for a no-replenishment case, then model actual expected replenishment times separately. A simple average daily borewell figure can conceal a gap before the next supply window.

Do not add water held in a hydraulically isolated tank to the inventory serving another system without a valid transfer arrangement.

STEP 10 — REPORT CLEARLY TO THE COMMITTEE

A concise weekly report can show:

Compare periods with the same measurement boundary. A decline in recorded borewell supply is an operational signal to verify, not by itself proof of a regional aquifer trend.

If restrictions or permits change, record the applicable authority notice and its effective scope before updating the operating plan.

WHERE TOWNEVE FITS

TownEve currently offers contactless ultrasonic monitoring for suitable overhead and underground tanks, current and historical level visibility, configured email alerts, telemetry-freshness monitoring and geometry-aware usable-volume calculations using configured tank dimensions and dead-water height.

These capabilities strengthen storage visibility and can prompt investigation of an unusual trend. Borewell extraction, groundwater level, water quality and pump electrical state are separate measurement questions that use the corresponding instrumentation or operating records.

Direct pump-state monitoring is in development; remote pump operation is in development and testing. Flow-meter integration is app-capable, although flow-meter hardware has not yet been deployed. These are development layers extending the current tank-monitoring platform.

The practical progression is to pair verified storage observations with independent source measurements and a consistent accounting boundary.

FAQ

Can I calculate borewell output from pump runtime?

Only as a qualified estimate if a relevant flow-rate relationship has been verified. Runtime alone is not a volume measurement.

Can an underground tank graph tell me how much groundwater entered?

Not reliably when municipal supply, tanker input or withdrawals occur simultaneously. The graph shows net storage change.

Should borewell water be combined with municipal water in a budget?

It can be included as a separate external supply column for the same legitimate water-service boundary. Keep its source and measurement status distinct.

What if the borewell has no meter?

Record the limitation, use transparently documented estimates only where justified, and assess independent measurement if source volume matters to decisions.

Does a borewell's historical output guarantee drought-period supply?

No. Use scenarios and verify current performance; do not promise future groundwater availability.

Can borewell water be used for drinking?

This guide does not determine water suitability. Appropriate treatment, testing and applicable requirements must be evaluated separately.

Are all Maharashtra housing societies subject to the same borewell restrictions?

Do not assume so. Verify the applicable location, source, use and current competent-authority directions.

Can TownEve directly measure borewell extraction today?

No released direct extraction or flow-meter measurement capability is claimed here. Its current verified role is tank-level and usable-storage visibility.

Municipal, Borewell and Tanker Water Accounting for Housing Societies

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:20:45 GMT

How should a housing society account for water from municipal supply, borewells and tankers? This source ledger is one part of a complete society water budget. Keep a source-specific ledger of independently evidenced water entering the society, distinguish delivery from procurement, and reconcile it against storage observations without counting internal tank transfers as new water. When a source volume is not metered or documented, report it as unmeasured rather than inferring it from a tank-level change.

The accounting boundary comes first

Choose a clear reporting boundary, such as all water entering the society during a defined calendar month. Identify each incoming source, its meter or delivery evidence, and which storage tanks and water services it feeds. Record municipal, borewell, tanker and any other source separately. Also separate drinking, domestic and treated/recycled water where they have different treatment or permitted uses. A mixed total can be useful for financial reconciliation only when its components and units are visible; it must never imply that water from different service categories is interchangeable.

Copyable source ledger

For each receipt, capture these fields:

Source: municipal / borewell / tanker / other.

Service category and destination: [drinking / domestic / treated or recycled / other], [UGT or direct feed].

Evidence reference: [incoming meter reading pair, delivery challan, supplier invoice, borewell run log, or other record].

Start and end timestamp: [period or arrival and unloading time].

Measured or declared volume and units: [kL or m³, with original units retained].

Evidence type: [calibrated incoming meter / supplier declaration / inferred estimate / unmeasured].

Status: [scheduled / arrived / unloading verified / volume verified / disputed].

Duplicate key: [unique receipt or meter-period ID].

Cost and invoice reference: [actual amount or pending].

Owner and exceptions: [person, missing record, overlap or quality flag].

One kilolitre equals one cubic metre and 1,000 litres. Convert consistently, retain original units and document any rounding.

Municipal water: measure the intake, not just the tank response

For an intermittent municipal connection, record the source meter's opening and closing readings for the reporting period if an appropriate meter exists, along with timestamps and outages. A reading at the underground tank can show whether storage rose, fell or stayed stable during a municipal supply window. It cannot, on its own, measure gross municipal inflow when residents or pumps draw water at the same time. Note meter coverage, any bypass, and whether multiple connections feed the same system. Do not assign an unmetered tank refill wholly to municipal supply if a borewell or tanker also contributed.

Borewell: keep run evidence separate from measured yield

Record borewell ID, service destination, operation period, any suitable flow meter, and maintenance or interruption notes. Where groundwater reaches a society through a tanker supplier's own borewell rather than an on-site borewell, record it as tanker supply at the society boundary and preserve the supplier-side source context separately. Pump run time multiplied by an assumed flow rate is an estimate, not a measured receipt. Actual yield may vary with operating conditions. Label the assumed rate, method and verification date if an estimate is used. Do not count a borewell-to-UGT transfer again when that water is pumped to an OHT.

Tanker: reconcile orders, arrivals, receipts and invoices

A booked tanker is not a delivered volume. Match the order, vehicle or trip reference, arrival record, supplier challan, any independently verified volume, destination tank, and invoice. A tank-level rise is corroborating evidence that stored water increased, not a stand-alone certification of the truck's delivered volume when concurrent outflow or another inflow is possible. Where supplier-declared capacity is the only figure, label it supplier-declared and do not present it as independently measured. Resolve duplicate challans and split deliveries before aggregation. Tanker-management software workflows are in development at TownEve. The source ledger described here is an operating method for the society's verified records.

Avoid the three common double counts

First, an incoming receipt appears in both the source ledger and the tanker invoice. Count its water volume once; the invoice belongs in the cost ledger. Second, water moves from an underground tank to an overhead tank. This is an internal transfer, not a second external receipt. Third, one supply period appears in both a meter total and individual delivery notes. Use the meter's coverage and receipt IDs to determine whether they overlap before summing.

Worked example, hypothetical only

A society has an independently metered municipal intake of 120 kL for the month, an independently metered borewell intake of 30 kL, and two tankers with independently verified receipts of 10 kL each. Verified external inflow is 120 + 30 + 10 + 10 = 170 kL. A further 80 kL moved from UGTs to OHTs is an internal transfer and does not increase the 170 kL external inflow total. If the two tanker quantities are merely supplier-declared rather than independently verified, show 150 kL independently metered plus 20 kL supplier-declared, not “170 kL measured.” None of these illustrative values describes Park Astra or another customer.

Water balance and consumption limits

For a defined storage boundary and time period, closing storage minus opening storage equals external inflow minus external outflow, adjusted for transfers crossing that boundary and measurement error. When simultaneous inflow and outflow are unknown, a tank-level change is only their net result. It does not reveal both separately. A controlled no-inflow observation can help study outflow when all incoming paths are known to be closed, but a short observation does not automatically represent daily or monthly consumption. Any controlled valve-isolation procedure must be authorized and performed by the facilities team without compromising essential supply or safety. TownEve has tested its sensor-assisted manual isolation investigation and continues to refine it; it is not an automatic consumption measurement feature.

Month-end reconciliation

1. Freeze the period, reporting boundary, units and water-service categories.

2. Deduplicate incoming meter intervals and tanker receipt IDs.

3. Sum independently measured external receipts by source; separately disclose supplier-declared, estimated and unmeasured amounts.

4. Record opening and closing storage by tank with timestamps, geometry assumptions and sensor freshness.

5. Mark internal UGT-to-OHT transfers separately and avoid treating them as external supply.

6. Reconcile supplier bills and operating logs without converting unexplained residuals into a claimed leak or resident demand figure.

7. Explain gaps, unmetered paths, maintenance changes, missing records and differing timestamps.

8. Obtain facilities and committee sign-off before sharing a resident-facing summary.

Useful monthly outputs

Report independently measured intake by source and service category; supplier-declared or estimated quantities separately; tank storage snapshots; verified interruption incidents; purchased-water cost and invoice status; evidence completeness; and open measurement gaps. Cost per kilolitre is meaningful only when the numerator and denominator cover the same source, period and measurement basis. Do not divide total society water costs by an unverified tank-level-derived intake.

What TownEve currently contributes

Current production supports contactless ultrasonic tank monitoring, historical water levels, configured level-based email alerts, role-based visibility, telemetry-freshness monitoring and stored-volume calculations derived from measured depth and configured tank geometry. These observations provide the storage evidence for source-ledger reconciliation and exception investigation. Source-specific municipal, borewell and tanker quantities use the corresponding meter, delivery evidence or controlled estimation method. Flow-meter integration is app-capable although flow-meter hardware has not yet been deployed. Direct pump-state monitoring and remote pump operation are in development/testing.

Frequently asked questions

Can we use a UGT level rise to calculate municipal inflow? Only under a validated boundary with other inflow and outflow known or controlled; otherwise it is net storage change.

Can we count a tanker at its nominal capacity? You may record supplier-declared capacity with its evidence class, but do not label it independently measured delivered volume.

What if municipal and borewell supplies run simultaneously? Use separately covered incoming meters or report the attribution as unknown. The combined storage trend cannot separate the two sources.

Should treated water be combined with drinking water? Keep service categories separate for operational and quality decisions, even if a transparent all-source accounting summary is also provided.

Does a mismatch prove leakage? No. Meter error, timing, internal transfers, unrecorded receipts, evaporation or other unmeasured paths may contribute. Investigate before attributing a cause.

Drought Readiness Checklist for Housing Societies

support@towneve.com (TownEve Editorial Team) — Thu, 01 Oct 2026 06:20:02 GMT

THE SHORT ANSWER

A drought-ready housing society knows which water sources it can actually rely on, how much usable water it has, what it withdraws, when replenishment is expected, and who will act if the plan changes.

The most useful preparation is a verified water budget plus an operational response plan. Do not wait until the rooftop tank is nearly empty to discover that the next municipal supply window is uncertain or the backup tanker supplier cannot deliver.

This checklist is designed for committee members, facility managers and engineering teams. It does not assume that a statewide drought declaration means every society has the same local restrictions or supply conditions.

START WITH THE TEN-STAGE JOURNEY

Supply → Storage → Consumption → Water Balance → Forecasting → Loss Detection → Tanker Planning → Pump Operations → Resident Communication → Drought Readiness.

Use the checks below in that order. Mark each item “verified,” “in progress,” “not applicable,” or “unknown,” and name the person responsible. An unverified assumption is not the same as a completed check.

1. SUPPLY — KNOW WHAT CAN ARRIVE

[ ] List each relevant water source: municipal connection, permitted borewell, contracted tanker or other authorized source.

[ ] Record which water service each source supplies; keep drinking, domestic and treated recycled-water systems distinct.

[ ] Identify how incoming quantity is measured and whether the latest figure is measured, estimated or unknown.

[ ] Record normal supply windows and any verified changes, rather than relying on historical schedules alone.

[ ] Verify the responsible utility or supplier contact and the latest known status.

[ ] Record dependencies that could interrupt delivery, including upstream pumping, power or supplier availability where documented.

[ ] Verify current local orders and restrictions with the responsible authority before changing operations.

Why it matters: “Water was expected today” is not equivalent to “water entered the society.” A booked tanker or scheduled municipal supply is a scenario until delivery is confirmed.

2. STORAGE — COUNT USABLE WATER, NOT NOMINAL CAPACITY

[ ] Inventory every relevant underground and overhead tank and any separately managed compartments.

[ ] Confirm tank identity, service, internal dimensions, shape, measurement reference and normal withdrawal arrangement.

[ ] Record the usable-water limit or dead-water height and its verification source.

[ ] Establish a consistent timestamp for current storage readings.

[ ] Sum verified usable litres only within the appropriate water-service and hydraulic boundary.

[ ] Check whether transfer constraints make some stored water temporarily unavailable to a particular tower or service.

TownEve allows tank dimensions and dead-water height to be entered in its dashboard. Its tank-specific level-to-volume calculation uses the configured geometry rather than assuming that tanks of different sizes or shapes are interchangeable. The configured unusable portion can be excluded from usable-water calculations.

This supports accurate tank-specific volume calculations when the entered geometry and measured level are valid. Geometry configuration does not remove the need to validate sensor installation and readings.

3. CONSUMPTION — ESTABLISH A DEFENSIBLE BASELINE

[ ] Use reliable measured outgoing volumes where available.

[ ] If measurement is unavailable, document occupancy, litres-per-person assumptions and separately accounted common-area uses.

[ ] Keep residential, common-area and different water-service requirements distinct.

[ ] Compare the baseline with available historical supply and storage records.

[ ] Record how demand may change during a supply interruption or approved conservation measures.

[ ] Identify which uses or services require separate operational or regulatory treatment.

An occupancy-based estimate is useful for planning but is not a measured consumption figure. Tank-level change alone is a net storage observation when inflow and outflow occur simultaneously.

4. WATER BALANCE — RECONCILE THE NUMBERS

[ ] Define the accounting boundary and the same cutoff period for all records.

[ ] Record external supply separately by source.

[ ] Record opening and closing usable storage.

[ ] Record independently measured outflow where available; otherwise label any derived withdrawal as implied or estimated.

[ ] Exclude underground-to-overhead transfers from a property-wide external inflow total.

[ ] Investigate unexplained differences without automatically labeling them leaks.

For a defined boundary:

Opening storage + external inflow − external outflow ± documented adjustments = closing storage.

A missing reading must remain “unknown,” not silently become zero.

5. FORECASTING — CALCULATE CONDITIONAL RUNWAY

[ ] Choose a documented operational response reserve for each relevant service.

[ ] Calculate no-replenishment runway using current usable storage and a stated withdrawal scenario.

[ ] Model the timing of expected municipal supply and tanker arrivals, not just their average daily quantity.

[ ] Include lower, baseline and higher demand scenarios where uncertainty is material.

[ ] Check whether a threshold could be crossed before the next delivery.

[ ] Record the last valid observation time, assumptions and next review time.

No-replenishment runway = usable water ÷ assumed daily withdrawal.

For illustration, 90 kL of usable water at an assumed 30 kL/day gives three days to modeled zero without replenishment. It is not a guarantee of uninterrupted tap service. A transfer failure can affect overhead supply before property-wide stored volume reaches zero.

6. LOSS DETECTION — INVESTIGATE, DO NOT ASSUME

[ ] Review abnormal level trends or unexplained reconciliation differences.

[ ] Check measurement timestamps, units, tank configuration and meter status first.

[ ] Check for unrecorded transfers or legitimate operating uses.

[ ] Arrange an authorized physical inspection when the evidence warrants it.

[ ] Record findings and corrective action without assigning an unverified cause.

An unexpected tank trend is a signal to investigate. It does not by itself quantify leakage, identify a specific pipe fault or prove misuse.

7. TANKER PLANNING — VERIFY CAPACITY, TIMING AND COST

[ ] Identify primary and backup suppliers and verify their current ability to serve the property.

[ ] Record contact details, order lead time, delivery windows, access constraints and service suitability.

[ ] Calculate the supplemental volume needed under a stated demand and reserve scenario.

[ ] Distinguish booked, invoiced and verified received tanker volumes.

[ ] Record destination tank, delivery time, volume evidence and actual charges.

[ ] Confirm contingency action if a scheduled delivery is delayed or smaller than expected.

A basic planning equation is:

Supplemental volume = projected demand + desired closing reserve − opening usable storage − expected non-tanker supply.

Use a zero floor when the arithmetic produces a negative shortfall; do not order a negative volume. The estimate must be checked against timing and available delivery sizes.

Record the actual supplier quote and verify received volume separately from the tanker's stated capacity.

8. PUMP OPERATIONS — CHECK THE TRANSFER PATH

[ ] Document which underground tanks supply which overhead tanks.

[ ] Identify authorized staff who can inspect pumps, electrical supply, valves and transfer controls.

[ ] Verify the escalation path for an overhead tank that is falling while underground storage remains available.

[ ] Record maintenance and power dependencies that affect transfer reliability.

[ ] Establish a safe, approved operating procedure; do not improvise electrical or confined-space work.

TownEve's current tank-level visibility and historical trends can help reveal a pattern requiring investigation. They do not directly establish pump electrical state or provide released automatic pump protection.

Direct pump-state monitoring is in development; remote pump operation is in development and testing.

9. RESIDENT COMMUNICATION — REPORT VERIFIED CONDITIONS

[ ] Identify who approves society-wide updates.

[ ] Prepare a factual notice format for the affected water service and towers.

[ ] Distinguish confirmed conditions from estimated runway and unverified delivery times.

[ ] Explain actions underway and give the next update time.

[ ] Use an accessible communication channel for residents and an escalation route for urgent needs.

[ ] Check current authority directions before describing restrictions or permissible uses.

A useful notice says what is known, what the facility team is doing, and when the next verified update will arrive. Avoid dramatic countdowns or claims that all water is exhausted when only one overhead service is affected.

10. DROUGHT READINESS — TURN THE CHECKLIST INTO AN OPERATING PLAN

[ ] Assign one owner for the daily water balance and a backup.

[ ] Set review frequency and response thresholds appropriate to the property.

[ ] Confirm supplier and facility-team contact trees.

[ ] Verify source permissions, applicable local restrictions and the current authority notices.

[ ] Approve the process for changing operating practices and informing residents.

[ ] Conduct a tabletop review of a delayed municipal supply, missed tanker and transfer failure.

[ ] Review the plan after an incident, major equipment change or supply-policy update.

The goal is a repeatable process, not a one-time checklist that becomes obsolete.

A ONE-PAGE COMMITTEE READINESS SUMMARY

For each water service, report:

Service and included tanks:

Last verified storage timestamp:

Current usable storage (kL):

External supply received in the last accounting period, by source:

Measured or estimated daily withdrawal and its basis:

Chosen response reserve (kL):

Modeled no-replenishment runway to reserve:

Next confirmed supply:

Next expected but unconfirmed supply:

Operational transfer constraints:

Unresolved discrepancy or incident:

Current local direction verified against:

Responsible person:

Next review time:

A blank or unknown field is an action item, not a reason to invent a number.

HOW TO USE THE CHECKLIST IN PUNE AND PCMC

Begin with the property's actual supply records and the current notices from the relevant municipal, water-supply and disaster-management authorities. Check whether the building's source is municipal, tanker, borewell or a combination and whether restrictions apply to that particular source or locality.

Regional rainfall, reservoir and groundwater reporting provides context, but it does not by itself prove that a particular society will run out of water or that a specific restriction applies to its residents.

When a regional development affects the property, record the date, verified source, operational implications and actions to review in the society's readiness plan.

WHERE TOWNEVE FITS

TownEve currently offers contactless ultrasonic level monitoring for suitable underground and overhead tanks, current and historical tank-level visibility, configured email alerts, telemetry-freshness monitoring, and tank-specific usable-volume calculations based on configured dimensions and dead-water height.

These capabilities give societies a live storage and historical visibility layer for drought readiness. Source quantities, tanker receipts, consumption and pump condition use the corresponding operational records, controlled methods or instrumentation appropriate to each question.

The broader roadmap progressively connects supply inputs, tanker records, pump information and consumption estimation. Direct pump-state monitoring is in development; remote pump operation is in development and testing; tanker workflows are in development; flow-meter instrumentation is a future layer.

Deployment planning starts with the current monitoring layer and the site's verified operating records.

FAQ

What is the first step in drought preparedness for a society?

Verify each water source, current usable storage, demand baseline and responsible operator. Then build a water balance.

How much emergency water should a society store?

There is no universal percentage. The choice depends on actual demand, supply reliability, replenishment lead times, usable capacity and operational constraints.

Can a society use nominal tank capacity to estimate its runway?

No. Use current usable water in the relevant service, accounting for dead-water height and transfer constraints.

Does a low overhead tank mean underground storage is empty?

Not necessarily. The transfer system and underground levels need separate verification.

How should tanker requirements be calculated?

Estimate the shortfall over the planning period after accounting for usable opening storage, expected non-tanker supply, projected demand and a chosen closing reserve.

Does a tank-level graph prove water leakage?

No. It can reveal an unexpected pattern but cannot independently determine its cause.

Are statewide drought announcements the same as a local water restriction?

No. Check the current applicable directions from the responsible authority.

Can TownEve automatically forecast a guaranteed shortage date?

No released end-to-end forecasting guarantee is claimed. Its verified storage monitoring can supply a useful input to a separately documented scenario.