7/28/2019 05628971

1/9

Mapping the Substation Configuration Language of IEC 61850 to ArchiMate

Johan Knig, Kun Zhu, Lars Nordstrm, Mathias Ekstedt, Robert Lagerstrm

Industrial Information and Control Systems,Royal Institute of Technology, KTH

Stockholm, Sweden

{johank, zhuk, larsn, mek101, robertl}@ics.kth.se

AbstractThis 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

enterprises 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 augmentedreliance 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 theirinformation systems and the trend is growing. Strategic andefficient management of the portfolio of systems is thusbecoming an increasingly important concern. Thereby,stakeholders need support for creating transparency betweenthe business and the supporting information systems and alsobetween the information systems as such. Not only is there aneed for a common understanding of an enterprises

information system portfolio but also support for rationaldecision making which prevents or reduces stakeholderssubjectivism in their decisions.

Enterprise Architecture (EA) is a discipline for managingan enterprises information system portfolio in relation to thesupported business. Metamodels, descriptive models on howto model the architecture, are one of the core components ofEA and can serve multiple purposes [1]: (i) to document theEA, (ii) to plan and design the EA, and (iii) to analyze the

EA. Analysis, in particular, closely relates to the use of EAand architectural models for decision-making [2].

Since modeling can be an effort and time consuming taskit is important that the metamodel serves the purpose of themodelers needs with precision. Domain specific models arepart of what assists the modeler to reduce the effort neededand enhance the precision of the models and hence do servean important purpose.

A domain with an augmented reliance on the support ofinformation systems is the power industry. The progressivefocus on the integration of renewable energy resources hasstressed the need for modernizing the power system. SmartGrid is the term commonly used to describe the vision of thefuture power grid. Such a modernized power system is beingpromoted as a way of addressing energy independence,global warming and emergency resilience issues. It is,according to the European Strategic Technology Platform, avision for creating a flexible, accessible, reliable andeconomical grid for the future [3]. To be able to do so thecapabilities of the power grid must be enhanced with newtechnology.

A main component for the vision to become a reality is

the development of technology standards. Withoutstandardizing the technology needed for a Smart Grid, powerutilities and system vendors will not be able to construct aflexible, accessible and reliable system in a cost efficientway. IEC 61850 is a standard developed by the InternationalElectrotechnical Commission (IEC) for the design ofSubstation Automation (SA) systems. A SA system isusually composed of 20-100 distributed IntelligentElectronic Devices (IED) connected via high-speedcommunication networks [4] and can be referred to as thebackbone of a Smart Grid. One of the primary objectives ofIEC 61850 is free allocation of functions which either can beexecuted locally, i.e. by a single IED, or in a distributedmanner over multiple IEDs [4].

The need for proper management of SA systems ismotivated both by their complexity and also by theirimportant role in the Smart Grid vision. The proposal ofusing EA, which has proven successful in other informationsystem domains, hopefully can support stakeholders inmanaging their SA system portfolio and their integration toother business domains.

Scope of the paper

The scope of this paper is to present a mapping betweenSCL of IEC 61850 and the EA framework ArchiMate. The

2010 14th IEEE International Enterprise Distributed Object Computing Conference Workshops

978-0-7695-4164-8/10 $26.00 2010 IEEE

DOI 10.1109/EDOCW.2010.35

60

2010 14th IEEE International Enterprise Distributed Object Computing Conference Workshops

978-0-7695-4164-8/10 $26.00 2010 IEEE

DOI 10.1109/EDOCW.2010.35

60

7/28/2019 05628971

2/9

need for a mapping will be argued for, and a demonstrationof the mapping will be presented applying the result to an SAconfiguration 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 generaldescription on the domain of substation automation and adescription of the IEC 61850 standard including the SCL ispresented. Section V is the locus of the main contribution,presenting a mapping between ArchiMate and the SCL ofIEC 61850. Section VI presents an example with the result ofthe mapping applied to a SCL configuration. Section VIIdiscusses the implications of the contribution and futurework. Finally, section VIII concludes the paper.

