SCADA Run

Introduction to SCADA

The SCADA tab provides the ability to run simulations that take into account the conditions measured within the distribution network via the Supervisory Control and Data Acquisition (SCADA) system.  

A SCADA system stores information useful for network many modeling applications. This system compiles both real-time and historical operational data for local and remote facility sites. Such information is useful to define input data conditions for InfoWater Pro including loading conditions in temporal format for pressure zone and system demands, boundary conditions for reservoir and tank water levels, as well as pipe status and pump and control valve settings. The SCADA output for pressure and flow measurements can also be used in model calibration to verify the reliability of the model results. The ability to interface with SCADA systems can offer a number of benefits including at a minimum:  

These benefits can only be realized if both systems communicate properly with one another, so that information gathered by the SCADA system can be shared with InfoWater Pro and could be used in simulation runs. The intent is to update InfoWater Pro with the most recent SCADA data.  

The best way to integrate InfoWater Pro securely with SCADA data is through Info360. This approach involves pushing encrypted data to the Info360 cloud for data cleanup, processing, and visualization. InfoWater Pro can use this data on-demand for simulations and publish results back to Info360 dashboards for comparison and review.  

The alternative is to manually create SDA files which are used in the engine to enforce boundary conditions on the model based on sensor data.  

SCADA Tab

SCADA tab is available in the Run manager window, which allows you to create a simulation based on SCADA data.

Fields Descriptions
Demand Adjustment Method

Select the appropriate option here and then enter the value in Demand Adjustment Factor field.

Show More
Scaling Factor Scale the junction node demands according to a user defined scaling factor.  The scaling factor is specified in the Demand Adjustment Factor entry field.  For example, if the total system demand for all junctions is 1200 unit (at the specified Pattern Start Time) and the Demand Adjustment Factor is set to 5, then all junction demands will be multiplied by 5 to give a total system demand of 6000 unit.
Total System Demand Divide the value specified in the Demand Adjustment Factor by the existing system demand (at the specified Pattern Start Time) and then multiply all junction node demands by the resulting ratio.  For example, if the value specified in the Demand Adjustment Factor is 800 gpm and the actual junction demand at hour 2:00 is 1000 gpm, then all junction nodes will be multiplied by the resulting ratio (0.8).
% Inflow / Outflow Adjust all junction nodes by the percentage value specified in the Demand Adjustment Factor to the difference between system inflows and outflows as specified from the SCADA System Data Edit.  For example, if 25 (25%) is entered into the Demand Adjustment Factor field, all junction demands (as computed from the difference between system inflows and outflows) will be multiplied by the percentage value entered into the Demand Adjustment Factor.  If the system inflow/outflow measurement option is chosen, the inflow/outflow measurement meters must first be configured using through the SCADA System Edit dialog box.
Demand Adjustment Factor

Specify the demand Adjustment factor. The factor will be dependent on the Demand Adjustment method and is a means to normalize the demands to reflect your true SCADA demands.

Info360   

When Info360 is selected in the SCADA Input Data File section, the SCADA Event Manager is used to control which timeseries event data from Info360 will be used in the simulation.  

  • Live Data Adapter – This button launches the Live Data Adapter which is used to manage the mapping between sensors and model elements.  
  • SCADA Event Manager – This will launch the SCADA Event Manager to configure events and select the active event for the run.  
  • Refresh boundary condition file from Info360 – When checked, timeseries data will be queried directly from Info360 prior to running the simulation. If unchecked, the existing data stored locally will be used.  
Browse SDA File  

When this option is selected in the SCADA Input Data File section, an SDA text file can be mapped directly to be used in the simulation.   

Note that any objects being controlled by the SDA File will need to have a SCADA Control setup ahead of time.  

Start Reporting fromSCADA Data Instant

When turned on, this option will delay all output reporting until the first timestep found in the SCADA file provided to the engine. In addition, the simulation will be extended to the final timestep reported in the SCADA file if necessary to span all measured data.

SDA File Example

When you select the Browse SDA File checkbox in the Run Manager dialog box, you can manually configure and map a SDA file to the simulation.

The following is an example of an SDA text file configured to update the initial conditions of several objects and modify the status of two pumps at hour 4.

After stating the time and day in your SDA file, controls are listed by stating the Keyword, Sensor ID, and Value.

Sensor ID’s must be defined for each model object using the SCADA Control definition, as shown below.

The following Keywords can be used in the SDA file:

Keyword

Control Action

Reservoir_Control

Update reservoir level

Tank_Control

Update tank level

Pump_Control_Status

Update the status of the pump

Pump_Control_Speed

Update the speed setting on the pump

Valve_Control

Update the setting of the valve

Parent topic: Running a Model