Basics of IEC61850 Standard

SUNDAYTUTORIAL: BasicsofIEC61850Standard
Sunday,October10th,1:00pm5:30pm IEC 61850 is a standard that is being used to make substation automation easier, save moneybyeliminationofsignificantamountofsubstationwiringandmakeinteroperability between relays manufactured by different vendors. The standard has its root in Europe and is spreading fast in other parts of the world. In USA the response has been cautious.Americanutilitiesareimplementingthisstandardonspecificstationstostudythe performanceandsavingsimpact.Hencethereisanunclearunderstandingofthisstandard intheUS. The intent of this tutorial is to introduce this standard to the engineers, managers and technicians representing various utilities. This session assumes that the audience knowledge of this standard is minimal to none. The tutorial will start with background informationandwillexplorethebasicsofthestandard.Itwillprovideageneraloverview of the various aspects of this standard including station bus details, GOOSE and GSE messaging,andabriefdescriptionofProcessBusimplementation. The implementation of this standard imposes new methods for testing relays that are compliantwiththisstandard.DetailsoftestingsuchrelaysandIEDs(IntelligentElectronic Devices)willbepresented. Afterattendingthistutorial,theaudiencewilltakeawayaverygoodconceptualknowledge oftheIEC61850standardwiththeadvantagesandchallengesposedinitsimplementation. Thistutorialwillbepresentedbythreespeakers; LarsFriskfromABB,RichHuntfromGE, andRalphMackiewiczfromSISCO,Inc. RalphMackiewiczofSISCO,Inc.willdiscussthefollowingtopicsdealingwithatechnical overviewoftheIEC61850Standard.Thiswillprovidebasicconceptsofthestandard neededbyengineers,managers,etc.whoareinvolvedwithsubstationequipmentin generalandautomationinparticular. TechnicalOverviewofIEC61850 1.IEC61850Summary 2.IEC61850LogicalDeviceStructure 3.IEC61850Services 4.SubstationConfigurationLanguage 5.Question/Answer RalphMackiewiczisVPofBusinessDevelopmentforSISCO,adeveloperof communicationsandintegrationproductsforelectricutilityapplicationslocatedinSterling Heights,Michigan.RalphhasaBSEEfromMichiganTechnologicalUniversityandwas engineeringmanagerforWestinghouseElectricCorporationpriortojoiningSISCOin1985. RalphhasbeenanactiveparticipantintheMMS,UCAandICCPTASE.2standardsactivities. Ralphhaspresentedtutorials,papers,andseminarsateventsandinpublications sponsoredbyIEEE,CIGR,Pennwell,EPRI,UCAInternationalUsersGroup,andothers. Ralphholdstwopatents,isamemberofIEEEandCIGR,andiscurrentlychairoftheUCA InternationalUsersGroupMarketingOversightSubcommittee.
Doble
RichHuntofGEwilldiscusstheProcessBusportionoftheIEC61850standard.Hewillgo intodetaileddiscussionaboutGEimplementationoftheProcessBus.Hewillalsodiscuss thebusinesscaseforsuchanimplementationandsomethoughtsoftestingprocessbus installation. IEC61850ProcessBusBusinessCase,ImplementationandTesting. 1. DefinitionofIEC61850ProcessBus 2. TheBusinessCaseforProcessBus 3. ConsiderationsforProcessBusInstallations 4. SomethoughtsontestingProcessBusinstallations 5. QuestionandAnswer RichHuntispresentlyaMarketDevelopmentLeaderforGEDigitalEnergy,responsiblefor HardFiber,theIEC61850ProcessBussolutionfromGE.Betweenutilitiesandvendors, Richhasover20yearsexperienceintheelectricutilityindustry.RichearnedtheBSEEand MSEEdegreesfromVirginiaTech,isaSeniorMemberofIEEE,thepastChairoftheSystems ProtectionSubcommitteeoftheIEEEPSRC,andisaregisteredProfessionalEngineer. LarsFriskofABBwilldiscussfield/practicalexamplesofIEC61850Solutions.Thiswill providetheaudiencewithclearexamplesofvariousapplicationsofthisstandardandhow thishas/willhelpsubstationautomation,communication,costsavingsandeasyduplication ofsystemdesign. FieldexamplesofIEC61850Solutions 1.PowerdistributionWherecanyoustart 2.TransmissionsubstationsCopperwire,howtogetridofit 3.LargesystemsHowtogobig 4.ProcessbusinstallationsAhighwayinyoursubstation 5.Q&A LarsFriskisApplicationSpecialistwiththeABBSubstationAutomationProductsteamin Burlington,Ontario.LarsistheABBNorthAmericanexpertonIEC61850andhasbeen instrumentalinimplementinganumberofprojectsintheUnitedStates,Canadaand Mexico. Hehaspublishedpapersthathavebeenpresentedatnumerousconferencesthroughout theUnitedStates.Larshas15yearsexperienceinhydropower,powerdistributionand substationautomationinSweden,IndiaandCanada. Mr.FriskholdsapatentonAutomatedGenerationofDisturbanceReports. HisstudiesfocusedonoperationsandmaintenanceinhydropoweratMidSweden University.
Doble
Systems Integration Specialists Company, Inc.
IEC 61850 618 0 T Technical h i l Summary
Ralph Mackiewicz SISCO, Inc. 6605 19 Mile Road Sterling Heights, MI 48314-1408 USA Tel: +1-586-254-0020 x103 Fax: +1-586-254-0053 Email: ralph@sisconet.com
Copyright 2010 SISCO, Inc.
Acronyms
Acronyms are unavoidable A id bl when h di discussing i communications and integration technology. It was our objective bj ti to t define d fi all ll acronyms before using them. If you are not t certain, t i please l ask k a question. ti
Ground Rules
Have a Question? Ask a Question As Needed! THERE WILL BE A TEST!!

3
Why Standards Are Needed
An Overview of IEC TC57 Standards
Interoperability
The ability of computer systems to exchange information with ith other th systems. t
Integration
The ability y of computer p based applications pp to interact with other systems in order to perform a useful function for the user.
Interoperability and Integration
Easy to Achieve:
Nearly anything is possible with enough money and development effort

6
A Better Way
z
Interoperability and Integration without having to create create, support support, maintain, improve, and fix it all yourself:
Where applications and devices are inherently capable of interoperating with other systems and performing integrated application functions in a cooperative and distributed manner.
This is only possible with Standards
This is the goal of the IEC TC57 standards
A Cautionary Note
z
Interoperability and Integration of applications is a path, not an end point. By the time we get to were we are going today, someone will have moved the goal. If you dont set out on the path, you will never make any progress. progress
International Electrotechnical Commission (IEC)

z
IEC is an international Standards Development Organization (SDO) with membership that is made up of national standards bodies of countries.
American National Standards Institute (ANSI) for USA
Standards jointly issued with International Organization for Standardization (ISO) IEC standards are inherently internationally focused versus other SDOs IEC standards from Technical Committee 57 (Power systems management and associated information exchange) have been the key foundation for many smart grid efforts.

125 existing publications 27 active projects
Key IEC TC57 Working Groups

z
WG 10 - Power system IED communication and associated data models
IEC 61850 Communications for power system automation
IEC TC88 IEC 61400 61400-25 25 series for IEC 61850 interfaces for wind power
WG 13 - Energy management system application program interface (EMS - API)
IEC 61970 Common Information Model (CIM) and Generic Interface Definition (GID) IEC 61968 CIM for f distribution di t ib ti and d model d ld driven i messaging i IEC 62351 Communications Security IEC 62325 CIM for energy markets IEC 61850-7-420 IEC 61850 for DER applications IEC 61850-7-410 IEC 61850 for Hydropower applications TC57 strategy and coordination CIM IEC 61850 Harmonization ICCP-TASE.2 Update
WG 14 - System interfaces for distribution management (SIDM)
WG 15 - Data and communication security
WG 16 - Deregulated energy market communications
WG 17 - Communications Systems for Distributed Energy Resources (DER)
WG 18 - Hydroelectric power plants - Communication for monitoring and control
WG 19 - Interoperability within TC 57 in the long term

10
What is IEC 61850?
Communications and Networks for Power Systems Automation
Traditional Protocol Standards

z
Specified how you arrange bytes on the wire in order to transfer bytes of data between a device and an application Good News: It worked! Device communications costs were lowered. Bad News: No standard for:
The meaning and organization of data. Configuration of devices. How devices should look and behave to network applications.
Some Level of Interoperability was achieved but not end-to-end Integration
12
IEC61850 is Different
z
IEC61850 is an object oriented substation automation standard that defines:
Standardized names Standardized meaning of data Standardized abstract services Standardized device behavior models Mapping of abstract services and models to specific protocol profiles for: Control and reporting Protection P t ti - GOOSE Transducers Process I/O
Companion Standards for:

13
Wind power Hydro power Distributed Energy Resources More likely
IEC 61850 Object Models

IED:Relay1/MMXU1.MX.A
Current Measurements
IED:Relay1/XCBR2.CO.Pos
Breaker Position Control
A PhV
Amps Volts
A PhV
Amps Volts
Pos
Position
Pos
Position
MX
DC
ST
Status
CO
Controls
Measurements Descriptions
Logical Nodes IEC 61850 Object Names Use Power System Context
MMXU1 Measurement Unit #1 XCBR2 Circuit Breaker #2
Logical Device (e g Relay1) (e.g.
Physical Device Named IED

(network address)
14
IEC 61850s Original Design Purpose Substation Automation
15
Smart Grid Application of IEC 61850 Wide Area Phasor Measurements and Protection
16
Smart Grid Application of IEC 61850 SCADA communications
17
Smart Grid Application of IEC 61850 Distributed Energy Resources
18
Smart Grid Application of IEC 61850 Impact on Meter Models
19
Long Term Impact of IEC 61850 Communications for Power System Automation
20
New IEC 61850 Activities

z
IEC 61850-80-1 Gateway mapping to IEC 60870-5-101/104 (DNP3) IEC 61850-90-1 Use of IEC 61850 for Communications Between S b t ti Substations IEC 61850-90-2 Use of IEC 61850 for SCADA Communications IEC 61850-90-5 Use of IEC 61850 for Synchrophasor Communications (GOOSE and Sampled Values (process bus) over UDP/IP) Edition 2 of IEC 61850 Update to the standard including some fixes fixes, clarifications, improvements, and more consistency.
21
Common Information Model (CIM) is an object object-
oriented information model of the power system
Central Generating Station
Step-Up Transformer
Distribution Receiving Gas Substation Turbine Station

Microturbine Recip Engine Photo voltaics Cogeneration
Distribution Substation
Recip Engine
Distribution Substation
Fuel cell
Commercial
Batteries Industrial Residential Commercial
Flywheel
UML Unified Modeling Language
22
CIM Packages
IEC 61970 from IEC TC57 WG13
Core SCADA
Load
Protection Financial
Assets
DocumenDocumen tation
Outage
Wires
Energy Scheduling
Consumer
Core2
Generation
Measurements
Reservation
ERP
OAG
Domain
Topology
Market Operations
Distribution
23
EMS, Transmission & Planning
Markets (Euro & NA)

How is CIM Used?

z
Power System Model Exchange between neighboring utilities and ISO/RTOs Definition D fi iti of fM Messages f for exchange h over an E Enterprise t i S Service i B Bus (ESB) using web services and a Service Oriented Architecture (SOA) Common Data Exchange g Model for Application pp Integration g using g modelaware, model-independent interface services
Generic Interface Definition (GID) and OPC Unified Architecture (UA)
A common semantic model for f integration of f disparate systems
It is the binding element of most of the NIST Smart Grid Interoperability Road Map standards.
24
CIM versus IEC 61850: What they define

CIM
z z z z z z z z z z z
IEC 61850
z z z z
Detailed Power System Topology Asset Model Consumer and load models Financial Scheduling and transactions M k t operations Market ti Work management SCADA and Measurements GIS Location Business Messaging (WG14) Interface Services (GID)
Power System Topology Model Device Configuration Description Device Models Service Models
Reporting Controls Protection

z z z
Performance/Requirements Object and Data Naming Conventions Protocols
25
CIM versus IEC 61850: What they define

CIM
z z z z z z z z z z z z
IEC 61850
z z z z z
Detailed Power System Topology Use of Globally Unique IDs (GUID) Asset Model Consumer and load models Financial Scheduling g and transactions Market operations Work management SCADA and Measurements GIS Location Business Messaging (WG14) Interface Services (GID)
Power System Topology Model Use of names in topology model Device Configuration Description Device Models Service Models
Reporting Controls C t l Protection

z z z
Performance/Requirements Object and Data Naming Conventions Protocols
26
CIM Asset-Power System Models & IEC 61850 Device Models

IEC61970/68 CIM
Power System Models Asset, g, trading, etc.
IEC61850
Power System Models
WG19 Harmonization
Device Models
Measurements
27
CIM and IEC 61850 Difference in Topology
Are these the same objects?
IEC 61970-301 EMS Diagram IEC 61850-6-1 SCL Diagram

28
Integration of CIM IEC 61850

z
IEC TC57 WG19: Interoperability Within TC 57
IEC 61850 for communications CIM for modeling, g messages, g and enterprise p integration g
Integration of non-overlapping models into a single unified model
IEC 61850 package for IEC 61970
Rules and procedures for transforming overlapping models when needed.
Convert from one model form to another to suit the application Modifications needed to the standards to support this.
29
DNP 3.0 and IEC 61850 Comparison
30
Evolution
100s of Proprietary Protocols 100s of Proprietary Protocols
EPRI UCA Architecture 1991 UCA2 0 UCA2.0 IEEE TR1550 1999
Mfg. Auto. Protocol-MAP 1984
MMS ISO9506 1988
ICCP IEC60870-6 1996
IEC 61850 2003
100s of Proprietary p y Protocols
IEC60870-5 IEC TC57 1994
IEC TC57 Substation Protocol Update 1995
DNP3 Serial Links 1993
DNP3 Ethernet ~2000
31
Comparison of Roots
z
DNP3 addressed North American requirements from IEC60870-5 work.
IEC61850 addressed European requirements from UCA2.0 work. work
32
Comparison of Roots
z
IEC61850 was developed for LAN/WAN Exclusively
UCA2.0 included profiles for serial links but not IEC 61850
DNP3 was developed for serial links and profiles were added later to run the protocol over LAN/WAN.
33
Comparison of Roots
z
DNP3 has roots in the RTU world where byte efficiency for low-speed links was important.
IEC61850 has roots in the LAN/WAN world where independence from the organization and storage of bytes was important.
34
Impact of Roots
z
DNP3 is very byte efficient optimized for low-bandwidth applications.
IEC61850 is feature rich with capabilities optimized for LAN/WAN based systems.
35
Impact of the Standard Structure
The DNP3 specifications look simpler.
IEC61850 defines more externally visible behavior for a device.
36
Service Comparison p
Service Description Read/Write Reporting Control (SBO and Direct) Enhanced Control (with Reports) Files p Start/Stop Event Logs Substitution (Forcing) Object Discovery Substation Configuration Language (XML) Protection Messaging (GOOSE) DNP3 YES YES YES * YES YES * YES Partial in future IEC61850
YES YES YES YES YES * YES YES YES YES YES
37
* Not in the standard, but can be implemented
Observation on Service Comparison
IEC61850 does have more services and options most notably:

Buffered reporting GOOSE (multi-cast protection messaging) Object j Discovery y Services Substation Configuration Language Sampled values for a process bus
Both B th DNP3 and d IEC61850 provide id sufficient ffi i t services i f for many applications.
38
Object Model Similarities

z
Both support discrete, digital, analog, counter, and floating point data types. B th support Both t pre-defined d fi d quality lit fl flags Both support time stamped data.
39
Object Models: DNP3

z
DNP3 Objects are described by:
Object #: 1=Binary Input Static, 2=Binary Input Event, etc. Variation #: 1=With status, 2 = without status, etc. Index #: Refers to a specific instance of an object.
40
Object Models: IEC 61850

A PhV
Amps Volts
A PhV
Amps Volts
Pos
Position
Pos
Position
MX
DC
ST
Status
CO
Controls

(network address)
41
Names v.s. Indexes

z
Names convey context and meaning improving understanding and reducing configuration. N Names need d more b bandwidth d idth t to communicate. i t
42
Conclusions
z
Both can be optimal for a given application depending on the requirements.
Both can be applied successfully in sub-optimal applications. Using one does not preclude the use of the other. Both can easily co-exist, AND PROBABLY SHOULD.
43
Benefits of IEC 61850
L Legacy SCADA Vi View of fD Data t
Applications
Flat set of f tags t
Applications Access Data by Tag
Device Addressing or SCADA Tag Data Base
45
Legacy View of Data

z
Proprietary tag formats. Arcane addressing:

Driver Wire Rack Device Register/Index # Network
Manually entered. Manually verified. Applications tied to tag or free form alias. Any user tag conventions are proprietary.
46
Typical Legacy Protocol Data Model

It is in: Obj t #6 Object #6, Variation #2, Index #27
Thats intuitive?
Device
47
I need d the h Ph Phase A voltage l for the 345KV primary feeder NO POWER SYSTEM CONTEXT FOR DATA ACCESS
Legacy Object Mapping

z
Legacy data objects must be manually mapped to power system for each different device, application, and vendor.
Legacy Device
R400040 R400041 Phase A Voltage R400042 R400043 R400044 R400045 Local/Remote Status R400046 R400047 R400048 R400049 R40004A R40004B
P Power S System t Functions F ti
Measurements
Phase B Voltage Phase C Voltage
Controls
Breaker Position Blocked Open Activate Phase A
Protection
Activate Phase B Activate Phase C
48
Behavior Modeling
z
Assume Index #25 is always used to store breaker status.

Does 1 mean open or closed? Can I write this object to operate the breaker? Where is the select? Is it selected?
Even if every device used Index #25 to hold breaker status this still isnt enough to provide end-to-end integration.
49
A New Approach Needed

z
For protocols to provide interoperability at the system level they need to:
Specify the bytes/format of the data on the wire Specify the meaning of data Specify the behavior of the data
50
IEC61850 is Different
z
IEC61850 is an object oriented substation automation standard that defines:
Standardized names Standardized meaning of data Standardized abstract services Standardized device behavior models Standardized mapping of services to protocols for:

Control SCADA Protection Transducers
Self-describing devices Common configuration language
51
Anatomy of an IEC61850 Object Model

A PhV
Amps Volts
A PhV
Amps Volts
Pos
Position
Pos
Position
MX
DC
ST
Status
CO
Controls

(network address)
52
IEC61850 View of Devices

B dX Brand
IOC Relay
B dY Brand
Diff Relay
PIOC
Measurements MMXU1
PDIF
Measurements MMXU1
ST
DC
DC
MX
ST
DC
DC
MX
Mod
Mod
PhV
PhV
Mod
Mod
PhV
PhV
MMXU1.MX.PhV MMXU1 MX PhV IEC61850 Name for Phase-to-Ground Voltage Measurements

53
IEC 61850 Object Mapping

z
NO MANUAL MAPPING NEEDED: IEC61850 objects already portray the power system context.
IEC61850 Device D i
LD
MX.A.PhsA.cVal.mag.f MMXU1 MX A PhsB cVal mag f MX.A.PhsB.cVal.mag.f MX.A.PhsC.cVal.mag.f ST.Loc.stVal XCBR1 ST.Pos.stVal ST BlkOpn stVal ST.BlkOpn.stVal ST.Op.phsA PIOC1 ST.Op.phsB ST.Op.phsC
54
IEC618 0 Vi IEC61850 View of fD Devices i

z
Only network addressing requires configuration in the remote client. Point names portray the meaning and hierarchy of the data with no mapping to I/O required. Point names can be retrieved from the device automatically without manual intervention or imported via SCL file. All devices share a common naming convention.
55
S b Substation i C Configuration fi i L Language (SCL)

(IEC 61850-6-1)
z
SCL Substation Configuration Language a standardized method of describing

Substation power systems D i configuration Device fi ti
SCL can be used to unambiguously describe user requirements for systems and devices. devices SCL can be used to configure applications without connecting to devices. devices SCL enables third party tools for configuration promoting choice and flexibility flexibility.
56
B Benefits fit
z
Reduced configuration costs:
Eliminates most manual configuration via automatic point name retrieval from devices Common naming and object models eliminates ambiguity and manual mapping of data points.
z z
Equipment migrations occur with minimal impact on applications. Application changes have minimal effect on devices, network or other applications. Users can specify equipment more precisely eliminating delays and costly rework. Adoption of IEC 1850 in the engineering process can significantly reduce the effort to design, test, and deploy substations.
57
IEC61850 Summary
IEC61850 Substation Architecture
GOOSE multicast and TCP/IP client/server communications
Station Bus
10/100/1000 MB Ethernet
Relay IED
Relay IED
Process Bus
Relay IED
Remote Remote Access Access
.1/1/10GB Ethernet
Network Network
Clk1 Clk1
MU MU
MU MU
MU MU
Clk2 Clk2
PT1 I/O Optical CT

59
PT2 I/O CT2

MU = Merging Unit
Optical I/O Optical PT CT

IEC 61850 Profiles
Today: SNTP Future: IEEE 1588
60
Two Party Application Association Client/Server

Used for read/write, reporting, controls (SBO), configuration, SCADA, etc.
Client
Maximum # of TPAA Supported
Client
Client
SERVER
From IEC61850-7-2
61
Multi-Cast Application Association

Generic Object Oriented Substation Event (GOOSE) is used to transmit a data set of status values to other relays for high-speed data exchange for protection messaging
Subscribing Application
Network A B B C C D
2 MCAAs 1 Service Access Point
Publishing SERVER
Publishing SERVER
Publishing SERVER
Service: send Data (unconfirmed)

62
Redundant Port Implementations

Redundant Port: 2 independent Ethernet ports with 2 different addresses MAC 1 IP Addr - 1 Ethernet1 Ethernet2 MAC 2 IP Addr - 2
Redundant Media: 1 Ethernet port with switched media MAC 1 IP Addr - 1 Ethernet Switches on loss of Ethernet pulses link p Primary Back-Up
Redundant Media is Common - Easy to Configure for Redundancy

63
Redundant Network Configuration
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet Card
WAN
WAN
Recent work involves putting 2 2-port port switches in the devices to form a ring for redundancy without switches
64
VLANs
z
VLANs: Are logical groupings of nodes that reside in a common broadcast domain Virtual because the VLAN is artificially created and the nodes need not be physically located on the same switch or even reside in the same building, but
Nodes that are members behave like they are connected together by one layer 2 bridge or switch A router is required to communicate between the two VLANs
E Segment 1 A B C D
VLAN 2 = Multicast domain ABE 65
VLAN 3 = Multicast domain CDFG
Ethernet Priority
Ethernet 802.1q provides a priority setting High priority messages are moved to the priority queue Specified S ifi d i in IEC GOOSE and dI Implemented l t di in switches it h
Ethernet Switch
Port 5
Port 6 Msg 1 New Msg 1 2 3 Msg 2 4 Msg g3 Msg 4 Port 4
Port 1
Port 2
Port 3
New New high priority message for Port 6

Courtesty of GE Multilin
66
IEC61850 St Standard d d
Basic principles Glossary General Requirements System and project management Communication requirements Substation Automation System Configuration Basic Communication Structure
Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7
Part 8
Mapping pp g to MMS and Ethernet
Sampled Values
Mapping to Ethernet
Part 9
Conformance testing g
Part 10
67
IEC61850 Layered L d St Standard d d

Device Object Models - IEC61850-7-3, 7-4
Abstract
Device Model
Data Objects
Data Types
Naming Conventions
Abstract Service Model - IEC61850-7-2

Associate Reporting Self-Description
Control
Data Set
Logs
M A P P I N G
Mapping to MMS Protocol - IEC61850-8-1
Write
VariableList
Real
Initiate
InfoReport InfoReport.
GetNameList
Journals
Communication Stack Profiles

ISO/OSI protocol stack TCP / IP protocol stack
68
IEC61850 Vi Virtual t lM Model d l
From IEC61850-7-1
69
IEC61850 Class Model in UML

Name ObjectName Obj tN ObjectReference SERVER
1 1..*
Contains LDs and files
Inheritance
Containment Heirarchy
LOGICAL-DEVICE (LD)
1 3..*
LOGICAL-NODE (LN)
1 1..*
Contains all other objects j
DATA
1 1..*
DataAttribute
70
UML Unified Modeling Language
Logical Device Structure
IEC61850 Clients
IEC61850 Server
Client Functions
Physical Device
1 to N Logical Devices Logical Device
Logical Device
Logical Node
...
Logical Node
Logical Node
...
Logical Node
Data Data
Data Data
Data Data
Data Data
Communications Driver
Process Bus
Field Signals
71
Legacy Device
Logical Node
A named grouping of data and associated services that is logically related to some power system function.
72
Examples of Logical Nodes

Circuit Breaker
Current T Transformer f Switch Controller Voltage Transformer
73
Common Data Classes (CDC)

z
Defines structure for common types that are used to describe data objects. CDC are complex l objects bj t b built ilt on predefined d fi d simple i l b base t types organized into functional constraints (FC) Examples: p

Single point status (SPS) on/off Double point status (DPS) on/off/transient
74
IEC 61850 TimeStamp Format

z
4 Bytes = Second Of Century (SOC) Starting January 1, 1970

Based on the Network Time Protocol (NTP) standard There are 31,536,000 seconds/year (non-leap) 4 bytes = 4 4, 294 294,967,296 967 296 counts do not wrap for 136 years or 2106
3 Bytes = Fraction of Second

16,777,216 counts about 60nsec potential resolution
1 Byte = Quality

1 bit : Leap Seconds not known 1 bit : Cl Clock k Failure F il 1 bit : Loss of Synchronization 5 bits: Number of significant bits in Fraction of Second (N)
75
IEC 61850 Quality

MSB 13 bit Bit-String, typically stored in a 16-bit integer LSB
9 10 11 12 13 14 15
OperatorBlocked p Test
Source = 0 Process = 1 Substituted
Inaccurate
Inconsistent Failure
OldData
BadReference
Oscillatory y OutofRange
Overflow
00 Good 01 Invalid 10 Reserved 11 Q Questionable ti bl
76
Common Data Classes

Name
SPS DPS INS ACT ACD SEC BCR MV CMV SAV WYE DEL SEQ HMV HWYE HDEL
Description
Single Point Status Double Point Status Integer Status Protection Activation Directional Protection Activation Info. Security Violation Counting Binary Counter Reading Measured Value Complex Measured Value Sampled Value Phase to ground measured values for 3-phase system Phase to phase measured values for 3-phase 3 phase system Sequence Harmonic value Harmonic value for WYE Harmonic value for DEL
77
Common Data Classes

Name
SPC DPC INC BSC ISC APC SPG ING ASG CURVE DPL LPL CSD
Description
Controllable Single g Point Controllable Double Point Controllable Integer Status Binary Controlled Step Position Info. Integer Controlled Step Position Info. Controllable Analogue Set Point Info. Single Point Setting Integer Status Setting Analogue Setting Setting Curve Device Name Plate Logical Node Name Plate Curve Shape Description
78
F Functional ti lC Constraints t i t
z
There are many data Th d t attributes tt ib t in i an object bj t like lik a b breaker k th that th have related use
Control, configuration, measurement, reporting, etc.
Functional Constraints (FC) is a property of a data attribute that characterizes the specific use of the attribute.
Useful to functionally organize the data attributes to provide structure and context.
79
Functional Constraints
FC Name
ST MX CO SP SV CF DC SG SE EX BR RP LG GO MS US XX
Description
Status Information Measurands (analog values) Control Set point Substituted Values Configuration Description Setting Group Setting Group Editable Extended Definition (naming read only) Buffered Report Unbuffered Report Logging GOOSE Control Multicast Sampled Value (9-2) Unicast Sampled Value (9-1) U d as wild Used ild card di in ACSI
80
Single Point Status (SPS)
From IEC61850-7-3
Attribute Name per clause 8 of f IEC61850-7-3 IEC61850 7 3
Type
Functional Constraint
Report Trigger Options
Mandatory/ Optional Range of Values
81
Logical Node Name Plate - LPL
From IEC61850-7-3
82
Device Name Plate - DPL
From IEC61850-7-3 IEC61850 7 3
83
Double Point Status (DPS)
From IEC61850-7-3
2-bit pair in DPS versus boolean in SPS

84
Integer Status - INS
From IEC61850-7-3
85
Controllable Double Point

Mandatory if control is supported
From IEC61850-7-3
Optional if control is supported
86
Logical Node
A named grouping of data and associated services that is logically related to some power system function.
87
IEC61850 Logical Node Groups

Name
Axxx Cxxx Gxxx Ixxx Lxxx Mxxx Pxxx Rxxx Sxxx Txxx Xxxx Yxxx Zxxx Wxxx Oxxx Hxxx Nxxx Bxxx Fxxx
Description
Automatic Control (4) Supervisory p y Control ( (5). ) Generic Functions (3). Interfacing/Archiving (4). System Logical Nodes (2). Metering g & Measurement ( (8). ) Protection (28). Protection Related (10). Sensors, Monitoring (4). Instrument Transformer (2). Switchgear (2). Power Transformer (4). Other Equipment (15). Wind (Set aside for other standards) Solar (Set aside for other standards) Hydropower (Set aside for other standards) Power Plant (Set aside for other standards) Battery (Set aside for other standards) Fuel Cells (Set aside for other standards)
88
System Logical Nodes
Name
LPHD LLNO
Description Physical Device Common Logical Node MANDATORY
89
Automatic Control Logical Nodes
Name
ANCR ARCO
Description
Neutral Current Regulator Reactive Power Control Automatic Tap Changer controller Voltage Control
ATCC AVCO
90
Supervisory Control Logical Nodes
Name
CALH CCGR CILO CPOW C O CSWI
Description
Alarm Handling Cooling Group Control Interlocking Point-on-wave o o a es switching c g Switch Controller
91
Generic Function Logical Nodes
Name
GAPC
Description
Generic Automatic Process Control
GGIO
Generic Process I/O
GSAL
Generic Security Application
92
Interfacing and Archiving Logical Nodes
Name
IARC IHMI ITCI ITMI
Description
Archiving Human Machine Interface Telecontrol Interface Telemonitoring Interface
93
Metering and Measurement Logical Nodes

Name
MDIF MHAI MHAN MMTR MMXN MMXU MSQI MSTA
Description
Differential measurements Harmonics or interharmonics Non phase related harmonics or interharmonics Metering Non phase related measurements Measurements Sequence and Imbalance Metering Statistics
94
Protection Logical Nodes

Name
PDIF PDIR PDIS PDOP PDUP PFRC PHAR PHIZ PIOC PMRI PMSS POPF PPAM
Description
Differential Direction Distance Directional overpower Directional underpower Rate of change of frequency Harmonic restraint Ground detector Instantaneous overcurrent Motor restart inhibition Motor starting time supervision Over power factor Phase angle measuring
95
Protection Logical Nodes (contd)

Name
PSCH PSDE PTEF PTOC PTOF PTOV PTRC PTTR PTUC PTUV PVOC PVPH PZSU
Description
Protection scheme Sensitive directional earth fault Transient earth fault Ti Time over current t Over frequency Over voltage Protection trip conditioning Thermal overload Under current Under voltage Voltage controlled time over current Volts per Hz Zero speed or under speed
96
Protection Related Logical Nodes

Name
RDRE RADR RBDR RDRS RBRF RDIR RFLO RPSB RREC RSYN
Description
Disturbance recorder function Disturbance recorder channel analogue Disturbance recorder channel binary Disturbance record handling Breaker failure Directional element Fault locator Power swing detection/blocking Auto reclosing y or synchronising y g Synchronism-check
97
Sensors and Monitoring Logical Nodes
Name
SARC SIMG SIML SPDC
Description Monitoring and diagnostics for arcs Insulation medium supervision Insulation medium supervision (liquid) Monitoring and diag. for partial discharges
98
Instrument Transformer Logical Nodes
Name
TCTR TVTR
Description
Current transformer Voltage transformer
99
Switchgear Logical Nodes
Name
XCBR XSWI
Description
Circuit Breaker Circuit Switch
100
Power Transformer Logical Nodes
Name
YEFN YLTC YPSH YPTR
Description
Earth fault neutralizer Tap changer Power shunt Power transformer
101
Other Power System Equipment Logical Nodes Name

ZAXN ZBAT ZBSH ZCAB ZCAP ZCON ZGEN ZGIL ZLIN ZMOT ZREA ZRRC ZSAR ZTCF ZTCR
Description
Auxiliary y network Battery Bushing Power cable Capacitor Bank Converter Generator Gas insulated line Power overhead line Motor Reactor Rotating reactive component Surge arrestor Thyristor controlled frequency converter Thyristor controlled reactive component
102
Logical Node Names

z
Example for Breaker:
ddd XCBR01
Logical Node Instance # Logical Node Name per IEC 61850-7-4 (circuit breaker)
Optional Application Specific Prefix
prefi digits + instance digits 7 prefix

103
L i lN Logical Node d Cl Classes

LN
LPHD
Common LN
Inherited Relationships
LLN0
Domain Specific LNs (i.e. XCBR)
An IEC 61850 device must contain LPHD LPHD, LLN0, and 1 or more domain specific logical nodes.
104
Common Logical Node Class
From IEC61850-7-4
ALL other logical nodes contain these attributes even though they are not t listed li t d i in th the other th l logical i l node d d description i ti t tables. bl
105
From IEC61850-7-4
NamPlt is mandatory and contains the nameplate for the individual logical node
106

From IEC61850-7-4
If the logical node is logically connected to some external equipment (e.g. breaker controller or server is a proxy, etc.) then EEName can contain the nameplate for that external e ternal de device. ice
107
LLN0 Containment
Containment Relationship
Inherited Relationship
From IEC61850-7-2
108
Logical g Node Description p - XCBR
From IEC61850 IEC61850-7-4 74
Loc
SPS
From IEC61850-7-4
Common Data Class Data Object Names 109
Mandatory/Optional Description
Single Point Status (SPS) CDC

(e.g. loc)
From IEC61850-7-3 stVal
Data Attribute Attrib te Names
Data Type of Attribute
110
Object Name for Local/Remote Attribute of XCBR1
XCBR1.ST.Loc.stVal
Attribute Data Functional Constraint L i lN Logical Node d
111
Mapping of Names via 8-1

z
Section 8-1 maps the IEC61850 LN and Data Object Names to MMS (ISO9506) MMS allows only numbers, letters, $, and _ in object names. Resulting MMS Object Name:
XCBR1$ST$Loc$stVal
112
Alternate Object Name Used
XCBR1.Loc.stVal[ST]
Attribute Functional Constraint
Data L i lN Logical Node d
113
Breaker Position
From IEC61850-7-4
Pos
DPC
From IEC61850-7-4
114
Breaker Position DPC Class

From IEC61850-7-3
stVal
115
Object Name for Breaker Position Attribute of XCBR1
XCBR1.ST.Pos.stVal
Attribute Data Functional Constraint L i lN Logical Node d
116
Report Model
Reporting
z
Unbuffered Reporting allows clients to receive data from the

server without polling.
If network connection (association) between client and server is lost, data is lost.
Buffered Reporting enables the server to retain data if

associations are lost enabling the client to retrieve ALL data. Reports are sent using the MMS InformationReport
Functionally equivalent to sending a Read response without the client g issued a Read request. q having
118
Report-Log Report Log Model
F From IEC61850-7-2 IEC61850 7 2
119
Report p Control Block Attributes

Attribute Name
RptID RptEna Resv DatSet ConfRev OptFlds sequence-number report-time-stamp reason-for-inclusion data-set-name data-reference buffer-overflow entry-ID conf-revision BufTim SqNum TrgOp data-change quality-change integrity general-interrogation IntPd GI PurgeBuf EntryID TimeOfEntry
Description
Name assigned to this RCB = 1 Reports enabled, = 0 Reports disabled = 1 In-use by client, =0 Available Name of the DATA DATA-SET SET reference Configuration Revision Number (can track Data Set changes) Optional Fields to Include in the Report Include the sequence number Include a report time stamp (even if DATA is time stamped) The reason the report was sent (dchg (dchg, qchg qchg, etc etc.) ) Include the DATA-SET name in the report Include the names of the DATA elements in the report Include buffer status in report (buffered only) Include the entry ID in the report (buffered only) Include the current value of the ConfRev in the report p Buffer Time (the fastest that reports will be sent) Sequence Number Trigger Conditions Send report on data change exceeding deadband Send report on change in quality Send report on integrity period expiration Send report when requested Integrity Period General Interrogation Purge the report buffer (buffered only) Start reporting from a specific entry in the buffer (buffered only) Start reporting from a specific entry time (buffered only)
120
Buffered Reporting with GI Example

Client enables BRCB report report p report report report report Communications Terminated
SqNum = 01, data change, <data> SqNum = 02, 02 data change, change <data> SqNum = 03, integrity, <data> SqNum = 04, data change, <data> SqNum q = 05, , data change, g , <data> SqNum = 06, integrity, <data>
Cli t request Client tG General-Interrogation lI t ti report report report report report report
SqNum = 07, data change, <data> SqNum = 08, data change, <data> S N SqNum = 09, 09 integrity, i t it <data> d t SqNum = 10, general-interrogation, <data> SqNum = 11, data change, <data> SqNum = 12, 12 data change, change <data>
SqNum = 10 flags when the GI was issued by the client to identify data that was reported while disconnected.
121
t time
IEC 61850 Client
Communications Reestablished Client Re-Enables the BRCB
Controls
Control Model Objects

z
Enables control of ACSI Objects:
Controllable Single Point (SPC) Controllable Double Point (DPC) ( ) Controllable Integer Status (INC) Binary Controlled Step Position (BSC) Integer Controlled Step Position (ISC) Controllable Analog Set Point (APC)
123
Control Model (ctlModel)

z
0: Status only. No control allowed. 1: Direct control with normal security (direct-operate) 2: SBO control with normal security (operate-once or operate-many) 3: Direct control with enhanced security y (direct-operate p ) 4: SBO control with enhanced security (operate-once or operate-many)
124
Direct Control with Normal Security
From IEC61850-7-2
125
SBO Control with Enhanced Security
Report_req(int)
From IEC61850-7-2 (modified)
126
Setting Groups
Setting Groups
z
Settings group is a logical element that is associated to all the settings in all the logical nodes within a logical device. A setting tti group is i referred f dt to by b a number b 1 1.n where h ni is th the number b of f setting groups supported. IEC 61850 clients use setting gg group p control blocks ( (SGCB) ) to access and manipulate the settings. 2 groups of settings:
S tti Groups Setting G (SG) th that t can b be selected l t d as th the active ti setting tti group Editable Setting Groups (SE) that can be selected and manipulated for editing.
128
Relay to Relay Applications
GOOSE Protection Messaging a.k.a. Peer-to-Peer messaging (misnomer Multicast messaging)

Legacy Hardwired Architecture

Breaker
Relay 2 1
Breaker
2 5 6 Relay 3 3 Relay 4 Hardwired signals for relay to relay links

Breaker Breaker
Relay 1 4
130
Legacy Architecture
z z z z
Requires N*(N-1)/2 links for N relays. Requires filtering on links to prevent false trips. Reprogramming can require rewiring. Dont know if links are working until you use them.
131
IEC61850 Network Architecture

Network Multicast Communications
GOOSE GOOS
Relay 1
Relay 2
Relay 3
Relay 4
Breaker
Breaker
Breaker
Breaker
GOOSE - Generic Object Oriented Substation Event (data sets)
132
IEC61850 Network Architecture

z
Relays R l share h a common network t k making ki sophisticated hi ti t d protection t ti schemes possible even across very large distances. Number of links for N relays is N and shared with SCADA. Relays send their status to all other relays at once using GOOSE GOOSE. Status exchanged continuously. Messages contain Time Allowed to Live parameter to detect missing messages messages.
133
GOOSE Traffic
Each line below represents a GOOSE message
State = 1, Seq = 0 St t = 2, State 2 Seq S =0 State = 1, Seq = 6
Event at t=0
Hold time increases from until steady state of ~1/min 1/min is reached
t State change occurs
134
Benefits
z
Reduction of wiring costs More flexible programming is independent of wiring Reliability: Link status known before use. New capabilities not cost-effective with hardwired systems. Higher performance with more data
~ 3ms for hundreds of points
135
Improved Performance
z
Network access resolves very fast
Duplex Ethernet switches NO collisions
Data is transmitted multiple times to avoid missing data.
Digital error checking instead of analog filtering.
Use of IEEE 802.1p with Virtual LAN (VLAN) for segmenting and priority tag processing by network switches.
136
GOOSE Wide Area Application
Wide Area Network
Application of VLAN and priority critical Substation-to-Substation IEC 61850-90-1 61850 90 1

137
Transducer Interfaces
Process Bus for transmitting sampled values
IEC61850 Substation Architecture
GOOSE multicast and TCP/IP client/server communications
Station Bus
10/100/1000 MB Ethernet
Relay(s) Subscribe to Datasets
Relay IED
Relay IED
Process Bus
Relay IED
Remote Remote Access Access
MU Publishes V/I/Status Datasets
.1/1/10GB Ethernet
Network Network
Clk1 Clk1
MU MU
MU MU
MU MU
Clk2 Clk2
PT1 I/O Optical CT

139
PT2 I/O CT2

MU = Merging Unit
Optical I/O Optical PT CT

Legacy Approach
Protection Relay
A/D
Voltages and currents
Bay Controller
A/D
A/D
Input
Breaker Status
A/D
Input
Breaker B k Status
140
Legacy Approach
z
Individually and redundantly wired to all devices needing the same signals:

CTs PTs Status Inputs Outputs p
Each individual sensor must be calibrated and maintained separately. Incremental cost is exponential (signals x devices) Result is minimization of I/O Analog signal wiring constraints
141
IEC61850 Process Bus

Bay Controller
Ethernet
Protection Relay y
Ethernet
Fault Recorder
Ethernet
RTU
Ethernet
9-2 Process Bus Ethernet
Merging Unit
A/D
A/D
Input
Breaker Status
142
IEC61850-9-2 Process Bus

z
Transducer and I/O signals are shared via a network. Only one transducer or I/O point per signal signal. Minimization of calibration and maintenance. Incremental cost is linear (signals only) CT/PT signals can be sent across long distances
143
What is a bus?
Bay Controller
Ethernet
Protection Relay y
Ethernet
Fault Recorder
Ethernet
RTU, etc.
Ethernet
9-2 Process Bus Ethernet
Merging Unit
A/D
A/D
Input
Breaker Status
144
What is a Bus?
Ethernet Switch
Ethernet Switch
Ethernet Switch
Ethernet
Merging Unit
A/D
A/D
I Input t
Breaker Status
145
What is a Bus?
Ethernet Switch
Ethernet Switch
Ethernet Switch
Process Bus
Ethernet
Merging Unit
A/D
A/D
I Input t
Breaker Status
146
New Development in Process Bus point-to-point!? point to point!?
Fiber Patch Panel

Fiber Optic Connector
Merging Unit or brick

A/D
A/D
I Input t
Breaker Status
147
Substation Configuration Language
SCL IEC61850-6
SCL Substation Configuration Language IEC61850-6-1

z
Description language for communication in electrical substations related to the IEDs.
XML based language that allows a formal description of
Substation automation system and the switchyard and the relation between them IED configuration Support for private extensions
149
SCL File Fil Types T

z
SSD: System Specification Description.
XML description of the entire system.
SCD: Substation Configuration g Description. p
XML description of a single substation.
CID: Configured IED Description.
XML configuration for a specific IED.
ICD: IED Capability Description.
XML description of what is supported by an IED (required for servers).
150
SCL Files
SSD File Entire System y SCD File #1 Single Substation Substation #1
CID File for IED #1 CID File for IED #2
CID File for IED #n-1
CID File for IED #n
CID File for IED #n-1
151
CID File for IED #n

SCD File #2 Single Substation Substation #n

CID File for IED #1 CID File for IED #2
ICD versus CID Files

z
ICD File What an IED is capable of CID Configuration for a specific IED
Substation specific configuration information
CID File = Subset of ICD File A t ll Used Actually U d + Substation S b t ti Specific Configuration Info. Subset:
Not all logical nodes, control blocks, I/O, etc. supported by the device are used in a system.
Substation Configuration Info:
Report control block presets Static values for location, and other descriptions.
152
SCL Driven Naming
153
Logical Device and LN Naming = IEDName
154
E Example l SCL B Based dO One-Line Li Di Diagram
Logical Node Designators
155
Example of SCL
SISCO IED For Demo
156
SCL Applications
z
For users to specify IED requirements. For vendors to specify IED capabilities. Configure IEC61850 clients w/o IEDs. Extract IED configuration g from p power system y design g tools. Export IED configuration to power system design tools and other applications.
157
A Shameless Plug
UCA International Users Group Users Group for IEC Standards

UCA C International Users G Group
Advancing Interoperability for the Utility Enterprise A non-profit users group http://www.ucaiug.org
159
UCA International Users Group

z
Certification of test procedures and systems

Educational seminars and conferences Help desk for user assistance G h i i Gathering input f for standards d d work k Promotional activities
160
Why Join?
z
Support rigorous testing that will lower your cost of ownership. Participate in the standards process without the cost of attending IEC meetings.
Access to IEC drafts via Liaison with IEC
Vote on key technical issues important to your organization. Learn from others through participation.
161
Who Needs to Join?

Every small utility using IEC61850 should have at least one individual member for access to information. Every large utility should be a corporate member to participate in and influence the standard and user group processes.
162
Were you paying attention?
A quick test before discussion
Heres the Test

z
Question #1:
The IEC 61850 set of standards specifies which of the following:
A. How data is stored in the memory of a device B. A configuration language for devices C. A single protocol for all IED communications D. An object model for how data in a device relates to the power system E. Reporting, controls, settings, and protection services and protocols F. How devices should be tested for conformance G. How an asset management system should be implemented
164
Heres the Test

z
Question #2
IEC 61850 specifies 2 kinds of reporting. Name them.
165
Discussion
! ! !
zzzzz
166
Thank You
Ralph Mackiewicz SISCO, Inc. 6605 19 Mile Road Sterling Heights, MI 48314-1408 USA Tel: +1-586-254-0020 x103 Fax: +1-586-254-0053 Email: ralph@sisconet.com
IEC 61850 Process Bus

Business Case, Implementation, and Testing Rich Hunt GE Digital Energy
2010 Doble Client Conference
Agenda Definition of IEC 61850 process bus The business case for process bus Considerations for process bus installations Some thoughts on testing process bus
Definition of IEC 61850 Process Bus
IEC 61850: a definition
IEC 61850 is not a protocol. It is a standard that describes a methodology of designing substations based on required functionality for operating the power system. 61850 defines the functions, the models, and the communications protocols required to achieve interoperability. The goal is reusable engineering based on standard, repeatable physical design.
Substation logical interfaces
Process bus definition Process bus interfaces: IF4: CT and VT instantaneous data exchange (especially samples) between process and bay level IF5: control-data exchange between process and bay level Process bus: When process bus is discussed, it usually means sampled values Original concept was to separate process bus and station bus networks due to bandwidth limitations
May still be a good idea for practical considerations
IEC 61850 9-2 Part 9-2: Specific Communication Service Mapping (SCSM) Sampled values over ISO/IEC 8802-3 Scope of 9-2: The intent of this SCSM definition is to supplement IEC 61850-9-1 to include the complete mapping of the sampled value model. This part of IEC 61850 applies to electronic current and voltage transformers (ECT and EVT having a digital output), merging units, and intelligent electronic devices for example protection units, bay controllers and meters. Process bus communication structures can be arranged in different ways as described in Annex B and IEC 61850-1.
Merging Unit
52
INPUTS ANALOG FILTER A/D CONVERTER Traditional Microprocessor Relay Front End DIGITAL FILTER MAGNITUDE ESTIMATOR
52
INPUTS ANALOG FILTER Merging Unit A/D CONVERTER DSP IEC 61850 9-2 SAV
IEC 61850 9-2 SAV
Power system signal Signal as measured by merging unit
Delay
Time
IEC 61850 9-2 SAV is some number of these samples packaged together
Process bus architecture
52
52
52
Process Interface Unit: - merging unit(s) - contact I/O
Process Bus Ethernet Network
10
Application needs for process bus IEC 61850, and Part 9-2, do not define: Process bus Ethernet network architecture
Intentional: this is an application issue
Merging unit sampling rate

IEC 61850 5 defines 480, 960, 1920 Hz for protection, 1500, 4000, 12000 Hz for metering
Specific SV data frames Frequency tracking Time synchronization method Also, the standard does not define why to use process bus
11
The business case for process bus
12
Enterprise Objectives
Financial Performance
Improve T&D capital utilization Reduced T&D operational & maintenance costs Example
Leverage highly integrated IEDs for significant savings from reduced wiring costs, number of devices Reducing labor required for infrastructure renewal & expansion Complete infrastructure projects faster faster ROI
Optimize shareholder investment

13
Changing Market Demands

Customer growth creating increased demand for energy Customers expect more reliable power Regulatory compliance influencing operational requirements Examples
Load growth requires increased capacity Increased customer sensitivity to service interruptions ISOs limiting the length of outages
Higher expectations require improved infrastructure

14
Workforce Utilization
Manpower is the largest P&C expense for switchyard expansion or refurbishment Workforce demographic resulting in a shortage of skilled labor Previous advancements in technology have not addressed workforce efficiency Example
Protection & Control material accounts for only 25% of total installed costs On-site labor for Protection & Control has changed little in 35 years
Improved workforce utilization 2010 Doble Client Conference
15
Technical Constraints
Designing-out copper wiring
Maximum pre-connectorization Early and comprehensive acquisition of signals Fiber-based signaling Ruggedness and security paramount Risk mitigation with built-in redundancy
16
Ready to use today and future-proof

Accepts reality of substation switchyards Open standard IEC 61850 Complete, simple and robust architecture Does not introduce new problems Respects the art of protection and control as practiced today
17
Labour & work transfer
Optimum partitioning for multiple suppliers Standardization of components and physical interfaces Minimum variability of material Minimum on-site labour and maximum quality control
18
Addressing the right problem A need for a technological solution that

Aligned with todays P&C practices Industry-wide acceptance IEC 61850 Delivers savings to the customer Replaces on-site labour with pre-fabricated material Facilitates transfer of work Increases key performance indices Complete and future-proof
Bringing industrial revolution to protection and control field

19
Process bus
A technical way of providing a mission-critical function of P&C, while meeting a business goal of designing out all copper signaling from a switchyard, to achieve considerable cost savings by simplification of engineering, drafting, construction, commissioning and ownership Business goal delivered in the simplest and safest way A fit-for-purpose architecture
20
Considerations for process bus installations
System design factors Measurement types Segmentation Performance Location Reliability Maintainability Interoperability
22
Measurement Requirements
Protection signals Sampled values, breaker status, breaker protection control Low latency High determinism Connection to few devices Operations signals V, I data, equipment status, equipment control High reliability Connection to many devices possible
23
4 control points 2 status points
Protection Measurements (V,I) Protection Status and Control
52
XX control points YY status points
Operations Measurements (V,I,P,E) Operations Status and Control
Segmentation
How to design the process bus network architecture Zone / bay architecture as shown Supports both point-topoint connections, and LAN connections Station-wide architecture LAN connections Choice is dependent on how many devices need access to data, how they are connected.
fiber to control house fiber to control house
52
to relays
as needed for I/O
All copper kept in line bay
PIU: MU and RIO
fiber to control house
24
Segmentation
Line protection zone Zone overlap Transformer protection zone Zone overlap
Line protection zone Observation: data only needed by 2-3 devices

25
Performance Requirements Synchronization between MUs and IEDs Zone-based Station wide External synchronization source or through the network Impact on relay operating speed Protection calculations, tripping speed Time delay relative to conventional devices Line differential relaying Response to lost SV message
26
Location
MUs, RIOs, PIUs placed where it makes sense to pick up signals Some can be centralized per zone, others may be distributed Yard vs. control house Control house is nonsensical Hardened devices for the yard
RIO RIO RIO RIO RIO RIO RIO RIO RIO RIO
to I/O network
RIO
RIO
to I/O network RIO
52
to I/O network
to relays
to I/O network to I/O network
RIO
RIO
RIO
RIO RIO
to I/O network
RIO
RIO RIO
27
Reliability Failure modes Loss of communications Loss of SV messages MU / PIU failure Clock failure Network equipment failure Redundancy MUs / PIUs Communications network equipment IEDs
28
Maintainability Training New skills (for P&C) for communications equipment, clock? Work procedures Documentation Testing Isolation for testing Testing tools and procedures Operations Maintenance, replacement on failure Expandability / Scalability Adding additional zones to process bus system
29
Interoperability
Option 1
52
Option 2
52
Option 1 is an unlikely scenario due to system availability requirements.
PIU A
PIU B
Relay A 1 PIU to 2 relays Option 3

52
Relay B
Relay A Relay B Duplicate or Redundant System: Each relay uses a PIU
More likely scenario. If PIU A and Relay A are from the same supplier, is there any need to interoperate with equipment from Supplier B?
For Option 3, only 1 PIU is required to maintain availability. The redundant system uses a different protection system, so a duplicate PIU will have little impact on protection system availability.
Relay A Relay B
Redundant Systems: 1 PIU
30
Interoperability
Does it matter? Redundant or duplicate process bus systems reduce the need for interoperability Benefits Future upgrades, changes to standard PIUs or IEDs, hot swappable SV measurements Risks Compatability glitches between equipment from different suppliers Customer assumes all risk of performance Issues IEDs from one supplier must accept SV data frames from MUs from a different supplier.
There are 2 different SV profiles currently in use
31
System Architecture
Physical interface for P&C is always the same: PIU connected to a fiber optic cable Cables can be point-to-point that land at patch panels, or LAN that land on switches.
PIUs PIUs
Outdoor multi-fiber Cables
Standard Ethernet Connectivity to SCADA & HMI IEDs, all I/O Via Fiber Cross-Connect Panels
32
Architecture comparison
Switched network Changes the P&C system into a LAN Measurement: latency and determinism impacted by network design Segmentation: zone based or station-wide Performance requirements: slower than conventional due to latency, risk of lost SV messages Location: PIUs in yard, switches in house Reliability: function of network design. Redundant networks or re-configuring ring. Redundant clock sources. Maintainability: Significant training of P&C personnel on communications equipment. Isolation for testing a concern. Scalability a factor of network design. Interoperability: high degree of interoperability required for successful implementation.
33
Architecture comparison Point-to-point network P&C system still a P&C system Measurement: low latency and highly deterministic Segmentation: zone based Performance requirements: comparable to conventional. Little risk of lost SV messages. Location: PIUs in yard, no other devices Reliability: Based on simple redundancy/duplication Maintainability: No training or special knowledge. Components easily replaceable. Simple isolation for test. Scalable. Interoperability: no special requirements.
34
Some thoughts on testing process bus
35
Reasons for Testing Verify that the protection and control systems are capable of correctly performing their intended functions: When initially placed in service (commissioned) When modifications are made - Firmware updates - Minor setting changes - Component replacements - System reconfiguration Periodically (to detect hidden failures) Troubleshooting
36
Conventional Protection
Test Switches
37
Process Bus Protection

High side PIUs
Protected Transformer
Low side PIUs
38
P&C System Testing - Overview

Zone of Verification
Relay
Tests
hardware, including I/O firmware settings
Traditional Methodology
isolate relay secondary ac injection (5A, 115/66.4V) short contact inputs monitor output contact continuity excitation check, ratio check force primary condition, monitor for continuity inject command, observe operation buzz wiring overall functional test
Process Bus Methodology

isolate relay optical ac injection (sampled values) optical contact input injection optical output (GOOSE) monitoring excitation check, optical ratio check (sampled values) force condition, monitor optical output inject optical (GOOSE) command, observe check packet S/Ns overall functional test
Primary Equipment
IT ratios and polarity condition sensing contacts breaker, disconnect, functionality
Interconnections
correct wiring
39
Process Bus System
Relay
40
Process Bus System
PIUs and associated primary equipment
Relay
41
Process Bus System
PIUs and associated primary equipment
Interconnections
Relay
42
Process Bus System

Overlapping zones: PIUs and associated primary equipment
Interconnections
Relay
43
Relay Testing Follow conventional strategy: Visual inspection Isolate relay under test Make any modifications or repairs required Inject signals representative of power system conditions Verify relay output signals (e.g. trip) are appropriate Restore relay to service after checking that it is safe to do so
44
PIU/Primary Equipment Testing Strategy: PIUs lumped with the associated primary equipment Equipment terminal points change from copper to fiber, otherwise same strategy as previous practices: Test from terminal points
P&C terminal point
Brick tester
45
872748A1.CDR
PIU Replacement PIU replacements are rare. For maximum worker safety, remove the primary equipment from service. Replacement PIU should be pre-tested before installation.
Brick tester
46
872748A1.CDR
PIU/IED Interconnection Testing

Establish that the fibers connect the relays to the correct PIUs, and that path losses leave adequate signal margin
Interconnections
Choice of network architecture determines degree, type of testing required

47
Test Switches Role of test switches:

Isolate the work space for personnel safety Maintain integrity of current signal paths Isolate the relay outputs to avoid inadvertent operations Facilitate secondary injection without affecting other devices Provide a convenient signal measuring facility
48
Testing - Summary
Process Bus is testable using accepted principles Uses overlapping test zones for full coverage Some architectures require new worker skills Fewer manual tests required Connectivity of all quantities on a fiber verified with a single test Switched LAN testing requires more (VLANs, failover, congestion) Less prone to human errors Test mode blocks and unblocks all relay outputs with a single action Self-testing of fiber connections, optical and electronic hardware Fewer manual tests required
49
Testing - Summary Enhanced personnel safety Reduced exposure to hazardous live electrical circuits (CTs, VTs, battery) Maintenance and periodic testing requirements relaxed due to unprecedented self-monitoring Outage-less routine maintenance run-to-fail with
50
Final Thoughts
51
Control Cables 1
Turn This
52
Process bus wiring
Into This
53
Close-up of Relay as Installed
Five copper connections, plus IRIG-B
Eight fiber connections, plus station LAN
And This
54
Quiz Questions
55
Quiz Questions What are the required number of measurements (currents and voltages), and the required number o measurement samples, in a IEC 61850 9-2 sampled value data set? Is a switched network (LAN) architecture required for IEC 61850 process bus communications?
56
Lars Frisk, Doble Austin TX, October 10 2010
Field Fi ld examples l of f IEC 61850 solutions l ti at have a e bee been do done e out t there ee - What
ABB Month DD, YYYY | Slide 1
Agenda
Background Distribution automation - Where can you start Transmission substations - Copper C wire, how to get rid of f it Large systems - How to go big Process bus installations - A highway in your substation Q&A
Background - why IEC 61850
Driving factors for IEC 61850 solutions

Cost reduction Smart grid enabling Future-proofing Increase reliability y Space saving Using new technology
Distribution automation
Distribution automation Protection and control applications
Circuit Breaker Failure Protection (CBFP) trip signal from all outgoing feeders to each corresponding incoming bay Under voltage and Under frequency trips from both Incoming feeders to all outgoing feeders, Truck positions, Parallel operation of the power transformers
IED
GOOSE
IED
Distribution automation Breaker failure scheme

OK, I hear you! Ill open my Breaker
Relay B (outgoing feeder) detects a fault, issues opening command to the breaker and starts the breaker failure The breaker in outgoing feeder fails to open and after a set time delay the breaker failure protection in Relay B sends out back-up command as a GOOSE message to Relay A After receiving the GOOSE message Relay A issues opening command to the incoming feeder breaker and the fault is cleared.
Relay A
GOOSE message
Relay B
My Breaker is not opening! Activate Breaker failure scheme

ABB Group Month DD, YYYY | Slide June 19, 2009 | Slide 6 6
Distribution automation Arc protection using GOOSE

3.
Both relay A (incoming feeder) and relay B (outgoing feeder) are equipped with three arc sensors Relay B detects an arc in the busbar compartment via sensor 1 and sends a related GOOSE message to relay A

Relay A
2. 1.
Conventional wiring: <37ms With GOOSE: <23ms
2. 1.
After receiving the GOOSE message relay A checks the current level and issues a trip command to breaker A -> GOOSE communication enables fast and station wide supervised arc protection schemes
GOOSE message
Relay B
3.
Distribution automation GOOSE based busbar protection
ABB Group Month DD, October 24,YYYY 2010 | Slide 8
Distribution automation GOOSE based busbar protection

Substation S
GOOSE Ethernet
Message Connection
automation system
Up
to 128
outgoing
feeders
Distribution automation IEC 62271-3 62271 3 Conformance testing with KEMA
Highlights confirmed by KEMA:
Distribution automation Simplifying wiring
Use case:
UniGear switchgear g with 10 bays y
Load management system, as well as control system interface
Fro om / to protec ction and control IEDs Number of IO wires I t b signalling Intebay i lli Automation system Other externals, i.e. load management system T t l Total 104 85 383 572 116 47 252 415 220 132 635 987 Fro om / to other r devices T Total
~70% of the LV signals are between the relays
Distribution automation Less wiring is more
Use case:
UniGear switchgear g with 10 bays y
Load management system, as well as control system interface
Fro om / to protec ction and control IEDs Number of IO wires I t b signalling Intebay i lli Automation system Other externals, i.e. load management system T t l Total 104 85 383 572 116 47 252 415 220 132 635 987 Fro om / to other r devices
~70% of the LV signals are between the relays
With GOOSE. GOOSE There Theres s a great potential to:

T Total
Simplify Make it more flexible Make it more extendible Make it more cost-efficient cost efficient Make it more reliable
Power Transmission Single line

500kV line 1
LA99A LA99B A99B

5018
DFR
87A 87B
74DFRX
30TA
LA52BCA
500kV YARD
30TB 30TC 30TS
LA52BCB
30SHA 30SHB
161kV line 1
5024 5028
L252BCA L252BCB
LB52BCA LB52BCB
914
161kV YARD
9A99A 9A99BB
1016
918
9152BCA LB99A LB99B

500kV line2
C1652BCA C1652BCB
9A52BCA 9A52BCB
9152BCB
1026
SCADA
GW
C2652BCA 9299A 9299B C2652BCB 9B99A 9B99BA

161 kV line 3
161kV line 2
Power Transmission Reducing copper wires

I/O IEDs in breaker cabinets in switchyard GOOSE from switchyard

Breaker position MOD position Breaker alarms Breaker commands MOD commands Interlocking AR master decision
GOOSE from P&C building

Distributed logic using GOOSE

Power Transmission Network Design
Power transmission Compact installation

P t ti and Protection d control t l for f 3*161 3 161 kV lines
2* 500kV lines
Large substation 500 kV

500kV
1 breaker 4 lines 9 breakers 4 transformers
Large substations 220 kV
220
110 kV 500 kV T2
110 kV 500 kV T2
110 kV 10 kV 20 kV 10 kV 20 kV 500 kV T3
110 kV
110 kV 10 kV 20 kV 10 kV 20 kV 500 kV T3
Double breaker 18 lines 46 breakers 9 transformers
Double breaker 17 lines 33 breakers 9 transformers
Large substation 20 kV
Large substation! 500 220 110 20 10 kV GIS 500-220-110-20-10

500kV 220 kV
10 kV
20 kV
10 kV
20 kV
10 kV
20 kV 10 kV
20 kV
220 kV T1
220 kV T3
10 kV
220 kV T2 220 kV T1
220 kV T4 220 kV T3
20 kV
220 kV T2
220 kV T4
Large substation A lot of IEDs
Transmission Protection

Line Distance Line Differential Transformer Diff B Differential Bus Diff ti l Total
42 pcs 144 pcs 34 pcs 80 pcs 300 pcs
Control
Bay Controller
99 pcs
Distribution P&C
Feeder protection
115 pcs
Large Substation GOOSE usage
Interlocking prevent e.g. e g closing a breaker in to a grounded bus.
Distributed
1-out-of-n control prevent simultaneous operations
Works regardless of operator place
Some IEDs do receive GOOSE from up to 25 other IEDs
Large substation HMIs HMI s and Gateways
Front end communication Front-end
IEC 61850 clients 9pcs
Hot-stand-by base system Operator workplace 3pc
Relay engineering workplace
Large substation How to connect it all
Redundant bay controllers connected via switch in P&C cabinet to decentralized ring Both A and B controller connected to the same network
Large substation More connections

A and B protections connected to separate star topologies Separate networks for different voltage levels
Large substation Operators interface 500 kV part
Process bus Eliminating copper for current and voltage
Process Bus Inside the Merging unit

CPSC CPSC CPSC ADC
Merging Unit LD MU014 LD MU01 LD MU01 LN ATVTR LD MU01 LN ATCTR
IEC61850-9-2 LE
Process Bus How it all is connected

PPS CPSC CB1 CPSC CPSC CB3 CPSC CPSC CB2 CPSC Control CB2
C t l CB1 Control
Merging Unit Line Protection
Control CB3 Merging Unit Line Protection
Process Bus Reactor protection

Merging Unit
P t ti IED Protection
CPSC
Questions The The only stupid question is the one never asked asked
Questions for CEU credits
1 1.
What is the meaning of MU MU

a) b) c)
Metering Unit Measurement Unit Merging Unit
2.
Using GOOSE in your SA system can

