TOPIC 3: SCADA SYSTEMS, SOFTWARE AND

PROTOCOLS
COURSE: SUPERVISORY CONTROL AND DATA ACQUISITION
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on
the hardware to be implemented.
User interface
 Keyboard
 Mouse
 Trackball
 Touch screen

Graphics displays
 Customer-configurable, object orientated and bit mapped
 Unlimited number of pages
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on the hardware to be
implemented.
Alarms
 Client server architecture
 Time stamped alarms to 1 millisecond precision (or better)
 Single network acknowledgment and control of alarms
 Alarms are shared to all clients
 Background trend graphics
 Real-time multi-pen trending
 Short- and long-term trend display
 Length of data storage and frequency of monitoring can be specified on a per-point basis
 Archiving of historical trend data
 On-line change of time-base without loss of data
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on the hardware to be
implemented.
Alarms
 Dynamic allocation of alarm pages
 User-defined formats and colors
 Up to four adjustable trip points for each analog alarm
 Deviation and rate of change monitoring for analog alarms
 Selective display of alarms by category (256 categories)
 Historical alarm and event logging
 Context-sensitive help
 On-line alarm disable and threshold modification
 Event-triggered alarms
 Alarm-triggered reports
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on
the hardware to be implemented.
Trends
 Client server architecture
 True trend printouts not screen dumps
 Rubber band trend zooming
 Export data to DBF, CSV files
 X/Y plot capability
 Event based trends
 Pop-up trend display
 Trend gridlines or profiles
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on the hardware to be
implemented.
Access to data
 Direct, real-time access to data by any network user
 Third-party access to real-time data, e.g. Lotus 123 and Excel
 Network DDE (Dynamic Data Exchange) Network DDE is used to initiate and maintain the network connections needed for DDE
conversations between applications running on different computers in a network. A DDE conversation is the interaction between client and
server applications.
 DDE compatibility: read, write and exec
 DDE to all IO device points
 Clipboard

Database
 ODBC (Open Database Connectivity) driver support
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on
the hardware to be implemented.
Networking
 Supports all NetBIOS compatible networks such as NetWare, LAN Manager, Windows for Workgroups,
Windows NT (changed from existing)
 Support protocols NetBEUI, IPX/SPX, TCP/IP and more
 Centralized alarm, trend and report processing – data available from anywhere in the network
 Dual networks for full LAN redundancy
 No network configuration required (transparent)
 May be enabled via single check box, no configuration

 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on
the hardware to be implemented.
Networking
 Multi-user system, full communication between operators
 RAS (Remote Access Server) and WAN supported with high performance
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally, these features depend on the hardware to be
implemented.
Fault tolerance and redundancy
 Dual networks for full LAN redundancy
 Redundancy can be applied to specific hardware
 Supports primary and secondary equipment configurations
 Intelligent redundancy allows secondary equipment to contribute to processing load
 Automatic changeover and recovery
 Redundant writes to PLCs with no configuration
 Mirrored disk I/O devices
 Mirrored alarm servers
 Mirrored trend servers
 SCADA KEY FEATURES

Typical key features expected of the SCADA software are listed below. Naturally these features depend on
the hardware to be implemented.

Client/server distributed processing

 Open architecture design
 Real-time multitasking
 Client/server fully supported with no user configuration
 Distributed project updates (changes reflected across network)
 Concurrent support of multiple display nodes
 Access any tag from any node
 SCADA SOFTWARE PACKAGE

There have been two main approaches to follow in designing the SCADA system in the past:
They are centralized and distributed.
o Centralized, where a single computer or mainframe performs all plant monitoring, and all plant data is
stored on one database that resides on this computer.
o Distributed, where the SCADA system is shared across several small computers (usually PCs).
CENTRALIZED PROCESSING
DISTRIBUTED PROCESSING
CLIENT SERVER APPROACH APPLIED TO SCADA SYSTEM
A TYPICAL
LARGE
SCADA
SYSTEM
REDUNDANCY

If any processes or activities in the system are critical, or if the cost of loss of production is high, redundancy
must be built into the system.
This can be done in several ways such as dual server redundancy or dual LANs and PLCs
The key to the approach is to use the client–server approach, which allows for different tasks (comprising the
SCADA system) to run on different PC nodes.
DUAL SERVER REDUNDANCY
DUAL LANS AND PLCS
SYSTEM RESPONSE TIME
Typical speeds that are considered acceptable are:
EXPANDABILITY OF THE SYSTEM
It is important to specify the expansion requirements of the system, so that:
 INTRODUCTION TO PROTOCOLS
The transmission of information (both directions) between the master station and RTUs using time division
multiplexing techniques requires the use of serial digital messages.
These messages must be efficient, secure, flexible, and easily implemented in hardware and software.
Efficiency is defined as:
 Information bits transmitted ÷ Total bits transmitted
