| Product(s): | WaterSight |
| Version(s): | 10.00. |
| Area: | Documentation |
Units Mismatch Issue
In case it is noted that the model values in WaterSight do not match the sensor values for the boundary elements (for example tank levels, PRV settings) please make sure that the units defined for the SCADA signals in the uploaded WaterGEMS model matches the units defined for the sensors in the WaterSight in the Admin >> sensors and are the same as in the database.
To check in WaterGEMS: go to WaterSight >> Numerical Models >> Previous Simulations. Download latest model. Open in WaterGEMS and go to SCADA signals, click on edit data source and go to units tab. If units are wrong, please update, save the model, and reupload again in WaterSight. Please note that these are the units for which measurements are being registered in the database and might be different than the display units!
To check in WaterSight: go to Admin >> Sensors. Check the units. If units are wrong please update by importing an updated configuration template or directly through the UI. Please note that these are the units for which measurements are being registered in the database and might be different than the display units!
Fig 1 - Model value at blue does not match sensor measurements (black line) for the PRV boundary element due to mismatch of units defined in the hydraulic model and in the sensor configuration template
Why is the model flow very different from the real flow?
In case there are significant differences between model flow (blue line in graph below and real flow (black line in graph below) first make sure that the option to enable automatic zone demand adjustment (zone by zone) is enabled in the Numerical Model settings (inside the administration).
If this option is enabled next step is to check if all the junctions in the WaterGEMS model that belong to that zone have the zone field assigned or if the zone name matches exactly the one defined in WaterSight. Note that for the model nodes with no zones assigned or with zones names different that those defined in WaterSight, patterns and demand adjustments will be ignored and the model base demand and units demands will be taken into account. This means for example that if a junction that belongs to a specific zone does not have a zone assigned in WaterGEMS and has a consumption of 10 l/s, and assuming the real average zone flow is 20 l/s, those 10 l/s will be added, which will contribute to a final zone average zone flow in the model of 30 l/s (instead of 20), which is not correct.
Figure 2- Assigning zones to the junctions in the WaterGEMS model. Example of junction J-713 with no zone assigned.
See Also
Imposing Initial Conditions from Sensors to the Model
Numerical Model Administration
Automatic Hydraulic Grade Adjustment
Using AMI/Smart meter for model runs