SCADA Systems

SCADA architecture: components and setup

SCADA (Supervisory Control and Data Acquisition) system refers to the combination
of telemetry and data acquisition. It consists of collecting information, transferring
it back to a central site, carrying out necessary analysis and control, and then
displaying this data on a number of operator screens. The SCADA system is used to
monitor and control a plant or equipment. Control may be automatic or can be
initiated by operator commands.

Widely used in industry for Supervisory Control and Data Acquisition of industrial
processes, SCADA systems are now also penetrating the experimental physics
laboratories for the controls of ancillary systems such as cooling, ventilation, power
distribution, etc. SCADA systems have made substantial progress over the recent
years in terms of functionality, scalability, performance and openness such that they
are an alternative to in house development even for very demanding and complex
control systems as those of physics experiments.

Fundamental principles of modern SCADA systems:

In modern manufacturing and industrial processes, mining industries, public and
private utilities, leisure and security industries telemetry is often needed to connect
equipment and systems separated by large distances. This can range from a few
meters to thousands of kilometers. Telemetry is used to send commands, programs
and receives monitoring information from these remote locations.
SCADA refers to the combination of telemetry and data acquisition. SCADA
encompasses the collecting of the information, transferring it back to the central
site, carrying out any necessary analysis and control and then displaying that
information on a number of operator screens or displays. The required control
actions are then conveyed back to the process.
In the early days of data acquisition, relay logic was used to control production and
plant systems. With the advent of the CPU and other electronic devices,
manufacturers incorporated digital electronics into relay logic equipment. The PLC
or programmable logic controller is still one of the most widely used control systems
in industry. As need to monitor and control more devices in the plant grew, the PLCs
were distributed and the systems became more intelligent and smaller in size.
SCADA stands for Supervisory Control And Data Acquisition. As the name
indicates, it is not a full control system, but rather focuses on the supervisory level.
As such, it is a purely software package that is positioned on top of hardware to
which it is interfaced, in general via Programmable Logic Controllers (PLCs), or other
commercial hardware modules.
SCADA systems are used not only in industrial processes: e.g. steel making, power
generation (conventional and nuclear) and distribution, chemistry, but also in some
experimental facilities such as nuclear fusion. The size of such plants range from a
few 1000 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 100 K: we know of two cases of near to 1 M I/O channels
currently under development.
SCADA systems used to run on DOS, VMS and UNIX; in recent years all SCADA
vendors have moved to NT and some also to Linux.
Core functionalities of a SCADA system are as follows:
1. Acquisition of data from field instrument devices via RTU.

2. Processing the field data to detect alarms and other significant process changes.
3. Providing a consistent database of process information about the pipeline and
facility.
4. Presenting the data via easy-to-understand graphical user interface, alarms,
trends, and reports.

5. Performing remote control of field devices.

6. Performing system monitoring and diagnosis and taking appropriate actions.

7. Historical archiving of data for recent and long-term historical storage and
analysis.
8. Transferring real-time engineering data directly to and from the modeling system
such as pipeline application system.
9. Providing system data to Management Information Systems (MIS) and supply
chain management.

10. Providing integration with geographical information system (GIS) facilities.

Architecture:
Hardware Architecture:
A SCADA system consists of a number of remote terminal units (RTUs) collecting
field data and sending that data back to a master station, via a communication
system. The master station displays the acquired data and allows the operator to
perform remote control tasks.
The accurate and timely data allows for optimization of the plant operation and
process. Other benefits include more efficient, reliable and most importantly, safer
operations. This results in a lower cost of operation compared to earlier non-
automated systems.
On a more complex SCADA system there are essentially five levels or hierarchies:
• Field level instrumentation and control devices

• Marshalling terminals and RTUs

• Communications system

• The master station(s)

• The commercial data processing department computer system

Background to SCADA:
The RTU provides an interface to the field analog and digital sensors situated at
each remote site.
The communications system provides the pathway for communication between the
master station and the remote sites. This communication system can be wire, fiber
optic, radio, telephone line, microwave and possibly even satellite. Specific
protocols and error detection philosophies are used for efficient and optimum
transfer of data.
The master station (or sub-masters) gather data from the various RTUs and
generally provide an operator interface for display of information and control of the
remote sites. In large telemetry systems, sub-master sites gather information from
remote sites and act as a relay back to the control master station.
 Typical Hardware Architecture

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. However,
it is possible to have dedicated servers for particular tasks, e.g. historian, data
logger, alarm handler.
SCADA software
SCADA software can be divided into two types, proprietary or open. Companies
develop proprietary software to communicate to their hardware. These systems are
sold as ‘turn key’ solutions. The main problem with this system is the overwhelming
reliance on the supplier of the system. Open software systems have gained
popularity because of the interoperability they bring to the system. Interoperability
is the ability to mix different manufacturers’ equipment on the same system.
Citect and WonderWare are just two of the open software packages available in the
market for SCADA systems. Some packages are now including asset management
integrated within the SCADA system. The typical components of a SCADA system
are indicated in the next diagram.

Generic Software Architecture

Types of SCADA:

 D+R+N ( Development +Run + Networking)

 R+N ( Run +Networking )
 Factory focus
1. D+R+N (Development + Run + Networking)

This is the most complete SCADA package, providing all three capabilities:

 Development (D):
o Engineers can design, configure, and build the SCADA application.
 o Includes tools for screen design, PLC driver setup, tag database
creation, alarms, trends, and reports.
o Example: Creating custom HMIs (Human Machine Interfaces) for a
plant.

 Run (R):
o The system can execute the SCADA application created in the
development environment.
o Handles real-time data acquisition, operator control, alarming, and
trending.

 Networking (N):
o Supports communication across multiple nodes in a plant or even
across locations.
o Allows distributed SCADA systems — e.g., multiple operator stations,
redundancy servers, and remote access.
Large industries like oil & gas, power plants, and manufacturing units that need
custom design + full runtime + multi-station networking.
Example software: Wonderware System Platform, Siemens WinCC Professional,
Ignition SCADA.

2. R+N (Run + Networking)

This type is limited to running pre-developed applications and networking.

 No Development Tools:
o You cannot build or modify SCADA applications here.
o You can only execute applications that were developed elsewhere
(using the D+R+N package).
 Run (R):

o Operators can use it to monitor and control processes.

 o Handles alarms, logs, and real-time monitoring.
 Networking (N):
