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

net/publication/224193171

Mapping the Substation Configuration Language of IEC 61850 to ArchiMate

Conference Paper · November 2010

DOI: 10.1109/EDOCW.2010.35 · Source: IEEE Xplore

CITATIONS READS
6 1,702

5 authors, including:

Kun Zhu Lars Nordström

ABB Enterprise Software KTH Royal Institute of Technology
34 PUBLICATIONS   327 CITATIONS    97 PUBLICATIONS   918 CITATIONS   

SEE PROFILE SEE PROFILE

Mathias Ekstedt Lagerström Robert

KTH Royal Institute of Technology KTH Royal Institute of Technology
148 PUBLICATIONS   2,108 CITATIONS    95 PUBLICATIONS   1,163 CITATIONS   

SEE PROFILE SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Back up the sanetics is add View project

EnergyShield View project

All content following this page was uploaded by Lars Nordström on 27 May 2014.

The user has requested enhancement of the downloaded file.

 Mapping the Substation Configuration Language of IEC 61850 to ArchiMate

Johan König, Kun Zhu, Lars Nordström, Mathias Ekstedt, Robert Lagerström
Industrial Information and Control Systems,
Royal Institute of Technology, KTH
Stockholm, Sweden
{johank, zhuk, larsn, mek101, robertl}@ics.kth.se

