Internship Report

''Supervisory Control and Data Acquisition''
AN INTERSHIP REPORT
Submitted by
AHIR NIRAV J
216840309008
In partial fulfilment for the award of the degree of
DIPLOMA IN ENGINEERING
In
ELECTRICAL ENGINEERING
GROW MORE FACULTY OF ENGINEERING
HIMATNAGAR (383001)
1 ..
Gujarat Technological University, Ahmadabad

2023 - 2024
Page I 1
Scanned with CamScanner

®
:
Et;to c.1..ot\:an
Ahmadaba,d-Udaipur Highway Himatnagar, Gujarat 383001
CERTIFICATE
This is to certify that the project report submitted along with the project
entitled Internship has been carried out by ahir nirav j under my guidance in
partial fulfilment for the diploma in Engineering in Electrical Engineering, 5th
Semester of Gujarat Technological University ersity, Ahmadabad during the
academic year 2023- 2024.
Sign Sign
Assi Prof :-Sohil Luhar Assi Prof:Ramesh Prajapati
Internal Guide. HEAD OF DEPARTMENT
Page I2

COMPANY CERTIFICATE
--
--
Entlehlng Skill$
-
An ISO 900'1:2015 Compafl'f'
,
t
This certificate is presented to
•
•
iSi ara; aiSuvera
for completion of 15 days Industrial on SCADA
Internship
(Supervisory Control and Data Acquisition} Technology
from 27th July 2023 to 10th August 2023
-
10th August 2023
5•0•t
,,..,.
I< I I. I Ii I I• t I ill••+ I t I· t I I I I• I i +III+ it i I<1•41 'I I
Date of Issue , 41 Signature

Head- Training & Project
·
Sofcon India Pvt Ltd

CIN NO. : U30007DL2002PTC115673
405, 4th Floor, Sukhsagar Complex,

Near Hotel Fortune Land Mark, Usmanpura,
Ashram Raad, Ahmedabad - Gujarat
380013
@ 9227185900
Certificate No. : SIPL/AHM/23/ A164
Page I 3

i : ,,
•
-;
.
I

Ahmedabad-Udaipur Highway
Himatnagar, Gujarat 383001
DECLARATION
We hereby declare that the Internship/ Project report submitted along

with the Internship entitled Internship submitted in partial fulfillment for the
diploma in Engineering in ELECTRICAL ENGINEERING to Gujarat
Technological University, Ahmedabad, is a bonafide record of original internship
work carried out by me at Sofcon India Pvt. Ltd. under the supervision.
Name of the Student Sign of Student
1. ahir niravkumar Jagdishbhai
Page I4

ACKNOWLEDGEMENT
Project would have not been possible without the help of many people that is why we would like
to thank all of them for their help.
During this Project we got a good experience of real work, which is completely different from
the academics. And this Project can be considered as the final step towards achieving the
Bachelor degree. We are very thankful to many people who helped us during our training.
We express our gratitude to our College GROW MORE FACULTY OF ENGINEERING for
giving this opportunity to undertake this training.
And last we convey our sincere thanks to Prof. Ramesh Prajapati (HOD,Department of EC,
GMFE), Asst. Prof. Sohil Luhar (Internal Guide) and other faculty members who the
necessary help in the training. Besides this we would like to thank all those people who helped
us in one or other way.
Page I5