o Allows this SCADA station to connect with others in a distributed
system.
o Commonly used as client stations, operator consoles, or secondary
servers.
Use Case:
Operator stations or client PCs in a large SCADA network where application
development isn’t needed.
Example: A control room operator PC in a steel plant connected to the main SCADA
server.
3. Factory (Standalone/Compact)
This is a basic SCADA package with limited or no networking capability.
 Usually includes Development + Run, but no advanced networking.
 Designed for small, standalone applications where everything runs on a
single PC.
 Suitable for factory-level or machine-level automation (e.g., one packaging
machine, a small water treatment plant).

 Less expensive compared to D+R+N.

Manufacturers of SCADA

 Modicon (Telemecanique) Visual look

 Allen Bradly : RS View
 Siemens: win cc
 KPIT : ASTRA
 Intelution: Aspic
 Wonderware : Intouch
Data acquisition methods
Data acquisition refers to the method used to access and control information or
data from the equipment being controlled and monitored. 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.
Telemetry is usually associated with SCADA systems. It is a technique used in
transmitting and receiving information or data over a medium. The information can
be measurements, such as voltage, speed or flow. These data are transmitted to
another location through a medium such as cable, telephone or radio. Information
may come from multiple locations. A way of addressing these different sites is
incorporated in the system.

Key data acquisition methods in SCADA:

1. Sensors and Field Devices: This is the starting point of data acquisition. Sensors
are deployed throughout the industrial process to measure physical parameters.
 Types of Sensors: Temperature sensors, pressure sensors, flow meters, level
sensors, vibration sensors, current transducers, voltage sensors, proximity
sensors, limit switches, etc.
 Actuators: While not directly acquiring data, actuators (like valves, pumps,
motors, circuit breakers) receive commands from the SCADA system based
on the acquired data. Their status (e.g., open/closed, on/off) is also a form of
data fed back to the SCADA system.
 How they work: Sensors convert physical quantities (like temperature or
pressure) into electrical signals (analog or digital).
2. Remote Terminal Units (RTUs): RTUs are specialized microcontrollers designed
for remote monitoring and control.
 Function: RTUs collect data directly from sensors and field devices at remote
locations. They perform analog-to-digital conversion (if the sensor provides
 analog output), preprocess the data, and then transmit it to the central
SCADA system.
A SCADA system incorporates multiple RTUs, physically placed in the field at
key measurement and control locations. The RTU began as a hardwired, fixed
function electronic device that could respond to simple commands received
as serially transmitted numeric codes. Early RTUs were used for remote
telemetry purposes, even before SCADA systems were created, through the
integration of a central computer. RTUs were connected, through serial
communication channels, to master terminal units (MTUs) – electronic
devices that provided a human interface, to enable display of data from the
RTUs and manipulation of control outputs of the RTUs. An MTU generally
consisted of an alphanumeric readout or display and a keypad for entering
parameters and commands. An operator could enter an RTU ID and an input
number and press a poll key.
 Control Capabilities: RTUs also receive control commands from the SCADA
master and send them to actuators.
 Communication: They communicate with the central SCADA system via
various methods (see point 4).
3. Programmable Logic Controllers (PLCs): PLCs are robust industrial computers
commonly used for automating specific, localized control tasks.
 Function: PLCs also collect data from sensors and can directly control
actuators based on programmed logic. They are highly efficient for fast,
deterministic control loops.
 Integration with SCADA: In a SCADA system, PLCs typically act as intelligent
data concentrators. They perform the local control, and then periodically or
upon request, they send their collected data (e.g., sensor readings,
equipment status, internal variables) to the central SCADA system. The
SCADA system then provides the supervisory overview and higher-level
control.
4. Communication Networks and Protocols: Once data is collected by RTUs or PLCs,
it needs to be transmitted to the central SCADA master station. This involves various
communication methods and protocols.
 Wired Connections:
o Serial Communication (RS-232, RS-485): Traditional methods, often
used over shorter distances or for older devices.
o Ethernet: Increasingly common for its speed, reliability, and ability to
use standard IT infrastructure. This can be industrial Ethernet (e.g.,
EtherNet/IP, PROFINET) or standard TCP/IP.
o Fiber Optics: Used for long distances, high bandwidth, and immunity
to electromagnetic interference, especially in critical applications.

 Wireless Connections:
o Radio (VHF/UHF): Common for widely dispersed remote sites where
wired connections are impractical.
o Cellular (4G/5G): Provides ubiquitous connectivity, especially for
mobile assets or locations with cellular coverage.
o Satellite: Used for extremely remote locations where other
communication methods are unavailable.
 Industrial Protocols: These are the "languages" that SCADA components use
to communicate and exchange data. Examples include:
o Modbus: One of the oldest and most widely used serial protocols, also
has a TCP/IP version.
o DNP3 (Distributed Network Protocol 3): Robust and secure protocol
often used in utility (electric, water) applications.
o OPC (OLE for Process Control): A set of standards that allow different
industrial automation devices and software applications to
communicate. OPC UA (Unified Architecture) is the modern, platform-
independent version.
 o Ethernet/IP, PROFINET: Ethernet-based protocols commonly used in
factory automation.
o MQTT (Message Queuing Telemetry Transport): A lightweight
messaging protocol often used in IoT and for bridging OT data to
IT/cloud environments due to its efficiency and publish-subscribe
model.

5. Data Processing and Storage: After data is acquired and transmitted:

 SCADA Servers/Master Station: The central SCADA software processes the
raw data. This involves:
o Data Validation and Filtering: Checking for errors, anomalies, or noise
in the data.
o Unit Conversion: Converting raw sensor values into meaningful
engineering units (e.g., mV to Celsius).
o Tag Management: Organizing data points (tags) with unique identifiers
and attributes.
o Calculations: Performing calculations based on raw data (e.g., flow
rate from differential pressure).
 Historian Database: Processed data is timestamped and stored in a historical
database (historian). This database is optimized for time-series data and
allows for:
o Trending: Visualizing data over time to identify patterns and
performance.
o Reporting: Generating reports on operational metrics, alarms, and
events.
o Analysis: Supporting root cause analysis, predictive maintenance, and
process optimization.
6. Human-Machine Interface (HMI): While not a direct data acquisition method,
the HMI is the primary way operators visualize the acquired data. It presents real-
time values, trends, alarms, and graphical representations of the process, enabling
operators to understand the current state of the system and make informed
decisions.
In essence, SCADA data acquisition is a multi-layered process, starting from physical
measurements at the field level, moving through intelligent devices that collect and
pre-process data, and finally transmitting that data over a network to a central
system for storage, analysis, and visualization.
SCADA system configuration tasks
SCADA (Supervisory Control and Data Acquisition) system configuration involves a
wide range of tasks to set up, define, and optimize how the system monitors,
controls, and manages industrial processes. These tasks ensure the system
functions correctly, securely, and efficiently to meet operational requirements.
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).
Functionality
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.

