energies

Article
Auto-Mapping and Configuration Method of
IEC 61850 Information Model Based on OPC UA
In-Jae Shin 1 , Byung-Kwen Song 2, * and Doo-Seop Eom 1
1 Department of Electrical Engineering, Korea University, Seoul 02841, Korea; kshinje@korea.ac.kr (I.-J.S.);
eomds@korea.ac.kr (D.-S.E.)
2 Department of Electrical Engineering, Seokyeong University, Seoul 02173, Korea
* Correspondence: bksong@skuniv.ac.kr

Academic Editor: Gianfranco Chicco

Received: 24 June 2016; Accepted: 20 October 2016; Published: 1 November 2016

Abstract: The open-platform communication (OPC) unified architecture (UA) (IEC62541) is

introduced as a key technology for realizing a variety of smart grid (SG) use cases enabling relevant
automation and control tasks. The OPC UA can expand interoperability between power systems.
The top-level SG management platform needs independent middleware to transparently manage
the power information technology (IT) systems, including the IEC 61850. To expand interoperability
between the power system for a large number of stakeholders and various standards, this paper
focuses on the IEC 61850 for the digital substation. In this paper, we propose the interconnection
method to integrate communication with OPC UA and convert OPC UA AddressSpace using system
configuration description language (SCL) of IEC 61850. We implemented the mapping process for
the verification of the interconnection method. The interconnection method in this paper can expand
interoperability between power systems for OPC UA integration for various data structures in the
smart grid.

Keywords: open-platform communication (OPC) unified architecture (UA); IEC 61850; system
configuration description language (SCL); abstract communication service interface (ACSI); smart grid

1. Introduction
In the energy field, smart grids are a much-discussed topic. Many views on smart grids exist,
which has led to many definitions of what is understood as a smart grid [1,2]. Power information
technology (IT) protocols have a complicated network configuration because of the presence of a
variety of protocols. The open-platform communication (OPC) unified architecture (UA) (IEC62451)
middleware has a simple network configuration because it can be integrated into a single protocol. OPC
UA is the communication protocol for the smart grid (SG) application platform. It was standardized
by the IEC TC57 group in December 2008. The abstract approach of the OPC UA enables extensions of
the application area, so the focus is on general data exchange within any domain, and it can be used
for integrated automation concerns [3–5].
The IEC 61850 is the communication protocol and the substation’s service model. It has been used
in digital substation systems and smart distributed systems. The top-level SG management platform
needs independent middleware to transparently manage power IT systems. Interconnection modules
between power IT and OPC UA in the top-level SG management system have to be developed to
manage the supervisory control and data acquisition (SCADA) protocol [6–8].
In this contribution, we focus on communication technology mappings of the IEC 61850 and
introduce the OPC UA as an alternative way of communication based on the IEC 61850 model.
We designed mapping between OPC UA AddressSpace and IEC 61850 model information using UA’s
UaModeler. We implemented System Configuration description Language (SCL) for the OPC UA

Energies 2016, 9, 901; doi:10.3390/en9110901 www.mdpi.com/journal/energies

Energies 2016, 9, 901 2 of 16
Energies 2016, 9, 901 2 of 16

UaModeler. We implemented System Configuration description Language (SCL) for the OPC UA
AddressSpace module.
AddressSpace module. We We converted
converted all
all the
the SCL
SCL files
files to
to the
the OPC
OPC UA UA AddressSpace.
AddressSpace. We We verified
verified IEC
IEC
61850 model mapping onto OPC UA using KEMA’s UniCA IED (level A certificate) ServerSimulator.
61850 model mapping onto OPC UA using KEMA’s UniCA IED (level A certificate) Server Simulator.
OPC
OPC UAUA was
wasdeveloped
developedusing
usingUA’s
UA’sUaModeler
UaModeler and
anda C++-based
a C++-based system development
system kit. The
development kit.
The IEC 61850 client module was developed using SISCO’s MMS-EASE Lite library, and the IEC 61850
IEC 61850 client module was developed using SISCO’s MMS-EASE Lite library, and the IEC 61850
server was
server was using
using KEMA’s
KEMA’s UniCA
UniCA IEDIED (intelligent
(intelligent electronic
electronic device)
device) simulator.
simulator.
The paper is
The paper is organized
organized asas follows.
follows. In
In Sections
Section 2, 2.1we
anddiscuss
2.2, wePower IT Power
discuss Protocols—the OPC UA
IT Protocols—the
(IEC62451) and IEC 61850 standards. In Section 3, we outline the IEC 61850 model
OPC UA (IEC62451) and IEC 61850 standards. In Sections 2.3 and 2.4, we outline the IEC 61850 mapping onto OPC
UA. Section 4 outlines the experimental results and performance evaluation. Section
model mapping onto OPC UA. Section 3 outlines the experimental results and performance evaluation. 5 concludes the
paper and
Section shows some
4 concludes the future perspectives.
paper and shows some future perspectives.

2. IEC
2. IEC61850
61850Model
ModelMapping
Mappingonto
ontoOPC
OPCUA
UA

2.1. OPC UA (IEC62451) Standard

OPC UA (IEC62451)
(IEC62451) was was standardized
standardized by by the IEC TC57 group in December December 2012. 2012. The classic
OPC was separated
separated into
intoOPC
OPCData
DataAccess
Access(DA),(DA),OPCOPCHistorical
HistoricalData
DataAccess
Access(HDA),
(HDA), OPC OPCAlarms
Alarms &
Conditions
& Conditions (AC),
(AC),andandOPCOPCExtensible
ExtensibleMarkup
MarkupLanguage
Language(XML).(XML).The The classic
classic OPC
OPC features
features were
integrated into OPC UA. UA. Additionally,
Additionally, service-oriented
service-oriented architecture
architecture (SOA)
(SOA) was
wasadded
addedto toOPC
OPCUA UA[3].
[3].
The information
informationmodel modelofofintegrated
integrated OPCOPC UAUA is shown
is shownin Figure 1 [4].1The
in Figure [4]. classic OPC can
The classic OPC be
builtbeonbuilt
can topon oftopthe OPCOPC
of the UA-based
UA-basedinformation
informationmodel.model. Vendor-specific
Vendor-specific modelsmodels and
domain/technology-specific models models can be built
built on top
top ofof the
the OPC
OPC UA-based
UA-based information model and
the classic OPC, exposing their specific information via OPC UA. OPC UA AddressSpace, provided
by OPC UA, is defined along with general information models based on object type. All information
models using OPC UA define the following: (i) the entry points into the address space used by clients
to navigate
navigate through
throughthe theinstances
instancesand
andtypes
types ofof
OPCOPC UAUA servers; (ii) (ii)
servers; the the
basebase
types that that
types buildbuild
the root
the
for the
root fordifferent typestypes
the different of hierarchies; (iii) the
of hierarchies; (iii)built-in but extensible
the built-in typestypes
but extensible (i.e., object typestypes
(i.e., object and data
and
types);
data and and
types); (iv) (iv)
the the
server object
server that
object provides
that provides capability
capabilityandanddiagnostic
diagnosticinformation.
information. OPC OPC UA
information models, as well as complex models, can provide simple information. The base modeling
concepts of OPC UA are nodes and references between nodes. Each node contains attributes, such as
ID and name.

Figure 1. Information
Figure 1. Information model
model of integrated OLE
of integrated (object linking
OLE (object linking and
and embedding)
embedding) for process control
for process control
OPC unified architecture (UA).
OPC unified architecture (UA).