II. RELATED WORKS

Much work has been established in SA metamodelingdomain with different research focus. It is commonly the factthat domain specific standards, like the case for IEC 61850,

is proposed by domain experts who in most cases are ofinsufficient knowledge about the Information andCommunication Technology (ICT) systems in contrast to thesoftware engineers who actually have the implementationresponsibilities. The implicit domain knowledge and rigor inthe data specification makes the standard difficult to use bydevelopers often lacking the domain knowledge. In [4] and[5] feasibility studies concerning mapping of IEC 61850standard to UML modeling language are presented with theambition to enable both manual and semi-automatic (ifUML-based computerized analysis tools are available)analysis of the complex substation automation systemarchitecture. Moreover, a model driven IEC 61850 modelingapproach based an Automation Systems Modeling Language

(ASML), an extension of UML subset, can be found in [6].Such an approach could facilitate next generation SAsystems, capable of handling system object models in anintegrated engineering environment.

In [7] the authors propose a modeling approach which iscapable of automatically generating system configuration forsecurity measures from description file together with itsapplication to IEC 61850 Substation ConfigurationDescription (SCD) files (part of SCL). Further, in [8] aSCADA reference architecture is generated by object-rolemodeling approach. Its usage is two-folds; first to generalizesecurity issues in automation systems within the powersystem domain and secondly to compare it with the initiatedsystem. When the non-applicability of the model indicates a

unique system configuration where significant securityanalysis could be warranted.In [9] an XML schema based solution for global power

quality analysis is proposed. Furthermore, in [10] Hughespresents the Intelligrid project which captures a general viewfor the business in power utilities and this work aims at

promoting for power industry standards development andmerging.

III. ARCHIMATE

ArchiMate is an open and independent modelinglanguage, i.e. metamodel, for enterprise architecture. Theprimary focus of ArchiMate is to support stakeholders how

to address concerns regarding their business and thesupporting ICT systems. It was first introduced by Lankhorstet al. in [11] and is partly based on the ANSI/IEEE 1471-2000, Recommended Practice for Architecture Descriptionof Software-Intensive Systems, also known as the IEEE 1471standard [12]. The Open Group accepted the ArchiMatemetamodel as a part of The Open Group ArchitectureFramework (TOGAF) in 2009 [13].

The ArchiMate metamodel consists of three layers; theBusiness layer, the Application layer and the Technologylayer. Where, technology supports the applications, which inturn supports the business. Each layer consists of a numberof 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 thearchitecture that perform the behavioral aspects.

One concept that is not widely used in the powercommunity is the concept of services. This is however usedextensively in ArchiMate. Services aim to encapsulate andhide the internal behavior of underlying layers and give theoverlying layers access to functionality from underlyinglayers through well-defined interfaces. For instance, anApplication Service is seen to encapsulate a number ofinternal Application Functions to make them useful to thebusiness actors of the business processes. By using services

the business actors neither have to consider the internalbehavior of the information systems nor the technology usedto realize the behavior. However, the use of services tomodel the relations between functions of separate layers isnot a requirement. For example, a business function candirectly be modeled with a relation to an applicationfunction. Figure 1. presents the complete ArchiMatemetamodel. For a more detailed description we refer to [13].

IV. SUBSTATION AUTOMATION AND IEC61850

It is commonly agreed upon that the prosperity of modernsociety is highly dependent of electricity. From a userperspective, the requirements are put on the supply of highquality power to a low cost. The generated power is

delivered through the network and finally distributed to theconsumers. The nodes in such a grid, whose basic functionsare transforming voltage and routing power flows, are calledsubstations. In the modern power system with a highautomation degree the substations are operated andcontrolled by SA systems.

6161

7/28/2019 05628971

3/9

ApplicationService

InfrastructureService

Business

ServiceBusiness

Interface

Application

Interface

InfrastructureInterface

Application

Function/

Interaction