Features of SCADA
 Dynamic representation
 Database connectivity
 Device connectivity
 Alarms
 Trends
 Scripts
 Security
 Recipe Management
 Networking
Dynamic Representation:
This feature explains about the representation of various symbols of field
instruments which are present in tool library which can be utilized in Scada
[Link] is not dedicated to any specific industry hence its library is so
large that can use it for any industries available.

Data base connectivity

Scada doesn’t has its own database just like Microsoft has. Hence for storage it rely
on databases available in the market. It can be connected to VB , SQL ,EXCEL , or
SAP.

Device Connectivity
Scada is not a 100% [Link] alone can’t do any controlling .It has to be
connected to controllers .Hence any scada can be connected to any PLC or DCS that
are available in the market by using specific driver software.

Alarm Handling
It is based on limit and status checking and performed in the data servers. More
complicated expressions (using arithmetic or logical expressions) can be developed
by creating derived parameters on which status or limit checking is then performed.
The alarms are logically handled centrally, i.e., the information only exists in one
place and all users see the same status (e.g., the acknowledgement), and multiple
alarm priority levels (in general many more than 3 such levels) are supported. It is
generally possible to group alarms and to handle these as an entity (typically
filtering on group or acknowledgement of all alarms in a group). Furthermore, it is
possible to suppress alarms either individually or as a complete group. The filtering
of alarms seen on the alarm page or when viewing the alarm log is also possible at
least on priority, time and group. However, relationships between alarms cannot
generally be defined in a straightforward manner. E-mails can be generated or
predefined actions automatically executed in response to alarm conditions.
Trending
The products all provide trending facilities and one can summarise the common
capabilities as follows:
The parameters to be trended in a specific chart can be predefined or defined on-
line 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) Means
Multiple trending charts 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 trending feature is either provided as a separate module or as a graphical object
(ActiveX), which can then be embedded into a synoptic display. XY and other
statistical analysis plots are generally not provided.

Logging/Archiving
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.

Scripts
It is the combination of logical operators which are written in a statement. It is used
to run the applications made or stimulate before final execution. Various types of
scripts make project execution simpler for programmer.
Security
Every application has to be secured from unauthorized users by different security
levels .In SCADA this security can be given as a whole as well as individually.

Recipe Management
One of the finest features of any Scada .It explains that we can maintain various
recipes of different process and implement it on the process. All the recipes are
stored in a single server and it can be fetched by any client server from any area to
run the process.
Networking
It explains we can share SCADA applications on LAN or Internet as well exchange of
data is possible. Lot many Networking protocols are supported by Scada software.
Can be put on networking with other peripherals and processors with various
networking topologies.

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.
Tag names and tag types
Every symbol used in software has to be specified name .The logical name given to
any symbol is said to be tag [Link] types define the symbol category. It may be
discrete analog or strings.
Alarm management systems
In industrial plants and installations, control systems are used to monitor and
control processes. These control systems—whether a conventional Control Desk, a
computer/PLC system with SCADA, or a Distributed Control System (DCS)—provide
a man-machine interface to monitor and manage plant equipment and processes.
Alarm systems are an integral part of the man-machine interface. A typical alarm
system comprises both hardware and software, including:

 Field signal sensors

 Transmitters

 Alarm generators & handlers

 Alarm processors
 Alarm displays

 Annunciator window panels

 Alarm recorders and printers

Alarm systems indicate abnormal conditions and equipment issues to operators,
enabling corrective action to restore normalcy. Alarms are signaled to operators
through:
 Audible sounds
 Visual indicators (e.g., different colors or continuous blinking)

 Text messages

Alarm System Alerts Help Identify:

 Problems needing operator attention

 Process changes requiring corrective action

 Unsafe conditions before emergency shutdown
  Hazardous situations
 Deviations from normal/desired operating conditions

Functions of the Plant or Process Operator

Alarm systems assist operators in monitoring and controlling the plant, equipment,
and processes within safe operating limits. To design an effective alarm system, it is
important to understand the functions of an operator, which typically include:
 Ensuring safe and normal operation of plant/equipment

 Maintaining production at optimum levels

 Identifying abnormal, hazardous, and unsafe conditions and taking corrective
action
 Diagnosing faults and communicating them to maintenance teams

Operator responsibilities and priorities vary with plant conditions such as:

 During start-up

 During stabilization
 Under normal running conditions

 During abnormal conditions

 Emergency shutdown
 Planned shutdown

 Manual operation mode

 Automatic operation mode

Functions of an Alarm System

The main function of an alarm system is to alert the operator to abnormal plant
conditions that require timely assessment and corrective actions. Alarm systems:
 Alert, inform, and guide the operator
  Provide audible warnings, blinking/flashing indicators, and messages
 Display problem details and possible corrective actions

 Offer help or response guidance

 Provide feedback on actions taken (through supplementary displays when an
alarm is selected)

An Effective Alarm System

To ensure effectiveness, an alarm system should:
 Present only relevant and useful alarms to the operator

 Have a defined operator response for each alarm

 Include only necessary alarms (avoid nuisance alarms)

 Allow sufficient time for operators to respond

Alarm System Design

Designing an alarm system involves assessing each alarm’s:
 Importance

 Reliability

This requires qualitative and quantitative risk assessment to determine:

 Whether the alarm is safety-related

 If it should be stand-alone or integrated into the process control system

Safety-related alarms require special attention in the man-machine interface.

Assessment of Risk
Risk is a function of the probability and severity of hazards. Risk assessment must
cover:
 Safety hazards

 Environmental hazards
  Economic losses
Alarm systems are configured to minimize suboptimal operation and to protect
against damage, injury, or loss.

The design must clearly specify which risk each alarm is intended to reduce.

Protection Provided by the Alarm System

Protection from alarms occurs in two ways:

1. The operator is warned before a protection system activates
2. The operator is notified when a protection system fails to activate

Safety-Related Alarms

