1

Tutorial on IEC 61850

Lima, October 14th, 2015

Thierry Lefebvre, EDF

Carlos Rodriguez, REE
Jaume Darne, PullNet
14/10/2015
Thierry Coste, EDF
2 Contents
1. At the beginning,
1. a strong need for standards dedicated to susbtations, relationships
with CIGRE
2. What is 61850 ?
1. Description of the main characteristics, The 61850 series for substations
2. The data model
3. Focus on communication inside and between substations (+ network
topology & Ethernet configuration)
4. Communications services, tools and roles
3. Extensions…towards a universal protocol for transmission &
distribution automation
1. Areas addressed: wind farms, hydro, DER, telecontrol, energy
storage…
2. Roadmap for short term extensions
3. How to cope with 61850 extension of scope ? 14/10/2015

4. Discussion
 At the begining…a challenge…
3 the digital substations
 80’s: several countries carried out experiments for EHV digital substations (USA,
Canada, Japan, France, Spain…) => many challenges were to be tackled:
 Performances,
 interfaces
 Data representation & interoperability
 Variousness…
 Early 90’s: first attempts for a standardization at CIGRE, EPRI/IEEE…
 CIGRE 35 => PiComs
 AHG in TC57 on substation architecture, decision in 1995 to launch 3 WGs :
 WG10: archirecture, WG11: control level, WG12: interfaces with process
 End of 90’s: agreement between IEC & IEEE => stds will be developed
in one place
 .
TC88’s demand to TC57 for Wind farm
control,Data & protocols
 61850 series for substation published in 2003

14/10/2015
 TC57 : Power system information management &
associated information exchange
To prepare international standards for power systems control
equipment and systems including EMS, SCADA, DA, teleprotection,
and associated information exchange for real-time and non-real-time
information, used in the planning, operation and maintenance of
power systems.

Power systems management comprises control within control centres,

substations and individual pieces of primary equipment including
telecontrol and interfaces to equipment, systems and databases, which
may be outside the scope of TC 57.
___

4
 TC 57 , production overview
 Reference Architecture for Power System Information Exchange
 Telecontrol
 60870-5, derivative DNP-3 in the US
 TASE.2 for inter control centres communications (60870-6)
 DLMS, Information exchange for metering
 61850 as universal protocol for power system management
 Distribution automation: substations control, measurement & protection, teleprotection
(62351)

 Wind power farms control, Photovoltaic, storage

Security

 Hydro power plant

 Distributed ressources control, Microgrids
 Electrical Vehicle (connection to the grid)
 CIM, for Common Information Model
 Energy management systems (61970)
 Distribution management sytems (61968)
 Communication exchange for markets (62325)
 Interfaces and communication profiles to Home/Building/Industry
Automation

5
Now… 61850 series is one of sets of core standards providing
interoperability in the power industry
CIM (IEC 61968, IEC 61970, IEC 62325)
Energy Management Systems
Distribution Management
IEC 61850
Market Communication
Substation automation
Distribution automation
Distributed Energy Resources
Hydro Power

Market

Enterprise

Operation

Station
Generation Zones
Transmission Field (Hierarchy)

Distribution
Process
DER
Domains Customer
14/10/2015
(Home, Building,
Industry, EV, Mobility)
Page 6
7
What is 61850 ?
 Description of the main characteristics, the 61850 series for
substations
 Focus on communication inside and between substations (+
network topology & Ethernet configuration)
 Data configutaion
 Roles played in the 61850 environment

14/10/2015
 What is 61850 ?
8
 Description of the main characteristics,
 Principles & contents
 the IEC 61850 series for substations

14/10/2015
 Incentives for 61850
9 in Substations Interoperability between pieces
of equipment (standardization of
data exchanged)
Overall configuration including
communication network and
embedded function
Enhanced Maintenance
with a clear separation
between functional
representation, physical
implementation and
communications stacks
To cope with the drastic
increase in data & in
applications 14/10/2015
10 How to cope with such a complex
problem ? Interfaces  interactions

14/10/2015
 11

Interfaces  interactions

