Substation Automation Systems - Day 3 - 1 IEC61850 The Approach and Standard

ABB Substation Automation Systems
IEC 61850 The Approach and the Standard
ABB Group July 26, 2012 | Slide 1
Content
Approach
Object Oriented Data Model
Logical Nodes
Data Hierarchy Communication Services
Substation Configuration Language
Conventional substation
Introduction to station bus
IEC61850
Introduction to process bus
High communication capacity

Remote Control (NCC)
Station Computer Gateway Station
Office
SMS & PCM TCP/IP LAN
Station Level
Station Bus or Interbay (LAN) IEC61850-8-1
Control Protection Protection & Control Protection Control
Bay Level
Process Bus (LAN) IEC61850-9-2
Process Level
Process Interface
Process Interface
Process Interface
Requirements for Standard in SA
Interoperability
The ability for IEDs from one or several manufacturer to exchange information and use the information for the their own functions.
Free configuration
The standard shall support different philosophies and allow a free allocation of functions e.g. it must work equally well for centralized (RTU like) or decentralized (SCS like) systems.
Long term stability
The standard shall be future proof, i.e. it must be able to follow the progress in communication technology as well as evolving system requirements.
Approach - Lifecycle
Long term stability through elimination of dependence on fast evolving automation technology
Slow IEC61850 Data Model of the Substation
Long-term definition Safe-guarding investments Abstract Interface
Mapping of objects & services
Mapping of objects & services
Only adaptation for new Communication stack nessecary.

Stack Interface Stack selection following state-of-art Communication technology
Fast
7 6 5 4 3 2 1
MMS
*)
TCP/IP
Ethernet
7 6 5 4 3 2 1
*) MMS : Manufacturing Message Specification
The Data model is mapped unambiguously to an existing stack. Example: Communication Technology ISO/OSI seven layer stack
Approach of IEC 61850
Slow changes
Data Model
Domain Substation : What data have to be communicated ?
DEFINITION Data and Services according to the Domain Substation
Communication Technology: How are the data communicated ?
Communication
MAPPING Data Model to the Communication Stack
ISO/OSI Stack Fast changes

SELECTION ISO/OSI Stack from the Main Stream
From real model to abstract model

Logical device (Bay) 61850-7-2 Services
Encapsulated real world
(Virtual)
Virtualization
Mapping
Network TCP/IP
MMS
LN
LN
LN
XCBR1
Position
SCSM, i.e. 61850-8-1
Mode
...
61850-7-4 logical node (circuit-breaker)
Real devices in substation
61850-7-4 data (Position)
61850-6 Configuration File

Data Hierarchy
Physical Device (IED) defined as Server
Bay Unit
Implementation
Logical Device (LD) Grouping
Bay Controller
Logical Node (LN)

Data Data (Object)
XCBR Circuit breaker
Position
Properties
Attribute Value
Control Value
ON/OFF
Status Value
INTERM./OFF/ON/BAD
User-near, object oriented Data model

Every days objects for the Substation Engineer
SIMG
Example : Object Current Breaker XCBR What data belong to this object ?
SIMG XSWI SIMG TCTR PTRC PTOC
CSWI CSWI TVTR
XSWI
CSWI
These Objects are called Logical Nodes
XCBR
Primary Technology (Switchgear)

Secondary Technology (Substation Automation)
Naming and Groups of Logical Node (First letter listed)
L System LN (2)
P Protection (28) R Protection related (10) C Control (5)
M Metering and measurement (8)

S Sensor and monitoring (4) X Switchgear (2) T Instrument transformers (2) Y Power transformers (4) Z Further power system
equipment (15)
G Generic (3)
I Interfacing and archiving (4)
A Automatic control (4)

Examples

PDIF: Differential protection

RBRF: Breaker failure
CSWI: Switch controller

MMXU: Measurement unit
XCBR: Circuit breaker
YPTR: Power transformer
Introduction of Logical nodes: Functional view
Communication relations between functions in a Substation Automation System Information is exchanged between all devices which comprise the system More precisely, data are exchanged between the functions and sub-functions residing in the devices
The smallest part of the function that exchanges data is called Logical Node (LN) in IEC 61850. The LN performs some operations for the overall function
Functions are not standardized ?

