See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/326047207

Interoperability testing for IEC61850 based substation automation system

Conference Paper · May 2018

DOI: 10.1109/EPE.2018.8395999

CITATION READS

1 997

2 authors:

Mayada Daboul Jaroslava Orságová

Brno University of Technology Brno University of Technology
4 PUBLICATIONS 7 CITATIONS 54 PUBLICATIONS 146 CITATIONS

SEE PROFILE SEE PROFILE

All content following this page was uploaded by Mayada Daboul on 18 March 2019.

The user has requested enhancement of the downloaded file.

 Interoperability testing for IEC61850 Based
Substation Automation System

Mayada Daboul, Jaroslava Orságová

Department of Electrical Power Engineering
Faculty of electrical engineering and communication
Brno, Czech Republic
[email protected], [email protected]

Abstract—Over the last years, the standard IEC 61850 related the switchyard are usually connected to the control
to automation systems within electrical substation has been room via fibre optic cables.
considered as a promising solution to provide better quality of
power supply and to cope the issue of increasing energy demand. The fundamental objective of this standard is to define
IEC 61850 as a communication protocol in the substation functional architecture, communication structure and the
automation provides efficient performance through the exchange substation requirements. Furthermore, it allow the
information in real-time. Moreover, one of the main motivations communication between IEDs and the operation centre
of using this standard is interoperability. However, connecting (vertical communication), between two or more IEDs
several IEDs manufactured by different vendors which are (horizontal communication), and between the process level and
compliant with IEC 61850 standard is not a trivial task. This the IEDs.
paper presents a method for interoperability testing of
multivendor IEDs based on the IEC61850 standard and includes Achieving substation level interlocking, protection / control
the laboratory results of the testing. functions are the most relevant items to ensure interoperability
between IEDs that can be provided by that standard. However,
Keywords— IEC61850; SAS; GOOSE; interoperability connecting several IEDs manufactured by different vendors
which are compliant with IEC 61850 standard is not a trivial
I. INTRODUCTION task.
International Electrotechnical Commission (IEC) issued This paper demonstrates the influencing factors on
IEC 61850 in 2003 as a communication standard for a interoperability between IEDs, also describes the need for
substation automation system. IEC 61850 used firstly in wind interoperability testing. It also presents a method for
power and then on hydroelectric power plants and on interoperability testing of multivendor IEDs and includes the
Distributed Energy Resources (DERs) [1]. Substations used hardware and software.
Automation Systems (SAS) has been used in modern
substation based on communication protocol standard IEC II. GOOSE MESSAGES
61850 that facilitates the interoperability among third-party
IEC61850 defined generic substation events (GSE) model
IEDs. Moreover, IEC 61850 has used in protection schemes to
to transfer event data between connected IEDs over substation
enhance the stability and the power quality of the system by
networks. GSE ensure that the same event message will be
very fast fault clearing for different faults.
received by single or multiple IEDs through multicast Ethernet
Electrical substation have developed thanks to this standard services. The GSE control model can be presented by two
features which can mention some of them: types of events. First is generic object oriented substation
events (GOOSE) that composed of status and analogue data
 Low project costs including installation, and (dataset) directly embedded into Ethernet data packets. Second
maintenance of automation systems and is generic substation state events (GSSE), which involves only
protection/control schemes. status data that included directly into Ethernet packets [2].
 Increasing the system reliability through direct access GOOSE messages allow the communication between IEDs and
to all local and remote substation control points and the process level. In another words, Current Transformers
replacing the centralized Remote terminal unit (RTU). (CTs) and Voltage Transformers (PTs) located at process level
can be associated with merging units that publish GOOSE
 Simplification the communication infrastructure messages including voltage and current samples to the devices
between IEDs. at bay level. GOOSE messages have replaced the hard wired
signals exchanged between IEDs for interlocking and
 Getting rid of electromagnetic interference in the
