IEC61850-Tutorialceb5.cepel.br/arquivos/eventos_setor/iec61850_tutoria.pdf · IEC 61850 Short Tutorial March2005 / Page 3 Market requirements Scope The standard structure Acceptance

IEC 61850 Short TutorialKlaus-Peter Brand

[email protected]

IEC 61850 Short Tutorial March2005 / Page 2

Market requirements

Scope

The standard structure

Acceptance

Approach

Logical Nodes and objects

Hierarchical data model

Services

SCL

Outlook

LecturerLecturer

Klaus-Peter BrandABB Switzerland LtdABB University Switzerland & ABB Power Technology Systems (Utility Automation)Member of TC 57 WG10Editor of IEC 61850-5Co-editor of IEC 61850-7-4 Co-editor of IEC 61850-10 Member of Group of Experts handling amendments, updates and extensions of IEC 61850 Liaison officer CIGRE SC B5 – IEC [email protected]


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Scope and SA structureScope and SA structure

Stationbus

Processbus

IEC 61850 means Serial Communication for all functions both between Station/Bay Level and Bay/Process Level

Stationgateway

Stationcomputer

HMIStationlevel

Control Protection Protection& Control

Control ProtectionBaylevel

Process Interface Process Interface Process InterfaceProcesslevel Switchgear/Switchyard

Cu wires


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Situation before IEC 61850Situation before IEC 61850

Protection1

Protection1

Protection2

Protection2

Station Gateway

CentralFunctions

HM I

Processinterface Processinterface Processinterface

��

��

��

��

MVB,CAN others

Protection& Control

Stationlevel

Baylevel

Processlevel


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Because of the• global, deregulated market• transnational business of utilities• international business of providers

one and only one global standardfor communication in substationsand beyond is needed

Market requirementMarket requirement


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Requirements and meaningRequirements and meaning

Free configuration The standard shall support different philosophiesand allow a free allocation of functions e.g. it must work equally well for centralized (RTU like) or decentralized (SCS like) systems.

Interoperability The ability for IED’s from one or several manufacturer to exchange information and usethe information for the their own functions.

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.


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

The response: IEC 61850 The response: IEC 61850 -- structure (1)structure (1)

Configuration

Part 6: Configuration Languagefor electricalSubstation IEDs

Part 1: Introduction andOverview

System Aspects

Part 2: Glossary

Part 3: General Requirements

Part 4: System and ProjectManagement

Part 5: Comm. Requirementfor Functions andDevice Models

IEC 61850IEC 61850--x x (x = (x = part numberpart number))

IEC 61850is readyfor use


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Part 10: Conformance Testing

Mapping to real Comm. Networks (SCSM)

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

Part 9-1: Sampled Values over Serial UnidirectionalMulti-drop Point-to-Point link

Part 9-2: Sampled values over ISO 8802-3

Testing

Part 7-3: Common Data Classes

Data Models

Part 7-4: Compatible Logical Node Classes and Data Classes

Part 7-1: Principles and Models

Abstract Communication Services

Part 7-2: Abstract Communication Services (ACSI)

IEC 61850IEC 61850--x x (x = (x = part numberpart number))

The response: IEC 61850 The response: IEC 61850 -- structure (2)structure (2)

IEC 61850

is ready

for use


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Acceptance by Suppliers: see exhibition at Cigre exhibition Paris 2004

Booth of IEC 61850 Users Group „UCA International“


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Acceptance by Suppliers: participation at the UCA International booth


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Acceptance by Customers: Acceptance by Customers: Pilot projectsPilot projects

Pilot projects have been started at the end of 2004

They are not part of the Tutorial

but will be reportedin the

Workshops or in the

Manufacturers’ Forum


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Approach and meaningApproach and meaning

Solution for standardization approach

DATA MODELObjectsService

ISO/OSIseven layer stack

7654321

APPLICATIONswitching devices

protection & controlcommands, events,

alarms,…

COMMUNICATIONmessages,

telegrams, frameson the wire

…

ApplicationDomain

Substation

CommunicationTechnology

Slow

Fast

Problem for standardization approach


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Introduction of Logical nodesIntroduction of Logical nodes

Communication relations in a Substation Automation System

� Information is exchanged between all devices (IED)which comprise the system

� More precisely, data are exchanged between thefunctions and sub-functions residing in the devices

� The smallest part of the function that exchanges datais called Logical Node (LN) in IEC 61850. The LNperforms some operations for the overall function

IED IEDLN LN


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Circuit BreakerQ0_L1/XCBR

Gas density mon.Q0_L1/SIMG Primary technology

Secondary technology

ControlQ0/CSWIQ8/CSWIQ9/CSWI

Bay-HMIIHMI

Distance Protection

PDIS

IsolatorQ9_L1/XSWI

Gas density mon.Q9_L1/SIMG

Earthing SwitchQ8_L1/XSWI

Gas density mon.Q8_L1/SIMG

Logical Nodes in the Language of Substation Engineers

Example GIS


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Logical Node Groups (First letter listed)Logical Node Groups (First letter listed)

L System LN (2)

P Protection (28)

