thank you for joining me in this

protocol overview basically I will

provide three main subjects I'll cover

the what's an electrical SCADA

protocol the history of protocols and

communication protocols the

classification in this very section

we're going to cover three topics

what's an electrical SCADA protocol an

example of a protocol encoding and

finally we'll talk about protocol layer

in an electrical supervisory control and

data acquisition system SCADA a non-id

which stands for an intelligent

electronic device in a substation

supervisory station and control centers

communicate data and control message in

a compact and coded signal over a

physical communication media the

structure of the encoded signal is

governed by a set of rules known as

communication protocol the communication

could be a local to the substation one

device to another device in a substation

or for an example a data concentrated

like the d20 collecting data from a

controller this controller Bay

controller could be controlling all the

applications in a Bay or it could be

over a wide geographic area where you've

got concentrator communicating to a

control center or it could be from one

control center to another control center

for example good protocol is the ICCP

protocol which stands for enter control

center communication protocol and that

would govern the communication between

one control center to another control

center by governing the complete

communication I mean that it will set

the rules for how the message should

look like between one control center

device to another control center

receiving device at the other center

for example in a substation if we have

two devices one of the devices that I

think as a master like the 20

communicating to our you are relay the

d20 needs to get a digital set of

digital inputs basically digital input

one to five from a relay with others of

two and the d20 address is four and the

preferred the communication protocol in

this case let's say is DMP protocol

version X the reason I'm referring to

this as version X that first the

protocol itself that I'm giving as an

example here does not exist I'm just

giving an oversimplification of a DMP

protocol because the DMP protocol

contains many features like we're going

to explain in the last section of this

demonstration so a simplification will

help our learning to understand what how

a protocol would impact the message

being transmitted between one IV to

another ie D so if we look at this

example basically the first part of the

message would be the identifier of the

message so in a machine language which

is zeros or ones where 0 stands for 0

volt and 5 stands 5 volts would stand

for the value of 1 the first thing that

we will take a look at is the hex value

0 5 64 which stands for protocol

identified then in the same message we

will have the from atoms in this case

it's X 4 after that will come the to

address which is hex - and every message

would have a functional code so the

functional code in this case is hex one

our hex value 1 and like I said earlier

we are asking for a starting point 1 all

the way to the ending point 5 and

that every message would have a cyclic

redundancy check or a message check in

it
I mean I'm giving one two three four

probably it's going to be some

mathematical formula that calculates the

message equation for CRC so in this case

that message would translate into zero

five sixty four zero four zero two zero

one zero one zero five one two three

four this is the full message in hex now

this hex message would be then

translated into machine language ones

and zeros that would be transmitted over

the wire as we said earlier using the

voltage sensing levels of zero to five

and translated at the other end in the

same manner from voltage level into

vitsin voice and into a meaningful

message for the device to take

appropriate action before we start to

talk about history of protocols with the

advent of new communication standards

after the protocols the new standards

rely on combining best protocols to

achieve efficiency and improved

functionality so the latest standards

for example the 61 850 standard if we

want to communicate protocol like MMS

over tcp/ip in order to achieve

communication of data over physical

networks are up basically the message

will consist of MMS message including

enveloped in a tcp/ip message let's say

we have a trigger that we have to

deliver this an alarm takes place and we

have to deliver this alarm from one

device to the other so this trigger

would be then would start the

application layer that would generate

the MMS

message and once the MMS message is

ready it will be enveloped or embedded

into a tcp/ip message and then the

tcp/ip message would be transmitted on

the wire like we've shown you earlier

using whatever physical encoding

required and then at the other end it

will be that physical encoding will be

decoded and the tcp/ip layer would check

the message for integrity once that

message is found to be a good message it

would be transmitted to the next layer

which is the MMS message the MMS

application layer

that would translate this message and

then would apply the appropriate action

based on the message received this would

achieve basically major efficiency every

layer so the MMS application would be

very efficient and object oriented and

allow for a lot of features and instead

of combining all the layers into a

single application and then the

application would become overwhelmed and

less would have less features like if it

was a single application handling tcp/ip

and MMS and all layer then it will be it

will be more difficult for that

application to handle all of these

aspects so this will give more

granularity fair application in order to

provide rich features in each protocol

layer and then the standard will combine

the best protocols with all the features

in order to provide the end-user with

that with the most efficient set up to

achieve reliable communication in a

substation and efficient communication

in this history

section we're going to discuss three

topics first how did the protocol

development start next the need for

interoperability and finally we're going

to discuss the new system architecture

communication between devices was

created by ie D vendors the vendors were

trying their best to make sure that the

communication protocol will serve the

required functionality between the IEDs

in a very efficient and compact manner

saying that some of the protocols

requirement were less than other

protocol requirements so what I mean by

that is one device requirement may be

just to report digital inputs and no

need for analog input reporting and some

devices would have to report digital

inputs and analog inputs what this

caused is that many different versions

of the same protocols were created and

for example the protocol like Modbus

which was created by a company and and

then was distributed and became widely

adopted because of the simplicity of the