Abstract—This paper presents a mapping between the
Enterprise Architecture framework ArchiMate and the
Substation Configuration Language (SCL) of IEC 61850.
Enterprise Architecture (EA) is a discipline for managing an
enterprise’s information system portfolio in relation to the
supported business. Metamodels, descriptive models on how to
model and one of the core components of EA, can assist
stakeholders in many ways, for example in decision-making.
Moreover, the power industry is a domain with an augmented
reliance on the support of information systems. IEC 61850 is a
standard for the design of Substation Automation (SA) systems
and provides a vendor independent framework for
interoperability by defining communication networks and
functions. The SCL is a descriptive language in IEC 61850 on
the configuration of substation Intelligent Electronic Devices
(IED) which describes the structure together with physical
components and their relating functions. By using SCL, which
models the architecture of SA systems, and mapping it to
ArchiMate, stakeholders are assisted in understanding their
SA system and its architecture. The mapping is intended to
support the integration of SA systems applying IEC 61850 into
the enterprise architecture. The mapping is demonstrated with
an example applying the mapping to a SA configuration based
on SCL.
Keywords-ArchiMate; Enterprise Architecture; IEC 61850;
Substation Configuration Language; Substation Automation.
I. INTRODUCTION
Many enterprises of today are highly dependent on their
information systems and the trend is growing. Strategic and
efficient management of the portfolio of systems is thus
becoming an increasingly important concern. Thereby,
stakeholders need support for creating transparency between
the business and the supporting information systems and also
between the information systems as such. Not only is there a
need for a common understanding of an enterprise’s
information system portfolio but also support for rational
decision making which prevents or reduces stakeholders
subjectivism in their decisions.
Enterprise Architecture (EA) is a discipline for managing
an enterprise’s information system portfolio in relation to the
supported business. Metamodels, descriptive models on how
to model the architecture, are one of the core components of
EA and can serve multiple purposes [1]: (i) to document the
EA, (ii) to plan and design the EA, and (iii) to analyze the
EA. Analysis, in particular, closely relates to the use of EA
and architectural models for decision-making [2].
Since modeling can be an effort and time consuming task
it is important that the metamodel serves the purpose of the
modeler’s needs with precision. Domain specific models are
part of what assists the modeler to reduce the effort needed
and enhance the precision of the models and hence do serve
an important purpose.
A domain with an augmented reliance on the support of
information systems is the power industry. The progressive
focus on the integration of renewable energy resources has
stressed the need for modernizing the power system. Smart
Grid is the term commonly used to describe the vision of the
future power grid. Such a modernized power system is being
promoted as a way of addressing energy independence,
global warming and emergency resilience issues. It is,
according to the European Strategic Technology Platform, a
vision for creating a flexible, accessible, reliable and
economical grid for the future [3]. To be able to do so the
capabilities of the power grid must be enhanced with new
technology.
A main component for the vision to become a reality is
the development of technology standards. Without
standardizing the technology needed for a Smart Grid, power
utilities and system vendors will not be able to construct a
flexible, accessible and reliable system in a cost efficient
way. IEC 61850 is a standard developed by the International
Electrotechnical Commission (IEC) for the design of
Substation Automation (SA) systems. A SA system is
usually composed of 20-100 distributed Intelligent
Electronic Devices (IED) connected via high-speed
communication networks [4] and can be referred to as the
backbone of a Smart Grid. One of the primary objectives of
IEC 61850 is free allocation of functions which either can be
executed locally, i.e. by a single IED, or in a distributed
manner over multiple IEDs [4].
The need for proper management of SA systems is
motivated both by their complexity and also by their
important role in the Smart Grid vision. The proposal of
using EA, which has proven successful in other information
system domains, hopefully can support stakeholders in
managing their SA system portfolio and their integration to
other business domains.
Scope of the paper
The scope of this paper is to present a mapping between
SCL of IEC 61850 and the EA framework ArchiMate. The
need for a mapping will be argued for, and a demonstration
of the mapping will be presented applying the result to an SA
configuration based on SCL.
Structure of the paper
The remainder of this paper is structured as follows.
Section II presents related work. Section III provides a brief
introduction to ArchiMate. In section IV a general
description on the domain of substation automation and a
description of the IEC 61850 standard including the SCL is
presented. Section V is the locus of the main contribution,
presenting a mapping between ArchiMate and the SCL of
IEC 61850. Section VI presents an example with the result of
the mapping applied to a SCL configuration. Section VII
discusses the implications of the contribution and future
work. Finally, section VIII concludes the paper.
II. RELATED WORKS
Much work has been established in SA metamodeling
domain with different research focus. It is commonly the fact
that domain specific standards, like the case for IEC 61850,
is proposed by domain experts who in most cases are of
insufficient knowledge about the Information and
Communication Technology (ICT) systems in contrast to the
software engineers who actually have the implementation
responsibilities. The implicit domain knowledge and rigor in
the data specification makes the standard difficult to use by
developers often lacking the domain knowledge. In [4] and
[5] feasibility studies concerning mapping of IEC 61850
standard to UML modeling language are presented with the
ambition to enable both manual and semi-automatic (if
UML-based computerized analysis tools are available)
analysis of the complex substation automation system
architecture. Moreover, a model driven IEC 61850 modeling
approach based an Automation Systems Modeling Language
(ASML), an extension of UML subset, can be found in [6].
Such an approach could facilitate next generation SA
systems, capable of handling system object models in an
integrated engineering environment.
In [7] the authors propose a modeling approach which is
capable of automatically generating system configuration for
security measures from description file together with its
application to IEC 61850 Substation Configuration
Description (SCD) files (part of SCL). Further, in [8] a
SCADA reference architecture is generated by object-role
modeling approach. Its usage is two-folds; first to generalize
security issues in automation systems within the power
system domain and secondly to compare it with the initiated
system. When the non-applicability of the model indicates a
unique system configuration where significant security
analysis could be warranted.
In [9] an XML schema based solution for global power
quality analysis is proposed. Furthermore, in [10] Hughes
presents the Intelligrid project which captures a general view
for the business in power utilities and this work aims at
promoting for power industry standards development and
merging.
III. ARCHIMATE
ArchiMate is an open and independent modeling
language, i.e. metamodel, for enterprise architecture. The
primary focus of ArchiMate is to support stakeholders how
to address concerns regarding their business and the
supporting ICT systems. It was first introduced by Lankhorst
et al. in [11] and is partly based on the ANSI/IEEE 1471-
2000, Recommended Practice for Architecture Description
of Software-Intensive Systems, also known as the IEEE 1471
standard [12]. The Open Group accepted the ArchiMate
metamodel as a part of The Open Group Architecture
Framework (TOGAF) in 2009 [13].
The ArchiMate metamodel consists of three layers; the
Business layer, the Application layer and the Technology
layer. Where, technology supports the applications, which in
turn supports the business. Each layer consists of a number
of entities and defined entity relations.
The entities in each layer are categorized into three
aspects of enterprise architecture: 1) The passive structure -
modeling informational objects. 2) The behavioral structure -
modeling the dynamic events of enterprise architecture. 3)
The active structure - modeling the components in the
architecture that perform the behavioral aspects.
One concept that is not widely used in the power
community is the concept of services. This is however used
extensively in ArchiMate. Services aim to encapsulate and
hide the internal behavior of underlying layers and give the
overlying layers access to functionality from underlying
layers through well-defined interfaces. For instance, an
Application Service is seen to encapsulate a number of
internal Application Functions to make them useful to the
business actors of the business processes. By using services
the business actors neither have to consider the internal
behavior of the information systems nor the technology used
to realize the behavior. However, the use of services to
model the relations between functions of separate layers is
not a requirement. For example, a business function can
directly be modeled with a relation to an application
function. Figure 1. presents the complete ArchiMate
metamodel. For a more detailed description we refer to [13].
IV. SUBSTATION AUTOMATION AND IEC 61850
It is commonly agreed upon that the prosperity of modern
society is highly dependent of electricity. From a user
perspective, the requirements are put on the supply of high
quality power to a low cost. The generated power is
delivered through the network and finally distributed to the
consumers. The nodes in such a grid, whose basic functions
are transforming voltage and routing power flows, are called
substations. In the modern power system with a high
automation degree the substations are operated and
controlled by SA systems.
 Information aspect Behavior aspect Structure aspect