ABSTRACT
This paper presents the development of a supervisory control and data acquisition (SCADAJ based
remote terminal unit (RTU) for customer side distribution automation system (DAS). It is to apply
automation technique for operating and controlling low voltage (LV) down stream of 415/240 V.
The SCADA system developed provides fault isolation operation, monitoring and controlling
functions for the operators and data collection for future analysis. An embedded Ethernet
controller is used as RTU to act as converter for human machine interface (HMI) and to interact
with digital input and output modules. RTU is the master and digital input and output modules are
the slaves. RTU will initiate the transaction with the digital input and output modules. Two
proprietary software systems are used are to develop algorithm for the controller and to develop
HMI for monitoring and controlling functions for the operator.
Page I6

Table of Contents
1. INTRODUCTION...............................................................................................................................................9
1.1 PROJECT SUMMARY..............................................................................................................................10

1.2 Purpose.....................................................................................................................................................10
1.3 Scope..........................................................................................................................................................11
1.4 Technology and Literature Review.....................................................................................................11
2. SYSTEM REQUIREMENT STUDY.................................................................................................................. 15
2.1 User Characteristics................................................................................................................................15
2.2 Hardware and software requirement....................................................................................................16
2.2.1 Hardware Requirement..................................................................................................................16
2.2.2 Software Requirement....................................................................................................................16
3. System Requirement Study.............................................................................................................................17
3.1 Feasibility Study.......................................................................................................................................17
3.2 Requirement Validations.......................................................................................................................18
3.2.2 User Requirement.............................................................................................................................18
3.2.3 Functional Requirement.................................................................................................................18
3.2.4 Non-functional Requirement..........................................................................................................19
3.3 Project Estimation..................................................................................................................................19
3.4 Project Planning & Scheduling.............................................................................................................20
4. SYSTEM DESIGN..........................................................................................................................................21
4.1 Process Model..........................................................................................................................................21
4.2 SCADA DIAGRAM ............ ....................... ....................... ....................... ................. _.................22
5. Snap Shots......................................................................................................................................................... 24
6. CONCLUSION........................................................................................................................... 33
7. FEATURE S OF SCADA............................................................................................................... 34
Page I7

TABLE OF FIGURE
FIGURE 1 SCAD A SYSTEM ARCHITECTURE...................................................................24

FIGURE 2 SCAD A SYSTEM.......................................................................................................25
FIGURE 3 SCADA FOR ENGINEERS.............................................................................................26
FIGURE 4 SCADA SYSTEM WORK........................................................................................27
FIGURE 5 Supervisory Co ntro I and Data Acquis it ion...................................................28
FIGURE6 COMMUNICATION LAYER SCADA..............................................................29
FIGURE 7 SCADA ANIMATION..................................................................................................... 30
FIGURE 8 SCADA RAIL MONITORING and Control...................................................................31
FIGURE 9 SCADA IN POWER SYSTEM........................................................................................ 32
Page I8

1. INTRODUCTION
► The term SCADA stands for Supervisory Control And Data Acquisition. A SCADA system is a
common process automation system which is used to gather data from sensors and instruments
located at remote sites and to transmit and display this data at a central site
► for control or monitoring purposes. The collected data is usually viewed on one or more SCADA
Host computers located at the central or master site.
► A real world SCADA system can monitor and control hundreds to hundreds of thousands of VO
points. A typical Water SCADA application would be to monitor water levels at various water
sources
► like reservoirs and tanks and when the water level exceeds a preset threshold, activate the system of
pumps to move water to tanks with low tank levels.
Page I9

1.1 PROJECT SUMMARY
► A SCADA system project is a complex and challenging undertaking that involves planning,
designing, installing, testing, and operating a supervisory control and data acquisition system for
industrial processes.
► Supervisory control and data acquisition (SCADA) is a system of software and hardware elements
that allows industrial organizations to: Control industrial processes locally or at remote locations.
Monitor, gather, and process real-time data.
1.2 Purpose
► What does SCADA stand for? Supervisory Control and Data Acquisition (SCADA)
systems are used for controlling, monitoring, and analyzing industrial devices and
processes. The system consists of both software and hardware components and enables
remote and on-site gathering of data from the industrial equipment.
► SCADA systems include hardware and software components. The hardware gathers
and feeds data into field controller systems, which forward the data to other systems that
process and present it to a human-machine interface (HMI) in a timely manner. SCADA
systems also record and log all events for reporting process status and issues. SCADA
applications warn when conditions become hazardous by sounding alarms.
Page I 10

1.3 Scope:
► SCADA has important role on automation project. SCADA has huge scope in all types of industries.
The entire automation field is heavily reliant on them in an industrial setup.
► SCADA allows for real-time plant information to be accessed from anywhere around the world.
SCADA has important role on automation project. SCADA has huge scope in all types of industries.
The entire automation field is heavily reliant on them in an industrial setup.
1.4 Technology and Literature Review
► SCADA, a system for gathering real time data, controlling processes, and monitoring CI equipment
from remote locations is a popular target for attacks. As more companies are implementing an open
SCADA architecture through the Internet to monitor CI components such as power plants, oil and
gas pipelines, chemical refineries, flood control dams, and waste and water systems, vital systems
are becoming increasingly open to attack.
► Communications protocols are necessary for the movement of electric power, gas, oil, and
transportation, and great interest in these systems has yielded several attacks in recent years.
► As more sophisticated and successful cybe rattacks are launched, increased attention is being given
to the security and protection of SCADA systems. According to the Industrial Control Systems
Cyber Emergency Response Team (ICS-CERT),
Page I 11

► First, threats and vulnerabilities of SCADA include replay, man-in-the-middle, brute force,
dictionary, eavesdropping, denial-of-service, war dialing and default passwords. These are discussed
in detail in the following pages.
► Secondly, are these threats and vulnerabilities significant? Without a doubt, yes. These electronic
real-time process networks, across the globe, are all the time subjected to serious cyber damage and
disruption by due to the fact that they are standardized and remain connected to other networks. A
few years ago, a report was released by the President's Commission on Critical Infrastructure
Protection outlining the country's reliance on increasingly vulnerable, interconnected physical and
cyber infrastructures.
► An important policy document known as the Presidential Decision Directive 63 (PDD63) defined
critical infrastructure as ''those physical and cyber-based systems essential to the minimum
operation.s of the economy and government'' (Homeland Security Digital Library, n.d). It defined
critical infrastructure as including: telecommunications, energy, banking and finance, transportation,
water systems, emergency services and essential government services.
t Uni
► The entire nation as well as its bordering nations and several parts of the world who depend on us
will be affected if an exploitation was successful.
Page I 12

Significance of the study
► SCADA, a system for gathering real time data, controlling processes, and monitoring CI equipment
from remote locations is a popular target for attacks. As more companies are implementing an open
SCADA architecture through the Internet to monitor.
► CI components such as power plants, oil and gas pipelines, chemical refineries, flood control dams,
and waste and water systems, vital systems are becoming increasingly open to
attack. Communications protocols are necessary for the movement of electric power.
► gas, oil, and transportation, and great interest in these systems has yielded several attacks in recent
years. Some attacks were viruses specifically targeting programmable logic controller (PLC) and
SCADA systems. Even though there are proven and reliable encryption systems designed for
industrial use, the overwhelming majority of SCADA systems in use do not use any authentication
or encryption methods.
With connectivity, comes vulnerability
► Most of our critical infrastructure (energy, water, telecommunications, rail and traffic management)
is controlled by SCADA systems that are connected to the rest of the world via high-speed data
networks. This makes them vulnerable to hackers or cyber-terrorists, who may be motivated to harm
these assets, steal, alter or inject data within the SCADA system.
► Critical infrastructure systems need to be protected from eavesdropping, but more importantly
against the injection of rogue data. The impact of fooling a ater treatment pl nt into thinking a
process had already been completed, or a power plant to think 1t was cooler than 1t really was, could
be catastrophic.
► Because SCADA control systems are used to manage anything from commercial and industrial
control systems to critical energy, water and telecommunications infrastructures, they are a prime
target for cyber-attacks by criminals, rogue states and terrorists.
► Even private data networks are vulnerable; which is why they should be protected with high
assurance data encryption to ensure both secrecy and integrity of data.
► We'd even argue that whatever high-assurance encryption solution is chosen, it should also be
''crypto-agile'' and quantum ready. That ensures the best long-term encryption security solution.
Page I 13

-
SCADA ED
ED
mo • ,Control
IED
lE
oca Con ol
Su o
Con oller
1 two '
' - _,
f
Autom tic R mot

od m on1toring

...._ 0:;:::;;;o::;o
-
odem
Router to WA 1
-
R mot Acee
Lcg·c
P DCB· 01"
► Attack: Intruder scans hundreds of phone numbers. When a possible connection is detected, multiple
returns. Login dialogue is acquired, followed by social engineering to determine login information
or dictionary-based or brute force attack is launched.
► Once connection is completed, attacker gains entry to shut off the device, gather data, change
settings, plant instructions, ark
change the data and/or degrade the device. Several actions can be taken
by the attacker to destroy or manipulate the system and harm populations.
lnt rfac
Page I 14

2. SYSTEM REQUIREMENT STUDY
2.1 User Characteristics

► Need for an application that makes communicating easy and comfortable. An application
that enables user to park a vehicle with safe and secure. Need for an application that is
easy to use and widely available and hence a web application Handling all functions done
with organization in a computerized manner. Allowing the user to park the vehicle
directly.
• Alarm Handling.
• Trend Curves Patterns.
• Data Access and Retrieval.
• Computer Networking and Processing.
a).Data Records
► A SCADA system can collect any type of data from plant equipment, such as temperature, pressure,
and speed data, as long as there is a connection to the equipment. Data from the equipment is the
raw data that the PLCs or RTUs then translate into comprehensible information for human operators
to act upon.
b).Reports
► The Report Page provides a variety of pre-defined report types designed to analyze the performance
of the equipment comprising your physical system. Most can be used across a wide variety of
industries while others are intended specifically for use in water and wastewater.
Page I 15

