Communication in Substations:

IEC61850

By: Sudhakar RAMPURKAR/ Manuj SAXENA

Control System Support
Engineering and Project Excellence

(06th Oct-11)

GRID

Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

 Present Situation of communication
protocols for Substations
There are over 50 protocols worldwide for substation automation.

IEC 60870-5-… had gained acceptance in 2004

Corporate
Network TCP/IP
Control Center

IEC 60870-5-104

IEC 60870-5-101

Still used

Legacy bus
IEC 60870-5-103
FO in start configuration
IEC 60870-5-103 Profibus FMS
RS485-Bus
Lon-Bus
….

...
Substation
 IEC 61850 – Present areas of application

Gas insulated substations

Gasisolierte Schaltanlagen
HoHighly
ch In tintegrated
egriert e
SchSubstation
alt an lag eHIS
HIS® ®

IEC 61850

Air insulatedSchaltanlagen
Luftisolierte substations Medium-voltage substations

IEC 61850 - in brief

• Not just another bus system…

• Goes far beyond almost all other communication standards
• It extends the way automation devices “work together”
• Defines WHAT to communicate and HOW to communicate
• Everything has a name
• Configuration language for devices and substations
 IEC61850 Key Benefits (1)

• Speed: 100 Mbps instead of few 10 kbps

Ř More data for a better operation & maintenance
• Peer-to-peer: No extra hardware
Ř Design of innovative automation schemes, late tuning
• Conditional report instead of polling
Ř Optimal performances
• IP (Internet Protocol) routing: Universal data access
Ř Capability to extend the system outside of the substation
• Client-server: Instead of master-slave
Ř Flexible designs easy to upgrade
• Pre-defined names: Single vocabulary between users
Ř Easier engineering between teams
• XML references: Formal interfaces
Ř Consistency between engineering tools

A true step forward..

IEC61850 Key Benefits (2)

• IEC 61850 is independent of short term benefits: focuses on the

“long living application objects”
• Independent of current product; stable over several product cycles
(long term stability)
• Independent of operating systems and programming languages
• Independent of middleware (firmware/ Hardware…)
• Independent of communication medias
• Independent of vendor (multi-vendor support)
Ř Manufacturer-independent exchange of configuration data
Ř Shorter Project Execution Time and more efficient Maintenance
 IEC61850 Key Benefits (3)

• Interoperability – without Gateway

• Ethernet
• Simpler Cabling in comparison with Hard-wiring
• Highly forward and backward compatible – 100Mbit/s of today
compatible with 10Gbit/s of the future
• Common Communication structure in enterprise – unified data flow
• TCP/IP – easy Access to public and private data networks
• Neither Station bus nor Process bus is defined – permitting
Optimisation of Costs and Performance of the System

IEC 61850 – Benefit of the User

Time savings in projects, operations and

maintenance of substations

Cost savings through the use of Ethernet

Internationally valid and checked interoperability

leading to smooth system interfacing
 IEC 61850 –Now being used worldwide

IEC 61850 specification has been

approved as international Standard

Tools for Analysis and

Tests are available

Interoperability Tests
were successfully carried out

Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

 IEC 61850 - Scope

IF10: control-data IF7: data exchange between

exchange between substation (level) and a
substation (devices) and remote engineer’s workplace
a remote control center

IF6: control-data exchange IF1: Protection-data exchange

between bay and station between bay and station level
level

IF3: data exchange

within bay level

IF2: protection-data exchange

between bay level and remote
protection

IF4: CT and VT instantaneous data

IF5: control-data exchange between
exchange (especially samples) between
process and bay level
process and bay level

IEC 61850 Standard

• Uses the strengths of the OSI 7 layer communication model

• Station bus
Ř Communication between IED and master stations
Ř Data polled by Master from IED (Buffered or un-buffered)
Ř Inter-IED data exchange through multi-cast GOOSE messages
• Process bus
Ř Communication between plant equipment and IEDs (switchgear,
Instrument transformers)
Ř Exchange of sampled values
• Bus separation is becoming less distinct

Standardized data models for all applications

 Station Bus

Communication within and between Unit and Station levels

Station bus

• Main Backbone linking IEDs to Controllers

• Protocol uses Manufacturing Message Specification (MMS)
• Most IEC61850 functionality mapped to MMS
Ř Controls
Ř Reports
Ř Get data
Ř Settings
Ř File Transfers
 Process Bus

Communication within and between Process and Unit levels

Process bus

• Data Exchange at process level

• Protocol uses Manufacturing Messaging System (MMS)
• IEC61850 functions applied
Ř GOOSE
Ř Sampled Values
 IEC 61850 – “Communication networks and systems
in substations”

• Fully supports all substation automation functions comprising

control, protection and monitoring

• A global standard and the key to interoperable Solutions

• Future-proof Architecture, easy Extension and safeguarding

Investments

• Optimisation of system architectures possible (scalable

technology)

• Provides engineering and maintenance support by means of

the substation configuration language based on XML

• Uses readily available industrial Ethernet and communication

components

IEC61850 System devices

• Merging Units
• Binary Interface Units
• Integrated Field Units
• Intelligent Multifunction Devices
• Communication Devices
• Computers for Substation Integration
• Real Time Computers
 Sub-station Automation Functions

• Protection
• Automation
• Control
• Measurements
• Metering
• Recording
• Analysis
• Alarm & Time stamping

IEC 61850: Services

• Control
• Reports (Buffered / Un-buffered)
• Logging
• GOOSE (fast inter-device communication)
• Setting Group
• Sampled Value
• Time Synchronisation
• File Transfer
 IEC61850 functionalities for Micom products

Master Slave Connection model

• In a Master-Slave relation only one master is acting at a

time
• The master polls the various slaves, then distributes the
information to the applications
• In redundant systems, If the Primary Master fails then a
Secondary master may be used
• Popular in legacy serial protocols
 Client Server Connection model