Product Value

Represen- Contract Business Business

Business
Meaning tation Service Collaboration
Interface
Event

Business object Business

process/ Business role Business
function Actor

Business
Application

Application Application Application

Service Interface Collaboration

Data Object
Application Application
Function/ Component
Interaction

Application

Technology

Infrastructure Infrastructure
Service Interface

Artifact Node Communication

path

System Software Device Network

Information aspect Behavior aspect Structure aspect

Figure 1. The ArchiMate metamodel.

Besides the monitoring, control and protection
functionalities, SA systems also provide interfaces to the
Supervisory Control and Data Acquisition (SCADA)
systems and the Human Machine Interfaces (HMI), which
realize both local and remote communication access. All
these aforementioned SA system functions are facilitated by
several IEDs, which are interconnected by communication
networks together with primary equipment such as switches,
transformers, measurement units, etc.
Figure 2. illustrates a conceptual power grid model,
which can be viewed as a composition of two subsystems.
One contains the primary equipment through which the
electricity is delivered and where the control and protection
of the grid is executed. Transmission lines, transformers,
switches, etc are catalogued in this subsystem. The other
system is the ICT infrastructure composed by devices, such
as communication networks, routers and IEDs, which
realizes the aforementioned SA functionalities.
A. IEC 61850 Basics
IEC 61850 is a standard developed by the International
Electrotechnical Commission (IEC) for the design of SA
systems [14]. The standard provides a vendor independent
framework for interoperability by defining communication
networks and functions.
Albeit the fact that IEC 61850 is proposed as a
communication solution for SA systems, it also supports the
operation functions of substations. Therefore, the standard
has to take operational requirements into consideration.
However, the purpose of the standard is neither to
standardize (nor limit in any way) the functions involved in
substation operation nor their allocation within SA systems.
The major advances of IEC 61850 are summarized
below:
• Functional modeling: the functions described by
IEC 61850 are realized by collaboration between a
set of atomic functional units. These functional
units can be implemented in different IEDs and
communicate with each other. The communication
behavior of the parts is described by Logic Nodes
(LNs). The separation between physical
infrastructure and logic enables functional
allocation independent for the ICT infrastructure,
which has not been presented in prior SA systems
and standards.
 object contained by a LogicNode. Router is a
