| Product(s): | WaterSight |
| Version(s): | 10.00. |
| Area: | Documentation |
WaterSight New Updates (December 2025)
A new release has been published in December 2025, bringing the following additional functionalities:
Aggregated Large Customer Flow per Zone
Zone Overview and Zone Graph
The total large customer flow obtained by summing each individual smart meter belonging to a specific zone is now displayed directly on the zone graph. By default the total large customer flow is disabled, but the user can enable it from the Zone overview page or zone detail graph page, by clicking on the visibility button and enabling large customer flow, which will be represented with a blue line (check figures below).
This is particularly useful to more efficiently analyse if zone flow events might represent real bursts or leaks or the zone flow increases are just due to large customer consumptions.
Figure 1 - Enabling large customer flow in the zone overview graph
Figure 2 - Enabling large customer flow in the zone detail graph
The Flow Remainder time series can also be enabled and represents the difference between the total zone flow and the total large customer flow series.
Comparison
The Total Large Customer Flow and Flow Remainder time series is also available under the Graph Comparison:
Figure 2 - Enabling large customer flow in the zone detail graph.
When accessing the comparison page directly from the zone graph detail (by pressing the comparison shortcut above the zone graph ) , automatically the inflow and outflow sensors of the zone as well as the total large customer series will be displayed. To quickly access those time series in the right side panel, press the "show selected in series-tree" button, located on the bottom of the side panel.
From the comparison page the user can also easily disaggregate the Total Large Customer Flow series to analyse the contribution of each individual large customer belonging to the same zone. To do this, press the graph icon located on the right side of the total large customer series, as shown below:
After that the graph will automatically populate with each individual Large Customer series (for that specific zone), as shown below. This can be useful to understand if in case there is a big large customer flow increase, which is the main responsible customer.
Figure 3 - Displaying each individual Large Customer series belonging to the same zone.
More information about Large Customer workflows and configuration can be seen here - Smart Meters/AMI and Large Customers Workflows
Ignore WaterSight zone demand adjustments in case there are no zone patterns
WaterSight automatically computes a pattern for the global system and each zone based on the available sensor data, and this pattern can be automatically applied to the real time hydraulic model. More information available here - Automatic Demand Adjustment.
However, sometimes, by different reasons, might not be possible to calculate the pattern for a specific zone (sensors broke/have no data or there are large period events with the option exclude from pattern enabled, etc).
Before hydraulic model run would fail with below message:
With the most recent improvement, if the same situation occurs, the model run will not fail anymore, but instead the WaterSight pattern will be ignored for that zone and the default pattern (if exists) in the original WaterGEMS model will be used instead. Whenever this happens a warning will be generated to inform the user, as shown below:
More information about why the automatic zone demand adjustment might be failing and possible solutions, check the Common Warning Section of this article - Previous Simulations.
Geolocation of Leaks Improvements
The new update brings several improvements in the geolocation of leaks algorithm. Besides this, it was also added the option to re-run again the same geolocation event, by pressing the re-run geolocation button (), as shown below. This might be useful for situations where for example the model needs to be reconfigured or updated and the user wants to run again the same geolocation but based on the most recent re-uploaded model. More information about geolocation workflow and requirements can be found here - Geolocation of Leaks.
See Also
OpenFlows WaterSight TechNotes and FAQ's
WaterSight Learning Resources Guide