Interfaces
 IF1: protection-data exchange between bay and station level
 IF2: protection-data exchange between substations. This interface refers both to analog
data e.g. for line differential protection and binary data e.g. for line distance protection
 IF3: data exchange within bay level
 IF4: Current transformer (CT) and Voltage Transformer (VT) instantaneous data transport
(especially samples) from the process to the bay level. This comprises in the reverse
direction also the protection trip
 IF5: control-data exchange between process and bay level
 IF6: control-data exchange between bay and station level
 IF7: data exchange between substation (level) and a remote engineer’s workplace
 IF8: direct data exchange between the bays especially for fast functions like interlocking
 IF9: data exchange within station level
 IF10: control-data exchange between the substation and remote control centre(s) 14/10/2015
 IF11: control-data exchange between substations. This interfaces refers to binary data e.g.
for interlocking functions or inter-substation automatics
 A quick overview on the documentation
12

14/10/2015
 Real world versus Virtual world
13

14/10/2015
 Structure & Content
14

System Aspects Data Models

Part 1: Introduction and Basic Communication Structure for
Overview Substations and Feeder Equipment
Part 2: Glossary Part 7-4: Compatible Logical Node Classes and
Part 3: General Requirements Data Classes
Part 4: System and Project Mng Part 7-3: Common Data Classes
Part 5: Comm Requirements for
Functions and Device Abstract Comm. Services
Models Basic Communication Structure for
Substations and Feeder Equipment
Configuration Part 7-2: Abstract Communication Services (ACSI)
Part 6: Configuration Lan- Part 7-1: Principles and Models
guage for electrical
Substation IED’s Mapping to real Comm. Networks (SCSM)
Part 8-1: Mapping to MMS and ISO/IEC 8802-3
Testing Part 9-1: Sampled Values over Serial Unidirectional
Part 10: Conform. Testing Multidrop Point-to-Point link
Part 9-2: Sampled Values over ISO/IEC 8802-3

14/10/2015
15 Structure & content…relationships with
a well-know model

14/10/2015
 Structure & Content: the logical node in its
16
environment

14/10/2015
 Structure & Content