Modbus protocol where it doesn't have

time in it and it's only reporting data

but even as it reports data some devices

follow the if you like the unwritten

rules of the protocol and some devices

created their own flavor or their own

version copy of Modbus and for example

in the d20 device on our remote terminal

unit the 20 device we have about nine

different types of Modbus or ten

different types of Modbus flavors or a

major application because every device

that we have interacted with in the

field might have had its own little

tweak or

change whether it was intentionally done

by the ie D creators and others to

walk-in customers or was unintentionally

done because not foreseeing

the importance of abiding by all the

rules because the device requirements is

way less what it ended up being is

basically a whole big database of

applications that we utilize in our and

protocols that we utilize in our SCADA

implementation in many devices around

the substations and that the diversity

in protocols or these proprietary

protocols have caused major issues for

utilities who are trying to standardize

among these protocols so between the

1920s to the 1980s some protocols that

some proprietary protocols gained a wide

acceptance and was shared between

vendors who are sharing the same project

so utilities around the 1980s

started to request and pteropod ability

among vendors and open protocols started

to appear in the market the open

protocol could be one of two things

either a vendor who has created a good

protocol like DMP was created by GE was

published and then adopted by an

international committee international

standard committee and then it was there

was many laboratories created to provide

certification for anybody claiming that

they talked EMP or it was initially

created by

certification body or a committee that

that made it available in public like

the 6870 - 5 - 101 102 103 and 104 and

then made it available also to

laboratories that would certify the

device talking now seeing that not all

devices requirements is the same so for

example let's say a device is just as

simple relay and does not require all

the functionality that comes in DMP so

it doesn't comply to the NP level 3 it

complies to DMV level 1 still talks DMP

but it doesn't talk all the OP code or

functionality that is available in in

the DMP

protocol so that that basically also had

a little bit of variance in the way the

protocol is communicated and configured

which is also a challenge for the end

consumer or the utilities on the

interoperability of devices within the

same within the same open protocol as

such there was a requirement for overall

standardization by the end customer by

the consumer in order to make sure that

these devices can be integrated in

smoother set up in where during a

project implementation so international

standardization body started to form

committees to standardize protocol

implementation in substations new system

architectures governing

ie D communication and a substation and

remote communication started to appear

for example we have the UCA protocol

you see instance for universal

communications architecture which was

the protocol that's a predecessor to the

existing most wide adopted protocol

which is 61 a most widely adopted

standard sorry which is 61 850 standard

that's basically the substation

automation standard and in the 61 850

like I said earlier they adopted the

wiring or what they call as a 60 180 50

stack and this 61 850 stack would define

what's the application layer and what

application would control would define

what application protocol would define

the physical or the session layer so it

basically took the best practices out of

all the older or the available protocols

in the market and standardized what

should be used for relay communication

what should be used for a concentrator

communication and they're trying to

define how the devices should interact

among each other whether these devices

exist in a substation

or one substation to another of one's

position to Control Center in this final

section we're going to discuss the

communication protocol classifications

basically two topics will cover the

types of protocols and the protocol

features and functionalities as another

way of classifying protocols so we can

define the protocols into three families

we've got the clothes the protocols like

Modbus gonna tell LNG 89 79 or an open

protocol family like the MPI EC 68 70 -

5 - 101 1 or 2

or or we can put them in standard like

the UCA standard or the 61 850

regardless of the protocol that we want

to use at the end of the day there is

information that transforming or that is

travelling from one device to another

device and in in this transportation of

information we need a way for one device

to understand the information that's

coming from another device we also have

the other requirements which is ease of

configuration efficiency in

communication and no loss of data so

like I discussed in other modules in in

this substation automation is different

protocols will give you different

features and depending on these features

that will categorize the protocol as

acceptable to the end application the

utility or the user wants to achieve or

it's not networks that are specific to

one manufacturer and which work with

specific hardware connections and

protocols are called closed systems

usually these systems and technologies

are dated and were developed at a time

before standardization or when it was

considered unlikely or not desirable to

have equipment from other manufacturers

included in the network in many of these

dated configurations a single device

acts as a protocol translator that

collects data from different devices in

the field using a variety of protocols

hence the term protocol translator the

purpose of the data collection is to

build up or concentrate the data in one

area for storage monitoring and control

purposes the data concentrator relays

the data back and forth between the

field devices and operator interface and

data storage devices with inherent

delays the term data concentrator refers

to a device that performs this function

open systems are those communication

networks that conform to specifications

and guidelines which are open to all

this allows equipment from any

manufacturer who claims to comply with a

particular standard to be used

interchangeably on this network this

provides the end-users with many choices

of equipment suppliers the network

standard being open will tend to be

updated on a frequent basis to take

advantage of the latest widely available

and cost-effective hardware and software

technologies the optimal configuration

would have all devices directly

connected to the land eliminating the

need for a relaying device such as a

data concentrator and its associated

delays the support of high-speed LAN

interfaces is now more common with the

increase in power of modern

microprocessor based devices one of the

most important features of a

communication system is the need for a

common set of rules in order for both