Data Object

Business object Business

process/

function

Communicationpath

Network

Node

DeviceSystem Software

Artifact

Business role BusinessActor

BusinessCollaboration

Product

Represen-

tation

Contract

Event

Value

Application

Component

Business

Application

Application

Technology

Meaning

Application

Collaboration

Information aspect Behavior aspect Structure aspect

Information aspect Behavior aspect Structure aspect

Figure 1. The ArchiMate metamodel.

Besides the monitoring, control and protectionfunctionalities, SA systems also provide interfaces to theSupervisory Control and Data Acquisition (SCADA)systems and the Human Machine Interfaces (HMI), whichrealize both local and remote communication access. Allthese aforementioned SA system functions are facilitated byseveral IEDs, which are interconnected by communicationnetworks 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 theelectricity is delivered and where the control and protectionof the grid is executed. Transmission lines, transformers,switches, etc are catalogued in this subsystem. The othersystem is the ICT infrastructure composed by devices, suchas communication networks, routers and IEDs, whichrealizes the aforementioned SA functionalities.

A. IEC 61850 BasicsIEC 61850 is a standard developed by the International

Electrotechnical Commission (IEC) for the design of SAsystems [14]. The standard provides a vendor independent

framework for interoperability by defining communicationnetworks 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 summarizedbelow:

Functional modeling: the functions described byIEC 61850 are realized by collaboration between a

set of atomic functional units. These functionalunits can be implemented in different IEDs and

communicate with each other. The communicationbehavior 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.

6262

7/28/2019 05628971

4/9

Figure 2. Conceptual power system model illustrating the application of

IEC 61850.

Data modeling: IEC 61850 provides not only thesyntax but also the semantics for the data exchange

within SA systems.

Communication service modeling: IEC 61850 does

not restrict itself to any concrete communicationsolutions. Instead it defines an abstract

communication interface which specifies the

mapping of communication services and data

models to the main stream communicationprotocols. 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 onlylimited to describe the communication and relatedprocesses. The XML-based Substation

Configuration Language describing the SA systems

and the communication topology is presented inIEC 61850-6 [17].

B. Substation Configuration Language (SCL)Defining business goals and functions is not a main

objective of IEC 61850 and hence the business domain is notwell captured in the standard. However, one relevant partthat does define some objects that can be modeled accordingto the ArchiMate metamodel is the Substation ConfigurationLanguage (SCL) which is a descriptive language on theconfiguration of substation IEDs. Its full scope coversprimary power system structure description, desired SAfunction implementation based on LNs, and communicationwithin substations. The SCL object model is presented in

Figure 3.

Product model: consists of hardware (IED) wherethe SA functions are implemented. Server is an

object within IED which specifies access tocommunication system. LogicDevice is a group of

atomic piesce of SA function (LogicNode) that is

contained in as Serverof an IED. Data is the data

object contained by a LogicNode. Router is a

function assigns the connection of a single IED to

multiple AccessPoint. Clock indicates the locationof asubnetworkmaster clock.

Communication model: contains physicalcommunication network components such as

Subnetwork and AccessPoint. Subnetwork is the

aggregation of the process communication bus

where the measurements collected from the processlevel are flowing though and the bay

communication bus along which the monitoring,

control and protection related signals are

exchanged. AccessPoint specifies connections of

LogicDevice inIED to Subnetwork.

Figure 3. The SCL object model [17]

It is worth mentioning that the SCL object model does

not cover communication services which are provided byIEDs and actually part of the SCL. Besides, from a modeling

perspective, this model is not completed as well. For

instance, the entire hierarchical structure is in absence, like

the upper-class from which the used classes may be derived

as well as classes on a lower level, attributes etc. It restricts

itself to those concrete object types related substation

functional designation. Furthermore, it does not contain the

levels below Data, which are structurally defined in IEC

61850-7-3 [20].

C. Motivation for mapping SCL to ArchiMateAs stated in the previous section, ArchiMate is an open

