Protection & Control Communications With IEC61850

Protection and Control
Communications with IEC 61850

1 – Introduction
Eric A. Udren
WSU Hands-On Relay School
March 2013
Discussion leader
Eric A. Udren
 43 year distinguished career in design & application of protective relaying, control, and communications systems.
 Executive Advisor with Quanta Technology, LLC of Raleigh, NC in 2008.
 Developing substation protection and control upgrading strategies for major North American utilities, relay
application research and design, and new data communications applications.
 Developed software for the world’s first computer-based relaying system.
 S
Supervised
i d relaying
l i and d control
t l software
ft d
development
l t ffor th
the iindustry’s
d t ’ fi firstt d
development
l t off a LAN
LAN-based
b d
integrated protection and control system.
 Designed the first interface of a microprocessor protective relay to an optical current sensor.
 Developed the technical strategy for some of the most progressive utility LAN-based substation protection and
control upgrading programs using IEC 61850 and other data communications, including technical design for utility
enterprise integration of substation information.
 IEEE Fellow.
 Chairman of two IEEE Power System Relaying Committee (PSRC) Standards Working Groups
 Chair of PSRC Relaying Communications Subcommittee.
 Received the PSRC Distinguished Service Award in 2001 and again in 2006.
 Member of IEC TC 57 Working Group 10 responsible for IEC 61850.
 Technical
ec ca Advisor
d so too the
e US National
a o a CoCommittee
ee o
of IEC
C foro TC C 95, Measuring
easu g Relays.
e ays
 Member of NERC System Protection and Control Subcommittee (SPCS, formerly SPCTF).
 Member of NERC Protection System Maintenance Standard Drafting Team. (PRC-005-2)
 Has written and presented over 80 technical papers and chapters of books on relaying topics, and has taught
courses on protection, control, communications, and integration. 2011 GA Tech PRC Walter A. Elmore Best Paper
Award; IEEE Prize Paper Award.
 Holds 8 patents on relaying and power-system communications.
Eric is based in Pittsburgh, PA and can be reached at eudren@quanta-

technology.com or (412) 596-6959.
© 2013 Quanta Technology LLC Page 2
1
Impact of substation data communications
Substation or facility local area

network (LAN) SUBSTA.
LAN
- Lack of standard protocols and
intervendor communications was a user
issue for years.
 Goal 1: Collect relay data, give control for

SCADA & facility operators (speed, accuracy, completeness, interoperability).
 Goal 2: Access operational and non-operational data from
relays or meters for many business purposes
purposes.
 Goal 3: Replace wired P&C schemes with LANs.
 Goal 4: Replace switchyard/power equipment wiring for
instrument transformer, status, control signals with LANs.
Relay data for SCADA/EMS

 RTUs connect to the same ac and apparatus signals as
the relays – lots of extra wiring & electronics.
 Microprocessor (µP) relays are designed for
measurements status
measurements, status, control via LAN data
communications.
Goal 1: Concentrator on LAN collects relay values and
reports to SCADA & local interface computer.
 Serial LAN (RS-485, multiple RS-232) still widely used.
 Ethernet LAN – recommended for Smart Grid
applications.
 Standard protocols – DNP3/IEC 60870-5 and Modbus –
serial links or Ethernet LAN.
 Smart Grid standards – DNP3 and IEC 61850.
2
Relay data for SCADA/EMS
Capabilities of new µP relays:
 Fast response & fresh accurate data.
 DNP3 and Modbus on RS-485 serial or Ethernet ports.
p
 IEC 61850 MMS server-client functions.
 IEC 61850 GOOSE high-speed publish/subscribe of status,
metered analogs, synchrophasors.
 IEEE C37.118 synchrophasor streaming.
 Trial in 2012 – 61850
61850-90-5
90 5 high security WAN
synchrophasors and wide-area GOOSE.
Goal 2 - Enterprise information – reliability & economic benefits
Planning &
Control centers models
- EMS &
SCADA
Management
Substation
S b t ti Dashboard
LAN
Integrate relay data Maintenance
communications to CORPORATE
the enterprise WAN with
firewalls & push Asset
servers Managementt
M
Substation
LAN
Protection
& Control
Databases & back Engineering
office applications
& models
for organizational
users
3
Relay data for non-operational users
Goal 2: Use the same communications facilities to get non-
operational data to the enterprise:
 Fault location, outages, failures, and system
maintenance.
maintenance
 Fault and disturbance recordings, event logs.
 Relay and IED self monitoring and failure reporting for
condition based maintenance in NERC PRC-005-2.
 Performance statistics - protection & communications
system management.
 Power apparatus monitoring by relays and IEDs.
 Measurements for trending system operations –
planning, engineering, and protection.
 Substation revenue metering.
Protection & control over Ethernet LAN

Goal 3: Replace control wiring with messages
on data networks.
Substations & systems with IEC 61850
GOOSE messaging on optical Ethernet
LANs in service.
Carry status & control points, including
tripping and lockout.
High-speed analog values capability.
Messages
M & relay
l llogic
i replace
l wires,
i
control switches, lockout switches.
Dramatic wiring reduction in the station.
Can be faster than wiring.
4
Sampled Values service on process bus
 Goal 4: Replace switchyard/facility wires with a few optical fibers.

 Eliminate conventional cables and surge/EMI pickup.
pickup
 Move some measurement and control closer to the power
apparatus.
 Move the relays away from the apparatus.
Why focus on Ethernet communications?
 Important – Ethernet networks

carry any combination
bi ti off mixedi d
traffic types, protocols, services…
• Network tools to manage & prioritize mixed traffic.

• Modern Ethernet switches end old concerns about non-
deterministic network traffic with collisions.
• Mission critical electric utility/industrial
tilit /ind strial applications in service.
ser ice
• Extra network capacity gets cheaper rapidly.
• Development of IT is crowding out other approaches.
5
IEC 61850 ‐ Communication networks and
systems for power utility automation
 Big standard, evolving for 18 years and still going...
 10 original parts – now in Edition 2, plus >23 new parts!
 Multiple services – not a monolith:
 Server-client design for Ethernet networks.
 Application layers for utility/industrial system application.
 High speed protection, control, and sampled data streaming services.
 System-wide data and control services and methods.

 Single international standard for power system communications.
 N t just