2.2 Hardware and software requirement
2.2.1 Hardware Requirement

► The Triangle MicroWorks SCADA Data Gateway (SDG) supports the following versions
► ofWindows
• Windows 10 IoT
• Windows 11
• Windows 10 (64-bit)
• Windows Server 2016 (64-bit)
• Windows Server 2019 (64-bit)
2.2.2 Software Requirement

• Runs on x86 64-bit Single Board Computers to large Servers
• Works on Virtual Machines
• Ubuntu 18.04 and 20.04
• Red Hat Enterprise 8.0
Page I 16

3. System Requirement Study
► They pull together hardware, software, and connectivity and then organize it into four layers: field
instrumentation; programmable logic controllers (PLCs) and remote telemetry units (RTUs);
communications; and the SCADA host platform.
► How many levels are present in a complex SCADA system? Explanation: There are four-levels in a
complex SCADA system. In complex SCADA architectures, there is a variety of wired and wireless
media. A diverse range of wired and wireless media can be utilized by the complex SCADA system.
Sensors and actuators.
► A sensor is a feature of a device or system that detects inputs from industrial processes. An actuator is
a feature of the device or system that controls the mechanism of the process. In simple terms, a sensor
functions like a gauge or meter, which displays the status of a machine; an actuator acts like a switch,
dial or control valve that can be used to control a device. Both sensors and actuators are controlled and
monitored by SCADA field controllers.
SCADA field controllers.
► Remote telemetry units, also called remote terminal units (RTUs), interface with sensors to
collect telemetry data and forward it to a primary system for further action.
► Programmable logic controllers (PLCs) interface with actuators to control industrial processes,
usually based on current telemetry collected by RTUs and the standards set for the processes.
Page I 17