and independent modeling language whose primary focus is

to assist stakeholders to address concerns regarding their

business and the supporting ICT systems, while IEC 61850

is an internationally accepted standard for substation

automation in the power industry, used as a baseline to

configure substations. However, it is less common to

6363

7/28/2019 05628971

5/9

address the dependency of supporting ICT systems with the

business processes of power utilities.

The mapping between SCL and ArchiMate enables theintegration of SA system to power utilitys 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 complexitytogether with the resulting specific communicationsservices, 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 IEC61850 and ArchiMate. The objective of the mapping is toidentify objects defined in SCL which have the relation isakind of to entities defined in ArchiMate. Some SCL objects

may however be composed of multiple ArchiMate entitieswith is a part ofrelation. The mapping is divided into threeparts - business, application and technology - in accordancewith the layers defined in ArchiMate.

The method that we have applied for mapping SCL toArchiMate is quite straight-forward. First we identifiedobjects in SCL together with their definitions using IEC61850-6 and IEC 61850-7 (part 1 to 4). In case of anyambiguity regarding definitions we used the glossarypresented in IEC 61850-2 [21]. Based on the profoundunderstating, 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 interactionbetween the business and the supporting information systems

an important first step is to define what we refer to as abusiness. Since SA systems are used for controlling andsupervising the power grid, and the power grid being thebusiness for the power system operators, it is reasonable tomap the business domain to the actual power grid. Hence,the business of a power utility managing a power grid is themonitoring, control and protection of the grid. The product isthus the delivery of electricity from the producers to theconsumers with a certain quality. In the context of SA thebusiness is delimited to the primary and secondaryequipment composing the substation. The behavior elementsof the business are represented by the primary equipment(e.g. breakers, switches, transformers, etc) which aresupported by secondary systems (e.g. control and protectionsystems). Each layer is presented in more detail below. Thecomplete result of the mapping in presented in TABLE I.

Business layer: The objects identified in SCL that aremapped to entities in the business layer of ArchiMate arefunction, subfunction, transformer, equipment andsubequipment, which all belong to the Substation model ofSCL. Objects such assubstation, voltagelevel, bay, terminaland connectivity node from the Substation model does modelstructural hierarchy of a substation, for example describing

that an IED is located at substation Xwith voltage level Y,and hence not identified with an is a kind of or is a part ofrelationto an entity of ArchiMate.

The business layer of ArchiMate primarily addressesentities of an organization with the interaction of businessactors. SA systems however lack the interaction with peopleand their behavior. Instead the behavior is allocated to

primary equipment and their functionality. Since primaryequipment involved in substation automation is offeringcertain functionality, it is neither a kind of business object,which is defined as a passive object, nor a kind of businessactor, given that a business actor is defined as anorganizational entity. Therefore, instead of mapping theequipment to any existing entity in ArchiMate, a new entityis 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 theArchiMate entity business function.

Figure 4. Introduced entity equipment

Its relation to the application layer is the same as for theentity business role of ArchiMate. Moreover, in contrast toan actor the equipment does not allow temporarycollaboration and thereby excludes the possibility ofperforming business interactions. Equipment can becomposed of subequipment, which is defined as a part ofequipment [17]. Equipment objects in SCL are: equipment -an apparatus within the switchyard; subequipment a part ofan equipment; and transformer a special equipment. The

function object in SCL represents functions that are part ofthe switch yard functionality which is a kind of businessfunction assigned to equipment. Functions may be composedof subfunctions - representing a hierarchical subpart of afunction also a kind of business function assigned toequipment.

Application layer: The objects identified in SCL that aremapped to entities in the application layer of ArchiMate arelogical node, data, server and IED which are objectsbelonging to the product model of SCL.