the receiver and transmitter to

understand each other this is referred

to as the need for compatibility there

are three issues associated with

compatibility the first issue is the

pure physical connection standard the

second is the existence of complimentary

software standards at the transmitter

and receiver which are used in

conjunction with the physical standards

to make a complete communication system

the third issue is the conformability of

the physical connection and software to

the open system interconnect model or

OSI model there are seven worldwide

organizations which are involved in

drawing up standards or recommendations

affecting data communications when one

of these organizations creates a new

standard the name of this organization

appears as part of the name of the new

standard

faced with the proliferation of closed

network systems in 1978 the

international standards organization

defined a reference model for

communication between open systems which

is called the open system

interconnection model this model is

composed of seven layers each layer has

a defined purpose and interfaces with

the layer above and below it let's take

a look at the role of each layer the

physical layer includes elements

involved with the actual transmission

and reception of signals such as

physical connections between the device

and the network network topology

electrical aspects of signaling voltages

and currents for example which voltage

levels are considered a logic one and

logic zero in addition to how much

current the transmitter must be capable

of supplying signal modulation technique

for example is it a simple on-off

technique or FM or AM etc mechanical

aspects such as the connectors and

physical medium to be used in utility

and industrial power system applications

the most commonly used physical layer

standards are rs-232 rs-422 rs-485 10

100 base T and 10 100 base F Ethernet we

will learn about these standards in

depth in the following sections of this

course the data link layer provides the

services that allow communication

between devices this includes framing or

separation of messages error detection

and correction mechanism and an

addressing mechanism while the data link

is concerned with a direct exchange of

frames among devices on a single

communications channel the network layer

is responsible for device to device data

delivery and optimal routing across

multiple data links these underlying

layers might result in packets that are

delivered out of sequence missing

corrupted or delayed due to lower layer

communication issues to address this the

transport layer provides a guaranteed

delivery messaging service that ensures

the data is error-free and correctly

sequenced allowing process to process

communications between devices across a

network or multiple networks the session

layer provides a mechanism for the

establishment of a communication session

between applications running within the

devices while the presentation layer

ensures the correct translation of data

the application layer provides the

facilities or interface to allow the

applications protocols or drivers such

as Modbus or DNP to use the network in

other words in order to look at the

capability of a protocol there is many

I'll give some examples of these

capabilities for example can the

protocol support serial or it will

support network or maybe it will support

both serial and network can if the

protocol supports network is it only

local capability I mean is it close to

the substation or close to one network

or can it talk on a broadcast network or

can it talk outside of the substation on

an Internet communication what does that

entail when it comes to security and

firewalls and gateways and what kind of

gateways is required that would be a

feature of the protocol the some of the

most important evaluation when we look

at the protocol is can the protocol

transmit time and what is the precision

of time that is used is it every second

every millisecond and the other thing is

that the protocol half-a-year or doesn't

have the year specified in every message

that that would impact the efficiency of

the protocol so if you say well I would

like to see the year and decade that

will make the protocol and each message

of the protocol bigger so you might lose

efficiency part will include will

improve the precision at the same time

if if we don't include the time then the

messages will will be very very compact

and it will be left up to the devices to

decide on the sequence of events of

these messages and how to load these

messages and the time for this message

so all depends on the philosophy that we

would like to implement

when it comes to time what kind of data

does the protocol support and is is it

required for our implementation maybe it

only supports digital analog or does it

have counters or it doesn't have

counters including data and what percent

of the earth there is it a 12 bit

extreme bit 64-bit and will that serve

our need for that for the implementation

of that protocol or standard in the

substation can the protocol report

interchanges interstates for example

let's say we've set up this protocol or

the the polling in our substation to

happen every two seconds and we there is

an inter inter changes that took place

between the polling so does the protocol

has the capability to report these

interchanges let's say at the first

point the data was that digital input

was 0 and then and then it changed to 1

and then it changed to 0 before the

second column came

well the protocol report that interstate

of 1 took place intermittently between

the polling is that important to us in

some of the modules I explained

debouncing and all of that so maybe it's

best to ignore these interim States or

it's important that we know about these

interim States because that might flare

something and last but not least of

course is two things security and

redundancy so do we need does the

protocol support if there is a firewall

maybe once we put a firewall in our

network that protocol will no more be

communicated or that message doesn't go

beyond a gateway does that protocol

support the redundancy can it be

communicated via two passes to the other

side

all of these are features of protocols

and features of standards that will play

a very important role on whether we

adopt

these protocols whether we implement

these protocols in the industry there is

many philosophies when it comes to which

protocol will stay which Pro will

disappear over time there is a

philosophy that say that serial

protocols will be around for decades to

come because of the number of devices

that exist in our substations with

serial with serial communication ability

and there is for those of his that say

that serial communication will disappear

and there will be only one standard in

the world of SCADA hopefully that that

will happen one day where we have only

one standard governing our electrical

systems until that time I hope you have

a good overview of the diversity of

protocols in our SCADA system and what

is protocol and we'll see you in future

modules

English (auto-generated)