17
The « what »
(Data model)
(IEC-61850 7-3; 7-4

IED Request IED

Inteligent Inteligent
Electronic Electronic
Device Device

Response

Indication

The « how to exchange » (IEC-61850 7-2)

14/10/2015
18 General Principles
Data Model
CEI 61850 7.3, 7.4
Information
Model

Abstract Communication
Service Interface
ACSI (services) CEI 61850 7.2
SCSM
WebServices
IECDLMS
DNP3
MMS
OPC
61870-5
(Mappings)

Mapping other protocols

CEI 61850 8.1, 9.1, 9.2
7
6
5
4
3
2 Stack of communication
1 MMS, TCP/IP , Ethernet
14/10/2015
19
What is 61850 ?
1. Description of the main characteristics,
 Data model

14/10/2015
20 The data model
IEC 61850 – Communication networks and systems for power
utility automation.

The building block => Logical Node

The circuit breaker:
A typical example of LN (XCBR)
From the LN to data
A hierarchical model

14/10/2015
 Structure & content: the hierarchical
21
model of the substation
LN , IHM CALH IHM CILO
substation
level Human Interlocking on
Interface Alarm station level
machine handler

Generic
Automation
LN, bay level Process
CSWI CILO ATCC
GAPC Control

Circuit Interlocking Automatic

A generic node for al non Breaker on bay level Tap controler
pre-defined funtions Controler

Generic
Input and
Output
LN, process level GGIO Control XCBR XSWI YLTC

A generic node for al non Circuit Breaker Isolator Tap changer

pre-defined Process devices

14/10/2015
22 Data Model
A : Automatic control
P : Protection Functions
C : Supervisory Control
Q : Power Quality Events
D : DER (Distributed Energy Ressources)
R : Protections Related Functions
F : Functional Blocks
S : Supervision and Monitoring
G : Generic functions Process I/O
T : Instruments Transformers and Sensors
H : Hydro power
W : Wind power
I : Interfacing and Achiving
X : Switchgear
K: Mechanical and non-electric primary
Y : Power transformer and related fonctions
equipement
Z : Further (power System) equipment
L: System Logical Nodes

M : Metering and measurement

154 LOGICAL NODE (Ed2 7-4)

14/10/2015
23 Data model

14/10/2015
 The Circuit Breaker
24

14/10/2015
25

DATA « Pos »
= 20 DATA ATTRIBUTES

Data Attribute « Pos.Ctval »

Control Information
ON / OFF

Data Attribute « Pos.Stval »

CB State
ON / OFF / Not valid

14/10/2015
 Compatible LN and
data object classes
26
IEC 61850-7-4

Mandatory / Optional
/ Conditional

The logical node

describes the
data that are
needed for the
inter-working

14/10/2015
 Common
data classes
IEC 61850-7-3
27

CDC : Comon Data Class

- DPC -

14/10/2015
28
IEC 61850-7-3

14/10/2015
 Data Model IEC 61850-7-3
29

Common Data Class (CDC) :

• States
• Measurements
• Triping
• Parameters
• Information

14/10/2015
30

LLN0 provides device

state & mode (LD)

LPHD provides the state

of the physical device or
of the server (IED)

14/10/2015
31

An example
of a simple modelisation

14/10/2015
32

Data Set

14/10/2015
33
Part 9-2 Sampled Values

14/10/2015
34
What is 61850 ?
1. Communication inside and between substations
 Preliminary concepts
 Network topology
 Ethernet configuration

14/10/2015
 Sas Structure
35

Remote Network Control Centre

SUBSTATION LEVEL Comms to/from Network Level

* Operator Workstation & HMI
* Gateway to NCC

BAY LEVEL Interbay bus (LAN)

* Protection, Control and
Measurement IED’s

PROCESS LEVEL Process bus

(Ethernet and Optical fibre)
* I/O Remote Units
* Intelligent sensors
* Primary system devices

14/10/2015
 The Bus Topology
36

 Four main possibilities:

 Single and double star
• Only 1 or 2 Main Switches
• High Number of ports per switch
• High performance Switch necessary
 Single and double three
• IEDs are chained towards the Bay Level
• Latency in transversal Communications
• Improved resiliency compared with star
 Mesh
 The Ring Topology
37
 Standard de facto in Industrial
Ethernet Networks
 Single element failure protected
 Multiple variants
• Single ring
• Multiple rings chained
• Ring of the rings
 Interconnecting points does not
increases significantly the risk
 Deterministic topology
 Balanced trade off between
efficiency and cost
 Ring Topology
38

WAN

SWITCH

SWITCH SWITCH SWITCH

IED IED IED IED IED IED

BAY 1 BAY 2 BAY n

14/10/2015
 Double Star Topology
39

WAN

SWITCH SWITCH

HUB HUB HUB

HUB
HUB HUB

IED IED IED IED IED IED

BAY 1 BAY 2 BAY n

14/10/2015
 The Cost of the Topology
40
 Main Protocols Resume
41
 RSTP + IEEE 802.1D
 Popular and Universal use
 Compatible with all Topologies
 Ring enhancements boost the recovery times up to 10 ms.
 MRP IEC 62439-2
 Single ring topology only. Uniform ring
 R.T. depends of the switch count: 14 Sw / 10 ms, 50 Sw / 30 ms
 Ethernet Filtering Database (FDB) flushed during Transition
 PRP IEC 62439-3
 Two independent networks with any topology
 Zero packet loss but un-deterministic in some cases
 Protocol implemented at the Endpoints. No recovery time
 HSR IEC 62439-3
 Standard HSR unpractical outside of ring topology.
 Implemented on two port IEDs with bridging functionality
 Zero packet loss. Un-deterministic. Duplicates the ring traffic
 IEC 62439-3 PRP
42
 Parallel Redundancy Protocol – “Bumpless redundancy”
 Cada trama se envía simultáneamente por ambos interfaces
 Al llegar las tramas al IED, una de ellas se descarta
 El IED sabe en todo momento el estado de las dos redes

ETHERNET
NETWORK
A

PROTECTION
MERGING UNIT
DEVICE

ETHERNET
NETWORK
B

Ethernet frame
14/10/2015
 HSR protocol implementation
43

14/10/2015
 Other Proprietary Ring Protocols
44

 MOXA’s V-ON PROTOCOL

 Initially developed for multicast streaming on uniform ring
 Based on previous Turbo- Ring and Turbo-Chain protocols.
 Recovery time: 20 to 50 ms
 KYLAND’s DT-RING
 Ring specific protocol. Uniform Ring
 Recovery time: 40 ms for a 15 nodes network
 Strongly dependent of the position and device count
 KORENIX’s SUPER RING
 Works with single or multiple uniform rings
 Recovery time 5 ms. Packet loss during transition
 Proprietary patented protocol suite
 VLAN Tunneling
45
 Allows the transport of some VLANs grouped in VLAN tunnel
 Grouping criteria based on QoS (Q-in-Q)
 VLAN stacking. Many Q-Tags stacked in the same tunnel
 VLAN IDs count increased
 Priorized VLAN structure

VLAN VLAN
VLAN VLAN
30 40
10 20

VLAN VLAN
30 20
VLAN VLAN
40 10
14/10/2015
 46

VLAN 5
VLAN 5
VLAN 4
VLAN 4
VLAN 3
VLAN 3
VLAN 2
VLAN 2
VLAN 1
VLAN 1

802.1Q
802.1Q

VLAN 1 - 4
VLAN 4

802.1Q
Example

Server1

VLAN 3
802.1Q
802.1Q

VLAN 2
VLAN 5
VLAN 1 VLAN 4

VLAN 1
Server2

VLAN
3-5
14/10/2015
47
Priority Criteria

Priority level 0 – Best Effort (ordinary LAN)

Priority level 1 – Background (specific applications)

Priority level 2 – not defined (reserved)

Priority level 3 – Excellent effort (business critical)

Priority level 4 – Controlled load (streaming multimedia)

Priority level 5 – Voice and Video (< than 100ms latency and jitter)

Priority level 6 – Voice and Video (< than 10ms latency and jitter)

Priority level 7 – Network control, critical, reserved traffic

14/10/2015
48
IEC 61850 Recomends…

14/10/2015
49
Timing Synchronization

14/10/2015
50
Synchronization Requirements

14/10/2015
51 Contents
1. Communication services
2. Tools
3. Roles
4. Discussion

14/10/2015
52 Communication services

 IEC 61850-5: Communication requirements

 IEC 61850-7-2: Abstract Communication Service Interface
(ACSI)
 IEC 61850-8-1: Specific implementation of ACSI services over
Ethernet and MMS
 IEC 61850-9-2 defines a specific implementation of the
Sampled Values services over Ethernet
 Goal: Communication services independent of the
implementation
 Specific implementations depending on the domains

14/10/2015
53 61850-5: Communication requirements

 Piece of Information for COMmunication (PICOM)

 Interchange of information between two logical nodes
 Defined in the specification phase by the user
 Part 5 defines several performance classes based on types
 Type 1: Fast messages (“Protection”)
 Type 2: Medium speed messages (“Automatics”)
 Type 3: Low speed messages (“Operator”)
 Type 4: Raw messages (“Samples”)
 Type 5: File transfer functions
 Type 6: Command messages and file transfer with access control
 A performance class is associated to each PICOM
14/10/2015
54 61850-5: Communication requirements

 Each type message is associated to typical interfaces

Time constraint

14/10/2015
55 61850-5: Communication requirements

 Part of the system

specification
 Each interaction between
logical nodes must be
defined
 Tools can be used to make
the process easier,
replicable and to generate
an SSD file
 Annex A and B defined
typical PICOMS in
substation automation
systems
PTRC 14/10/2015

1 Type as defined in Annex B

56 61850-5: Communication requirements

 Time defined in part 5 is

transfer time
 Process time taking into
account functions time to
process information is not
covered

14/10/2015

1 Type as defined in Annex B

57 61850-7-2: ACSI services
 Independent of the protocol stack used for implementation
 Services for
 Fast interchange of information (Goose)
 Data acquisition (polling, report)
 Sequence of event off-line acquisition (Log)
 Control model and services
 Substitution model and services
 Association for client-server model
 Auto descriptive services (to recover IED data model)
 Settings
 Sampled values
 Synchronization and file transfer
 Create, Query, Delete Dataset
14/10/2015
 Tracking services
58 61850-7-2: ACSI services
 Information model class  Control model

14/10/2015
59 61850-7-2: Dataset and Control Block

 A dataset is an ordered set of data objects/data attribute

references of a Functional Constraint (FCD or FCDA)
 A Control Block defines how a dataset is transmitted using a
specific ACSI service
 Applicable to:
 Goose
 Sampled values
 Report
 Log
 Settings
 Tracking

14/10/2015
60 61850-8-1: ACSI services over Ethernet and MMS

 Specific implementation of the ACSI services

 Using Ethernet and MMS protocols

14/10/2015
61 GOOSE
 Publish – Subscription mechanism over Ethernet frames
 Event-driven mechanism
 Used for fast transmission of information (trips, blockings, …)
 A dataset and a GOOSE Control Block is used
 Published in a multicast address over a VLAN
 Each message has three protocol control values
 State change number: Increase by one when a new event is generated
 Sequence number: Increase by one each time a Goose message is
repeated. Reset to 0 when a new event is generated
 Time Allowed To Live: Time for the subscriber to wait for the next repetition of
the Goose message

14/10/2015
62 GOOSE

Goose Goose
IED 1 switch IED 2
Goose
IED 3
Goose
IED 4

stNum=1;sqNum=128
T0

stNum=1;sqNum=129 (1) sqNum is set to 0 when a

Event … new event is detected
T1
stNum=2;sqNum=0 (2) sqNum is set to 1 when it rolls
stNum=2;sqNum=1 over
T1
stNum=2;sqNum=2

14/10/2015
63 Reports
 Typically used for data acquisition
 Client-Server mechanism over MMS association and TCP
connection
 Interested in status, quality and time tag information
 Time constraint is around 200-500 ms
 A dataset and a Control Block is used
 Two types of service: Buffered and Unbuffered reports
 Buffered report store reports when there is no connection with
the client to send them after reconnection
 Trigger Options can be configured in Control Blocks
 Report must be enabled by the client before receiving 14/10/2015

information
64 Reports
Client Server

ASSOCIATE-request

ASSOCIATE-confirmation

Write “OptFlds”

OK

Write “TrgOpts”

OK

Write “RptEna” = “true”

OK

Event
Report
< BufTm

Event
Report

< BufTm

14/10/2015
65 61850-9-2: Sampled values
 Sampled values are mapped over Ethernet
 Can be unicast or multicast
 Needs PPS signal
 The number of samples per period is configured
 Samples are numbered sequentially and reset each second
 Multiple samples can be sent in the same ASDU
 Control Blocks are handled using MMS (client-server services)
 Typical rates: 80 samples/cycle (2 Mbps), 256 s/c (16 Mbps)
 IEC 61850-9-2 LE is a specific profile widely used today

14/10/2015
66 Tools: Going deeper into the process
 SCL language provides the means to configure the
communication between IEDs
 Do we intend to create SCL files by hand? Of course we don’t
 Standards writes about top-down approach

14/10/2015
67 Tools: Going deeper into the process
 Logical Node Library
Specification  PICOMs
System Specification Tool (SST)
 Single Line Diagram SSD File
 Substation Automation Functions
IED Procurement
 Requirements about function allocation
IED Templates Library

 Specific IED allocation

Engineering  Specific Goose and report messages defined System Configuration Tool (SCT)
 Specific Network architecture SCD file
 SCL Configuration Files generation
IED Configuration Tool (ICT)
Factory test
 Configuration of IEDs System Configuration Tool
 Functional test
CID, IID files
 Installation of equipment
Installation  Configuration of the network IED Configuration Tool
 Wiring, functional test Testing tools
IID files
Commissioning  Global tests, testing procedures
Network protocol analysers
 Diagnostics 14/10/2015
Testing tools
Exploitation  Maintenance tests
 Upgrades System Configuration Tool
68 System Specification Tool
 Tool to generate the final user specification using IEC 61850
semantic language and data object architecture
 Creation of the logical node instances needed
 Definition of the PICOMS between logical nodes
 Possibility of creating virtual IEDs (collection of Logical Node
instances grouped in Logical Devices)
 Virtual IEDs help the IED procurement process
 The output is an SSD file to be used during the engineering
process
 This tool is normally part of the System Configuration Tool

14/10/2015
69 Engineering process
 Top-down approach based
 Inputs: SSD file and IED Library

14/10/2015
70 System Configuration Tool (SCT)
 IED independent tool to generate a System Configuration File
 Creation of IED instances from IED Templates
 Engineer the data flow between IEDs
 Give addresses
 Bind logical nodes to primary system
 Handle SCL sections
 Substation section (single line diagram)
 Communication section, including IP address assignments
 Datasets and control blocks
 Allocation of report control blocks to clients
 DataTypeTemplates reorganization
14/10/2015
71 System Configuration Tool (SCT)
 Creation of the real IEDs
IED instantiation
 Allocation of IEDs per bay

 Network architecture
Network
 Connection of IEDs to the network

ACSI services  Dataset configuration

configuration  Control Block configuration

Network
 IP addresses
parameters

GOOSE  Final GOOSE configuration (VLAN, priority)

 Final Report, LOG configuration (Client

Reports, Logs
assignment to reports)

Network check  Check the configuration of the network 14/10/2015

72 System Configuration Tool (SCT)
IED selection
1. Single wire
2. IEDs
SSD File
DataSet
DataSet
<FCDA>
DataSet
<FCDA>
<FCDA>

3. Physical Conn.
ReportControlBlock GSEControlBlock
<DataSet> <DataSet>

Network
Datasets
Control Blocks
Services
Between
4. Goose & IEDs
IED.cid Subs.scd
IED.cid Reports
IED.cid
14/10/2015

Output SCL Files

73 Documentation
74 IED Configuration Tool (ICT)
 Tool to create IED templates (ICD, IID files)
 ICD is the basic, pre-defined template for an IED product type
 IID file is an ICD file with modifications on the data model,
parameter and configuration settings
 Tool to create final IED configuration file (CID file)
 Bind incoming data from other IEDs using the imported SCD file

14/10/2015
75 Tools for exploring IEDs
 IEC 61850 provides semantic interoperability
 Independent third party tools can connect to any IED
 To connect to the IED
 To subscribe to IED Goose messages
 To recover the IED data model
 To acquire real time information from the IED
 To enable reports available in the IED
 There are a lot of different tools in the market for this purpose
 There are also tools for simulating IEDs

14/10/2015
76 Tools for maintenance and diagnosis
 Tools for maintenance and diagnosis are out of the scope of
the standard
 Utilities to specify what they need for maintenance
 Specific tools should be developed for utilities
 A engineering mapping information is usually needed for
maintenance
 Maintain the well-known semantic of information
 A mapping between IEC 61850 data model and engineering semantic
 A troubleshooting guide related to communication and lose of service is
needed, as maintenance people have to know the implications

14/10/2015
77 Tools for testing
 IEC 61850 edition 2 has improved testing functionalities
 In a digital world, isolating IEDs implies isolating messages in
the network
 Testing tools are needed and must cover edition 2
functionalities
 Clear procedures must be defined for testing
 Tools to implement the procedures in order to automatize the
process
 Keep in mind that factory, commissioning and maintenance
tests are similar, but they are not the same

14/10/2015
78 Roles in IEC 61850: Who is who?
 Roles
 End user: the ultimate owner, operator
 Integrator: in charge of the detailed design
 Constructor: group that does the physical build
 Vendor: supply products
 The same company or group can have different roles
 The utility can be end user and also integrator
 A company can be integrator, constructor and vendor
 Roles – Companies relation depends on the project type
(turnkey project, internal project, outsourcing, …)

14/10/2015
79 Roles in IEC 61850: Who is who?

Role Specific IED Engineer Factory Installati Commis Exploitat

ation Procure ing Test on sioning ion
ment

End user
X X X X

Integrator
X X X

Constructor
X X

Vendor X

14/10/2015
 61850 Extensions & future work
 Extensions…soon on your screens !
 IEC/ACTAD: Guidelines for extending scopes (mainly for
TCs)
80
 Miscellaneous (verbal), depending on the remaining
time:
 61850 users’ group, UCA
 61850 maintenance
 core components,
 XML tools for speeding up publications of standards
 TC57 reference architecture
 […] 14/10/2015
61850 – one of the core standards providing
interoperability for Smart Grids & power systems
CIM (IEC 61968, IEC 61970, IEC 62325)
Energy Management Systems
IEC 61850 Distribution Management
Substation automation Market Communication
Distribution automation
Distributed Energy Resources
Hydro Power

Market

Enterprise

Operation

Station
Generation Zones
Transmission Field (Hierarchy)

Distribution
Process
DER
Domains Customer
14/10/2015
(Home, Building,
Industry, EV, Mobility)
Page 81
82 IEC 61850 is extending
IEC 61850 Scope (2011) 0
Smart Users
185
6
C Charging
IE -9
station

61850-90
IEC
IEC 6140
Control center 0-25
Network SCADA
IEC 61850
stability

IEC 61850
IEC 61400-25

IEC 61850-90-2
Use of 61850
IEC

IEC 61850-80-1
Guideline to exchange 61850
for substation to IE Wind power plant
control center C IEC 61400-25
61
618

information over IEC 60870-5- (expected)

101/104 85
0
50

IE
C
-90

IEC

61
Local
-5

RTU

85
Synchrophaser SCADA IEC 61850

618
IEC 61850-90-5

0
(PMU)
Distributed Energy Ress

50
IEC 61850-7-420
IEC 61850 IEC 61850-90-7
Station IEC 61850 Power Utility substation B
IED IED IED IEC 61850-90-1
between stations
IEC 61850
Hydro power plant
Power Utility substations A IEC 61850-90-6 IEC 61850-7-410
IEC 61850-7-4 MV network

Storage
XXX IEC 61850 parts, as of 2010
IEC 61850 future parts
XXX (already engaged)

XXX New IEC 61850 work

14/10/2015
 IEC 61850 extensions
83
Charging
station 1. Alarm management
2. Logic modeling
Control center

3. FACTS
SCADA
Network
IEC 61850
stability
IEC 61400-25

IEC 61850
Use of 61850
IEC 61850-80-1

4. Bulk generation
for substation to
Guideline to exchange 61850 control center Wind power plant
information over IEC 60870-5-101/104 (expected)

Local
5. Revenue metering (COSEM)
SCADA RTU IEC 61850-7-420
6. Scheduling
Synchrophaser
(PMU)

Distributed Energy
IEC 61850 Resources
IEC 61850-90-7
Station
IEC 61850 Power Utility substation B 7. Storage (battery)
IED IED CTs/VTs IEC 61850-90-1
between stations

IEC 61850-7-410 8. Condition monitoring (UPS)

9. Feeder automation (Fault
Hydro power plant
Power Utility substations A IEC 61850-90-6
IEC 61850-7-4 MV network Storage
detectors - with TC38)
IEC 61850-90-8
XXX
10.EV charging spot
IEC 61850 parts, as of 2013

IEC 61850 future parts (already DER Integration

XXX engaged)
IEC 61850-90-15

11.Network management
*: use of IEC 61850 over WAN can/will take advantage of
IEC 61850-80-1, IEC 61850-90-2 and IEC 61850-8-2 (web based) , and IEC 61850-90-12 (WAN)

12.Multiple use of DER

13.Communication from CC to SS

14/10/2015
 61850 road map (within TC57)
84

14/10/2015
 IEC 61850 documentation structure (reminder)
85
Introduction
IEC 61850-1
Glossary
IEC 61850-2
General requirements System and project management
IEC 61850-3 IEC 61850-4

Domain specific application

Application guide guides
IEC 61850-7-5 IEC 61850-7-5xx
Compatible LN and Data Domain specific LN and Data
object classes object classes
Basic Technical Technical
IEC 61850-7-4 IEC 61850-7-4xx Configuration specification report
communicati
on structure description --- ---
Principles Common Data Classes language Guidelines Guidelines
and models IEC 61850-7-3 IEC --- ---
IEC 61850-6 IEC IEC
61850-7-1 Basic models, abstract services and basic types 61850-80-xx 61850-90-xx
IEC 61850-7-2
Communication
requirement
for devices and Mapping on network Sample Values mapping on
functions (except sample values) network
IEC 61850-5 IEC 61850-8-xx IEC 61850-9-xx

Implementation in IEDs and tools

Conformance testing
14/10/2015
IEC 61850-10
86 Additional deliverables
Introduction
IEC 61850-1
Glossary
IEC 61850-2
General requirements System and project management
IEC 61850-3 IEC 61850-4

P3
Product-specific profiles

Basic Compatible LN and Data Product specific LN and Data

communi- object classes object classes
Technical
cation IEC 61850-7-4xx xxxxx P2
Configuration specification
structure ---
description
Principles Guidelines
Common Data Classes language
and ---
models IEC 61850-7-3 IEC
61850-6 IEC
IEC
Communic Basic models, abstract services and basic types 61850-80-1
ation 61850-7-
IEC 61850-7-2 Protocol
require- 1
Cases of ---
ment
use of a for devices Mapping on network Sample Values mapping on IEC
given and (except sample values) network 60870-5-101
product functions IEC 61850-8-xx IEC 61850-9-xx 60870-5-104
IEC
61850-5
P1

Implementation in IEDs and tools

Conformance testing
IEC 61850-10
14/10/2015
Product Profiles conformance testing P4
 How to manage extensions ?
87 To sum up
uc Product specialisation

Complement IEC
61850 usage to
support "product"
integration

«include»
«include»
«include»
«include»
Product profile
testing
«include» «include»
List the main cases
of use of the product
Define typical
Get the know ledge of «precedes» classes of products «precedes»
the existing 61850
(per set of functions)
content
«precedes»
Define product
«precedes» profile(s) - if needed
«precedes»
«precedes»
Define a product
Identify possible
namespace - if «include»
61850 gaps «precedes» «include»
needed

Define
«include» interoperability Publish profile(s)
«precedes»
obj ectiv es
Propose 61850 data
model extensions
«include» «include» «include»

Get a model manager Get the proposed Publish a namespace

nominated «precedes» model rev iew ed
«precedes» extension 14/10/2015
 Guideline for Technical Committees
88 and Working Groups on Using IEC
61850
1) Scope
The guide is for working groups (in / out side TC57) that intend to use IEC
61850 as a base standard within the scope of their work. The document
shall help to identify the required steps in applying IEC 61850 for
standardization work and shall provide guidelines for the individual steps.
Within that scope, the document addresses the following topics.
 For the usage of IEC 61850 for new domains, the initial analysis how IEC