Not j t a protocol
t l – includes
i l d ffunction
ti modeling
d li standards.
t d d
 Recognized by DOE & NIST as a Smart Grid communications
backbone – NIST Smart Grid Interoperability Panel (SGIP)
Category of Standards (CoS) listing.
What is IEC 61850?

A single international Ethernet based standard data communications
protocol & model structure with services and features aimed at protection
and control requirements:
 Relay/IED measurement & control exchanges with substation hosts –
RTUs, concentrators, HMIs – client-server objects.
 High-speed status, control, analog value transfer over LAN to eliminate
control wiring – GOOSE messaging.
 Switchyard/switchgear data acquisition and apparatus control – sampled
values (called process bus).
 Services for time synchronization (SNTP - obsolete), file transfer (FTP).
 Reporting and configuration services
services.
 Standardized automatic configuration of substation IEDs (SCL).
 New wide-area communications services.
Vision of a complete solution to replace existing diverse protocols and
communications systems.
6
IEC 61850 is not just a protocol on a wire…
• A modeling approach, a system architecture, and a protocol.
• Multiple services.
Models for
P&C functions &
Standardized points
configuration Ethernet
process LAN/WAN
Switchyard
sampled value
IEC 61850 High-speed
streaming Architecture GOOSE control
messaging
Ti
Time TCP/IP
TCP/IP,
synch UDP/IP,
with SNTP
Layer 2
COMTRADE
multicast
Fault records
Evolution of IEC 61850
DNP3 becomes IEEE 1815 & stays strong
1994
US approach UCA™ 2
2000-2012
The international goal – agree on a One standard

single standard IEC 61850
May 2000
1996 Asheville, NC
European
IEC 61850
experience UCA 2 & IEC
IEC 60870-5 61850 “merge”
IEC 60870-6
IEC 60870-5 – vendors shifting support away…
7
IEC 61850 wiring reduction
Integrated P&C system using fiber

optic network cables
Ethernet
Conventional
point to point
wiring
Standard
objects
objects,
models,
& point
descriptions Be careful – the wiring
goes away, but not the
complexity...
IEC 61850 Edition 1 Documents

System Aspects Data and Services Model
Part 1: Introduction and Overview Part 7-4: Compatible Logical Node Classes
and Data Classes
Part 2: Glossary
Part 7-3: Common Data Classes
Part 3: General Requirements
Part 7-2: Abstract Communication Services
Part 4: System & Project Management
Interface (ACSI)
Part 7-1: Principles and Models
Part 5: Comms. Requirements for
Functions and Device Models Mapping to Ethernet
Configuration Part 8-1: Mapping to MMS and ISO 8802-3

(Ethernet)
Part 6: Configuration Description
Language for Communication in Part 9-1: Sampled Values over Serial
Electrical Substations Unidirectional Point-to-Point link
using ISO 8802-3 (defunct)
Test
Part 9-2: Sampled Values over ISO 8802-3
Part 10: Conformance Testing
International Standard (IS) 9-2 LE: UCA Implementation Agreement for

merging units in switchyards (LE = Lite
Technical Report / Specification
Edition)
8
IEC 61850 as multivendor standard
 Aims for integration of multiple vendors’
devices.
 Each product has its own list of implemented
services and features.
 Conformance – a product is tested to validate
that its included services conform to standard
specs.
 Vendor gets KEMA, TÜV SÜD, etc. certificate.
 Interoperability – two or more products actually
exchange information (no certification yet).
 Be aware of compliant creativity, generic
modeling shortcuts. Will products actually
interoperate?
 Performance – a system of products performs
the application properly (no certification yet).
OSI 7-Layer Communications Stack
Layer Name Function
7 Application Meaning of the data (utility user specifics)
6 Presentation Building blocks of data and encryption for security
5 Session Opening and closing specific communications paths
4 Transport Error checking
3 Network Determining the data paths within the network
2 Data Link
Li k Data transmission, source and destination, checksum
i i dd i i h k
1 Physical Signal levels, connections, wires, fiber, wireless
9
IEC 61850 profile or stack - client-server exchanges
IEC 61850 Applications
MMS
ISO CO Presentation A li ti P
Application Profile
fil
ISO CO Session
RFC1006 - ISO TP0

TCP
IP p Profile
Transport
Ethernet
Fiber, Twisted Pair Cu
IEC 61850 Communications stack mappings
Application (Objects,Services)
Sampled Client - server

GOOSE
Values communications
Mapping
MMS
High-speed messaging
on LAN – skip WAN
layers
aye s a
and
dpprocessing
ocess g
delays
GOOSE & IP
Sampled Values: TCP
Layer 2 multicast Ethernet Link Layer (with Priority, VLAN)
Ethernet 100 MB/s Fiber
10
IEC 61850 Station Bus protocol services
Station bus mappings (8‐1)
For SCADA, protection, control, and
SCADA information for the enterprise
•Objects on MMS and TCP/IP layers
Obj t MMS d TCP/IP l
•GOOSE (on Data Link layer 2)
Substation •Time synch (SNTP) [Later IEEE
Host 1588/C37.232]
Station Bus
Relay 1 IED2 Relay 3
Process Bus
MU - CT MU - VT
IEC 61850 server-client object services

 The bulk of the standard (Parts 7-1, -2, -3, -4; new 7-
5, new applications) describes object modeling
methods.
 In general, relays and IEDs are servers; higher-level
computers and systems are clients.
 Data messages include point descriptions or
semantics – self-identifying.
 Products are self-describing – aimed at making
configuration faster and easier than with manual point
maps used with other protocols (Substation
Configuration Language, Part 6).
11
Object models - logical groupings
Data
Data Class
StV q Ph 1 Ph 2
A Logical Node
Pos (1 to n)
LN1 LN2
(XCBR) (MMXU)
Logical Device
(1 to n)
Logical Device
(IED1)
Physical Device
Physical Device
(network address)
Logical Node (LN)
 A single name always used for a particular function.
 Each