All messages are divided into three basic parts as follows:
A TYPICAL ASYNCHRONOUS MESSAGE FORMAT

A typical example of commonly used asynchronous message format is shown below:

 THE MESSAGE ESTABLISHMENT FIELD

The message establishment field has three components:

THE INFORMATION FIELD

The information field contains 20 bits, of which eight bits are a function code and 12 bits are used for data.
o For remote-to-master messages, this represents the first message in a sequence, additional messages directly
following the first message also transmit information in the RTU address and function code spaces, so that
24 bits of data are transmitted.
o These 24 bits may contain two 12 bit analog values or 24 device statues.
o Additional discussion of the use of the information field is contained in the section ‘information transfer’.
THE MESSAGE TERMINATION FIELD
INFORMATION TRANSFER
Master-to-remote data transfer Information transmitted from master to remote is for the purpose of device
control, setpoint control, or batch data transfer.
Due to the possible severe consequences of operating the wrong device or receiving a bad control message,
additional security is required for control.
This is provided in the form of a sequence of messages, commonly called a select-before-operate sequence, as
shown in the figure below:
INFORMATION TRANSFER

 Message establishment and message termination

fields are not shown.
 Function code specifies the operation to be
performed by the RTU.
 Control address specifies the device or set-point
to be controlled.
 Set-point provides the value to be accepted by
the RTU.
 A remote-to-master check-back message is
derived from the RTU point selection hardware
in order to verify that the RTU has acted
correctly in interpreting the control selection.
BATCH DATA TRANSFER

Batch data transfers from master to remote include

such data as parameters for report by exception
and parameters for locally controlled devices. This
type of transfer is accomplished by the sequence
shown in Figure
 REMOTE-TO-MASTER DATA TRANSFER

 Remote-to-master data transfer. All remote-to-master data transfer is accomplished with one basic
message sequence by using variations in the field definitions to accommodate different types of data. The
basic sequence is shown in the figure below:
EXAMPLE MESSAGES
 ERROR DETECTION

Most error detection schemes involve having

redundant bits transmitted with the message
to allow the receiver to detect errors in the
message bits (and sometimes to reconstruct
the message without having to request a
retransmission).
Typically a signal transmitted across any
form of transmission medium can be
practically affected by four phenomena:
FEEDBACK ERROR CONTROL

Message security. It is essential to protect against fake control action and corruption of data resulting from
communication noise.
o Security is achieved by adding a check code to each transmitted message.
o The concept is for the transmitting station to calculate the check code from the message pattern.
o The receiving station then repeats the same check code calculation on the message and compares its
calculated check code to that of the message received.
o If they are identical it is assumed that the received message has not been corrupted. If they are different the
message is discarded.
DISTRIBUTED NETWORK PROTOCOL

Introduction. The distributed network protocol is a data acquisition protocol used mostly in the electrical and
utility industries.
o It is designed as an open, interoperable and simple protocol specifically for SCADA controls systems.
o It uses the master/slave polling method to send and receive information, but also employs sub-masters
within the same system. The physical layer is generally designed around RS-232 (V.24), but it also supports
other physical standards such as RS-422, RS-485 and even fiber optic.
o The distributed network protocol is an interoperable protocol designed specifically for the electric utilities,
oil, gas, and water/waste water and security industries.
o As a data acquisition protocol, the need to interface with many vendors equipment was and is necessary.
o The DNP was created with the philosophy of being a completely open standard.
o Since no one company owns the DNP standard it means that producers of equipment feel that they have a
level playing field on which to compete
PHYSICAL LAYER OF DNP

The physical layer of DNP is a serial bit oriented asynchronous system

using 8 data bits, 1 start bit, 1 stop bit and no parity. Synchronous or
asynchronous is also allowed.
o It has two physical modes of operation, direct mode (point-to-
point) or serial bus mode (multidrop).
o The two modes are not usable at the same time. Both modes can be
half or full duplex.
o The DNP protocol supports five communication modes, two-wire
point-to-point, two wire multidrop, four-wire point-to-point, four-
wire multidrop, and dial up modems.
o A system with only two nodes, a master and a slave is called a
direct bus.
o If the system is multidrop with multiple nodes, it is called a serial
bus.
 TWO WIRE DIRECT MODE
 Two wire point-to-point. The DNP protocols physical layer supports point-to-point communications. The two wire half-duplex mode
usually uses RS-485 or a two-wire modem as a physical system. If a modem is used, then the interface to the modem usually uses the
V.24 ITU standard (RS-232). The two-wire mode does not support a full duplex operation within DNP, only halfduplex. With the
point-to-point mode there is no possibility of collisions. The master transmits the frame and then the slave responds.
 TWO WIRE MULTIDROP

 Two wire multidrop. The DNP physical layer supports multi-point communications. The two wire multidrop mode usually