Applications in SA systems are not much different fromany other type of ICT system applications. However, thepurpose of IEC 61850 is not to standardize the applicationfunctions involved in substation operation. Instead,application functions are identified and descried in order todefine their communication requirements [18] and areconceptually realized by (collaborations of) primitive, atomicfunctional building blocks, the so-called Logical Nodes(LNs) [4]. A LN is the smallest part of an applicationfunction that can exchange information over the network[19]. The realization relationship between functions andservices in ArchiMate indicates how logical entities, what,such as services, are realized by means of more concrete

6464

7/28/2019 05628971

6/9

entities, how [13]. In [4], the functionality of a SA systemis described by a logical system, interpreted as what, thatis comprised of the set of functions (LNs), interpreted ashow, that operate in the substation environment. Hence, aLN is interpreted as a kind of application function instead ofas a service.

In ArchiMate an application function is defined as a

representation of a coherent group of internal behavior of anapplication component [13]. The internal behavior is aspreviously motivated a kind of LN; however, its relation toan 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 applicationcomponent module as a bundled part of it [19]. Hence, anapplication component is a part of an IED.

Server is a communication entity which allows LNs toaccess other LNs allocated to remote IEDs via thecommunication system. It is only possible to remotely accessLNs contained in a server. An application interface inArchiMate is defined as a declaration of how a componentcan connect with its environment [13]. It specifies how the

functionality of a component can be accessed by othercomponents (provided interface), or which functionality thecomponent requires from its environment (requiredinterface) [13]. Hence, server is interpreted as a kind ofapplication interface.

The object data in SCL models the data contained in aLN [17]. Data represents specific information, for examplestatus or measurement, and is a kind of data object entity inArchiMate.

Technology layer: The objects identified in SCL that aremapped to entities in the technology layer of ArchiMate arerouter, IED, access pointandsubnetworkwhich are objectsbelonging both to the product and communication model of

SCL. Another object also part of SCL, however not definedin the SCL object model, is service capability which also ispart of the mapping.

For the objects defined in SCL a central component is theIED, which, if excluding the application, is a kind of deviceor node in ArchiMate depending on the level of abstraction.In ArchiMate a device is a specialization of a node and isdefined as its physical part. Hence, a device together withsystem software can constitute a node. For the case of anIED it can be said to be composed of hardware together witha real-time operating system and consequently constituting anode. Depending on the context, an IED can represent eitheran application component, as described in the applicationlayer mapping, or a node, consisting of a physical device

together with system software. In our case, an IED isprimarily mapped as a node, since applications are not partof SCL. However, to address functional compatibility ofIEDs, i.e. support for certain functionality, applicationcomponents may also need to be taken into consideration.

Moreover, all devices connected to a subnetwork candirectly communicate to each other, without an interveningrouter which is a kind of node. A router however enablescommunication access between subnetworks. Thefunctionality of a router can directly be hosted by an IED,

providing both communication between two subnetworksand the functionality of its assigned LNs.

The communication system model in SCL is used tomodel logical connections between components and not thephysical structure. As for example, an access point maymodel a physical port or a logical address of a server IED towhich clients can connect, but not the physical components

connecting them. A subnetwork models the connecting nodefor direct communication between access points [17]. Asuitable mapping is to view the subnetwork as a kind ofnetwork. Furthermore, the access point is a kind ofinfrastructure interface where the functionality offered by anode can be accessed by other nodes and applicationcomponents.

Communication services, although not included in theSCL object model, are also part of SCL and define servicesoffered by IEDs. An IED contains a service capability listwith all offered communication services. A list of servicecapabilities is presented in 61850-6, for exampleReadWrite,GOOSE, GetDirectory etc, all which are kinds ofinfrastructure services in ArchiMate.

VI. EXAMPLE

In this section the mapping is demonstrated by applyingthe result to an example using SCL for the configuration of asubstation automation system. The SCL configuration usedfor the example is based on a specification in IEC 61850-6which includes the substation topology together with twoIEDs and the data flow them between. The focus of themapping is on the function syncro-check, a function forconnecting two unsynchronized power system or energize afeeder, which can be modeled using ArchiMate as presentedin Figure 5.Starting from the bottom, two IEDsD1Q1SB4 andE1Q1SB1are defined in the SCL who are exchanging data for synchro-