E h substation
b i ffunction
i may use one or more other h
logical nodes to perform its job (e.g., distance protection
needs measurements from logical nodes CT and VT).
12
Logical node groups
L: system LN (2) M: Metering and measurement (8)

P: protection (28) S: Sensor and monitoring (4)
R: protection related (10) X: switchgear (2)
C: control (5) T: instrument transformers (2)
G: generic (3) Y: power transformers (4)
I: interfacing and archiving (4) Z: further power system equipment (15)
A: automatic control (4)
Examples
p of Logical
g Nodes ((LNs):
)
PDIS: Line distance protection
PDIF: Differential protection CSWI: Switch controller
RBRF: Breaker failure MMXU: Measurement unit
XCBR: Circuit breaker YPTR: Power transformer
Logical Nodes (LN)

Control
Q0/CSWI
Disconnect sw. Grounding Switch Q8/CSWI
Q9_L1/XSWI Q8_L1/XSWI Q9/CSWI
Bay-HMI
IHMI
Circuit Breaker
Q0_L1/XCBR Distance Protection
Gas density monitoring PDIS
Q0_L1/SIMS
Control house
Primary equipment equipment
13
Accessing data
Tree view
IED1
+ PTOC
+ RREC
IED1/XCBR.Pos
- XCBR
+ Mode (Mode)
+ Beh (Behavior )
+ Health (Health)
+ Name (Name plate)
+ Loc (Local operation)
+ EEHealth (External equipment)
+ EEName (External equipment name plate)
+ O C t
OperCnt (O
(Operation
ti counter)
t )
+ Pos (Switch position)
+ BlkOpen (Block opening)
+ BlkClos (Block closing)
+ ChMotEna (Charger motor enabled)
+ CBOpCap (Circuit breaker operating capability)
+ POWCap (Point On Wave switching capability)
Accessing data
IED1
+ PTOC IED1/XCBR.Pos.stVal
+ RREC
- XCBR
+ Mode (Mode)
+ Beh (Behavior )
+ Health (Health)
+ Name (Name plate)
+ Loc (Local operation)
+ EEHealth (External equipment)
+ EEName (External equipment name plate)
+ OperCnt (Operation counter)
- Pos ((Switch position)
p )
ctlVal
stVal intermediate-state (0)
pulseConfig off (1)
operTim on (2)
q bad-state (3)
…more
14
Helpful explanation of 61850 modeling
By Karlheinz Schwarz,
Schwarz
Netted Automation GmBH
See
http://www.nettedautomation.com/qanda/iec61850/information-service.html#Q1
Hierarchical standard object naming

Example:
 Substation (S151) – Voltage level (E1) – Bay (Q3)
 Physical Device (BC) – Logical Device (CTR)
 <prefix> <Logical Node> <instance>
 Data description (from common data class, CDC)
 Attribute – the current value
In MMS notation:
 S151E1Q3 $ BCCTR $ Q0XCBR1 $ Pos $ ST$ stVal
