SCADA

Current State
and
Perspective
 Overview

 What is SCADA (compared with DCS systems)

 Where and Why are SCADA systems used
 What do SCADA systems Provide?
 Evolution
 Benefits
 Experience
 Outlook
Traditional Control
Traditional Control 2nd

 Dedicated Consoles
 Point to point communication
 No network
 No remote access
 No remote diagnostic
Distributed Control

Network Protocol
PLC’s

Field Bus

Field Bus-Integrator
Distributed Control 2nd

 Advantages:
 Distributed databases/ programs created from a single
development environment (also in front end processor)
 Distributed access
 Distributed diagnostic
 Display ‘everything everywhere’

 Disadvantages:
 None of the DC systems are compatible to each other

 Difficult:
 Integration of various field bus components
 SCADA
SC ADA ?
SCADA ?
Supervisory And Data
Control Acquisition
Archiving, Logging,
Graphics and Batch processing Access Control, Alarms

Distributed database
Data Server Data Server PLC’s

Field Bus
Control Programs
 What, Where and Why
 What is “SCADA”and where is it used
 Supervisory Controls And Data Acquisition
 Application area :
 Industrial processes: chemical, power generation and distribution,
metallurgy, …
 Nuclear processes: reactors, nuclear waste, ...
 Experimental physics: Tokamaks, HEP laboratories
 Application size:
 20 K I/O to 450 K I/O, two examples of 1 M I/O under development
 Why SCADA systems were evaluated for LHC SLC ?
 Reduction of resources
 CERN policy of “outsourcing”
What do SCADA Provide?

 Flexible and open architecture

 Basic SCADA functionality
 MMI
 Alarm Handling and Trending
 Access Control
 Automation
 Logging, Archiving, Report Generation
 Interfaces to H/W and S/W
 Development Tools
 Generic Software Architecture
SCADA Client Active X
Graphics
Tren- Alarm Log Controls
ASCII Editor MMI Active X
File ding Display Display
Editor Container
SCADA Developt. Environt.

Library Client / Server - Publish / Subscribe - TCP/ IP

Recipe SCADA Server
ASCII RT & Event Manager
DB
Files Report
Export Recipe Data Alarm Log Archive
/ Gener.
Managt Proces
Import
Commercial RT SQL Alarm DB Log DB Archive DB
Ref. DB
DB
Project DB ODBC
Editor Data DDE
Commercial
R/W API/DLL
Devel. Driver
Private
tool Toolkit Driver OPC EXCEL
Application

VME PLC PLC

SCADA functions (1): MMI
 SCADA functions (2)

 Alarm Handling
 Based on limit and status checking *
 More complicated expressions developed by creating
derived parameters *
 Alarms are time stamped and logically centralised *
 Notifications (audible, visual, Email, GSM)
 Multiple alarm priority levels
 Grouping of alarms and handling of groups is possible
 Suppression and masking of alarms either individually or as
a complete group
 Filtering of alarms is possible
 SCADA functions (3)
 Trending
 Multiple trending charts
 Charts are pre-defined or configured on-line
 Charts contain multiple pens,
 Zooming, scrolling, panning, ‘Hairline’
 Real-time and historical trending
 SCADA functions (4)

 Access Control
 Users organised in groups with a set of allocated privileges
 Large number of groups possible
 Privileges limit write access to process parameters
 Some allow access to graphics and functionality to be limited
 Automation
 Actions can be initiated automatically triggered by an event *
 Recipes
 Sequencing and scripting possibilities
 SCADA functions (5)

 Logging, Archiving
 Data stored in compressed and proprietary format
 Logging / Archiving either for a set number of parameters or
for a set period of time
 Logging / Archiving can be frequency or event driven *
 Logging of user actions together with a user ID
 VCR facility for playback of stored data
 Report Generation
 Reports created using SQL type queries to the RTDB or logs
 Automatic generation, printing and archiving of reports
 Use of ‘components’ for report generation
 Interfaces to H/W and S/W

 H/W
 Multiple communication protocols supported in a single
system (in particular CERN supported Field busses)
 Support for major PLCs/DCSs but not VME
 S/W
 API
 ODBC, DDE and OLE I/F to PC Products
 OPC Client
 ActiveX Containers
 Web clients
 Development Tools

 Project editor
 Graphics editor
 Configuration through parameter templates
 Scripting language
 Driver Development Tool Kit
 Evolution

 Frequent new versions

 From “tag/ channel-based” to “device oriented”
 Multi-team development
 Web technology, Active X, Java, etc.
 OPC for internal communication
 Etc
 Why is OPC Data Access needed?

Display Trend Report

Application Application Application

Software Software Software Software

Driver Driver Driver Driver
 How does OPC Solve the Problem?

Display Trend Report

Application Application Application

OPC OPC OPC

OPC OPC OPC OPC

Software Software Software Software
Driver Driver Driver Driver
 Where does OPC Data Access Fit?

OPC (via DCOM)can also

be used between subsystems
and Management Consoles