check functionality. They are connected to each other overthe subnetworkW01. The IEDs are modeled as nodes eventhough, as described in the mapping, are composed ofhardware, a real-time operating system and an applicationcomponent. The IEDs are interfacing each other via theassess point S1 which enables the use of GOOSE (GenericObject-Oriented Substation Events), an infrastructure servicerealized by D1Q1SB1, and SMV (Sampled MeasuredValues), realized by E1Q1SB1. The logical node RSYN(synchronizing) uses the SMV service to access voltagemeasurements, Vol, offered by the LN TVTR (voltagetransformer) which models the logical association to thevoltage transformer VTR. The required interface betweenRSYN and TVTR is representing the required client-server

association to obtain access to remote logical nodes and theirdata. The mandatory data ofRSYNisRel(release) which issent to CSWIfor breaker position control.

Two breaker control functions, CSWI, are used in thesystem setup; one for each circuit breaker (CBR). Since onlyone of the control functions are remotely located, client-server association is only required between them, as seen inthe figure.

6565

7/28/2019 05628971

7/9

TABLE I. AMAPPING BETWEEN SCL AND ARCHIMATE

SCL (IEC 61850) ArchiMate

Business

Function

Application

Function

Application

Component

Application

Interface

DataObject

Infrastructure

Interface

Infrastructure

Service

Node

Device

System

Software

Network

Newentity

Equipment

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, ofRSYNtheremote control switch function, i.e. the LN CSWIassociatedwith IEDE1Q1SB1, uses the infrastructure service GOOSE.The dataPos (position) ofCSWIcan be set depending on theinput data Rel. The function provided by the LNs CSWI isthen used by the two circuit breakers, CBR, for changingtheir position from either stare OPEN to CLOSED, or vice-versa. The circuit breaker is modeled as an equipmententity

with the business functionPosition.VII. DISCUSSION AND FUTURE WORK

What has been shown in the presented work is thepossibility of integrating SA configurations based on SCLinto ArchiMate models. Although ArchiMate mainly isintended for modeling ICT intense organizations, otherdomains such as SA may also benefit from the capability ofintegration into EA models. Furthermore, since the use ofArchiMate has proven successful for quality analysis ofinformation system architectures, for example performanceand cost analysis [11], availability analysis [22], dataaccuracy assessment [23], etc., similar analysis can beapplied to SA systems. By applying the result of the

mapping, SCL configurations could possibly be translated

into the structure of ArchiMate. A fact however worthpointing out is that some entities used for architectureanalysis is not explicitly described in the SCL configuration,for example application components. Although applicationcomponents normally are a bundled part of an IED, andhence not independent from the physical infrastructure,future implementations and systems may offer stand-aloneapplications which can be implemented on any IED or PC.

One part that does somewhat suffer from the limitedscope of the SCL is the mapping to business entities. Forexample the business functions assigned to equipment arenot explicitly described in SCL. Instead functions ofswitchyard equipment are described by the relating LNs.

Another interesting aspect, suitable for future work, is theapplication of automated enterprise architecture modeling.As described in the introductions, SA systems can becomposed of 20-100 IEDs interconnected by networks andthereby would require a fairly extensive modeling effort.However, by using the XML configuration files, used forconfiguration of SA systems according to SCL, it would bepossible to automate the extraction of SA systemspecifications using IEC 61850 and for instance import thearchitecture into an EA modeling tool.

6666

7/28/2019 05628971

8/9

Figure 5. An example showing the application of ArchiMate to an SCL configuration

VIII. CONCLUSIONS

In this paper we have argued for and demonstrated theability to integrate models of SA systems configured usingSCL of IEC 61850 into ArchiMate based EA models. Thepresented work identifies objects in SCL and maps them toentities in ArchiMate. As been shown, many objects of SCLcan directly be mapped to ArchiMate; however, the businessdomain does require certain modification. AlthoughArchiMate is intended for IT intense organizations, it could