Interpretation: (Substa-V-bay) . (Physical box, and functional
element
l within
i hi that
h h has b
breaker
k iimage)) . (I
(Image off B
Breaker
k
Q0) . (Data name Pos is position value) . Functional
Constraint ST (a momentary status report only) . [the status
value report – transition, open, closed, invalid]
15
LN example – control, breaker, voltage reg.
 Note generic LNs – manual config. – versus std. defined

LNs supporting auto config.
Time synchronization
 IEC 61850 specifies simple network time protocol
(SNTP) from the IT world.
 Accuracyy assured onlyy within a few milliseconds

(although some claim better recently).
 Requirement for time stamping of events and

oscillographic records is 1 ms (from NERC, for event
analysis)
 Requirement
equ e e t foro ttime
e sy
synchronization
c o at o o of waveform
a eo
sampling for process bus merging units is 1 to 10
microseconds, tighter for synchrophasors.
16
Time synchronization
 The practical solution – wired IRIG-B or fiber

connections of time synchronization signals directly from
GPS clock IED to IEC 61850 servers and clients.
 Same as non-61850 practice
 Leaves a few wires in an otherwise clean design
 IEEE 1588 – a new standard for time synchronization on
a LAN with sub-microsecond accuracy – IEC 61850
profile started at IEEE PSRC WG H7.
 PC37 238 IEEE 1588 Profile for Protection Applications
PC37.238
Configuration with 61850-6 SCL tools

Unified configuration of entire facilities via XML file
process – even over wide area.
Not exactly plug-and-play.
Functional specifications &

design standards
17
Some configuration tools
 Siemens DIGSI (oldest)

 GE EnerVista (umbrella for many functions; SCL added)
 SEL AcSELerator Architect
 ABB ITT Integrated Toolset (recent benchmark, but only ABB)
 Applied Systems Engineering (ASE) Visual SCL
 Triangle Microworks SCL File Editor, Anvil, Forge…
 Kalkitech SCL manager
 Helinks (from 61850 developers)
 Grid Smart 61850easy – handy diagnostics
Tools are biggest challenge – area of active work and user
complaints.

2 - GOOSE Messaging and Networks
Eric A. Udren
March 2013
18
Fast relaying over Ethernet LAN
From Part 1 -
Goal 3: Replace control wiring with messages on
data networks.
 Logicin the relays exchanges messages over
high speed redundant optical LANs to replace
wires, control switches, lockout switches.
 Dramatic wiring reduction in the station.
 Many
installations designed with IEC 61850
GOOSE messaging on LANs are in service.
 Statuspoints,
points control including tripping and
lockout, high-speed analog values.
 Can be faster than wiring.
Role of IEC 61850 GOOSE messaging
IEC 61850 GOOSE messaging provides:
 High-speed peer-to-peer transfer of status/control bits (reporting

contact state over a wire) or analog values including synchrophasors
for protection and control.
 GOOSE messaging plus programmable logic in relays and IEDs

replaces panel wiring and controls.
 Benefits – wiring and control elimination, panel and floor space

reduction, less equipment overall in P&C system, continuous
monitoring and management of the system design (“wiring”)
( wiring ).
 Works with other IEC 61850 services, or without them (e.g., with
60870-5 or DNP3 polling for SCADA)
19
61850 GOOSE and GSSE messaging
 Generic Object Oriented

Substation Event.
 A relayy or IED can send a

sequence of control, status point,
or analog value messages to
replace control and measurement
signals on dedicated wires.
 Not just a single message to request remote action…
 A process to “continuously”
continuously send intended state from
transmitting IED – like a contact that picks up and drops out
at critical moments.
 Even if a subscribing (receiving) relay is just powered up, it
can get updated status it needs.
GOOSE Protocol in 61850-8-2

 Application layer directly accesses link layer for speed – no TCP/IP
 Uses Ethernet frame directly with Priority/VLAN 802.1Q tag
 Use priority ≥4 due to criticality or messages.
 VLAN use is optional.
p
 Fields in payload - source ID, status bits, analog values, time stamp,
sequence number, time to live, quality bits, test modes.
 Typical packets 200 – 300 bytes long.
Ethertype (8100 = Ethernet
20
Overview of GOOSE messaging
Publisher-subscriber exchange:
 Each relay publishes a continuous stream of packets with values

that others might need.
 Any other relay or IED can subscribe to (view contents from) the
streams it needs.
 Publisher just talks – does not know who subscribers are, or

whether they got the messages in the stream.
Overview of GOOSE messaging

Adaptive rate of GOOSE message transmission:
• Time values are examples in standard – manufacturers vary.

• Some let you set base heartbeat rate and acceleration profile.
• Heartbeat reports values during quiescent times:
– Communications monitoring by all subscribing relays.
relays
– Update of latest status in case of any relay on the LAN that was
just turned on.
• Modern LAN with Ethernet switches handle all the messages even for
a worst-case power system event.
21
GOOSE packet rates
 SEL example, set 1 s  GE UR V5.70 example:

heartbeat:
Message Interval from Time
number
b previous, ms
i mark, ms
k
1 N/A 0
2 4 4
3 8 12
4 16 28
5 32 60
6 64 124
7 128 252
8 256 508
9 512 1s
Did the GOOSE messages arrive?
Publisher-subscriber exchange:
• Unconfirmed service, backed up by:
– Constant repetition or updating

updating.
– Redundancy in LAN and relaying
architecture.
– Monitoring and alarming by subscriber
IEDs that fail to receive publisher’s
message stream – call maintenance for
repair.
Wires cannot continuously monitor
themselves as GOOSE messages can do!
© 2011 Penwell & Quanta 44
Technology LLC
22
Analog GOOSE messaging
 Concept - send analog values with same millisecond

exchanges as for status or control points.
 Change events defined by settable measurement
deadband.
 Multiple values in one GOOSE packet.
Analog GOOSE messaging
Products today:
 Send analog values at a fixed slower rate – 100 ms
or 250 ms – not as useful for relaying as GOOSE
status
t t points.
i t
 Some will send values at rate driven by status points
in message, but analogs are repeated and updated
every 100 to 500 ms.
 NEW: publish synchrophasor values at a rate of 2 to
4 per second (GE and SEL) - Synchrophasor time
tags in packets.
 Ask vendor how to get at GOOSE time tag – not the
same as synchrophasor time tag.
 This GOOSE is too slow for high speed WAMPAC.
23
Speed of GOOSE messaging
GOOSE message control can
be faster than a wired
connection! Save 1-4 ms.
How?
A wired trip signal goes through:
 The relay processor output program loop delay.
 Output delay of hardware interface to wires.
 Input debounce filter delay of receiving relay.
 Signal
g waits milliseconds for the input
p p processing
g
program logic loop to notice it and react.
 GOOSE message bits are sent and read directly
between relay processors with microsecond Ethernet
delays.
Products vary – ask manufacturer, or test.
Electromechanical lockout switch drawbacks

 Adds 1 cycle operating time.
 Funnels wiring from bus full of
breakers into one panel location.
 A lot of wiring.
 Wiring reflects and must adapt to
changes in substation topology or
relaying philosophy.
 Rarely operates in normal service
– some jam
j anddddon’t’t ttrip.
i
 Dangerous testing challenge -
NERC says test it.
 Big cost adder to scheme –
deterrent to differential relay use.
24
Distributed lockout with GOOSE
 Each relay with relevant breaker control keep track of
lockouts in effect, by logic programming.
 Relays are coordinated by the lockout initiating relay, or
b a station
by t ti computert lockout
l k t monitorit function.
f ti
 Each relay has a nonvolatile memory of lockout state
(some use mechanically latched output relays).
 Uses messaging capabilities already in new relays.
 No extra wiring or cost.
 Self monitoring feature eliminates testing problem.
 As fast as direct tripping.
 See 2009 NETAWorld article by Myrda, Donahoe, Udren
for design example.
Ability to trip is monitored

End-to-end check of GOOSE communications:
 Transformer relay publishes a GOOSE message including a bus
breaker trip bit.
 Normal-state message (do not trip) is generated every second by DSP
in transformer relay.
 Passed through communications network to bus relay DSP
 Bus relay DSP alarms if no-action message disappears.
 Wires cannot check themselves this completely!
Bus Relay
Line Relay
System A
52 System A
TC
Ethernet Switch
System A
Monitor Xfmr Relay

IED
System A
System A
25
Redundant station bus
for IEC 61850 GOOSE
messaging
 Engineering of mission
critical substation
Ethernet network
 No single point of failure
within each of dual
redundant LANs.
 Use relay primary and
f il
failover optical
ti l Eth
Ethernett
ports.
 Dual switches and paths
for GOOSE messages.
GOOSE and wide area networks

 Multicast GOOSE messages have no destination address
 Designed to stay within a LAN or Virtual LAN.
 Do not pass through routers to the WAN or other LANs.
 But –routers make secure bridged connection between two
LANs separated by a WAN – works like one big LAN.
 Useable for transfer tripping, monitoring, control or load
mitigation via WAN.
 Need cyber security – VPN, firewalls, etc.
 Slows down messaging – today 20 ms
ms, getting faster
faster.
 See IEC 61850-90-1 for teleprotection over WAN
examples.
 See 61850-90-5 for new GOOSE streaming over WAN.
52
© 2013 Quanta Technology, LLC
26
Settings management
 Need a closed-loop business process that initiates and

tracks all installation and updating of setting records.
 Communicates with the IEDs themselves (over WAN is
future method) to check consistency between the data
base and the installed settings and firmware.
 Need a convenient way of installing settings within the
management system in every use case.
 Firmware update, maintenance check, operating
emergency, relay replacement, etc.
 New software data base tools can connect with tested
d i
devices, test
t t equipment,
i t andd enforce
f managementt
processes – OMICRON, EnoServ, IPS, others.
This is a big need for all 61850 services and systems, and
all new complex relays and IEDs!
Using 61850 services on the LAN

 Use client-server exchanges of standard defined objects for
metering, status, control, and IED configuration.
 Metering and status via polling or report-by-exception.
 No visible impact on installation – benefit is drive to easy
engineering and maintenance.
 DNP3 can perform similar role with familiar manual point
configuration lists.
 GOOSE messaging and Sampled Values service get rid of
conventional control wiring among relays, IEDs, power apparatus –
design commitment; visible change.
 DNP3 has no high speed data or control ability like GOOSE or Sampled Values
 New – 90-5 R-GOOSE and R-SV over WAN.
 LAN can carry mixed traffic – e.g. DNP3 metering and status, non-
61850 legacy device traffic, plus GOOSE for wiring elimination.
27
3 - Recent Developments in IEC 61850
Eric A. Udren
March 2013
IEC 61850 is living and growing
 IEC 61850 Edition 1 – the

seed – 1700 pages
IEC 61850 Edition 2
 International application –
improved models
 Expanded structure
 Improved clarity
 TISSUES (bugs)
(b ) cleared
l d
 New practical features
 New application domains
28
IEC 61850 is branching
New parts of IEC 61850
 Expanding outside the
substation
 Between substations
 To control centers
 Communications and
application modeling across
the entire power system
 Integration with enterprise
systems
 Interfaces with popular
SCADA and control protocols
 Wide-area high-speed data &
control services with security
What is new in Edition 2 of existing parts?

 Clarifications and corrections (TISSUES)
 Modeling
 Power Quality
 Statistical evaluation of information
 New models for mechanical equipment and measurements of
non-electrical quantities
 New features for testing support
 Support for exchange of engineering information for
configuration across projects and between facilities
 Redundancy – possibility to have IEDs with dual
connections
29
Testing improvements
• Edition 1 required expedient user construction of

testing facilities (mainly with GOOSE).
Edition 2 –
• Mirroring/feeding
/f back control information
f
• Isolation of functions in service
• Interlocking test methods
IEC 61850 – new parts

New facilities modeling:
 IEC 61850-7-410 – Hydroelectric power plants –
Communication for monitoring and control
 IEC 61850-7-420 – Communication Systems for
Distributed Energy Resources (DER)
 IEC 61850-7-500 /-7-510 (Technical Reports)
 Explains how to use the concepts of IEC 61850 to model
applications
 IEC 61400-25-x – Communications for monitoring and
control of wind power plants
30
More new parts under development
 Part 7-5 - defines the usage of information models for
substation automation applications - examples on how to
apply logical nodes from 7-4 for various applications.
 Part 7-10- web based IEC 61850 models
 More consistent implementations than those from programmers
reading paper documents.
 Part 100-1 - Methods for functional testing in IEC 61850
based systems.
 Configuration management of IEC 61850 based systems
Mappings for gateways

60870
Station Controller &
 IEC 61850-80-1 – Guideline for Gateway
exchange information from a 61850
common data class (CDC) based

data model using IEC 60870-5
60870 5
61850 61850
 IEC 61850-80-2/IEEE Protection Bay Controller
1815.1 – Exchanging
Information between DNP Master
networks implementing IEC
61850 and IEEE 1815
DNP Outstation
(DNP3) Gateway
 Just starting – IEEE C37.118 IEC 61580 Client
synchrophasors to IEC 61850-90-5
synchrophasors – at PSRC
IEC IEC IEC IEC
61850 61850 61850 61850
Device Device Device Device
31
How to address new areas?
 Technical reports explain “How to use IEC 61850 for...“

 Technical reports describe:
 The use cases considered
 The impact on the communication
 The impact on the modeling
 The impact on the engineering
 Results will be used to update the standards later.
(
(amendments
d t or new editions)
diti )
Technical reports (not standards)
 IEC 61850-90-1: Using IEC 61850 for communication

between substations (published)
 IEC 61850-90-2: Using IEC 61850 for communication
b t
between substations
b t ti and
d control
t l center
t
 IEC 61850-90-3: Using IEC 61850 for condition
monitoring
 IEC 61850-90-4: Network engineering guidelines
 IEC 61850-90-5: Using IEC 61850 to transmit
synchrophasor
h h iinformation
f ti according
di tto IEEE C37
C37.118
118
 Really important – how to stream sampled values,
synchrophasors, or GOOSE messages over WAN with
security using standard IT services
32
90-1 on interstation communications
 61850 communications, modeling/semantics, & system engineering
across stations need Ethernet communications.
 GOOSE needs LAN, or equivalent…
 Ethernet between stations:
 Wideband direct interfaces of LANs
 Tunnel that filters and directly passes packets over WAN
 Gateway that acts as a proxy for packets – e.g. teleprotection device
 Ethernet LAN/WAN configuration advice
Teleprotection equipment
acting as gateway
Station A Station B
? ? ?
Function Proxy Function
A1 B1 B1
Function Function
A2 B2
Transparent Tunnel
61850-90-2 and 90-3

 90-2 - Using IEC 61850 for the communication between substations
and control centers – in development
 90-3 – Condition monitoring of primary power apparatus –
communications & asset management requirements:
 Transformers, LTCs
 GIS
 Lines, UG cables
 Sta. batteries
33
Part 90-4 - Network Engineering Guidelines
 Ethernet network&
physical layers were black
box – you make it work.
 Now – comprehensive
guidance on reliable
network design.
Part 90-4 - Network Engineering Guidelines

Layer 2 redundant network paths for protection messages
 Short-bump or bumpless rerouting for segment failures
 62439-3 Parallel Redundancy Protocol (PRP) – 2 LANs
 62439-3 High availability Seamless Redundancy (HSR)
 Rapid spanning tree protocol (RSTP) from IT and redundancy – simple and
fine!
singly attached nodes
source destinations
DANH DANH
CPU CPU switch
„C“-frame „D“-frame
interlink
RedBox
„A“-frame „B“-frame
(HSR) (HSR)
CPU CPU CPU CPU CPU

DANH DANH DANH DANH DANH
destinations
34
90-5 WAN synchrophasor transport
 Sampled Value or GOOSE publish/subscribe across the WAN – useful
way beyond just synchrophasors.
 Add layer 3 transport – UDP/IP unicast or multicast (unconfirmed
efficient stream of data p
packets – not like slow,, confirmed TCP/IP))
 Routers can search for subscribers and establish routes dynamically
using Internet Group Management Protocol (IGMP) V.3, a standard IT
router service.
 New - a big deal – end-to-end authentication in the packet!
 SHA-2 authentication hash code - computed in real time.
 Needs new PMU/relay platforms/processors to compute
authentication hash code (coming in 2012).
 Industry standard Group Domain of Interpretation (GDOI) security
key distribution/management.
 Packet encryption specification – can be done in routers.
WG17 technical reports - SG integration
• IEC 61850-90-6: Using IEC 61850 for distribution automation.
• IEC 61850-90-7: IEC 61850 object models for photovoltaic, storage

and other DER inverters.
• IEC 61850-90-8: IEC 61850 object models for electrical vehicles.
• IEC 61850-90-9: IEC 61850 object models for battery storage systems.
• IEC 61850-90-10 – DER scheduling.
• IEC 61850
61850-90-11
90 11 – Modeling of
programmable logic per IEC 61499.
• IEC 61850-90-14 – Modeling of FACTS

power controllers
35
Other standards projects supporting IEC 61850
 IEC 62445-2 Standard for communications between

substation and control center.
 IEC
C 62351-6 - Cyber
C security structure ffor IEC
C
61850.
 Harmonize data models of IEC 61968 Common
Information Model [formerly EPRI CIM] and IEC
61850.
Product development
 61850 compliant relays and IEDs are widely available.
 It’s been a long expensive road for manufacturers – they are
committed to development.
 See http://www.ucausersgroup.org/ for list of compatible
products
d t and d other
th iinformation.
f ti
 In early 2012 – lots of servers (relays), growing choices for
clients (substation hosts), emergence of commercial process
bus (sampled data) systems based on IEC 61869-9.
 Learn status at UCA International Users’ Group
http://sharepoint.ucausersgroup.org/default.aspx
 Reports and related standards developments at IEEE Power
S t
System Relaying
R l i C Committee
itt (PSRC) meetings
ti
http://www.pes-psrc.org/
 Articles in PACworld magazine
http://www.pacw.org/home.html
36
IEC 61850 – supported in products
 Embeddable stacks for sale to IED manufacturers – Triangle
Microworks and SISCO.
 Supported by IED manufacturers – SEL, GE, Siemens, ABB,
Alstom Grid/Schneider, ZIV, RFL, Ametek Pulsar, others.
 R l ttestt sett manufacturers
Relay f t introducing
i t d i 61850 products
d t –
OMICRON, Doble, Megger, others.
 Industry-standard conformance testing program per 61850-10
and UCAIUG program with laboratories.
 Substations with significant 61850 in North America since 2005
– going into design standards at large utilities.
 Used in critical special protection schemes.
IEC 61850 versus DNP3

IEC 61850 Pros –
DNP3 Pros –
 Single international Smart Grid integration
 IEEE 1815 standard, long standard suite
complete (according to its own
 All required services
targets)
 All major vendors support
 Widely sold and used
used.
 High-speed control (GOOSE) and process
 Debugged, stable data (Sampled Values) including wide-area
and security
 Supported by Users’ Group
 Models the functions for automated
integration process (little hand configuration)
DNP3 Cons –  Supported by Users’ Group
 No high speed control or data
services, IEC 61850 Cons –
 Just for SCADA  Integration tools have been work in progress
for a long time
 Manual configuration of points and
data types takes time.  Interoperability work in progress
 Big product development effort, depending on
 Mostly North American scope focus.
 Design for usability and maintenance is an
area of opportunity
37
Troubleshooting Ethernet/61850 systems
 Function level monitoring - program the relay logic to report data
sent/received – catches most problems!
 This is an IT network.
 Basic tools for Ethernet networks – e.g.,
e g WireShark
 Protocol-specific tool examples:
 Applied Systems Engineering DNP3 Analyzer
 SMC 61850 GOOSEMeter (hand tool)
 61850Easy configuration/troubleshooting tools
 SISCO AXS4MMS Client - analyzer for relays (servers).
 SISCO GOOSE Blaster simulator
 NetScout network traffic monitoring for GOOSE
Most important – design functional test

features into the logic.
61850 progress
 Massive standard – growing beyond 2000 pages
(users don’t need to read all this).
 Continuing development and issue resolution among
vendors users
vendors, users, and standards developers
developers.
 Edition 2 and new parts of 61850 are being published.
 Supported by today’s major relay vendors.
 Paper and article traffic reaching saturation level.
 Varying interpretations by vendors require industry
conformance test program
program.
 61850 reaches inside the devices – there are problems
– get experienced guidance for standard development.
 DNP3 remains a widely used client-server protocol that
works on Ethernet (hand point map; no GOOSE).
38
Steps of typical IEC 61850 project
Each utility has unique organization and needs
1. Data gathering – engage all stakeholders up front!
2. Develop specifications.
3. Develop
p Request
q for Information ((RFI)) with specs.
p
4. Conduct RFI & process – get back a practical plan?
5. Business case - justify proceeding?
7. Full specifications.
8. RFP & vendor selection for trial standard system.
9. Detailed design with vendors.
10. Organizational design and preparation.
11. Development lab, training facilities.

12. Field trials.
13. Standards development; procedures and documentation.
14. Interface systems to the utility enterprise.

4 - Sampled Values Service & Process Bus
Eric A. Udren
March 2013
39
Sampled Values service for process bus
 If a LAN can carry critical

relaying traffic in the control
h
house, can it carry ddata
t andd
control between the switchyard
and the control house?
 Goal 4: Replace switchyard wires with a few optical fibers.
 Eliminate conventional cables and surge/EMI pickup.
 Move some measurement and control out to the yard, closer to the
power apparatus
apparatus.
 Just a few wires left - we still have to get dc and station service
power out to the yard.
Process bus
 Voltages, currents, and status sampled near the source and

converted directly to Ethernet packet stream.
 Multiple sample sets per packet for data transmission efficiency.
 Support trend towards intelligent power apparatus - relays,
metering, control IEDs installed directly in the power apparatus,
even in the factory.
 Reduce field wiring cost.
 Cut wiring losses and burdens.
 Add field signals without new wiring to control house.
40
Process Bus concept
 If we cut a microprocessor based relay in two and put a communications
bus between the I/O and the processing...
LP FILTER
Ethernet Network M
Communications µP LP FILTER
A/D
1 OR
Sub-
SAMPLE
AND
U
MORE
system
HOLD
X LP FILTER
CTs,
LP FILTER
VTs
125 Vdc Station Relay Output
Battery Supply
Relay Output
Trip and
Relay Output
alarm
circuits
POWER SUPPLY
Contact Inputs
Status
contacts
Control House Switchyard

Substation S/H & Filter
LAN Comm. A/D

M S/H & Filter
O/E Sub-
Controller system U S/H & Filter
X
S/H & Filter
Comm. Optical fibers Relay Output

µP Controller
Process Bus Combining data from diverse locations around the

LAN switchyard
S/H & Filter
A/D
Comm. Comm. Sub- M S/H & Filter
µP Controller
Controller system U
O/E X
S/H & Filter
S/H & Filter
Relay Output
Process bus services in 61850-9-2
•Sampled values protocol (on data

SCADA link layer 2 for speed and simplicity)
•GOOSE (on data link layer 2 for
speed d andd simplicity)
i li i )
Substation •Time synch (SNTP)
Host
Station Bus
Relay1
y IED2 Relay
y3
MU - CT Process Bus MU - VT
MU = switchyard Merging Unit
41
Merging unit
Line Protection Bus Protection

