h5 brunner 61850 intro

© C

opyr

ight

200

2 AB

B.Al

l rig

hts

rese

rved

. -1

-10

/3/2

003

IEC 61850 Object Model and Configuration Language

Christoph BrunnerABB Switzerland Ltd

© C

opyr

ight

200

2 AB

B -2

-

Contents

The object model defined in IEC 61850-7-3 and 61850-7-4The communication services defined in IEC 61850-7-2The XML based substation configuration language defined in IEC 61850-6

© C

opyr

ight

200

2 AB

B -3

-

Logical nodes represent the core functions

Primary technology Secondary technology

PTOC

XSWI

XSWI

SIMG

XCBRSIMG

PTRCCSWI

CSWI

CSWI

© C

opyr

ight

200

2 AB

B -4

-

Logical nodes and devices

Physical Device PISA_Q0_L3

Logical Device Q0_L3/

Logical Node XCBR

Logical Node LN0

Logical Device B_L3/

Logical Node B0_SIMG

Logical Node LN0

Logical Node B1_SIMG

© C

opyr

ight

200

2 AB

B -5

-

Specializations of LN and Data Classes

LOGICAL-NODE

DATA

61850-7-2

DPC

ISI

..

.61850-7-3

XCBR

MMXU

..

.

61850-7-4

compatibledata classes

common data classes

compatibleLN classes

...

EEHealth

Pos

...

..

.

..

.

© C

opyr

ight

200

2 AB

B -6

-

Logical node groups

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)

Examples:PDIF: Differential protectionRBRF: Breaker failureXCBR: Circuit breaker

CSWI: Switch controllerMMXU: Measurement unitYPTR: Power transformer

© C

opyr

ight

200

2 AB

B -7

-

Example of a logical node: XCBR

Attribute Name

Attribute Type

Mode INCHealth ISINamPlt LPLLoc SPSEEHealth ISIEEName DPLOpCnt ISI

Common LN Information

Pos DPCBlkOpn SPCBlkCls SPCChaMotEna SPC

Controls

CBOpCap ISIPOWCap ISIMaxOpCap ISI

Status Information

© C

opyr

ight

200

2 AB

B -8

-

Common data classes

Status information (7)Measured information (9)Controllable status (5)Controllable analogue (1)

Status settings (2)Analogue settings (2)Description information (3)

Examples:SPS: Single point statusACT: Protection activation informationMV: Measured valueWYE: 3 Phase measured valueDPC: Double point controlSPG: single point settingDPL: Device nameplate

© C

opyr

ight

200

2 AB

B -9

-

Example of common data class: MV

Attribute Name

Attribute Type

instMag AnalogValuemag AnalogValuerange ENUMERATEDq Qualityt TimeStamp

Measured values

i INT32f FLOAT32

scaleFactoroffsetdb INT32U

zeroDb INT32UsVC ScaledValueConfigrangeC RangeConfigd Visible String255

Configuration and description

subEna BOOLEANsubMag AnalogValuesubQ QualitysubID Visible String64

Substitution

© C

opyr

ight

200

2 AB

B -1

0 -

Device modeling example: Busbar Protection

Logical Device “Busbar Protection”

Breakers belonging to the zone decided based on switch positions

LN PTRC LN PTRC LN PTRC

One Instance per breaker

Trip L1, L2, L3

LN PDIFLN PDIFLN PDIF

One Instance per zone

started, operated

© C

opyr

ight

200

2 AB

B -1

1 -

Contents

The object model defined in IEC 61850-7-3 and 61850-7-4The communication services defined in IEC 61850-7-2The XML based substation configuration language defined in IEC 61850-6

© C

opyr

ight

200

2 AB

B -1

2 -

Communication protocols

Network independent

Interface

Network independent

InterfaceACSIAbstract Comm.Service Interface

Specific InterfaceSpecific Interface

Layer 1..6

Application Layer 7

Specific Comm. Service MappingSpecific Comm. Service Mapping

ApplicationProcess

SCSM 1 SCSM 2 SCSM n

AL 1 AL 2 AL n

© C

opyr

ight

200

2 AB

B -1

3 -

Basic information model defined in 61850-7-2

DATA

DataAttribute

1..*1..*

1

LOGICAL-NODE

1..*1..*

1

LOGICAL-DEVICE

1..*1..*

1

SERVER

1..*1..*

1

ServicesGetXXXDirecxtoryGet/SetDataValuesGetDataDefinition

© C

opyr

ight

200

2 AB

B -1

4 -

Further service models defined in 61850-7-2

1..*

DataAttribute

LOGICAL-DEVICE

SERVERBUFFERED-REPORT-CTRL-BLOCK0..*

LOG0..1

LOG-CONTROL-BLOCK

0..*

1

0..*

0..*

SETTING-GROUP-CONTROL-Block0..1

GOOSE-CONTROL-BLOCK

0..1

GSSE-CONTROL-BLOCK0..1

MULTICAST-SAMPLED-VALUE-CTRL-B.

0..1

0..1

DataSet

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

0..*

1

1

1

1

1

1

11

11

1

1

0..*

1..*1

1

1

1..*

DATA

1

1..*

11

13

14

14

14

14

15

15

16

16

Substitution12

Control17

Time18

File20

6

8

9

10

10

LOGICAL-NODE

0..*

1

0..*

LLN0

UNICAST-SAMPLEDVALUE-CTRL-B.

