CA Department of Water Resources · ZSRR. Enterprise-wide Data Access – for Maintenance and Analysis. Time Series data, Stores tag values, interfaces. Data aggregation. Data Hierarchy,

Wonderware and Historian Implementation on the CA State Water Project

CA Department of Water Resources

© 2019 AVEVA Group plc and its subsidiaries. All rights reserved.

Presented by: Steve BallardControl Systems Branch, Senior Control Engineer (Supv.)

October 1, 2019 v1.0

For Internal and Partner Use Only

TopicsCA DEPT. OF WATER RESOURCES

Wonderware and Historian Implementation on the CA State Water Project

State Water Project Overview

Historians – Tier 1’s and Tier 2

Data Sharing from Global Historian

Integration with other Systems

Plant Protection and DNP3

Information Portal – InTouch Access Anywhere

Enterprise-wide Data Access – for Maintenance and Analysis



State Water Project Overview Facilities


• 36 storage facilities, reservoirs and lakes• 21 pumping plants• 4 pumping generating plants• 5 hydroelectric power plants• 26 dams• 66 gate control sites on main canal (check-sites)• 115 other control and monitoring sites (turnouts, inlets,

outlets, reservoirs, canal branch locations)• 705 miles of open canals, tunnels and pipelines.

For more information, visit: http://www.water.ca.gov/

“The Big Lift” - Edmonston

Lake Oroville


State Water Project Overview Facts & Figures


• Provides water supplies for 27 million Californians and 750,000 acres of irrigated farmland.

• Largest state-built water and power development and conveyance system.

• 75% goes to urban users and 25% goes to agricultural users.

• Completion in late 1960’s up to San Luis reservoir

• Over the Tehachapi's in 1973 (Hwy 5 grapevine region). Edmonston Pumping Plant

• East Branch Extension Phase 1 2003 (San Bernardino and Riverside counties)

• For more information, visit: http://www.water.ca.gov/

http://www.water.ca.gov/


CA SWP29 Water Contractors

Service Areas





State Water Project Overview


• 5 Field Divisions• 5 Area Control Centers

• 1 per Field Division• 1 Operations Center

• Controls SWP from Central Location (Alstom)• Wonderware System Platform

• 4 Galaxies (Current 16K I/O….total will be ~40K)• 51 HMIs• 13 AOS• 6 Historians (1 Global) • 1 WIS – Data Share to Biz Partners• DEV & QA systems too.

• 340 Controllers (50% New PLCs, 50% old RTUs due for replacement in the next 5-7 years)

Oroville

Delta

San Luis

San Joaquin

Southern

Operations Center


Wonderware System Overview Role and Functionality


• Primary System for backup control to main “execution” SCADA System

• Contains ALL the detailed data for maintenance and analysis

• Sequence of Event Data for Troubleshooting

• Data Source for Local and Global Historians

• Supports Business Interfaces and Data Provisioning to business partners





Wonderware System Overview


Topics


• State Water Project Overview

• Historians

• Data Sharing with Business Partners

• Integration with other Systems

• Plant Protection and DNP3

• Wonderware Information Server

• Enterprise-wide Data Access – for Maintenance and Analysis



• Data Requirements• Definition and Rationalization• Summary Statistics, State

Summaries• Equipment Runtimes• Flows, Volumes• Operational Availability

Reports• Environmental Reports• Water Demand Scheduling

and modeling

16,000

15,500

16,200

17,000

28,000

4,500

~93K Tier 1 - 4,500 Tier 2

88,000 Kept in Locals

Tier 2 Tier 1’s

INFOSERVER

Historians




• Historians







Data Sharing with Business Partners• Users develop own ways to get data – creates “silos”

• Many options to choose from

• Business and Functional Requirements support design

• User’s Data Requirements define parameters

Tier 1’s

Tier 2

SQL Server

Water Contractors

Power Scheduling Office

Environmental Reporting

Water Management Office

B.I.D.S.


Topics



• Historians







System Platform & Device Integration used to Support SCADA Upgrades


The Situation:• Aging ARINC DCS system, no longer supported, no spare parts, increasing failures• Needed solution to:

• retire old system until new controllers can be installed over the next 5+ years• save data to new Wonderware Local and Global Historians

• Legacy InTouch used as the Plant’s secondary, standalone SCADA system• Both systems collected important SOE (sequence of events) millisecond data• Both used different, custom protocol drivers

Old Controllers

Legacy InTouch

Old SCADA (ARINC)Custom Drivers

New SCADA(Alstom)

(Data historized locally)

Custom

Data Link




Custom

Data Link

Solution:• Implement Redundant DIO Servers as Protocol Translators to:

• Collect data from old controller protocol (driver used on Legacy InTouch)• Translate or re-map data to new protocol (using Wonderware scripting)• Send Data to new, upgraded system via standard protocol (Modbus TCP)

• Convert Legacy InTouch Applications to Managed Applications to:• Update and deploy from Galaxy the InTouchViewApp objects in System Platform• Get data into Historians on the SCADA network so Enterprise can access data

Old Controllers

Legacy InTouch

Old SCADA (ARINC)Custom Drivers

New SCADA(Alstom)

(Data historized locally)

RDIOModbus

1 commondriver

ManagedViewApp

Historian




Benefits• Able to use commercial-off-the-shelf solution• Use built-in functionality such as Redundant I/O Servers• Minimizing complexity enables existing and future staff quicker ramp-up time on

acquiring the knowledge and skills required to maintain and support the system.• Updates legacy InTouch systems to common version of Wonderware implemented

throughout the SWP. Updates to new operating systems for meeting cyber security requirements.

• Positions each system in a stable environment until new controllers can be installed.



Topics• State Water Project Overview

• Historians








• Intelligent Electronic Devices

• Sequence of Event (millisecond) Data for troubleshooting and analysis.• Data Selection Criteria and Requirements• Operational Availability, Service Rates Reporting

DNP3 and Protection Relays



IDE

DNP3 I/O Server

DNP3 and Protection Relays




• Historians




• Information Portal – InTouch Access Anywhere




InTouch Access Anywhere





• SQL Server Reporting Services

• Alarm Reporting from central location.

• Wonderware Alarm Databases in Local and Global Historians

• ANSI/ISA 18.2 Management of Alarm Systems

• Monitoring and Assessment, Audit Life Cycle.

InTouch Access Anywhere




• Historians




• Information Portal – InTouch Access Anywhere




Down-loadfile

Down-loadfile

Down-loadfile

Screenscrape

Screenscrape

Browser

HTTP/XML

Trans-action

file

Trans-action

file

Trans-action

file

Trans-action

file

Messagequeue

Messagequeue

Messagequeue

FTP

SocketsE-mail

Message

XML/HTTP

Gateway RPC

CICS gateway

APPC

SMTP

CICS gateway

ORB

LegacyApplications

PurchasedPackages

External Partners

External Sources

End UserDevelopment

AutonomousDivisions

Outsourced andASP

Applications

Enterprise-wide Data Access – for Maintenance and AnalysisComplex Mix of Applications, Sources and Users – Untangling “The Octopus”



1. Complex interfaces are required between systems2. Management reports can be inconsistent and may affect the department’s credibility3. Management reports may not be readily available.4. Data is not available to all those who need it5. Data is extracted and stored for exclusive use by the extracting system or users6. Multiple extractions create redundant data stores that are not synchronized7. Data is extracted from the source system and stored within the control of individual systems8. Distinct systems acquire, store and update data independently, causing data to be out of sync9. Extra resources are required to maintain data10.Extra resources are required to maintain and run data exports and edit applications11.System changes are cumbersome and risky

Enterprise-wide Data Access – for Maintenance and AnalysisAs-Is: Concerns / Issues for Data Collection and Sharing



1. Data is “stove-piped” or “data silos” which leads to inefficient data sharing

2. Focus on data as an enterprise, not narrow business area/divisions

3. Large amount of unplanned, redundant data that is collected and/or processed more than once

4. Data from legacy applications needs to be retained and managed into the future data sources

5. Data from legacy applications needs to be merged into new systems

6. Data that might be useful to another system or group of people is sometimes deleted without any notice

7. Too many ways of bringing data in and not easily integrated.

Enterprise-wide Data Access – for Maintenance and AnalysisSummary of Findings



Reporting, and Analytical layer(Business choice)

Data Sources

Data Preparation, Integration, and Aggregation Layer

Users

Users

UsersData Analytics

Tool DashBoards

Users

Reports

Future Database

FTP Server

External Data

SAP SCADA

Video/ Surveillance

Data

Piezometer, inclinometer

Survey dataTopographical

dataBoring logs

EDMS

LISPOrca OperationsGADS

ZFMCTZSRR

Enterprise-wide Data Access – for Maintenance and Analysis

Time Series data, Stores tag values,

interfaces

Data aggregation

Data Hierarchy, Relational Data

Engine

Data analysis engineData preparation, data

integrationData Backup


Thank-you!

Please visit www.water.ca.gov


[email protected]

http://www.water.ca.gov/

Documents

CA Department of Water Resources · ZSRR. Enterprise-wide Data Access – for Maintenance and Analysis. Time Series data, Stores tag values, interfaces. Data aggregation. Data Hierarchy,