Ethernet Ethernet
Controller Controller
IEC 61850-9-2
Binary Inputs &
Ethernet Switch Process Bus
Control Outputs
Sample timing synchronization

Ethernet
Controller
Merging Unit C37 92 OVT

C37.92
EOVT with
fiber Combined C37.92 OCT
ECT and EVT
Conventional CTs
MOCT
fiber
Conventional VTs
Process Bus Protocol in 61850-9-2

 Application layer directly accesses link layer for speed – same as GOOSE
messaging – no TCP/IP
 Uses Ethernet frame directly with priority/VLAN .1Q tag
 Use p
priority
y ≥4 due to criticalityy or messages,
g , same as GOOSE
 VLAN use is optional
 What goes into the packet payload?
Ethertype (8100 = Ethernet
42
IEC 61850-9-2 frame – generic and flexible
Octets 8 7 6 5 4 3 2 1 Notes
Preamble
Start of frame
0
1
2
Destination address
3
4
5 Refer to “Address
Header
6 Fields” section.
MAC
7
8
Octets 8 7 6 5 4 3 2 1 Source address
9
10
1
TPID 0 x 8100 (802.1Q Ethertype) 11
2 12
TPID Refer to ”Priority
13 Priority
3 User priority CFI VID Tagging/VirtualLAN
14 tagged
TCI TCI section.
4 VID 15
16
Ethertype
17
18 Length Start
APPID
19
Service Default VID Default priority 20 Ethertype PDU
Length (m + 8)
Sampled Values 0 4 21
Refer to “Ethertype
22
Reserved 1 and Other Header
23 Information”
24 section.
Reserved 2
25
26
. APDU (of length m)
m + 26
.
(Pad bytes if necessary)
.1517
.
.
Frame check sequence
.
.1521
9-2 LE Implementation Guideline
43
IEC 61850-9-2 LE Data Set
 Fixed sampling rates of 80 or 256

samples per power cycle at 50 or
60 Hz.
 Fixed data frame format
 Fixed configuration format
9-2 LE fiber 1 pps synchronizing clock input specs
44
Unified substation-wide LAN using 9-2 LE
Chopping up the ring for redundancy

 Design concept of big ring station/process bus does not separate the zones
of protection – zones share merging units and communications.
 Relay engineers are used to separating zones of protection for reliability &
g
failure mode handling.
 Another way to apply MUs –
dedicated merging unit
function for each zone,
each location, and
System A or System B
– full redundancy and
isolation.
 This takes a lot more
equipment but
separates zones.
45
Another direction – 61850-9-2, but not 9-2 LE
GE Multilin HardFiber® process bus system.

 Uses conformant 61850-9-2 sampled values frame.
 Uses 61850-8-1 GOOSE for sampling synchronization and control .
 61850-8-1 GOOSE is not how 9-2 LE synchronizes sampling – not
compatible with other vendors’ MUs.
 Technically thoughtful (an opinion) architecture solution that
addresses application concerns:
 Isolation of protection zones.
 Isolation of redundant systems.
 Works with
ith toda
today’s
’s GE UR rela
relays.
s
 Each relay drives its own data sampling, as it does conventionally.
 Tracks system frequency and avoids distance relay polarizing
problems.
 Design includes solutions to installation efficiency and testing issues.
GE HardFiber® process bus system
 Weatherproof Brick® mounts on apparatus; has four mini merging units

inside – GE calls them cores.
 Connect to relays in control house via premade fiber assemblies and
weatherproof
eat e p oo co
connectors.
ecto s
Images
courtesy
GE Multilin
46
GE HardFiber components
 GE prefab copper cable  GE prefab multiple fiber plus power
for field connections – cable from Brick to SCE relays in
SCE facility.
CTs, PTs, contacts, trip
 Variety of standard lengths up to 500
circuits. meters.
 C il th
Coil the excess cable
bl where
h
convenient.
 Brick end and indoor end shown.
Images
courtesy
GE Multilin
 Indoors:
 Cross connect
panel.
 Fibers to/from
relays.
 Power from panel
to remote Brick via
HardFiber cable.
 Flexible easy
patching of Brick
cores to multiple
GE UR relays.
Images
courtesy
GE Multilin
47
 Process card replaces UR analog/binary input card.
 A special purpose Ethernet switch connecting
multiple brick core fiber signals to the protection
processor.
 NOTE: No network connection is possible to
existing UR Ethernet port used for:
 IEC 61850 GOOSE messages to control center.
 Relay settings, events, or configuration.
 Isolated by protection application processors.
 Can’t hack from Brick into substation network.
 Critical CIP compliance help.
Image
courtesy
GE Multilin
GE HardFiber system configuration

 Sampling is triggered by downward GOOSE messages, not 1 pps
timing fibers across switchyard.
 Electronic data sources are not shared across zones or between
redundant systems.
Image
courtesy
GE Multilin
48
HardFiber interoperability with other vendors?
 ABB, Siemens, Alstom Grid, SEL

used 9-2 LE.
 9-2 LE is an implementation
guideline,
id li nott partt off 61850 standard.
t d d
 Brick cannot work in a 9-2 LE system
& vice versa.
 What about multiple vendors and
interoperability of 61850?
2012 - a way out of the impasse

 Merging unit standards project in IEC TC 38 (Instrument
Transformers) – IEC 61869-9 Merging Unit Standard.
 IEC 61869-9 cites 61850-9-2 and chooses specific options – one
sampling rate only (4 kHz), standard frames, etc. – even more
specific than 9-2 LE.
 Eliminates 1 pps fiber time synchronization - IEEE 1588 precision
timing protocol (PTP) on the existing Ethernet connection to
synchronize samples.
 Every vendor can adapt its products to work with this standard
without big hardware changes.
 GE and the others said they will adapt to published standard
standard.
 Products interoperate, with flexible architectures.
 Implementation agreement in drafting.
49
Ngrid UK 400 kV process bus demo
 Ratcliffe indoor
substation
Switchyard maintenance solution!
50
Cost effective partial solution
 Extend the station bus into the switchyard for binary

status and control I/O.
 Put a remote binary I/O relay (SEL 451, GE UR C90+,
etc.) in the switchyard for all status and control via
GOOSE.
 Wire only the CTs and CVTs back to the control house.
 Eliminate 70-80% of switchyard wiring.
 We can do it right now.
 Solution for NU 61850 EHV P&C design standard.
Questions?
eudren@quanta-technology.com or (412) 596-6959.
51

Protection &amp; Control Communications With IEC61850

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Protection &amp; Control Communications With IEC61850

Uploaded by

Copyright:

Available Formats

Protection and Control

Communications with IEC 61850

Eric is based in Pittsburgh, PA and can be reached at eudren@quanta-

© 2013 Quanta Technology LLC Page 2

Substation or facility local area

 Goal 1: Collect relay data, give control for

© 2013 Quanta Technology LLC Page 3

Relay data for SCADA/EMS

© 2013 Quanta Technology LLC Page 5

Goal 2 - Enterprise information – reliability & economic benefits

Integrate relay data Maintenance

© 2013 Quanta Technology LLC Page 6

Protection & control over Ethernet LAN

 Goal 4: Replace switchyard/facility wires with a few optical fibers.

© 2013 Quanta Technology LLC Page 9

Why focus on Ethernet communications?

 Important – Ethernet networks

• Network tools to manage & prioritize mixed traffic.

© 2013 Quanta Technology LLC Page 10

 System-wide data and control services and methods.

© 2013 Quanta Technology LLC Page 11

What is IEC 61850?

© 2013 Quanta Technology LLC Page 12

© 2013 Quanta Technology LLC Page 13

Evolution of IEC 61850

DNP3 becomes IEEE 1815 & stays strong

The international goal – agree on a One standard

IEC 60870-5 – vendors shifting support away…

© 2013 Quanta Technology LLC Page 14

Integrated P&C system using fiber

© 2013 Quanta Technology LLC Page 15

IEC 61850 Edition 1 Documents

Configuration Part 8-1: Mapping to MMS and ISO 8802-3

International Standard (IS) 9-2 LE: UCA Implementation Agreement for

OSI 7-Layer Communications Stack

Layer Name Function

© 2013 Quanta Technology LLC Page 18

IEC 61850 Applications

RFC1006 - ISO TP0

Fiber, Twisted Pair Cu

© 2013 Quanta Technology LLC Page 19

IEC 61850 Communications stack mappings

Sampled Client - server

© 2013 Quanta Technology LLC Page 20

Relay 1 IED2 Relay 3

IEC 61850 server-client object services

© 2013 Quanta Technology LLC Page 22

© 2013 Quanta Technology LLC Page 23

Logical Node (LN)

 A single name always used for a particular function.

© 2013 Quanta Technology LLC Page 24

L: system LN (2) M: Metering and measurement (8)

© 2013 Quanta Technology LLC Page 25

Logical Nodes (LN)

© 2013 Quanta Technology LLC Page 26

© 2013 Quanta Technology LLC Page 27

© 2013 Quanta Technology LLC Page 28

© 2013 Quanta Technology LLC Page 29

Hierarchical standard object naming

© 2013 Quanta Technology LLC Page 30

 Note generic LNs – manual config. – versus std. defined

© 2013 Quanta Technology LLC Page 31

 Accuracyy assured onlyy within a few milliseconds

 Requirement for time stamping of events and

Protection & Control Communications With IEC61850

Protection & Control Communications With IEC61850