function assigns the connection of a single IED to
multiple AccessPoint. Clock indicates the location
of a subnetwork master clock.
• Communication model: contains physical
communication network components such as
Subnetwork and AccessPoint. Subnetwork is the
aggregation of the process communication bus
where the measurements collected from the process
level are flowing though and the bay
communication bus along which the monitoring,
control and protection related signals are
exchanged. AccessPoint specifies connections of
LogicDevice in IED to Subnetwork.
Figure 2. Conceptual power system model illustrating the application of
IEC 61850.

• Data modeling: IEC 61850 provides not only the

syntax but also the semantics for the data exchange
within SA systems.
• Communication service modeling: IEC 61850 does
not restrict itself to any concrete communication
solutions. Instead it defines an abstract
communication interface which specifies the
mapping of communication services and data
models to the main stream communication
protocols. The flexibility of switching to future
communication solutions enables easy adaption
and reduces the investment on substation
refurbishment significantly.
• Engineering tool and testing: IEC 61850 is not only
limited to describe the communication and related
processes. The XML-based Substation
Configuration Language describing the SA systems Figure 3. The SCL object model [17]
and the communication topology is presented in
IEC 61850-6 [17]. It is worth mentioning that the SCL object model does
not cover communication services which are provided by
B. Substation Configuration Language (SCL)
IEDs and actually part of the SCL. Besides, from a modeling
Defining business goals and functions is not a main perspective, this model is not completed as well. For
objective of IEC 61850 and hence the business domain is not instance, the entire hierarchical structure is in absence, like
well captured in the standard. However, one relevant part the upper-class from which the used classes may be derived
that does define some objects that can be modeled according
as well as classes on a lower level, attributes etc. It restricts
to the ArchiMate metamodel is the Substation Configuration
Language (SCL) which is a descriptive language on the itself to those concrete object types related substation
configuration of substation IEDs. Its full scope covers functional designation. Furthermore, it does not contain the
primary power system structure description, desired SA levels below Data, which are structurally defined in IEC
function implementation based on LNs, and communication 61850-7-3 [20].
within substations. The SCL object model is presented in C. Motivation for mapping SCL to ArchiMate
Figure 3.
As stated in the previous section, ArchiMate is an open
• Product model: consists of hardware (IED) where and independent modeling language whose primary focus is
the SA functions are implemented. Server is an to assist stakeholders to address concerns regarding their
object within IED which specifies access to business and the supporting ICT systems, while IEC 61850
communication system. LogicDevice is a group of is an internationally accepted standard for substation
atomic piesce of SA function (LogicNode) that is automation in the power industry, used as a baseline to
contained in as Server of an IED. Data is the data configure substations. However, it is less common to
address the dependency of supporting ICT systems with the
business processes of power utilities.
The mapping between SCL and ArchiMate enables the
integration of SA system to power utility’s enterprise
architecture. Furthermore, in the previous domain standards,
the data model can be specified and maintained directly
given information or textual notations. However, due to the
growing number of data object types and their complexity
together with the resulting specific communications
services, the informal textual notation is no longer capable
to handle entire specification in a consistent way [16]. As a
consequence SCL is mapped to ArchiMate partly with the
ambition to generate a more rigorous specification for data
and communication service modeling.
V. MAPPING ARCHIMATE AND SCL
This section presents a mapping between SCL of IEC
61850 and ArchiMate. The objective of the mapping is to
identify objects defined in SCL which have the relation is a
kind of to entities defined in ArchiMate. Some SCL objects
may however be composed of multiple ArchiMate entities
with is a part of relation. The mapping is divided into three
parts - business, application and technology - in accordance
with the layers defined in ArchiMate.
The method that we have applied for mapping SCL to
ArchiMate is quite straight-forward. First we identified
objects in SCL together with their definitions using IEC
61850-6 and IEC 61850-7 (part 1 to 4). In case of any
ambiguity regarding definitions we used the glossary
presented in IEC 61850-2 [21]. Based on the profound
understating, SCL objects that have the relation is a kind of,
or an is a part of, to any entity of ArchiMate are identified.
Since ArchiMate is intended for modeling the interaction
between the business and the supporting information systems
an important first step is to define what we refer to as a
business. Since SA systems are used for controlling and
supervising the power grid, and the power grid being the
business for the power system operators, it is reasonable to
map the business domain to the actual power grid. Hence,
the business of a power utility managing a power grid is the
monitoring, control and protection of the grid. The product is
thus the delivery of electricity from the “producers” to the
“consumers” with a certain quality. In the context of SA the
business is delimited to the primary and secondary
equipment composing the substation. The behavior elements
of the business are represented by the primary equipment
(e.g. breakers, switches, transformers, etc) which are
supported by secondary systems (e.g. control and protection
systems). Each layer is presented in more detail below. The
complete result of the mapping in presented in TABLE I.
Business layer: The objects identified in SCL that are
mapped to entities in the business layer of ArchiMate are
function, subfunction, transformer, equipment and
subequipment, which all belong to the Substation model of
SCL. Objects such as substation, voltage level, bay, terminal
and connectivity node from the Substation model does model
structural hierarchy of a substation, for example describing
that an IED is located at substation X with voltage level Y,
and hence not identified with an is a kind of or is a part of
relation to an entity of ArchiMate.
The business layer of ArchiMate primarily addresses
entities of an organization with the interaction of business
actors. SA systems however lack the interaction with people
and their behavior. Instead the behavior is allocated to
primary equipment and their functionality. Since primary
equipment involved in substation automation is offering
certain functionality, it is neither a kind of business object,
which is defined as a passive object, nor a kind of business
actor, given that a business actor is defined as an
organizational entity. Therefore, instead of mapping the
equipment to any existing entity in ArchiMate, a new entity
is introduced called equipment, much similar to an actor,
although without the need of being an organizational entity.
Figure 4. shows the equipment entity and its relation to the
ArchiMate entity business function.
Figure 4. Introduced entity equipment
Its relation to the application layer is the same as for the
entity business role of ArchiMate. Moreover, in contrast to
an actor the equipment does not allow temporary
collaboration and thereby excludes the possibility of
performing business interactions. Equipment can be
composed of subequipment, which is defined as a part of
equipment [17]. Equipment objects in SCL are: equipment -
an apparatus within the switchyard; subequipment – a part of
an equipment; and transformer – a special equipment. The
function object in SCL represents functions that are part of
the switch yard functionality which is a kind of business
function assigned to equipment. Functions may be composed
of subfunctions - representing a hierarchical subpart of a
function – also a kind of business function assigned to
equipment.
Application layer: The objects identified in SCL that are
mapped to entities in the application layer of ArchiMate are
logical node, data, server and IED which are objects
belonging to the product model of SCL.
Applications in SA systems are not much different from
any other type of ICT system applications. However, the
purpose of IEC 61850 is not to standardize the application
functions involved in substation operation. Instead,
application functions are identified and descried in order to
define their communication requirements [18] and are
conceptually realized by (collaborations of) primitive, atomic
functional building blocks, the so-called Logical Nodes
(LNs) [4]. A LN is the smallest part of an application
function that can exchange information over the network
[19]. The realization relationship between functions and
services in ArchiMate indicates how logical entities, “what”,
such as services, are realized by means of more concrete
entities, “how” [13]. In [4], the functionality of a SA system
is described by a “logical system”, interpreted as “what”, that
is comprised of the set of functions (LNs), interpreted as
“how”, that operate in the substation environment. Hence, a
LN is interpreted as a kind of application function instead of
as a service.
In ArchiMate an application function is defined as a
representation of a coherent group of internal behavior of an
application component [13]. The internal behavior is as
previously motivated a kind of LN; however, its relation to
an application component is not explicitly described in SCL.
An IED (further described in the technology layer mapping)
does, although not described in SCL, include an application
component module as a bundled part of it [19]. Hence, an
application component is a part of an IED.
Server is a communication entity which allows LNs to
access other LNs allocated to remote IEDs via the
communication system. It is only possible to remotely access
LNs contained in a server. An application interface in
ArchiMate is defined as a declaration of how a component
can connect with its environment [13]. It specifies how the
functionality of a component can be accessed by other
components (provided interface), or which functionality the
component requires from its environment (required
interface) [13]. Hence, server is interpreted as a kind of
application interface.
The object data in SCL models the data contained in a
LN [17]. Data represents specific information, for example
status or measurement, and is a kind of data object entity in
ArchiMate.
Technology layer: The objects identified in SCL that are
mapped to entities in the technology layer of ArchiMate are
router, IED, access point and subnetwork which are objects
belonging both to the product and communication model of
SCL. Another object also part of SCL, however not defined
in the SCL object model, is service capability which also is
part of the mapping.
For the objects defined in SCL a central component is the
IED, which, if excluding the application, is a kind of device
or node in ArchiMate depending on the level of abstraction.
In ArchiMate a device is a specialization of a node and is
defined as its physical part. Hence, a device together with
system software can constitute a node. For the case of an
IED it can be said to be composed of hardware together with
a real-time operating system and consequently constituting a
node. Depending on the context, an IED can represent either
an application component, as described in the application
layer mapping, or a node, consisting of a physical device
together with system software. In our case, an IED is
primarily mapped as a node, since applications are not part
of SCL. However, to address functional compatibility of
IEDs, i.e. support for certain functionality, application
components may also need to be taken into consideration.
Moreover, all devices connected to a subnetwork can
directly communicate to each other, without an intervening
router which is a kind of node. A router however enables
communication access between subnetworks. The
functionality of a router can directly be hosted by an IED,
providing both communication between two subnetworks
and the functionality of its assigned LNs.
The communication system model in SCL is used to
model logical connections between components and not the
physical structure. As for example, an access point may
model a physical port or a logical address of a server IED to
which clients can connect, but not the physical components
connecting them. A subnetwork models the connecting node
for direct communication between access points [17]. A
suitable mapping is to view the subnetwork as a kind of
network. Furthermore, the access point is a kind of
infrastructure interface where the functionality offered by a
node can be accessed by other nodes and application
components.
Communication services, although not included in the
SCL object model, are also part of SCL and define services
offered by IEDs. An IED contains a service capability list
with all offered communication services. A list of service
capabilities is presented in 61850-6, for example ReadWrite,
GOOSE, GetDirectory etc, all which are kinds of
infrastructure services in ArchiMate.
VI. EXAMPLE
In this section the mapping is demonstrated by applying
the result to an example using SCL for the configuration of a
substation automation system. The SCL configuration used
for the example is based on a specification in IEC 61850-6
which includes the substation topology together with two
IEDs and the data flow them between. The focus of the
mapping is on the function syncro-check, a function for
connecting two unsynchronized power system or energize a
feeder, which can be modeled using ArchiMate as presented
in Figure 5.
Starting from the bottom, two IEDs D1Q1SB4 and E1Q1SB1
are defined in the SCL who are exchanging data for synchro-
check functionality. They are connected to each other over
the subnetwork W01. The IEDs are modeled as nodes even
though, as described in the mapping, are composed of
hardware, a real-time operating system and an application
component. The IEDs are interfacing each other via the
assess point S1 which enables the use of GOOSE (Generic
Object-Oriented Substation Events), an infrastructure service
realized by D1Q1SB1, and SMV (Sampled Measured
Values), realized by E1Q1SB1. The logical node RSYN
(synchronizing) uses the SMV service to access voltage
measurements, Vol, offered by the LN TVTR (voltage
transformer) which models the logical association to the
voltage transformer VTR. The required interface between
RSYN and TVTR is representing the required client-server
association to obtain access to remote logical nodes and their
data. The mandatory data of RSYN is Rel (release) which is
sent to CSWI for breaker position control.
Two breaker control functions, CSWI, are used in the
system setup; one for each circuit breaker (CBR). Since only
one of the control functions are remotely located, client-
server association is only required between them, as seen in
the figure.
 TABLE I. A MAPPING BETWEEN SCL AND ARCHIMATE