UNBUFFERED-REPORT-CTRL-BLOCK

Control Blocks

1

© C

opyr

ight

200

2 AB

B -1

5 -

Handling of events in IEC 61850-7-2

Datase t

Reportcontrol

Reporthandle r

Eventmonitor

Da tase t

has association to

controls controls

eventReports

Get, Set Report control attribute valuesReporting

Logging

LogcontrolGet, Set Log control attribute values

Loghandler

Eventmonitorevent

controlscontrols

has association to

Log

Logentry

Query log (from m clients)

Realda ta

hasassociation to

Datase t

DO

DO

DO

DO

DO

DO

DO

DO

© C

opyr

ight

200

2 AB

B -1

6 -

The log class as defined in IEC 61850-7-2LOG class

Attribute name Attribute type FC Value/value range/explanation

LogName ObjectName Instance name of an instance of LOG

LogRef ObjectReference Path-name of an instance of LOG

OldEntrTm TimeStamp LG

NewEntrTm TimeStamp LG

OldEntr INT32U LG

NewEntr INT32U LG

Entry [1..n]

TimeOfEntry EntryTime

EntryID EntryID

EntryData [1..n]

DataRef ObjectReference

Value (*) (*) type(s) depend on the definition of common data classes in IEC 61850-7-3

ReasonCode TriggerConditions If reason-for-inclusion (=TRUE) in optFlds.ReasonCode general-interrogation shall never occur as TRUE.

ServicesQueryLogByTimeQueryLogAfterGetLogStatusValues

© C

opyr

ight

200

2 AB

B -1

7 -

Contents

The object model defined in IEC 61850-7-3 and 61850-7-4The communication services defined in IEC 61850-7-2The XML based substation configuration language defined in IEC 61850-6

© C

opyr

ight

200

2 AB

B -1

8 -

IED Engineering

ICD-File

Format: XML

IED Configuration Tool

Library

The IED capability description file (.icd) describes the capabilities and (optional) the preconfigured data model of the IED

logical devices, logical nodes, logical node typesdata setscontrol blocks

© C

opyr

ight

200

2 AB

B -1

9 -

Substation Modeling

SSD-File

Format: XML

System Specification Tool

Library

The system specification description file (.ssd) describes the single line diagram of the substation with the associated logical nodes

single line diagramlogical nodes, logical node types

© C

opyr

ight

200

2 AB

B -2

0 -

Substation EngineeringSSD-File

SCD-File

ICD-FileICD-File

ICD-FileICD-File

System Configuration Tool

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

single line diagramcommunication networkIED configurationsbinding information (e.g. trip matrix)

© C

opyr

ight

200

2 AB

B -2

1 -

IED configuration

SCD-File CID File

IED Configuration Tool

The configured IED description file (.cid) describes a instantiated IED with all configuration parameters relevant for that IEDIt is created by the IED configuration tool from the .scd file and includes the device specific configuration dataThe use of the .cid file to configure the IED is optional. As an alternate solution, a vendor specific file may be used

© C

opyr

ight

200

2 AB

B -2

2 -SCL object model (simplified)

Substation Voltage Level

Bay Equipment Subdevice / Phase

1 1 1 1

CBRDISVTR

Terminal

ConnectivityNode

1 0..5

1

1

Functional / Substation structureFunctional / Substation structure

1Product / IED structureProduct / IED structure

DataLDeviceServer111

IED LN

LNode0 ..*

111 1 1

LNTypeAssociation implemented by full name

1..* Client access points

0,1

AccessPoint1

Subnetwork

Clock

Router

11..*

0,1

0,1 Communication structureCommunication structure0,1

0,1

0..*

© C

opyr

ight

200

2 AB

B -2

3 -

Elements of the SCL File

Header<?xml version ="1.0"?><SCL xmlns="http://www.iec.ch/61850/2003/SCL" ...<Header id="Substation Atlanta" nameStructure = "IEDName"/>Substation Section<Substation name="Atlanta">

<Voltage Level name="D1" ><Voltage multiplier="k" unit="V">220</Voltage><Bay name="Q1">

<LNode lnInst="1" lnClass="PDIS"...><ConductingEquipment name="QA1" type="CBR">

<LNode lnInst="1" lnClass="CSWI"...><Terminal connectivityNode="Pt1">< Terminal connectivityNode ="Pt2">

</ConductingEquipment> ...

Header

Substation Section

Communication Section<Communication>

<Subnetwork ...><ConnectedAP iedName="E1Q1SB1" ...>

<Address><P type="IP">10.0.0.11</P>

</Address> ...

Communication Section

IED Section<IED name "E1Q1SB1">

<AccessPoint name="S1"><Server>

<LDevice inst="C1"><LN0 lnType="LN0" lnClass="LLN0" inst=""/><LN lnType="myRDRE" lnClass="RDRE" inst="1"/>

<DOI name="FltNum"><DAI name="stVal">

<Val>125</Val></DAI> ...

</LDevice> ...

IED SectionIED Section

Data Type Templates<LNodeType id="CTRa" lnClass="TCTR">

<DO name="Mode" type="myINC"/></LNodeType<DOType id="myINC" cdc="INC">

<DA name="ctlVal" fc="CO" bType="INT32"/></DOType><DAType id="myAnalogValue">

<BDA name="f" bType="FLOAT32"/></DAType> ...

Data Type Templates