Data Monitor
OPC is generally used SubSystem
between Monitoring
applications and I/O specific OPC Low level sensors
software drivers Typically use a dedicated
Device Specific Hardware Interface and protocol
I/O Control
 Benefits of SCADA

 Standard frame for application

 Rich functionality (50 - 100 p-yrs investment)
 Reliability and Robustness (very large installed base,
mission critical processes)
 Limited specific development
 Technical support and maintenance
 ….. Etc
 Let’s go for it ! ???
Let’s go for it !
More Aspects to take into Account:
 Configuration of SCADA Systems
 Data Access Mechanism’s

DESY Experience:
 Namespace: flat vs. OO
 System Load
 Network
 Processor
 Project Management
Configuration
of SCADA Systems

Data Server Data Server PLC’s

Different Namespaces!!
 Configuration
PLC SCADA
of SCADA Systems 2nd
Programs
Communication
Processor
•Analog-Input •Analog-Input
•Value-AI-0 •Vacuum_VALUE
•Value-AI-1 •Pressure_VALUE
•Analog-Output Mapping •Analog-Output
•Value-AO-0 •Valve_1_OUT
•Value-AO-1 •Heater_1_OUT
Field Bus
 Configuration
of SCADA Systems 3rd (Alarms)

SCADA
Data Server Alarm Generation
•Analog-Input (generic) Alarm scripts:
•Vacuum_VALUE
•Pressure_VALUE IF (Pressure_VALUE > Pressure_HIHI_ALARMVAL)
•Analog-Output {Pressure_ALARM_HIHI=TRUE
Pressure_ALARM_STATE=CRITICAL
•Valve_1_OUT Pressure_ALARM_COLOR=RED }
•Heater_1_OUT IF (Pressure_VALUE < Pressure_LOLO_ALARMVAL)
{Pressure_ALARM_LOLO=TRUE
Pressure_ALARM_STATE=ATTETION
Pressure_ALARM_COLOR=BLUE }
Winnings !!!
How many individual Tags did I create
up to now in my example?

4 8 10 17
•Vacuum_VALUE Pressure_VALUE
•Pressure_VALUE Pressure_HIHI_ALARMVAL
•Valve_1_OUT Pressure_ALARM_HIHI Pressure_ALARM_STATE
Pressure_ALARM_COLOR
•Heater_1_OUT
4 Pressure_VALUE 4
Pressure_LOLO_ALARMVAL
Pressure_ALARM_LOLO
Pressure_ALARM_STATE
Pressure_ALARM_COLOR

2
 Data Access Mechanism's
Alarm Server
 Alarm Server typically poll
data from the data server
( -> impact on network bandwidth)
Data Server
Polling

Po
 Data from field buses are

lli
n
mainly polled

g
Asynchronous protocols are difficult
to handle
Field Bus
Experience 1st

 Namespace
 Individual tags for each property blow up the namespace
 Flat namespaces of thousands of tags can not be properly
handled without adequate tools
 Latest SCADA technology clearly shows the trend to support
the definition of objects which cleans up the namespace
 System Load
 Additional –non standard- features like
 calculating alarms for each channel
 temperature conversions ( 6th grade polynomial)
... can cause a lot of overhead which needs to be taken into
account for the calculation of the system load on process
controllers ( here: in a SCADA-like DCS system)
Experience 2nd

 Project Management
 Small systems can be easily handled with in-house personal
 Big systems (several thousand of channels) should be
coordinated by an engineering office because of:
 The coordination of the Field Bus (PLC) databases and the
SCADA databases
 The knowledge of the various tools which come along with a
SCADA system
 One of the main arguments for SCADA systems is: outsourcing
 Let’s go for it ! ???
Let’s go for it ! ???
 Utility controls @ DESY use EPICS as a SCADA system

 H1 is going to use PVSS for their slow controls

 There‘s no alternative for big projects like TESLA

 Various subsystems can be controlled by SCADA systems:
 Utility Controls (water, energy, air, heating...)
 Cryogenic Controls (cryogenic plants, cryogenic distribution)
 Vacuum Systems (insulation vacuum, beam vacuum)
 Special developments i.e. for RF control should have a ‚SCADA-aware‘ design
 Is SCADA the only Future ? ...
New Technology: JetWeb
Each node is an individual Web Server
All nodes and all I/O hooked up to the Ethernet

... probably not, but a very attractive one.

That’s all
Folks
 SCADA functionality (1)

 MMI
 Library of "generic" symbols with TAG links
 Dynamic linking of parameters to graphics
 On-line configuration and customisation of MMI
 Links can be created between display pages
 Animation and multimedia facilities
SCADA functions (2): Alarm Handling
SCADA functions (3): Trending
 SCADA related Engineering:
Examples

 Define:
 hierarchies and partitions and their distribution over the network
 user groups and their access rights
 naming convention for devices, etc.
 library of objects (PLC, devices, subsystems, ...)
 templates for different categories of "panels"
 mechanism to prevent conflicting controls (if not provided with the
SCADA)
 alarm levels, behaviours,
 etc.
 Hardware Architecture

Dedicated
Client Client Server

Ethernet

Data Data
Server Server

Fieldbus Fieldbus

Con- Con-
troller Con- Con- Con-
troller
troller troller troller