Infrastructure

Infrastructure
Data Object
Component
Application

Application

Application

New entity

Equipment
ArchiMate

Software
Interface

Interface
Function

Function

Network
Business

System
Service

Device
Node
SCL (IEC 61850)
Function(s) - - - - - - - - - - -
Subfunction - - - - - - - - - - -
Transformer - - - - - - - - - - -
Equipment - - - - - - - - - - -
Subequipment - - - - - - - - - - -
LNode - - - - - - - - - - -
Data - - - - - - - - - - -
Server - - - - - - - - - - -
Router - - - - - - - - - - -
IED - - - - - - - -
AccessPoint - - - - - - - - - - -
Subnetwork - - - - - - - - - - -
Service capability - - - - - - - - - - - -

Is a kind of
Is a part of

For remote access to the release data, Rel, of RSYN the
remote control switch function, i.e. the LN CSWI associated
with IED E1Q1SB1, uses the infrastructure service GOOSE.
The data Pos (position) of CSWI can be set depending on the
input data Rel. The function provided by the LNs CSWI is
then used by the two circuit breakers, CBR, for changing
their position from either stare OPEN to CLOSED, or vice-
versa. The circuit breaker is modeled as an equipment entity
with the business function Position.
VII. DISCUSSION AND FUTURE WORK
What has been shown in the presented work is the
possibility of integrating SA configurations based on SCL
into ArchiMate models. Although ArchiMate mainly is
intended for modeling ICT intense organizations, other
domains such as SA may also benefit from the capability of
integration into EA models. Furthermore, since the use of
ArchiMate has proven successful for quality analysis of
information system architectures, for example performance
and cost analysis [11], availability analysis [22], data
accuracy assessment [23], etc., similar analysis can be
applied to SA systems. By applying the result of the
mapping, SCL configurations could possibly be translated
into the structure of ArchiMate. A fact however worth
pointing out is that some entities used for architecture
analysis is not explicitly described in the SCL configuration,
for example application components. Although application
components normally are a bundled part of an IED, and
hence not independent from the physical infrastructure,
future implementations and systems may offer stand-alone
applications which can be implemented on any IED or PC.
One part that does somewhat suffer from the limited
scope of the SCL is the mapping to business entities. For
example the business functions assigned to equipment are
not explicitly described in SCL. Instead functions of
switchyard equipment are described by the relating LNs.
Another interesting aspect, suitable for future work, is the
application of automated enterprise architecture modeling.
As described in the introductions, SA systems can be
composed of 20-100 IEDs interconnected by networks and
thereby would require a fairly extensive modeling effort.
However, by using the XML configuration files, used for
configuration of SA systems according to SCL, it would be
possible to automate the extraction of SA system
specifications using IEC 61850 and for instance import the
architecture into an EA modeling tool.
 Figure 5. An example showing the application of ArchiMate to an SCL configuration