According to IEC 61508, an alarm system is safety-related only if:

 It is claimed to reduce hazard risks to an acceptable level

 It offers a significant reduction in risk, defined as PFDAvg < 0.1

 It is designed, operated, and maintained as per standards
 It is independent from the process control system (unless the control system
itself is safety-certified)
Purpose of an Alarm
Before configuring an alarm, consider:

1. What hazard or risk does the alarm address?

2. What are the consequences of failure or a missed alarm?

3. If the alarm is only informational, it should not be configured as an alarm
4. Conduct risk severity assessment (loss of life, injury, economic loss,
environmental impact)

5. Estimate risk occurrence frequency (e.g., once a week, monthly)

6. Are other protection systems available?

 7. Are there reliability claims requiring the alarm to be safety-classified?
8. What are the economic/environmental risks if not classified as safety-
related?
9. What if the sensor or instrument fails? Can it be validated or made
redundant?
10. Can the operator effectively respond? If not, the alarm has no benefit.
Operator Response

An operator’s response must be:

1. Clearly defined: Action, conditional action, or cognitive switch

2. Based on a clear and readable message

3. Supported by additional display information, if required

4. Timely: Consider how long the operator and plant take to respond

5. Guided by documented response procedures

Alarm Prioritization

When prioritizing alarms:

1. Assess consequences (safety, economic, environmental) of non-response
2. Determine time criticality and available response time

3. Assign priority based on severity and urgency

4. Consider whether priority needs to change under different plant conditions

Alarm Settings

For effective alarm thresholds, consider:

1. What is the normal process range?
2. What thresholds should be used (Low, Low-Low, High, High-High)?

3. Should settings change with plant operating conditions?

 4. What are normal fluctuations in process variables?
Alarm Suppression

Alarm suppression logic should be applied when:

1. Disturbances or plant trips would otherwise generate unnecessary alarms

2. More significant alarms occur simultaneously

3. Process variables exceed limits without actual risk

4. Specific signals can be used for logical suppression

5. Invalid or out-of-range variables may create nuisance alarms

Mitigation must ensure that:

 Operators are informed of suppression
 Unnecessary plant/equipment trips are avoided

 Alarm suppression does not interfere with critical interlocks

Real-time control and monitoring techniques
Real-time control and monitoring are the core functions of SCADA systems, enabling
operators to maintain immediate awareness of industrial processes and intervene
directly when necessary. These techniques are crucial for operational efficiency,
safety, and responsiveness.
Here's a breakdown of the key techniques:

I. Real-time Monitoring Techniques:

1. High-Speed Data Acquisition:
o Fast Polling Rates: SCADA systems are configured to poll (request data
from) RTUs, PLCs, and other field devices at very frequent intervals
(e.g., milliseconds to seconds) to ensure the data displayed is as
current as possible.
o Event-Driven Data: Instead of constant polling, some systems use
event-driven communication where field devices only send data when
a significant change or event occurs, reducing network traffic and
improving responsiveness for critical events.
o Data Aggregation at Edge: RTUs/PLCs often aggregate and preprocess
data locally before sending it to the SCADA master, optimizing the
amount of data transmitted and reducing latency.
2. Real-time Data Visualization (HMI/SCADA Screens):
o Dynamic Graphics: HMIs display live data on graphical representations
of the plant or process. This includes real-time values, changing colors
to indicate status (e.g., green for running, red for stopped/alarm),
animated movements (e.g., rotating pumps, flowing liquids), and filling
tanks.
o Trend Displays: Operators can view real-time and historical trends of
critical process variables on interactive graphs. This allows them to
 quickly identify deviations from normal operation, understand the rate
of change, and predict future behavior.
o Overview and Detail Screens: HMI design often follows a hierarchy,
with high-level overview screens providing a summary of the entire
system, and drill-down screens offering detailed views of specific
equipment or process areas.
o Situational Awareness: HMI design principles focus on minimizing
cognitive load, using consistent colors and symbols, and highlighting
critical information to help operators quickly grasp the situation,
especially during abnormal conditions.
o Alarm Banners and Summaries: Dedicated areas on the HMI (like
banners) display active alarms, their priority, and time of occurrence,
ensuring operators are immediately aware of critical events regardless
of the screen they are viewing.

3. Alarm Management:
o Alarm Generation: Alarms are triggered when process variables
exceed predefined limits, equipment status changes to an abnormal
state, or communication failures occur.
o Prioritization: Alarms are assigned priorities (e.g., critical, high,
medium, low) to guide operator response. Critical alarms might
require immediate action and louder alerts.
o Notification: SCADA systems can notify operators through various
channels:

 Audible alarms (horns, chimes)

 Visual alerts on HMI (flashing colors, pop-up windows)

 Email, SMS, or voice calls (for off-site personnel or escalation)
o Acknowledgment and Shelving: Operators acknowledge alarms to
indicate they are aware of the condition. Alarm shelving temporarily
 hides nuisance alarms to reduce clutter while the underlying issue is
being addressed, with mechanisms to ensure they are not
permanently forgotten.
o Alarm Suppression/Filtering: During planned operations (e.g., startup,
shutdown, maintenance), non-critical alarms can be temporarily
suppressed to prevent "alarm floods" that overwhelm operators.
Filtering allows operators to view only alarms relevant to their area of
responsibility.
o First-In-Fault Detection: Identifying the very first alarm in a cascade of
related alarms is crucial for root cause analysis, preventing operators
from chasing symptoms rather than the underlying problem.

4. Event Logging and Historical Data (Historian):

o Comprehensive Logging: The SCADA system logs all significant events,
including operator actions (setpoint changes, control commands),
system messages, and alarm activations/clears. Each event is time-
stamped for accurate record-keeping.
o Historian Database: A specialized database (historian) continuously
collects and stores vast amounts of time-series data from the process.
This data is essential for:
 Post-incident Analysis: Replaying events to understand what
happened during an upset.
 Performance Monitoring: Analyzing long-term trends to
identify operational inefficiencies.
 Predictive Maintenance: Using historical data to anticipate
equipment failures.
 Compliance Reporting: Generating reports for regulatory