uses RS-485, fiber optic or Bell 202 modems as a physical system. The two-wire mode does not support a full duplex
operation within DNP, only half-duplex. With the multidrop two wire mode there are possibilities of collisions. This is
possible because two masters or slaves can access the line at the same time. To overcome this DNP inserts a time delay after
the loss of carrier. Carrier is an indication that someone is transmitting on the two-wire bus. In a two-wire multimode, all
devices on the line must have some way of determining that someone is transmitting.
 FOUR WIRE POINT-TO-POINT

 Four wire point-to-point. Four-wire point-to-point is used within DNP as a full duplex master to slave system. The
physical standards used are RS-422, RS-232 and four wire modems. Since this mode is only point-to-point, there is
no problem with collisions.
 FOUR WIRE MULTI-POINT
 Four wire multi-point. DNP allows for a four wire multi-point mode. This mode can use half or full duplex
communications, although again full duplex is rarely used. The reason full duplex is not used is because of the
complexity of collision avoidance. Having multiple devices all talking at the same time in both directions is difficult
at best to implement.
 DIAL UP MODEM
 Dial up modem. The DNP supports the use of a dial up modem mode. This mode is a point-to-point circuit. It usually
uses V.24 as a connection system (RS-232). DCD is used differently in this case because carrier detect in modems
means that a line has been established, not that data is being sent.
 There is no way for the local end to tell the remote end that data is being transferred. It is then up to the remote end to
be able to detect data coming in.
 NEW TECHNOLOGIES IN SCADA SYSTEMS

A few of the new developments that are occurring in SCADA technology will be briefly listed below. The rapid advance
in communications technology is an important driving force in the new SCADA system.

 Rapid improvement in LAN technology for master stations. LANs are increasingly forming a key component of
the master stations with dual redundant LANs being able to provide very reliable systems. The movement to higher
speed LANs (100 Mbit/sec up from 10 Mbit/sec) are providing faster response times.
 Man machine interface. Typical areas where improvements are occurring are: Improved graphics on the operator
stations with the operator planning and zooming on the system on-line to arrive at any given subset of the network.
Improved response times on the operator interfaces.
 NEW TECHNOLOGIES IN SCADA SYSTEMS

Remote terminal units

 Decentralized processing of the data at the RTU rather than the master station
 Further decentralized gathering of data from intelligent instruments, which transfer the data back to the RTU over a
communication network
 Redundancy of RTUs is easily implemented on I/O, CPU, power supplies etc
 Multiple communications with multiple masters with partitioned (separate) databases for each master station
 User generated programs could be run in the RTU to reduce the number of alarm traffic to master station (by
combining alarms, filtering or irrelevant alarms)
 Checking on the validity of real-time data received
 Inter RTU communications (rather than through the master stations)
 Sophisticated man-machine interfaces directly connected to RTU
 NEW TECHNOLOGIES IN SCADA SYSTEMS

Communications
 Open standards (i.e. non-vendor specific) are appearing to interface RTUs to the master stations
 Spread spectrum satellite – an improved, low cost and low power method of transferring data over a satellite system
for remote site RTUs
 Fiber optics – lower cost and ease of installation is making this an attractive option
 THE GOLDEN RULES

A few rules in specifying and implementing a SCADA system are listed below:
 Apply the ‘KISS’ (keep it simple stupid) principle and ensure that the implementation of the SCADA system is
simple.
 Ensure that the response times of the total system (including the future expansion) are within the correct levels
(typically less than one-second operator response time).
 Evaluate redundancy requirements carefully and assess the impact of failure of any component of the system
on the total system.
 Apply the open systems approach to hardware selected and protocols communication standards implemented.
Confirm that these are indeed TRUE open standards.
 Ensure that the whole system including the individual components provide a scaleable architecture (which can
expand with increasing system requirements).
 Assess the total system from the point of view of the maximum traffic loading on the RTU, communication
 THE GOLDEN RULES

 Ensure that the functional specification for the system is clearly defined as far as number of points are
concerned, response rates and functionality required of the system.
 Perform a thorough testing of the system and confirm accuracy of all data transferred back, control actions
and failure of individual components of system and recovery from failures.
 Confirm operators of individual components of the system in the (industrial)
environment to which they would be exposed (including grounding and isolation of the system).
Ensure that all configuration and testing activities are well documented.
 Ensure that the operational staffs are involved with the configuration and implementation of the system and
they receive thorough training on the system.
 Finally, although the temptation is there with a sophisticated system, do not overwhelm the operator with
alarm and operational data and crowded operator screens. Keep the information of loading to the operator
clear, concise and simple.