0 ratings0% found this document useful (0 votes) 440 views12 pagesIec 61850
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content,
claim it here.
Available Formats
Download as PDF or read online on Scribd
During the WG10 meeting in
May in Berlin representatives from,
ENTSO-E were invited 1 express
their concerns and were asked
to provide examples to support
them. As a result, the ENT'SO-E
created a"Punch-List" with about
25 individual issues, which were
presented atthe WG 10 meeting in
Oceoberin Houston,
The "Punch-List” confirmed
‘what was expected based on the
several thousands of IEC 61850
substations in operation and the
hundreds of satisfied IEC 61850
customers around the world: IEC
(61850 isalready far beyond legacy
protocoslike DNP3 orlEC60870-5.
‘There is no single concern about
communication interoperability.
Most ofthe concernsare related to
the engineering capabilities of EC
{61850 and tothe complexity ofthe
standard
Similar to the move from
electromechanicaltomicroprocessor
based relays some 30 years ag0.
the introduction of IEC 61850 is
Usa f£c 62850 forthe communcestion buses sobs
How dothe
end users see
IEC 61850?
the ENTSO-E statements on IEC
{61850 brit diseused them in
another significant step. This has
probably been underestimated by
the WG while editingthe standard.
‘The utility engineer trying to
apply the standard needs guidance,
‘otherwise he will noc be able to
assfy problemsthat naturally may.
apex.
‘The"Panch-List” however, has
identified some issues that - once
solved -willenhancethebenefits oF
IBC618S0:
1m Semanticincerpretation ofreal
modes
The multi-vendorengineering
process
‘While some of the issues have
been addressed, iisstilla valuable
input that bas been provided by a
group of utilities thanks to their
lingness to fully exploit the
benefits of IEC 61850. Similar
Incroduetion and overview
‘Communication requirements for functions and device models
by Christoph runner, fpower, Sized
Issues have been identified by
other utilities while doing their
‘own integration of standard based
products.
This is also a good example
that standards need to be jointly
developed between vendors and
users to ensure that the standards
fulfil the requitementsof the users.
‘The contribution ofthe users is
crucial - they need to have a clear
‘understanding of what they want,
and how they want to use the
standard based productssothacthey
can formulate their roquirements
‘The technology today offers too
‘many possiblities that would not
be fully expioited if we would just
dobusinessas usual.
‘As | am describing in cover
story of ths issue of PAC world,
significant work is ongoing to
add functionality that will solve
many of the raised concerns
‘The remaining ones are mainly 3
question of product functionality. A
listof EC 61850 documents under
developments included below. a
Hydroelectric powerplants = Communication fr monitoring end control 's
13 | IeCotaso modeling concepts ir
{300 | Use of ooica’ nodes to madel functions ofa substation automation system i
3pece communieaton ervice mapping (CSM) Mappings toweb services| Is
anformance testing 5
Mapping ‘to Web Services ~ Requirement Analysis and Technology Assessment | Ft
Sha conivl centres | TR
Usina IEG 62880 for condition monaring tt
Network engineering guiselines for substations m
UEraIEC CRESS Caution Ariat gpa 7k
Beet models er era cle fe
ect models for electrical energy storage
(Object models for schedules i
Methodolotes fr modeling of loges for IEC 61850 baced applications te
Wine area network engineering gullies mt
Extension of IC 61690 information models to also include logical odes and data
{Gonmumieation network srustures in hydro power plants Th
rnetional esting of EC G80 based Systerta, Te
Interoperability tests for hydro equipment based on IEC 61850 8
IEC 61850 update Ee
‘Christoph Brunner:
Pretident of son dependent
UC hed Sutzenand Hef
5 years of eine with
ned across sever areas
manage at A8 Sizerand
stem Hes Convener of WO 20
f the EC TOSY and ia member of
W718 and 19 of C1057. He
IEEESA He isan EEFelow anche
ofthe REEPSAC aea meres of
‘he PRE mal comet an theby Alvaro. A, Perc, Jono Fete, TemostonesN Tavares
‘Companhia Hidocleria do Sa Francisco, CHESE, Bra
Oo Theelectri di e
g L L d he electric power industry is ex- mi
te
2 LESSONS LEAMNE|G| perescingimporantchangesin
3 pe
2 f h fF the implementation of new SAS the
& trom the use o P ‘ Ps
g (Substation Automation System), and
:
§ IEC 61850 in =
g iba ‘ Sa
& + TEC61850standard by many utili: fen
+ Substation =
8 ties, in differentscopes ofapplica- tm
2 . and
& Automation Systems iorsicprovisessomesotutions is
for the exchange of information, oe
sit
integration and standardization. Meanwhile, many legacy IEDs (Intelligent Electronic Devices) thet
and communication protocols till existand will ast formany yeatsin theirapplications. More- | ay
SAS
over, these systems may need to be expanded ormay have some EDs retrofitted later, withim- eau
pacts on their architecture. This article is about the practical use of the IEC 61850 standard in ee
totally new SAS, as wel asin integrations to legacy systems, based on expansions orrefurbish- | 2)
ments applied to more than 30 high voltage substations at Chesf Companhia Hidro Eletricado | i
vars Tadeo
H}| araijoPerote Sao Francisco), in the last years.
\ u So aR, IEC 63850 IAs BEEN
used at new SAS station bus, for
. interlocking, discurbancereord-
: ings wart, relundaney, protection
Berl ietestoer schemes and supervision nial
theConpomie evaluation is made, considering
Yorrisencnsso Specification, documentation,
rancsco-chel Runetonaliies,relabir, ala
a ing, testing operation and main
Ssotsnpows tenance. GOOSE and MMS based
Spm toraion | rnasengesare subject torelabiiny
00, fone | anaes. important bnefic area
Federer of ready accomplished, while pls
Da UFDA baal and drawbacks aise, Fist stage
Sifebioied obstacles represent challenges to
hdeagrinne be faced. Information within the
tainting | meneges supa burthelack of
misirigand | tnthi-vendor tnveropersiicy is
neces _agreatdisappointment The need
dntaionptce | foradditional Ratucsarereported,
‘ Some are covered by Edition 2 of
: the standard. Examples of imple
ea‘mentations are shown, exploiting
techniquesandsolutions. though
in| therearesome research projects,
| process bus is stil not used, for
is | ‘there are concerns on maturity, lack
J ofpreducts, time synchrontzation
3), | andnetworkreiblty
IEC6185Dhasalzobeenwsedin
he | inegration of new bays to Legacy
| SAS, with impacts on the archi-
tecture, Significant changes are
reported, on retrofitting the subst-
tion SCADA (Supervisory Control
and Data Acquisition) system, A
ns migration plan forthe overall solu-
tion is needed, with detailed stages
i, “oftransient topologies and testing
strategies, designed for connecting
x) the operational legacy SAS to the
new one. A special issue after ince-
e ‘gation 102 limited protocol legacy
SASisthe broad capability for new
n expansions the future. Lessons
‘were learned with the above men-
‘by Also A Poon, Joel Ferree, Temostenes Tavares
toned experiences. Practical apli-
cations and operational experiences
provide useful tipsand implemen-
tation guidelines, which can lead
to the best practices. The exper-
tisebuilt with chisstate-in-the-ate
technology ean avoid some inital
dificuties and can give important
feedback,
‘This article aims to providere-
tum on experience of some SAS
applications, functional scopes,
diliculties and ideas, highlighting
tho useof the IEC 61850 standard,
‘within thesmargrid scenario,
‘The Use of IEC 61850 Stan-
dard in SAS at CHESF
‘Brazilian tiles have different
levels of local automation in sub-
stations, starting from decreasing
use ofl elecromechanicalelays
angi control buttons up to increas-
ing use of complete digital SAS.
IEC.61850 standard was irseavail
‘Companhia Hldoaletis do Sao Fancisco,CHESE, Bes
Most recent SAS
implementations were
based on the typical
architecture shown
below.
ablein the year of 2004. There sa
huge change in paradigms, for itis
based on standardized information
‘models, data semantics, common
use ofa language called SCL (Sub-
station Configuration Language),
functional virtualization and ad=
‘vanced communication services for
information exchange.
Inthe 1990'sand early 2000,
many differen vendorsused sup”
ply SAS, using specific proprietary
and some standardized protocols,
i 2 The SAS (Substation Automation System) typical architecture
ena One Cartel Cer et
fe Dchesr
nt
Ec
7
peste
sev SCADA
| bigs istrtenee Racerdse 7)
Jecnildo Cosar
orora Ferrera
yoked san
cal gine
i 2mn atthe
Supeires de Maceo
CESMAG, a He
He achieve i MBA
ret inuy 200,
‘ota vargas Fo,
a Chet hee
inated with the de
testing and commis
slonng of azomaton
systoms
‘emestenes Nunes
Tavares rae
sted aan eis
gern 2000 at
He as beenin the
etica do Sao Fan
isco Ces since
2002 Mes Masten
Hectic engineers
MSe.in Power Sy
the Federal Uniersty
USC faehin
2003 At hes hes
‘votes ith sy,
desig implement
anemaetanance oflesson learned a
rec618s0
Figure 3: some
1eDs come with
buitein Goose
in funtion,
white others
Implemented
with ogies
and profile
bby Alvaro‘. A. Pore, Jono Ferree, TemostenesN Tavares
‘Companhia Hldvodlecia do Sto Raneiso, CHES, Bre
The use of IEC
61850 standard
at Chesf started
in 2006 with the
specification of
new SAS.
such as: Conitel/PCD5000, EFIP,
K-Bus, SPA Bus, Modbus, Profibus,
TEC 60.870-5-101/108/104, IEC
60.870-6, DNP3.0 ete. However,
the need for expansions, prococol
compatibility, high costs, obso-
lescence and spare parts Became
important issues, considering the
heterogeneous solutions.
“Theuse of the IEC61850 stan-
dard came upasa hopeful solution
‘to many problems, by promising
standardization, optimization and
system interoperabilcy. Theuse of
IEC61850 standardat Chesfstarced
{in 2006, with thetechnical specifi-
‘ation of new SAS. The fist one of
‘thor was intograted tothe clectr-
‘alsystem in 2007. It hasthen been
adopted inall new SAS specifiea-
tions for thestation bus, ineluding
integration tolegacy SAS:
‘This article presents some les-
sons learned from practical applica-
tions withthe use ofthe IEC61850
standard at Chesf, so far in more
than 30 high voltage SASs
Practical Applications
The Typical Architecture: ‘The
most ecent SAS implementations
‘were based on the typical achitec-
ture, brelly shown in Figure 2
“The Human Machine Interface ~
IML is formed by redundant com:
[puters in the Local Area Network,
with connections to the IEDs,
‘within the station bus. Soar, here
areno applications with IEC61850
sample values in the process bus
General Functionalities: The
local SCADA syscerisimplement-
edwith the SAGE (Sistema Aberto
de Gorenciamento de Energia) sou-
tion, that was developed by CEPEL
(Electric Power Research Center), in
Bazil. There ate redundane servers
performing real time database man-
agemencand advanced applications,
besides regular HMI functionality
forlocal operation. The system per-
forms simultaneous communication
trough the neework, using the fol-
lowing usual protocols:
'm IEC 61850 based protocols
(TCP/IP, MMS and Goose), with re-
portand peer to peer messages, com
prising SAGEand IEDsof the SAS
I DNP3.0 protocol, with theRe-
‘mote Operation Control Center
(COR") system.
lm DNP30, IEC 60.870-5-101 oF
‘other protocols, with the legacy SAS
if prosont, usually by Terminal Server
serialeannections
‘There isan Ethernet ring,some-
times more than one, formed by
redundant switches, with RSTP
protocol. Depending on the types
of the IEDs, they can be part of the
ring, partof multiple rings, or star
‘connected, Connectionsto the COR
canbe either by serial dedicated fines
‘orrouted through the LAN / WAN.
GPS feod the NTP Server, con-
nected to theswitch, to synchronize
the IEDsand the computers,
An example of GOOSE monitoring
066): 58/95
So x 8) X) BO Ae
‘Remoteaccess to IEDs and SCA-
DA system by maintenance station
ispossibleand represents powerful
tool foranalysisand quick re-estab-
lishment ofthe systom.
Communication and Messages:
AttheSCADA level, supervisionand
control messages are based on the
MMS protocol, according tothe Ci
‘ent/Servermodel.
Prioritized multicast GOOSE
messagesare adopted in the exchange
‘finformation between the IEDs, for
status, interlocking, testing, distur
bancerecordings, blocking redundan-
‘Sampled values within the process
busarebeing considered, burnotbeen
used sofa
Special Implementation Fea-
‘tures: Considering the characteris-
tics ofthe messages and its reliability,
special features have been added in
‘implementations, sch as:
1 GOOSE “latching” or “default
status,” for keeping desired status of
‘important messages participating in
logics, in caseit vanishes due to com
‘munication failures
Use of GOOSE messages to
achieve redundancy in control logics
impler
file tres
exampl
Prot
supple
a "Protandprotecionschemes.asanalte- The use of the IEC 61850 Standard came up
tte way for hardwired abl solsti
si.ui"urnateie. __aSahopeful solution to many problems, by
ee ea logcsofthe promising standardization, optimization and
‘tipcommands to the process or to system interoperability. |
scar interrip messages between
IEDs, when est modetsselecied be developed, explicitly showing schemeandinertrip-Thered lines
1 On-line supervision forthe the protection functional inter= indicate the physialconnetions
communication inks between de- _ communication among IEDs and fom the tansformerto the IEDs,
vicesand SCADA, inthenetwork switchyard equipments, aswellasfrom the IEDsto the cir.
.GOOSEon-line monitoring, example shown in the Figure be- cuit beakers, for protection trip
focfiluresupervisionafthesub: low In this case, the transformer Function purposes Onecan notice
scribed messages. Different solu- is protected by 3 three) protection thatthe rp functions canbe origi
tions have been conceived by relays F, F2 and F, that canis. nated from the protection device
diffrent vendors. Some IEDsal- sue trip commands othe 2 (wo) itself or from an inererip source,
readycomewiththisbuilein fine- icuit breakers, called 1471 and coming fom another ED.
tion, while others need to have it 1271, respectively on the primary “The protection diagram is very
‘implemented withlogiesand pro- and secondary sides hhelpflin integration and commis
fletreatmene (Figure 3 showsan Theblue dotted lines indicate sioning tests, fulfilling the lack of
camp) the GOOSE messages flow toand documentations usally available.
Protection Diagram: As a fiomalldiferent EDs, sed fr ster “The maintenance team may find
supplement for documentation, tusinformation, interlocking func. ievery helpful too, during future
"Protection Diagram" can also tions, breaker fare protection ‘work, voidinglongtime esearch
4 An example of a “Protection Diagram”
Dchesr “ee
also being used
for achieving
a PIERRE physica
FOSS IS Sane
eter pee
from logical
Gr raterarton Na r
Pn rose Fee tama,
Ceara F = with some
configuration
roegesiarean efforts but no
extra cable
1 yates 6008507)lesson learned. a
Figure
or “Goose
oveloped, with
the information
low, sources,
eseriptions,
addresses ete
by luo. A. Pate, Jocnldo C Ferrer, Temostenes N. Tavares
Compan Hideeeris do Sao France, CHESE, Braz
in functional drawings and vendor
tools, as well as reducing the un
availablity time of the power sys-
tem, From the example in
4, GOOSE messages are also being
‘used for achieving physical redun
ancy from logical messages, with
some configuration efforts but no
extra cable costs
Lessons Learned
Some difficulties should be ex:
pected in advance, eto the new
conceptsand new features brought
by the IEC 61850 standard, On the
‘other hand, many benefits could be
expected
‘The real applications imple
‘mented in high voltage substations
at Chesfshowed up many diffcul-
tesand beneftsalready forecasted,
‘but they have added some others
thaeshould be highlighted.
Difficulties & Pitfalls: Some
important difficulties were found
5 an example of a GOOSE map
{in the IEC 61850 based practical
applications in SAS:
'W There isa lack of technical
Jmowledge on the standard, om-
puter networks and supporting
tools
Interoperability hasshownto
‘be much more difficult to achieve
than could be expected, Private
contain, non interoperable tools
and different interpretations often
1 Network monitoringis very.
important and there i aneed of
better supervision functionalities
inthe HMTimplementation. Very
important functions bave been m=
plemented using GOOSE messages
snd they mustflow on very reliable
networks. New Human Machine
Tnterface-}1MI functionalities shall
Deimplemented,todetecteventual
‘GO0SE failures and other nework
disturbances
[IG = waver too neRO a weoae
ts oases 4
TEC 61850 Edition 1
defined essential methods
forsystem testing, to
handle isolation to the
physical process.
Im Thereisan exaggerated use of
generic GGIO objects, with loss of
semantics, Sometimes, existing
logical nodes themselves are not
‘used when they are needed. IEC
61850 new edition and more ap-
propriate implementations will
hopefully attenuate that problem
1m Genericand better handling
tools for SCL files are needed to
control and ease importing or ex-
porting, included the integration
‘with SCADA systems
1 Nev Network approachesare
‘necessary for assuring SASarchi-
tecture with high reliability and
fulfilling the desired performance
requirements, RST? redundancy
protocol ispredominant
‘Usual documentation ismiss-
ing in derailed specification and
datapoint routing of messages.Sig-
nallists should be more complete,
‘withthe virtua witing map
1m Traditional documentation
has shown to beinsuffcient, with
TEC61850. Information of GOOSE
‘messagesate sattered through tr-
ditional insufficient documenta-
‘ton different ED toolsand specific
descriptions, So, virtual wiring
‘maps called "GoOOSE Maps” have
bbeen developed, with the informa
tion flow, sources, destinations,
descriptions, addresses etc, a8
shown in Figure 5. Trassociatesthe
Publishers and the subscribers,
their messages, links and
descriptions.
“Eventual pitfills need tobe well
mown and managed accordingly.
Fist pitfalls from IEC 61850 based
‘SAS applications have already been
reported, suchas:
1m Wrong involuntary GOOSE
mapping
Tes
Lbad
systen
isolai
Editio
dition:
derail
produc
andtes
ready
those
Editi
the ch:
Goo
publis
purpo
Ste
im1 (Morethan expected) GOOSE
failures
Side effects from software
‘updates
1 A now need for sc files back
‘upand control
WA strong need forconfigura-
tion revision mechanism, absent in
somelEDs
1 Increased virtual interaction
Deeween IEDs
‘Testing: The IEC 61850 ition
1 had defined essential methods for
system testing, in order to handle
isolation to the physical process.
Edition 2 comes with many ad
ditional feturesand sophisticated
details for implementations in
products, with test bits, testmodes
and testbehavior. Sof, the imple:
‘mented systems didnot seem to be
ready or matured enough roexploit
those features, as fiom Editon 1 or
Edition 2, Performance testing is
now a complex task. Considering
thecharactristics ofthe multicast
GOOSE messages with transient
publishing times, the redundant
network topologies, priority rag-
‘ing, VLAN use, EDs internal pro-
cessing, switch configuration and
ius features etc, message traffic
's difficult to evaluate for testing
purposes and dimensioning. But
etworkcreliablityand the manage-
‘ment of possible message storms
need tobe known, toassure the ex-
pected performance
Despite many tests throughout
the world and Cigré workforces,
thereisaneed to specify morede-
tailed procedures and criteria.
Benefits: Many benefits of
the IEC 61850 standard applica-
tions are already known, such as:
standardization, interoperabilit
>etween different vendor IEDs,
bling reduction, distributed aa
mation, low costs etc
Immediate Benefits.
"TheSAS implementations have
showed additional benefitsas de-
scribed below:
Ac fist, functional testing
seemed to be harder. However, by
using network analysis softwares
(eg, Wireshark), they provided
‘2001 views of messages through
‘network ports. Independent and
vendor tols et software sirmulate
and perform traditional physical
checksinstead
' GOOSE messages can pro-
vvidea good economy with the im:
ited number of 1/0 ports to be
‘reached by hard wires in the EDs
1 Special implementation fea-
tures have been applied, such as
(GOSEon line monitoring, GOOSE
“hatching” and physical edundaney
by logical GOOSE messages. Ie isa
greatadvantage, when compared to
limitations ofthe hard wires
'W The content of the GOOSE
_message has plenty of information
inthe header, which could be used
forextra functionalities, like net-
‘work monitoring, configuration
revision control, validity status,
testbitetc.
m The “Time allowed to live”
eld permits very fastsignal super-
vision in justafew seconds, when
compared to an eventually long
lasting unknown copper miseon-
nection, that could take weeks or
leven months tobe discovered
MAfieranintegration of egacy
SAS with IEC 61850, the hybrid
SAS became prepared forretrofit-
ting the legacy SAS or for new
expansions
As to the IEDs’ inputs and
outputs, cabling structure was re-
duced, overcoming intrinsic
physical limitations. With IEC
(61850, programmable logics and
algebraic operatorscan be processed
Standardization, interoperability
between different vendor IEDs,
cabling reduction, distributed
automation, low costs are some of
the benefits of IEC 61850. |
using also some GOOSE messages
flowingtoand from different IEDs.
‘The above mentioned benefits
are just initial ones. Exploring the
potential ofthe standard will ead to
full bnefitsin the future
Conclusions
TEC 61850 isalready a reality in
electrical systems, with increasing
acceptance and so many successful
practical applications around the
‘world, Mostofthem have been done
innew substations by si
Some multi-vendor ap
already in operation too, although
‘there are reports about interoper-
ability problems.
Migration from legacy systems
tonew IEC61850 based SASisalso
very important. It can provide the
capability for new expansions atthe
substation, solving intial peblems,
‘The implementation of practical
applications with IEC 61850 high-
lighted difficulties and benefits. By
planning and managing these as-
‘pects, an expertise can be buile with
this nev technology. Ie ean avoid
somedifficulties that were fond
‘early stagesand meet the best prac-
tices, providing useful road-mapsto
achieve full benefits,
Looking forward to next imple-
mentacions, the lessons leaned will
‘help to overcome dificulces. Longer
‘term benefitsare certainly expected,
‘with maturation and knowledge i
‘crease by exploring the perspectives
‘ofthenew sandaed, m
Starting from the learning curve, amore solid background is very
important for the near future, emerging with the process bus and
the smart grid scenario.
Bonofts: The sas
inmplementation
have showed up
adaitonal ber
fits as decribed‘by Hovberc fll, Solutions Architect, ISCO,USA
IEC 61850-90-5 g
Cc
%
i &
ain Uverview 9°
wy
a
The article describes the requirements that lead to IEC 61850-90-5, £
overview of the technology, emerging implementation agreements, results of g
initial utility testing, and overall reliability of UDP/IP. 3
IECTR61850-90-5is2protocolfor _ The IEBE request to TEC for _performnancewwithina substation, It Herbert Falko» beer
transmitting digital stateand time C37.118duallogoin August 2009: was revised to 3 msec with the sumone wmiin
synchronized powermeasurement Theduallogorequestwastefusedby publication f1EC61850-Sin 2003
‘over wide area networks enabling IEC since IEC had protocol _ m ThedevelopmentofSampled
implementation of wide area technology (IEC 61850-9-2) that Values, a streaming protocol, to
‘measurement and protection could convey synchrophasor allow high-speed sampled current
and control (WAMPAC) systems information. Thisresultedinajoint and voltage measurements, from.
based on the IEC 61850 protocols task force being formed between CTs and VTs, to be shared with bse" ves 9 she teeta
commonly used in substation IEEE and IEC, which worked on multiple IEDs. The initial ation ser neds ad
automation. The development of _methodologes/agroementsthatled | measurement/delivery rate, =inie sore nh
TECTRG1850-90-5 wasmotivated tochangesinlEEEC37.118andthe according to the UCAlug 9-2LE ype! ety om
bbyseveral majorevents: creation ofIECTR61850-90-5 specifications were 80 ar 256. 0A Soil Yetroes Wi m
W The August 2003blackoutin Besides these events, and samples/eycleforintr-substation |"! Ne vissov ant merenta
theNortheastern United States: The the technical requirements for il Thedevelopmentof security
snalysis ofthis event indicated a supportingsynclnophisors,ECTR standards for IEC 61850, including
need for a well-recognized 61850-90-5 wasalso designed to |GOOSEand Sampled Values. This,
synchrophasor standard that had supporethe performance/usecases development started in 2004 and.
explicit time synchronization/ already supported by the Generic _wascompletedin 2007
time-stampingalgorithms.Thiswas Object Oriented Substation Event Ml In 2005, the work to use
themajorimpetusforthecreationof (GOOSE)and Sampled Values(SV) 61850 inter-substation and for
IBEE 37.1 18toreplace IEEE 1344 parts of IEC 61850. The history of substation-to-control center
and the Easter interconnect Phasor these requirements dates back to communications was started, but 00) he es E187
Project (EIPP) October 1995, and an integrated thetechnology ofGOOSE remained 3s roe seu eFut
I In May 2005, cyber security timeline/history of GOOSE, SV, non-routablealthough specified for»
requirements were published IEEE Synchrophasors, and the use in these new communication
regudingeritcalascetsthstindicated resulting 90-5 canbe found.atthe architecture/deployments (IEC
need for securing wide zea power _endofthisarte. 661850-90-1 and [EC 61850-90-2)
‘system communications Requirements weredeveloped, In 2003 IEEE began the effort
MH In November 2006, the changed, and added, The inital to transition from IEEE 1344 10
Esstern Interconnect Phasor Project focus of GOOSE and Sampled IEEE C37.118in orderto improve
(G1PP) wascombined with Western Values was on control and_theaccuracy of the measurement,
and Texas initstivesto become the automation applications. Some of of time-synchronized phasor
North American Synehrophasor these requirements were: -measutements (synchrophasors).
Project Initiative (NASPI), which im The development of the Theneed forthisimprovement was
generates technical functional functionalrequirementsforGOOSE based ona post-mortem analysis of
Fequitements for synchrophaser performance. intially, the orginal the 2003 North American blackout.
systems, architecture, and phasor performance requirement was 4 In 2009, when the reques fora dual
rmeasurementunits ‘msecinondertoachieveprotection logo standard was made, the IEEEIEC 61850
An Overview
the major
technological
parts of
FS
6
Figure 4 depicts
The development
of IECTR
61850-90-5 was
motivated by
several events.
€37.118and 1861850 standards
‘were evalated and resulted inthe
‘comparsonshownin table
Prior eo the request for dual
logo the NASPI activity created
many more requirements for
synchrophasor measurement
“These requirements included the
need for secure large scale wide
sea distribution of synchrophasor
information across the North
‘Ameriancontnent. ThejointEC/
IEEE tak forcedevelopeda strategy
to split C37.118 into two pars
‘whileaceommodatinga migration
tolEC61850based technology to
smeetthe NASPL requirements:
IEEE C37.1264: Synchronized
phasor (synchrophasor)
‘measurements for power systems
axe presented Thisstandard defines
Synchrophasors,fequencyandrate
of change of frequency (ROCOF)
‘measurement under all operating
‘conditions. Iespecfes methods for
evaluating hese measorementsand
bypHerbereFll, Solutions Archive, SISCO, USA,
table 1 Comparison of IEEE C37.118 and IEC 61850
Sao obs
Ween to asp)
| ote
a Mistsehpe ona arr
Georoneten te eid
stan oy
| roselare dient id
requirements for compliance with
‘hestandand under both steady-state
snd dynamic conditions Time tg,
nd synchronization requirements
are included. Performance
requzementsare confirmed witha
reference model, provided in etal
‘This document defines 2 phasor
measurement uni (PMU), which
canbeastand-slone physical wit or
4 functional unit within another
plyseal unit Thisstandard doesnot
specify hardware, software, oF 8
method for computing phasors,
frequency, ROCOF
IEEE 037.1182: A method
for real-time exchange of
synchronized phasor measurement
data between power system
tquipment i defined. Iespocfies
tmesagingthatcanbewsed with any
suitable protocol for real-time
commnication betwoen phasor
‘measurement units (PMU), phasor
dataconceotracors (PDC) and other
applications. It defines message
1 Ec TR 61850-90-5 Overview
lec 6185074
lec 61850-7-4 r 1p gos: pscp_) i
‘types, contents, and use. Datatypes
and formats are specified. typical
‘measurement system, a5 well 5,
communication options and
requirements are described
IEEE C37.118.1 remains as
the global standard for defining
the measurement technology
{for synchrophasors while IEEE
37.1182 the IEEE protocol to
addresscurrent system requires
‘enabling IEC TR 61850-90-5 to
Dethe basis fora more scalable, and
secure, protocol to meet NASP
requirements, IECTR 61850-90-5
has normative references to IEEE
€37.118.1 as the method for
‘measuring synchrophasors. The
scope of IECTR61850-90-Sisto:
Enhance the 61850 object,
‘model fr proper representation of
protocol chat can transmit either
‘GOOSE or Sampled Value using
those TEC 61850 Application
Protocol Data Units (ADPUs)
1 Provide migration capability,
from the C37.118, and its typical
encapsulated in an IEC TR
{61850-90-5 session layer, which
provides security and management
via the 90-5 specific Keya
3 Use of data example The Session|
° Protocol Data Unit}
we is transmitted using|
a multicast UDP/IP,
©
(CU __ Distribution Center(KDC) provocl overtheentreSPDU contents, The Interpretation (RFC3547 -GDON,
TEM Theencpsultedappliation signature provided through the GDOI provides the capability of
FE | mesagesare bis’ UDI/P weof.ymmetr:keysbeingapplid the KDC toexchange keys securely
Tulsineceeriessywhichurlithe to crete a cur Hae Megas vi either clients requesting the
Differentiated Service Control _Atthentction ode(HMAG) And Tees of the KDC pushing keys
2 Prottool [DSCP te provide 1P bral the 50-3 scatanie eed Pattie stscitc
5 prioitytaggingso hatthe packets supports the ability to enerypthe GDO1 orginally allowed keys to
é Ielesslikelytobelostduetorouter | SPDU payload content. De associated with IP addresses
2 congestion “The Session Protocol Data ‘only, This prove insuficient for
TW inorderzoconfigurethenew Unit (SPDU) is transmitted using ‘hesecurity model/requitements
transportand contol blocks, the multiast UDE/IP. In the past for 90:5, Therefore, the GDOI
Substation Configuration Langage the use of UDP/IP multicast has protocol was extended vo provide
{SCL}oflEC61850-6wasexended been problematic Gucto the packet ey management based upon
The 90-5 session protocol delivery paths being difficalt to dlestination addressing service and
: provides the capability foconvey determine/configure. Many IP DatSetdefnitions. This allows
: {oupsofGOOSEorSV application —muliasepackersare delivered over jst be assigned and managed
sccon protaca) messages (APDUs) inva single every path thita router supports Ibaedlspoal is delivery vrvice
Sesion Protocol Data Uit(SPDU). In order oad in the control and (eg. GOOSE or SV) even if the
sovdes the Tealsohas the ability to support path determination, IEC TR. destination address and DataSet
secure tunneling ofthe Evhernet_61850-90-5 species the use oF contentsarehesane
spabty to based GOOSE abd SV packets to the Internet Group Management Migration of €37.238.2 to
faite easier exchange between Protocol, Version 3 (IGMP V3 1c 61850905
vey groups sibstationsand controeentersfor_REC'3376). IGMPV3 differs from “There are several aspects of
thecurreny existing GOOSE and previous GMPYersionsin thatthe rigration from IEEE C37.1182 0
fcoose or SVmesages gue) ibscption toa multcast adres TEC61830thatare provided in IEC
In order 10 provide security, canbefltered based upon the source TRE1850-90-5. Koy items that
Sy application theconcept of perfeceforward* TPadressof the publishe- known, provid gradual migration voward
security was implemented. ‘The s“sourefitering” TECO1850 include
a Security paradigm was designed to Through the use of source 1 Changes forIEC61850.6t0
Sow encryption key otation in filtering routers can determine the support the configuration of
apOUs) ina sichamannertharthe subscriber appropiate path() cough which ca7ie2viascL
Ligonciencelveminycinion cedsteer tbe malice Bed 18 Use of GOOSE or SV, inthe
single Session the next Key rotation isto occur _preventingthedlvery fhe packet. context of 90-5, without explicit
(limcToNextkey)andodetectifit_ overall pcsible paths Figure 4). contol blocks interaction being
Protocol Data isoutcfaynewiththacurentkey. The bey managementand Key required, ‘This allows the SCL
TECTR 61850-90-5 security Distribution Center protocol is configirationtobe tized and IEEE
Unie (POU). mandates the use ofa signature based upon Group Domain of C2718. tobe replaced with IEC
4 Free range IP multicast: IGMPv2 and IGMPv3
ss oy esp etn a Ha ie ats
Q ite ashi basse se
=. we
peta est2
>
‘by Heber Falk, Solutions Architect, ISCO,USA
burp
funet
from:
of th
prov:
pbcTRO61850-90-5 withoucrecuiting
the full EC61850-8-1 profile over
‘TCP/IP (c=. MMS)
The use of IEEE C37.118
has resulted in an archizeccural
deployment entity known as 3
Phasor Data Concentrator (PDC)
tobe used inexistingsystems. The
primary purpose of PDCs are to
Povidemorescabbledisributionof
Synchrophusor meastrements since
substation eypealy have limited
communication capability and are
noegenerally capable ofdistribating
the measurements othe required
number ofclints. The othertypcl
purpose of PDC isto provide
measurement time-alignment
function between measurements
from diffrent PMUssothatclients
of chat data are not required to
provide this function (eg. the
PDCisan extension ofthe client
applications). In the realm of IEC
TR61850-90-5, PDCsneed tobe
configured based upon the proxy
modeling capability of 61850 and
SCL IECTRO1850-00-5 contains
cexplici modeling thatsupporsthe
PDCeoncept
‘Another issue being addressed is
thatof implementatonagreements
thatexplicly definohowtotransate
€37.118.2 Information into IEC
61850andhowoutlizelEC61850
Sampled Values to reliably deliver
synchrophasor measurements,
‘These implementations will be
codifed by ECTCS7 WG10,
History: The start of the IEC
61850 GOOSE requirements has
its basis in che introduction of the
ASEA high speed (4 ms) auxiliary
tripping relay. This introduction
cecurred in the mid-1970sand had
adirectimpact on the performance
requirements included in the
EPRI RP 3599 report - known
as the Unility Communication
Architecture (UCA) version 1.0.At
the time there were several parallel
standardization efforts that would
intimeimpactlECTR61850-90-5,
‘Themmjoreffors were:
The pocential standardization
(FUCA intoan IEE standard
rs}
‘The 90-5 session protocol has the
ability to support secure tunneling of
the Ethernet based GOOSE and
SV packets. |
LIEER’s workon synchrophasor
standards. This work tarted before
the publication of IEEE 1344 (crea
1995)and continues today with the
publication of IEEE C37.118.1 and
IEEE C37.1182
HEC's workonEC61850
Ieisimportancto note that the
UCA/IEEEand IECstandardization
activities were attempting £0
address the same issues within che
industry and therefore would have
‘competed with each other gltslly.
In ate 1996, it was agreed to see
ifthe concepts of UCA, including
the use of multicast for high speed
peer-to-peer communication (te.
the original GOOSE), could be
harmonized accepted as part of
TEC61850. The results areevident
today in the fact that IEC 61850
(crea 2004) is an international
5 Relevant events - 1995 and December 2011 {'3,2004) #1" smationl
ema AMO Wer? Ma,
BBB wnbBboe, ound Tre eto
erttnions SUN
fuuosos $2 go2mcqmee
‘atop wrtnatind BO
hose
ee
coset ene
oregon
‘were placed into [EEE Technical
Report (TR) 1550 for posterity.
AS pe BME vc S2ERre mpl withourcoorinaion
‘with IEC, IEEE continued to address
therequirementsofsynchrophasors.
‘The efforts within IBEE acelerated
Wea gene
am a tt Seok due to deficiencies found during
ae eSEsft the analysis ofthe August 2003
nial ad blackout. This effort resulted in IEEE
Tommiypais NPMOmgrerew 134 being superseded by TEEE
37.118. When IEEE published
C37.118, it approached IEC with
atequest for dual log (circa March
2009), IEC rejected the request
for dual log since IEC 61850-9-2
(SV) and GOOSE were both
HE ESocWk venom antenes capable ofcaryingsynchophasot
‘ont CVI Gi Feed
information.
Thistefusal led tothe creation of
UeeiBESEos eH eed joint TaskForce between EEE and
IEC, and thus the beginning of the
development of IEC TR
61850-90-5, Figure 5 shows the
bea: importanc events thar eventually
FDgDEAMD? — NcHeNDRComie produced IECTR 61850-90.5. Mb
Figures 5 shows
the imporant
that eventually
reduced IEC TR
2050-905.
|
|