Introduction of Logical nodes: Data view
Exchanged Data in Substation Automation System
More precisely, data are exchanged between the functions and sub-functions residing in the devices
The exchanged data are grouped to into objects belonging to functions The objects called Logical Node (LN) may be seen as Containers containing the data provided by a dedicated function for exchange (communication)
The Name of the Logical Node may be seen as a Label attached to this container Functions are not standardized !
Allocation of LNs to devices (IEDs)
Device Example: Station Workplace

IHMI
(Human Machine IF)
Device Example: Combined Protection and Control Unit

CSWI
(Switch Controller)
PDIS
(Distance Protection)
TVTR
XCBR
(Circuit Breaker)
(Voltage Transformer)
TCTR Device Example: Circuit Breaker

(Current Transformer)
Device Example: Combisensor
Allocation of LNs to devices (IEDs)
Device Example: Station Workplace

IHMI
(Human Machine IF)
Control Unit CSWI

(Switch Controller)
Protection Unit PDIS

(Distance Protection)
Voltage Sensor XCBR

(Circuit Breaker)
TVTR
(Voltage Transformer)
TCTR Device Example: Circuit Breaker

(Current Transformer)
Current Sensor
High degree of freedom for optimization
Free allocation of Logical Nodes (functions) to devices
The support of free allocation Logical Nodes (functions and sub-functions) allows an optimization of systems today and tomorrow The free allocation is controlled by strict rules and the concept of IEC 61850
The free allocation does not disturb interoperability but may increase the requirements for tools
The free allocation is limited by the device capacities as described in data sheets same as today
Maintaining interoperability by strict rules for Extensions
Existing Logical Nodes, Data, and Attributes shall be used if applicable Mandatory data shall be provided if claiming conformance Before making any extension, the Optional data shall be used if applicable If the conditions apply, Conditional data get mandatory For Extensions of Logical Nodes, first data defined for other Logical Nodes shall be used In creating data extensions, combinations of well-defined Terms shall be used Name spaces shall be used for any extension referring to some document where the meaning and the use of these extensions is defined
Communication Services Overview
There are 3 services available for sending data on the communication bus
Network Control Centre

SAS Station Computer
Gateway
Client - server: Commands, Reporting, Log, Directory services, File transfer
Master Clock
Ethernet Switch
IEC61850-8-1 Station Bus
Real time: GSE

Protection Control
......
Protection
Control
Process Bus IEC61850-9-2
Real time: SV, GSE

Bay N
Bay 1
Merging Unit
Data access and transfer (Services)
read a value / attribute

write configuration attributes control a device (direct operate / select before operate) event oriented communication with reporting local storage of time-stamped events in a log get directory information
file transfer for e.g.

parameter and software download upload from monitoring information like travel curves or history of gas density values
Transfer of generic object oriented system events (GOOSE)
Transfer of sampled (analog) values (SV)
Data access and transfer (Services)
Data Model that can be accessed Query
Reply
What can be changed (IEC 618550-7-4 and 61850-7-3)
Events
How to change (IEC 61850-7-2)

How to exchange data by serial communication ? Sender: Information Receiver: Information
Rules for Coding Information in Bits ?
Rules for Decoding Bits Back to Information ?
Line: Series of Bits = Telegrams

Coding information in the ISO/OSI 7 layer model
Sender: Coding
Application data
Receiver: Decoding
Application Layer
Application Layer Presentation Layer Session Layer
6 Presentation Layer
5 4 Session Layer
Transport Layer Network Layer

Link Layer
Transport Layer Network Layer

Link Layer
3
2 1
Physical Layer
Physical Layer
The 7 layers of the ISO/OSI Model
Application Process (Function)
Stack = Hierarchical Set of Rules For Coding and Decoding
Full 7 Layer Stack
Application L.
X11, MMS, http, etc.

Presentation L.
Session Layer Transport Layer
Internet TCP/IP
Network Layer needed for Networks (LAN) Link Layer
Office, Home Ethernet
Physical Layer
MMS Manufacturing Message Specification TCP Transport Control Protocol IP Internet Protocol
Mapping the Data Model to the Stack

SA specific data model evolves slowly Communication technology changes quickly Splitting of SA specific data model from communication technology
Abstract Communication Services Interface (ACSI)
Data Model (Objects,Services)
Client Server Communication
GOOSE*
Sampled Values
Mapping
MMS
Stack Interface
Time critical Communication
ISO/OSI Stack Hierarchical set of Rules how information is coded for transmission According to state-of-the art communication technology
TCP IP Ethernet Link Layer with Priority tagging