OPC UA software layers are shown in Figure 2. The complete software stack can be implemented
OPC UA software layers are shown in Figure 2. The complete software stack can be implemented
with C, .Net, or JAVA. OPC UA is not limited to these programming languages and development
with C, .Net, or JAVA. OPC UA is not limited to these programming languages and development
platforms, however, only these environments are currently used for implementing the OPC
platforms, however, only these environments are currently used for implementing the OPC foundation
foundation UA stack deliverables [9].
UA stack deliverables [9].
Energies 2016, 9, 901 3 of 16
Energies 2016, 9, 901 3 of 16

Energies 2016, 9, 901 3 of 16

Figure 2.
Figure 2. OPC
OPC UA
UA address
address space.
space.
Figure 2. OPC UA address space.

Figure 3 shows the OPC UA AddressSpace. The AddressSpace model specifies the building
Figure
Figure 3 shows
3 shows the OPC
the OPC UA AddressSpace.
UA AddressSpace. TheThe AddressSpace
AddressSpace model
model specifies
specifies thethe building
building blocks
blocks to expose
blocks to instance
expose and
instance andtype
typeinformation
information and
and thusthe
thus theOPC
OPCUA UA meta-model
meta-model usedused
to to describe
describe
to expose instance and type information and thus the OPC UA meta-model used to describe and expose
and expose
and exposeinformation
information models
models and toto build the OPC UA UAserver
serverAddressSpace.
AddressSpace. The OPCOPC UA UA
information models and to build theandOPC UAbuildserver
the OPC
AddressSpace. The OPC UAThe AddressSpace is
AddressSpace
AddressSpace is modeled
is modeled as as
a set
a setofofnodes
nodes that are accessible
that are accessiblebybyOPC
OPC UAUA clients
clients using
using OPCOPC UA UA
modeled as a set of nodes that are accessible by OPC UA clients using OPC UA services. The nodes in
services. The The
services. nodes in the
nodes AddressSpace
in the AddressSpaceare areused
used to represent
representreal
real objects,
objects, their
their definitions,
definitions, and their
and their
the AddressSpace are used to represent real objects, their definitions, and their references to each other.
references to each other. The view is a specific subset of the AddressSpace that
references to each other. The view is a specific subset of the AddressSpace that is of interest is of interest to theto the
The view
OPC is
UA a clients
specific subset of the AddressSpace that is of interest to the OPC UA clients [10].
[10].
OPC UA clients [10].

Figure 3. OPC UA AddressSpace.

Figure 3. OPC UA AddressSpace.
2.2. IEC 61850 Standard Figure 3. OPC UA AddressSpace.
2.2. IEC 61850 Standard
IEC 61850 is a communication standard for electrical substation automation systems. It is the
2.2. IEC 61850 Standard
IEC 61850
standard is a communication
protocol standardsystems
used in digital substation for electrical substation
and smart distributedautomation
systems. Thesystems. It is the
goal of the
IEC 61850
standard 61850
protocol is aused
series communication
is toinprovide standardsystems
digital interoperability
substation for electrical
between andthe substation
IEDs
smart automation
from different
distributed systems.
suppliers
systems. or,goal
The It of
more is the
IEC precisely,
standard
61850 between
protocol
series to functions
isused in digital
provide to be performedsystems
substation
interoperability bybetween
systemsandfor power
smart
the IEDs utility
from automation
distributed systems.
different while
Theresiding
suppliers goal
or, of the
more
IEC in equipment
61850 series from
is to different
provide suppliers. IEC
interoperability 61850-7 describes
between the the
IEDs relationships
from
precisely, between functions to be performed by systems for power utility automation while residing between
different other
suppliers parts
or, more
of thebetween
precisely, IEC 61850functions
series [11].to be performed by systems for power utility automation while residing
in equipment from different suppliers. IEC 61850-7 describes the relationships between other parts of
The models of the Abstract Communication Service Interface (ACSI) provide [12]:
in equipment
the from different
IEC 61850 series [11]. suppliers. IEC 61850-7 describes the relationships between other parts
• IECmodels
of theThe The definition
61850 series of the
[11]. basic model of the utility
of the Abstract Communication information
Service models
Interface (ACSI)contained
providein[12]:
IEC 61850-7-3
The models of the Abstract Communication Service Interface (ACSI) provide [12]: logical
(common data classes for utility automation applications), IEC 61850-7-4 (compatible
• node classesofand
The definition thecompatible
basic model dataofclasses for utility
the utility automation
information applications),
models containedandin IEC
IEC61850-6
61850-7-3
• The definition
(the substationof the basic
configurationmodel of the
language). utility information
(common data classes for utility automation applications), IEC 61850-7-4 (compatible models contained in IEC 61850-7-3
logical
•
(common
The data
definition classes
of for utility
information automation
exchange service applications),
models. IEC 61850-7-4
node classes and compatible data classes for utility automation applications), and IEC 61850-6 (compatible logical
node classes
(the substation
The following
and compatible
configuration
overall classes
data classes
language). for utility automation applications), and
are defined: Server, Logical Device, Logical Node, and Data Object.
IEC 61850-6
(the substation configuration language).
• The definition of information exchange service models.
• The definition of information exchange service models.
The
The following
following overall
overall classes are defined:
classes are defined: Server,
Server, Logical
Logical Device,
Device, Logical
Logical Node,
Node, andand Data
Data Object.
Object.
Energies 2016, 9, 901 4 of 16

Energies 2016, 9, 901 4 of 16

The IEC 61850 information model is shown in Figure 4. The information model is an abstract
representation
The IEC of61850
the devices inside
information the issubstation.
model The logical
shown in Figure devices (LDs)
4. The information model comprise a virtual
is an abstract
representation
representationof physical devices,
of the devices such
inside theassubstation.
relays or The
bayslogical
in thedevices
substation.
(LDs) An LD includes
comprise a virtualmany
representation
logical nodes (LNs).ofLNs physical devices,
are virtual such as relays or
representations of bays in the substation.
components Ansuch
of devices, LD includes many
as switches, circuit
logical
breakers, nodes
and (LNs).
voltage LNs are
meters. virtual
Data representations
objects of components ofofdevices,
(DOs) are representations such asinformation
the common switches, of
circuit
nodes. breakers,
All devices and avoltage
follow common meters.
naming Data objectseven
scheme; (DOs) aremanufacturer
if the representations of the common
is different, it is possible
information of nodes. All devices follow a common naming scheme; even if the manufacturer is
to access the same device. DOs are typed by common data classes (CDC) from IEC 61850-7-3 or IEC
different, it is possible to access the same device. DOs are typed by common data classes (CDC) from
61850-7-2 [12,13].
IEC 61850-7-3 or IEC 61850-7-2 [12,13].

Figure 4. IEC
Figure 61850
4. IEC 61850information model(Source:
information model (Source:IEC
IEC 61850-7-2).
61850-7-2).