In a client-server model, each application (client) can

request (in parallel) what it exactly needs from each server
Ř Clients are typically HMIs and Gateways; servers are typically
bay controllers, protection, measurement centers
Ř Applications do not go through a central point therefore they
get the information in a faster and more reliable way
Ř Failure of a client does not affect the other clients
Ř A new client might be added without changing the existing
communications

Reporting Vs Polling

• Reports transmit data based on a condition being met

Ex: Change of state
• Reports are more efficient than polling
Ř Data are transmitted ONLY when there is a need to transmit them,
therefore reducing network and application load
Ř Polling cycle might be too long compared to the application dynamics
and loses events
• Reporting is fully compatible with client-server mode
• It can be emulated on master-slave mode but less efficiently
 Does IEC 61850 standardise a station
or process bus?

• IEC 61850 defines neither a station bus nor a process bus

• IEC 61850 defines no communication network architecture
• IEC 61850 provides solutions for different communication
requirements independent of a station or process bus
• IEC 61850 defines Ethernet for all levels

Free Configuration of communication (1)

Hardwired & point to point links

Point to Point

Hardwired
 Free Configuration of communication (2)

Separate Station and Process bus networks

Station bus

Process bus

Free Configuration of communication (3)

Single substation bus network

Single bus
 Free Configuration of IED functions (1)

Combined protection and control unit

Free Configuration of IED functions(2)

Separate protection, Smart switchgear

 IEC 61850 Standard - Organization

What does IEC 61850 achieve?

Defines structure
for protection and
System control
configuration Communication
between
bay devices

Standardised
language for
describing
substation
IEC 61850 Fault records
in Comtrade
format

Standard
communication Time
with TCP - IP synchronisation
Based on with SNTP
Ethernet
standard
 Substation Communications
Architecture

Substation HMI Substation Computer SCADA Master

Router WAN

Switch Switch

IED IED IED IED IED IED IED

System Communications
Architecture
Traders Analysts
EMS
EMS

SCADA Server Substation j

ISD

Substation WAN
Gateway
Substation i
Substation 1
Switch

Substation 2
IED
IED

IED IED
 New Architecture creates Advantages
Distributed Intelligence
No more classical Master/ Slave configuration and bottlenecks

Engineering HMI
Browser
Station Unit SCADA – WAN

Station bus
Ethernet IEC61850

independent communication

Process

Client / Server Architecture with Distributed Intelligence

IEC 61850 –Station bus Layout

Corporate
Network TCP/IP
Control Center

IEC T101 IEC T104

Router
IEC61850 Station Bus

Serial Hub
103 over
Ethernet IEC 61850 (Ethernet)
Protection - Control

IEC 60870-5-103
for Protection
 Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

Communication in Substations

• Centralized monitoring and control

• With IEDs, substation automation has become Popular and easy to install
• Reduced hardwiring – saving time and effort on commissioning and
maintenance
 Communication in Substations

SUBSTATION COMMUNICATION

Physical link Protocol

RS232 - copper Courier

Proprietary
RS485 - copper SPA

Ethernet - copper Profibus . . .

Ethernet – optic MODBUS

DNP3 Open

IEC 60870

7 Layer Open Systems Interconnection model

Protocol services for Applications

Application Selection
What toofgotype
? of dialog 7
Identification and Authorisation
Representation of data Application FTP/ SNMP/
Presentation Definition of coding type
issues 6 SNTP/ Telnet
Definition of used characters

Dialog control
Session Synchronisation of session connection 5
Sequencing of application data
Transport How toofgo
Control ? end of transmission
start/ 4 TCP/ UDP
Error detection and clearing
Routing, Prioritisation
Network Setup/ Release
Where to goof? connections
Data
3 IP
Flow control
Transport
Framing
issues
Data Link Sequence control 2
Flow control
Ethernet
Bit transmission
Physical Coding 1
Synchronisation
 Parallel running communication services
at the Ethernet port
Parallel running services: Port B

IEC 61850
Info – Report
Optical module

IEC 61850
Goose 1)
Data- Electrical Ethernet module
highway:
IEC 61850 100 MBit/s
timesync.(SNTP2)
Ethernet

Micom S1

Web - Monitor Port B

1) Generic Object Oriented Substation Event

2) Simple Network Time Protocol

Ethernet: A Data Highway for everything

Transmission system

100 Mbit/s
Ethernet

• Bay devices to station controller

• Inter-device communication
• Remote setting of parameters

One communication technology in the substation

 Protocol stack of IEC 61850

Assignment of Functions, Services and Protocols

Example Fault messages Interlocking Measurement

Objects Time
Client-Server GSSE GOOSE Sampled Values
(Part 7) Sync

Mapping 8-1
8-1 9-2 9-1 8-1
Layer 7 MMS

Layer 6 ASN.1/BER (ISO 8824/5) SNTP

Layer 4 TCP ISO 8326 UDP

Layer 3 IP LLC IP

Layer 1 and 2 Ethernet 10/100 MBit/s FO or TP

Comparison of protocols/standards
IEC IEC
60870- 60870- Profibus DNP Modbus LON IEC 61850
5-104 5-103
Control Centre Yes
Level
Yes -- -- Yes -- -- (future)

Station Level No Yes Yes Yes Yes Yes Yes

Bay Level No Yes Yes Yes Yes Yes Yes

Process Level No No Yes No Yes Yes Yes

Engg. Data
Exchange
No No Partially No No No Yes

Global approach Partially Partially Partially Partially Partially Partially Yes

Comm. speed 100M 19.2k 12M 19.2k 19.2k 78k 100M

 Network Terminology

Network : An interconnected group of nodes or stations linked by

communication channels
Node : The interface point where one or more functional units
are connected
LAN : Local area network (<5km)
WAN : Wide area network
IP : Internet Protocol

Ethernet Switch features