3.1 RequirementValidations
3.1.1 Information gathering
You can use validation tools such as Modbus Conformance Test Tool, DNP3 Conformance
Test Suite, or IEC 61850 Conformance Test Tool to run a series of tests that check the correctness
and completeness of your protocol implementation.
► Interviewing the users:
• Explain PLC?
• What are the different parts of automation?
• What are the implementations of PLC automation?
• Role of PLC in Automation?
• What is redundancy in PLC?
• What is scan in PLC?
• How does a Latch coil work?
• What is a draw close to the control relay?
3.1.2 User Requirement

► Minimum system requirements for the host computer: 1.5 GHz processor; recommended: 2.4 GHz
multi-core processor. 1 GB RAM; recommended: 4GB RAM. Windows 8 or higher.
► 32- or 64-bit Windows OS. 2 GHz dual-core processor. 40 GB free drive space. 4 GB RAM.
3.1.3 Functional Requirement

• Data Acquisition. SCADA systems acquire machine data through networked devices and sensors
connected to a PLC or RTU. ...
• Control. Automated process control based on defined set-points is another SCADA function....
• Alarms....
• Inputs and Sensors..
• Conversion Units: PLCs and RTUs.
• HMI.
Page I 18

3.1.4 Non-functional Requirement
• Examples ofNon-functional Requirements
Scalability: The system must be able to scale up or down as needed. Availability: The system
must be available when needed. Maintenance: The system must be easy to maintain and update.
Portability: The system must be able to run on different platforms with minimal changes.
3.2 Project Estimation
► A SCADA system project is a complex and challenging undertaking that involves

planning, designing, installing, testing, and operating a supervisory control and data
acquisition system for industrial processes.
► A successful project not only meets the technical and functional requirements, but also
delivers value and benefits to the stakeholders. To ensure that the project outcomes are
aligned with the expectations and objectives, it is essential to evaluate and report the
results and lessons learned of the project in a systematic and transparent way. In this
article, we will discuss how you can do that using some practical steps and tools.
► The first step when evaluating a project is to define the criteria for measuring and
assessing its performance and impact.
► These criteria should be based on the project scope, goals, deliverables, and indicators that
were established at the beginning of the project, as well as taking into account feedback
from the project team, end users, sponsors, and other stakeholders.
Page I 19

