Академический Документы
Профессиональный Документы
Культура Документы
COMPANY PROFILE
Founded in 1997, with the vision of "Best quality high end training on
automation platforms and Components (PLCs /SCADA /DCS /Drives
/Instrumentation /Electricals /networking) to serve 2 noble purposes – Cost effective
job oriented training for needy engineering graduates and upgrading skill levels of
working professional in manufacturing industry". Prolific services enterprises and
individuals in over 20 Indian cities with its wide ranging knowledge based learning
solutions in Automation industry. Prolific strength stems from its well accepted
expertise in providing turnkey automation solutions. Brief Background of prolific is
professionally run company established by technocrats with several years of
experience in the automation industry and embedded systems. Prolific is one of the
leading turnkey automation solution provider and the largest Indian advanced training
provider in the areas of automation systems and embedded systems. Prolific has fully
equipped facilities at OVER 20 KEY LOCATIONS
IN INDIA. Prolific - India's largest automation training company In order to cater to
Indian industry's demand for skilled technical manpower in high-end technologies,
Prolific established the Training division that imparts advanced technology training,
currently, in the areas of control systems, instrumentation and embedded systems.
Prolific also provides corporate training. Prolific generic teaching methodology and
focus on practical training has helped it gain strong foothold in Indian industry.
PLCs
SITE NATHDWARA Page 1
IV YEAR 2011-12 PLC, SCADA
Instruments
All kinds of instruments used in temperature, pressure, flow, pH, weight, speed
measurement and control
Embedded Systems
Microcontrollers, Embedded C programming
1. INTRODUCTION
provide means to eliminate high cost associated with inflexible, conventional relay
controlled systems. Programmable controllers offer a system with computer
flexibility:
1.3-DEFINATION OF PLC
2.PLC ARCHITECTURE
memory, which are PROM or ROM and RAM chips. It is, however, much easier to
change a program when a different process is required than to rewire the control
system. For example, it may take electricians a couple of weeks to require a pipe
mill, whereas a programmer will spend only a fraction of this time to reprogram a
PLC since no wires will have to be changed. In addition, various recipes can be
stored in memory and accessed when required, making the program extremely
flexible.
The system operates through interaction with the processor and program
memory. When the power to the system is turned on, the processor reads the first
instruction stored in memory and acts on this instruction. When completed, it goes
back to the memory for the next instruction, and so on until task is complete. This
operation is called the fetch-execute cycle. The processor communicates with the
outside world via input and output modules.
1. Input/output Section
The I/O section contains input modules and output modules. Functionally,
the input modules are equivalent to the signal converters (i.e. Analog to Digital or
high power to low power). All modern PLC input modules use optical devices to
accomplish electrically isolated coupling between the input circuit and the processor
electronics.
Each input device is wired to a particular input terminal on the I/O
section. Thus if the switch is closed, 5v dc appears on input terminal, converts this dc
voltage to a digital 1 and sends it to the processor via programmable peripheral
interface (PPI). Conversely, if the switch is open, no dc voltage appears on input
terminal. Input section will respond to this condition by sending a digital 0 to the
processor. The other input terminals behave identically.
2. The Processor
The processor of a PLC holds and executes the user program. In order to
carry out this job, the processor must store the most up-to-date input and output
conditions.
When the CPU is executing an instruction for which a certain data value
must be known, that data value is brought in from data memory. When the CPU
executes an instruction that provides a numerical result, that result is put out into data
memory. Thus, CPU can read from or write to the data memory. Understand that this
relationship is different from the relationship between the CPU and the user program
memory. When the user program is executing, the CPU can only reads from the user
program memory, never write to it.
This O.S. makes supervision over entire system, so O.S. programs are
said to running in supervisory mode.
When the user completely enters his program in user memory, he transfers
control from PROGRAM mode to RUN mode. In RUN mode the control of the
whole system is transferred to operating system. Now operating system takes care of
the whole system such that the whole system becomes automatic and appears as
magic to users.
4. SOFTWARE DESCRIPTION
This chapter explains how to program the PLC. It describes how to write
a program, how the program is structured and representation of the programming
language.
Writing a Program:
A control program specifies a series of operations that tell the
programmable controller how it has to control a system. For example, a control
program might be the series of operations that tell the PLC how to use open loop
control or close loop control for a specific system. We must write the program in a
specific programming language and according to some specific rules so that the
programmable controller can understand it.
Method of Representation:
5. APPLICATIONS OF PLC
1. The batch processes in chemical, cement, food and paper industries which
are sequential in nature, requiring time of event based decisions is
controlled by PLCs.
2. In large process plants PLCs are being increasingly used for automatic
start up and shut down of critical equipment. A PLC ensures that
equipment cannot be started unless all the permissive conditions for safe
start have seen established. It also monitors the conditions necessary for
safe running of the equipment and trips the equipment whenever any
abnormality in the system is detected.
3. The PLC can be programmed to function as an energy management system
for boiler control for maximum efficiency and safety.
4. In automation of blender recliners
5. In automation of bulk material handling system at ports.
6. In automation for a ship unloaded.
7. Automation for wagon loaders.
SCADA
SUPERVISORY CONTROL AND DATA ACQUISITION
6. INTRODUCTION
SCADA is an acronym for Supervisory Control and Data Acquisition.
SCADA systems are used to monitor and control a plant or equipment in industries
such as telecommunications, water and waste control, energy, oil and gas refining and
transportation. These systems encompass the transfer of data between a SCADA
central host computer and a number of Remote Terminal Units (RTUs) and/or
Programmable Logic Controllers (PLCs), and the central host and the operator
terminals. A SCADA system gathers information (such as where a leak on a pipeline
has occurred), transfers the information back to a central site, then alerts the home
station that a leak has occurred, carrying out necessary analysis and control, such as
determining if the leak is critical, and displaying the information in a logical and
organized fashion.
These systems can be relatively simple, such as one that monitors
environmental conditions of a small office building, or very complex, such as a
system that monitors all the activity in a nuclear power plant or the activity of a
municipal water system. Traditionally, SCADA systems have made use of the Public
Switched Network (PSN) for monitoring purposes. Today many systems are
monitored using the infrastructure of the corporate Local Area Network (LAN)/Wide
Area Network (WAN). Wireless technologies are now being widely deployed for
purposes of monitoring.
SCADA systems consist of:
1. One or more field data interface devices, usually RTUs, or PLCs, which
interface to field sensing devices and local control switchboxes and valve
actuators
2. A communications system used to transfer data between field data interface
devices and control units and the computers in the SCADA central host. The
system can be radio, telephone, cable, satellite, etc., or any combination of
these.
3. A central host computer server or servers (sometimes called a SCADA Center,
master station, or Master Terminal Unit (MTU)
7. OVERVIEW OF SCADA
Types of SCADA
1. D+R+N (Development +Run + Networking)
2. R+N (Run +Networking)
3. Factory focus
Features of SCADA
1. Dynamic process Graphic
2. Alarm summery
3. Alarm history
4. Real time trend
5. Historical time trend
6. Security (Application Security)
7. Data base connectivity
8. Device connectivity
9. Scripts
10. Recipe management
Manufacture of SCADA
Modicum (Telemecanique) Visual look
Allen Bradley: RS View
Siemens: win cc
Gefanc:
KPIT: ASTRA
Intelution: Aspic
Wonderware: Intouch
8. ARCHITECTURE OF SCADA
SCADA systems have evolved in parallel with the growth and sophistication
of modern Computing technology. The following sections will provide a description
of the following three generations of SCADA systems:
• First Generation – Monolithic
• Second Generation – Distributed
• Third Generation – Networked
8.1 Monolithic SCADA Systems
When SCADA systems were first developed, the concept of computing in
general centered on “mainframe” systems. Networks were generally non-existent, and
each centralized system stood alone. As a result, SCADA systems were standalone
systems with virtually no connectivity to other systems. The Wide Area Networks
(WANs) that were implemented to communicate with remote terminal units (RTUs)
were designed with a single purpose in mind–that of communicating with RTUs in the
field and nothing else. In addition, WAN protocols in use today were largely unknown
at the time. The communication protocols in use on SCADA networks were
developed by vendors of RTU equipment and were often proprietary. In addition,
these protocols were generally very “lean”, supporting virtually no functionality
beyond that required scanning and controlling points within the remote device. Also,
it was generally not feasible to intermingle other types of data traffic with RTU
communications on the network.
Connectivity to the SCADA master station itself was very limited by the
system vendor. Connections to the master typically were done at the bus level via a
proprietary adapter or controller plugged into the Central Processing Unit (CPU)
backplane. Redundancy in these first generation systems was accomplished by the use
of two identically equipped mainframe systems, a primary and a backup, connected at
the bus level. The stand by system’s primary function was to monitor the primary and
take over in the event of a detected failure. This type of standby operation meant that
little or no processing was done on the standby system. Figure 3.1 shows a typical
first generation SCADA architecture.
nature, where the vendor created its own network protocol or version thereof rather
than pulling an existing one off the shelf. This allowed a vendor to optimize its LAN
protocol for real-time traffic, but it limited (or effectively eliminated) the connection
of network from other vendors to the SCADA LAN. Figure 11.2 depicts typical
second generation SCADA architecture. Distribution of system functionality across
network-connected systems served not only to increase processing power, but also to
improve the redundancy and reliability of the system as a whole. Rather than the
simple primary/standby failover scheme that was utilized in many first generation
systems, the distributed architecture often kept all stations on the LAN in an online
state all of the time.
For example, if an HMI station were to fail, another HMI station could be
used to operate the system, without waiting for failover from the primary system to
the secondary. The WAN used to communicate with devices in the field were largely
unchanged by the development of LAN connectivity between local stations at the
SCADA master. These external communications networks were still limited to RTU
protocols and were not available for other types of network traffic. As was the case
with the first generation of systems, the second generation of SCADA systems was
also limited to hardware, software, and peripheral devices that were provided or at
least selected by the vendor.
Hardware Architecture
One distinguishes two basic layers in a SCADA system: 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. PLCs, are connected to
the data servers either directly or via networks or field buses 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. The data servers and client stations
are NT platforms but for many products the client stations may also be W95
machines.
Software Architecture
The products are multi-tasking and are based upon a real-time database (RTDB)
located in one or more servers. Servers are responsible for data acquisition and
handling (e.g. polling controllers, alarm checking, calculations, logging and
archiving) on a set of parameters, typically those they are connected to.
9. FUNCTIONALITY OF SCADA
9.1 Access Control
Users are allocated to groups, which have defined read/write access
privileges to the process parameters in the system and often also to specific product
functionality.
9.2 Trending
The products all provide trending facilities and one can summaries the common
Capabilities as follows:
the parameters to be trended in a specific chart can be predefined or defined
online
a chart may contain more than 8 trended parameters or pens and an unlimited
number of charts can be displayed (restricted only by the readability)
real-time and historical trending are possible, although generally not in the
same chart
historical trending is possible for any archived parameter
zooming and scrolling functions are provided
parameter values at the cursor position can be displayed
The terms logging and archiving are often used to describe the same
facility. However, logging can be thought of as medium-term storage of data on disk,
whereas archiving is long-term storage of data either on disk or on another permanent
storage medium.
Logging is typically performed on a cyclic basis, i.e., once a certain file
size, time period or number of points is reached the data is overwritten. Logging of
data can be performed at a set frequency, or only initiated if the value changes or
when a specific predefined event occurs. Logged data can be transferred to an archive
once the log is full. The logged data is time-stamped and can be filtered when viewed
by a user. The logging of user actions is in general performed together with either a
user ID or station ID. There is often also a VCR facility to play back archived data.
9.5 Report Generation
One can produce reports using SQL type queries to the archive, RTDB or
logs. Although it is sometimes possible to embed EXCEL charts in the report, a "cut
and paste" capability is in general not provided. Facilities exist to be able to
automatically generate, print and archive reports.
9.6 Automation
The majority of the products allow actions to be automatically triggered
by events. A scripting language provided by the SCADA products allows these actions
to be defined.
In general, one can load a particular display, send an Email, run a user
defined application or script and write to the RTDB. The concept of recipes is
supported, whereby a particular system configuration can be saved to a file and then
re-loaded at a later date. Sequencing is also supported whereby, as the name indicates,
it is possible to execute a more complex sequence of actions on one or more devices.
LAKE FILTER
RESERVIOR MANAGEMENT
PROJECT
CONCLUSION
Thus it can be concluded using cost benefit analysis and some technical aspects being
included in the report that through total automation solution, synthetic chemical plant
following gain points can be achieved:
Higher productivity
REFERENCES