VIII. CONCLUSIONS
In this paper we have argued for and demonstrated the
ability to integrate models of SA systems configured using
SCL of IEC 61850 into ArchiMate based EA models. The
presented work identifies objects in SCL and maps them to
entities in ArchiMate. As been shown, many objects of SCL
can directly be mapped to ArchiMate; however, the business
domain does require certain modification. Although
ArchiMate is intended for IT intense organizations, it could
by small modifications be used for modeling other types of
organizations with the business mainly being represented by
functionality provided by hardware equipment, for example
within the power or processing industry, instead of people.
REFERENCES
[1] S. Kurpjuweit and R. Winter, “Viewpoint-based meta model
engineering,” in EMISA 2007: Proceedings of Enterprise Modelling
and Information Systems Architecures. Bonn, Germany: Gesellschaft
fr Informatik, Oct. 2007, pp. 143–161.
[2] P. Johnson and M. Ekstedt, Enterprise Architecture: Models and
Analyses for Information Systems Decision Making. Studentlitteratur,
2007.
[3] European Commission, European SmartGrids technology platform:
vision and strategy for europe’s electricity networks of the future.
UR 22040, Brussels, Belgium, 2006.
[4] Kostic, T., Preiss, O., Frei, C. “Understanding and Using the IEC
61850: A Case for Meta-Modelling,” Elsevier Journal of Computer
Standards & Interfaces, 2004.
[5] Preiss, O. and Wegmann, A., “Towards a Composition Model
Problem Based on IEC61850”, The Journal of Systems and Software,
Vol. 65/3, Elsevier Science, 2003, pp. 227–236.
[6] Paulo, R., Carvalho, A. “Towards Model-driven Design of
Substation Automation Systems”, CIRED 2005, Torino, Italy, 2005
[7] Hadeli, H. et al. “Generating Configuration for Missing Traffic
Detector and Security Measures in Industrial Control Systems Based
on the System Description Files”, 2009 IEEE International
Conference on Technologies for Homeland Security, Waltham,
Greater Boston, MA - USA, 11 - 12 May 2009
[8] Berg, M., Stamp, J. “A Reference Model for Control and Automation
Systems in Electric Power”, Tech. Rep. SAND 2005-1000C, Sandia
National Laboratories, 2005
[9] Braun, J., Gosbell, V. and Robinson, D., "XML Schema for Power
Quality Data", 17th International Conference on Electricity
Distribution (CIRED), May 2003, Barcelona, Spain, Session 2, Paper
No. 42.
[10] Hughes, J. “IntelliGrid Architecture Concepts and IEC 61850” IEEE
PES. T&D Conference Dallas May 2006
[11] M. Lankhorst, Enterprise Architecture at Work: Modelling,
Communication and Analysis. Springer, 2005.
[12] Recommended practice for architectural description. IEEE Standard
P1471, 2000.
[13] The Open Group, ArchiMate® 1.0 Specification. Van Haren
Publishing, 2009. http://www.opengroup.org/archimate,
http://www.opengroup.org/bookstore/catalog/c091.htm,
[14] IEC-TC57-WG10/11/12, Communications Networks and Systems in
Substations, International Electrotechnical Commission, Geneva,
International Standard IEC 61850-1..10, 2003.
[15] IEC 61346 Industrial systems, installations and equipment and
industrial products – Structuring principles and reference designations
(http://www.iec.ch)
[16] Preiss, O., Kostic, T., Frei, C. “Data Communications Standards: A
Case for the UML,” <<UML>> 2004 Conference, Industry Track,
Lisbon, Portugal, October 10-15, 2004.
[17] IEC TC 57, 2004, IEC 61850-6 Communication Networks and
Systems in Substations – Part 6: Substation Configuration
Description Language for communication in electrical substations
related to IEDs, IEC, Geneva, Switzerland.
[18] IEC TC 57, 2003, IEC 61850-1: Communication networks and
systems in substations – Part 1: Introduction and overview, IEC,
Geneva, Switzerland.
 [19] EPRI Guidelines for Implementing Substation Automation Using
IEC61850, the International Power System Information Modeling
Standard, 2004
[20] IEC TC 57, 2003, IEC 61850-7-3: Communication networks and
systems in Substations – Part 7-3: Basic communication structure for
substation and feeder equipment – Common data classes, IEC,
Geneva, Switzerland.
[21] IEC TC 57, 2003, IEC 61850-2: Communication networks and
systems in Substations – Part 2: Glossary, IEC, Geneva, Switzerland.
View publication stats
[22] König, J., Franke, U. and Nordström, L., “Probabilistic Availability
Analysis of Control and Automation Systems for Active Distribution
Networks”, to be published, Transmission and Distribution
Conference and Exposition (TDCE), New Orleans, USA, 2010
[23] Närman, P., Johnson, P., Ekstedt, E., Chenine, M., König, J.
”Enterprise Architecture Analysis for Data Accuracy Assessments”,
IEEE International Enterprise Distributed Object Conputing
Conference, 2009