• Substation environment !
Ř Electro-magnetic compatibility
Ř DC power supply with 20ms voltage dips, possibly
redundant
• Priority and VLAN (802.1q):
Ř Virtual LANS
• Management
Ř Capability to detect a switch failure: SNMP or watch-dog
• Redundancy management
Ř No standard today for hard real time redundancy
Ř Redundancy between switches (not applications)
 Star architecture

Double Star architecture

 Ring architecture

Network components
Industrial substation hardened switch

• Fulfill the EMC - requirement (ANSI, IEC, IEC61850 Part 3)

• Supports priority tagging of Goose - messages
 Network components –
Media converter

10 MBit/s or Optical
Ethernet
100 MBit/s Electrical
Ethernet

Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

 Interoperability

Ability of two or more IEDs from the same/ different vendors, for
information exchange and usage of specified functions

Has a DATA
MODEL that can
be accessed

Request

IED : WHAT to exchange

(IEC 61850-7-3 &4)
Response Intelligent
Electronic
Event Device

HOW to exchange
(IEC 61850-7-2)

IEC 61850: Interoperability….1

What is needed for interoperability

Common standardised:
• Language (data model)
• Services (service model)
• Protocol
• Communication medium
• Engineering data exchange
• Conformance test

IEC 61850 standardised these needs

 IEC 61850: Interoperability…2

• IEC 61850 does not automatically ensure interoperability

• To reach interoperability a well-done engineering is necessary
as per :
– IEC 61850-4 System and project management
Clause Engineering Requirements
– IEC 61850-6 Configuration description language for
communication
• Conformance Testing will be an important part to provide
interoperability
– IEC 61850-10 specifies the conformance testing

Documents needed for Interoperability

Protocol Implementation Conformance Statement (PICS)

Summary of the communication capabilities of the system or device
Protocol Implementation eXtra Information for Testing (PIXIT)
Communication capabilities of the system or device which are outside
the scope of the IEC 61850. The PIXIT not part of standardization.
Model Implementation Conformance Statement (MICS)
Details out Data object model elements supported by the system or
device
Tissue Implementation Conformance Statement (TICS)
Details out Technical Issues for IEC61850 implementation
 Sample KEMA certificates

P634 C264P

Acrobat Document Acrobat Document

Inter-operability Demo Set-up

Substation Substation Substation

Controller Controller Controller
Ethernet
Switch IEC 61850-8-1
(MMS, GOOSE)
Main X Main Z Bay
Main Y
Protection Protection Controller
Protection

IEC 61850-9-2/8-1
IEC 61850-9-2 (GOOSE, SAV, MMS)
(SAV)
IEC 61850-9-2 IEC 61850-9-2
(SAV) Merging (SAV) Merging
Unit Unit
3rd Fibre
Alstom
Sensor Trips
IEC 61850-8-1
(GOOSE)
Trip
 Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

Virtualization
 Data Communication using IEC 61850

Logical groupings – Devices, nodes, classes and data.

Logical grouping
Logical Groupings – 13 different groups for 92 nodes
MMXU Measuring (Measurand unit)
Group Logical Node Groups LNs defined
MMTR Metering
Indicator MSQI Sequence and Imbalance
A Automatic Control 4 MHAI Harmonics and Inter-harmonics
MDIF Differential Measurements
C Supervisory control 5
G Generic Function References 3 PSCH Protection Scheme
PTEF Transient Earth Fault
I Interfacing and Archiving 4 PZSU Zero speed or underspeed
L System Logical Nodes 3 PDIS Distance protection
…more
M Metering and Measurement 8
P Protection Functions 28
SIMG Insulation medium meas unit
R Protection Related Functions 10 SARC Monitoring and diagnostics for arcs
Sa) Sensors, Monitoring 4 SPDC Monitoring and diagnostics for
a)
partial discharge
T Instrument Transformer 2
Xa) Switchgear 2
a)
Y Power Transformer and Related 4 XCBR Circuit Breaker
Functions XSWI Circuit Switch
Za) Further (power system) 15
Equipment
 Data Classes

355 Data classes

Example of Data Classes

Data classes and example

 Mapping Example

Single Line Diagram Physical Device Bay Controller

GGIO GAPC limit

overflow
General Input / Output Automatic Process
Control

XCBR XARC added switch

current
Circuit Breaker Monitoring for Arcs

RFLO distance
Fault Locator

ICIRC TCTR PDIS reactance

Current Transformer Distance Protection

RDRE instantaneous
TVTR (record)
Disturbance Recorder
Voltage Transformer
MMXU RMS
demand
Measurement Unit
ATCC circulating
current
Tap Changer Controller

Example for some current related information

Modelling Principles

• Model is a Logical representation

• Identifies the various elements in the system
Ř Protection, Control, Reporting
• Provides a common ‘view’ of a system
Ř Across different products (Px30, Px40)
Ř Across different suppliers (Areva, Siemens, ABB)
 Modelling Example

Example: Bay unit with Time Over Current Logical

Protection, Control, Automation, Recloser Device

IED1 Time Over

Current
PTOC
Auto Reclosing
RREC
Switch Control
CSWI
Measurement
MMXU Unit
Logical
Device Logical
IED1 Device
IED3 IED2
Circuit
TCTR XCBR Breaker

Current Transducer
IED - Intelligent Electronic Device (each
device with a communication interface)

IEC 61850: Modelling Example

Device 1 Bay device Device1/Q0CSWI.Pos

+ PTOC
+ RREC
- Q0CSWI
+ Mode Mode
+ Beh Behavior
+ Health Health
+ NamePlt Name plate
+ Loc Local operation
+ OperCnt Operation counter
+ Pos Switch position general
+ PosA Switch Position Phase A
+ PosB Switch Position Phase B
+ PosC Switch Position Phase C
+ OpOpn Operation “open switch”
+ OpCls Operation “close switch”
+
+
 IEC 61850: Modelling Example