Ethernet Physical Layer (100 Mbit/s)
* Generic Object Oriented Substation Event

Stack selection according to the state-of-the-art Communication technology
Model according to state-of-the-art SA technology
Vertical communication
Control Station
Examples: Comands Events
Station Level
Vertical Serial Communication
HMI
Station Computer
Gateway
NCC
IEC 61850
Bay Level
Parallel cabels (vertical) Parallel cables horizontal ?
Control
Protection
Protection & Control
Control
Protection
Process Interface
Process Interface
Process Interface
Process Level
(Equipments, processes)
Vertical communication
Control Station
Examples: Comands Events
Station Level
HMI
Station Computer
Gateway
NCC
IEC 61850
Bay Level
Examples: Samples Trips Positions
Control
Protection
Control
Protection
Process Interface
Process Interface
Process Interface
Process Level
Horizontal communication
Control Station
Station Level
HMI
Station Computer
Gateway
IEC 61850
Horizontal communication
Examples: Blockings Unblockings States
Bay Level
Vertical Serial Communcation
Control
Protection
Control
Protection
Process Interface
Process Interface
Process Interface
Process Level
The mechanism Client-Server messages
Client Server
A point point association is established and supervised and may be terminated: Associate / Release / Abort MMS: Dynamically built (server addresses, authentication) Maximum client number is IED implementation dependent The mechanism of TCP is very reliable Telegrams are acknowledged on a low level Normally, no data are lost since telegrams with errors may be resend again
Comfortable mechanism you know it from your office and from the Internet - but time consuming, i.e. not suited for time-critical communication
Common features of Reports, GOOSE and SV
All these three services send data spontaneously, i.e. without being asked from a Master or Client For defining the data to be transmitted by these services, a Data Set is defined comprising all these data out of the overall data model (for Report, GOOSE or SV)
The triggering event (conditions) when the data transmission is performed has to be defined in a Control Block (for Report, GOOSE or SV)
The triggering event for Reporting and GOOSE messages may be a change of a value, a crossing of a boundary, etc.
The triggering event of sending synchronous sampled values (SV) is a clock event
How to handle these spontaneous services?
The reception of a report is confirmed on lower layers, and in case of losses repeated. This takes some time.
The data stream of sampled values (SV) is not confirmed, but losses of some samples are handled without problems by the receiving functions, e.g. by a protection algorithm.
The unconfirmed GOOSE messages may transport important time critical information like a block or a trip. Therefore, a special mechanism has to guarantee a reliable transfer of these data (see next page).
Horizontal communication: GOOSE

SCADA Engineering
GPS
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Switch
The mechanism of GOOSE messages
Without any changes, the GOOSE-message is repeated with Tmax until the next event / change.
t max = 1024ms
t max = 1024ms
time
In case of a information-change, the GOOSE-message will be repeated within Tmin. The repetition frequency is lowered until Tmax is reached.
t max = 1024ms
t min = 2ms
t max = 1024ms
time
Time synchronization
Time synchronization is independent from the other services

Currently defined: SNTP (Simple Network Time Protocol) for 1 ms accuracy (class T1)

The IED fetches the time from a time server The transmission delays are corrected by a special procedure
There might be different actual services for different synchronization accuracy classes Under discussion: IEEE 1588 as HW addition to Ethernet for 1 s accuracy (Classes T3 T5); needs support in switches
IEC 61850 Overview and status

IEC 61850: Communication Networks and Systems for Power Utility Automation
IEC 61850 Edition 2 Why Edition 2 is required
Remedying various shortcomings identified during first installations

Enhance the applications range / new applications

Automation of wind power systems Hydro power systems
Distributed energy resources

Combined heating and power systems
Photovoltaic plants
Beyond the switch yard

Communication between substations Communication between substations and network control centers
Remaining challenges from Edition 1
Complete process bus between primary and secondary equipment (analog samples and switch positions and commands)
IEC 61850 Edition 2 Definition of IEC 61850 Edition 1 and Edition 2
IEC 61850 EDITION 1

Published parts tagged as Edition 1 First 14 parts of the standard SERIES IEC 61850 (published 20012004) IEC 61850-7-410 (Hydro Power)
IEC 61850-7-420 (DER)
IEC 61850 EDITION 2