3.3 Project Planning & Scheduling
► A typical supervisory control and data acquisition (SCADA) system or an energy management
system (EMS) has an installed life of only 10 to 15 years. System operations' needs and the
underlying technology are rapidly changing,
► so it is unlikely that the life expectancy will increase any time soon. Because it can take 5 years or
more to implement a new EMS or SCADA system, managing such projects is becoming a way of
life for utilities. Therefore, it behooves utility engineers to be familiar with the process of managing
► EMS or SCADA implementation projects. Implementing a new EMS or SCADA system is a project
management challenge. It is a challenge that can be met by using state-of-the-art project
management tools, together with old-fashioned discipline. One of the first orders of business is to
establish a preliminary project schedule. As described in this article, the process encompasses three
major phases: (1) project definition, (2) procurement, and (3) implementation.
Project Plan
► SCADA provides organizations with the tools needed to make and deploy data-driven decisions
regarding their industrial processes. One of the most commonly used types of industrial control
system, SCADA can be used to manage almost any type of industrial process.
► In a conventional SCADA master plan, the project team gathers information on the major
components of the SCADA system and the processes it monitors and controls. The components
include PLCs, servers, workstations, communications equipment, process control narratives, and
operational objectives.
Project Scheduling
► SCADA master plans are typically shaped by plant processes, end users' specific necessities, budget
constraints, the ascension of new disruptive technological paradigms and unexpected challenges
such as the current pandemic, which calls for more unsupervised intelligent controls and secure
remote access.
► An SMP is an organized set of proposals, engineering documents and guidelines to generate the
design framework and roadmap for capital expense projects related to SCADA and automation
assets to be executed during a specified period.
Page I 20

2. SYSTEM DESIGN
4.1 Process Model
Iterative Model
► Iterative process starts with a simple implementation of a subset of the software
requirements anditeratively enhances the evolving versions until the full system is
implemented. At each iteration, design modifications are made and new functional
capabilities are added.
► Iterative and Incremental development is any combination of both iterative design

or iterative method and incremental build model for software development. The combination
is of long standing and has been widely suggested for large development efforts. For
example, the 1985 DOD-STD-2167 mentions (in section 4.1.2):
► "During software development, more than one iteration of the software development cycle
may be in progress at the same time." and "This process may be described as an 'evolutionary
acquisition' or 'incremental build' approach." The relationship between iterations and
increments is determined by the overall software development methodology and software
development process. The exact number and nature of the particular incremental builds and
what is iterated will be specific to each individual development effort.
► An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of the
software, which can then be reviewed in order to identify further requirements. This process
is then repeated, producing a new version of the software for each cycle of the model.
Page I 21