Device 1 Bay Device Device1/Q0CSWI.Pos.stVAL

+ PTOC
+ RREC
- Q0CSWI
+ Mode Mode
+ Beh Behavior
+ Health Health
+ NamePlt Name plate
+ Loc Local operation
+ OperCnt Operation counter
+ Pos Switch position general
ctlVal
stVal intermediate-state (0)
pulseConfig off (1)
operTim on (2)
q bad-state (3)
…more

IEC 61850-7: Addressing “Switching Circuit Breaker”

BUK01/Q0CSWI1.Pos.ctlVal

Attribute Name (fixed)

Data Object Name (fixed)
Logical Node Name Suffix (free)
Logical Node Class (fixed)
Logical Node Name Prefix (free)
Logical Device Name (free)
 Example: Control Circuit Breaker and Report Position

Bay Device “Bay A”

Station Controller Circuit Breaker
Client Server Client Server
SelectRequest (on)
Check
SelectResponse +

OperateRequest (on)
Check OperateRequest (on) Activate motor
OperateResponse + OperateResponse +

UnbufferReport (between) Position Between

UnbufferReport (on) UnbufferReport (on) Position ON

CommandTermination + Deactivate motor

Communication over Communication e.g. over

Station Bus Process Bus

Addressing Modes

• Unicast communication is between a single sending IED and a single

receiving IED. The Destination Address identifies a unique device that
will receive the Ethernet frame.
• Multicast is the addressing mode in which a given frame is targeted to
a group of logically related IEDs. In this case the Destination Address is
the Multicast Address, also called a "group" address.
• Broadcast is the mode when an IED is sending a frame to all devices
connected to the substation network
 Time Synchronisation

• Time synchronization is essential to any event analysis system

• There are two common ways of synchronizing various devices to the same clock
source:
Ř Synchronization over direct connection
Ř Network synchronization
• Time Synchronization in IEC61850 system uses SNTP (Simple Network Time
Protocol) with ~2ms accuracy
Ř SNTP is in essence a subset of NTP (Network Time Protocol). NTP uses UTC (Universal Time Coordinated) as
reference time.
Ř UTC is an official standard for the current time and evolved from the former GMT (Greenwich Mean Time)

• Px40 supports IRIG-B with Ethernet

Ř Still the most accurate way of time synchronisation
Ř Used as highest priority clock source
• Px30 does not support IRIG-B with Ethernet
Ř Need to use SNTP or other communication port (e.g. 103)

Time Synchronisation Methodology

• 2 SNTP time servers can be specified

• Both equal priority alternatives
• UNICAST mode used by specifying individual IP addresses
• ANYCAST mode used by specifying the broadcast address for the
sub-network
• The first server that responds will be used
 IED 61850 Logical Nodes
Relay Object Models
Physical Device

Logical Device
LD1 LLN0

MMXU1
Ocp Gnd PIOC1
PTOC1
PTOC2
RDIR1

Phs PIOC1
PTOC1
PTOC2
RDIR1

RREC1

IED 61850 Logical Nodes

IED Functional Hierarchy
Physical Device

Logical Device
LD1 LLN0

LPHD

External Functional Ocp Gnd PIOC1 Logical

Group Name Nodes
PTOC1
(Overcurrent
Protection function) PTOC2
RDIR1

Phs PIOC1
Internal Functional
Group Name PTOC1
(Phase Overcurrent PTOC2
Protection sub-function)
RDIR1

RREC1
 Logical Devices

• IED Model contains 1 or more Logical Devices

• LD corresponds to an area of functionality
Ř Over-current Protection
Ř Logging & Recording
• Alstom Grid Relays have up to 5 Logical Devices
Ř System
Ř Control
Ř Measurands
Ř Records
Ř Protection

Logical Device contents

• Logical Devices contain functional elements.

• The functional elements are the smallest parts of a function
that can exchange data.
• These functional elements are called Logical Nodes
Ř Circuit Breaker
Ř Over-Current Stage 1
 Logical Node naming

• Logical Nodes have a 4 character name (Upper Case)

• First character defines its Group
• Other characters relate to its function
• Examples
Ř XCBR; Switchgear, Circuit Breaker
Ř PTOC; Protection, Timed Over-current
Ř GGIO; Generic, General I/O
Ř MMXU; Measurements - 3-phase Amps, Volts, etc.
Ř CSWI; Control, Switch

Mandatory Logical Nodes

• Every LD has two mandatory Logical Nodes

• LLN0 (Logical Node 0)
Ř common data of the LD
• Mode, Behaviour
• LPHD (Physical Device)
Ř common data of the physical device hosting LD
• Name, Health
• Unique Naming
Ř LPHD – no prefix, instance number always 1
Ř LLN0 – no prefix, no instance number
 Data path example

MMXU1.A.phsB.cVal.mag.f
Ř MMXU1: instance of LN class MMXU defined in Part 7-4
Ř A: instantiation of the Composite DATA class WYE (defined in 7-3)
Ř phsB: value of the current in phase B as a Simple Common DATA
class of type CMV (defined in 7-3 )
Ř cVal: is the complex value of the current in phase B (of the Common
DataAttribute type Vector)
Ř mag: this object represents the magnitude of the complex value
(type AnalogValue - defined in 7-3)
Ř f is a DataAttributeComponent which is of the basic type FLOATING
POINT (defined in 7-2)

Common data classes for measurand information

• Measured value (MV)

• Complex measured value (CMV)
• Sampled value (SAV)
• WYE
• Delta (DEL)
• Sequence (SEQ)
• Harmonic value (HMV)
• Harmonic value for WYE (HWYE)
• Harmonic value for Delta (HDEL)
Protection Logical Nodes…1

Protection Logical Nodes…2

 Services

Multifunctional IED Object Model

Server
LN1

LN2
LD1
LN3

LN4