protection purposes. GOOSE message delivers the IEDs
control room in case of utilising a merging unit or
indication that a new event has occurred and the time of event
optical transducer technologies; where merging units in
This research work has been carried out in the Centre for Research and
Utilization of Renewable Energy (CVVOZE). Authors gratefully
acknowledge financial support from the Ministry of Education, Youth and
Sports of the Czech Republic under NPU I programme (project No. LO1210
Energy for Sustainable Development) and BUT specific research
programme (project No. FEKT-S-17-4784 New Technologies for
Sustainable Power Engineering II).

978-1-5386-4612-0/18/$31.00 ©2018 IEEE

 occurrence. IEDs receive the information of message and SCL file is classified based on its purpose into four types as
accordingly react appropriately. (in IEC 61850 edition 1):
Functions performed using GOOSE messages are very  IED Capability Description (ICD) file: It includes
important; therefore the performance conditions most to be the activated items function, logic settings, and
very strict. In another words, the implementation of high-speed input/output of analogue/digital contacts of the
peer-to-peer communications should be equal to or better than device. This file is usually supplied by an
values recommended by existing technology. IEC61850 independent tool of each manufacturer to complete
defines that the total peer-to-peer time should not exceed 4 ms the system configuration.
[3].
 Configured IED Description (CID) file: It is used
Proceeding from the importance of the functions used to communicate an IED configuration tool to an
GOOSE (e. g. Breaker Failure Protection BFP), GOOSE IED.
messages should be very high reliable to ensure the correct
reception of the message by IEDs and the proper execution of  System Specification Description (SSD) file: It
orders as expected. High level of reliability can be achieved by includes full SAS specification such as single line
repeating the messages during the situation continuation. diagram for overall substation, its functionalities
(logical nodes) and communication systems.
GOOSE message is alive during particular parameter
known as “hold time” after which the message is cancelled  Substation Configuration Description (SCD) file:
unless the same status message is repeated or a new message is Complete data description file of overall
received before the expiration of the hold time. Initial GOOSE substation. It contains substation, communication,
message is repeated during a short time (a few milliseconds) IED and Data type template sections. SCD file can
but subsequent messages have an increase in repeat and hold be made by contribution by a SSD file and
times until a maximum is reached. In addition, GOOSE different ICD files.
message has all required protection scheme information for IEC 61850 edition 2 has introduced two file types as:
individual IED to achieve high speed performance and reduce
the network traffic during harsh fault conditions [4].  Instantiated IED Description (IID) file: This file is
used as data exchange format from the IED
GOOSE messages is transferred over the substation local configuration tool to the System Configuration
area network by embedding into Ethernet data packets. The Tool (SCT). It contains only the data for the IED
Virtual Local Area Network (VLAN) tagging is used on being configured.
Ethernet frame to identify which VLAN the frame belongs to,
meaning that Ethernet frames from one VLAN will not be  System Exchange Description (SED) file: This is
transmitted onto another VLAN. an information file exchanged between several
substations due to the need of tele-protection
III. SUBSTATION CONFIGURATION LANGUAGE functions among many SASs. It describes the
interfaces of one SCD to be used by another IEC
Abstract configuration languages describe how components 61850 project. It is a subset of an SCD file with
are really associated with each other. Two of these additional engineering rights for IED and the
configuration languages have been used in the utility industry ownership of SCL data.
such as:
The standard provides these set of files with a suggested
a. Substation Configuration Language (SCL) for the use, and enables the user to determine the tools based on their
configuration of devices within substations. specification to the vendor. Each of ICD, CID and IID files can
b. Common Information Model (CIM) for the total be created by the IED Configuration Tools of the particular
configuration of the power system, from corporate vendor.
proprietorship through the lines, substations, and
feeders, down to the client destinations. IV. CONFORMANCE AND INTEROPERABILITY TESTING
SCL means that the configuration of the substation can be
Conformance Testing
modelled electronically using object models, not just by the
data in the substation. This model shows how each device Conformance testing is a part of the product testing. It is a
inside a substation is actually interconnected electrically with test of communication interfaces type. Conformance test is
the other devices. usually performed by the vendor itself in order to determine
whether the product conforms to the specifications of the
IEC 61850-6-1 specifies a SCL based on the eXtensible standard.
Markup Language (XML) to describe exchanging information
between different proprietary configuration tools for substation IEC 61850 defined what items are necessary to be
devices. Every proprietary tool should permit export IED examined during conformance testing and then Utility
description into SCL file [5]. Communications Architecture (UCA) illustrates how the tests
are conducted in their testing procedures followed in all
SCL file typically contains data, logical nodes (functions) certified test facilities. [6].
and communication profile of the configured device.
 Part 10 of IEC61850 specified the conformance tests that connections through Ethernet network of the