There will not be an EDITION 2 of the standard SERIES IEC 61850 per se Various parts will be revised / extended and then published tagged as Edition 2.0
New parts will be published with the tag Edition 1.0
Name the specific part when talking about Edition 2
Optional
IEC 61850 Edition 2 Main features and benefits

Communication principles between substations based on IEC 61850
Communication between substations
Data model and SCL extensions for communication between substations
Direct tunneling of Ethernet Level

Proxy gateways with low-bandwidth Higher Integration
IEC 61850-90-1
Redundancy in the nodes
Redundant IED interfaces
(n-1) criteria
Zero recovery time upon failure

Refers to IEC 62439-3

PRP: Parallel Redundancy Protocol

HSR: High-available Seamless Redundancy
Higher System Availability

IEC 61850-8-1, IEC 61850-9-2
Optional

Example for statistical methods (ClcMth) applied on MMXU
Statistical evaluations of measurements

Contained in the logical nodes MMXU and MMXN Triggered by Power Quality discussions and other application domains like Wind power
More information
IEC 61850-7-3, IEC 61850-7-4
Support for tracking and logging
Services and service responses

Makes service parameters and service handling visible without the use of protocol analyzers Uses standards existing reporting and logging facilities
Logical Node LTRK defines control and access service tracking
Commissioning and security supervision
IEC 61850-7-3, IEC 61850-7-4
Increased Security
Optional

Management hierarchy for logical devices
Management hierarchies of logical devices
Especially complex multifunctional protection IEDs request more functional levels for the management of common parameters Higher level logical device controls the mode of the lower level logical devices by group reference
IEC 61850-7-2
Reduced complexity
New data objects and concepts for testing

Testing during system is in operation using test mode
Testing of function parts in the running system Allows a standardized application of the test and test-blocked mode
IEC 61850-7-2
Easier testing and maintenance
Optional
SCL extensions
Describes new IED properties

IID: Instantiated IED Description Describes the instantiated data model of an IED SED: System Exchange Description Describes interface data exchange between different projects
Clear and more flexible Engineering
SCL implementation conformance statement (SICS)
IEC Engineering data exchange using substation configuration language (SCL)
61850-6
Stating mandatory and optional features of IED tools and system tools Allows judging the degree of interoperability between different engineering tools, system tools as well as IED tools.
Clarity on Interoperability
IEC 61850 Edition 2 Introducing new edition into products and solutions
Time Schedule of the standard
Main parts of IEC 61850 standard with Edition 2 ready by end 2010
Edition 2 complete (all 14 parts that are affected) is expected by end of 2011
Product certification

New test procedures, client and server certification Certification of Edition 2 devices earliest possible by mid 2012
Migration scenarios
Edition 1 and Edition 2 devices can work together considering there are no new features out of Edition 2 used
No need to upgrade server devices to Edition 2 e.g. protection and control IEDs
Main issue is to ensure tools and clients support both Edition 1 and Edition 2
Example for Logical Node (1) out of part 7-4
Common Logical Node class Attribute Name LNName Data Attr. Type Explanation Shall be inherited from Logical-Node Class (see IEC 61850-7-2). T M/O
Mandatory Logical Node Information (Shall be inherited by ALL LN but LPHD)

Mod Beh Health NamPlt Loc EEHealth EEName OpCntRs OpCnt OpTmh INC INS INS LPL SPS INS DPL INC INS INS Mode Behaviour Health Name plate Local operation External equipment health External equipment name plate Operation counter resetable Operation counter Operation time M M M M O O O O O O
Optional Logical Node Information
Data Sets (see IEC 61850-7-2) Inherited and specialised from Logical Node class (see IEC 61850-7-2). Control Blocks (see IEC 61850-7-2) Inherited and specialised from Logical Node class (see IEC 61850-7-2). Services (see IEC 61850-7-2) Inherited and specialised from Logical Node class (see IEC 61850-7-2).
Example for Logical Node (2) out of part 7-4
XCBR class Attribute Name LNName Data Attr. Type Explanation Shall be inherited from Logical-Node Class (see IEC 61850-7-2) T M/O
Common Logical Node Information see Example for Logical Node (1)
Loc EEHealth EEName OpCnt SPS INS DPL INS DPC SPC SPC SPC BCR INS INS INS LN shall inherit all Mandatory Data from Common Logical Node Class Local operation (local means without substation automation communication, hardwired direct control) External equipment health External equipment name plate Operation counter Switch position Block opening Block closing Charger motor enabled Sum of Switched Amperes, resetable Circuit breaker operating capability Point On Wave switching capability Circuit breaker operating capability when fully charged M M O O M M M M O O M O O
Controls
Pos BlkOpn BlkCls ChaMotEna
Metered Values
SumSwARs
Status Information
CBOpCap POWCap MaxOpCap
Examples of Attributes allocated to Common Data Class (CDC)