R Protection related (10)

C Control (5)

G Generic (3)

I Interfacing and archiving (4)

A Automatic control (4)

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)

ExamplesPDIF: Differential protectionRBRF: Breaker failureXCBR: Circuit breaker

CSWI: Switch controllerMMXU: Measurement unitYPTR: Power transformer


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Data model: HierarchyData model: Hierarchy

Physical Device (IED)defined as Server

↑ Implementation

Logical Device (LD)

↑ Grouping

Logical Node (LN)Logical Node (LN)

Data (Object)

Data ↓

Attribute

Properties ↓

Value

Bay Unit

Control

CSWI CSWI Switch Control

Position

Control Valueoff/on

Status Valueintermediate/off/on/bad


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Common LLN0

ProtectionPTOC Str Op

LLN0

ControlCSWI Pos ctlVal stVal

LLN0

ControlSwitch Control

PositionControl ValueStatus Value

ProtectionOvercurrent

Start/Pick-upOperate/Trip

CommonLLN0

Name plate“Vendor etc.”

Data model: Hierarchical set of objectsData model: Hierarchical set of objects

Phy

sica

l Dev

ice

(Ser

ver)

Example: Modeling of a combinedExample: Modeling of a combinedControlControl--Protection deviceProtection device

See IEC 61850-7-1,2,3,4

Data container with related data


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook Device Example: Combisensor

Device Example: Combined Protection and Control Unit

Device Example: Circuit Breaker

Device Example: Station Workplace

XCBR(Circuit Breaker)

TCTR(Current Transformer)

TVTR(Voltage Transformer)

CSWI(Switch Controller)

PDIS(Distance Protection)

IHMI(Human Machine IF)

Benefits of modeling relationships between LNs


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Example for Logical Node: Example for Logical Node: LN XCBR out of IEC 61850LN XCBR out of IEC 61850--77--44

��

��

�� !� � �

��

�� !��"�#�� #�� !��$%&�

� � �� "�� #�$�� "�

�� %�� &� ��'��(��(��(��(��)�� '� �� !�

� "�

��*�� +�� ,(�&�� -�

�� $%�� +�� ,(�&��&�� -�

-&�� -&� ��(�� "�

��

%�� '�� '��&�� "�

./-&�� %�� .��/��&�� "�

./�� %�� .��/�� "�

��"�� %�� -�

��!�(��

�(��'01�� .�1� �(��'��0�&� ��)� �� -�

)��"�#��

�.-&��&� �� (�� /� ��&� ��&��#� � "�

%-2��&� �� %��-��2�3��'��&��#� � -�

"�+-&��&� �� (�� /� ��&� ��&��#�'��(#�� -�


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Example for Common Data Class Example for Common Data Class DPCDPC

Attribute Name

Attribute Type

ctlVal BOOLEANoperTm TimeStampstVal CODED ENUMq Qualityt TimeStamp

Control and status

pulseConfig PulseConfigctlModel CtlModelssboTimeout INT32UsboClass SboClassesd Visible String255

Configuration and description

subEna BOOLEANsubVal CODED ENUMsubQ QualitysubID Visible String64

Substitution

intermediate/off/on/bad

off/on


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

'�")��

��

�� !4� � �

��

�� !��"�#�� #�� !��$%&�

� � �� "�� #�$�� 4� � "�

-&��1�� 1��&� ��(�� -�

)��"�#��

�� 0�$� �� "�

-&� 0�5� -&� �� 5� "�

)��

%�1�� 0�6� %�� 1�� "�� -�

%�� 0�6� %�� 7�(�� -�

6�� 0�6� 6 �(�� 7�(�� -�

$� "�� 6� $� ��"�� -�

%��1�� 0�6� %� ��1�� -�

-�� 0�6� -�� -�

%��-�� 0�6� %� ��-�� -�

1�� 0�6�� 1��3�� -�

0�� 0�6� 0�� -�

more …

Example for Logical Node: Example for Logical Node: LN PDIS out of IEC 61850LN PDIS out of IEC 61850--77--44


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Common data classes (CDC)Common data classes (CDC)

Status information (7)

Measured information (9)

Controllable status (5)

Controllable analogue (1)

Status settings (2)

Analogue settings (2)

Description information (3)

ExamplesSPS: Single point statusACT: Protection activation

informationMV: Measured valueWYE: 3 Phase measured value

DPC: Double point controlSPG: single point settingDPL: Device nameplate


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

ServicesServices

� 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 (SAV)

StandardizedStandardized data accessdata access and and transfertransfer (Services)(Services)


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

IEC 61850: Details for Communication services IEC 61850: Details for Communication services

Client Server Communication

Sampled Values

Data Model (Objects,Services)

Ethernet Link Layer

Ethernet Physical Layer with Priority tagging (100 Mbit/s)

Real timeCommunication

IP

TCP

MMS

� Stack selection according to the state-of-the-artCommunication technology

Mapping

GOOSE*

� SA specific data modelevolves slowly

� Communication technologychanges quickly

� Splitting of SA specificdata model fromcommunication technology

StackInterface

AbstractCommunicationServicesInterface (ACSI)

ISO/OSI – StackHierarchical set ofRules how information is coded for transmissionAccording to state-of-the art communication technology

� Model according to state-of-the-art SA technology

* Generic Object Oriented Substation Event


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Client-server communication and reporting

Client-server communication� using full seven layer stack� confirmed transmission layer � very reliable� relatively time consuming. Therefore, the client-server communication is not suited for time-critical data transmission but very well for the communication with an operator having a response time of the order of 1 s.

The client� asks the server for information.� changes by parameter setting the behavior of the server� issues commands via the server e.g. to switchgear� configures at the server conditions which allow the server to send a � report automatically to the client (report control block)The content of the report is defined by a data set. In contrast to master-slavemulitiple client-server links are possible.

The server� is the source of all data for the client


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Time critical communication with GOOSE Time critical communication with GOOSE

time

Data change GOOSE messages starts immediately with the changed values in some short repetition intervals (Tmin), then the interval will be increase (fast or slowly) to Tmax

Tmax = 1024 ms

Tmax = 1024 ms

b

Tmax = 1024 ms

Tmin = 2 ms

time

No data change

GOOSE messages (content defined by data set) are repeated with maximum interval Tmax

Tmax = 1024 ms Tmax = 1024 ms

Problem for real-time data:- No time for acknowledgement- No time for repetition after loss detected


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Time critical data flow with SV (sample values)Time critical data flow with SV (sample values)

Problem for real-time data:- No time for acknowledgement- No time for repetition after loss detected

Benefit for samples:Some few samples may be lost without impact on the function to be performed

� Sampled values (SV) messages are very similar to GOOSE messages:

� SV messages are defined with help of data sets; the start event is a continuous clocks pulse

� The problem is the high synchronicity requested for phasors (about 1 µµµµs);this problem has to be solved by time pulses for the time being.

� An extensions for time synchronization over the bus according to IEEE 1588is not yet included but in preparation for IEC 61850


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

Substation Configuration description Language (SCL)Substation Configuration description Language (SCL)

� To provide interoperability a formal description of the Substation Automation System with all communication links is needed

� All IED capabilities have to be described formally in an unambiguous way

� All communication services applicable have to be described formally in an unambiguous way

� The relationship between the switchgear (single line) and the data of the substation automation system have to be described formally in an unambiguous way

Formal description of device and system structure


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

BU 1 BU 2 BU 3 BU 4

HMI GW

Topics of SCLTopics of SCL

Data model (server side) with services: IED capability description

Instantiable types of LNs (LN Type), Data objects (DO types), Data attributes (DA types)

What inputs, e.g. GOOSE messages belong to an IED? Input section !

Data sets and control blocks for report and GOOSE messages

Access points for LAN connection

Allocation to Single line diagram

Description of Single line diagram


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

For the formal description is provided by theSubstation Configuration description Language (SCL)Substation Configuration description Language (SCL)

� based on XML� defined in part 6 of the standard (IEC 61850-6)usable for� IED Capability Description (ICD) files� System Configuration Description (SCD) file� System functional specification (SSD)and more

The engineering information is exchangeable between tools !!!

See IEC 61850-6

SCL: Formal description of device and system structureSCL: Formal description of device and system structure


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

System specification description (SSD) file

SystemDocumentation

files

Dev

ice

Sel

ectio

n

Systemconfigurator

Single LineDiagram(S/S spec)

Feeder Block Diagram(function spec)

Device (IED)

System Configuration

Description (SCD) file

IED Capability De-scription (ICD) file

Device specific

tool

SCD file part per

IED

SCL files

The Engineering Process with SCLThe Engineering Process with SCL


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

BU 1 BU 2 BU 3 BU 4

HMI GW

Design exampleDesign example

EthernetSwitch

EthernetRing

Bay Control and/or Protection Unit


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

IEC 61850: What is standardized and what not ?IEC 61850: What is standardized and what not ?

Standardized

� Data model with LN, DO, Attributes� Services� Configuration Language (SCL)� ICD file (requested) and other SCL based files

Not standardized

� LD and high plant identification� Functions � Allocation of functions to IEDs� SA concepts and architectures� Redundancy� Tools and engineering process


Market requirements

Scope


Acceptance

Approach



Services

SCL

Outlook

FutureFuture

� Maintenance of IEC 61850 within substations � Work started to use use IEC 61850 also outside the substation, i.e.

� for wind power, � for hydro power, � for distributed energy resources (DER)

� The feasibility of IEC 61850 for the link to the NCC has been proven, a harmonization between the data model of IEC 61850 and the CIM model on Network Level is in progress

� New work items to use IEC 61850 for line protection (teleprotection) are in preparation.

� The IEC TC57 WG10 takes care to the common data model� The user group UCA International promotes the standard and

tries to support all users.

� The goal is a seamless communication architecture for utilities

Activities

Documents

IEC61850-Tutorialceb5.cepel.br/arquivos/eventos_setor/iec61850_tutoria.pdf · IEC 61850 Short Tutorial March2005 / Page 3 Market requirements Scope The standard structure Acceptance