LNn
 Multifunctional IED Object Model

PQM IED
HV LD1 LN(i)

hv MMXU1

MMTR1

MMHI1

MSTA1

mv MMXU2

MMHI2

MSTA2
MV

Multifunctional IED Object Model

BiTRONICS M871 Recorder

LLNO LPHD DIAG1
Controls
HV GCTL1
RWRE1 RDRE1 RDRE2
GIND1
MMXU1 dmd prs MMXU1
MMTR1 MMXU2
RSYN1 MHAI1 AMXU1
RSYN2 MSQI1 min MMXU1
RSYN3 RATO1
MMXU2
MMXU2 max MMXU1
MMHI2
MMXU2
MSQI2
MMXU3 AMXU1
MV RATO2
RATO3
 Gateway Object Model

Gateway: Physical Device PD0

Logical Device LD0
GLOBE
Legacy Device PD1
Multiple
Bricks Logical Device LD1
GLOBE
Logical Device LD1
GLOBE Multiple
Bricks
Multiple
Bricks
Legacy Device PD2
Logical Device LD2 Logical Device LD2
GLOBE GLOBE
Multiple Multiple
Bricks Bricks

Gateway Object Model

Gateway: Physical Device PD0

GOOSE Out Logical Device LD0

GOOSE0
GOOSE In

GOOSE Out Logical Device LD1 Status Legacy Device

GOOSE1 PD1
GOOSE In Control

GOOSE Out Logical Device LD2 Status Legacy Device

GOOSE2 PD2
GOOSE In Control

LAN
 Alstom Grid Wrapper Table

Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

 Generic Substation events

Generic substation Events (GSE) is a control model, which provides a fast and reliable mechanism of
transferring event data. This provides facility to transfer the same event message to multiple physical
devices using multicast / broadcast services. GSE control model is further subdivided into GOOSE and
GSSE.

Generic Object Oriented Substation Events (GOOSE) :

Generic Object Oriented Substation Events (GOOSE) is a control model mechanism in which any
format of data (status or analog ) can be grouped into data set and transmitted within a time period of
4 milliseconds.

Generic Substation State Events (GSSE) used in UCA2:

In GSSE, only Status data can be exchanged and it uses a status list (string of bits) rather than dataset
used in GOOSE.

GSSE message is transmitted over MMS based stack (base stack without using TCP/IP) which
necessitates more time for transmission & processing in comparison with GOOSE messages

GSE messages

• The Generic Substation Event (GSE) model provides the

possibility for a fast and reliable system-wide distribution of
input and output data values.
• The GSE model is based on the concept of an autonomous
decentralization, providing an efficient method allowing the
simultaneous delivery of the same generic substation event
information to more than one physical device through the use of
multicast/ broadcast services
 GSE messages

• Two services for peer-peer event messaging:

Ř GSSE (same as UCA2 GOOSE)
• Binary bit-pairs (State change information)
Ř GOOSE
• Any data object / data attribute contained in a Data Set
• GSSE is being depreciated from the standard
• GSSE Not generally supported in MiCOM relays
Ř Included in Px30 phase 1
Ř Mx70 include it for distributed disturbance recorder triggering
schemes only

GOOSE messages

• The GOOSE messages contain information that allow the receiving device
to know that a status has changed and the time of the last status
change.
• The time of the last status change allows a receiving device to set local
timers relating to a given event.
• A newly activated device, upon power-up or reinstatement to service,
shall send current data (status) or values as the initial GOOSE message.
• All devices sending GOOSE messages shall continue to send the message
with a long cycle time, even if no status/ value change has occurred.
• This ensures that devices that have been activated recently will know the
current status values of their peer devices.
 GOOSE Application & advantages

• Used in Horizontal communication

O
• Used for Data Access & Fast transfer of inputs/ outputs between
IEDs
• Used in Interlocking & Tripping
• Cost effective solution for Interlocking with saving in Hardwired
cable costs
• GOOSE report enables High speed trip signals with high
probability of delivery

Peer to Peer Messaging Connection model

• This service is normally used for distributed automation

Ř e.g. Interlocking, Inter-tripping, Voltage regulation, Load Shedding, etc.
• Requirements:
Ř The data produced (“published”) by one IED might be used (“subscribed”)
by one or more IEDs
Ř The publishing IED might be any IED thus peer-to-peer exchanges shall be
possible
Ř Real time constraints are in the range of ms (“4 ms” for an intelligent
circuit breaker)
Ř The failure and restart of one IED (whether publisher or subscriber) must
be tolerated
 The idea behind IEC 61850: Publisher/ Subscriber

Someone posting a message on a bulletin board

corresponds to the publisher. Someone reading
the bulletin board corresponds to a subscriber.

GOOSE Publishing & Subscription

• GOOSE Publishing
Ř Data sets should be located in the same Logical Node as the GOOSE
control block that uses them
Ř Preferred to map the lowest data attribute in the model rather than
data objects (for ease of subscription & message size)
Ř Any data attribute from the entire data model can be published in any
data set.
• GOOSE Subscription (unchanged)
Ř Only certain data attribute types can be subscribed to
• Only SPS & DPS data object types can be mapped.
 GOOSE messages

GOOSE Performance requirements

• There are two independent groups of performance classes:

Ř for control and protection
Ř for metering and power quality applications
• Since the performance classes are defined according to the
required functionality, they are independent from the size of the
substation
• The requirements for control and protection are higher, because
of the effect of the fault clearing time on the stability of the
system or on sensitive loads
 Performance requirements

IEC 61850 defines three Performance Classes :

Ř P1 : applies typically to the distribution level of the substation
or in cases where lower performance requirements can be
accepted.
Ř P2 : applies typically to the transmission level or if not
otherwise specified by the user.
Ř P3 : applies typically to a transmission level applications with
high requirements, such as bus protection.

GOOSE Transmission Principle

A GOOSE message is:

Ř Multicasted
• All IED belonging to the multicast address will decode the message
simultaneously
• Decoding is by hardware, multicast address is by system configuration
Ř Repeated in order to cope with
• A temporary failure of an IED (example: queue overflow) or of the
communication (example: re-configuration after a failure)
• The restart of a subscribing IED so that it can re-initialize its automation
sequence
• However there is no guarantee that the message has been received
Ř Prioritized:
• This is used by the switches (IEEE 801.2Q) and by the application
 GOOSE: Receiver side

• The receiver will normally execute a logic combination or

sequence upon the GOOSE reception
• The receiver will receive the repetitions of GOOSE and possibly
ignore them in its application processing (depending on internal
implementation)
Ř However this is consuming some processing capacities
Ř MiCOM devices only process the message if a change is detected.

GOOSE Message
 IEC 61850 – GOOSE Principle

A device sends information by Multicasting.

Only devices which are subscribers receive and Process this message.
In the example, Receiver Z receives the message. Receiver Y is not a
subscriber.
EXAMPLE: GOOSE
Receiver
Device Y
GOOSE

Ethernet
Sender

GOOSE message
Device X

GOOSE
Receiver
Device Z
GOOSE (Generic
Object Oriented
Substation Event)

IEC 61850 – GOOSE Principle

Priority Tagging of GOOSE Telegrams Ethernet-Switch

Overtake lane for IEC GOOSE

fast

GOOSE

Normal Telegrams

Buffer for normal telegrams

 GOOSE Implementation in Micom

• GOOSE Control blocks are attached to LN0

• Implementation on IEC GOOSE:
Ř Px40
• 32 Virtual GOOSE outputs are transmitted as BOOLEANS
• Each has a quality bit (Good/ Bad).
• No individual timestamp
• 32 Virtual GOOSE inputs can be received from up to 32 clients
• Inputs must be mappable onto DDB signals
Ř Px30
• 32 Single Status Points (SPS) data objects (StVal, q, t)
• DPS data objects for control IEDs
• Timestamps are included.
• 32 Virtual GOOSE inputs accept CDCs or Data Attributes

GOOSE Transfer time

Performance example (ms)

Goose applications:
Adaptive Load Shedding
 Goose applications:
Bus Protection (Line Fault)

Goose applications:
Bus Protection (Bus Fault)
 Goose applications:
Breaker Failure Protection

Goose Demonstration :
Demo setup
Test Equipment
Analog inputs

Relay Relay

Ethernet Network

Network Analyzer Switchgear Simulator

 Case 1: Trip and auto-reclosing

OMICRON Test
Equipment
Analog inputs

1. Simulated fault
SIEMENS Relay Areva Relay
2. Trip generated

Ethernet Network

Goose Message:
Simulation Trip
software

Case 1: Trip and auto-reclosing

OMICRON Test
Equipment
Analog inputs

1. Simulated fault
SIEMENS Relay Areva Relay
2. Trip generated
3. New position

Ethernet Network

Simulation Goose Message:

software Positions
 Case 1: Trip and auto-reclosing

OMICRON Test
Equipment
Analog inputs

1. Simulated fault
SIEMENS Relay Areva Relay
2. Trip generated
3. New position
4. Reclose command

Ethernet Network

Goose Message:
Simulation Reclose
software

Case 1: Trip and auto-reclosing

OMICRON Test
Equipment
Analog inputs

1. Simulated fault
SIEMENS Relay Areva Relay
2. Trip generated
3. New position
4. Reclose command
5. New position

Ethernet Network

Goose Message:
Simulation Positions
software
 Case 3: switch position change

OMICRON Test
Equipment

SIEMENS Relay Areva Relay

1. Position change
2. New position

Local Ethernet Network

entry of
new
Goose Message:
position Positions
Simulation
software

Example on IEC 61850–GOOSE

Config Server PC
tool
Central device with
time synchronisation optical
OSM-
62,5Ŧ or 50Ŧ optical fibre switch electrical

OC-Feed4
OC-
OC-Feed2
ANSI IEC61850
50-
50-1 picked up
–F2 >Block 50-2 OC-
OC-Feed3 station
IEC 50-
50-1 picked up
OC-
OC-Feed1 >I>> Block - F3
50-
50-1 picked up
- F1

OC-Feed2 ANSI
50-
50-1 picked up
IEC
OC-Feed4 OC-Feed3 I> picked up
OC-Feed1
Incoming feeder Outgoing feeder
Outgoing feeders
 Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

SCL, the IEC 61850 description language

The key to a manufacturer-independent exchange of planning

data is a standardized description language. This is why SCL, or
Substation Automation Configuration Description Language has
been developed.
 Substation Configuration Description Language

Types of SCL Files

1.IED Capability Description (.ICD) File –This file needs to be supplied by each manufacturer to
make the complete system configuration. The file contains a single IED section, an optional
communication section and an optional substation part which denotes the physical entities
corresponding to the IED.

2.System Specification Description (.SSD) File – This file contains complete specification of a
substation automation system including single line diagram for the substation and it’s functionalities
(logical nodes). This will have Substation part, Data type templates and logical node type definitions
but need not have IED section.

3.Substation Configuration Description (.SCD) File –It contains substation, communication, IED
and Data type template sections. An .SSD file and different .ICD files contribute in making an SCD
file.

4.Configured IED Description (.CID) File – It is a file used to have communication between an IED
configuration tool to an IED. It can be considered as an SCD file stripped down to what the
concerned IED need to know and contains a mandatory communication section of the addressed IED

SCL files: ICD and SCD

• SCL enables you to write all the relevant information into a text
file, according to a standardized, XML-based structure.
• Each IEC 61850-compliant device must provide such a file, known
as the device description (ICD). It defines the configuration, as well
as the functions and communication abilities of the device.
• Likewise, the station description contains information on the
station’s network structure and internal communication as well as
on the allocation of the devices to the primary technology (SCD).
 System Configuration

