OUR OFFICE
Rukan Great Wall, Jl. Green Lake City Boulevard No.63 Blok B, RT.002/RW.008, Petir, Kec. Cipondoh, Kota Tangerang, Banten 15146 Indonesia
Want to learn more?
Contact UsOUR OFFICE
Rukan Great Wall, Jl. Green Lake City Boulevard No.63 Blok B, RT.002/RW.008, Petir, Kec. Cipondoh, Kota Tangerang, Banten 15146 Indonesia
Want to learn more?
Contact UsA water meter can report that a customer consumed five cubic meters of water in a day. The figure is useful for billing, but it reveals very little about how that water was used.
Was most of the consumption concentrated in the morning? Did water continue flowing overnight? Was there an unusual increase compared with previous days?
These questions become easier to investigate when water consumption data is collected at shorter, consistent intervals.
Smart water meters provide an opportunity to move beyond periodic meter readings toward data-driven water management. For water utilities, building managers, and industrial operators, that information can support consumption analysis, unusual usage alerts, and investigations into possible water losses.
The distinction between identifying an anomaly and confirming a leak is important. A smart meter measures water passing through its measurement point. Interpreting what that measurement means requires context, reliable data, and sometimes further investigation.
A smart water metering system typically combines a water measurement device with a method for collecting and transmitting readings.
Depending on the meter and communication module, the information available may include cumulative water volume, interval consumption, device status, battery condition, and diagnostic alerts.
Not every smart meter provides the same measurements.
Some systems transmit cumulative meter readings at scheduled intervals. Others can report additional information such as flow conditions or specific device alarms.
The difference matters when designing a monitoring application.
A cumulative meter reading represents the total volume recorded by the meter over time.
Consumption during a particular period can be calculated by subtracting an earlier valid reading from a later valid reading.
For example, consider a meter reporting the following values:
| Time | Cumulative reading |
|---|---|
| 08:00 | 1,250.0 m³ |
| 09:00 | 1,250.4 m³ |
| 10:00 | 1,251.1 m³ |
| 11:00 | 1,251.3 m³ |
Consumption between 09:00 and 10:00 is 0.7 m³, equivalent to 700 liters.
This is a hypothetical calculation, not data from a field installation.
An important limitation follows from this method. If the system receives cumulative readings only once per day, it can calculate daily consumption but cannot reconstruct precisely when water was used throughout that day.
A dashboard should not present such readings as continuous, real-time flow measurements.
The United States Environmental Protection Agency (EPA) identifies more frequent water-use information as one of the benefits of Advanced Metering Infrastructure (AMI). More detailed data can help utilities and facility managers identify unusual consumption sooner than conventional billing cycles allow.
However, higher reading frequency introduces trade-offs.
Additional transmissions may increase communication traffic, data storage requirements, and energy consumption in battery-powered devices.
The appropriate interval depends on what the organization needs to detect.
Daily readings may be sufficient for routine consumption reporting. Hourly readings provide more detail for investigating unexpected usage. Applications requiring more precise analysis may need shorter intervals or dedicated flow instrumentation.
An abnormal reading does not necessarily mean that a meter has malfunctioned or a pipe has leaked.
Water usage changes for legitimate reasons. A hotel may experience higher consumption during periods of greater occupancy. A factory may use additional water during cleaning or production. A household may increase consumption when guests are staying.
Meaningful anomaly detection requires comparing current measurements with expected operating conditions.
One pattern worth investigating is persistent consumption during periods when little or no water should normally be used.
For example, an office building that operates only during business hours might report water consumption throughout the night.
This pattern could be associated with a leaking fixture, equipment that continues operating, an unauthorized use, or a legitimate overnight activity.
The meter data provides a reason to investigate. It does not identify the cause on its own.
A sudden increase in consumption compared with comparable previous periods may also justify further examination.
The comparison should account for operating schedules, occupancy, seasonal changes, and other conditions that influence demand.
A simple fixed threshold may produce unnecessary alerts if it ignores these factors.
More advanced analysis can incorporate historical baselines, time-of-day patterns, or differences between weekdays and weekends.
Even then, the output should be treated as an indication requiring interpretation.
Smart meter data can support leak detection, particularly when water passes through the meter and creates a measurable change in consumption.
According to the EPA's WaterSense guidance, AMI data can help utilities and facility managers recognize excessive water use associated with possible leakage.
There are nevertheless important limitations.
A customer meter cannot directly detect every leak within the upstream distribution network. Leakage occurring before the meter may not appear in that customer's recorded consumption.
The system also cannot automatically distinguish every leak from intentional water use.
Flow monitoring, pressure measurements, acoustic monitoring, and field inspections may be needed to confirm a suspected problem.
For water passing through a customer's meter, interval consumption data can provide clues about abnormal usage.
If a property has an established pattern of very low overnight consumption but begins reporting persistent use, an operator may investigate fixtures, storage systems, or internal piping.
The usefulness of the alert depends on meter sensitivity, reading frequency, and the configuration of the detection logic.
Finding water losses in a distribution network requires a broader assessment.
A utility may compare measured water supplied into an area with customer consumption, taking account of timing, authorized unbilled uses, data quality, and other relevant factors.
Pressure and flow monitoring may provide additional evidence.
This approach is different from analyzing a single household meter.
Non-Revenue Water (NRW) is water supplied into a distribution system that does not generate corresponding billed revenue.
The World Bank and its water-sector partners distinguish between physical losses, apparent or commercial losses, and authorized consumption that is not billed.
Physical losses include leakage from pipes and other distribution infrastructure.
Apparent losses can result from meter inaccuracies, unauthorized consumption, and errors in reading or processing billing information.
These categories matter because they require different corrective measures.
Installing remote-reading technology can improve the availability and consistency of consumption records. It may also help identify data collection problems that contribute to commercial losses.
But remote communication does not automatically improve the measurement accuracy of an aging mechanical meter.
If a meter under-registers consumption, transmitting its readings wirelessly does not correct the underlying measurement error.
Similarly, smart customer meters alone cannot eliminate physical losses throughout a distribution system.
NRW reduction requires an appropriate combination of measurement, network analysis, field investigation, repair, commercial controls, and maintenance.
Connecting thousands of meters creates a larger flow of information, but the usefulness of that information depends on its quality.
Several issues should be considered before data is used for billing or operational decisions.
Missing readings
A device may fail to transmit because of network conditions, insufficient battery power, or a technical issue. Missing intervals must be identified rather than silently interpreted as zero consumption.
Measurement and unit consistency
Meter values should use documented units and consistent scaling. Incorrect pulse factors or register interpretation can produce significant errors in calculated consumption.
Timestamp accuracy
The time associated with a reading affects comparisons and daily reporting. Systems should distinguish the measurement time from the time data was received whenever the device and architecture support that distinction.
Validation and reconciliation
Unexpected values should be examined before triggering consequential actions. For billing applications, exception handling and reconciliation procedures are particularly important.
A sophisticated dashboard does not remove the need for these basic controls.
For Indonesian water utilities, the value of smart metering depends on operational priorities and existing infrastructure.
Remote reading can support routine meter collection across distributed customer locations. Consumption histories can help customer service teams investigate disputed readings. Unusual usage alerts can provide information for targeted follow-up.
In apartment buildings and industrial estates, submeters may help distinguish water consumption across tenants, buildings, or operational areas.
However, system design must account for installation conditions, meter compatibility, network coverage, reporting requirements, and maintenance.
PT IoT Kreasi Indonesia (IKI) provides Smart Water Monitoring solutions covering metering, connectivity, and monitoring applications.
Its published portfolio includes smart water metering devices and LoRaWAN-based connectivity.
IKI also published an announcement in July 2025 describing an agreement with Perumdam Gapura Tirta Rahayu in Purwakarta for automatic meter monitoring using LoRaWAN.
The announcement establishes the stated collaboration and project objectives. It should not be treated as independent verification of final operational results or quantified NRW reduction.
A useful dashboard should be designed around operational questions rather than the number of charts it displays.
| Operational question | Relevant information |
|---|---|
| How much water was consumed? | Valid cumulative readings and calculated interval consumption |
| Is consumption changing unexpectedly? | Comparable historical usage and anomaly thresholds |
| Are readings arriving as expected? | Device reporting status and missing-data records |
| Does a suspected leak require investigation? | Persistent consumption patterns and contextual information |
| Can the data support billing? | Meter identity, reading validity, units, timestamps, and reconciliation status |
For larger deployments, operators may also need device health monitoring, network diagnostics, alerts, and integration with existing billing or asset management systems.
These features should be defined during system design, not added as an afterthought once devices are installed.
Generally, a customer smart meter cannot locate a leak precisely. Consumption patterns can indicate unusual usage, but locating the cause may require inspection or additional sensors.
No. Data availability depends on the device, communication network, and reporting configuration. Scheduled readings should not be confused with continuous measurement.
They can support NRW management by improving data availability and helping investigate some commercial and consumption-related issues. Reducing NRW requires additional operational measures, especially for physical distribution losses.
Not necessarily. Accuracy depends on the measurement technology, meter condition, installation, and applicable performance specifications. Adding remote communication alone does not improve measurement accuracy.
Some existing meters support compatible reading modules or pulse interfaces. Other installations require meter replacement. Compatibility must be assessed for the specific meter model.
Depending on device design and network availability, systems may use LoRaWAN, NB-IoT, other cellular technologies, or wired communication interfaces.
Smart water meters provide more than an alternative method of collecting consumption readings, but their value should not be overstated.
Consistent data can reveal patterns that are difficult to observe through occasional manual readings. It can support investigations, improve visibility, and give operators a stronger basis for deciding where further action is needed.
The most reliable implementations combine suitable meters, well-designed connectivity, validated data processing, and operational procedures for handling abnormal readings.
For utilities and facility operators, the objective should be a system that produces trustworthy information and supports measurable decisions.
Explore PT IoT Kreasi Indonesia's Smart Water Monitoring solutions to learn more about connected metering and IoT integration.
U.S. Environmental Protection Agency. Advanced Metering Infrastructure. WaterSense. https://www.epa.gov/watersense/advanced-metering-infrastructure
U.S. Environmental Protection Agency. Leak Detection and Flow Monitoring Devices. WaterSense. https://www.epa.gov/watersense/leak-detection-and-flow-monitoring-devices
U.S. Environmental Protection Agency. Getting Started. WaterSense, water management and metering guidance. https://www.epa.gov/watersense/getting-started
World Bank Group. Contracting Tools for Non-Revenue Water Reduction. World Bank PPP Reference. https://ppp.worldbank.org/water-and-sanitation/contracting-tools-non-revenue-water-reduction
PT IoT Kreasi Indonesia. Smart Water Monitoring. Official solution portfolio. https://www.weiots.io/solution/water-monitoring
PT IoT Kreasi Indonesia. (2025, July 15). Enabling Automatic Water Monitoring with LoRaWAN in Purwakarta. https://www.weiots.io/blog/en/enabling-automatic-water-monitoring-with-lorawan-in-purwakarta