Escolar Documentos
Profissional Documentos
Cultura Documentos
Short Tutorial
Klaus-Peter Brand
klaus-peter.brand@ch.abb.com
Lecturer
Scope
Market Klaus-Peter Brand
requirements
ABB Switzerland Ltd
The standard ABB University Switzerland & ABB Power
structure
Technology Systems (Utility Automation)
Acceptance Member of TC 57 WG10
Approach Editor of IEC 61850-5
Logical Nodes
Co-editor of IEC 61850-7-4
and objects Co-editor of IEC 61850-10
Hierarchical
Member of Group of Experts handling amendments,
data model updates and extensions of IEC 61850
Services Liaison officer CIGRE SC B5 – IEC TC57
SCL klaus-peter.brand@ch.abb.com
Outlook
Acceptance
Station
Approach bus
Logical Nodes Bay
and objects Control Protection Protection Control Protection
level & Control
Hierarchical
Process
data model Cu wires
bus
Services Process Interface Process Interface Process Interface
Process
SCL
level Switchgear/Switchyard
Outlook
Scope
Market
requirements
Station HM I Central Station
The standard level Gateway
Functions
structure
Acceptance
Approach
Scope
Market
requirements
The standard
structure Because of the
Acceptance • global, deregulated market
Approach • transnational business of utilities
Logical Nodes • international business of providers
and objects
Hierarchical
data model one and only one global standard
Services for communication in substations
SCL and beyond is needed
Outlook
Scope
Interoperability The ability for IED’s from one or several
Market
requirements manufacturer to exchange information and use
the information for the their own functions.
The standard
structure
Hierarchical Long term stability The standard shall be future proof, i.e.
data model it must be able to follow the progress in
Services communication technology as well as
evolving system requirements.
SCL
Outlook
Scope
IEC 61850-x (x = part number)
Market
requirements
System Aspects Configuration
The standard
Part 1: Introduction and Part 6: Configuration Language
structure
Overview for electrical
Acceptance Substation IEDs
Part 2: Glossary
Approach
Part 3: General Requirements
Logical Nodes Part 4: System and Project
and objects Management IEC
is 618
Hierarchical Part 5: Comm. Requirement r 5
data model for Functions and for ead 0
Device Models us y
Services
e
SCL
Outlook
Scope
IEC 61850-x (x = part number)
Market
requirements
Abstract Communication Services Mapping to real Comm. Networks
The standard (SCSM)
Part 7-1: Principles and Models
structure
Part 7-2: Abstract Communication Part 8-1: Mapping to MMS and
Services (ACSI) to ISO/IEC 8802-3
Acceptance
Data Models Part 9-1: Sampled Values over
Approach Serial Unidirectional
Part 7-3: Common Data Classes Multi-drop Point-to-Point link
Logical Nodes
and objects Part 9-2: Sampled values
Part 7-4: Compatible Logical Node
Classes and Data Classes over ISO 8802-3
Hierarchical
data model Testing
The standard
structure
Acceptance
Approach
Logical Nodes
and objects
Hierarchical
data model
Services
SCL
Outlook
Scope
Market
requirements
The standard
structure
Acceptance
Approach
Logical Nodes
and objects
Hierarchical
data model
Services
SCL
Outlook
Scope
Market
Pilot projects have been started at
requirements the end of 2004
The standard
structure
Acceptance
They are not part of the
Approach Tutorial
Logical Nodes but will be reported
and objects
in the
Hierarchical
data model Workshops
Services or in the
SCL Manufacturers’ Forum
Outlook
Approach
Logical Nodes
and objects
COMMUNICATION ISO/OSI 7
Hierarchical messages, 6
data model seven
telegrams, frames 5
layer
on the wire 4
Services …
stack 3
Communication 2
SCL Fast Technology 1
Outlook
Services
IED IED
SCL LN LN
Outlook
Logical Nodes
and objects
Examples
Hierarchical PDIF: Differential protection CSWI: Switch controller
data model RBRF: Breaker failure MMXU: Measurement unit
Services XCBR: Circuit breaker YPTR: Power transformer
SCL
Outlook
Hierarchical Properties ↓
data model
Attribute Control Value
Services off/on
Value Status Value
SCL intermediate/off/on/bad
Outlook
Scope
Data container with related data
Market Example: Modeling of a combined Common
requirements
Control-Protection device LLN0
Name plate
The standard
“Vendor etc.”
structure
Common LLN0
Physical Device (Server)
Acceptance Control
Switch Control
Approach Control LLN0
Position
Logical Nodes CSWI Pos ctlVal stVal Control Value
and objects Status Value
Hierarchical LLN0
Protection Protection
data model
PTOC Overcurrent
Services Str Op Start/Pick-up
Operate/Trip
SCL
Outlook
See IEC 61850-7-1,2,3,4
IEC 61850 Short Tutorial March2005 / Page 17
Benefits of modeling relationships between LNs
Acceptance
Device Example: Combined Protection and Control Unit
CSWI PDIS
Approach (Switch Controller) (Distance Protection)
Logical Nodes
and objects
TVTR
Hierarchical
XCBR (Voltage Transformer)
data model
(Circuit Breaker)
Services TCTR
(Current Transformer)
SCL Device Example:
Circuit Breaker Device Example: Combisensor
Outlook
Scope
!
Market
requirements ! "# # ! $
%&
" #$ "
The standard % & ' ( ( ( ( ) "
' !
structure * + ,(& -
$% + ,(& & -
Acceptance -& -& ( "
Outlook
Scope off/on
Attribute Attribute Type
Market Name
requirements Control and ctlVal BOOLEAN
intermediate/off/on/bad
status operTm TimeStamp
The standard
structure
stVal CODED ENUM
q Quality
Acceptance t TimeStamp
Approach pulseConfig PulseConfig
Configuration ctlModel CtlModels
Logical Nodes and description sboTimeout
and objects INT32U
sboClass SboClasses
Hierarchical d Visible String255
data model
subEna BOOLEAN
Services Substitution subVal CODED ENUM
SCL subQ Quality
Outlook
subID Visible String64
SCL more …
Outlook
Approach
Logical Nodes
and objects Examples
SPS: Single point status DPC: Double point control
Hierarchical SPG: single point setting
ACT: Protection activation
data model
information DPL: Device nameplate
Services MV: Measured value
SCL WYE: 3 Phase measured value
Outlook
Outlook
Client-server communication
Scope
using full seven layer stack
Market confirmed transmission layer
requirements very reliable
relatively time consuming.
The standard
structure Therefore, the client-server communication is not suited for time-critical
data transmission but very well for the communication with an operator
Acceptance having a response time of the order of 1 s.
Acceptance
Tmax = 1024 ms Tmax = 1024 ms time
Approach
Data change GOOSE messages starts immediately with the changed
Logical Nodes values in some short repetition intervals (Tmin), then the
and objects interval will be increase (fast or slowly) to Tmax
Hierarchical
b
data model
Services
Tmin = 2 ms time
SCL Tmax = 1024 ms
Outlook
Tmax = 1024 ms Tmax = 1024 ms
IEC 61850 Short Tutorial March2005 / Page 26
Time critical data flow with SV (sample values)
Approach Sampled values (SV) messages are very similar to GOOSE messages:
Hierarchical The problem is the high synchronicity requested for phasors (about 1 µs);
data model this problem has to be solved by time pulses for the time being.
Services An extensions for time synchronization over the bus according to IEEE 1588
is not yet included but in preparation for IEC 61850
SCL
Outlook
Scope
Formal description of device and system structure
Market
requirements
To provide interoperability a formal description of the
The standard Substation Automation System with all communication links is
structure needed
Acceptance
All IED capabilities have to be described formally in an
Approach unambiguous way
Logical Nodes
and objects All communication services applicable have to be described
formally in an unambiguous way
Hierarchical
data model
The relationship between the switchgear (single line) and
Services
the data of the substation automation system have to be
SCL described formally in an unambiguous way
Outlook
Scope HMI GW
Market
requirements
Description of Single line diagram
The standard
structure Allocation to Single line diagram
Approach What inputs, e.g. GOOSE messages belong to an IED? Input section !
Logical Nodes Data sets and control blocks for report and GOOSE messages
and objects Instantiable types of
LNs (LN Type), Data objects (DO types), Data attributes (DA types)
Hierarchical
data model
Data model (server side) with services: IED capability description
Services
SCL BU 1 BU 2 BU 3 BU 4
Outlook
Scope
For the formal description is provided by the
Market
requirements Substation Configuration description Language (SCL)
The standard
structure
based on XML
defined in part 6 of the standard (IEC 61850-6)
Acceptance usable for
Approach IED Capability Description (ICD) files
System Configuration Description (SCD) file
Logical Nodes
and objects System functional specification (SSD)
and more
Hierarchical
data model
The engineering information is exchangeable
Services
between tools !!!
SCL
Outlook
See IEC 61850-6
IEC 61850 Short Tutorial March2005 / Page 30
The Engineering Process with SCL
SCD file
Scope Device
part per
Market Device (IED) IED specific
requirements tool
Device Selection
The standard IED Capability De-
structure scription (ICD) file
The standard
structure
Ethernet
Acceptance
Switch
Approach
Logical Nodes
and objects
Hierarchical
data model
Services
BU 1 BU 2 BU 3 BU 4
SCL
Outlook Bay Control and/or
Protection Unit
IEC 61850 Short Tutorial March2005 / Page 32
IEC 61850: What is standardized and what not ?
Scope
Standardized
Market
requirements
Data model with LN, DO, Attributes
The standard Services
structure Configuration Language (SCL)
Acceptance
ICD file (requested) and other SCL based files
Approach
Not standardized
Logical Nodes
and objects
LD and high plant identification
Hierarchical Functions
data model Allocation of functions to IEDs
Services SA concepts and architectures
Redundancy
SCL Tools and engineering process
Outlook