a) b) c) d)
Save space Save time Save cost All of the above
Conclusions
IEC 61850 fits well for different kind of applications There are no absolute right and wrongs S Solutions and concepts depend on requirements Applications do expand all the time
Thank you for your interest!

Basics of IEC61850 Standard

Uploaded by

Document Information

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

Basics of IEC61850 Standard

Uploaded by

Copyright:

Available Formats

SUNDAYTUTORIAL: BasicsofIEC61850Standard

Systems Integration Specialists Company, Inc.

IEC 61850 618 0 T Technical h i l Summary

Copyright 2010 SISCO, Inc.

Copyright 2010 SISCO, Inc.

Have a Question? Ask a Question As Needed! THERE WILL BE A TEST!!

Systems Integration Specialists Company, Inc.

Why Standards Are Needed

An Overview of IEC TC57 Standards

Copyright 2010 SISCO, Inc.

Copyright 2010 SISCO, Inc.

Interoperability and Integration

Nearly anything is possible with enough money and development effort

This is only possible with Standards

This is the goal of the IEC TC57 standards

Copyright 2010 SISCO, Inc.

Copyright 2010 SISCO, Inc.

International Electrotechnical Commission (IEC)

American National Standards Institute (ANSI) for USA

125 existing publications 27 active projects

Copyright 2010 SISCO, Inc.