4.2 SCADA DIAGRAM
► Supervisory control and data acquisition (SCADA) is a system of software and hardware
elements that allows industrial organizations to: Control industrial processes locally or at
remote locations. Monitor, gather, and process real-time data.
Symbol used Scada:
► The Symbol Factory Universal is the combination of a software application for the management and
manipulation of the appearance of an included, extensive library of industrial graphics optimized for
high performance for use in industrial automation HMI applications, including pumps, pipes, valves,
tanks, mixers, motors ...
► Supervisory Control and Data Acquisition (SCADA) systems are used for controlling, monitoring,
and analyzing industrial devices and processes. The system consists of both software and hardware
components and enables remote and on-site gathering of data from the industrial equipment.
► Symbol Systems is a theory of media-based learning. Its perspectives on learning are based on
Information Processing Theory, and so both the learner and the medium of learning are described in
terms of symbol-based processing. (Hence the theory's name.)
Page I 22

f
'
I t
•
advancedclassifi aeromechanical aeromecha nical aeromechanical ag1' _m1xer bulk_bag_disharg bulk_bag_filler bulk_bag_loader conical_screw_pr cyclone_l dryer-cooler
cation_system conveyor_l conveyor_2 conveyor_3 er ocessor
• •
dust reclaim electrostaticdust leeder heaV_'dfuty_m e hommo hopper_4 inclined_plate_cla jaw_crusher_l jaw_crusher_2 Jaw_crusher_3
collector ixer rifier
high_vacuum_co r
nveyor ,- □J.
--.illllli -
\
-
--- -
I \
rI
-
....

pipeline.mixer simple_agglomer simple_bag_dum .simple_bul _bag_ simple_centr ug sim pie_classifier simple_dyna- simpleJeeder simple.filter simple_fine_grin
p filler al_scalper _ mill slid d ing_mill
-
simple_a ir_dassifi ation e feeder
er
'-
- i::::
I
I
I I
1
I
OJ
I
I I
I', ,, I

I I
f I
I I
I I
I I
I
' ..... ,_, I
...
siniple_hammer simple_hammer simple_hopper_w simple_rolle ill .simple_rotary_ai simple_screener simple_shredder simple_silo simple_solids_pr msiple_transport simple_vibrating_
mr_ rl o
mill- mill itmh- ock- cessmg er
1 2
aterial feeder
► HMI/SCADA collects data from RTUs (Remote Terminal Units), PLCs (Programmable Logic
Controllers), and other control devices such as flow meters and temperature controllers. This data is
presented to an operator using a Human Machine Interface (HMI).
► While SCADA systems are standard with industrial systems, IoT adds features and functionality
where SCADA ends. SCADA and IIoT (Industrial Internet of Things) concepts and their overall
system architecture face cybersecurity challenges since they are a likely target for advanced hacking
groups.
Page I 23

5. Snap Shots
1. Scada System Architecture
e·a ,or
Co ·1s0 es
m y .. ===;E_::=. B
un· a •
I
s .
e e , c·
C s
•
et o cs 0
Page I 24

2. Scada System
SCAlDA
s;yster11
,,
■ l!il Ill Ii iii ■,Iii
lll\r-' : ii!
!!
i!-
A. : Ill "■ ■ ■
N : ■
llll Ill
'!II llilfUs Ren1oft:e R'T1Us

... iii [ !!iii!
ta
,■
.., !!! !I! !II• ii! !!! !I! !!I■
I I ■
I■
llifUs. ,

Rl"Us RTlllllls
ti
ilJ lAN
-
Jli
11 ■'1·1 ii Iii Iii Ii I ii■-
A.emote
acc.es:s;-1rn 1
.s.vs-lellriniS

"Iii
1
0 oer:ati nu .siati 11.s
Page I 25

3. Scada for Engineers
STOP
WINLOG
Page I 26

4. Scada System Work
I
I
vi I
I
I
--
.. -
.,
- --
- -- qui
I
p
•
- -;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;..;;;..............;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;--=,••
Page I 27

5. Supervisory Control and Data Acquisition
Layer structu e echnolog es Architecture
Sup rvtsory SCADA --

- . •I
I
I
GPRS, lnte net I
Com1m • nicatio Radio, Satelli.te,
OPC,VPN
'
I
I
Connect,ivity: wired or wireless

I
Ml
R
PLC & RTU
Local control
& HMI
Field
Sensors &
Att_ators -
Page I 28

6. Communication layer Scada
•
I
Page I 29

7. Scada Animation
. ...
I FEED (PADD E) CONVEYOR
••••••••••••••••••••••••••••••••••••••••• ,
INFEEOBELTCONVEYOR
1■■■111■11■■1 .
•••••••••••••••••••••••••••••••••••••••••••••••••••••
Ill■ ■1111 I■ Ill 111■111111111 II 1111
VSA VSA VSA VS. A
m, It:; u:r?:
I "-'
111111 u rrun
VSB
C: GURRlt Ml: .ClJllRll Cl;R.R

. .
IDID Jl IDID mu, WI 20mm WI
rnm11 Frum. Fruiu Fnuts
1 2 4
w·
3
7S'Jlltom \!{ei ht: 7!16'.l too
0
\\'Eigln. Olllim W,isi,t 999 toll5
Au1m. /\cum. J&.i;,,n:,. )ll-..m.
\\'ftp 2'11l!l6 llln5 Yl'Pigln: 17960 l(JIU, 'n'f'tgbl; DIDns Wei;ght:
.AUGER AUG£R
l!IEQUEMCE;
n !IEQUEHCE: n SEQUDICE: Cl !EQUENCIE: 0
REAOY 0 0
IIEAOY
z READY 0 0
CHAJIGE z OWIOE
0
CHARQE
0 z READY
0
0
m m QtARQE
z
COOPG
z
Ul .COOIUNG V, COOUKI UJ OOOKN8 (/)
IIECtu.RGE
)), )), >
DIIIOWICIE DIIICflMCll:
irl CIIIICHARGE
OUIF DRAIN DlalP DRAIN DIIIP DRAIN DUIP ORAi
,.............................D.I.SC.H...........R.................................
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
COMPRESSED AIR PRESSURE STEAM AJR PRESSURE
Page I 30