requirements.
II. Real-time Control Techniques:
1. Direct Control through HMI:
o Setpoint Changes: Operators can directly adjust setpoints (desired
values) for process variables (e.g., desired temperature, flow rate) via
the HMI. The SCADA system then communicates this new setpoint to
the underlying PLC/RTU.
o Manual Control Actions: Operators can manually initiate control
actions, such as starting/stopping pumps, opening/closing valves, or
changing motor speeds, by clicking on graphical objects on the HMI
screens.
o Interlocks and Safety Mechanisms: SCADA systems incorporate safety
interlocks and permissive logic to prevent operators from issuing
unsafe commands (e.g., preventing a pump from starting if a valve is
closed, or not allowing a change beyond safe operating limits).
2. Automated Control Loops (via PLCs/RTUs):
o Feedback Control Loops (PID): This is the most common technique.
PLCs/RTUs implement control algorithms (like PID - Proportional-
Integral-Derivative) that continuously compare a measured process
variable (PV) to a desired setpoint (SP). Based on the difference (error),
the controller calculates and sends an output signal to an actuator
(e.g., a valve positioner, motor speed controller) to bring the PV back
to the SP. This happens automatically and in real-time at the PLC/RTU
level.
 Open Loop Control: Control action is independent of the
process output (e.g., turning a light on/off with a switch). Less
common in complex SCADA.
 Closed Loop Control: Control action is based on feedback from
the process (e.g., a thermostat controlling room temperature).
This is the dominant form in SCADA.
 o Sequential Control: Programming PLCs to execute a series of actions
in a specific order (e.g., a batch process with fill, mix, heat, drain steps).
o Logic Gates and Boolean Logic: Implementing simple ON/OFF control
based on logical conditions (e.g., if tank A is full AND valve B is open,
THEN start pump C).
o Cascade Control: One controller's output acts as the setpoint for
another controller, improving control accuracy and disturbance
rejection (e.g., a temperature controller adjusts the setpoint of a flow
controller for a heating medium).
o Advanced Process Control (APC): More sophisticated algorithms that
go beyond basic PID, optimizing multiple interacting variables to
achieve specific objectives (e.g., maximizing yield, minimizing energy
consumption). These are often implemented on dedicated control
platforms or as software layers above the basic SCADA/PLC level.

3. Command Execution and Verification:

o Secure Command Transmission: Control commands are transmitted
securely from the SCADA master to the RTUs/PLCs using robust
communication protocols.
o Command Confirmation: The SCADA system typically waits for
confirmation from the field device that the command was received and
executed successfully.
o Alarm on Non-Response: If a command is not acknowledged or the
desired change in the process variable does not occur within an
expected timeframe, an alarm is generated.
These real-time capabilities empower operators to effectively supervise and control
vast and complex industrial operations, ensuring safety, efficiency, and consistent
product quality.
Cloud-based SCADA systems
Industry 4.0 calls for deployment flexibility, and SCADA cloud solutions have
emerged as enablers of distributed operations, remote monitoring, and enterprise-
wide visibility.
Hybrid Deployment Options

Contemporary SCADA solutions should enable:

 Edge processing: Execution directly on local devices for low-latency control
and offline capability
 On-premises servers: Enabling legacy control center functionality with
added features
 Cloud deployment: Allowing remote access, central management, and
integration with cloud services
 Hybrid architectures: Blending these strategies to find the best balance of
performance, reliability, and cost
FrameworX demonstrates this adaptability through a uniform architecture applied
across deployment contexts, from embedded edge devices to enterprise cloud
installations. Its web-based portals take advantage of HTML5 and WebAssembly
technologies to provide rich visualization functionality no matter where processing
is done.
Horizontal and Vertical Scalability
As business expands, SCADA systems need to scale horizontally (increasing numbers
of sites and systems) and vertically (increasing numbers of data points, users, and
functionality). Industry 4.0-enabled platforms do this by:

 Containerized designs that enable deployment on distributed infrastructure

 Microservices designs that enable components to be scaled in isolation.
 Database clustering and partitioning for management of huge volumes of
data
  Load balancing and redundancy capabilities that ensure performance under
rising loads
These capabilities ensure that as your industrial operations evolve, your SCADA
infrastructure can grow seamlessly without disruptive re-architecting.
Cloud-based SCADA is enabled through an Industrial Internet of Things (IIoT)
ecosystem, such as Netilion. A second channel of information is opened and
transferred into the cloud. This channel is typically created using edge devices.
Once data is uploaded to the cloud, web applications can visualize it on any
internet-connected device. Communication in cloud-based SCADA is enabled via:

 HTTP protocol
 OPC/UA protocol

When to Use Cloud-Based SCADA vs. Local SCADA

1. Price Points
 Local SCADA requires hardware such as panel PCs or workstations installed
in the plant, increasing costs.
 Cloud-based SCADA uses existing internet-connected devices like
smartphones or PCs, making it potentially more cost-effective depending on
the use case.
2. Accessibility and Remote Monitoring

 Local SCADA requires on-site access.

 Cloud-based SCADA enables remote monitoring, which is ideal for processes
that need off-site supervision.
Use Case Differences
Control vs. Monitoring
One key difference is control capability:
 In cloud-based SCADA, data transfer is typically one-way (from field to
cloud), enabled via edge devices.

 This makes cloud SCADA more suitable for:

o Monitoring

o Visualization

o Data analysis
It lacks the control functionality commonly found in local SCADA systems. This is
largely due to security concerns, but control can be enabled if proper security
certifications (like ISO 27001) are in place.

When Cloud-Based SCADA is Advantageous

Cloud-based SCADA is ideal for applications where monitoring is the main focus,
particularly in remote or distributed locations. Some use cases include:

 Level monitoring in remote tanks or reservoirs

 Air or gas consumption tracking
 Emission, chimney, or wastewater monitoring

 Energy management systems

In these scenarios, data must be accessible remotely and in real-time, which cloud-
based solutions handle well.

Additional Benefits of Cloud SCADA

Cloud-based systems often provide an Application Programming Interface (API),
allowing you to:
 Integrate SCADA data with external systems
  Create custom dashboards
 Enable real-time analytics

This level of integration is not commonly available with local SCADA solutions.
Cyber security: SCADA system protection strategies
SCADA (Supervisory Control and Data Acquisition) systems are the backbone of
critical infrastructure, controlling and monitoring industrial processes across a
multitude of sectors like energy, water treatment, manufacturing, and
transportation. Due to their vital role, protecting them from cyber threats is of
paramount importance. A successful cyberattack on a SCADA system can lead to
severe consequences, including physical damage, operational disruption,
environmental harm, economic loss, and even loss of life.
Here's a comprehensive overview of SCADA system protection strategies, drawing
from industry best practices and frameworks:

1. Network Segmentation and Isolation (The Foundation):

 Air Gapping/Physical Separation (where feasible): Historically, "air gapping"
(physical isolation from external networks) was the ideal. While true air gaps
are rare today due to IT/OT convergence, the principle of strong isolation
remains.
 Segregate IT and OT Networks: This is a fundamental and non-negotiable
step. The corporate IT network (email, web Browse, business applications)
should be strictly separated from the Operational Technology (OT) network
where SCADA systems reside. This prevents typical IT cyber threats from
easily propagating to critical control systems.
 Demilitarized Zones (DMZs): Implement secure DMZs (buffer zones)
between the IT and OT networks. All communication between these two
environments must pass through the DMZ, where it can be inspected,
filtered, and controlled by firewalls and other security devices.
 Micro-segmentation within OT: Further divide the SCADA (OT) network into
smaller, isolated segments based on function, criticality, or device type. For
example, separate segments for PLCs, HMIs, engineering workstations, and
historians. This limits lateral movement for attackers if one segment is
compromised, akin to bulkheads in a ship containing a leak.
  Firewalls and Intrusion Detection/Prevention Systems (IDS/IPS): Deploy
robust, industrial-grade firewalls to control traffic between all network
segments and at the perimeter of the OT network. Implement IDS/IPS
specifically designed for OT environments that can understand and inspect
industrial protocols (e.g., Modbus, DNP3, OPC UA) to detect and block
malicious or anomalous activities.
 Network Whitelisting: Implement network whitelisting rules that explicitly
allow only approved devices and applications to communicate within and
between SCADA network segments. All other traffic is implicitly denied.

2. Strong Access Control and Authentication:

 Principle of Least Privilege (PoLP): Grant users (and automated
processes/devices) only the minimum access necessary to perform their
specific job functions. Avoid widely distributing administrative or "superuser"
privileges.
 Multi-Factor Authentication (MFA): Implement MFA for all access to SCADA
systems, especially for remote access, administrative accounts, and critical
control functions. This adds a crucial layer of security beyond just passwords.
 Strong Password Policies: Enforce complex password requirements (length,
special characters, mix of cases), mandate regular password changes, and
strictly prohibit the use of default or easily guessable credentials.
 Role-Based Access Control (RBAC): Define distinct user roles (e.g., Operator,
Engineer, Administrator, Read-Only Viewer) and assign permissions based on
these roles, ensuring that users can only interact with the SCADA
components relevant to their duties.
 Limit and Monitor Remote Access: Strictly control and monitor all remote
access to SCADA systems. Utilize secure VPNs with strong encryption and
endpoint validation. Implement jump hosts or bastion servers as
intermediaries, ensuring no direct remote access to critical devices. All
remote sessions should be logged and monitored. Disable remote access
channels when not in use.
3. Device Hardening and Secure Communication:
 Regular Patching and Updates: Establish a structured and tested patch
management process for all SCADA system components, including operating
systems, SCADA software, PLC/RTU firmware, and HMI applications. This is
critical for addressing known vulnerabilities. Due to the sensitive nature of
OT, patches often require thorough testing in a non-production environment
before deployment.
A system with unpatched vulnerabilities but zero external connectivity (Air
Gapped) has a near-zero remote attack surface, whereas a fully patched
system directly connected to the public internet has a huge attack surface.
 System Modernization: Plan for upgrading or replacing legacy SCADA
systems and devices that operate on outdated software and lack modern
security features. This is a long-term strategy but essential for reducing the
attack surface.
 Disable Unnecessary Services and Ports: Configure all SCADA devices
securely by disabling any services, applications, or open ports that are not
absolutely essential for their operational function. Minimize the attack
surface.
 Secure Communication Protocols: Whenever possible, use secure versions
of industrial protocols or implement encryption (e.g., TLS/SSL, IPsec VPNs)
for data in transit, especially for critical telemetry data or control commands,
to ensure confidentiality and integrity.
 Tamper Detection Devices: Deploy physical tamper detection sensors on
critical SCADA hardware in remote locations to alert personnel to
unauthorized physical access attempts.
4. Continuous Monitoring and Anomaly Detection:
 Industrial Intrusion Detection Systems (IDS/IPS): Utilize specialized OT-
aware IDS/IPS solutions that can parse and understand industrial protocols
 to monitor for unusual command sequences, unauthorized configuration
changes, unexpected data flows, or attempts to exploit known vulnerabilities.
 Security Information and Event Management (SIEM) Systems: Collect and
centralize logs from all SCADA components, network devices, and security
tools into a SIEM system. This enables comprehensive analysis, correlation of
events, and real-time alerting for suspicious activities.
 Behavioral Analytics: Implement tools that establish a "baseline" of normal
SCADA system behavior (e.g., typical data ranges, command patterns,
communication flows). Deviations from this baseline can indicate potential
security incidents.
 Regular Security Audits and Assessments: Conduct periodic security audits,
vulnerability assessments, and penetration tests specifically tailored for OT
environments to identify weaknesses, misconfigurations, and compliance
gaps.
 Threat Intelligence Integration: Subscribe to and integrate relevant industrial
control system (ICS) threat intelligence feeds to stay informed about
emerging threats, vulnerabilities, and attack techniques targeting SCADA
systems.
5. Incident Response and Recovery:
 Develop a Comprehensive Incident Response Plan (IRP): Create a detailed,
written plan for responding to cybersecurity incidents targeting SCADA
systems. This plan should include:
o Roles and responsibilities for a multi-disciplinary team (OT engineers,
IT security, management, legal, communications).
o Procedures for incident detection, analysis, containment, eradication,
recovery, and post-incident review.
o Specific playbooks for common SCADA attack scenarios (e.g.,
ransomware, denial-of-service, unauthorized access).
  Conduct Regular Tabletop Exercises and Simulations: Periodically test the
IRP in simulated attack scenarios to ensure that personnel understand their
roles, the procedures are effective, and communication channels work under
pressure.
 Backup and Recovery Plan: Implement robust, regular, encrypted, and
isolated (offline) backups of all critical SCADA system data, software
configurations, and operating system images. Critically, regularly test the
restoration process to ensure recoverability and minimize downtime in the
event of a catastrophic incident.
 Disaster Recovery (DR) and Business Continuity (BC) Plans: Integrate SCADA