Functional constraints (FC) play a crucial role in the definition of the information models and in
Functional constraints (FC) play a crucial role in the definition of the information models and
the services used to access the various parts of the information model. The FC is not shown in the
in the services used to access the various parts of the information model. The FC is not shown
object reference. The FC information may be mapped into the object reference in a Specific
in theCommunication
object reference.ServiceTheMapping;
FC information may maps
IEC 61850-8-1 be mapped into the the
the FC between object reference
logical node namein aand
Specific
Communication
the data name Service Mapping; IEC 61850-8-1
(Relay1:MMXU1$CF$PhV). FCs maps the FCasbetween
are defined follows: the logical node name
MX—measurements; ST—and the
data name
status; (Relay1:MMXU1$CF$PhV).
CF—configuration; RP—unbuffered FCs arereport
defined as follows:
control MX—measurements;
blocks; LG—log control blocks;ST—status;
BR—
CF—configuration;
buffered report RP—unbuffered report control
control blocks; GO—Generic blocks;
Oriented LG—log
Object System control
Event blocks;
(GOOSE) BR—buffered
control blocks;report
GS—Generic Substation Status Event (GSSE) control blocks;
control blocks; GO—Generic Oriented Object System Event (GOOSE) control blocks; SV—substituted values; SE—setting
GS—Generic
group Status
Substation editing Event
[14]. (GSSE) control blocks; SV—substituted values; SE—setting group editing [14].
The language
The language for for
thethe configurationofofelectrical
configuration electrical substation
substationIEDs IEDsis is
called System
called Configuration
System Configuration
description Language (SCL) [15]. It is used to describe IED configurations and communication
description Language (SCL) [15]. It is used to describe IED configurations and communication systems
systems according to IEC 61850-5 and IEC 61850-7. It allows the formal description of the relations
according to IEC 61850-5 and IEC 61850-7. It allows the formal description of the relations between the
between the utility automation system and the process (substation, switchyard).
utility automation system
Table 1 shows andgroups
all the the process
in the (substation,
logical node switchyard).
defined in IEC 61850-7-4 [16]. This group is
Table
defined as approximately 90 logical nodes, such asnode
1 shows all the groups in the logical definedapplications
the common in IEC 61850-7-4 [16].
and supply This group is
of substation
defined as approximately
equipment. One major 90 logical
focus is thenodes, suchofasinformation
definition the common applications
models and supply
for applications of to
relating substation
the
equipment. One
Protection andmajor focus is the definition
Protection-related. of information
The two groups constitute models
almost halffor of
applications relating
the logical node. Thisto the
showsand
Protection the high importance of the
Protection-related. TheProtection
two groupsfor the safety and
constitute stablehalf
almost operation of the power
of the logical node.system.
This shows
the high importance of the Protection for61850
Table 1. IEC the safety
logical and
node stable operation
(LN) groups [16]. of the power system.

Table
Logical 1. IEC
Node 61850 logical nodeNumber
Groups (LN) groups [16].Nodes
of Logical
System logical nodes 3
Protection
Logical Node functions
Groups Number of 28Logical Nodes
Protection related functions 10
System logicalcontrol
Supervisory nodes 53
Protection functions
Generic references 28
3
Protection related
Interfacing functions
and archiving 10
4
Supervisory control
Automatic control 45
Generic references
Metering and measurement 83
Interfacing and archiving 4
Automatic control 4
Metering and measurement 8
Energies 2016, 9, 901 5 of 16

Table 1. Cont.

Logical Node Groups Number of Logical Nodes

Energies 2016, 9, 901 5 of 16
Sensors and monitoring 4
Switchgear
Sensors and monitoring 42
Instrument transformer
Switchgear 22
Power transformer
Instrument transformer 24
Further power
Power system equipment
transformer 15
4
Total number
Further power of logical
system nodes
equipment 92
15
Total number of logical nodes 92
2.3. Design of OPC UA AddressSpace for IEC 61850
2.3. Design of OPC UA AddressSpace for IEC 61850
Figure 5 shows the whole design flow of OPC UA AddressSpace for IEC 61850. First, the engineer
Figure 5 shows the whole design flow of OPC UA AddressSpace for IEC 61850. First, the
has toengineer
define IEC 61850 logical node type using UA’s UaModeler—Section 2.3. Second, the user needs
has to define IEC 61850 logical node type using UA’s UaModeler—Section 2.3. Second, the
to generate IECto61850
user needs logical
generate IEC node
61850 instance using
logical node SCL using
instance to OPC
SCLUA AddressSpace
to OPC Tool—Section
UA AddressSpace Tool— 2.4.
IEC 61850
Section 2.4. IEC 61850 logical node type source file and IEC 61850 logical node instance source file the
logical node type source file and IEC 61850 logical node instance source file represent
IEC 61850 information
represent in OPC
the IEC 61850 UA. in OPC UA.
information

Figure 5. The whole design flow.

Figure 5. The whole design flow.
OPC UA provides extensible information models. The information models of OPC UA are
OPC
mappedUAafter
provides extensible
generating information
the abstract models. TheTherefore,
object on AddressSpace. information
the IECmodels
61850 of OPC UA are
information
model
mapped hasgenerating
after to be modeled
theonto OPC UA
abstract AddressSpace.
object The following
on AddressSpace. describes
Therefore, the how
IEC the IEC16850
61850 is
information
modelmapped
has to to
bethe OPC UA
modeled AddressSpace.
onto OPC UA AddressSpace. The following describes how the IEC16850 is
mapped to The
themapping
OPC UA ofAddressSpace.
the IEC 61850 information model onto OPC UA AddressSpace is shown in
Figure 6 [1]. The OPC UA AddressSpace changes the model from the IEC 61850 information to the
The mapping of the IEC 61850 information model onto OPC UA AddressSpace is shown in
IEC62541 information. Then, it has and holds as nodes on AddressSpace.
Figure 6 [1]. The OPC UA AddressSpace changes the model from the IEC 61850 information to the
To structure the objects, three standard UA reference types are used [2]:
IEC62541 information. Then, it has and holds as nodes on AddressSpace.
– structure
To HasComponent describes
the objects, threepart of theUA
standard relationship
referencebetween LNused
types are and [2]:
its attributes as well as
between CDC and its attributes. Furthermore, it is used for the grouping by FC.
- – Organizes
HasComponent is describes
used to group
partthe CDC
of the attributes bybetween
relationship FC. LN and its attributes as well as between
– HasTypeDefinition connects the LN attributes with the according CDC.
CDC and its attributes. Furthermore, it is used for the grouping by FC.
- Organizes is used to group the CDC attributes by FC.
- HasTypeDefinition connects the LN attributes with the according CDC.

Mapping example: The model of the XCBR, one of the logical nodes (LNs) of the IEC 61850, using
UA’s Modeler tool can be mapped by reference to Figure 5. The XCBR LN of the IEC 61850 is the circuit
breaker (CB) of the substations or distributed devices [12]. It is mapped to object type because of the
LN class. Additionally, it has many common data classes (CDCs) of the attribute type [11]. CDCs are
modeled to object type. CDCs reference the LN data defined in the IEC 61850. The Single Point Status
(SPS), one of the CDCs, provides status information. The quality of the measured value (q) and the
Figure 6. Mapping of the IEC 61850 information model onto OPC UA AddressSpace.
 OPC UA provides extensible information models. The information models of OPC UA are