rely on exchanging the messages between a test system and the substation.
device under test (DUT). The approach of these tests is based The importance of interoperability testing of multivendor
on that a selection of test messages have been published from IEDs can be attributed to the fact that conformance testing does
the test system to DUT as well as recording the tested device not guarantee the desired interoperability due to the differences
response to these messages. Furthermore, IEC61850-10 defines of IEDs communication profiles. Interoperability tests can be
the performance tests for communication latency and time categorized based on vendors as:
synchronization. Conformance testing has decreased the
amount of issues related to integration, site commissioning and  Single-vendor multi-device interoperability tests:
operation in the substation. consists of several IEDs belonging to the same
manufacturer and communicate to each other devices
Performance tests demands evaluation of the processing in the same platform. In addition, all devices are
time of I/O of the tested device. Also, realisation a standardized usually compatible with the IEC 61850 and are
testing process applied to all hardware and software configured by proprietary Device configuration tool
configurations is not a cushy matter. Thus, UCA excluded (DCT).
performance test (e.g. testing GOOSE latency) due to the
complexity and obscurity the performance testing goals defined  Multi- vendor multi-device interoperability tests:
in IEC 61850-5 such as time synchronization, check GOOSE consist of devices and systems manufactured by
performance, examine SCL (ICD & SCD) schemas and different vendors and communicate to each other via
communication services. Resulting in a case in which the event different platforms. It is usually needed DCTs also a
transfer time is much longer than 4ms the time limit for system configuration tool (SCT) for data flow
control/ protection trip signals class P2/3. Thus, conformance engineering.
testing is a prerequisite for ensuring the proper performance of
Electrical devices can interoperate in all substation levels; it
IEC 61850 system but not sufficient.
means that such IEDs of bay level can interoperate with each
From above can say that, interoperability testing is other as well as can interoperate with devices and systems at
important to decrease the risk of delays of peer-to-peer the station level (e.g. HMI, Data warehouse). Interoperability
communication due to incompatibilities. In other words, tests can be assorted on the basis of the substation hierarchy as
conformance tests help vendors discover early problems of the follows:
product during development phases, while interoperability
testing is the next step after conformance test to obtain a  Horizontal interoperability test: includes many IEDs
guarantee that IEC 61850 system will interoperate as it should. located at the bay levels connected via a
connectionless-oriented Ethernet. It is necessary to
Briefly can be said that conformance tests offer to the verify all point-to-point connections and interaction of
customers a percentage of confidence that devices passed the distributed function as designed.
conformance test may interoperate together. Thus,
Interoperability is a key issue of integrating IEC61850.  Vertical interoperability test: involves devices located
at the bay level and station level. IEDs at bay level (as
server) can communicate with IEDs at station level (as
Interoperability Testing
client) via a connection-oriented client-server profile.
IEC 61850 only defined the conformance testing unlike the
interoperability testing that is undefined.
V. INTEROPERABILITY IEC61850 CHALLENGES
Interoperability is the ability of many multivendor IEDs to
1) Different Application
share information used to perform applications for proper
Although the standard has defined standardized logical
cooperation between the different IEDs. Interoperability testing
nodes (LNs), data and data attributes (DAs), it has also allowed
includes network connections among IEDs and application
manufacturers to create optional LNs, generic logical nodes
functions related to information exchange. This testing
(GGIOs) for difficult cases to deal with standard models. This
provides a guarantee to the end-client that the system will
difference in the private data models included in manufactured
interoperate properly. [7].
IEDs leads to the fact that devices are not able to interoperate
Interoperability tests can be classified on the basis of the with each other even though they are on compatibility with IEC
purpose of the test as follows: 61850.

 Proof-of-concept interoperability test: aims to 2) Different Interpretations