incident response into broader organizational DR and BC plans to ensure the
continuation of essential operations even after a major cyberattack or other
disruption.
6. Human Factor and Third-Party Management:
 Employee Training and Awareness: Conduct regular and mandatory
cybersecurity awareness training for all personnel (operators, engineers, IT
staff, contractors) who interact with SCADA systems. Educate them on social
engineering, phishing, malware, physical security protocols, and incident
reporting procedures. Foster a strong security-conscious culture.
 Secure Physical Locations: Ensure that all SCADA hardware (servers,
workstations, PLCs, RTUs, communication equipment) is housed in secure,
monitored facilities with controlled access (e.g., card readers, biometrics),
surveillance systems, and detailed access logs.
 Vendor Risk Management: Establish a robust program for vetting and
managing cybersecurity risks associated with third-party vendors, suppliers,
and service providers who may have remote or physical access to SCADA
systems. Implement strict contracts outlining security requirements, conduct
regular audits, and limit their access to only what is absolutely necessary.
  Supply Chain Security: Address the security of hardware and software
components acquired from the supply chain, as malicious implants or
vulnerabilities introduced during manufacturing can pose significant risks.
7. Adherence to Standards and Frameworks:
 NIST Cybersecurity Framework (CSF): A widely adopted, voluntary
framework that helps organizations manage and reduce cybersecurity risks.
It provides a flexible, risk-based approach with five core functions: Identify,
Protect, Detect, Respond, and Recover (and a new "Govern" function in CSF
2.0).
 ISA/IEC 62443 Series of Standards: These international standards specifically
address the security of industrial automation and control systems (IACS),
including SCADA. They provide a comprehensive framework covering
technical, operational, and governance aspects of ICS security.
 CISA (Cybersecurity and Infrastructure Security Agency) Guidelines: CISA
provides valuable resources, alerts, and best practices for securing critical
infrastructure, including specific guidance for ICS/SCADA.
By implementing a multi-layered, defense-in-depth approach incorporating these
strategies, organizations can significantly enhance the cybersecurity posture of
their SCADA systems and reduce the risk of successful cyberattacks.

Metric What it Indicates Relevance

Exposure. How many ways can an The most practical measure of

Attack Surface
attacker get into the SCADA. overall system risk.

Technical Severity. How bad is a Used to prioritize which patches

CVSS Score
specific software bug? to apply first.

MTTD (Mean Resilience. How long does a Indicates the vulnerability of your
Time to hacker exist in the system before defense team, not just the
Detect) being caught? hardware.

Business Impact. Likelihood of Used by management to budget

Risk Score
attack $\times$ Cost of impact. for security upgrades.
AI and Machine Learning: Predictive maintenance
AI and Machine Learning (ML) are revolutionizing predictive maintenance in SCADA
(Supervisory Control and Data Acquisition) systems, moving industries beyond
reactive "break-fix" and scheduled "preventive" maintenance to a more proactive
and optimized approach. By leveraging the vast amounts of data collected by SCADA
systems, AI/ML can anticipate equipment failures, optimize maintenance
schedules, reduce downtime, and improve overall operational efficiency and safety.

How AI/ML Enhances Predictive Maintenance in SCADA:

1. Advanced Data Acquisition and Processing:
o High-Volume Data Ingestion: SCADA systems are already collecting a
wealth of real-time and historical data (temperature, pressure,
vibration, current, voltage, motor speed, flow rates, operational logs,
alarm history, etc.). AI/ML thrives on this large volume of data.
o Data Quality and Preprocessing: AI/ML models require clean,
consistent data. SCADA data, while extensive, can sometimes be
noisy or incomplete. AI/ML pipelines involve robust data cleaning,
normalization, outlier detection, and feature engineering to prepare
the data for analysis.
o Multi-Source Integration: AI/ML can integrate data not only from
SCADA's operational data but also from other sources like Enterprise
Resource Planning (ERP) for spare parts inventory, Computerized
Maintenance Management Systems (CMMS) for maintenance history,
and even weather data, to create a holistic view.

2. Sophisticated Pattern Recognition and Anomaly Detection:

o Beyond Thresholds: Traditional SCADA systems use fixed thresholds
to trigger alarms. AI/ML algorithms can go beyond this by identifying
subtle, complex patterns and correlations in multi-variable data that
might precede a failure, even if individual parameters are still within
normal "safe" limits.
 o Anomaly Detection: Unsupervised learning algorithms can detect
deviations from "normal" operating behavior without prior
knowledge of what a "failure" looks like. This is crucial for identifying
novel failure modes.
o Failure Signatures: Supervised learning models can be trained on
historical data where failures have occurred, learning the unique
"signatures" (patterns of sensor readings) that indicate impending
equipment degradation.
3. Predictive Analytics and Remaining Useful Life (RUL) Estimation:
o Failure Prediction: ML models (e.g., regression models, decision
trees, neural networks) can predict when a piece of equipment is
likely to fail or if it will fail within a certain timeframe.
o Remaining Useful Life (RUL): AI/ML can estimate the RUL of critical
assets, providing a proactive indication of how much longer a
component can operate reliably before maintenance is required. This
allows for optimal scheduling.
o Prescriptive Maintenance: Beyond just predicting, advanced AI can
recommend what maintenance actions should be taken, when, and
even suggest optimal resource allocation (e.g., ordering parts,
scheduling technicians).

4. Optimized Maintenance Scheduling:

o Just-in-Time Maintenance: Instead of fixed schedules or emergency
repairs, AI/ML enables maintenance to be performed precisely when
needed, just before a predicted failure. This minimizes unnecessary
maintenance costs and maximizes equipment uptime.
o Resource Planning: By accurately predicting maintenance needs,
organizations can optimize the allocation of spare parts, labor, and
tools, reduce inventory costs and improving technician efficiency.
 o Batch Maintenance: AI can identify when multiple components on
the same asset are likely to fail, allowing for coordinated
maintenance activities to minimize downtime.
5. Continuous Learning and Adaptation:
o Model Refinement: AI/ML models continuously learn from new data,
improving their accuracy and adaptability over time. As more
operational and failure data is collected through the SCADA system,
the models become more precise.
o Digital Twins (Advanced): In highly advanced implementations,
AI/ML models can be integrated with digital twins – virtual replicas of
physical assets. The digital twin receives real-time SCADA data, and
the AI/ML model simulates and predicts the asset's behavior,
allowing for scenario testing and proactive intervention in the virtual
world before affecting the physical asset.