mapped after generating the abstract object on AddressSpace. Therefore, the IEC 61850 information
model has to be modeled onto OPC UA AddressSpace. The following describes how the IEC16850 is
mapped to the OPC UA AddressSpace.
Energies 2016, 9, 901
The mapping of the IEC 61850 information model onto OPC UA AddressSpace is shown in6 of 16
Figure 6 [1]. The OPC UA AddressSpace changes the model from the IEC 61850 information to the
IEC62541 information. Then, it has and holds as nodes on AddressSpace.
timestamp of the measured value (t) are modeled to the variable [11]. The predefined data type is
To structure the objects, three standard UA reference types are used [2]:
referred to in Modeler. The XCBR LN has LN data: Loc (local control behavior), EEHealth (external
–
equipment HasComponent describes
health), EEName part of
(external the relationship
equipment name between LN so
plate), and and its attributes
forth, as well as
as the HasComponent.
between CDC and its attributes. Furthermore, it is used for the grouping by FC.
The HasComponent ReferenceType is used, exposing the configuration of a device as a component of
– Organizes is used to group the CDC attributes by FC.
the device. The attribute types of LN refer to the CDC, such as SPS to HasTypeDefinition [1,10].
– HasTypeDefinition connects the LN attributes with the according CDC.

Figure
Figure 6. Mapping
6. Mapping of the
of the IECIEC 61850
61850 information model
information model onto
ontoOPC
OPCUA
UAAddressSpace.
AddressSpace.

Data-type mapping is the most basic information in the rules of mapping. IEC 61850 BasicTypes
are consistent with OPC UA BaseDataTypes. Table 2 shows the data-type mapping table for mapping
the IEC 61850 and OPC UA.

Table 2. Data-type mapping.

IEC 61850 BasicTypes OPC UA BaseDataType

BOOLEAN Boolean
INT8 Number-Integer-Sbyte
INT16 Number-Integer-Int16
INT24 Number-Integer-Int32
INT32 Number-Integer-Int32
INT128 Number-Integer-Int64
INT8U Number-Integer-Uinteger-Byte
INT16U Number-Integer-Uinteger-UInt16
INT24U Number-Integer-Uinteger-UInt32
INT32U Number-Integer-Uinteger-UInt32
FLOAT32 Number-Float
FLOAT64 Number-Double
ENUMERATED Enumeration
CODED ENUM Enumeration
OCTET STRING ByteString
VISIBLE STRING String
UNICODE STRING String

Figure 7 shows ACSI server class mapping. The server class represents the external visible
behavior of a device. It is composed of 1 to N logical device classes. The attribute ServiceAccessPoint
identifies a server within the scope of a subnetwork. The attribute LogicalDevice identifies a logical
device that is contained in a general server. The attribute File identifies a file system included in a
general server. The attribute TPAppAssociation identifies a client with which a server maintains a
two-party application association. The attribute MCAppAssociation identifies a subscriber with which
a server maintains a multicast application association. ServiceAccessPoint is mapped to the variable
node class type. The remaining attributes are mapped to the object node class type [6,10,12].
 Energies 2016, 9, 901 7 of 16
Energies 2016, 9, 901 7 of 16

Figure 7. Abstract Communication Service Interface (ACSI) server class mapping.

Figure 7. Abstract
Figure Communication
7. Abstract CommunicationService Interface(ACSI)
Service Interface (ACSI) server
server class
class mapping.
mapping.

ACSI logical device mapping is shown in Figure 8. The logical device classes comprise three or
ACSIACSI logical
logical device
device mapping
mapping isisshown
showninin Figure
Figure 8.
8. The
Thelogical device
logical device classes
classescomprise
comprisethreethree
or or
more logical
more node classes.
logical node The The
classes. attribute
attributeLDName
LDName unambiguously
unambiguously identifies
identifies an an instance
instance of a of a logical
logical
more logical node classes. The attribute LDName unambiguously identifies an instance of a logical
device within
devicethe scope
within of a subnetwork.
the scope of a subnetwork. The
Theattribute LDRef
attribute LDRef identifies
identifies the reference
the reference
device within the scope of a subnetwork. The attribute LDRef identifies the reference path of a logical
path of path of a logical
a logical
device devicethe
within within
scopethe scope
of a of a subnetwork.
subnetwork. Theattribute
The attribute LogicalNode
LogicalNode is a list
is aoflist
all logical
of all nodes that
logical nodes
device within the scope of a subnetwork. The attribute LogicalNode is a list of all logical nodes that that
are contained in a general logical device class. LDName and LDRef are mapped to the variable Node
are contained
are containedin a general logical device class. LDName andLDRef
LDRefare are mapped to the variable Node
class type.in a general
LogicalNode logical device
is mapped class.
to the LDName
object node classand
type. mapped to the variable Node
classclass
type.type.
LogicalNode
LogicalNode is mapped
is mappedtotothe theobject
object node classtype.
node class type.

Figure 8. ACSI logical device mapping.

The ACSI logical node class is a composition of LNName, LNRef, DataObjects, DATA-SET,
BRCB (buffered report control block), and URCB (unbuffered report control block) [9]. The attribute

ACSIlogical
Figure8.8.ACSI
Figure logical device
devicemapping.
mapping.

The ACSI logical node class is a composition of LNName, LNRef, DataObjects, DATA-SET,
BRCB (buffered report control block), and URCB (unbuffered report control block) [9]. The attribute
Energies 2016, 9, 901 8 of 16

The ACSI logical node class is a composition of LNName, LNRef, DataObjects, DATA-SET, BRCB
(buffered report control block), and URCB (unbuffered report control block) [9]. The attribute LNName
unambiguously identifies a logical node within the scope of a logical device. The attribute LNRef is
the unique path name of a logical node. The attribute DataObject is a data object contained in a logical
node. The attribute DataSet is a list of all data sets that are included in a logical node. The attribute
BRCB is a list of all buffered report control blocks that are comprised in a logical node. The attribute
URCB is a list of all unbuffered report control blocks that are contained in a logical node. LNName
and LNRef are mapped to the variable node class type. The remaining attributes are mapped to the
object node class type.
The ACSI data object class is a key element in IEC 61850. It is a composition of DataObjectName,
DataObjectRef, and DataObjectType. The attribute DataObjectName unambiguously identifies a data
object within the scope of a logical node. The attribute DataObjectRef is the unique path name of a
data object. The DataObjectType is the CDC type.
Table 3 shows an example of the common data class (CDC—Data Object). The CDCs are defined
in IEC 61850-7-3 [13]. CDCs are a configured common data attribute (base data type or data structure)
and they are defined for use in IEC 61850-7-4 [16]. CDCs define the relation between their attributes
and the functional constraint as well as the possible trigger options. CDC specifications are classified
as status, measurand, controls, status settings, analog settings, and description. DPS (double point
status) belongs to status.

Table 3. Example of common data class: DPS (double point status) mapping.

PDS Type
Name Type Definition Data Type Node Class Type
Data Name
Data Attribute
Status
stVal Enum_stVal Enumeration Variable
q Quality_type BaseDataType Variable
t TimeStamp_type BaseDataType Variable
Substitution
subEna DataAttribute_Type Boolean Variable
subVal Dnum_stVal Enumeration Variable
subQ Quality_type BaseDataType Variable
subID DataAttribute_Type String Variable
Configuration, description and extension
d DataAttribute_Type String Variable
dU DataAttribute_Type String Variable
cdcNs DataAttribute_Type String Variable
cdcName DataAttribute_Type String Variable
dataNs DataAttribute_Type String Variable