verify the communication interfaces between
As mentioned before that IEC 61850-6 defined tow type of
various IEDs for ensuring the ability of IEDs to IED Description.
communicate with each other. The features of
this test are the simplicity of connections Firstly, ICD file containing default addresses of the IED. It
between the IEDs and non-testing of also contains described IED capabilities only, and the IED
interoperability functions.. name shall be TEMPLATE. In addition, needed data type
templates including logical node type definitions are included
 Site acceptance interoperability test: aims to in this file. So it can notice that ICD file has no specific
verify all virtual point-to point logical
information required for an application. Secondly, CID file the IED such as GOOSE messages that will be published/
describing IED in a specific project with all exchanged subscribed by a certain IED.
GOOSE messages, and a specific IED configuration
information including IED address. Each IED configuration tool is provided by the
manufacturer for configuration IED parameters and accessing
Vendors have been finding that selecting CID or ICD files to all supported functions. The final configuration is done by
for data exchange is ambiguous because of differing the proprietary tool and can be either as a proprietary format or
interpretations the IEC 61850 Standard. Thus, they have a standard CID format. Nowadays many vendors have decided
divided into two groups about what should SCL file be ICD or to have a CID file using a proprietary format while a few
CID? Other words, different interpretations have led to vendors create the CID file similar to the ICD file.
different implementations and interoperability issue.
Finally, after the IED configuration, an ICD or CID file is
3) Communication Profiles exported. Some of the manufactured IEDs only export an ICD
IEC 61850 defined that IEDs communications can be file while others export a CID file. Technically, these two file
formed based on five sorts of communication profiles such as types are similar but the difference is how each one is
Abstract Communication Service Interface profile (ACSI), generated. Thus, this creates a challenge with the entire system
Generic Object Oriented Substation Event profile (GOOSE), configuration.
Generic Substation Status Event profile (GSSE), Sampled
Measured Value multicast profile (SV), and Time VII. EXPERIMENTAL TESTBED
Synchronization profile. The communication profiles In order to give a clear description of the interoperability
implemented in IEDs are different among various vendors that issue, a physical connection between the systems devices
have all conformed to the standard whilst may not be shown in Figure 2. The basic components of the
interoperable to each other. interoperability testing are protection IEDs, Ethernet switches
and PC. IEDs totally are from different vendors.
VI. CONFIGURATION OF IEC61850-IEDS
The main of configuring IEDs is to obtain the SCL files
necessary for system configuration. This SCL files is come in
either ICD or CID formats that will export after IED
configuration [8].

Fig. 2. Typical System Connection

According to the experience the first step is to configure the

Relay A to send a GOOSE message as defined in the Dataset
using the DCT. By configuring individual IED type A can then
Fig. 1. Substation Engineering Process
obtain the ICD file. In a similar way, the relay type B is
IED can be configured by a manufacturer’s particular IED configured by its specific DCT and get its CID file not ICD
configuration tool. Advanced configuration tools for some file.
manufacturers can be used at the same time as IED and system
System configuration tool is used to define GOOSE
configurators.
mapping (publisher/subscriber) and generate SCD file as in
Fig. 1 shows that ICD file must be imported into the IEC Fig. 3. This SCD is exported to each relay tool and enable
61850 system configurator that then creates SCD file. Relay type B to be configured as a receiver for GOOSE
Control Block (GCB) from Relay type A and extract the
The SCD file can include the one line diagram of the substation information that associated with these messages, execute the
with the description of the GOOSE. IED Configuration Tool is internal functions and publish another GOOSE messages to the
used to import SCD file and extract the information needed for communication network. Similarly, Relay type A is configured
to receive the second GOOSE from Relay type B. After
configuration each relay, CID must uploaded to the physical explains how the time communication is different between
protection devices. GOOSES and wired analogue signals. It is important to keep in
our mind that the logical nodes from which the GOOSE is
being published can cause an inherent time delays. Thus, a
simple test required to verify that there is no inherent delay.
To make the test connections for the hardwire test, the
outputs of the relays are wired to the inputs of the other relay.
After several attempts, the average value of wired connection is
28ms.
From the above we conclude that IEC 61850 has reduced
the copper wiring as well as GOOSE messages are much faster
than traditional hardwire communication.