Key IEC TC57 Working Groups

WG 10 - Power system IED communication and associated data models

IEC 61850 Communications for power system automation

WG 13 - Energy management system application program interface (EMS - API)

WG 14 - System interfaces for distribution management (SIDM)

WG 15 - Data and communication security

WG 16 - Deregulated energy market communications

WG 17 - Communications Systems for Distributed Energy Resources (DER)

WG 18 - Hydroelectric power plants - Communication for monitoring and control

WG 19 - Interoperability within TC 57 in the long term

Systems Integration Specialists Company, Inc.

What is IEC 61850?

Communications and Networks for Power Systems Automation

Copyright 2010 SISCO, Inc.

Traditional Protocol Standards

Some Level of Interoperability was achieved but not end-to-end Integration

Copyright 2010 SISCO, Inc.

IEC61850 is an object oriented substation automation standard that defines:

Companion Standards for:

Wind power Hydro power Distributed Energy Resources More likely

Copyright 2010 SISCO, Inc.

IEC 61850 Object Models

Logical Device (e g Relay1) (e.g.

Physical Device Named IED

Copyright 2010 SISCO, Inc.

IEC 61850s Original Design Purpose Substation Automation

Copyright 2010 SISCO, Inc.

Copyright 2010 SISCO, Inc.

Smart Grid Application of IEC 61850 SCADA communications

Copyright 2010 SISCO, Inc.

Smart Grid Application of IEC 61850 Distributed Energy Resources

Copyright 2010 SISCO, Inc.

Smart Grid Application of IEC 61850 Impact on Meter Models

Copyright 2010 SISCO, Inc.

Copyright 2010 SISCO, Inc.

New IEC 61850 Activities

Copyright 2010 SISCO, Inc.

Common Information Model (CIM) is an object object-

oriented information model of the power system

Central Generating Station

Distribution Receiving Gas Substation Turbine Station

Batteries Industrial Residential Commercial

UML Unified Modeling Language