Table 4 shows an example of mapping using the IEC 61850 information model defined in
IEC 61850-7-4. The logical node is to be composed of several CDCs. The logical node is composed
of three categories of data, and status information can be information that controls the logical node.
The categories are defined in several classes of data. The logical node is mapped to the OPC UA node
model based on the previously mapped CDC.
The UaModeler tool is used to implement the OPC UA AddressSpace for IEC 61850 ACSI mapping.
The UaModeler tool produces the source code for types of mapped IEC 61850 models (e.g., XCBR
type). It can easily implement information modeling, and it is represented graphically for the OPC UA
AddressSpace. The generated source code is C++, ANSI C, .NET [17].
Energies 2016, 9, 901 9 of 16

Table 4. Example of logical node: XCBR mapping.

Energies 2016, 9, 901 9 of 16
XCBR Type
Name Type Definition Modeling Rule Data Type Node Class
Table 4. Example of logical node: XCBR mapping.
LLName ObjectName_Type Mandatory BaseDataType Variable
Data
XCBR Type
Data from Override Instance
Name Type Definition Mandatory
Modeling Rule Data Type Object
Node Class
Common_LN_Type Declaration
LLName
Loc ObjectName_Type
SPS_Type Mandatory
Mandatory BaseDataType Variable
Object
Data
Data from EEHealth
Common_LN_Type INS_Type
Override Instance DeclarationOptional
Mandatory Object
Object
EEName
Loc DPL_TypeSPS_Type Optional
Mandatory Object
Object
EEHealth
OpCnt INS_Type
INS_Type Optional
Mandatory Object
Object
EEName DPL_Type Optional Object
Pos DPC_Type Mandatory Object
OpCnt INS_Type Mandatory Object
BlkOpn
Pos SPC_Type
DPC_Type Mandatory
Mandatory Object
Object
BlkCls
BlkOpn SPC_Type
SPC_Type Mandatory
Mandatory Object
Object
BlkCls
ChamotEna SPC_Type
SPC_Type Mandatory
Optional Object
Object
ChamotEna SPC_Type Optional Object
SumSwARs
SumSwARs
BCR_Type
BCR_Type
Optional
Optional
Object
Object
CBOpCap
CBOpCap INS_Type
INS_Type Mandatory
Mandatory Object
Object
POWCap
POWCap INS_Type
INS_Type Optional
Optional Object
Object
MaxOpCap
MaxOpCap INS_Type
INS_Type Optional
Optional Object
Object

2.4. SCL to OPC UA AddressSpace Module Implementation

The IEC 61850 server uses SCL files and preferences for the server. The OPC UA AddressSpace
may configure the IEC 61850 model information using SCL files, because the IEC 61850 server
configures the information model using SCL SCL files. The SCL
files. The SCL to OPC UA AddressSpace module
converts the IEC 61850 model informationinformation in the SCL file into OPC UA AddressSpace AddressSpace information.
information.
The mapping
mapping types
types in
inSection
Section2.3 2.3help
helpthe
theconversion.
conversion.The TheOPC OPCUA UAAddressSpace
AddressSpace creation
creation process
process is
performed
is performed in in
twotwosteps.
steps.
Figure 99 shows
showsstepstep1.1.Step
Step 1 creates
1 creates thethe TDF
TDF (type(type definition
definition file)file)
andand
NDF NDF(node(node definition
definition file)
file) with
with the Data
the Data Map Tool.
Map Tool. The DataTheMapDataTool
Mapmaps Tool the
maps IECthe IECmodel
61850 61850 information—logical
model information—logical device,
device, node,
logical logicalfunctional
node, functional constraint,
constraint, data object,
data object, and data andattribute.
data attribute.
TDF isTDF typeis definition
type definition fileIEC
file for for
IEC 61850 node in SCL file. NDF is node definition file for IEC 61850 node in
61850 node in SCL file. NDF is node definition file for IEC 61850 node in SCL file. TDF and NDF make SCL file. TDF and NDF
makeinformation
SCL SCL information
simple; simple; theyto
they help help to create
create logicallogical
node node instances
instances for a predefined
for a predefined logical
logical nodenodetype
type
in OPC in OPC UA. With
UA. With TDF TDF
and NDF,and NDF, the mapping
the mapping processprocess
time time is reduced
is reduced to than
to less less than one minute.
one minute. The
The
TDFTDF and and
NDFNDF are shown
are shown in Figure
in Figure 10. 10.