DPC class Attribute Name Attribute Type FC TrgOp Value / Value Range M/O
DataName
Inherited from Data Class (see IEC 61850 -7-2)
DataAttribute
control and status

ctlVal operTim origin ctlNum stVal q t stSeld pulseConfig ctlModel BOOLEAN TimeStamp Originator INT8 CODED ENUM Quality TimeStamp BOOLEAN PulseConfig ENUMERATED CO CO CO, ST CO, ST ST ST ST ST CF CF off (FALSE) | on (TRUE) AC_CO_M AC_CO_O AC_CO_O AC_CO_O M M M AC_CO_O AC_CO_O M
out of Part 7-3
0..255 dchg qchg dchg intermediate-state | off | on | bad state
configuration, description and extension

status-only | direct-with-normalsecurity | sbo-with-normal-security | direct-with-enhanced-security | sbo-with-enhanced-security operate-once | operate -many Text
sboTimeout sboClass d dataNs cdcNs tag
INT32U ENUMERATED VISIBLE STRING255 VISIBLE STRING255 VISIBLE STRING255 Tag
CF CF DC EX EX AX
AC_CO_O AC_CO_O O AC_DLN_M AC_DLNDA _M O
The Data Attributes for Substitution have been taken out for editorial reasons
Refinement of Data Class

Substation Automation Systems - Day 3 - 1 IEC61850 The Approach and Standard

Uploaded by

Document Information

Original Description:

Original Title

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

Substation Automation Systems - Day 3 - 1 IEC61850 The Approach and Standard

Uploaded by

Copyright:

Available Formats

ABB Substation Automation Systems

IEC 61850 The Approach and the Standard

ABB Group July 26, 2012 | Slide 1

Substation Configuration Language

ABB Group July 26, 2012 | Slide 2

ABB Group July 26, 2012 | Slide 3

Introduction to station bus

ABB Group July 26, 2012 | Slide 4

Introduction to process bus

ABB Group July 26, 2012 | Slide 5

High communication capacity

Requirements for Standard in SA

Long term stability

ABB Group July 26, 2012 | Slide 7

Slow IEC61850 Data Model of the Substation

Long-term definition Safe-guarding investments Abstract Interface

Mapping of objects & services

Mapping of objects & services

Only adaptation for new Communication stack nessecary.

*) MMS : Manufacturing Message Specification

ABB Group July 26, 2012 | Slide 8

Approach of IEC 61850

DEFINITION Data and Services according to the Domain Substation

Communication Technology: How are the data communicated ?

MAPPING Data Model to the Communication Stack

ISO/OSI Stack Fast changes

SELECTION ISO/OSI Stack from the Main Stream

From real model to abstract model

SCSM, i.e. 61850-8-1

Real devices in substation

61850-7-4 data (Position)

61850-6 Configuration File

Physical Device (IED) defined as Server

Logical Node (LN)

XCBR Circuit breaker

ABB Group July 26, 2012 | Slide 11

User-near, object oriented Data model

SIMG XSWI SIMG TCTR PTRC PTOC

CSWI CSWI TVTR

Primary Technology (Switchgear)

Secondary Technology (Substation Automation)

Naming and Groups of Logical Node (First letter listed)

M Metering and measurement (8)

A Automatic control (4)

PDIF: Differential protection

CSWI: Switch controller

XCBR: Circuit breaker

YPTR: Power transformer

ABB Group July 26, 2012 | Slide 13

Introduction of Logical nodes: Functional view

Functions are not standardized ?

Introduction of Logical nodes: Data view

Exchanged Data in Substation Automation System

Allocation of LNs to devices (IEDs)

Device Example: Station Workplace

Device Example: Combined Protection and Control Unit

TCTR Device Example: Circuit Breaker

Device Example: Combisensor

ABB Group July 26, 2012 | Slide 16

Allocation of LNs to devices (IEDs)

Device Example: Station Workplace

Control Unit CSWI