Product(s):	WaterSight
Version(s):	10.00.
Area:	Documentation

Overview

Administration page used to import sensors data (SCADA sensors or data loggers installed in the system) and sensors characteristics into WaterSight. Sensors types available to upload include the following types: flow, pressure, level, pump power and pump status.

It is possible to import sensors information through a configuration excel file (template file available for download in the Digital Twin Setup page) or to manually add a sensor and its characteristics. After uploading sensor information, it is also possible to edit, delete or copy information, using the available buttons located above the table. 

Note: To enable the Copy, Edit and Remove options, please select a sensor first (row in the table). When clicking in a specific sensor (table row) the fields available for editing will appear below the sensor configuration table.

The more actions button includes:

• Purge: clicking purge when a sensor (row) is already selected will delete all the data/history for that specific sensor. If the On-Premise tools (OpenFlows On-Site Data Coordinator) are working, the sensor should be automatically re-uploaded with the historical data after some minutes;
• Purge all: this option deletes all the data/history for all sensors. If the On-Premise tools are working, sensors should be automatically re-uploaded with the historical data after several minutes;
• Delete all: this option deletes not only the data but also all sensor elements (together with all properties defined) from the application. 

In order to have sensors transmitting real time data into WaterSight, it is required that:

• The user completes the sensors configuration table (below) - at least all minimum required fields; 
• The On-Premise Tools are correctly installed and configured in a machine that has direct access to the sensors data and is running 24/7. 

Sensor Configuration Table

Note: Minimum required fields are marked with an asterisk.

Column	Description
ID/Tag*	Required field. Unique name in the database for each sensor. Please just consider flow, pressure, level, pump power or pump status types.
Name	The name which will be displayed in the application. If empty tag name will be used.
Type*	Required field. Parameter of the signal in the database/source. Options are flow, level, pressure, power or status.
Units*	Required field. Units of the parameter in the database.
Communication Frequency*	Required field. Communication or transmit frequency. The typical time interval in minutes in which the collected/read data is sent to the database (eg: 60 = in every 60 minutes data is send to the database). Note: most SCADA sensors have low communication frequencies (communicate every minute or every 5 minutes for example) but some sensors (like for example dataloggers, AMI systems,, IOT devices) may communicate with the data source only once or twice a day but download data covering multiple time steps at one time
Registration Frequency*	Required field. Minimum read frequency. The time in minutes interval in which at least one data point is expected to be registered in the database (E.G 15 means at least one data point is expected every 15 minutes) Note: This is different from the communication frequency. One sensor may only communicate once a day, but the registration frequency may be every 5 minutes for example (this means that data gets into the data source only once a day, but when it arrives there is data for all the day in every 5 minutes time step)
Timezone*	Required field. Time offset from UTC given in HH.mm. (example -05:00 or 05:00; please note that +05:00 is not considered a valid input). This is the timezone which sensors are being registered in the database, and not the timezone of the digital twin.
Longitude*	Required field. Longitude related to sensor location. The coordinate system should be defined by the user before the upload of the file in the settings.
Latitude*	Required field. Latitude related to sensor location. The coordinate system should be defined by the user before the upload of the file in the settings.
Reference Elevation	Elevation of Sensor above datum (usually mean sea level). Only required for pump pressure data (in order to calculate the head). For tank level sensors this corresponds to the tank elevation base.
Last Instant in DB	Once a connection between WaterSight and Sensors data source is established, this column will display the last instant available in the database.
Priority	The priority when displaying in the sensor overview. Note that a priority of 0 means that the sensor will not be included or shown in the Sensor Overview, Sensor Status and Home Dashboard.
Offline	If for example there are well known sensors with no data for already a long period of time, it is recommended to mark them as offline so that the performance of the on-premise data pusher tool is not affected.
Pattern	Pattern group assigned to the sensor. Pattern groups can be created the the Administration > Settings > Pattern. If Pattern None is selected, then no patterns will be computed and displayed in the sensor graph. Patterns are displayed in the sensors graphs as grey bands.
Tags	Tags allow to group sensors inside the application, so it is easier to search and find specific sensors of interest.

Note: When uploading the sensor configuration file for the first time, the default patterns will be assumed:

• Flow, level, pressure, turbidity, chlorine, pH measurement types will have assigned the default pattern Weekday, Saturday and Sunday. 
• Power, Pump Speed, Pump Status, Temperature, Valve Status, Volume will have assigned the pattern None

Tags (User defined groups)

It is possible to insert tags (or user defined groups) for each sensor, by directly filling the Tags column in the Sensors Configuration Template or by directly clicking  Edit   in the property grid. Once tags are defined, those will be available in the Network Monitoring pages, so that is easier to search and find specific sensors of interest. Below some examples of groups that may be relevant:

• grouping sensors by zones
• grouping sensors by towns
• grouping sensors by vertical assets (pumps, tanks, PRV, etc)
• grouping sensors by critical and non-critical
• etc, etc

For more information about WaterSight, please go to OpenFlows WaterSight TechNotes and FAQ's.