CONCLUSION
Fig. 3. System configuration IEC 61850 is widely used today, with hundreds of
Network analyser is used to sniff the network and capture substations already in service; this standard is accompanied
the network messages as is displayed if Fig. 4. with some of challenges arising from lack of knowledge about
this standard. Wherefore, it is important to understand the
basics of IEC 61850 and also learn each IED’s configuration
tools in order to reduce the IEC 61850 issues during
configuring process into protection schemes.
Some of IEC 61850 challenges has discussed. It was
figured out that differences in IED configuration tools lead to
many configuration issues such as import or export errors of a
specific SCL type file.
Lastly, it has been shown the timing test comparison
between a hardwired relays contacts and GOOSE messages
and it has been concluded that GOOSE is faster than traditional
wiring as expected.

REFERENCES
Fig. 4. Captured GOOSE messages in the network [1] A. Hadbah, T. S. Ustun and A. Kalam, “Using IEDScout software for
managing multivendor IEC61850 IEDs in substation automation
GOOSE communication time delay has measured to verify systems,” 2014 IEEE International Conference on Smart Grid
Communications (SmartGridComm), Venice, 2014, pp. 67-72.
the compatibility of each relay with IEC 61850.
[2] G. Manassero, E. L. Pellini, E. C. Senger and R. M. Nakagomi,
After several attempts of changing the initial status of the “IEC61850–Based Systems—Functional Testing and Interoperability
data (Tab. 1), the delay time of GOOSE message had an Issues,” in IEEE Transactions on Industrial Informatics, vol. 9, no. 3, pp.
1436-1444, Aug. 2013.
average value 2.7 ms.
[3] M. Daboul, J. Orsagova, T. Bajanek and V. Wasserbauer, “Testing
protection relays based on IEC 61850 in Substation Automation
TABLE I. DELAY COMMUNICATION TIME FOR GOOSE AND WIRED SIGNAL Systems,” 2015 16th International Scientific Conference on Electric
Delay GOOSE Time Delay Wired Connection Time Power Engineering (EPE), Kouty nad Desnou, 2015, pp. 335-340.
(ms) (ms) [4] A. Apostolov, “Impact of IEC 61850 on the interoperability and
reliability of protection schemes,” 2013 IEEE Power & Energy Society
1 2.1 32
General Meeting, Vancouver, BC, 2013, pp. 1-5.
2 3.4 32 [5] R. Aguilar and J. Ariza, “Testing and configuration of IEC 61850
multivendor protection schemes,” IEEE PES T&D 2010, New Orleans,
3 3.1 32.5 LA, USA, 2010, pp. 1-8.
4 2.8 21 [6] J. C. Tan, C. Zhang and Z. Q. Bo, “The importance of IEC 61850
interoperability testing,” 2008 43rd International Universities Power
5 2 20 Engineering Conference, Padova, 2008, pp. 1-5.
[7] J. C. Tan, V. Green and J. Ciufo, “Testing IEC 61850 based multi-
VIII. COMPARISON OF WIRED AND GOOSE SIGNAL vendor substation automation systems for interoperability,” 2009
IEEE/PES Power Systems Conference and Exposition, Seattle, WA,
As a result of the fact that many customers have a reticence 2009, pp. 1-5.
of to switch over to GOOSE messaging for tripping or even B. Stojcevski and A. Kalam, “Multi-vendor portable IEC61850 testing
performing control functions, many installations of substations unit,” 2011 IEEE PES Innovative Smart Grid Technologies, Perth,
WA, 2011, pp. 1-8
that are based on IEC 61850 are also hardwired. This section

View publication stats