61850 can be used and what extensions may be required. The results of
that step may be documented in a technical report.
 The extension of the IEC 61850 object models for new domains. The
typical work associated with that is, to identify existing logical nodes
that can be reused with or without extensions and to define new logical
nodes.
 Product standards for products that have an interface based on IEC
61850.
 IEC 61850 profiles for domains.
14/10/2015
89 Guide, Table of contents (1)
2) How to use IEC 61850 for a domain
 Data Model
 Check existing logical nodes
 Identify usable LNs
 Identify extension requirements
 Identify new LNs
 Identify requirements to extend CDCs
 Communication
 Check services; identify services to be used; identify need for new services
 Identify requirements on communication network topology, redundancy,
reliability
 Engineering
 How to apply engineering; new requirements?
 Document with a technical report
 Security
14/10/2015
90 Guide, Table of contents (2)
3) Guideline for extension of IEC 61850 Object Models
 Principle modeling concepts
 Detailed modeling guidelines
4) Product standards for products with IEC 61850 interface
 Recommended elements of a product standard
 Additional specifications – nameplate; logical devices,
datasets, control blocks, etc
5) IEC 61850 profiles for domains
 Elements of a profile
 Profile / a product standard

14/10/2015
91
Discussion & Experience
Questions ?

14/10/2015