• Substation Configuration description Language (SCL)

• Formal description of the
• Single-line diagram
• Substation automation functionality
• IED capability and configuration
• Communication network
• Binding information (e.g. trip matrix)
• Only IEC 61850 offers SCL

SCL overview

Formal configuration description language

Ř Based on modern internet technologies
Ř A set of standardized files that can be exchanged between
tools
 IED Engineering

ICD-File

IED Configuration Tool

Format: XML
Library

• The IED capability description file (.icd) describes the capabilities

and (optional) the preconfigured data model of the IED
Ř logical devices, logical nodes, logical node types
Ř data sets
Ř control blocks
• The .icd file may be created by an IED configuration tool or exist in
a library from the IED vendor

ICD: Map IEDs to logical devices

 Substation Modeling

SSD-File
System
Specification Tool

Format: XML
Library

• The system specification description file (.ssd) describes the single

line diagram of the substation with the associated logical nodes
Ř single line diagram
Ř logical nodes, logical node types
• The .ssd file is created with a system specification tool or may be
existing in a library of the utility

SSD: One Line diagram and functions

 Substation Engineering

SSD-File

SCD-File

ICD-File
ICD-File
ICD-File
ICD-File

System Configuration Tool

• The substation configuration description file (.scd) describes the

complete substation configuration
Ř single line diagram
Ř communication network
Ř IED configurations
Ř binding information (e.g. trip matrix)

IED configuration

SCD-File CID
File

IED Configuration Tool

• The configured IED description file (.cid) describes a instantiated IED

with all configuration parameters relevant for that IED
• It is created by the IED configuration tool from the .scd file and
includes the device specific configuration data
• The use of the .cid file to configure the IED is optional. As an
alternate solution, a vendor specific file may be used
 Complete engineering process IEC 61850

ICD-File
Library ICD- device Library

File of other SSD-

vendor File System Specification Tool
IED Configuration Tool

ICD - IED capability...

SCD – substation configuration… System

Configuration Tool
SSD - system specification…

CID - configured IED description SCD-

File
CID-File
(optional)
IED Configuration
Tool parame-
ter file

Substation Configuration Language

Bay A Bay B
Before Configuration

Q1

New IED
Address of
Receiver

Data name: XCBR.Pos.stVal ? Get ?

IED Address: 12345
Service: Report, GOOSE, …
Address of
After Configuration

Receiver
New IED
12345 Get BayA/Q1XCBR.Pos.stVal

Data name: BayA/Q1XCBR.Pos.stVal

IED Address: 12345
Service: Report, GOOSE, …
 Self-description

• Engineering starts before the system is physically available

• IEDs are adaptable to many different tasks
Ř Not all tasks can run in parallel at the same time.
Ř Capability subsets need to be defined.

• Device capabilities as well as project specific configuration in

general and with respect to the system parameters need to be
available in a standard way before the IED itself is available.

Substation Configuration Language Scheme

 SCL File Elements

• Header : Used to identify version and other basic details of an SCL configuration file
• Substation : substation entities including various devices, interconnections & other functionalities.
The elements include Power Transformers, Voltage Levels, Bays, General Equipments, Conducting
Equipments like breakers, logical nodes etc…
Ř primary apparatus functions used
Ř Connections
• Communication: Communication points for accessing the different IEDs of the complete system
containing different Sub Networks and Access Points.
Ř connections of IEDs to networks and sub-networks
• IED : Contains different access points of the specific IED, the logical devices, and logical nodes,
report control blocks etc
Ř logical devices configured
Ř logical nodes, reports, data logging
• Data Type Templates: Defines logical devices, logical nodes, data

Simplified SCL Object Model

 Expected Engineering process

IED Configurator

• All IEC61850 configuration and settings are done using the IED
configuration
• One tool for Px30, Px40 and eventually Mx70 devices
• Currently there are some differences between the implementations
due to platform limitations
• Phase 2 brings more harmonisation of the approach and
integration of the Mx70 devices
• MiCOM Phase 1 devices have a fixed data model with fixed data
sets and report control blocks
• The following features are configurable:
Ř IED identification & communication address
Ř SNTP time servers
Ř GOOSE interconnections
 Px40 configuration

• Px40 configuration parameters are not available via the front

panel or Courier – they are only visible and settable via the IED
configurator.
• Configuration is transferred as an MCL file using Courier Binary
File Transfer.
• Two Configuration Banks
Ř Active and Inactive banks
Ř compatibility with PACIS
Ř Allows quick re-configuration of the system

Px30 configuration

• In Px30 the configuration parameters are integrated into

S&R103
Ř Edited manually
Ř Launch IED Configurator
• Only 1 set of configuration parameters
Ř Phase 2 will bring 2 configuration banks
 Reporting

• Mechanism for reporting data changes

• Types of Report
Ř Instantaneous – Report generated when the data changes
Ř Delayed – Report generated after expiry of a timer started when
data first changes
• Optional Features
Ř Integrity (Timed) - Regular reporting irrespective of any changes
Ř On Demand (General Interrogation) - Client interrogates server to
get latest report
• Data in report defined by a Data Set (Named Variable List)

Report Contents

• Sequence Number
Ř Increments for each report
• Timestamp
Ř When report was generated
• Inclusion
Ř Mask indicating which elements of dataset have changed
• Data Set Values
 Data Sets

• Collection of data values

Ř e.g. Measurements related to overcurrent
• Basis of data included in Reports and Goose messages
• Phase 1
Ř Data Sets are preset by the modelling tool and are fixed.
Ř Each LN with an ST FC will have a data set called <lnname>$ST
• e.g. XCBR1$ST
Ř Each LN with an MX FX will have a data set called <lnname>$MX
• e.g. FouMMXU1$MX
• Phase 2
Ř Data sets must be constructed in IED Configurator
Ř Can contain any data object or attribute
Ř Can be assigned to any Goose or Report CB
Ř No Data Sets are preset by the modelling tool