Figure 9. Step
Step 1:
1: Creation
Creation of
of TDF
TDF (type
(type definition file) and NDF (node definition file).
Energies 2016, 9, 901 10 of 16

Energies 2016, 9, 901 10 of 16

(A) (A) (B)

(B)

Figure 10. Examples of TDF and NDF. (A) Example of a created TDF file. Parentheses indicate the data
Figure 10. Examples
Examples of TDF and NDF. (A) Example of aa created
type—(TL) is the type of logical node, (FC) is the functional
created TDF
TDF
constraint, and
file.
file.
(TA)
Parentheses indicate the
is a type of data
data type—(TL) is the type of logical node, (FC) is the functional constraint, and
attribute. Brackets indicate the name of the data and the data for each data type and braces (TA)
indicate the is a type of data
name of the type. (B) Example of a created NDF file. Parentheses indicate the data type—(LD) is an
attribute. Brackets
Brackets indicate
indicate
instance thedevice,
the
of a logical name
name ofofisthe
(LN) the
an dataand
data
instance ofand thethe
a logical data
data
node, forfor
(FC) theeach
iseach data data
functional typetype
and
constraint, and braces
braces
(DO) indicate
indicate the
the
name name of the
of the type;type;
is (B) (B)object,
the data
ExampleExample of aof
and (DA) a data
iscreated
the created NDF
attribute.
NDF file.file.
Brackets Parentheses
indicate the name of
Parentheses theindicate
data and
indicate thethe
the data
data data
for type—(LD)
type—(LD) is
is an
each data type and braces indicate the name of the type.
an instance
instance of aoflogical
a logical device,
device, (LN)(LN)is anisinstance
an instance of a of a logical
logical node,node,(FC) (FC)
is theisfunctional
the functional constraint,
constraint, (DO)
is the is
(DO) data
theobject, and (DA)
data object, andis(DA) the data
is the attribute. Brackets
data attribute. indicateindicate
Brackets the name theofname
the data anddata
of the the data for
and the
each for
data dataeach
typedata
andtype bracesandindicate the namethe
braces indicate of name
the type. of the type.

Figure
Figure 1111shows
showsstep
step2. 2.
TheThe SCL
SCL to OPC
to OPC UA UA AddressSpace
AddressSpace module
module generates
generates the OPC theUAOPC UA
source
source
code forcode for building
building the OPCtheUA OPC UA using
server serverthe
using
TDFthe TDF
and theand
NDF.theThe
NDF. The generated
generated OPC UA OPC UA
source
source code is configured as the OPC UA AddressSpace of the OPC UA server
code is configured as the OPC UA AddressSpace of the OPC UA server for the IED represented in for the IED
represented
the IEC 61850 inmodel.
the IECThe
61850codemodel. The
for the codeoffor
types the types
mapped IECof61850
mapped
modelIECwas
61850 modelinwas
created created
Section 2.3.
in Section 2.3. Thus, generated code is valid for IEDs or any IEC 61850 systems due it is able
Thus, generated code is valid for IEDs or any IEC 61850 systems due it is able to receive as input and to receive
as
SCLinput
file. and SCL file.

Figure 11. Step 2: Generation of OPC UA source code.

3.
3. Experimental
ExperimentalResults
Resultsand
andPerformance
PerformanceEvaluation
Evaluation
The OPC
OPCUA UAserver
servercontains
containsthe OPC
the OPC UA server
UA module
server moduleandand
IECIEC
61850 client
61850 input/output
client (I/O)
input/output
module.
(I/O) The OPC
module. TheUAOPC server modulemodule
UA server configures the OPC
configures theUA AddressSpace
OPC for the IEC
UA AddressSpace 61850
for the IECmodel.
61850
The OPC UA client can access the IEC 61850 information model by searching for a
model. The OPC UA client can access the IEC 61850 information model by searching for a node node in the OPCin
UA AddressSpace. If the OPC UA server synchronizes with the data of the actual IEC
the OPC UA AddressSpace. If the OPC UA server synchronizes with the data of the actual IEC 6185061850 server,
the OPC UA client may be used to obtain the data in the IEC 61850 server without using the
IEC 61850 protocol.
Figure 12 shows a network diagram between IEC 61850 and OPC UA. The OPC UA client
requests the service for the OPC UA server. The OPC UA server module is transmitted to the IEC
61850 client I/O modules via the interprocess communication (IPC) service required. The IEC 61850
Energies 2016, 9, 901 11 of 16

server, the OPC UA client may be used to obtain the data in the IEC 61850 server without using the
IEC 61850 protocol.
Figure
Energies 12901
2016, 9, shows a network diagram between IEC 61850 and OPC UA. The OPC UA client requests 11 of 16
the service for the OPC UA server. The OPC UA server module is transmitted to the IEC 61850 client
clientmodules
I/O I/O modules
via the deliver the required
interprocess service (IPC)
communication to the IEC required.
service 61850 server. Table
The IEC 5 shows
61850 test
client I/O
environments.
modules deliver the required service to the IEC 61850 server. Table 5 shows test environments.

Figure 12. Network diagram between IEC 61850 and OPC UA.

Table 5. Test environments

environments [17–20].
[17–20].

Component OPC UA Client OPC UA Server IEC 61850 Client IEC 61850 Server
Component OPC UA Client OPC UA Server IEC 61850 Client IEC 61850 Server
OS Ubuntu 14.04 Ubuntu 14.04 Ubuntu 14.04 Windows
OS Ubuntu 14.04 Ubuntu 14.04 Ubuntu 14.04 Windows
KEMA’s UniCA
Tool UA’s UaExpert KEMA’s UniCA
Tool UA’s UaExpert IED Simulator
IED Simulator
UA’s OPC UA SDK Sisco’s MMS-EASE
SDK
SDK UA’s OPC UA SDK 1.3.1 Sisco’s MMS-EASE Lite 5.02
1.3.1 Lite 5.02
Language
Language C++
C++ CC

We have
have performed
performed an IEC 61850 and OPC UA interlock test using SCL files with the IED
information of the four manufacturers—Table 6; these these are
are the
the SCL
SCL files
files that
that compose
compose the
the real
real IED.
IED.
files were
All four SCL files were successfully
successfully converted
converted to
to the
the OPC
OPC UA
UA AddressSpace.
AddressSpace.

Table 6. The number of nodes for each data type and

and rate
rate of
of conversion.
conversion.

Metric IED A IED B IED C IED D

Metric IED A IED B IED C IED D
Logical Device(Num) 2 4 1 4
Logical Device(Num)
Logical Node(Num) 2 80 4217 811 1164
Logical
DataNode(Num)
Object(Num) 80 979 217
2532 81
840 116
809
Data Object(Num) 979 2532 840 809
Data Attribute(Num) 2795 6276 2095 2108
Data Attribute(Num) 2795 6276 2095 2108
Conversion (%) 100% 100% 100% 100%
Conversion (%) 100% 100% 100% 100%

Figure 13 shows the results of IEC 61850–OPC UA interconnection. Figure 13b is the IEC 61850
model Figure 13 shows
information the KEMA’s
using results ofUniCA
IEC 61850–OPC UA interconnection.
IED simulator Figurethat
[19]. Figure 13a shows 13bUA’s
is theExpert
IEC 61850
tool
model information using KEMA’s UniCA IED simulator [19]. Figure 13a shows that
(OPC UA client) accesses the IEC 61850 model information by searching for nodes in the OPC UA UA’s Expert tool
(OPC UA client)
AddressSpace [5].accesses the IEC
The results of 61850
the IEC model information
61850–OPC by searching forinclude
UA interconnection nodes in the OPC
logical UA
device,
AddressSpace [5]. The results
logical node, functional of the data
constraint, IEC 61850–OPC
object, and UAdatainterconnection include logical
attribute. GEDeviceF650 device, Device
is a Logical logical
node, functional constraint, data object, and data attribute. GEDeviceF650 is a Logical Device
for the generator role. GGIOs (generic process input/output) are logical nodes. This node is used only for the
generator role. GGIOs (generic process input/output) are logical nodes. This node
to model process devices that are not predefined by LN groups in a generic way. CF (configuration),is used only to
model process devices
DC (description), that are not
EX (extended predefined
definition), MXby(measurands),
LN groups in anda generic way. CF
ST (status) are(configuration),
the functional
DC
constraints. AnIn is a data object with the CDC MV (measured values) type. The data the
(description), EX (extended definition), MX (measurands), and ST (status) are functional
attributes (db,
constraints.
RangeC, units) AnIn is a to
belong data
MVobject
CF. with the CDC MV (measured values) type. The data attributes
(db, RangeC, units) belong to MV CF.
Energies 2016, 9, 901 12 of 16
Energies 2016, 9, 901 12 of 16
Energies 2016, 9, 901 12 of 16

(a) (b)
(a) (b)
Figure 13.
Figure 13. Results
Results of
ofIEC
IEC61850–OPC
61850–OPCUA UAinterconnection.
interconnection.(a)(a)
UA’s Expert
UA’s Experttooltool
(OPC UAUA
(OPC client); (b)
client);
Figure
KEMA’s 13.UniCA
ResultsIED
of IEC 61850–OPC
(intelligent UA interconnection.
electronic device) (a)(IEC
Simulator UA’s61850
Expert tool (OPC UA client); (b)
server).
(b) KEMA’s UniCA IED (intelligent electronic device) Simulator (IEC 61850 server).
KEMA’s UniCA IED (intelligent electronic device) Simulator (IEC 61850 server).
We have performed simulations in an environment as shown in Figure 12. We simulated
We have
have
throughput
performed simulations
forperformed simulations
the IEC 61850 and OPC in
in an
UAan
environment
environment
network area, and
as shown
as the
shown in Figure
in are
results Figure
shown
12.
12.inWe simulated
Figure 14. We
throughput for the
for theIEC
IEC61850
61850and
andOPC
OPCUA UA network
network area,
area, andandthe the results
results are are
shownshown
in in Figure
Figure 14.
14. We
used GetDataValues service. The throughput of IEC 61850 is 65,000 byte/s, and the throughput of
We
usedused GetDataValues service. The throughput of IEC 61850 is 65,000 byte/s, and the throughput
OPC GetDataValues service.
UA is 20,000 byte/s. TheThe
OPC throughput of IECthroughput
UA network’s 61850 is 65,000 byte/s,
is lower thanandthatthe
of throughput
the IEC 61850of
of OPC
OPC UAUAis is 20,000
20,000 byte/s.
byte/s. TheThe
OPCOPC UAUA network’sthroughput
network’s throughputisislower lower thanthat that of the
the IEC 61850
network, and this result means that the number of messages of IEC 61850than
is greater of
than that of OPC
network, and this result means that the number of messages of IEC 61850 is greater than that of OPC
UA. The OPC UA can efficiently transmit a greater number of items.
UA. The OPC UA can efficiently transmit a greater
greater number
number of of items.
items.

Throughput
Throughput
80000
Size(byte)

80000
Size(byte)

60000
60000
40000
40000
Data

20000
Data

20000
0
0
1 1
9 9
1717
2525
3333
4141
4949
5757
6565
7373
8181
8989
9797
105
113
121
129
137
145
153
161
169
177
185
193
201
209
217
225
233
105
113
121
129
137
145
153
161
169
177
185
193
201
209
217
225
233

Time(s)
Time(s)
OPC UA IEC61850
OPC UA IEC61850

Figure 14. OPC UA and IEC 61850 throughput.

Figure
Figure 14.
14. OPC
OPC UA
UA and
and IEC
IEC 61850
61850 throughput.
throughput.
Figures 15 and 16 show the round-trip time (RTT) of IEC 61850 (IEC 61850 client module—
KEMA Figures 15 and 16 and
IED Simulator) show
OPCtheUA round-trip time (RTT)UA
(UA Expert—OPC of server
IEC 61850 (IECWe
module). 61850
usedclient module—
GetDataValues
KEMA IED Simulator) and OPC UA (UA Expert—OPC UA server module). We used GetDataValues
service. The RTT of IEC 61850 is less than 8 ms. On the other hand, the RTT of OPC UA is less than
service. The the
20 ms, thus RTTRTT
of IEC 61850UA
of OPC is less than 8than
is higher ms. IEC
On the other
61850. (1)hand, the RTT
The OPC UA of OPCmodule
server UA is less than
conveys
20 ms, thus the RTT of OPC UA is higher than IEC 61850. (1) The OPC UA server module conveys
Energies 2016, 9, 901 13 of 16

Figures 15 and 16 show the round-trip time (RTT) of IEC 61850 (IEC 61850 client module—KEMA
Energies 2016, 9, 901 13 of 16
IED Simulator) and OPC UA (UA Expert—OPC UA server module). We used GetDataValues service.
The RTT
Energies
the of 9,IEC
2016,
information 61850 is less
901 received fromthan
the 8IEC
ms.61850
On the other
client hand,to
module the
theRTT
OPC of UA
OPCClient;
UA is(2)
less than
The OPC20 ms,
13 of
UA 16
thus the RTT of OPC UA is higher than IEC 61850. (1) The OPC UA server
server module performs a process for mapping the IEC 61850 data model and OPC UA AddressSpace module conveys the
the information
information received
received from from the 61850
the mapping
IEC IEC 61850
clientclient
modulemodule
to theto the UA
OPC OPC UA Client;
Client; (2) The(2) TheUA
OPC OPC UA
server
model. All information about data was exchanged correctly.
server module
module performs performs a process
a process for mapping
for mapping the IECthe IECdata
61850 61850 data and
model model andUA
OPC OPC UA AddressSpace
AddressSpace model.
model.
All All information
information about mapping
about mapping data wasdata was exchanged
exchanged correctly.correctly.

Figure 15. Round-trip time (IEC 61850: IEC 61850 client module—KEMA IED Simulator).

Figure 15.
Figure 15. Round-trip
Round-trip time
time (IEC
(IEC 61850:
61850: IEC
IEC 61850
61850 client
client module—KEMA
module—KEMA IED
IED Simulator).
Simulator).

Figure
Figure 16.
16. Round-trip
Round-trip time
time (OPC
(OPC UA:
UA: UA
UA Expert—OPC UA server
Expert—OPC UA server module).
module).

Figures 17 Figure
and 1816.are
Round-trip timeIO
Wireshark (OPC UA: UA
graphs Expert—OPC
of IEC UA server
61850 GOOSE module).
message (IEC 61850 client
module—KEMA IED Simulator) and OPC UA (UA Expert—OPC UA server Module), respectively.
Figures 17 and 18 are Wireshark IO graphs of IEC 61850 GOOSE message (IEC 61850 client
We used GOOSE control block service. The IO graph of GOOSE is 120–160 packets/s. On the other
module—KEMA IED Simulator) and OPC UA (UA Expert—OPC UA server Module), respectively.
hand, the IO graph of OPC UA is 43–46 packets/s, thus the IO graph of GOOSE is higher than OPC
We used GOOSE control block service. The IO graph of GOOSE is 120–160 packets/s. On the other
hand, the IO graph of OPC UA is 43–46 packets/s, thus the IO graph of GOOSE is higher than OPC
Energies 2016, 9, 901 14 of 16

Figures 17 and 18 are Wireshark IO graphs of IEC 61850 GOOSE message (IEC 61850 client
module—KEMA IED Simulator) and OPC UA (UA Expert—OPC UA server Module), respectively.
Energies 2016, 9, 901 14 of 16
We used
Energies GOOSE
2016, 9, 901 control block service. The IO graph of GOOSE is 120–160 packets/s. On the14 other
of 16
hand, the IO graph of OPC UA is 43–46 packets/s, thus the IO graph of GOOSE is higher
UA. (1) GOOSE messages support real-time communications for critical messages; (2) All devices than OPC UA.
(1)
UA. GOOSE
(1) GOOSE
sending messages
GOOSEmessages support real-time
messagessupport communications
real-time
shall continue for
to communications critical
send the message messages;
forwith
critical (2) All
messages;
a long devices
(2) All
cycle time, sending
devices
even if no
GOOSE
sending messages
GOOSE shall continue
messages shall
status/value change has occurred. to send
continuethe
tomessage
send thewith a long
message cycle
with atime,
longeven
cycle if no status/value
time, even if no
change has occurred.
status/value change has occurred.

Figure 17. Wireshark IO (input/output) graphs: packet (IEC 61850 Client module—KEMA IED
Figure
17. 17.
Simulator).
Figure Wireshark
Wireshark IO (input/output)
IO (input/output) graphs:
graphs: packetpacket (IECClient
(IEC 61850 61850module—KEMA
Client module—KEMA IED
IED Simulator).
Simulator).

Figure 18.
Figure 18. Wireshark
Wireshark IO
IO graphs:
graphs: OPC
OPC UA
UA packet
packet (UA
(UA Expert—OPC
Expert—OPC UA
UA server
server module).
module).
Figure 18. Wireshark IO graphs: OPC UA packet (UA Expert—OPC UA server module).
4. Conclusions
4. Conclusions
4. Conclusions
Withthe
With thedevelopment
development of technology,
of technology, the smart
the smart gridbeen
grid has hascertified
been certified as the underlying
as the underlying structure
With
structure the
of thedevelopment
core strategy of technology,
for energy the
saving. smart
The grid
power has been
network certified
requires as
a the underlying
unified platform
of the core strategy for energy saving. The power network requires a unified platform through the
structure
through of the
the core strategy
interworking of for energy
various power saving. The OPC
protocols. power UA network
adopted requires
a unified a unified
platform platform
because
interworking of various power protocols. OPC UA adopted a unified platform because it provides a
through theainterworking
it provides of various power
model for meta-information andprotocols. OPC UA adopted
an expandable with anaobject-oriented
unified platform because
model for meta-information and an expandable type with antypeobject-oriented model. Themodel.
main aim The
itmain
provides of a model for meta-information and an expandable type with an object-oriented model. The
of thisaim
paper has this been
paper tohas been to demonstrate
demonstrate how to convert howthe to OPC
convert
UAthe OPC
information UA model
information
throughmodel
the
main aim of this paper has been to demonstrate how to convert the OPC
through the analysis of the IEC 61850 standards and implement the SCL to OPC UA AddressSpace UA information model
through
module theusing analysis of the
IEC 61850 IECfiles.
SCL 61850Thestandards
SCL to OPC and UA
implement the SCLmodule
AddressSpace to OPCcan UAconvert
AddressSpace
all SCL
module using IEC 61850 SCL files. The SCL to OPC UA AddressSpace module
files. This paper has shown a process in which the SCL file (IEC61805 model) is converted to the can convert all OPC
SCL
files. This paper has shown a process in which the SCL file (IEC61805 model)
UA address of the OPC UA server. We were able to view and change the value of IEC 61850 data is converted to the OPC
UA address of
information in the OPC UA
the OPC UA client
server.using
We were able to view
the technique and change
proposed in this the value
paper. Allof IEC 61850about
information data
information in the OPC UA client using the technique proposed in this paper. All information about
Energies 2016, 9, 901 15 of 16

analysis of the IEC 61850 standards and implement the SCL to OPC UA AddressSpace module using
IEC 61850 SCL files. The SCL to OPC UA AddressSpace module can convert all SCL files. This paper
has shown a process in which the SCL file (IEC61805 model) is converted to the OPC UA address of
the OPC UA server. We were able to view and change the value of IEC 61850 data information in
the OPC UA client using the technique proposed in this paper. All information about mapping data
was exchanged correctly. The application of the OPC UA offers great potential in the smart grid field.
This paper contributes to the identification of information and communication technologies (ICTs)
capable of satisfying the communication requirements for future power systems.

Acknowledgments: This research was supported by the Energy Technology Development Project through the
Korea Institute of Energy Technology Evaluation and Planning (KETEP) funded by the Ministry of Trade, Industry
& Energy (MOTIE) (No.: 20131020400660 and No.: 20131020402080) and Seokyeong University (2016).
Author Contributions: In-Jae Shin and Byung-Kwen Song designed the study and the simulation. In-Jae Shin
performed the simulation and data analysis. In-Jae Shin wrote the paper, with assistance and editing from
Byung-Kwen Song, Doo-Seop Eom.
Conflicts of Interest: The authors declare no conflict of interest.

References
1. Lehnhoff, S.; Rohjans, S.; Uslar, M.; Mahnke, W. OPC UA Unified Architecture: A Service-Oriented
Architecture for Smart Grids. In Proceedings of the First International Workshop on Software Engineering
Challenges for the Smart Grid, Zurich, Switzerland, 2–9 June 2012.
2. Lehnhoff, S.; Mahnke, W.; Rohjans, S.; Uslar, M. IEC 61850 based OPC UA Communication—The Future of
Smart Grid Automation. In Proceedings of the 17th Power Systems Computation Conference (PSCC’11),
Stockholm, Sweden, 22–26 August 2011.
3. International Electrotechnical Commission. Part 1: Overview and Concepts. In IEC 62541-1: OPC Unified
Architecture, 1st ed.; Springer: Berlin/Heidelberg, Germany, 2008.
4. Naumann, A.; Bielchev, I.; Voropai, N.; Styczynski, Z. Smart grid automation using IEC 61850 and CIM
standards. Control Eng. Pract. 2014, 25, 102–111. [CrossRef]
5. Buchholz, B.M.; Brunner, C.; Naumann, A.; Styczynski, Z. Applying IEC standards for communication and
data management as the backbone of smart distribution. In Proceedings of the 2012 IEEE Power and Energy
Society General Meeting (PES 2012), San Diego, CA, USA, 22–26 July 2012.
6. Cavalieri, S.; Regalbuto, A. Integration of IEC 61850 SCL and OPC UA to improve interoperability in Smart
Grid environment. Comput. Stand. Interfaces 2016, 47, 77–99. [CrossRef]
7. Srinivasan, S.; Kumar, R.; Vain, J. Integration of IEC 61850 and OPC UA for Smart Grid automation.
In Proceedings of the 2013 IEEE Innovative Smart Grid Technologies-Asia (ISGT Asia), Bangalore, India,
10–13 November 2013.
8. Cintuglu, M.H.; Martin, H.; Mohammed, O.A. An intelligent multi agent framework for active distribution
networks based on IEC 61850 and FIPA standards. In Proceedings of the 2015 18th International Conference
on Intelligent System Application to Power Systems (ISAP), Porto, Portugal, 11–16 September 2015.
9. Mahnke, W.; Leitner, S.-H.; Damm, M. OPC Unified Architecture; Springer: Berlin/Heidelberg, Germany, 2009.
10. International Electrotechnical Commission. Part 3: Address Space Model. In IEC 62541-3: OPC Unified
Architecture, 1st ed.; Springer: Berlin/Heidelberg, Germany, 2008.
11. International Electrotechnical Commission. Part 7-1: Basic Communication Structure—Principles and
Models. In International Standard IEC 61850, Communication Networks and Systems for Power Utility Automation,
2nd ed.; IEC: Geneva, Switzerland, 2010.
12. International Electrotechnical Commission. Part 7-2: Basic Information and Communication Structure
Abstract Communication Service Interface (ACSI). In International Standard IEC 61850, Communication
Networks and SYSTEMS for Power Utility Automation, 2nd ed.; IEC: Geneva, Switzerland, 2010.
13. International Electrotechnical Commission. Part 7-3: Basic Communication Structure for Substation and
Feeder Equipment Common Data Classes. In International Standard IEC 61850, Communication Networks and
Systems for Power Utility Automation, 2nd ed.; IEC: Geneva, Switzerland, 2010.
Energies 2016, 9, 901 16 of 16

14. International Electrotechnical Commission. Part 8-1: Specific Communication Service Mapping
(SCSM)—Mappings to MMS (ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3. In International Standard
IEC 61850, Communication Networks and Systems for Power Utility Automation, 2nd ed.; IEC: Geneva,
Switzerland, 2011.
15. International Electrotechnical Commission. Part 6: Configuration Description Language for Communication
in Electrical Substations. In International Standard IEC 61850, Communication Networks and Systems for Power
Utility Automation, 2nd ed.; IEC: Geneva, Switzerland, 2009.
16. International Electrotechnical Commission. Part 7-4: Basic communication structure—Compatible Logical
Node Classes and Data Object Classes. In International Standard IEC 61850, Communication Networks and
Systems for Power Utility Automation, 2nd ed.; IEC: Geneva, Switzerland, 2010.
17. Unified Automation, UA Server SDK C++ Bundle 1.3.1. Available online: www.unified-automation.com
(accessed on 24 June 2016).
18. SISCO Inc. MMS-EASE Lite 5.02; SISCO Inc.: Rancho Dominguez, CA, USA, 2008.
19. DNV KEMA Energy & Sustainability, UniCA IED Simulator User Manual; DNV KEMA: Groningen,
The Netherlands, 2012.
20. Unified Automation, UA Modeler. Available online: www.unified-automation.com (accessed on 24 June 2016).

© 2016 by the authors; licensee MDPI, Basel, Switzerland. This article is an open access
article distributed under the terms and conditions of the Creative Commons Attribution
(CC-BY) license (http://creativecommons.org/licenses/by/4.0/).