of 9
7/31/2019 TVA Autumn07
1/9
PAC.AUTUMN.2007
50
IEDs exchange signals using numerous GOOSEmessages
BradleyI am very proud of the effort by all concer-
ned on the project. I believe the industry is
about to see a transformation that will im-
prove operation, maintenance, and reliabili-
ty, while at the same time reducing the cost
for design, construction and maintenance.
Jim Kurtz, Manager of Protection & Control
at Tennessee Valley Authority (TVA)
The project
7/31/2019 TVA Autumn07
2/9
PAC.AUTUMN.2007
51
Bradley
IEC6
1850
Projects
by Dr. J. Holbach, J. Rodriguez , C. Wester, D. Baigent, L. Frisk, S. Kunsman, L. Hossenlop
The wires are replaced with thecommunication infrastructurefulfilling the requirements of theprotection and control applications
by exchanging IEC61850 GOOSEmessages over Ethernet.
Protection & Control
Scheme
Redundant protection, a TVAcore protection requirement, isapplied on all 500kV and 161kVtransmission lines breakers and threesingle-phase 500/161/13kV powertransformers within substation.
Transformer Protection
Two complete, comprehensiveand independent transformerprotection systems are implemented.Set A protection providestransformer differential protection,overcurrent protection, transformersudden pressure protection, hot spotprotection, LTC sudden pressureprotection and restricted groundfault (RGF) protection for bothneutral CTs. Every transformer
status and alarms, such as fan status,liquid levels, etc. are collected bythe devices, which are located incabinets mounted on each of thefour single-phase 500/161/13kVtransformers. Analog and digitaldata from the IEDs are available inIEC61850 format to the substationautomation system.
Line Protection
Line protection relays provided i s t a n c e / p i l o t p r o t e c t i o n ,directional ground overcurrent,synchrocheck, breaker failure andreclosing. Additional pilot tele-protection devices are used for theSequoyah 500 kV line (individualPOTT schemes for both lineprotection relays) and the Conasauga500 kV line (individual unblockingschemes for both line protectionrelays). Both line protection systemson each of the 161 kV lines will sharea single communications devicefor their POTT schemes. Each linerelay is operating in a breaker & topology. (Fig. 2, Fig. 3)
Breaker Control
Th e s u b s t a t i on con t a i n sredundant breaker control devices.The idea behind dual breaker controlIEDs is to meet the same redundancyrequirement as for line protection.The breaker control IED within thesubstation yard sends information
to and receives information from theline relays using IEC61850 GOOSEmessaging. (Fig. 4)
The only hardwire status input toeach line relay is the breaker positionstatuses and this is only used if adigital IEC61850 state from either52BCA or 52BCB devices are notavailable. A hardwire trip output
First IEC 61850
Multivendor Project in the USAAn excellent group of TVA and vendor personnel made this Bradley
project a success. Jim Kurtz, Manager of Protection and Control at TVA, had thefollowing comments on the project: I cannot stress how important collaborationlike this is to the industry. For vendors and suppliers to work together to resolveissues will help not only them to provide a better product, but also to developproducts that will meet the long term needs of the industry. While this effort hasleaped TVA forward in technology, we still have work to complete.
T he I EC 6 1 85 0 s u b s ta ti o n
communication standardis almosttwo years old. Worldwide, thereare already over one hundredsubstations that have beencommissioned and running withthis new standard.
Several projects in NorthAmerica have been implementedwith IEC61850 by using productsfrom a single manufacturer. Thisarticle reports on the status of a500KV project - the first multi-vendor project in the United Statesto use this new standard. (Fig. 5)
The goal of the project isto utilize the new IEC61850standard to its fullest (as practicallypossible) therefore confirming thatthe standard is much more than
just a communicat ion protocol.Interoperability, one of the majoradvantages of IEC61850, will bedemonstrated. Our focus is not todescribe or explain the theoretical
background of the standard itself,
but rather to show and demonstratethe practical use of an actual multi-vendor project and how the standardapplies to protection engineers.
Substation Design & Layout
Another goal of this project isto eliminate or significantly reducewiring between the relays, thecontrol house and the breakers.
Dr. Juergen Holbach is man
ger of operation at Sieme
Power and Distribution in We
dell, NC. He was born in Ge
many and graduated from th
University of Berlin with a Ph
in Electrical Engineering. H
joined the Siemens AG in 19
as a development engineer
Berlin Germany. In 1994 he jned the product manageme
group for protection relays
Nuremberg Germany. Fro
2000 he works at Siemen
Power and Distribution in We
dell, NC as a product manag
for transmission relaysRaleig
NC USA.
7/31/2019 TVA Autumn07
3/9
PAC.AUTUMN.2007
byDr. J. Holbach, J. Rodriguez, C. Wester, D. Baigent, L. Fr isk, S. Kunsman, L. Hossenlop
52
Bradley
IEC6
1850
Projects
fullest, it is clear that the customerhad some key project expectations:
Open system for protection,control and data collection from any
IED. Interoperability betWeenIEDs for protection and controlfunctions. Ability to configureIEC61850 system with availablemanufacturer tools without need foron-site manufacturer support.
Comparable functionalitywith streamlined design. Eliminatepanel control switches and lockoutrelays and incorporate functionalityi n t o I EC 6 1 8 5 0 I EDs . Th i sdramatically reduces the panel layoutdesign and allows for a smallercontrol house (about the size vs.traditional design). For example,consider that just one set ofprotection, up to 12 breakers, can beprotected and controlled using onesingle 19 wide panel versus olderdesigns with 1 breaker per panelwith both Set A and Set B protectionsystems. Standard panel designs forany application can be created.
Accommodate multiplevendor IEDs
Comparable performancetime
Secure & dependableoverall system. Timely, secureflexible information transfers.
Flexible management/operation
Economically viablesolution
C o m m o n t e c h n o lo g yinfrastructure
Reusable practices. Projectestablished foundation of newsubstation practices oriented aroundIEC61850 and new procedures.Business case can be made forwholesale refurbishment with these
new practices. Effective data management
system Reduced wiring and
installation costs. Besides the CTand PT wiring from switchyard
br ea ke rs an d mo tor op er at eddisconnects, only breaker status and
br ea ke r tr ip wir in g ha s be en
implemented. No inter-wiring existsbetween any of the IEC61850 IEDs.
High-speed local and remotedownloads to IEDs over network
Improved Operations andMaintenance from remote andlocal monitoring and diagnostics vianetwork to reduce service time
System health/statusmonitoring
Status communicationsbetween IEDs
Testing methodology. Newtest plan, tools and methodologyneeded to match systems newcapabilities and plan to implementtest cases. Ability to individually testany IED without the concern ofoperating other IEDs via thenetwork.
On-Site LAB Workout
Sessions & Configuration Tools
Used
In August 2005, the TVAIEC61850 project team metfor the first time (Fig. 6) to beginthe process of designing the firstIEC61850 based high voltagesubstation in the US. The teamconsisted of four major relayvendors and representatives fromTVAs relay and communicationengineering departments. Besidesall interoperability demonstrationsorganized previously by the UCAInternational Users Group or byCIGRE, the teams objective forthis project was to show that eachrelay vendor can demonstrateinteroperability of the protectionand automation devices from designto implementation in real life.
D u r i n g t h e I E C 6 1 8 5 0integration process the four relayvendors participated in threeprimary tests at the TVA "test
lab substation. The goal was todemonstrate that TVA could takethe primary lead of configuringtheir substation with the availableIEC61850 configuration tools usingthe manufacturers in a support role.This would be the first IEC61850project where the customer woulddo the system engineering and
Craig Wester, is southeast US regional sales/application ma-
nager for GE Multilin in Norcross, Georgia.
He was born in Belgium, Wisconsin, and received a B.S. in Elec-
trical Engineering with a strong emphasis on power systems
from the University of Wisconsin-Madison in 1989. Craig joined
General Electric in 1989 as a utility transmission & distribution
application engineer. He is a member of the IEEE.
from the line IED is wired directly tothe breaker 1 and breaker 2 trip coils(for risk management purposes).
With experience, future designs mayprovide the substation engineer theoption to eliminate these hardwireinputs and outputs and to strictlyuse the GOOSE functionality.
Network Connections
A l l I E C 6 1 8 5 0 I E D s a r econnected via 100 MBps multi-mode fiber cables to substationhardened Ethernet switches locatedin the control house. VLANsare used within the IEC61850GOOSE message configuration ofeach IEC61850 device to providesecurity within the network. Figure9 shows a conceptual layout of thenetwork.
C u s t o m e r / P r o j e c t
Expectations
Since one of the goals of thismulti-vendor project was to utilizethe new IEC61850 standard to its
Drew Baigent, is a senior design engineer with GE Multilin in
Markham, Ontario, Canada. He has over twenty years expe-
rience in the design and implementation of test systems, mo-
tor protection & control products, power system protection &
control products, and communication protocols & systems. He
was involved in the design of the IEC61850 implementation in
the GE Multilin Universal Relay family of products.
This project wasa tremendouslearningexperience
Luc Hossenlopp, is working at AREVA T&D as Substation Auto-
mation Product Line manager. He is member of IEC TC 57 WG
10 and has been involved with the design of the IEC 61850
standard since its beginning.
7/31/2019 TVA Autumn07
4/9
ICD
File
IEC 61850 worldSystem ConfgurationTool
ICD
File
ICD
File
SCDFile
PAC.AUTUMN.2007
53
IED integration. The integrationduring previous interoperabilitytests on other projects throughoutthe world had been implemented
by members of the relay vendorsdevelopment department usingtools and programming languagethat were not always accessible oravailable for use by the customer. Allparticipating vendors had previousexperience with commissioningseveral IEC61850 based substationworldwide, but in almost all casesone of the vendors was the integratorand mainly used their own products,engineering tools and integrationprocedure to configure a substation.The integration of these previousprojects was simpler becauseinterpretation of the IEC61850standard was uniquely confined tothat vendors system architecture andproduct implementation. It is also
important to note that trade showinteroperability testing only coversa small portion of the functionalityrequired for a complete substationsolution. So, the TVA project in thisrespect was completely differentfrom previous projects and the tradeshow interoperability tests. TVAwas the system designer and system
integrator and they would use theavailable tools from each vendorwhile at the same time deal with theunique interpretations of the newIEC61850 standard by each vendor.
Configuration Tools, ICD
and SCD Files
The primary goal during the firsttest meeting (August 2005) of theproject team was to configure allGOOSE links between the relaysfrom the different manufacturersand to reach a minimal levelof device interoperability. Theprocedure to achieve this is showninFigure 1. All manufacturers hadto supply an ICD file (IED CapabilityDescription) that described theability of the relays in a standardIEC61850 format. This ICD fileis the interface between the relaymanufacturers IEC61850 tools and
the IEC61850 world. With the ICDfiles available, the customer can useany independent IEC61850 SystemConfiguration tool to import theICD files from each relay vendor andconfigure the system. (Fig. 7) Oncethe IEC61850 station is configured,a SCD file (Substation ConfigurationDescription) can be created and
exported describing the station ina standard IEC61850 format. Therelay vendors must be able to usetheir proprietary tools to extract
the information inside the SCD fileand use it to configure the individualrelays. TVA decided to use the onlycommercially available at the timeIEC61850 station configuration toolwith all the required functionality
Lessons Learned & Testing
Tools Used
During the first test meeting asignificant amount of discussionwas centered around the questionof whether TVA wanted to use theGOOSE message implemented inUCA called GSSE in IEC61850to provide compatibility with UCA2.0 implemented substations, orto use the real IEC61850 GOOSEmessage. After evaluation of all prosand cons, the decision was made touse the IEC61850 GOOSE message
because of the advantages this newimplementation has to offer.
Some discussions made itapparent that all relay vendorsdid not fully understand thepower of the new standard. Forexample, it was thought that it wasnecessary to manually configurewhich information in a GOOSEmessage was to be sent first, thedata information or the qualityinformation. It was discoveredthat different manufacturersand, sometimes, different relaysfrom the same manufacturer didit differently, so there was a fearthat the information may getmisinterpreted.
After a lot of discussions andphone calls, the team determinedthat the order of the informationand quality data did not matter as
long as it was declared in the ICDfile. The receiving relay will get theinformation because it is defined viathe SCD file and it knows how toprocess the information correctly.
During that meeting most relayvendors also did not have theirtools ready to automatically exportand import from their proprietary
1 IEC 61850 File Standards
Another
goal of t
project
to
eliminat
significa
reduce
wiring
between
the rela
the con
house a
the
breakers
7/31/2019 TVA Autumn07
5/9
PAC.AUTUMN.2007
Bradley
54
IEC6
1850Projects
p rog ra m m i n g t ool s t o t h eIEC61850 world via ICD and SCDfiles. This resulted in a significantamount of manual programming
work. To validate the correctnessof the ICD file, the team used theSystem Configurator as well as theIEC61850 Validator tool. It wasdetermined initially that some ofthe ICD files had some format errorsand during the import of the files, anIEC61850 Validator tool producederror reports.
These errors were the first hurdlethat had to be resolved.
Even though the validation ofthe ICD files could verify the correctsyntax of the file, it could not checkfor the semantics. Once we wereable to import the ICD files anduse the System Configurator toolto configure the required system,in some cases, we were not able toreceive the programmed GOOSEmessage because the GOOSEmessage description was differentthan what was actually described inthe ICD file. To analyze problemswhere one relay vendor claimedthat they were sending a GOOSEmessage that the receiving vendordid not receive, the team used thenetwork protocol analyzer toolEthereal with the MMS decoder
functionality. Ethereal allowedfor the entire GOOSE structure to
be displayed, so that a view of thespecific relay IED including the value
of the data and quality informationcould be analyzed.By using Ethereal, we were
able to see where adjustments werenecessary and finally all GOOSEmessages were sent and receivedcorrectly between IEDs of thedifferent manufacturers. The goalfor the test week was achievedand the concept of IEC61850 wasproven powerful. Even with thisaccomplished, configuration ofthe TVA system was not simple.However, the tools available wouldallow the customer to configurethe system by themselves. Duringthe design process, there wereseveral firmware updates, patchesand discussions between thedevelopment departments of eachof the relay manufacturers. Withoutthe great teamwork between allthe manufacturers and the deepknowledge of the implementationd et a i l s of I EC 6 1 8 5 0 , t h einteroperability goal could not have
been achieved. But it was clear thatthis was not a pract ical procedurethat a utility could use to configuretheir IEC 61850 substations.
The second test week waconducted in January 2006. Thgoal was to have TVA be thsystem designer/ integrator anconfigure the system with as littas possible support from the relamanufacturers. We have to admthat this goal was not achieved
because some of the manufacturertools were still not mature enoughA lot of manual work was stirequired and detailed knowledgof IEC 61850 was also necessarin order for the correct ICD files t
be extracted out of the SCD file foconfiguring each IED. With suppoof the relay manufacturers, thsystem was successfully configureand working at the end of the wee
but the actual goal was not achieveAt the end of the meeting TVrequested that each relay vendo
2 A Set Protection
The configurationof the IED
communicationwas achieved usingSCL files only
3B Set Protection 4Breaker Control IEDRelays from
several ma-
nufacturers
are used for
all line and
transformer
protection
requirements
7/31/2019 TVA Autumn07
6/9
Bradley 500 kVSubstation
PAC.AUTUMN.2007
55
finish their tools, so that they canhave the capability of configuring anIEC61850 system independent ofthe relay manufacturers.
All manufacturers met again inthe TVA test lab substation inthe third test week (March 2006).Focus was now on the tools of themanufacturers and if they wereable to support TVA in configuringtheir IEC 61850 substation withoutany major support from the relayvendors and a need to have deepknowledge of the IEC 61850implementation details.
The tools from ABB, GE Multilinand Siemens were found matureenough to fulfill the customerrequirements. However, a newproblem was discovered regardingdifferent tools supporting differentoptional features of the IEC 61850standard. For example, some IEDsneed to know some hierarchicaldata like voltage level, feedername in each IED. This data can
be submit ted to the IEC 61850system configurator via theSSD files (System SpecificationDescription). This file format isoptional in IEC 61850 and doesnthave to be implemented. The usedsystem configurator in this casedid not support this feature at this
time. This made it necessary thatafter the SCD file was created bythe system configurator that thefile was edited by another tool
to add this hierarchical data andthen re-imported in the systemconfigurator.
At the end, TVA was able todevelop a procedure that allowedthem to configure and design thesystem independently, withouton-site support from the differentrelay manufacturers. This wasdemonstrated by TVA during thepreparation for the May 2006 IEEET&D show in Dallas, TX wherethe Bradley project configurationproved interoperability in the UCAInternational Users Group IEC61850 demonstration.
TVA built the demonstrationpanels and configured the systemthat was placed on display at theshow using the IEC 61850 toolsprovided by each vendor.
Overall, the process involveda n u m b er of h u rd l es , b u t demonstrated that by having astrong and determined team ofrelay manufacturers and excellentgroup of TVA engineers, future IEC61850 project implementationscan be successful and economicallyadvantageous.
Lessons Learned Throughout
the Project
This project was a tremendouslearning experience for the
participating vendors and TVA. Inaddition to those described in theon-site lab workout, the followingare some of the additional lessonslearned throughout the project.
VLAN issue with Ethernet
switch - The Virtual LAN (VLAN),an advanced layer 2 function definedin IEEE 802.1Q, provides highpriority tagging of a message andefficient means for data exchangein applications using the IEC61850station bus and process bus profiles.In the IEC61850 standard, a
VL AN tag wa s defined as part ofa valid GOOSE message. Somevendors IED implementationrequired the VLAN tag in a receivedGOOSE messages to validate theinformation. The Ethernet switchesused in the Bradley project initiallydid not pass the VLAN priority tagthrough the switch. This issue wasidentified early in the project and afirmware update was provided forthe Ethernet switches.
Logical device names - LogicalDevice (LD) naming syntax isdefined in IEC 61850 part 7-2. Thelogical device names in this system
5 Substation Location 6 Project Kick-off MeetingThe success
of the project
is the result of
multi-vendor
team work
Steven Kunsmanjoi
ABB Inc. in 1984 and
has B.S. in Electrical E
neering from Lafaye
College and an MBA f
Lehigh University.
He is the Head of Glob
Product Management
responsible for ABB S
station Automation
Products portfolio
worldwide. He is an ac
member of the IEEE Po
Engineering Society PS
and Substations C
mittees, an IEC TC57
delegate in the deve
ment of the IEC61
standard and UCA
ternational Users Gr
Executive Commit
co-chairperson.
7/31/2019 TVA Autumn07
7/9
PAC.AUTUMN.2007
56
Status vs. quality order- Itwas thought that it was necessaryto specify which information in aGOOSE message was to be sent first,
the data information or the qualityinformation. It was discoveredthat different manufacturers andsometimes different relays from thesame manufacturer did it differently,so there was a fear that theinformation may get misinterpreted.After a lot of discussions and phonecalls, the team determined thatthe order of the information andquality data did not matter, as longas it is declared in the ICD file.The receiving relay will get theinformation because it is defined viathe SCD file and it knows how toprocess the information correctly.
The effect of the quality state
on the status state - Conventionalhard wiring states are either on oroff without an indication of signalquality. The IEC 61850 standarddoes not provide rules for theinteraction between quality andstatus bits. The question posed isshould the loss of the quality stateeffect the state of the status value,thus a quality state of 0 results ina force of status state of 0 (even ifthe status is actually true or 1)? Orshould a quality state of 0 result instaying at the last known status state(which is 1 in this example)?
Both vendors meet standard,but do not interoperate - Device
(IED) conformance to the standard isaccomplished by validating an IED atan accredited IEC 61850 test facilityin accordance to the IEC 61850
Part 10 and the UCA Internationaltest procedures. It is important tonote that the conformance testingdoes not validate conformity butonly validates the IED testing hasidentified no non-conformities.An IEC 61850 device certificateis then issued by the accreditedtest facility providing the vendor astatement that no non-conformitieswere identified during the IEDtesting. The testing is limited to asingle device in a test system anddoes not cover multi-device systemlevel testing or interoperabilityin a multi-vendor system, i.e. theIEC 61850 certificate does notguarantee that a certified device willinteroperate with another device.Device and client interoperabilityhas been left to the vendors tovalidate. In the Bradley project, allvendors had IEC 61850 certifiedIEDs, but several issues as previouslymentioned resulted from wronginterpretation or ambiguity in theIEC 61850 standard. Below are someexamples of issues encounteredduring the Bradley project thatimpacted GOOSE interoperability
between different vendor devices:Supporting optional attributes
in GOOSE- One example of theinteroperability issues encountered
were to be named according tothe customers standard practicefor devices associated with
breakers. The 99A and 99B
breaker identification labels werepreferred since this was TVAsstandard for naming multifunctionmicroprocessor based relays. Thenaming syntax restrictions definedin the IEC 61850 standard does notallow these type of LD names (thosestarting with a number) due toconstraints in MMS (ManufacturingMessage Specification).
The solution for this issue wasto name the breaker IEDs (LogicalDevice names) LA99A andLA99B respectively.
GOOSE ID naming - GOOSEID naming is an attribute that iscontained in the GOOSE message.One IED vendor uses this GOOSEattribute to display status of receivedGOOSE messages. In the Bradleyprojects system engineering tool,the GOOSE ID was automaticallyassigned as a number, althoughthe standard is not restrictive tonumbers and allows strings.
The issue on utilization of IEC61850 data is that one vendor usageor extension of the data may not
be possible with another vendorsimplementation.
The GOOSE ID strings in theSCD file were renamed using aseparate tool capable of manualmodification of GOOSE ID names.
7Configuration Tool 8 Bradley - Final Configuration
7/31/2019 TVA Autumn07
8/9
PAC.AUTUMN.2007
57
Bradley
IEC6
1850Projects
was that one vendor could includeboth mand ato ry and opti onalattributes in the IED using GOOSEmessaging. Then another vendorsIED (GOOSE receiver) could onlyunderstand mandatory attributesand was not able to supportthe optional attributes; thuspreventing interoperability. Theresolution was to not use the vendorspecific attributes in the GOOSEcommunication between theseIEDs.
Adherence to name case
sensitivity - Another issueencountered was in the adherencelower and upper case sensitivity.One vendor was more liberal anddid not strictly adhere to the casesensitivity as defined in the standard.The other vendors engineering toolwas rejecting the names when thecase was opposite to that as definedin the IEC61850 Part 7. This wasresolved by using a newer version ofthe SCL XML schema.
Quality in GOOSE versus no
quality - The support of data itemquality flags in GOOSE datasets wasa major obstacle in the beginningof the Bradley project. Differentvendors provided different levels ofsupport for quality flag data. In thiscase, one vendor required quality
information in their application toconfirm validity of the data for eachvalue received via GOOSE. At thesame time, another vendor was notable to send quality information inthe GOOSE message. This resultedin the inability to exchange GOOSEmessage between IEDs and thus,a major interoperability issue. It
was decided to use both status andquality within the Bradley projectfor consistency. Both quality andstatus are now available in each
vendors device and successfulGOOSE interoperability betweenmultiple vendors has beenaccomplished.
Length of names of GOOSEControl Blocks - The length ofGOOSE control block namessupported in the different vendorIEDs was an issue. The Bradleyprojects system engineering toolautomatically generates namesfor DataSets and GOOSE ControlBlocks. The string length of theseautomatically generated names wastoo long for one vendors IED. TheGOOSE Control blocks in the SCDfile were renamed using a separatetool capable of manually modifyingthe GOOSE control block names.
Substati on sect ion - Thesubstation section of a SCL filecontains information about thesubstation layout, logical nodereferences and device configurationand association information. Onevendors IED tool required thissubstation section along withthe Logical Node references to beimported from SCD file generated
by the system engineering tool. Thesystem engineering tool was not ableto produce the needed informationso manual manipulation of the SCDfiles was required to complete theIED engineering. The resolutionwas manual configuration of theSCD file adding the necessaryinformation.
What vendors have toimprove to make it easier? - Betterpreparation of the product andsystem technology is needed. IEC61850 is a very comprehensive
and complex standard that has thepotential to revolutionize substationautomation systems if the necessarytools and product functionality isavailable. The vendors involved inthis project needed to collaborateto assure that the substationautomation system functionalityand interoperability capabilities
were validated prior to the executionof the customer engineering andsystem build up.
What could have been done
differently? - Clearly, the lessonslearned in the multi-vendor TVABradley IEC 61850 substationproject have been extremelyvaluable for the entire industrypushing for this new standard.The extent of the Bradley projectprovides complete functionality,with a goal to move into the digitalsubstation.We can state that theBradley project has explored all
benefit s made possible throughthe new standard that prior to thisproject has not been done in a multi-vendor environment. Most of theexecuted IEC 61850 projects have
been turnkey homogenous vendorsolutions where interoperability
between one vendor's products ismuch easier. In the other projectswhere multi-vendor projects have
been executed, the foreign devicehas typically been a main 2 or
backup protection terminal wherethe system functionality onlyrequired limited exposure of theIED functionality via the IEC 61850system. On the other hand, industryexpositions demonstrating multi-vendor IEC 61850 interoperabilityhave set expectations that thecomplete IEC 61850 benefits arereadily available. This is not the casesince these demonstrations focus on
Collaborationbetween vendors isextremelyimportant for theacceptance ofIEC 61850
Julio Rodriguez, works for Siemens PT&D in Wendell, N
rolina. He was born in Colombia and graduated from
University in Bogot as Electrical Engineer. He joined S
in 1996 as design engineer for substation automatio
got, Colombia. In 2000 he moved to Nuremberg in G
to the configuration and project management group
station automation, developing projects all around th
In 2006 he joined Siemens PT&D in Wendell as Sr. App
engineer focused on automation for substations and
plementation of the IEC61850 protocol.
Lars Frisk, joined ABB in 1998 and has since then be
king with IED and Tool development in Vsters, Swed
is currently working as Engineering Architect with fo
IEC61850 in tools and IED development. He has 15 y
experience within hydropower plants, power distribut
substation automation.
7/31/2019 TVA Autumn07
9/9
PAC.AUTUMN.2007
58
Bradley
IEC6
1850Projects
The system engineering process isone area that multi-vendor exchangeof IED and engineering data needsimprovements. Today, a vendorssystem engineering tool worksperfectly with their own devices butcreates limitation when exposed to
other vendors devices.What needs to be done in
the industry is a higher level ofinteroperability functionality andstandard test cases that can assure aminimum level of interoperability.Here the recommendation is that theUCA International Users Group setup performance and functionality
criteria for levels of interoperability.D e v i c e l e v e l c o n f o r m a n c ecertification only validates a fractionof the overall substation automationcapability. Figure 8 shows the finaldesign deployed for the TVA BradleySubstation.
T h e i n d u s t r y s h o u l dconsider Ethernet switches asprotective devices when itcomes to implementations ofcritical protection schemes usingIEC61850 standard and whetherthey are configured and maintained
by protection/test engineer or ITdepartment.
simplistic applications and minimalfunctionality to prove vendor A caninteroperate with vendor B.
What could have been done
in this project is to set up aninteroperability project to validateproduct and system functionality
before starting the Bradley project.In this case, the project wasconducting the interoperabilityvalidation. System engineeringis the critical step in the Bradleyproject where an open discussionregarding system engineeringtool to know the limitation in theintegration of other vendors IEDs.
PMU
RelayA
OIP(HIMI)A
52BCA
SCADAA
RelayA
METERA
52BCA
RelayB
OIP(HMI)B
52BCB
SCADAB
RelayB
METERB
52BCB
GPSReceiver
CarrierSet
XFMRMonitor
WeatherStation
XFMRIED
PMU
MaintPC
CBMonitor
DFR
DFRIED
CarrierSet
TelecomDevice
AlarmRemote
RouterFirewall A
RouterFirewall B
WAN Link BWAN Link A
BackboneEthernet Switch A
BackboneEthernet Switch B
Ethernet Switch(Common Network)
Ethernet Switch(A Train Network)
Ethernet Switch(A Train Network)
Ethernet Switch(B Train Network)
Ethernet Switch(B Train Network)
Ethernet Switch(Common Network)
Ethernet Switch(Common Network)
Ethernet Switch(General Network)
IEC61850
based system
must be
considered
an integral
part of the
protection
and control
system and
not just
another
protocol
application
for substation
automation.
9 TVA Bradley - Conceptual Network Layout