8. Scada Rail Monitoring and Control
R ii Contro I Ce
1ter
D Engineering
Hiaori n V\blcslstions
C rolSehW Printer
(SCAOA - hi
Tll)
Ring Topology
Hub
Rail Secf 011 1 Rail Section 3
Hub
Ra:il S cti o.i
RlU
- RJU
Signruing Sigmli
mi'lto Tr • lo
V\lllysict • Col'flrol w.·yscre Cort,..
T !into
,--- = on ---. Pow:r deCcntrol
I • II •• • I
radlon
Eledri Ion
Eledrilcmion Tr!llll Traction SlatMi
Subst!l.ion rilh;stl.T,
SI.lb cn
,n PlC.
PLC: !lo
Tre.ellon eI nrie -oti
1t ct.ionEI d:( iO omoring Cortrcl
t.torrllnin ' nd Control ra El dri on
Con1rol
Page I 31

9. Scada In Power System
Page I 32

6. Conclusion
► Generating stations and power lines were interconnected to provide redundancy. As the system
expanded and began to scale out in size, it became harder to manage. Solutions were needed to face
the challenges of controlling equipment over long distances. To overcome this, operating personnel
were often stationed at the important points in this grid system so that they could monitor and
quickly respond to any problems that might arise due to any fault or failure. They would
communicate with central electricity dispatchers, often employing telephone, to keep them informed
about the condition of the system.
► n the early years when electric power systems began developing, electricity generation plants were
only associated with their respective local loads. If anything failed in the whole linearly connected
system, which could include subsystems like generating plant, power lines, connections, then the
lights would be out. Customers had not yet adapted to depend on electricity. Outages, whether
routine or emergency, were taken as a matter of course. As reliance on electricity grew, so did the
need to find ways to improve reliability.
Page I 33

7. Features Of Scada
1. Alaram Handling
2. Trend Curves Patterns
3. Data Access and Retrieval
4. Computer Networking and Processing
5. Dynamic Process Graphics
6. Security
7. Device Connectivity
8. Database Connectivity
9. Real Time and Historical trend
10. Recipe Management
Page I 34

Internship Report

Uploaded by

Copyright:

Available Formats

Internship Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Internship Report

Uploaded by

Copyright:

Available Formats

''Supervisory Control and Data Acquisition''

Gujarat Technological University, Ahmadabad

Scanned with CamScanner

GROW MORE FACULTY OF ENGINEERING

Ahmadaba,d-Udaipur Highway Himatnagar, Gujarat 383001

Assi Prof :-Sohil Luhar Assi Prof:Ramesh Prajapati

Internal Guide. HEAD OF DEPARTMENT

Scanned with CamScanner

Date of Issue , 41 Signature

Sofcon India Pvt Ltd

405, 4th Floor, Sukhsagar Complex,

Certificate No. : SIPL/AHM/23/ A164

Scanned with CamScanner

GROW MORE FACULTY OF ENGINEERING

We hereby declare that the Internship/ Project report submitted along

Name of the Student Sign of Student

1. ahir niravkumar Jagdishbhai

Scanned with CamScanner

Scanned with CamScanner

Scanned with CamScanner

1.1 PROJECT SUMMARY..............................................................................................................................10

Scanned with CamScanner

FIGURE 1 SCAD A SYSTEM ARCHITECTURE...................................................................24

Scanned with CamScanner

Scanned with CamScanner

Scanned with CamScanner

1.4 Technology and Literature Review

Scanned with CamScanner

Scanned with CamScanner

With connectivity, comes vulnerability

Scanned with CamScanner

Autom tic R mot

Scanned with CamScanner

Scanned with CamScanner

2.1 User Characteristics

Scanned with CamScanner

2.2.1 Hardware Requirement

2.2.2 Software Requirement

Scanned with CamScanner

Sensors and actuators.

SCADA field controllers.

Scanned with CamScanner

► Interviewing the users:

3.1.2 User Requirement

3.1.3 Functional Requirement

• Inputs and Sensors..

• Conversion Units: PLCs and RTUs.

Scanned with CamScanner

• Examples ofNon-functional Requirements

3.2 Project Estimation

► A SCADA system project is a complex and challenging undertaking that involves

Scanned with CamScanner

Scanned with CamScanner

► Iterative and Incremental development is any combination of both iterative design

Scanned with CamScanner

Symbol used Scada:

Scanned with CamScanner

Scanned with CamScanner

Scanned with CamScanner