by small modifications be used for modeling other types oforganizations with the business mainly being represented byfunctionality provided by hardware equipment, for examplewithin the power or processing industry, instead of people.

REFERENCES

[1] S. Kurpjuweit and R. Winter, Viewpoint-based meta modelengineering, in EMISA 2007: Proceedings of Enterprise Modellingand Information Systems Architecures. Bonn, Germany: Gesellschaftfr Informatik, Oct. 2007, pp. 143161.

[2] P. Johnson and M. Ekstedt, Enterprise Architecture: Models andAnalyses for Information Systems Decision Making. Studentlitteratur,2007.

[3] European Commission, European SmartGrids technology platform:

vision and strategy for europes electricity networks of the future.UR 22040, Brussels, Belgium, 2006.

[4] Kostic, T., Preiss, O., Frei, C. Understanding and Using the IEC61850: A Case for Meta-Modelling, Elsevier Journal of ComputerStandards & Interfaces, 2004.

[5] Preiss, O. and Wegmann, A., Towards a Composition ModelProblem Based on IEC61850, The Journal of Systems and Software,Vol. 65/3, Elsevier Science, 2003, pp. 227236.

[6] Paulo, R., Carvalho, A. Towards Model-driven Design ofSubstation Automation Systems, CIRED 2005, Torino, Italy, 2005

[7] Hadeli, H. et al. Generating Configuration for Missing TrafficDetector and Security Measures in Industrial Control Systems Basedon the System Description Files, 2009 IEEE InternationalConference 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 AutomationSystems in Electric Power, Tech. Rep. SAND 2005-1000C, Sandia

National Laboratories, 2005

[9] Braun, J., Gosbell, V. and Robinson, D., "XML Schema for PowerQuality Data", 17th International Conference on ElectricityDistribution (CIRED), May 2003, Barcelona, Spain, Session 2, Paper

No. 42.

[10] Hughes, J. IntelliGrid Architecture Concepts and IEC 61850 IEEEPES. 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 StandardP1471, 2000.

[13] The Open Group, ArchiMate 1.0 Specification. Van HarenPublishing, 2009. http://www.opengroup.org/archimate,http://www.opengroup.org/bookstore/catalog/c091.htm,

[14] IEC-TC57-WG10/11/12, Communications Networks and Systems inSubstations, International Electrotechnical Commission, Geneva,International Standard IEC 61850-1..10, 2003.

[15] IEC 61346 Industrial systems, installations and equipment andindustrial products Structuring principles and reference designations(http://www.iec.ch)

[16] Preiss, O., Kostic, T., Frei, C. Data Communications Standards: ACase for the UML, 2004 Conference, Industry Track,Lisbon, Portugal, October 10-15, 2004.

[17] IEC TC 57, 2004, IEC 61850-6 Communication Networks andSystems in Substations Part 6: Substation Configuration

Description Language for communication in electrical substationsrelated to IEDs, IEC, Geneva, Switzerland.

[18] IEC TC 57, 2003, IEC 61850-1: Communication networks andsystems in substations Part 1: Introduction and overview, IEC,Geneva, Switzerland.

6767

7/28/2019 05628971

9/9

[19] EPRI Guidelines for Implementing Substation Automation UsingIEC61850, the International Power System Information ModelingStandard, 2004

[20] IEC TC 57, 2003, IEC 61850-7-3: Communication networks andsystems 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.

[22] Knig, J., Franke, U. and Nordstrm, L., Probabilistic AvailabilityAnalysis of Control and Automation Systems for Active Distribution

Networks, to be published, Transmission and DistributionConference and Exposition (TDCE), New Orleans, USA, 2010

[23]Nrman, P., Johnson, P., Ekstedt, E., Chenine, M., Knig, J.Enterprise Architecture Analysis for Data Accuracy Assessments,IEEE International Enterprise Distributed Object ConputingConference, 2009

6868