Reporting Measured Values

• Measured Values can exhibit small fluctuations

• Capability of generating large number of reports
• Deadbands used to control data change reports
Ř Integer value defining percentage of the difference between
max and min values of measurement
Ř Data must change by the specified difference to generate
report
Ř 1 point = 0.001%
Ř 0 = no deadband so all changes are reported
Ř 100,000 = 100% so no changes reported
Ř Full range is 0 – 100,000
 Reporting Measured Values

• Alstom Grid scheme is slightly different

• No Min/ Max values for measurements
• Instead, dead-band is absolute value changes
• Range is still 0 to 100,000
• 1 point = 0.001 absolute value
Ř e.g. Dead-band value 100 = 0.1 then measurement must change by value
greater than 0.1 to trigger report
• 0 still means no dead-band
• 100,000 means changes greater than 100 are reported

Systems C264 IEC 61850 Implementation

• Object model covering IED measurements, control, recording and

some protection functions, including settings
• Un-buffered and Buffered Reports – configurable datasets
• GSE (IEC GOOSE) with digital statuses and analogues
Ř configurable messages
• SNTP time synchronization
• Controls
Ř Direct control with normal security
Ř SBO with normal security
Ř SBO with enhanced security

• Support for up to 5 Ethernet clients

• Configuration using ‘SMT’ tool of PACiS
 IEC 61850 Availability in MiCOM relays

Relay types with optional IEC 61850-8-1 interface now available to order:
• P132, P139 Feeder Management + Motor
• P141, P142, P143, P144, P145 Feeder Management
• P433, P435, P437, P439 Distance
• P442, P444 Distance
• P443 Distance
• P543, P544, P545, P546 Line Differential + Distance
• P631, P632, P633, P634 Transformer Differential
• P547 Phase Comparison
• P741, P743 Busbar
• P34x Generator

Protection Products IEC 61850 Implementation (1)

Functionality in MiCOM Px3x and Px4x relays

• Object model covering IED measurements, protection, control and
recording functions
• Unbuffered Reports (on change of state / deadband) – fixed datasets
• Disturbance Record file transfer
• GSE (IEC GOOSE) with digital statuses
Ř 32 digital statuses in published message
Ř 32 digital statuses in subscribed message
• SNTP time synchronization
 Protection Products IEC 61850 Implementation (2)

Functionality in MiCOM Px3x and Px4x relays

• Controls*
Ř Direct control with normal security
Ř SBO with normal security
Ř SBO with enhanced security
• Support for up to 16 Ethernet clients
• Protection & logic settings over Ethernet using MiCOM S1 Setting Software
Ř Available in S1 version 2.13 and later
• ‘IED Configurator’ software**, to configure communication aspects of the MiCOM
relay, per Part 6 of IEC 61850
Ř Available in S1 version 2.13 and later
* Initially in Px3x relays only
** Initially in Px4x relays only

Agenda

Chapter 1.1 : Generalities 9

Chapter 1.2 : Main Features 33

Chapter 1.3 : Communication 14

Chapter 1.4 : Inter-operability 6

Chapter 1.5 : Data Modelling 32

Chapter 1.6 : GOOSE Messaging 30

Chapter 1.7 : Engineering 30

Chapter 1.8 : Conclusion 8

 Summary..1

• One standardised communication for all needs in the

substation
• Fully supports all substation automation functions comprising
control, protection and monitoring
• Is a global standard and the key to interoperable solutions
• Architecture is future proof and facilitates future extensions,
therefore it safeguards investments
• Ability to reuse typical functions and/or bay designs vendor
independent

Summary..2

• Defines the availability requirements, environmental conditions

and the auxiliary services of the system
• Specifies the engineering process and its supporting tools,
system life cycle and the quality assurance requirements
• Provides engineering and maintenance support by means of the
substation configuration language based on XML, i.e.
documentation included
• Vendor-independent engineering-data exchange
 Summary..3

• States the conformance tests to be carried out on the products

• Flexibility allows optimisation of system architectures (scalable
technology)
• Uses commercially available hardened communication
components (Industrial Ethernet)
• Common use of infrastructure

Market demand:
Systems sales / Segmentation

• IEC 61850 has become a strong requirement for

Substation Automation Systems, approx. 40%
Ř Transmission: 60% (main exceptions: US, China)
Ř Distribution: 20% growing (linked to the IED price)
Ř Rail: 10% growing (Europe, India starting)
Ř Industry/ Oil & Gas: rare
 Market demand: Regional

Strongest demand in:

• India
• Brazil
• Central & South America
• China
• Middle East
• Europe – various countries

IEC61850 from Project Perspective

• IEC61850 is very large with many service models and optional

features
• End users implement different combinations of these service
models and the different features they provide
• The protocol is still being evolved
• Insufficient to simply specify IEC61850
• Necessary to state:
Ř What features are to be used
Ř What performance is required
• Requires detailed analysis and comparison of all products in the
project to ensure a good fit
 IEC61850 at Tendering stage

• A sample of important device specifications:

Ř Quantity of client/server associations to each IED
Ř Quantity of peer-peer messages the device will publish
Ř Quantity of peer-peer messages the device will subscribe to
Ř Number of characters allowed in the device name
Ř Service Models required
Ř Control models to be used
Ř Implemented Logical Nodes & Optional Data Objects/Attributes
Ř Implemented TISSUES
• Where can this information be found?
Ř Device Documentation
Ř Substation Configuration Language Files

Motivation for use of IEC61850

• Utilities expect
Ř Interoperability of:
• functions
• devices
• uniform system handling
• harmonised general system properties
Ř To Reduce Engineering Costs by:
• Standardized information exchanges between tools
• Reduction of manual entry & associated errors
• Reuse of project information & configuration