SEMINAR REPORT ON SCADA Submitted For Partial Fulfilment of Awa BACHELOR OF TECHNOLOGY Degree In Electronics & Communication Engineerin Submitted to: Submitted by: Mr. AMIT BINDAL ASHUTOSH KR. MAURYA Assistant Professor ECE - 4 th Year ECE Department (0712831028) 1
SCADA Submitted For Partial Fulfilment of Award Of BACHELOR OF TECHNOLOGY
Degree In Electronics & Communication Engineering
Submitted to: Mr. AMIT BINDAL Assistant Professor ECE Department
Submitted by: ASHUTOSH KR. MAURYA ECE - 4th Year (0712831028)
BHARAT INSTITUTE OF TECHNOLOGY BY-PASS ROAD, PARTAPUR MEERUT ,U.P NOVEMBER, 2010
1
ACKNOWLEDGEMENT I to E E guid n I xpr ss ould lik to th nk v ryon o pl tion In p rti ul r, G ys V I ho h lp d to s ould lik to this s th nk
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SEMINAR REPORT
ON
SCADA
Submitted For Partial Fulfilment of Award Of
BACHELOR OF TECHNOLOGY
Degree
In
Electronics & Communication Engineering
Submitted to: Submitted by:
Mr. AMIT BINDAL ASHUTOSH KR. MAURYA
Assistant Professor ECE - 4th Year
ECE Department (0712831028)
BHARAT INSTITUTE OF TECHNOLOGY
BY-PASS ROAD, PARTAPUR
MEERUT ,U.P
NOVEMBER, 2010
1
2
ACKNOWLEDGEMENT
I would like to thank everyone who helped to see this seminar
to completion. In particular, I would like to thank my
ECE HOD Mr. P.K.RAGHUVANSHI for his moral support and
guidance to complete my seminar on time.
I express my gratitude to all my friends and classmates for their
support and help in this seminar.
Last but not the least I wish to express my gratitude to God
almighty for his abundant blessings without which this seminar
would not have been successful.
ASHUTOSH KUMAR MAURYA
ECE-4th year
0712831028
3
CONTENTS
Topic Page No.
Introduction 5
What is data acquisition? 6
Why or where we use SCADA? 7
Architecture 8
Communication 9
Interfacing 10
Database 11
SCADA as a system 12
Example of SCADA system 13
Human Machine Interface 14
Remote Terminal Unit 15
Central Root Computer 15
System Concept 15-16
Features of SCADA 17-18
Usefulness of SCADA 19-20
General terminology 21-23
Security Issues 24
What is Intouch 25
4
Key Benefits 26
Key Capabilities 26
SCADA as an asset 27
SCADA System Management 28
SCADA a boom in engineering 29
Practical uses of SCADA 29
Advantages of SCADA 30
SCADA Manufacturer 31
Conclusion 32
References 33
INTRODUCTION:
5
SCADA stands for Supervisory Control And Data Acquisition. SCADA refers to a system that collects data from various sensors at a factory, plant or in other remote locations and then sends this data to a central computer which then manages and controls the data. SCADA focuses on gathering and circulating the right amount of system information to the right person or computer within the right amount of time so that creative solutions are made possible.
The keyword supervisory indicates that decisions are not directly made by the
system. Instead, the system executes control decisions based on control
parameters entered by the agency staff. The system monitors the health of the
process and generates alarm notifications when conditions are out of tolerance.
It is also tasked with placing the process in a safe mode. It waits for user inputs
to correct problems. The supervisory mode is designed to operate the system in
a manner that avoids out of tolerance conditions. In a water / wastewater
process, pumps are started and stopped by the system according to limits
assigned by operations. As long as the system responds correctly to the control
commands, the system remains in control. It includes three processes.
● Industrial processes include those of manufacturing, production, power
generation, fabrication, and refining, and may run in continuous, batch,
repetitive, or discrete modes.
●Infrastructure processes may be public or private, and include water
treatment and distribution, wastewater collection and treatment, oil and gas
pipelines, electrical power transmission and distribution, civil defense siren
systems, and large communication systems.
●Facility processes occur both in public facilities and private ones,
including buildings, airports, ships, and space stations. They monitor and
control energy consumption.
WHAT IS DATA ACQUISITION?
6
Data acquisition is the process of retrieving control information from the
equipment which is out of order or may lead to some problem or when decisions
are need to be taken according to the situation in the equipment. So this
acquisition is done by continuous monitoring of the equipment to which it is
employed. The data accessed are then forwarded onto a telemetry system ready
for transfer to the different sites. They can be analog and digital information
gathered by sensors, such as flow meter, ammeter, etc. It can also be data to
control equipment such as actuators, relays, valves, motors, etc.
WHY OR WHERE WE USE SCADA?
7
SCADA can be used to monitor and control plant or equipment. The control
may be automatic, or initiated by operator commands. The data acquisition is
accomplished firstly by the RTU's (remote Terminal Units) scanning the field
inputs connected to the RTU (RTU’s may also be called a PLC - programmable
logic controller). This is usually at a fast rate. The central host will scan the
RTU's (usually at a slower rate.) The data is processed to detect alarm
conditions, and if an alarm is present, it will be displayed on special alarm lists.
Data can be of three main types. Analogue data (i.e. real numbers) will be
trended (i.e. placed in graphs). Digital data (on/off) may have alarms attached to
one state or the other. Pulse data (e.g. counting revolutions of a meter) is
normally accumulated or counted.
These systems are used not only in industrial processes. For example,
Manufacturing, steel making, power generation both in conventional, nuclear
and its distribution, chemistry, but also in some experimental facilities such as
laboratories research, testing and evaluation centers, nuclear fusion. The size of
such plants can range from as few as 10 to several 10 thousands input/output
(I/O) channels. However, SCADA systems evolve rapidly and are now
penetrating the market of plants with a number of I/O channels of several 100K.
The primary interface to the operator is a graphical display (mimic) usually via
a PC Screen which shows a representation of the plant or equipment in
graphical form. Live data is shown as graphical shapes (foreground) over a
static background. As the data changes in the field, the foreground is updated.
E.g. a valve may be shown as open or closed. Analog data can be shown either
as a number, or graphically. The system may have many such displays, and the
operator can select from the relevant ones at any time. SCADA systems were
first used in the 1960s.
ARCHITECTURE
8
In this section we are going to details which describe the common architecture
required for the SCADA products
Hardware Architecture
The basic hardware of the SCADA system is distinguished into two basic
layers: the "client layer" which caters for the man machine interaction and the
"data server layer" which handles most of the process data control activities.
The data servers communicate with devices in the field through process
controllers. Process controllers, e.g. PLC’s, are connected to the data servers
either directly or via networks or fieldbuses that are proprietary (e.g. Siemens
H1), or non-proprietary (e.g. Profibus). Data servers are connected to each other
and to client stations via an Ethernet LAN. Fig.1. shows typical hardware
architecture.
Figure 1: Typical Hardware Architecture
Communication
9
Internal Communication:
Server-client and server-server communication is in general on a publish-
subscribe and event-driven basis and uses a TCP/IP protocol, i.e., a client
application subscribes to a parameter which is owned by a particular server
application and only changes to that parameter are then communicated to the
client application.
Access to Devices:
The data servers poll the controllers at a user defined polling rate. The polling
rate may be different for different parameters. The controllers pass the requested
parameters to the data servers. Time stamping of the process parameters is
typically performed in the controllers and this time-stamp is taken over by the
data server. If the controller and communication protocol used support
unsolicited data transfer then the products will support this too.
A single data server can support multiple communications protocols; it can
generally support as many such protocols as it has slots for interface cards. The
effort required to develop new drivers is typically in the range of 2-6 weeks
depending on the complexity and similarity with existing drivers, and a driver
development tool kit is provided for this.
Interfacing
10
Application Interfaces / Openness
The provision of OPC client functionality for SCADA to access devices in an
open and standard manner is developing. There still seems to be a lack of
devices/controllers, which provide OPC server software, but this improves
rapidly as most of the producers of controllers are actively involved in the
development of this standard.
The products also provide
an Open Data Base Connectivity (ODBC) interface to the data in the
archive/logs, but not to the configuration database,
an ASCII import/export facility for configuration data,
a library of APIs supporting C, C++, and Visual Basic (VB) to access
data in the RTDB, logs and archive. The API often does not provide
access to the product's internal features such as alarm handling, reporting,
trending, etc.
The PC products provide support for the Microsoft standards such as Dynamic
Data Exchange (DDE) which allows e.g. to visualize data dynamically in an
EXCEL spreadsheet, Dynamic Link Library (DLL) and Object Linking and
Embedding (OLE).
Database
11
The configuration data are stored in a database that is logically centralized but
physically distributed and that is generally of a proprietary format. For
performance reasons, the RTDB resides in the memory of the servers and is also
of proprietary format. The archive and logging format is usually also proprietary
for performance reasons, but some products do support logging to a Relational
Data Base Management System (RDBMS) at a slower rate either directly or via
an ODBC interface.
Scalability
Scalability is understood as the possibility to extend the SCADA based control
system by adding more process variables, more specialized servers (e.g. for
alarm handling) or more clients. The products achieve scalability by having
multiple data servers connected to multiple controllers. Each data server has its
own configuration database and RTDB and is responsible for the handling of a
sub-set of the process variables (acquisition, alarm handling, archiving).
SCADA AS A SYSTEM
12
A SCADA System usually consists of the following subsystems:
A Human-Machine Interface or HMI is the apparatus which
presents process data to a human operator, and through this, the human
operator monitors and controls the process. A supervisory (computer)
system, gathering (acquiring) data on the process and sending commands
(control) to the process.
Remote Terminal Units (RTUs) connecting to sensors in the
process, converting sensor signals to digital data and sending digital data
to the supervisory system.
Programmable Logic Controller (PLCs) used as field devices
because they are more economical, versatile, flexible, and configurable
than special-purpose RTUs.
Communication infrastructure connecting the supervisory
system to the Remote Terminal Units.
A SCADA system could be programmed to:
monitor high and low levels in the day tanks,
fill them when a certain level is reached,
calculated and store the volume used,
monitor the level in the main feed tank,
Alarm when a certain level is reached to notify purchasing (or send an e-
mail),
Plot the usage of chemicals vs time, process, or any other parameter.
13
TYPICAL SCADA SYSTEM
Example of scada system
14
HUMAN MACHINE INTERFACE
A HMI is the apparatus which presents process data to a human operator, and
through which the human operator controls the process.
HMI's are an easy way to standardize the facilitation of monitoring multiple
RTU's or PLC's (programmable logic controllers). Usually RTU's or PLC's will
run a pre programmed process, but monitoring each of them individually can be
difficult, usually because they are spread out over the system. Because RTU's
and PLC's historically had no standardized method to display or present data to
an operator, the SCADA system communicates with PLC's throughout the
system network and processes information that is easily disseminated by the
HMI.
HMI's can also be linked to a database, which can use data gathered from PLC's
or RTU's to provide graphs on trends, logistic info, schematics for a specific
sensor or machine or even make troubleshooting guides accessible.
REMOTE TERMINAL UNIT
The RTU connects to physical equipment. Typically, an RTU converts the
electrical signals from the equipment to digital values such as the open/closed
status from a switch or a valve, or measurements such as pressure, flow, voltage
or current. By converting and sending these electrical signals out to equipment
the RTU can control equipment, such as opening or closing a switch or a valve,
or setting the speed of a pump. The RTU can read digital status data or analogue
measurement data, and send out digital commands or analogue setpoints.
An important part of most SCADA implementation arealarms. An alarm is a
digital status point that has either the value NORMAL or ALARM.