AI/ML Techniques Used in SCADA Predictive Maintenance:

 Supervised Learning:
o Classification: Predicting discrete outcomes (e.g., "Will fail in next 30
days," "Healthy," "Degraded"). Algorithms: Support Vector Machines
(SVMs), Random Forests, Gradient Boosting, Neural Networks.
o Regression: Predicting continuous values (e.g., RUL in days/hours).
Algorithms: Linear Regression, Ridge Regression, Neural Networks.

 Unsupervised Learning:
o Anomaly Detection: Identifying data points that deviate significantly
from the learned "normal" behavior. Algorithms: Isolation Forests,
Autoencoders, K-means clustering (for identifying abnormal clusters).
 Deep Learning: Neural networks (especially Recurrent Neural Networks like
LSTMs for time-series data) are highly effective at learning complex patterns
in large, sequential SCADA datasets.
  Reinforcement Learning (Emerging): For optimizing maintenance strategies
over time by learning from outcomes of previous maintenance decisions.

Benefits of AI/ML in SCADA Predictive Maintenance:

 Reduced Unplanned Downtime: Proactive identification of potential
failures prevents costly unexpected shutdowns.
 Lower Maintenance Costs: Fewer emergency repairs, optimized scheduling,
and reduced unnecessary preventive maintenance. McKinsey reports
suggest AI can cut maintenance downtime by 30-50% and increase machine
life by 20-40%.
 Extended Equipment Lifespan: Addressing issues before they escalate
prolongs the life of expensive assets.
 Improved Safety: Predicting failures in critical equipment reduces the risk
of accidents and hazards.
 Enhanced Operational Efficiency: Smoother operations due to fewer
disruptions and optimized resource utilization.
 Better Resource Management: Optimized spare parts inventory, labor
allocation, and maintenance scheduling.
 Data-Driven Decision Making: Insights from AI/ML empower operators and
managers to make more informed decisions.
Challenges of Implementation:
 Data Quality and Quantity: AI/ML models require large volumes of clean,
labeled, and representative data, especially historical failure data, which can
be scarce or inconsistent in OT environments.
 Integration with Legacy Systems: Many SCADA systems and industrial
assets are legacy systems that may not have the sensors or connectivity
needed for easy data extraction. Retrofitting can be costly.
  OT/IT Convergence: Bridging the gap between operational technology (OT)
data and information technology (IT) infrastructure for AI/ML processing
requires specialized expertise and secure integration.
 Cybersecurity Risks: While enabling benefits, the increased connectivity
required for data collection can introduce new cybersecurity vulnerabilities
if not managed carefully.
 Domain Expertise: Interpreting AI/ML outputs and acting on predictions
requires close collaboration between data scientists and domain experts
(maintenance engineers, operators) who understand the industrial process.
 Trust and Acceptance: Gaining the trust of maintenance personnel and
operators in AI-driven recommendations is crucial for successful adoption.
 Explainable AI (XAI): Understanding why an AI model made a particular
prediction (its "explainability") is often critical in industrial settings to build
trust and troubleshoot issues.
Despite the challenges, the integration of AI and ML into SCADA systems for
predictive maintenance is a transformative trend that is reshaping industrial
operations, leading to more resilient, efficient, and cost-effective processes.
Module 3 Quiz
1. Which SCADA topology has central servers and remote HMI clients on a LAN?
A. Monolithic
B. Distributed
C. Peer-to-Peer
D. Edge-only
Answer: B

2. In OPC UA, secure communication uses:

A. HTTP BASIC authentication
B. X.509 certificates
C. Plain-text usernames
D. FTP encryption
Answer: B

3. Modbus function code 03 reads:

A. Discrete Inputs
B. Coils
C. Holding Registers
D. Input Registers
Answer: C

4. An alarm with priority “HH” is typically:

A. Lowest importance
B. High-High (critical)
C. Historical log only
D. Maintenance reminder
Answer: B

5. ISA 18.2 defines:

A. Ethernet/IP
B. Alarm management best practices
C. Wireless sensor specs
D. Batch-control standards
Answer: B

6. Event-driven data updates are implemented via:

A. Modbus polling
B. OPC UA subscriptions
C. HTTP GET loops
 D. FTP transfers
Answer: B

7. A historian database should support:

A. Uncompressed raw storage only
B. Data aging and compression
C. Only alarm logs
D. Flat-file CSV exports exclusively
Answer: B

8. MQTT is best described as:

A. A batch-file protocol
B. Publish/subscribe messaging
C. A database query language
D. A serial-link standard
Answer: B

9. Which port is default for Modbus TCP?

A. 80
B. 502
C. 44818
D. 1234
Answer: B

10. Network segmentation for SCADA prevents:

A. Faster polling
B. Unauthorized lateral movement
C. Data compression
D. HMI scripting errors
Answer: B

11. A DMZ in SCADA architecture is used to:

A. Increase scan time
B. Isolate control network from business network
C. Archive historian data
D. Host the HMI only
Answer: B

12. Which protocol supports unsolicited responses?

A. Modbus RTU
B. DNP3
 C. OPC DA
D. HTTP
Answer: B

13. Alarm shelving means:

A. Permanently deleting an alarm
B. Temporarily hiding an alarm for a set time
C. Escalating alarm priority
D. Logging and clearing automatically
Answer: B

14. In a recipe manager, setpoints are stored as:

A. Tags in PLC only
B. Profiles in SCADA database
C. CSV files on HMI client
D. Firmware parameters
Answer: B

15. A lost TCP connection can be auto-recovered by:

A. Rebooting SCADA server
B. Enabling client-side reconnect
C. Increasing baud rate
D. Changing IP subnet
Answer: B

16. Time-sync between PLC and SCADA is typically via:

A. NTP
B. FTP
C. SMTP
D. SNMP
Answer: A

17. Which is NOT a SCADA security measure?

A. VLAN isolation
B. SNTP synchronization
C. IDS/IPS deployment
D. Multi-factor VPN
Answer: B

18. Cloud SCADA often uses:

A. Direct serial links
 B. MQTT over TLS
C. Profibus DP
D. Fieldbus over USB
Answer: B

19. A trend view shows:

A. Alarm priority only
B. Historical tag values over time
C. User login history
D. Network bandwidth usage
Answer: B

20. Which tool helps diagnose serial comms?

A. Wireshark
B. Serial sniffer (e.g., PortMon)
C. SCADA simulator
D. Spreadsheet
Answer: B