Attachment 0 PDF

Ref.
Ares(2016)7200006 - 30/12/2016
Real proven solutions to enable active demand and distributed

generation flexible integration, through a fully controllable
LOW Voltage and medium voltage distribution grid
WP 2 – Innovative Distribution Grid Use

Cases and Functions
Report on the implementation of
the CIM as the reference data
model for the project
D2.4
2015 The UPGRID Consortium
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under
grant agreement No 646.531
WP 2 – INNOVATIVE DISTRIBUTION GRID USE CASES AND FUNCTIONS
D.2.1 REPORT ON THE IMPLEMENTATION OF THE CIM AS THE REFERENCE DATA MODEL FOR THE
PROJECT
PROGRAMME H2020 – Energy Theme
GRANT AGREEMENT NUMBER 646.531
PROJECT ACRONYM UPGRID
DOCUMENT D2.4
TYPE (DISTRIBUTION LEVEL) ☐Public

☒ Confidential
☐Restricted
DUE DELIVERY DATE 31/12/2016
DATE OF DELIVERY 30/12/2016
STATUS AND VERSION V1.2
NUMBER OF PAGES 130
WP / TASK RELATED WP2 / T2.3
WP / TASK RESPONSIBLE COMILLAS
AUTHOR (S) José Antonio Rodríguez Mondéjar (COMILLAS),

José María Oyarzabal Moreno (TECNALIA)
PARTNER(S) CONTRIBUTING Vattenfall, GE, Iberdrola, ITE, Energa, IEN, Powel
FILE NAME UPGRID_D2.4 Report on the implementation of

the CIM as the reference data model for the
project_v1.2
2 | 130
PROJECT
DOCUMENT HISTORY
VERS. ISSUE DATE CONTENT AND CHANGES
0.0 1/10/2016 Initial draft with TOC
0.1 1/12/2016 First draft by the partners
1.0 12/12/2016 First version of the document (for official review)
1.1 16/12/2016 Modification of Chapter 5.3 with data from the Polish demo
1.2 21/12/2016 Integration of the reviewer comments
3 | 130
PROJECT
EXECUTIVE SUMMARY
This deliverable reports the using of the CIM (Common Information Model) as the reference data model
of the project UPGRID. The CIM models the information that defines a power system, both the static
and the dynamic view, to facilitate the integration of EMS (Energy Management System) and DMS
(Distribution Management System) applications developed independently by different vendors. The CIM
is standardized through the IEC 61970, IEC 61968 and 62325 series. The CIM also provides two methods
for transmitting the CIM data using the XML language: the CIM RDF XML format for transferring the full
CIM model of a power system or for transferring changes in the CIM model; and the CIM XML format for
transferring simple changes in the CIM model or add new data, as meter readings.
The aims of using the CIM in the UPGRID project were:
 Common language to interoperate between working groups. This objective was fundamental in
the project. The development of distribution networks has historically followed different
approaches in the countries where demos are placed (Spain, Portugal, Sweden, and Poland). For
instance, components have different local names that depend on the technical background and
the country language.
 Common messaging between applications to be developed in the project. If an application is
going to be deployed in different demos, the CIM offers a common way, using XML messages, for
interchanging electrical data and related data.
 Fast development of applications. The CIM is based on object-oriented modelling using UML. So,
the development time of applications will be shortened thanks to this approach, because many
tools in the market provide a direct link between the UML model and the final application code.
These goals have been achieved through the following tasks performed at WP2 and WPs of the demos:
 CIM modelling of the data requirements of the components to be developed at WP2. This
modelling has provided a common vocabulary for the developers. Additionally, the best strategy
(CIM RDF XML format or CIM XML format) has been established for communicating the CIM data
between each component and other DMS applications. Also, a full profile based on CIM XML has
been generated for one of the components for guiding the development of the interfaces of this
component and the rest of the components of WP2.
 Development of a CIM interface based on CIM XML RDF between the different existing databases
and the LVNMS (Low Voltage Network Management System) in the Spanish demo. In this case,
an application gets the electrical and asset data disseminated in different databases and
generates the CIM data. The configuration and continuous update of the LVNMS are based on
this data. To achieve the objective, the CIM model was extended to fulfil the data requirements
of the Spanish demo and some limitations of the application. The CIM has proved their capacity
using its own mechanism for generating the extensions when the standard CIM classes cannot
4 | 130
PROJECT
fulfil the requirements. Nevertheless, the majority of the used CIM classes belongs to the
standard core of the CIM model.
 Development of an alternative profile for the Spanish demo. In the last task, some new classes
were added due to the application limitations. This task has generated a full model of the
distribution network without these limitations. Only 2 new classes were necessary to add. This
task has proved the power of the standard CIM core for modelling distribution systems and, also,
as in the last task, the ability to include new classes inside the CIM, if they are necessary.
 Development of a CIM interface, also based on CIM XML RDF, between the existing database and
the LVNMS in the Swedish demo. This task is similar to the Spanish demo, except that new
classes have not been added because the Swedish demo has fewer data requirements, and the
Swedish application for doing the translation to the CIM format is more flexible. This also proves
the adaptability of the CIM. Moreover, the use of CIM has allowed sharing experiences between
developer groups to facilitate the comparisons between solutions, and generate a practical
guideline about using CIM, in addition to the ample available bibliography.
 Development of a CIM interface in the Polish demo, based on the CIM XML format, for
transferring mainly reading data between applications. This proves the adaptability of CIM by
offering solutions of varying degrees of complexity: the CIM XML format for communicating a
simple set of data, the CIM RDF XML format for complex electric models.
This document has also displayed some disadvantages of working with the CIM. The main one is the
development from scratch of CIM solutions using only as input the IEC standard documents. The IEC
only provides PDF documents that cannot be copied. The IEC must provide the codes of the models as
the CIM XML schemas or the CIM RDF XML schemas. Another negative aspect is the learning curve of
the CIM model. The model is fractioned in hundreds of classes with many relationships between classes.
New tools are necessary that permit an engineer with a non-deep object oriented programming
background to deal with this issue.
In summary, the CIM has played, and it is playing, an important role in the UPGRID project because it
has provided a common vocabulary, a common way for modelling the distribution networks and a
common way for transmitting the associated data. And also, its flexibility permits one to include new
element types in the future in a way compatible with what has already been developed, without waiting
to be standardized.
5 | 130
PROJECT
TABLE OF CONTENTS
EXECUTIVE SUMMARY _________________________________________________________________ 4

TABLE OF CONTENTS __________________________________________________________________ 6
LIST OF FIGURES ______________________________________________________________________ 8
LIST OF TABLES ______________________________________________________________________ 11
ABBREVIATIONS AND ACRONYMS ______________________________________________________ 13
1. INTRODUCTION ___________________________________________________________________ 14
2. BRIEF INTRODUCTION TO CIM________________________________________________________ 15
2.1 THE CIM MODEL _______________________________________________________________________ 15
2.2 COMMUNICATION OF THE CIM DATA ______________________________________________________ 17
2.2.1 CIM RDF XML _________________________________________________________________________________ 17
2.2.2 CIM XML ____________________________________________________________________________________ 19
2.3 CIM PROFILES _________________________________________________________________________ 23

3. THE CIM PHOTO AT THE BEGINNING OF THE PROJECT ____________________________________ 25
4. THE APPLICATION OF CIM IN THE DEVELOPMENT OF WP2 COMPONENTS ____________________ 29
4.1 CIM VERSION HARMONIZATION ___________________________________________________________ 29
4.2 MATCHING BETWEEN COMPONENT DATA MODEL REQUIREMENTS AND THE CIM ___________________ 30
4.4 PROFILE DEVELOPMENT _________________________________________________________________ 38
4.4.1 LOAD AND GENERATION FORECASTING AT SECONDARY SUBSTATION ___________________________________ 39
4.5 STUDY ON THE USE OF THE CIM MODEL FOR BUILDING THE CORE OF AN APPLICATION _______________ 45
5. CIM AT THE DEMOS ________________________________________________________________ 49
5.1 SPANISH DEMO ________________________________________________________________________ 49
5.1.1 INTERFACE BETWEEN EXISTING DATABASES AND THE LVNMS __________________________________________ 49
5.1.2 DISTRIBUTION NETWORK MODEL WITHOUT TOOL LIMITATIONS _______________________________________ 59
5.2 SWEDISH DEMO _______________________________________________________________________ 71

5.3 POLISH DEMO _________________________________________________________________________ 79
5.3.1 METERING ___________________________________________________________________________________ 79
5.3.2 ELECTRIC OBJECTS _____________________________________________________________________________ 85
6. PRACTICAL GUIDELINE FOR USING THE CIM _____________________________________________ 97
6 | 130
PROJECT
7. CONCLUSIONS ____________________________________________________________________ 98
REFERENCES ________________________________________________________________________ 99
ANNEX I MATCHING TABLES BETWEEN COMPONENT DATA MODEL REQUIREMENTS AND THE CIM104
ANNEX II CIM XML RDF EXAMPLE OF A LOW VOLTAGE DISTRIBUTION NETWORK IN THE SPANISH
EXAMPLE 120
7 | 130
PROJECT
LIST OF FIGURES
FIGURE 1 EXAMPLE OF CIM CLASSES AND RELATIONSHIPS ........................................................................16

FIGURE 2 BASIC RDF MODEL........................................................................................................................17
FIGURE 3 EXAMPLE OF A CIM RDF TRIPLE ...................................................................................................18
FIGURE 4 EXAMPLE OF RDF SERIALIZATION USING XML ............................................................................18
FIGURE 5 EXAMPLE OF A DIFFERENCE CIM RDF FILE (SOURCE IEC 61970-552) .........................................19
FIGURE 6 EXAMPLE OF A CIM XML DOCUMENT: METER READINGS (SOURCE: IEC 61968-9) ....................20
FIGURE 7 METER READINGS XML SCHEMA (SOURCE: IEC 61968-9) ...........................................................21
FIGURE 8 MESSAGE ORGANIZATION (SOURCE: IEC 61968-100) .................................................................22
FIGURE 9 EXAMPLE OF MESSAGE FOR TRANSMITTING CHANGES IN THE POSITION OF SWITCHES
(SOURCE: IEC61968-100) .............................................................................................................................23
FIGURE 10 CLASS ASSET ...............................................................................................................................24
FIGURE 11 EXAMPLE OF CIM RDF XML DESCRIBING A SEGMENT OF AN AC LINE ......................................34
FIGURE 12 EXAMPLE OF CIM RDF XML DESCRIBING AN ANALOG VALUE ..................................................35
FIGURE 13 EXAMPLE OF CIM RDF XML DESCRIBING A DISCRETE VALUE....................................................35
FIGURE 14 EXAMPLE OF CIM RDF XML DESCRIBING OBJECTS OF A POWER FLOW ANALYSIS ...................36
FIGURE 15 EXAMPLE OF ENERGY INPUT DATA FILE (SOURCE [2] ) .............................................................41
FIGURE 16 SELECTED FIELDS FROM THE ORIGINAL METERREADINGS SCHEMA ........................................41
FIGURE 17 SNAPSHOT OF THE JAVA SOURCE TREE FOR THE CIM IMPLEMENTATION ...............................46
FIGURE 18 SNAPSHOT OF THE JAVA API FOR THE CIM IMPLEMENTATION ................................................47
FIGURE 19 USED CIM CLASSES IN THE INTERFACE BETWEEN EXISTING SYSTEM AND THE LVNMS ...........53
FIGURE 20 RDF XML EXAMPLE OF IBDSECONDARYSUBSTATION................................................................54
FIGURE 21 RDF XML EXAMPLE OF IBDDISTRIBUTIONTRANSFORMER ........................................................54
FIGURE 22 RDF XML EXAMPLE OF IBDFUSELV ............................................................................................55
FIGURE 23 RDF XML EXAMPLE OF IBDLOWVOLTAGELINE ..........................................................................55
FIGURE 24 RDF XML EXAMPLE OF IBDACLINESEGMENT.............................................................................55
8 | 130
PROJECT
FIGURE 25 RDF XML EXAMPLE OF IBDENERGYCONSUMER ........................................................................56

FIGURE 26 3-PHASE VIEW OF A FUSE ..........................................................................................................57
FIGURE 27 EXAMPLE OF THE DIFFERENCE CIM RDF XML FORMAT ............................................................59
FIGURE 28 GRAPHICAL REPRESENTATION OF A DISTRIBUTION NETWORK USING THE CIM MODEL .........60
FIGURE 29 CIM CLASSES FOR REPRESENTING THE ELECTRICAL VIEW OF THE DISTRIBUTION NETWORK .62
FIGURE 30 CIM CLASSES FOR REPRESENTING THE ASSET VIEW OF THE DISTRIBUTION NETWORK...........63
FIGURE 31 RDF XML EXAMPLE OF THE TRANSLATION OF IBDSECONDARYSUBSTATION ...........................67
FIGURE 32 RDF XML EXAMPLE OF THE TRANSLATION OF IBDDISTRIBUTIONTRANSFORMER ...................68
FIGURE 33 RDF XML EXAMPLE OF THE TRANSLATION OF IBDFUSELV ........................................................69
FIGURE 34 RDF XML EXAMPLE OF THE TRANSLATION OF IBDENERGYCONSUMER ...................................71
FIGURE 35 CIM CLASSES OF THE SWEDISH DEMO AND COMPARISON WITH THE SPANISH DEMO
(ELECTRICAL VIEW) ......................................................................................................................................73
FIGURE 36 CIM CLASSES OF THE SWEDISH DEMO AND COMPARISON WITH THE SPANISH DEMO (ASSET
VIEW) ...........................................................................................................................................................74
FIGURE 37 RDF XML EXAMPLE OF SECONDARY SUBSTATION ....................................................................75
FIGURE 38 RDF XML EXAMPLE OF TRANSFORMER .....................................................................................75
FIGURE 39 RDF XML EXAMPLE OF FUSE ......................................................................................................76
FIGURE 40 RDF XML EXAMPLE OF LINE SEGMENT ......................................................................................77
FIGURE 41 RDF XML EXAMPLE OF ENERGY CONSUMER .............................................................................77
FIGURE 42 XML SCHEMA OF METERREADINGS...........................................................................................79
FIGURE 43 XML SCHEMA OF GETMETERREADINGS ....................................................................................79
FIGURE 44 XML SCHEMA OF GETMETERREADSCHEDULE ...........................................................................80
FIGURE 45 XML SCHEMA OF METERREADSCHEDULE .................................................................................80
FIGURE 46 ORIGINAL XML SCHEMA OF METERREADINGS DEFINED BY IEC 61968 ....................................81
FIGURE 47 REQUEST OF METER READINGS .................................................................................................83
FIGURE 48 RESPONSE WITH READINGS .......................................................................................................85
FIGURE 49 CIM CLASSES FOR FORWARDING OBJECT STATES .....................................................................86
FIGURE 50 SCHEMA MEASUREMENTS.XSD .................................................................................................87
FIGURE 51 CIM CLASSES FOR SWITCH STATE COMMANDS ........................................................................88
FIGURE 52 SCHEMA COMMANDS.XSD ........................................................................................................88
9 | 130
PROJECT
FIGURE 53 CIM CLASSES FOR FORWARDING FDIR SEQUENCES ..................................................................89

FIGURE 54 SCHEMA SWITCHINGPLANS.XSD ...............................................................................................90
FIGURE 55 CIM CLASSES FOR POTENTIAL OUTAGE INFORMATION EXCHANGE .........................................91
FIGURE 56 SCHEMA OUTAGES.XSD .............................................................................................................91
FIGURE 57 SCHEMA GETMEASUREMENTSKSD.XSD FOR GETTING MEASUREMENTS ................................92
FIGURE 58 SCHEMA CHANGEDMEASUAREMENTSKSD.XSD FOR SENDING THE MEASUREMENTS ............93
FIGURE 59 SCHEMA GETCIMXML FOR REQUESTING CIM RDF XML OR CIM XML DOCUMENTS ................94
FIGURE 60 MESSAGE FOR SENDING MEASUREMENTS ...............................................................................95
FIGURE 61 MESSAGE FOR SENDING COMMANDS ......................................................................................96
10 | 130
PROJECT
LIST OF TABLES
TABLE 1: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE SPANISH DEMO __________25
TABLE 2: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE PORTUGUESE DEMO ______26
TABLE 3: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE SWEDISH DEMO __________27
TABLE 4 CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE POLISH DEMO _____________28
TABLE 5: DIFFERENCES BETWEEN VERSIONS OF THE CIM MODEL (SOURCE IEC STANDARDS AND CIM
USER GROUP) _______________________________________________________________________29
TABLE 6: SECONDARY SUBSTATION MV RELATED DATA _____________________________________31
TABLE 7: CUSTOMER SMART METERS RELATED DATA _______________________________________32
TABLE 8. STRUCTURE EXAMPLE OF THE ENERGY INPUT DATA FILE (SOURCE: [2]) __________________39
TABLE 9. STRUCTURE EXAMPLE OF THE TEMPERATURE INPUT DATA FILE (SOURCE: [2]) ____________39
TABLE 10. STRUCTURE EXAMPLE OF THE ENERGYFORECAST.OUT DATA FILE (SOURCE: [2]) __________40
TABLE 11. STRUCTURE EXAMPLE OF THE ENERGYERROR.OUT INPUT DATA FILE (SOURCE: [2]) _______40
TABLE 12 DESCRIPTION OF THE SELECTED FIELDS FROM THE ORIGINAL METERREADINGS SCHEMA (IEC
61968-9) ___________________________________________________________________________42
TABLE 13 DESCRIPTION OF THE USED VALUES IN READING TYPE _______________________________43
TABLE 14 DEMO CIM FORMATS _________________________________________________________49
TABLE 15 NEW CLASSES FOR SUPPORTING THE INTERFACE BETWEEN EXISTING SYSTEM AND THE NEW
SCADA SYSTEM ______________________________________________________________________50
TABLE 16 TRANSLATION OF THE ATTRIBUTES OF THE NEW CLASSES DEFINED AT SECTION 5.1.1 ______63
TABLE 17 COMPARISON OF USED ATTRIBUTES IN SOME STANDARD CLASSES _____________________77
TABLE 18 COMPARISON BETWEEN SPANISH AND SWEDISH CIM MODELLING _____________________78
TABLE 19: PRIMARY SUBSTATION MV DATA _____________________________________________104
TABLE 20: MV FEEDERS DATA _________________________________________________________105
TABLE 21: SECONDARY SUBSTATION MV RELATED DATA ___________________________________106
TABLE 22: SECONDARY SUBSTATION LV RELATED DATA ____________________________________107
TABLE 23: LV FEEDERS RELATED DATA __________________________________________________109
TABLE 24: LV CABINETS RELATED DATA _________________________________________________109
11 | 130
PROJECT
TABLE 25: CUSTOMER SMART METERS RELATED DATA _____________________________________110

TABLE 26: CONSUMPTION/GENERATION PATTERNS AND HOME EQUIPMENT RELATED DATA _____113
TABLE 27: MV STATIC DATA___________________________________________________________116
TABLE 28: LV STATIC DATA ___________________________________________________________116
TABLE 29: OUTPUT DATA OF EXISTING STATE ESTIMATOR __________________________________119
12 | 130
PROJECT
ABBREVIATIONS AND ACRONYMS
CIM Common Information Model
DMS Distribution Management System
DT Distribution transformer.
EMS Energy Management Systems
ENTSO-E European Network of Transmission System Operators for Electricity
EPRI Electric Power Research Institute
FDIR Fault Detection, Isolation & Restoration
GML Geography Markup Language
GE General Electric
LV Low Voltage
LVNMS Low Voltage Network Management System
MV Medium Voltage
RDF Resource Description Framework
SCADA Supervisory Control and Data Acquisition
SQL Structured Query Language
UML Unified Modelling Language
XML eXtensible Markup Language
13 | 130
PROJECT
1. INTRODUCTION
The aims of using the CIM in the UPGRID project were:
 Common language to interoperate between working groups. This objective was fundamental in
the project. The development of distribution networks has followed different approaches in the
countries where demos are placed (Spain, Portugal, Sweden, and Poland). For instance,
components have different local names that depend on the technical background and the
country language.
 Common messaging between applications to be developed in the project. If an application is
going to be deployed in different demos, the CIM offers a common way, using XML messages, for
interchanging electrical data and related data.
 Fast development of applications. The CIM is based on object-oriented modelling using UML. So,
the development time of applications will be shortened thanks to this approach, because many
tools in the market provide a direct link between the UML model and the final application code.
This document gathers the relevant information about the application of the CIM in the UPGRID project
and how the above aims have been fulfilled. It has been organized in the following sections:
 A brief introduction to the CIM. The section summarizes the CIM model and the two methods,
the CIM RDF XML and the CIM XML, for transmitting CIM data. The main objective of this section
is to establish a basic CIM nomenclature that is going to be used in the rest of the sections.
 The CIM photo at the beginning of the project. This section presents the previous knowledge of
the demos related with the CIM before the starting of the UPGRID project. Also, it shows the
expected results at the end of the project. However, this deliverable does not check all the
expected results because the UPGRID project has not yet ended.
 The application of the CIM in the development of WP2 components. One of the objectives of
WP2 is the development of components to be used in the demos. Therefore, the CIM is a helper
for achieving these objectives providing common data modelling and data communication. This
section summarizes the use of the CIM in the development of WP2 components.
 The CIM at the demos. The section presents the developments related with the CIM in the
demos. The information is not complete because the CIM at the demos has not been completely
deployed.
 Practical guidelines, or recommendations, for using the CIM. The experience of using the CIM in
the UPGRID project permits one to generate a short list of practical guidelines in addition to the
guidelines generated by EPRI or the IEC.
Finally, the document has a section dedicated to the conclusions.
14 | 130
PROJECT
2. BRIEF INTRODUCTION TO CIM

The CIM models the information that defines a power system, both the static and the dynamic aspect.
The result is the CIM model of the power system. The CIM also provide two methods for transmitting
the CIM model using the XML language:
 CIM RDF XML for transferring the full CIM model of a power system or for transferring complex
changes in the CIM model.
 CIM XML for transferring simple changes in the CIM model or add new data, as meter readings.
So, the CIM is an ecosystem that provides a data model (the CIM model), a set of methods for
transferring the data associated with the model, and a set of guidelines for the extension of the model
or for using a subset of the model. Next sections provide more explanations about the CIM Model and
its transfer. For more explanations about the CIM, besides the standards, the introduction to the CIM
prepared by EPRI is an excellent starting point [22] . Also, the number 1 of volume 12 in IEEE Power and
Energy Magazine ([25] [26] [27] [28] [29] [30] [31] ) is a good introduction.
2.1 THE CIM MODEL

The CIM is standardized through the IEC 61970, IEC 61968 and 62325 series. The principal objective of
these standards is to facilitate the integration of EMS (Energy Management System) and DMS
(Distribution Management System) applications developed independently by different vendors. This
goal is achieved by the definition of the application program interfaces (APIs) to enable exchange
information between EMS applications and between DMS applications and between them
independently of how such information is represented internally [3] .
The standards IEC 61970-301, IEC 61968-11 and IEC 62325-301 define the common information model
(CIM) that specifies the semantics for this API. The CIM is a data model that represents all the major
elements in an electric company needed to model aspects as operation, topology asset management,
outage management, metering, etc. The model is based on the UML notation. The CIM describes the
elements or objects as classes and relationships between classes.
Figure 1 is an example of classes and relationships between classes used by the CIM for describing the
most relevant elements of a power system. The figure describes that a power geographical region
contains power sub-geographical regions. Each sub-geographical region contains or has substations.
Each substation could have one or more voltage levels (VoltageLevel), and each voltage level is
organized in bays. On the other hand, substations, voltage levels, and bays are a type of equipment
container (EquipmentContainer). An equipment container contains equipment or devices; for example,
a bay contains breakers, cables, fuses, etc. A ConductingEquipment (example: switch, fuse, cable) is a
type of equipment, designed to carry current, that has terminals (association to class Terminal). An
equipment is a type of power system resource.
15 | 130
PROJECT
cl a ss M a i n
IdentifiedObject
P SRTy pe +PSRType
0..1
0..*
+PowerSystemResources
IdentifiedObject
P ow er Sy st emResour ce
C onnect i v i t y NodeC ont a i ner
+Equipments
0..*
Equi pment C ont a i ner Equi pment
0..1
+EquipmentContainer
+ConductingEquipment +Terminals
1 0..* ACDCTerminal
C onduct i ngEqui pment Ter mi na l
0..*
IdentifiedObject
Geogr a phi ca l Regi on
+ConductingEquipment
+Region 0..1
+Regions 0..*
IdentifiedObject
SubGeogr a phi ca l Regi on
+Region 0..1
+Substations 0..*
Subst a t i on
+Substation
+Substation 1 0..1
+VoltageLevels 0..* +BaseVoltage 0..1

+VoltageLevel IdentifiedObject
V ol t a geLev el
0..* B a seV ol t a ge
+BaseVoltage 1
+VoltageLevel 0..1
+Bays 0..* 0..*

+Bays
Bay
FIGURE 1 EXAMPLE OF CIM CLASSES AND RELATIONSHIPS
16 | 130
PROJECT
The IEC 61970 series is mainly dedicated to model the general aspects of a power system. Figure 1 is one
of the main class organization of these standards. The IEC 61968 series complement these series in
order to cover the specific aspects of a distribution network as asset management, metering
management, work management, etc. IEC 62325 models the energy markets.
2.2 COMMUNICATION OF THE CIM DATA

For interchanging data between two systems that speak CIM, the IEC 61970, IEC 61968 and 62325 series
of standards propose two methods:
 CIM RDF XML. The IEC 61970-501 and IEC 61970-552 describe the method.
 CIM XML. The IEC 61968-3 to -9 and the IEC 62325 series describe it.
Following sections describes these methods.
2.2.1 CIM RDF XML
The Resource Description Framework (RDF) is a standard model for data interchange on the Web [12] .
It organizes the information as a set of triples, each consisting of a subject, a predicate, and an object.
The triple says that some relationship, the predicate, exists between the subject and the object. This
triple is also known as RDF triple or RDF statement. Each RDF triple is graphically represented as a node-
arc-node link (see Figure 2).
FIGURE 2 BASIC RDF MODEL
There are three types of nodes: IRI, literal, and blank node. An IRI (Internationalized Resource Identifier)
is a generalization of URI (Universal Resource Identifier) that permits a wider range of Unicode
characters. Literal is used for a value such as string, number, and date. Blank nodes are disjoint from IRIs
and literals. Figure 3 shows an example of description in RDF used by the CIM: the subject is
“ACLineSegment”, the predicate is “length” and the object is “12.3 km”. The example triple indicates
that the length of a segment of an AC line is 12.3 km.
From the point of view of the CIM model, a particular power system is a big basket that contains millions
of triples that describe the elements of the system and their relationships. This approach is far more
powerful that the classical based on predefined tables (SQL database). Nevertheless, the CIM standards
only specify the interfaces of applications, not the way of developing the applications.
17 | 130
PROJECT
FIGURE 3 EXAMPLE OF A CIM RDF TRIPLE
For communicating the triples, RDF uses the XML format. This operation is named serialization. Figure 4
shows an example based on Figure 3: the ACLineSegment, a segment of AC line, identified by
“#_f998d686-95b9-44d3-8987-377fb5da519b” (the subject) has a predicate “r”, the resistance, which
value is “0.0001” (the object). The figure shows 5 RDF triples in a concise way, sharing the same subject
(the ACLineSegment identified by “#_f998d686-95b9-44d3-8987-377fb5da519b”).
<cim:ACLineSegment rdf:about="#_f998d686-95b9-44d3-8987-377fb5da519b">
<cim:IdentifiedObject.name>Line_1_Segment_2</cim:IdentifiedObject.name>
<cim:Equipment.EquipmentContainer rdf:resource="#_1fd8cd35-03af-4b9b-835a-f3837ce94c25" />
<cim:Conductor.length>1</cim:Conductor.length>
<cim:ACLineSegment.r>0.0003</cim:ACLineSegment.r>
<cim:ACLineSegment.x>0.0001</cim:ACLineSegment.x>
</cim:ACLineSegment>
FIGURE 4 EXAMPLE OF RDF SERIALIZATION USING XML
In the case of the CIM, RDF is used in two levels:

 CIM model description. It permits the serialization of the CIM UML model. The result is an XML
file named CIM RDF Schema. For example, a CIM RDF Schema file says that a substation is a class
that inherits attributes and associations from EquipmentContainer (see Figure 1).
 Power system network description. It represents the specific information of a power network
described using the vocabulary defined by a CIM RDF Schema. The result is an XML file named
CIM RDF file (or CIM XML file, or simply CIM file). For example, a CIM RDF file says that a
particular power network has an AC line segment named Line_1_Segment_2 whose resistance is
0.0003 (see Figure 4)
The IEC 61970-501 standardizes the translation of the CIM UML model to the CIM RDF Schema. The
standard uses the vocabulary defined by the World Wide Web Consortium (W3C) as rdfs:Class,
rdfs:Literal and rdfs:subClassOf. For instance, rdfs:Class is used for defining that a Substation is a class,
and rdfs:subClassOf for defining that a Substation inherits from EquipmentContainer its attributes and
associations (see Figure 1). Each official version of the CIM UML model has an associated official CIM
RDF Schema.
The IEC 61970-552 standardizes the use of the vocabulary defined by the CIM RDF Schema for
describing the specific data of a power network. It defines two methods for describing a power network
or the data related to a power network:
18 | 130
PROJECT
 Full model. It represents all the information necessary for representing a power network or an
aspect of the power network. As XML is verbose and the power network could be huge, a full
model CIM file is frequently transmitted compressed. The text of Figure 4 is part of a full CIM
RDF file.
 Difference model. It only describes the change occurred in a power network. It allows to reduce
the volume of information that two systems interchange. The difference vocabulary includes
operations as add, delete or change elements of a power network data. Figure 5 is an example of
difference CIM RDF file for deleting a power transformer.
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cim="cim-namespace-uri"
xmlns:dm="difference-model-namespace-uri" xml:base="urn:uuid:">
<dm:DifferenceModel rdf:about="#_26cc8d71-12f1-4de9-9e68-125d95073a75">

<dm:reverseDifferences rdf:parseType="Statements">
<cim:PowerTransformer rdf:about="#_41bb4445-6756-43fa-9e5a-48B6cd71790e">

</cim:PowerTransformer>

</dm:reverseDifferences>
</dm:DifferenceModel>
</rdf:RDF>
FIGURE 5 EXAMPLE OF A DIFFERENCE CIM RDF FILE (SOURCE IEC 61970-552)
2.2.2 CIM XML
The CIM RDF XML is the appropriated method for transmitting data when there are horizontal (links
between elements at the same level) and vertical relationships between the elements. The description
of a distribution network is a good example. In the case of only vertical relationships (or parent-child
relationships), the use of XML, where the syntax is defined by an XML schema, is the right solution. This
approach, named CIM XML, is followed by IEC 61968 and IEC 62325 series for transmitting data and
commands as meter readings, customer switching commands, meter firmware upgrade, work orders,
market participant information, bid and allocate capacity data, etc.
Figure 6 is an example of a CIM XML document for transmitting the readings of a meter. This example
communicates two readings of the meter 63.89.98.184. The tag “0.0.0.1.4.1.12.0.0.0.0.0.0.0.0.3.72.0”
indicates that the type of the reading value is bulk energy. Figure 7 shows the XML Schema that must
fulfill the example of Figure 6. The XML schema is an XML document that defines the structure of
another XML document: the XML elements and attributes, the number and order of child elements, the
data types for elements and attributes, and default and fixed values for elements and attributes.
Typically, a graphical representation based on the XMLSpy tools (www.altova.com) is used for
representing the organization of the XML schema (see Figure 7). Notice that the XML document of
Figure 6, the data to be transferred, and Figure 7, the graphical view of the XML schema, have the same
organization.
19 | 130
PROJECT
<mr:MeterReadings xmlns:mr="http://iec.ch/TC57/2011/MeterReadings#">
<mr:MeterReading>
<mr:Meter>
<mr:Names>
<mr:name>63.89.98.184</mr:name>
<mr:NameType>
<mr:description>This is an endpoint serial number</mr:description>
<mr:name>EndpointID</mr:name>
<mr:NameTypeAuthority>
<mr:description>AssetManagementSystem</mr:description>
<mr:name>com.company.assets</mr:name>
</mr:NameTypeAuthority>
</mr:NameType>
</mr:Names>
</mr:Meter>
<mr:Readings>
<mr:timeStamp>2011-12-05T17:21:40.628Z</mr:timeStamp>
<mr:value>25.633</mr:value>
<mr:ReadingType ref="0.0.0.1.4.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</mr:Readings>
<mr:Readings>
<mr:timeStamp>2011-12-05T17:21:40.628Z</mr:timeStamp>
<mr:value>10.0</mr:value>
<mr:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.38.0"/>
</mr:Readings>
</mr:MeterReading>
</mr:MeterReadings>
FIGURE 6 EXAMPLE OF A CIM XML DOCUMENT: METER READINGS (SOURCE: IEC 61968-9)
20 | 130
PROJECT
FIGURE 7 METER READINGS XML SCHEMA (SOURCE: IEC 61968-9)
The IEC 61968 series and IEC 62325 series defines the XML schemas that the CIM XML documents must
fulfill for interchanging CIM data through the interface of the applications that use the CIM XML format.
Each standard of these series is dedicated to cover a specific aspect. Example:
 IEC 61968-3: Interface for network operations.
 IEC 61968-4: Interface for record and asset management.
 IEC 61968-6: Interface for maintenance and construction.
21 | 130
PROJECT
 IEC 61968-8: Interface for customer operations.

 IEC 61968-9: Interface for meter reading and control.
 IEC 62325-451-1: Acknowledgement business process and contextual model for CIM European
market.
 IEC 62325-451-2: Scheduling business process and contextual model for CIM European market
In any case, the XML schema defined by these standards (named CIM XML Schema) are based on the
CIM model. The IEC62361-1 and IEC62361-100 define how to build a new XML Schema from the CIM
model. This standard permits to add new XML schemas, private or public, in a harmonised way.
From the point of the interface of the applications, the method for transmitting the XML documents
(CIM XML or CIM RDF XML) must be standardised. The IEC 61968-100 defines the method. It uses an
XML message, defined by XML schema, with a mandatory field, the Header, and three optional fields:
Request, Reply, and Payload. Figure 8 presents the structure of the message using the graphical notation
of the XML Schema. The header element provides information about how to interpret the remainder of
the message. The request element contains parameter relevant to a request message as the time
interval for a search. The reply element contains an indication of success or error to a request message.
The payload element transports the data to be communicated. So, the XML document to be transferred
is placed in the Payload field. The IEC 61968-100 defines also the messages sequences for requesting
data and transmitting events.
FIGURE 8 MESSAGE ORGANIZATION (SOURCE: IEC 61968-100)
Figure 9 shows an example of a message for transmitting events. In this case, the new position of two
switches is transferred.
22 | 130
PROJECT
<ns0:EventMessage xmlns:ns0="http://www.iec.ch/TC57/2008/schema/message">
<ns0:Header>
<ns0:Verb>changed</ns0:Verb>
<ns0:Noun>Switches</ns0:Noun>
<ns0:Revision>1</ns0:Revision>
</ns0:Header>
<ns0:Payload>
<m:Switches xsi:schemaLocation="http://iec.ch/TC57/2008/CIM-schema-cim12#Switches.xsd"
xmlns:m="http://iec.ch/TC57/2007/CIM-schema-cim12#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance">
<m:Switch>
<m:mRID>363482488448</m:mRID>
<m:normalOpen>false</m:normalOpen>
</m:Switch>
<m:Switch>
<m:mRID>894094949444</m:mRID>
<m:normalOpen>true</m:normalOpen>
</m:Switch>
</m:Switches>
</ns0:Payload>
</ns0:EventMessage>
FIGURE 9 EXAMPLE OF MESSAGE FOR TRANSMITTING CHANGES IN THE POSITION OF SWITCHES (SOURCE: IEC61968-100)
2.3 CIM PROFILES

Another important aspect to be considered about CIM is the CIM profiles. A CIM profile is a subset of
the more general CIM [14] . Two applications that are going to interoperate need to share the same CIM
profile: CIM objects to be interchanged must be available and have the same interpretation in both
sides. CIM is plenty of optional features. So, both sides must have an agreement about the options to be
used. For example, an object that fulfils the class Asset (see Figure 10) could have all the attributes that
appear in the class definition and other, none of them. Both objects comply with the definition of Asset
because the multiplicity of the attributes is [0..1]; in other words, the attributes are optional. Therefore,
if an application needs to receive the information about the serial number of an equipment
(serialNumber), a document must specify that this attribute is mandatory for this case. This type of
document is denominated a profile.
23 | 130
PROJECT
cl a ss A sset sO v er v i ew
IdentifiedObject
A sset
+ acceptanceTest: AcceptanceTest [0..1]

+ baselineCondition: String [0..1]
+ baselineLossOfLife: PerCent [0..1]
+ critical: Boolean [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ inUseDate: InUseDate [0..1]
+ inUseState: InUseStateKind [0..1]
+ kind: AssetKind [0..1]
+ lifecycleDate: LifecycleDate [0..1]
+ lifecycleState: AssetLifecycleStateKind [0..1]
+ lotNumber: String [0..1]
+ position: String [0..1]
+ purchasePrice: Money [0..1]
+ retiredReason: RetiredReasonKind [0..1]
+ serialNumber: String [0..1]
+ status: Status [0..1]
+ type: String [0..1]
+ utcNumber: String [0..1]
FIGURE 10 CLASS ASSET
In the CIM world, there are two kinds of profiles:

 Standard profiles. They are specific standards that specify the minimum subset of the model CIM
for managing a specific view. For example, IEC 61970-456 specifies the required CIM subset to
describe a steady-state solution of a power system case, such is produced by power flow or state
estimation applications [21] .
 Private profiles. They are profiles that only works inside a company or they are the result of an
agreement between companies for interchanging CIM data. Normally, these profiles include
extensions to the standard CIM. IEC 61970-301 dedicates the section “Modelling guidelines” to
provide guidelines on how to maintain and extend the CIM [3] .
24 | 130
PROJECT
3. THE CIM PHOTO AT THE BEGINNING OF THE PROJECT

The UPGRID deliverable D1.3 [1] showed that the previous experience of the demos about using CIM
was practically null. TABLE 1 to TABLE 4 from deliverable D1.3 summarizes the used standards at the
demos. Only the Spanish demo has a very limited experience of using CIM. Nevertheless, these tables
show that all demos are interested in using CIM, except the Portuguese demo.
TABLE 1: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE SPANISH DEMO
DEMO BASE DEMO DEVELOPED UNDER UPGRID
Used standard protocols Proposed standard protocols to be used

DLMS COSEM PRIME 1.3.6
 Transport layer for SMs provided data 4-  IP convergence sublayer
32/PRIME
 Transport layer for line monitoring units CTI
hdlc/rs485
 Data model for SMs: T5 Spanish Companion
Specification
 Data model for line monitoring units CTI: CTI
Companion Specification
PRIME 1.3.6 SNMPv3 for MIB collection
 4-32 convergence sub-layer
 SMs profile
ICCP / TASE2 (IEC 60870-6-503) ICCP / TASE2 (IEC 60870-6-503)
IEC 60870-5-104 IEC 60870-5-104
CIM (IEC 61968, IEC 61970, IEC 62325)
Development of new protocols / Development of
extensions to a standard protocol / protocol
Used proprietary protocols
profiles to be developed (and Possible
standardization process)
STG-DC 3.2 for SMs management DLMS COSEM
Data model for line monitoring units CTI: CTI
Companion
Extend STG 3.2 to include Line Supervision

Particular profile of CIM
25 | 130
PROJECT
TABLE 2: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE PORTUGUESE DEMO

IEC60870-5-104 IEC60870-5-104
 Light Protocol Implementation Document  Light Protocol Implementation Document
(LPID) for IEC 60870-5-104 defined by EDP (LPID) for IEC 60870-5-104 defined by EDP
Distribuição Distribuição
PRIME PRIME
 Version 1.3.6 established by PRIME Alliance  Version 1.3.6 established by PRIME Alliance
 PRIME MAC & PHY layers (PLC)  PRIME MAC & PHY layers (PLC)
 PRIME 4-32 convergence sub-layer  PRIME 4-32 convergence sub-layer
DLMS/COSEM DLMS/COSEM
 EDP Box data model – EDP companion for  EDP Box data model – EDP companion for
DLMS/COSEM DLMS/COSEM
Web services SOAP (STG-DC 3.1.c) Web services SOAP (STG-DC 3.1.c)
 Central System – DTC interface based on DC  Central System – DTC interface based on DC
INTERFACE SPECIFICATION, v3.1.c, authored by INTERFACE SPECIFICATION, v3.1.c, authored by
Iberdrola but currently under the responsibility of Iberdrola but currently under the responsibility of
the Prime Alliance the Prime Alliance
 EDP profile with specific Orders (Bnn) and  EDP profile with specific Orders (Bnn) and
Reports (Snn) - WS_STG.DTC_perfil.EDP_v5.13 Reports (Snn) - WS_STG.DTC_perfil.EDP_v5.13
FTP (RFC959) FTP (RFC959)
MODBUS over serial line MODBUS over serial line
 MODBUS APPLICATION PROTOCOL  MODBUS APPLICATION PROTOCOL
SPECIFICATION, V1.1b for HAN interface of the SPECIFICATION, V1.1b for HAN interface of the
EDP Box EDP Box
extensions to a standard protocol / protocol profiles
to be developed (and Possible standardization
process)
HAN interface N/A
 Data model and communication protocol for
the HAN interface of the EDP Box
26 | 130
PROJECT
TABLE 3: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE SWEDISH DEMO

OSGP ETSI GS OSG 001 - Open Smart Grid Protocol for OSGP
both measurements and events between SM<->DC<-
>AMI Head End system
GS2* - Message based protocol for measurement GS2
values (meter stands and hourly values) between AMI
Head End and Vattenfall (MDMS)
*GS2 stands for "GränsSnitt2" or "Interface2", which is

an object-oriented data model, similar to XML, for
handling metering and settlement information.
XML - Message based protocol for events from SM from XML
AMI Head End system and Vattenfall PER-system
(PerformanceEventReport system)
PLC - Power Line Communication, using both A and C PLC
band, and different frequencies. Communication carrier
between the SM and DC.
GPRS/3G - Communication between the field installed GPRS/3G/CDMA
IED, e.g. DC, and telecommunication service provider
hardware environment
IEC-60870-5-104 - Communication between FPI and
SCADA-DMS and/or fault analysis tool in MV
substation
IEC-60870-5-104 - Communication between
secondary substation (10-20/0.4 kV) and SCADA-
DMS
DNP3 (IEEE Std. 1815) - Distributed Network
Protocol might be used by one RTU manufacturer,
while -104 implementation is finalized
ZigBee (IEEE 802.15.4) - Communication between
wireless current sensor and RTU
CIM - Common Information Model for data
exchange between Network Information System
and LV SCADA
FTP (RFC959) over GPRS
extensions to a standard protocol / protocol
profiles to be developed (and Possible
standardization process)
N/A N/A
27 | 130
PROJECT
TABLE 4 CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE POLISH DEMO

PRIME Specification revision 1.3.6. PRIME Alliance IEC 60870-5-104 Std.: Telecontrol equipment and
systems – Part 5-104: Transmission protocols –
Network access for IEC 60870-5-101 using standard
transport profiles. Second edition, 2006
DLMS/COSEM Architecture and Protocols. Green IEEE 1815 Std.: IEEE Standard for Electric Power
book – 8th edition. Technical report. DLMS User Systems Communications—Distributed Network
Association, 2014 Protocol (DNP3). Revised edition, 2012
COSEM Identification System and Interface Classes.
Blue Book – 12th edition. Technical report. DLMS
User Association, 2014.
STG-DC 3.1 IEC 61970 Std.: Energy Management System
Application Program Interfaces EMS-API
IEC 61968 Std.: Application Integrational Electric
Utilities - System Interfaces for Distribution
Management
IEC 61968-100 Std.: Application integration at electric
utilities - System interfaces for distribution
management - Part 100: Implementation profiles
IEC 62325-301 Std.: Framework for Energy Market
Communication
extensions to a standard protocol / protocol profiles
to be developed (and Possible standardization
process)
DC-SAP (Data Concentrator - Simple Acquisition DLMS/COSEM Extensions for PRIME PLC LV
Protocol) monitoring and control unit
Also, the tables show that the initial wishes about using CIM are ambiguous and different:
 Spanish demo wishes to achieve a specific CIM profile.
 Swedish demo is going to use CIM for data exchange between Network Information System and
LV SCADA.
 Polish demo is going to use all the IEC 61970 series, the IEC 61968 series and, even, the IEC
62325-301 dedicated to the energy market.
28 | 130
PROJECT
4. THE APPLICATION OF CIM IN THE DEVELOPMENT OF WP2

COMPONENTS
The application of CIM in the development of WP2 components has followed these steps:
 CIM version harmonization.
 Matching between functionalities and the CIM.
 Profile development.
 Study on the use of the CIM model for building the core of an application.
4.1 CIM VERSION HARMONIZATION

At the beginning of the UPGRID project, the groups involved in the development of components were
using different versions of the CIM model. This issue is not a problem, because a new version is normally
compatible with older versions, except if the used version is older than version v15. Version v15
reformulates the power transformer for supporting balanced and unbalanced networks in a way that is
not compatible with older versions.
The current version of the model CIM is v15. The core of this model was published in IEC61970-
301:2013-12 [3] as edition 5. The edition 6, that corresponds to v16, will be published in early 2017. The
IEC working groups are working now with version v17. Table 5 shows the major changes between
versions 14, 15 and 16. The change of the transformer model from version 14 to version 15 has been
highlighted. This change is a great improvement from the point of view of the electrical modelling of the
distribution networks.
TABLE 5: DIFFERENCES BETWEEN VERSIONS OF THE CIM MODEL (SOURCE IEC STANDARDS AND CIM USER GROUP)
Standard version Major changes from the previous edition
IEC 61970-301  Several classes have been moved from IEC 61970 to the Assets package in IEC 61968.
 Zero and negative sequence impedance terms have been added where missing.
2013-05 Ed4  New StateVariables package has been added to support exchange of network model
(CIM model v14)  Additional classes that have been added included:
– PhaseTapChanger
– RatioTapChanger
– ImpedanceVariationCurve
– RatioVariationCurve
– TapSchedule
– SwitchSchedule
– PhaseVariationCurve
– EquivalentInjection added to the Equivalents package
– WindGeneratingUnit and NuclearGeneratingUnit added as subtypes of GeneratingUnit
 Classes that were removed included:
– Company
– HeatExchanger
– MeasurementType class removed and replaced with attribute
Measurement.measurementType.
29 | 130
PROJECT
– Datatypes ShortLength and LongLength were removed and replaced with Length.
– Load, CustomerLoad, and InductionMotorLoad.
– Subtypes of ConformLoad and NonConFormLoad
 Various editorial changes to clean up the UML model.
IEC 61970-301  Transformer models have been modified to be consistent for use by distribution and
2013-12 Ed5 transmission purposes. Additionally, the tap changer model was updated to more
clearly reflect the intended usage without relying upon rules for which attributes are
(CIM model v15) appropriate in which situations.
 A more general and clear naming approach was added and several ambiguous
attributes related to naming were dropped. The approach allows for users to define
new name domains and to give them their own unique description.
 Phase component wires models have been enhanced to describe internal phase
specificattributes and connections.
 Addition of diagram layout models to facilitate the exchange of diagram layout
information.
 Addition of new data types for Decimal, and clean-up of date and time types.
 Addition of new Compound data types to the Domain package.
IEC 61970-301  New model for grounding including Petersen coils.

Ed6 draft (CIM  Models for HVDC
 Addition of Static Var Compensation models.
model v16)
 Phase shift transformer updates.
 Short circuit calculations based on IEC 60909.
 Addition of non-linear shunt compensator.
 Addition of model for steady state calculation inputs, Steady State Hypothesis.
 Addition of base frequency model.
 Corrections of several smaller issues, e.g. issues found at ENTSO-E interoperability
tests.
 UML clean up.
At the beginning of the project, the decision was to adopt the version v16 in WP2 in order to avoid the
editorial errors of v15. From the point of UPGRID data modelling, version 16 does not add new relevant
classes to version 15. Additionally, in the case of model extensions and model errors, the draft of version
v17 will be consulted in order to follow a similar approach. This draft has important improvements from
the point of view of asset management.
4.2 MATCHING BETWEEN COMPONENT DATA MODEL REQUIREMENTS

AND THE CIM
After version decision, the next step was to model, from the point of view of CIM, the data requirements
of the components to be developed at WP2, in order to use a common vocabulary. Additionally, the
best strategy was studied for communicating the CIM data between each component and other DMS
applications.
TABLE 6 and TABLE 7 show an partial example of the translation of the data requirements gathered in the
functionalities defined in WP2 into the data classes that the CIM model provides. Annex I defines the full
30 | 130
PROJECT
translation. The “CIM class” column indicates the CIM class that best suits the data requirement. The
“CIM attribute” column indicates an attribute inside the class that represents the data in the case of a
simple data requirement. The column “WP2Cs” indicates the keyword of the WP2 component where the
modelling is going to be applied. The “CIM communication mechanism” column indicates the typical
CIM mechanism to transmit a set of this kind of data, using the nomenclature defined in section 2.2:
 CIM RDF XML.
 CIM XML. In this case, the XML schema is indicated.
The data of TABLE 6 are related with input and the output of a power flow analysis. Also, the packet
StateVariable could be used.
TABLE 6: SECONDARY SUBSTATION MV RELATED DATA

CIM
CIM
Nº Data Description CIM class communication WP2Cs
attribute
mechanism
Measured voltages on the HV side of
Analog S2.1.1-
1 Voltage the transformer in the secondary CIM RDF XML
AnalogValue A
substation
S2.1.1-
Measured active power flow through
Active Analog A
2 the HV side of the transformers in CIM RDF XML
power flow AnalogValue S2.1.3-
the secondary substation
B
Measured reactive power flow
Reactive through the HV side of the Analog S2.1.1-
3 CIM RDF XML
power flow transformers in the secondary AnalogValue A
substation
Measured current flow through the
Analog S2.1.1-
4 Current flow HV side of the transformers in the CIM RDF XML
AnalogValue A
secondary substation
Active Forecasted active power at Analog
power secondary substation for those AnalogValue S2.1.1-
5 CIM RDF XML
demand substations with no measurements MeasurementValu A
forecast available eSource
Reactive Forecasted active power at Analog
6 CIM RDF XML
Status of Measured status (open//close) of the
Discrete S2.1.1-
7 switching dynamically controlled switching CIM RDF XML
DiscreteValue A
elements elements
8 Date and Date and time information of the AnalogValue timeStamp CIM RDF XML All
31 | 130
PROJECT
CIM
CIM
attribute
mechanism
time of each temperature, active and reactive DiscreteValue
1
variable power measurement
(UTC, UNIX
Timestamp)
TABLE 7 shows an example of partial modelling of the data related to customers. Notice that the use of
ReadingQualityType field permits to distinguish between measured, projected and estimated. In the
case of measured, the ReadingQualityField field is not used.
TABLE 7: CUSTOMER SMART METERS RELATED DATA

CIM communication
Nº Data Description CIM class CIM attribute WP2Cs
mechanism
Measured
S2.1.1
active power
S2.1.3-
Active power at end user CIM XML:
1 MeterReading A
demand (kW) connection MeterReadings.xsd
S2.2.2
point per
WP8
phase
Measured
reactive S2.1.1
Reactive
power at end S2.1.3-
power CIM XML:
2 user MeterReading A
demand MeterReadings.xsd
connection S2.2.2
(kW)
point per WP8
phase
Power
Prosumer’s S2.1.3-
generation CIM XML:
3 generation MeterReading A
from the client MeterReadings.xsd
(kW) WP8
side
Demand
profile for the
consumers in
the group for
Total demand ReadingQualityType. CIM XML:
4 each day type MeterReading S2.2.1
profile category= Projected MeterReadings.xsd
considered.
The day type
might be a
combination
1
It is supposed the Time Stamp included in the records which contain the considered related data.
32 | 130
PROJECT
CIM communication
mechanism
of season and
workday/
weekend/
holiday
This value must
be calculated
Number of from the number
Number of consumers of objects of the CIM XML:
5 S2.2.1
Consumers belonging to class type UsagePointGroups.xsd
the group UsagePoint
associated to a
UsagePointGroup
Price profile
Electricity charged for CIM XML:
6 Tariff S2.2.1
Tariff the consumed PricingStructureConfig.xsd
electricity
Forecasted
active power
at end user
Active power connection S2.1.1
ReadingQualityType. CIM XML:
7 demand point per MeterReading S2.1.3-
category= Estimated MeterReadings.xsd
forecast phase if no B
real
measurements
are available
4.3 CIM RDF XML AND CIM XML EXAMPLES

In addition to the matching between component data requirements and the CIM, a series of general
examples of CIM XML RDF and CIM XML were prepared, in order to help the component developers.
The following sections present these examples.
4.3.1 CIM RDF XML
These examples come from CIMUG group (cimug.ucaiug.org).

4.3.1.1 ACLINESEGMENT
The XML text of Figure 11 describes a segment of an AC line using one object of the class
ACLineSegment and two objects of the class Terminal. The information between <cim:ACLineSegment
and </cim:ACLineSegment> defines the object of the class ACLineSegment. The fields bch (susceptance),
gch (conductance), r (resistance) and x (reactance) define the electric parameters of the segment. The
field length defines the length of the segment and is a case of inheritance. The attribute length is part of
33 | 130
PROJECT
the class Conductor, and ACLineSegment inherits from Conductor; so, the attribute length is part of the
class ACLineSegment. The two fields Terminals establish that the object of the class ACLineSegment has
two terminals. The yellow colour signals the link between the ac line segment and its two terminals. The
ACLineSegment object also provides information about the nominal voltage of the segment, the name
of the segment and a reference of the container of the ac line segment, typically, an object of the class
Line. Each terminal object is connected to a different node represented by the field ConnectivityNode.
In this case, the link from the ACLineSegment to the two terminals is redundant with the link from the
terminals to the segment. One of the links could be eliminated. CIM does not limited the use of
redundant data if they are coherent.
<cim:ACLineSegment rdf:ID="_7814201">
<cim:ACLineSegment.bch>2.914E-4</cim:ACLineSegment.bch>
<cim:ACLineSegment.gch>0.0</cim:ACLineSegment.gch>
<cim:Conductor.length>0.0</cim:Conductor.length>
<cim:ConductingEquipment.Terminals rdf:resource="#_7814303"/>
<cim:ConductingEquipment.Terminals rdf:resource="#_7814304"/>
<cim:ConductingEquipment.BaseVoltage rdf:resource="#_400000302"/>
<cim:Equipment.MemberOf_EquipmentContainer rdf:resource="#_343959201"/>
<cim:IdentifiedObject.description>AMHE400MARCLINE</cim:IdentifiedObject.description>
<cim:IdentifiedObject.name>SEG1</cim:IdentifiedObject.name>
<cim:Terminal rdf:ID="_7814303">
<cim:Terminal.ConductingEquipment rdf:resource="#_7814201"/>
<cim:Terminal.ConnectivityNode rdf:resource="#_7826201"/>
<cim:IdentifiedObject.name>T1</cim:IdentifiedObject.name>
</cim:Terminal>
<cim:Terminal rdf:ID="_7814304">
<cim:Terminal.ConductingEquipment rdf:resource="#_7814201"/>
<cim:Terminal.ConnectivityNode rdf:resource="#_208201"/>
</cim:Terminal>
FIGURE 11 EXAMPLE OF CIM RDF XML DESCRIBING A SEGMENT OF AN AC LINE
Section 5.1.2 and Annex II provides a full description of a distribution network using CIM RDF XML.
4.3.1.2 ANALOGVALUE
The example of Figure 12 describes a measurement represented by the object AnalogValue and the
description of the associated measurement point represented by the object Analog. The yellow colour
signals the link between the analogue value and the measurement point of the analogue value. The
object Analog provides two kinds of data: the information related to the type of the measurement, as
the normal value, and the information related to the physical measurement point through the field
Terminal.
34 | 130
PROJECT
<cim:AnalogValue rdf:about=“#__2220358">
<cim:MeasurementValue.value>0.0</cim:MeasurementValue.value>
<cim:MeasurementValue.MemberOf_Measurement rdf:resource="#_2220201"/>
<cim:MeasurementValue.MeasurementValueSource rdf:resource="#_504301"/>
<cim:IdentifiedObject.description>TROYTRAFO1SL_APP_P_SE</cim:IdentifiedObject.description>
<cim:IdentifiedObject.name>APP_PW_L_SE</cim:IdentifiedObject.name>
</cim:AnalogValue>
<cim:Analog rdf:about=“#__2220201">
<cim:Measurement.positiveFlowIn>true</cim:Measurement.positiveFlowIn>
<cim:Measurement.normalValue>600.0</cim:Measurement.normalValue>
<cim:Measurement.MeasurementType rdf:resource="#_402301"/>
<cim:Measurement.Terminal rdf:resource="#_2137304"/>
<cim:Measurement.MemberOf_PSR rdf:resource="#_2137201"/>
<cim:Measurement.Unit rdf:resource="#_3301"/>
<cim:IdentifiedObject.description>TROYTRAFO1SL_APP_P</cim:IdentifiedObject.description>
<cim:IdentifiedObject.name>APP_PW_L</cim:IdentifiedObject.name>
</cim:Analog>
FIGURE 12 EXAMPLE OF CIM RDF XML DESCRIBING AN ANALOG VALUE
4.3.1.3 DISCRETEVALUE
The example of Figure 13 is similar to the previous example, changing the analogue value for a discrete
value. An example of discrete value is the current position of the switch. The yellow colour signals the
link between the discrete value and the measurement point of the discrete value.
<cim:DiscreteValue rdf:about=“#__146359">
<cim:MeasurementValue.value>2</cim:MeasurementValue.value>
<cim:MeasurementValue.MemberOf_Measurement rdf:resource="#_146334"/>
<cim:MeasurementValue.MeasurementValueSource rdf:resource="#_501301"/>
<cim:IdentifiedObject.description>AMHE400BC4SW_D_D_S</cim:IdentifiedObject.description>
<cim:IdentifiedObject.name>SWITCH_D_D_S</cim:IdentifiedObject.name>
</cim:DiscreteValue>
<cim:Discrete rdf:about=“#__146334">
<cim:Measurement.MeasurementType rdf:resource="#_408301"/>
<cim:Measurement.MemberOf_PSR rdf:resource="#_146201"/>
<cim:Measurement.Unit rdf:resource="#_11301"/>
<cim:IdentifiedObject.description>AMHE400BC4SW_D_D</cim:IdentifiedObject.description>
<cim:IdentifiedObject.name>SWITCH_D_D</cim:IdentifiedObject.name>
</cim:Discrete>
<cim:MeasurementType rdf:about=“#__408301">
<cim:IdentifiedObject.name>SwitchPosition</cim:IdentifiedObject.name>
</cim:MeasurementType>
FIGURE 13 EXAMPLE OF CIM RDF XML DESCRIBING A DISCRETE VALUE
4.3.1.4 STATE VARIABLES
This case of Figure 14 illustrates the definition of the input and the output of a power flow analysis.
35 | 130
PROJECT
<cim:SvVoltage rdf:about=“#_xasvVoltage164">
<cim:SvVoltage.angle>14.248034</cim:SvVoltage.angle>
<cim:SvVoltage.v>13.8</cim:SvVoltage.v>
<cim:SvVoltage.TopologicalNode rdf:resource="#xaDBus164"/>
</cim:SvVoltage>
<cim:SvPowerFlow rdf:about=“#_xasvPowerFlowGenr141">
<cim:SvPowerFlow.p>-42.0</cim:SvPowerFlow.p>
<cim:SvPowerFlow.q>14.143607</cim:SvPowerFlow.q>
<cim:SvPowerFlow.Terminal rdf:resource="#xaGenTerminal141"/>
</cim:SvPowerFlow>
<cim:SvInjection rdf:about=“#__c1d5c03d8f8011e08e4d00247eb1f55e_X13nl">
<cim:SvInjection.pNetInjection>153.6141</cim:SvInjection.pNetInjection>
<cim:SvInjection.qNetInjection>149.2567</cim:SvInjection.qNetInjection>
<cim:SvInjection.TopologicalNode rdf:resource="#_9d25a1f9e5d14d47b6dcde99c4380b40" />
</cim:SvInjection>
FIGURE 14 EXAMPLE OF CIM RDF XML DESCRIBING OBJECTS OF A POWER FLOW ANALYSIS
4.3.2 CIM XML
Following sections show examples of the CIM XML format.

4.3.2.1 METERREADING
The example comes from the Polish demo. It represents a set of readings associated with the meters
installed in the physical points whose identifiers are “PL0012312312312312:*” and
“PL0023423423423412:*”. The ReadingType “0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0” indicates instantaneous
power measurement.
<?xml version="1.0" encoding="UTF-8"?>

<ns2:MeterReadings xmlns:ns2="http://iec.ch/TC57/2011/MeterReadings#"
xsi:schemaLocation="http://iec.ch/TC57/2011/MeterReadings# xsd/MeterReadings.xsd">
<ns2:MeterReading>
<ns2:Readings>
<ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp>
<ns2:value>4.12</ns2:value>
<ns2:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.38.0"/>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
<ns2:value>8</ns2:value>
</ns2:Readings>
<ns2:UsagePoint>
36 | 130
PROJECT
<ns2:mRID>PL0012312312312312:*</ns2:mRID>
</ns2:UsagePoint>
</ns2:MeterReading>
<ns2:MeterReading>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:UsagePoint>
<ns2:mRID>PL0023423423423412:*</ns2:mRID>
</ns2:UsagePoint>
</ns2:MeterReading>
</ns2:MeterReadings>
4.3.2.2 METERCONFIG
The example is from IEC 61968-9 standard. It describes the asset parameters of a meter as model
number, manufacturer or name.

<m:MeterConfig xsi:schemaLocation="http://iec.ch/TC57/2011/MeterConfig# MeterConfig.xsd"
xmlns:m="http://iec.ch/TC57/2011/MeterConfig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<m:Meter>
<m:amrSystem>CCTR</m:amrSystem>
<m:serialNumber>82000001</m:serialNumber>
<m:ConfigurationEvents>
<m:createdDateTime>2011-11-09T13:55:02.776Z</m:createdDateTime>
<m:effectiveDateTime>2011-11-09T00:00:00.000Z</m:effectiveDateTime>
<m:reason>AssetCreation</m:reason>
</m:ConfigurationEvents>
<m:EndDeviceInfo>
<m:AssetModel>
<m:modelNumber>F60</m:modelNumber>
<m:Manufacturer>
<m:Names>
<m:name>LG</m:name>
</m:Names>
</m:Manufacturer>
</m:AssetModel>
</m:EndDeviceInfo>
37 | 130
PROJECT
<m:Names>
<m:name>1234LG</m:name>
<m:NameType>
<m:name>PrimaryName</m:name>
</m:NameType>
</m:Names>
</m:Meter>
</m:MeterConfig>
4.3.2.3 USAGEPOINTCONFIG
The example is from IEC 61968-9 standard. It is similar to MeterConfig but describing the point, the
UsagePoint, where the meter has been installed.

<m:UsagePointConfig xsi:schemaLocation="http://iec.ch/TC57/2011/UsagePointConfig#
UsagePointConfig.xsd" xmlns:m="http://iec.ch/TC57/2011/UsagePointConfig#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<m:UsagePoint>
<m:isSdp>true</m:isSdp>
<m:ConfigurationEvents>
<m:createdDateTime>2011-11-09T10:58:03.616Z</m:createdDateTime>
<m:effectiveDateTime>2011-11-09T00:00:00.000Z</m:effectiveDateTime>
</m:ConfigurationEvents>
<m:Names>
<m:name>SDP1234E001001</m:name>
<m:NameType>
</m:NameType>
</m:Names>
<m:UsagePointLocation>
<m:Names>
<m:name>LOC1234</m:name>
<m:NameType>
</m:NameType>
</m:Names>
</m:UsagePointLocation>
</m:UsagePoint>
</m:UsagePointConfig>
4.4 PROFILE DEVELOPMENT

The following section describes a profile developed by Comillas for the WP2 component “Load and
generation forecasting at secondary substation” using the CIM XML format. The profile includes the
detailed definition of inputs and outputs of the component.
In section 5.1.2, a profile using the CIM RDF XML format will be presented. The profile also has been
developed by Comillas.
38 | 130
PROJECT
4.4.1 Load and generation forecasting at secondary substation
The original input and output format defined in [2] has been translated to the CIM XML format using the
MeterReadings schema defined by IEC 61968-9. It uses two types of inputs and two type of outputs:
 Energy input file: see Table 8. DT means distribution transformer.
 Temperature input file: see Table 9.
 Energy output file: see Table 10 .
 Energy error output file: Table 11.
TABLE 8. STRUCTURE EXAMPLE OF THE ENERGY INPUT DATA FILE (SOURCE: [2])
Date
Date Date (day Energy Energy Energy
DT name (Month …
(year) 1-31) value (h1) value (h2) value (hx)
1-12)
DT 1 Year 1 Month 1 Day 1 Value 1 Value 1 … Value 1
DT 1 … … … … … … …
DT 1 Year x Month y Day z Value n Value n … Value n
… … … … … … … …
DT M Year x Month y Day z Value m Value m … Value m
TABLE 9. STRUCTURE EXAMPLE OF THE TEMPERATURE INPUT DATA FILE (SOURCE: [2])
Date
Date Date (day Temperature Temperature Temperature
(Month …
(year) 1-31) value (h1) value (h2) value (hx)
1-12)
Year 1 Month 1 Day 1 Value 1 Value 1 … Value 1
Year 1 Month 1 Day 2 Value 2 Value 2 … Value 2
… … … … … … …
Year x Month y Day z Value n Value n … Value n
39 | 130
PROJECT
TABLE 10. STRUCTURE EXAMPLE OF THE ENERGYFORECAST.OUT DATA FILE (SOURCE: [2])
Date Date Energy value Energy value Energy value
DT name Date (day) …
(year) (Month) (h1) (h2) (hx)
DT 1 y m Day d Empty forecast (d,h2) … forecast (d,hx)
forecast forecast
DT 1 y m Day d+1 forecast (d+1,h2) …
(d+1,h1) (d+1,hx)
forecast
DT 1 y m Day d+2 Empty … Empty
(d+2,h1)
DT 2 y m Day d Empty forecast2 (d,h2) … forecast2 (d,hx)
… … … … … … … …
forecastM
DT M y m Day d+2 Empty … Empty
(d+2,h1)
TABLE 11. STRUCTURE EXAMPLE OF THE ENERGYERROR.OUT INPUT DATA FILE (SOURCE: [2])
Date Date Error value
DT name Date (day) Error value (h2) … Error value (hx)
(year) (Month) (h1)
DT 1 y m Day d Empty forecast (d,h2) … forecast (d,hx)
forecast forecast
DT 1 y m Day d+1 forecast (d+1,h2) …
(d+1,h1) (d+1,hx)
forecast
DT 1 y m Day d+2 Empty … Empty
(d+2,h1)
DT 2 y m Day d Empty forecast2 (d,h2) … forecast2 (d,hx)
… … … … … … … …
forecastM
DT M y m Day d+2 Empty … Empty
(d+2,h1)
40 | 130
PROJECT
Figure 15 is an example of the energy input file (source [2] ).
FIGURE 15 EXAMPLE OF ENERGY INPUT DATA FILE (SOURCE [2] )
The translation to CIM uses a common format based on the MeterReadings schema defined by IEC
61968-9. Figure 16 Selected fields from the original meterReadings Schema indicates the used fields.
FIGURE 16 SELECTED FIELDS FROM THE ORIGINAL METERREADINGS SCHEMA
Table 12 describes the used fields from the original MeterReadings.
41 | 130
PROJECT
TABLE 12 DESCRIPTION OF THE SELECTED FIELDS FROM THE ORIGINAL METERREADINGS SCHEMA (IEC 61968-9)
MeterReading Set of readings obtained from a meter or equivalent.
MeterReading.Readings A reading is a specific value measured by a meter or other asset, or

calculated by a system. Each reading is associated with a specific
ReadingType.
MeterReading.timeStamp The time when the value was last updated.
MeterReading.ReadingType ID of the type of the reading value, according with IEC 61968-9. The
possible values are:
 “0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0” for forward energy.
 “0.0.0.4.19.1.12.0.0.0.0.0.0.0.0.3.72.0” for reverse energy.
 “0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0” for temperature.
The value is a concatenation of 18 fields. TABLE 13 explains the
meaning of the fields from left to right.
MeterReading.UsagePoint.mRID UsagePoint is a logical or physical point in the network to which

readings may be attributed. Used at the place where a physical or
virtual meter may be located; however, it is not required that a
meter must be present.
mRID is the ID of the UsagePoint.
UsagePoint is not used in the case of temperature.
42 | 130
PROJECT
TABLE 13 DESCRIPTION OF THE USED VALUES IN READING TYPE
Forward energy Reverse energy Temperature

Field
Field name Value Value description Value Value description Value Value description
Number
1 macroPeriod 0 not applicable 0 not applicable 0 not applicable
2 Aggregate 0 not applicable 0 not applicable 0 not applicable
3 measuringPeriod 0 not applicable 0 not applicable 0 not applicable
4 Accumulation 4 Delta value 4 Delta value 0 not applicable
Energy is
Energy supplied by produced and
5 flowDirection 1 19 0 not applicable
the utility backfed onto the
utility network.
All types of
All types of
electricity
6 Commodity 1 electricity metered 1 0 not applicable
metered
quantities
quantities
7 measurementKind 12 Energy 12 Energy 46 Temperature
8 interharmonicNumerator 0 not applicable 0 not applicable 0 not applicable
9 interharmonicDenominator 0 not applicable 0 not applicable 0 not applicable
10 argumentNumerator 0 not applicable 0 not applicable 0 not applicable
11 argumentDenominator 0 not applicable 0 not applicable 0 not applicable
12 Tou 0 not applicable 0 not applicable 0 not applicable
13 Cpp 0 not applicable 0 not applicable 0 not applicable
14 consumptionTier 0 not applicable 0 not applicable 0 not applicable
15 Phases 0 not applicable 0 not applicable 0 not applicable
16 Multiplier 3 k 3 k 0 1
17 Unit 72 Watt 72 Watt 23 Degrees Celsius
18 Currency 0 None 0 None 0 None
The following XML document is an example of energy file that works as energy input, energy output or
energy error output:
<MeterReadings xmlns="http://iec.ch/TC57/2011/MeterReadings#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iec.ch/TC57/2011/MeterReadings# S213MeterReadings.xsd">
<MeterReading>
<Readings>
<timeStamp>2001-12-17T09:00:00Z</timeStamp>
<value>Value 11</value>
<ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<Readings>
43 | 130
PROJECT
<ReadingType ref="0.0.0.4.19.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<Readings>
<ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<UsagePoint>
<mRID>DT 1</mRID>
</UsagePoint>
</MeterReading>
<MeterReading>
<Readings>
<ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<Readings>
<ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<Readings>
<ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/>
</Readings>
<UsagePoint>
<mRID>DT 2</mRID>
</UsagePoint>
</MeterReading>
</MeterReadings>
The following XML document is an example of input temperature file:

<MeterReadings xmlns="http://iec.ch/TC57/2011/MeterReadings#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iec.ch/TC57/2011/MeterReadings# S213MeterReadings.xsd">
<MeterReading>
<Readings>
<ReadingType ref="0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/>
</Readings>
<Readings>
<ReadingType ref="0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/>
</Readings>
<Readings>
<ReadingType ref="0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/>
</Readings>
44 | 130
PROJECT
</MeterReading>
</MeterReadings>
The main advantages of using the designed CIM XML format versus the original format (Table 8 to Table
11 and Figure 15 as an example) are:
 Same data format.
 Automatic validation before using.
 An easy way for adding new fields, because each field is self-contained.
The main disadvantage is the size of the document because XML format is verbose. This issue is easily
solved using a standard compression format as the gzip. In large files, the size after compression of the
original files using simple tables and the CIM XML files is very similar.
4.5 STUDY ON THE USE OF THE CIM MODEL FOR BUILDING THE CORE OF
AN APPLICATION
In UPGRID, TECNALIA started with the development of a Java partial implementation of IEC 61970-
301:2013-12 standard leaving the packages for generation dynamics and generation production
uncompleted with several classes on the pending list as they were far from being relevant for UPGRID
purposes.
The IEC 61970-301:2013-12 is published as a PDF file but it is possible to gain, through public access
mechanisms, to the Enterprise Architect2 model files supporting the CIM model. As many other UML
tools, Enterprise Architect allows to generate source code in several object oriented programming
languages in order to use the model in a real application. The main problem with this code is that being
automatically generated, many of the coding standards and good programming practices could be left
out. In any case, the Enterprise Architect source code generation process failed to produce code for only
a few classes and gave little indication of the found error.
Therefore, it was decided to perform a manual implementation of the Java code taking into account that
it was a repetitive, work demanding but easy task as the CIM model consist almost only of classes, their
attributes, associations and inherited elements. At the same time, it requires some design decisions, is
intensive on data model characteristics and results on detection of applicability problems.
One of the first problems is that there are too many other IEC standards in the same family in advanced
draft form so, sometimes, it will be worth waiting until they are finished and released before continuing
with a model that could be obsolete in a relatively short period of time. The large number of editions of
the CIM (currently Ed6.0 is in “final draft international standard” form released 23/Sep/2016) and the
2
The CIM release of IEC 61970-301:2013-12 was constructed using Sparx Systems Enterprise Architect product. Enterprise Architect is the (trade name or
trade mark) of a product supplied by Sparx System (source [3] ).
45 | 130
PROJECT
remaining parts demonstrate that CIM is an evolving standard so it is extremely difficult to keep a
compliant application the continuous updates require permanent efforts on the developer side.
Once decided to implement the CIM model from scratch using Java programming language, there is a
key decision about the use of native data types (i.e. java.lang.Integer, java.util.Date, java.lang.String,
etc.) to model CIM types (domain package Integer, Date or String primitives) or avoid the native versions
overwriting it. In the reference implementation of the model, it was decided to opt for the first
approach, gaining access to library methods. In the same way, associations holding pointers to other
objects (references in Java properly speaking) are instrumented with ArrayList class. Class inheritance is
directly supported as well as enumerations are.
The CIM data model complexity in terms of code is negligible, private attributes with getter and setter
methods allowing gaining access to the attribute value. Therefore, it is of utmost importance to clearly
document the CIM data model API paving the engineering use of the model by providing as much
information as needed. As said before, the IEC 61970-301:2013-12 is published as a protected PDF file
and a simple copy&paste text operation is forbidden. Obviously, there are plenty of methods to
overcome this prohibition and original text can be incorporated into the source code. Figure 17 is a
snapshot of the developed java classes, and Figure 18 shows an example of JAVA API for using the CIM
class ActivePower.
FIGURE 17 SNAPSHOT OF THE JAVA SOURCE TREE FOR THE CIM IMPLEMENTATION
46 | 130
PROJECT
FIGURE 18 SNAPSHOT OF THE JAVA API FOR THE CIM IMPLEMENTATION
There are many lessons learned from the implementation of the CIM from scratch, mainly because of
the detailed review required for the Java implementation given the paper printed standard.
- The model has grown to include more and more aspects of the transmission network operation
adding complexity but unknown added value. The models for generation dynamics are a clear
example because classes are added to support governor, voltage regulator or generator models…
when simulation tools formats could have been used instead.
- There are plenty of typos in the PDF version of the standard. The decision to made the CIM model a
UML based model makes sense for modelling purposes and adds some coherence but then reviewing
class descriptions, attributes explanations and supporting text becomes highly demanding having to
navigate, one by one, every small misspelled word.
47 | 130
PROJECT
- The model is designed in such a way that when one relation exists between one class and other the
reverse relation is automatically created. Some of them may not make any sense even if the CIM
profile would define later what classes and relations are used.
- The naming of attributes and classes should be reviewed. In many cases, a relation from one to many
receives a singular name while in other cases it is a plural name. One may think that “getTerminal()”
method would return a single instance but it returns a collection of names. There are tens of classes
affected (roughly 10% of the classes) and UML cardinality is lost when the model is implemented
using many programming languages.
At the level of Java implementation, most of the CIM packages hold a ‘README.txt’ file containing
comments regarding classes, attributes, etc. For instance, the ’wires’ package readme file:
- The class EnergyConsumer has an attribute called 'grounded' of type 'WindingConnection' with some
sort of error. The name and the description suggest type Boolean so the type should be wrong.
- The types of synchronous generators seem to be taken from PSS/E dynamic model names rather than
from a serious taxonomy.
- One of the names in the enumeration is 'transient' that may interfere with the java keyword
'transient'.
- The types of operating modes of synchronous machines could be expanded into 'motor' with little
effort but only generator and condenser are defined. Definitions of the meaning are empty asking for
some effort form the WG team.
- The names of PhaseTapChangerAsymetrical and PhaseTapChangerSymetrical are misspelled.
Based on the experience of trying to use the CIM model directly from the standards documents, there is
still a long way to go before the CIM model becomes an effective standard, if the standard for data
exchange changes continuously there is not such a unique data model. Even worse, the errors,
inconsistencies and typos do not help to consider CIM seriously. In any case, it is always good to have
some common reference, common concepts and CIM clearly satisfies this basic purpose. The question is
whether the common model should only focus on the main components for the sake of simplicity but
leaving many specific uses for private arrangements among parties or try to model everything adding
complexity and error prone parts.
The IEC working groups are aware of this problem and are working on the realization of guidelines and
standards that deal with the issue of different profiles. The IEC also committed itself in its last plenary
sessions to releasing the codes (XSD schemas, XML RDF schemas) that support the documents to
facilitate the work of the developers. Nevertheless, the use of CIM increases day by day. For instance,
the ENTSO-E (European Network of Transmission System Operators), that represents 42 electricity
transmission system operators (TSOs) from 35 countries across Europe, has adopted CIM for grid models
exchange and for energy markets. In the USA, other TSOs as CAISO have adopted CIM. In the other
hand, many solutions providers have adopted CIM as GE, Siemens, ABB, SYSCO, etc.
48 | 130
PROJECT
5. CIM AT THE DEMOS

Table 14 shows the use of the CIM formats at the demos in Spain, Poland and Sweden, and compares to
the formats in the WP2 components. WP2 components don’t use the difference CIM RDF XML format
because components do not need to partially update the received network model. Also, the table shows
if the demo has extended the CIM model or the associated CIM XML schemas. Portuguese demo does
not deploy CIM features.
Spanish Portuguese Swedish demo Polish demo WP2

demo demo components
CIM RDF XML (full model) Yes Yes Yes
CIM RDF XML (difference Yes Yes

model)
CIM XML Yes Yes
CIM Model extensions Yes
CIM XML schema Yes

extensions
TABLE 14 DEMO CIM FORMATS
5.1 SPANISH DEMO

The Spanish demo has two applications of the CIM model:
 Interface between existing databases and the LVNMS (Low Voltage Network Management
System).
 Distribution network model without tool limitations.
Following sections describe these applications.
5.1.1 INTERFACE BETWEEN EXISTING DATABASES AND THE LVNMS
The CIM RDF XML format is used for feeding the LVNMS installed in the Spanish demo with distribution
network data from the existing databases of Iberdrola. The LVNMS is based on the PowerOn technology
of GE and admits the CIM RDF XML format, both full and difference, as input. A tool named Smallworld
Electric Office, also from GE, gets the data from the Iberdrola databases and generates CIM data using a
subset of the CIM model version v15 with some additional model extensions developed by GE and
Comillas to fulfil the data requirements of the LVNMS. In addition, the LVNMS receives a graphic
representation of the network using the GML format (Geography Markup Language), provided by the
Electric Office from existing databases; but it is out of the CIM scope.
49 | 130
PROJECT
The data requirements of the SCADA use numerous asset and control parameters that were not initially
supported by the CIM version of the Smallworld Electric Office. Fortunately, the GE SCADA and the
Smallworld Electric Office support the extension of the CIM model using the generalization of existing
classes. So, the decision was to extend the CIM model with new classes that extend existing classes and
to concentrate in the attributes of these new classes the requirements of control and asset data
demanded by the SCADA. If it was possible, the name of the attributes was the same that the full CIM
model uses in other classes. Table 15 shows the main classes added to the CIM model, the standard
parent class and the new attributes that the new class adds to the parent class. The name of the new
classes uses the prefix IBD. A detailed analysis of the new attributes indicates that most of them are
related to asset data. For example, the attribute ProvinceCode or town will be not necessary if the
ServiceLocation class is supported. In any case, if Small Word Office supported the full CIM model v15,
most of these extensions would not have been necessary.
TABLE 15 NEW CLASSES FOR SUPPORTING THE INTERFACE BETWEEN EXISTING SYSTEM AND THE NEW SCADA SYSTEM
New class name Inherited from (standard New attributes

CIM class)
IBDSecondarySubstation Substation provinceCode
town
direction
postalCode
functionKind
physicalLocationKind
electricalConfigurationKind
status
manufacturer
maintenanceResponsible
accessMethod
property
dataBaseID
IBDDistributionTransfomer PowerTransformer position
positionKind
positionStatus
mvConnectionKind
mvConnectionSection
mvConnectionMaterial
manufacturer
ratedS
outputKind
physicalPlacementKind
refrigerantKind
connectionKind
regulationRange
50 | 130
PROJECT
tapStep
embeddedFuse
IBDFuseLV Fuse IBDSecondarySubstationID
position
cabinet
fuseKind
fuseDescription
manufacturer
manufacturerModel
nominalCurrent
IBDLowVoltageLine Line nominalVoltage
position
cabinet
cableKind
phaseWireCount
layingKind
section
headMaterial
IBDACLineSegment ACLineSegment IBDSecondarySubstationID

IBDSecondarySubstationName
nameIBD
segmentNumber
cableKind
Conductor.length
property
manufacturer
maximumCurrent
layingKind
neutral
phases
nominalVoltage
IBDEnergyConsumer EnergyConsumer provinceCode
town
street
streetNumber
bisData
bisKind
nameIBD
IBDSecondarySubstationID
IBDACLineSegmentID
customerCount
contractedPower
51 | 130
PROJECT
threePhaseCustomerCount
specialNeedCustomerCount
generationCustomerCount
less15kwCustomerCount
less15kwContractedPower
between15kwAnd50kwCustomerCount
between15kwAnd50kwContractedPower
greater50kWCustomerCount
greater50kWContratedPower
generationContractCount
generatedPower
generationKind
secundarySubstationDistance
maximumCurrent
connectionKind
direction
accessMethodKind
accessMethod
supplyKind
internalExternal
phaseCode
neutralConductor
fuseRatedCurrent
status
insulationKind
fuseKind
fuseClass
fuseSize
incomingCableKind
incomingCableLength
outcomingCableKind
mainConsumptionKind
amiBillingReadyKind
Figure 19 shows all the used CIM classes in the development of the interface. The blue colour indicates
the new classes added to the standard CIM model.
52 | 130
PROJECT
cl a ss I B DGE
+Assets
P SRTy pe A sset
GEP SRRol e 0..*
+PSRType 0..1 +Assets 0..*
+PowerSystemResources 0..* +PowerSystemResources
P ow er Sy st emResour ce 0..* +AssetInfo 0..1
A sset I nf o
+ConnectivityNodeContainer 1 +EquipmentContainer +Equipments Equi pment W i r eI nf o
0..1 0..*
Equi pment C ont a i ner
Li ne
C a bl eI nf o
+ConnectivityNodes 0..*
Subst a t i on
C onnect i v i t y Node
I B DLow V ol t a geLi ne C onduct or
+Substation 1
+ConnectivityNode 0..1
I B DSeconda r y Subst a t i on
+VoltageLevels 0..* A C Li neSegment
V ol t a geLev el C onduct i ngEqui pment +ACLineSegment 1
+VoltageLevel 0..1 +ConductingEquipment 1

+Bays 0..* I B DA C Li neSegment
Bay
+ACLineSegmentPhases 0..*
Ener gy C onnect i on
A C Li neSegment P ha se
C onnect or
Ener gy C onsumer
+Terminals
+Terminals
0..* 0..*
Ter mi na l Tr a nsf or mer Ta nk End

I B DEner gy C onsumer
+Terminal 0..1
B usba r Sect i on
+Switch
Sw i t ch
+TransformerEnd 0..* 1+SwitchPhase
0..* Sw i t chP ha se
Tr a nsf or mer End
Fuse
I B DFuseLV
FIGURE 19 USED CIM CLASSES IN THE INTERFACE BETWEEN EXISTING SYSTEM AND THE LVNMS
53 | 130
PROJECT
Figure 20 to Figure 25 show RDF XML examples of the new classes. Notice that some attributes of Table
15 do not appear in the examples. The reason is all attributes of Table 15 are optional. If the element
does not need the attribute, or it does not appear or appear empty.
<cim:IBDSecondarySubstation rdf:ID="ctm_394379549">
<cim:IBDSecondarySubstation.provinceCode>48</cim:IBDSecondarySubstation.provinceCode>
<cim:IdentifiedObject.name>MARTINI ROSSI</cim:IdentifiedObject.name>
<cim:IBDSecondarySubstation.physicalLocationKind>EDIFICIO
LONJA</cim:IBDSecondarySubstation.physicalLocationKind>
<cim:IBDSecondarySubstation.postalCode>48008</cim:IBDSecondarySubstation.postalCode>
<cim:IBDSecondarySubstation.maintenanceResponsible>BRIGADA
BILBAO</cim:IBDSecondarySubstation.maintenanceResponsible>
<cim:IdentifiedObject.aliasName>200000261</cim:IdentifiedObject.aliasName>
<cim:IBDSecondarySubstation.town>BILBAO</cim:IBDSecondarySubstation.town>
<cim:IBDSecondarySubstation.accessMethod>DEBAJO RAMPA GARAJE( CAJETIN CON LLAVE PARA
ACCESO )</cim:IBDSecondarySubstation.accessMethod>
<cim:IBDSecondarySubstation.electricalConfigurationKind>CONVENCIONAL</cim:IBDSecondarySubstation.el
ectricalConfigurationKind>
<cim:IBDSecondarySubstation.functionKind>CTD: CENTRO DE TRANSFORMACION DE
DISTRIBUCION</cim:IBDSecondarySubstation.functionKind>
<cim:IBDSecondarySubstation.property>IBERDROLA (PROPIEDAD DE LA
EMPRESA)</cim:IBDSecondarySubstation.property>
<cim:IdentifiedObject.mRID>200000261</cim:IdentifiedObject.mRID>
<cim:IBDSecondarySubstation.status>En servicio</cim:IBDSecondarySubstation.status>
<cim:IBDSecondarySubstation.direction>ALDA.URQUIJO 28 E.C.
BILBAO</cim:IBDSecondarySubstation.direction>
<cim:IBDSecondarySubstation.dataBaseID>1944</cim:IBDSecondarySubstation.dataBaseID>
<cim:PowerSystemResource.PSRType rdf:resource="#PSRType_CTD_INTERIOR"/>
</cim:IBDSecondarySubstation>
FIGURE 20 RDF XML EXAMPLE OF IBDSECONDARYSUBSTATION
<cim:IBDDistributionTransformer rdf:ID="eo_power_xfrmr_inst_73666007">
<cim:IBDDistributionTransformer.outputKind>B2(A)</cim:IBDDistributionTransformer.outputKind>
<cim:IBDDistributionTransformer.physicalPlacementKind>INTERIOR (CABINA, LONJA,
CASETA)</cim:IBDDistributionTransformer.physicalPlacementKind>
<cim:IBDDistributionTransformer.connectionKind>Dyn11</cim:IBDDistributionTransformer.connectionKind>
<cim:IdentifiedObject.aliasName>200000261_2</cim:IdentifiedObject.aliasName>
<cim:IBDDistributionTransformer.refrigerantKind>ACEITE DE
SILICONA</cim:IBDDistributionTransformer.refrigerantKind>
<cim:IBDDistributionTransformer.manufacturer>INCOESA</cim:IBDDistributionTransformer.manufacturer>
<cim:IBDDistributionTransformer.position>2</cim:IBDDistributionTransformer.position>
<cim:IdentifiedObject.name>MARTINI ROSSI 200000261 T2</cim:IdentifiedObject.name>
<cim:IBDDistributionTransformer.ratedS>630.0</cim:IBDDistributionTransformer.ratedS>
<cim:IBDDistributionTransformer.positionStatus>En
servicio</cim:IBDDistributionTransformer.positionStatus>
<cim:PowerSystemResource.PSRRoles rdf:resource="#PSRRole_Lateral"/>
<cim:Equipment.EquipmentContainer rdf:resource="#ctm_394379549"/>
</cim:IBDDistributionTransformer>
FIGURE 21 RDF XML EXAMPLE OF IBDDISTRIBUTIONTRANSFORMER
54 | 130
PROJECT
<cim:IBDFuseLV rdf:ID="eo_isolating_eqpt_inst_76784477">
<cim:IBDFuseLV.IBDLowVoltageLineNameIBD>60245</cim:IBDFuseLV.IBDLowVoltageLineNameIBD>
<cim:IBDFuseLV.IBDSecondarySubstationID>200000261</cim:IBDFuseLV.IBDSecondarySubstationID>
<cim:IdentifiedObject.name>MARTINI ROSSI T2 L9</cim:IdentifiedObject.name>
<cim:IBDFuseLV.cabinet>21</cim:IBDFuseLV.cabinet>
<cim:IBDFuseLV.userReferenceID>200000261_2_21_L60245</cim:IBDFuseLV.userReferenceID>
<cim:Switch.normalOpen>false</cim:Switch.normalOpen>
<cim:PowerSystemResource.PSRRoles rdf:resource="#PSRRole_Service"/>
<cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Unknown"/>
<cim:ConductingEquipment.BaseVoltage rdf:resource="#BaseVoltage_0.380"/>
<cim:Equipment.EquipmentContainer rdf:resource="#ctm_394379549_60245"/>
</cim:IBDFuseLV>
FIGURE 22 RDF XML EXAMPLE OF IBDFUSELV
<cim:IBDLowVoltageLine rdf:ID="eo_circuit_76784647">
<cim:IBDLowVoltageLine.nominalVoltage>220/380 V</cim:IBDLowVoltageLine.nominalVoltage>
<cim:IdentifiedObject.aliasName>MARTINI ROSSI-2</cim:IdentifiedObject.aliasName>
<cim:IdentifiedObject.name>MARTINI ROSSI-2</cim:IdentifiedObject.name>
</cim:IBDLowVoltageLine>
FIGURE 23 RDF XML EXAMPLE OF IBDLOWVOLTAGELINE
<cim:IBDACLineSegment rdf:ID="eo_cable_segment_inst_74288439-NL.407781193-NH.407781204">
<cim:IdentifiedObject.name>200000261_9_8</cim:IdentifiedObject.name>
<cim:IBDACLineSegment.nominalVoltage>220/380 V</cim:IBDACLineSegment.nominalVoltage>
<cim:IBDACLineSegment.nameIBD>9</cim:IBDACLineSegment.nameIBD>
<cim:IBDACLineSegment.physicalPlacementKind>A</cim:IBDACLineSegment.physicalPlacementKind>
<cim:IBDACLineSegment.cableKind>RZ 0,6/1 KV 3X95/54,6 ALM</cim:IBDACLineSegment.cableKind>
<cim:IBDACLineSegment.property>IBERDROLA (PROPIEDAD DE LA
EMPRESA)</cim:IBDACLineSegment.property>
<cim:IBDACLineSegment.IBDSecondarySubstationName>MARTINI
ROSSI</cim:IBDACLineSegment.IBDSecondarySubstationName>
<cim:IBDACLineSegment.segmentNumber>8</cim:IBDACLineSegment.segmentNumber>
<cim:IBDACLineSegment.IBDSecondarySubstationID>200000261</cim:IBDACLineSegment.IBDSecondarySub
stationID>
<cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Overhead"/>
<cim:Equipment.EquipmentContainer rdf:resource="#eo_circuit_75164516"/>
</cim:IBDACLineSegment>
FIGURE 24 RDF XML EXAMPLE OF IBDACLINESEGMENT
55 | 130
PROJECT
<cim:IBDEnergyConsumer rdf:ID="caja_402172151">
<cim:IBDEnergyConsumer.connectionKind>CGP ESQUEMA
8</cim:IBDEnergyConsumer.connectionKind>
<cim:IBDEnergyConsumer.incomingCableKind>RZ 0,6/1 KV 3X50/54,6
ALM</cim:IBDEnergyConsumer.incomingCableKind>
<cim:IBDEnergyConsumer.town>BILBAO</cim:IBDEnergyConsumer.town>
<cim:IBDEnergyConsumer.contractedPower>35.60</cim:IBDEnergyConsumer.contractedPower>
<cim:IBDEnergyConsumer.outcomingCableKind>L. R. 0.6/1 KV 35
CU</cim:IBDEnergyConsumer.outcomingCableKind>
<cim:IBDEnergyConsumer.generationContractCount>0</cim:IBDEnergyConsumer.generationContractCount>
<cim:IBDEnergyConsumer.accessMethodKind>INDIRECTO</cim:IBDEnergyConsumer.accessMethodKind>
<cim:IBDEnergyConsumer.status>En servicio</cim:IBDEnergyConsumer.status>
<cim:IBDEnergyConsumer.supplyKind>B2 3X400/230</cim:IBDEnergyConsumer.supplyKind>
<cim:IBDEnergyConsumer.userReferenceID>3141630_3</cim:IBDEnergyConsumer.userReferenceID>
<cim:IBDEnergyConsumer.fuseClass>GT (FUSION LENTA)</cim:IBDEnergyConsumer.fuseClass>
<cim:IdentifiedObject.name>caja_3141630</cim:IdentifiedObject.name>
<cim:IBDEnergyConsumer.mainConsumptionKind>VI</cim:IBDEnergyConsumer.mainConsumptionKind>
<cim:IBDEnergyConsumer.generatedPower>0</cim:IBDEnergyConsumer.generatedPower>
<cim:IBDEnergyConsumer.fuseKind>PENDIENTE</cim:IBDEnergyConsumer.fuseKind>
<cim:IBDEnergyConsumer.direction>PATIO ACCESORIO CASA</cim:IBDEnergyConsumer.direction>
<cim:IBDEnergyConsumer.physicalPlacementKind>AEREA</cim:IBDEnergyConsumer.physicalPlacementKind
>
<cim:IBDEnergyConsumer.nameIBD>3</cim:IBDEnergyConsumer.nameIBD>
<cim:IBDEnergyConsumer.IBDACLineSegmentID>9</cim:IBDEnergyConsumer.IBDACLineSegmentID>
<cim:IBDEnergyConsumer.maximumCurrent>160 A</cim:IBDEnergyConsumer.maximumCurrent>
<cim:IBDEnergyConsumer.IBDSecondarySubstationID>200000261</cim:IBDEnergyConsumer.IBDSecondaryS
ubstationID>
<cim:IBDEnergyConsumer.customerCount>3</cim:IBDEnergyConsumer.customerCount>
<cim:IBDEnergyConsumer.threePhaseCustomerCount>2</cim:IBDEnergyConsumer.threePhaseCustomerCou
nt>
<cim:IBDEnergyConsumer.fuseSize>0</cim:IBDEnergyConsumer.fuseSize>
<cim:IBDEnergyConsumer.streetNumber>24</cim:IBDEnergyConsumer.streetNumber>
<cim:IBDEnergyConsumer.provinceCode>BIZKAIA</cim:IBDEnergyConsumer.provinceCode>
<cim:IBDEnergyConsumer.accessMethod>POR UNA VIVIENDA</cim:IBDEnergyConsumer.accessMethod>
<cim:IBDEnergyConsumer.secundarySubstationDistance>155.0</cim:IBDEnergyConsumer.secundarySubstati
onDistance>
<cim:IBDEnergyConsumer.insulationKind>AISLANTE</cim:IBDEnergyConsumer.insulationKind>
</cim:IBDEnergyConsumer>
FIGURE 25 RDF XML EXAMPLE OF IBDENERGYCONSUMER
Another characteristic of the used CIM RDF XML format in the Spanish demo is the single phase
approach. For instance, it uses the standard ACLineSegmentPhase and SwitchPhase classes for
describing the circuits phase by phase. Figure 26 shows an RDF XML example: the fuse
eo_isolating_eqpt_inst_76784472 modelled by IBDFuseLV is, in fact, three fuses
(SwitchPhase_76784473_A, SwitchPhase_76784473_B and SwitchPhase_76784473_C). The asset
named eo_isolating_eqpt_76784471 establishes the relationship between the single phase view and the
56 | 130
PROJECT
3-phase view. Another way of setting up the correlation between these two views is the use of objects
of the classes Terminals and ConnectivityNodes.
<cim:Asset rdf:ID="eo_isolating_eqpt_76784471">
<cim:Asset.type>FUSIBLE SECCIONADOR</cim:Asset.type>
<cim:IdentifiedObject.name>Isolating Equipment_76784471</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#SwitchPhase_76784473_A"/>
<cim:Asset.PowerSystemResources rdf:resource="#eo_isolating_eqpt_inst_76784472"/>
<cim:Asset.PowerSystemResources rdf:resource="#SwitchPhase_76784475_C"/>
<cim:Asset.PowerSystemResources rdf:resource="#SwitchPhase_76784474_B"/>
</cim:Asset>
<cim:SwitchPhase rdf:ID="SwitchPhase_76784473_A">
<cim:SwitchPhase.normalOpen>false</cim:SwitchPhase.normalOpen>
<cim:IdentifiedObject.name>76784473_A</cim:IdentifiedObject.name>
<cim:SwitchPhase.phaseSide1 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-
cim15#SinglePhaseKind.A"/>
cim15#SinglePhaseKind.A"/>
<cim:SwitchPhase.Switch rdf:resource="#eo_isolating_eqpt_inst_76784472"/>
</cim:SwitchPhase>
<cim:SwitchPhase rdf:ID="SwitchPhase_76784475_C">
<cim:IdentifiedObject.name>76784475_C</cim:IdentifiedObject.name>
cim15#SinglePhaseKind.C"/>
cim15#SinglePhaseKind.C"/>
</cim:SwitchPhase>
<cim:SwitchPhase rdf:ID="SwitchPhase_76784474_B">
<cim:IdentifiedObject.name>76784474_B</cim:IdentifiedObject.name>
cim15#SinglePhaseKind.B"/>
cim15#SinglePhaseKind.B"/>
</cim:SwitchPhase>
<cim:IBDFuseLV rdf:ID="eo_isolating_eqpt_inst_76784472">
<cim:IBDFuseLV.IBDLowVoltageLineNameIBD>6371</cim:IBDFuseLV.IBDLowVoltageLineNameIBD>
<cim:IBDFuseLV.IBDSecondarySubstationID>200000261</cim:IBDFuseLV.IBDSecondarySubstationID>
<cim:IdentifiedObject.name>MARTINI ROSSI T2 L8</cim:IdentifiedObject.name>
<cim:IBDFuseLV.cabinet>21</cim:IBDFuseLV.cabinet>
<cim:IBDFuseLV.userReferenceID>200000261_2_21_L6371</cim:IBDFuseLV.userReferenceID>
<cim:PowerSystemResource.PSRRoles rdf:resource="#PSRRole_Service"/>
<cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Unknown"/>
<cim:Equipment.EquipmentContainer rdf:resource="#ctm_394379549_6371"/>
</cim:IBDFuseLV>
FIGURE 26 3-PHASE VIEW OF A FUSE
57 | 130
PROJECT
An important issue detected in the use of the CIM model was the extension of enumerative types. For
example, the standard class WireInfo has the attribute “material” and its type is the enumerative type
WireMaterialKind whose values are “copper”, “copper aluminum”, “aluminumSteel”, “acsr”,
“aluminumAlloy”, “aluminumAlloySteel”, “aaac” and “other”. In the case of the Spanish demo, the use
of the value “other” is not enough for describing other types of material. The possible solution is to use
the string format instead of enumerative format and to provide a table with the standard values.
Unfortunately, this solution has the drawback of losing the automatic value checking.
Another important aspect of the application of the CIM in the Spanish demo is the use of the difference
mode for transferring data updates and including new elements. Figure 27 shows an example of this
format. The example indicates: delete values of the attributes of element #eo_cable_77012730
(reverseDifferences part), provide new values for the attributes of element #eo_cable_77012730, and
include a IBDACLineSegment element.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<rdf:RDF xmlns:dm="http://iec.ch/2002/schema/CIM_difference_model#" xmlns:cim="http://iec.ch/TC57/2010/CIM-
schema-cim15#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<dm:DifferenceModel rdf:about="">
<dm:forwardDifferences rdf:parseType="Statements">
<rdf:Description rdf:about="#eo_cable_77012730">
<cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-
NL.407802580-NH.407887210"/>
NL.407802580-NH.407887210_77012731_A"/>
NL.407802580-NH.407887210_77012731_B"/>
NL.407802580-NH.407887210_77012731_C"/>
</rdf:Description>
<cim:IBDACLineSegment rdf:ID="eo_cable_segment_inst_77012698-NL.407802445-NH.407887103">
<cim:IdentifiedObject.name>200000260_9_2</cim:IdentifiedObject.name>
<cim:IBDACLineSegment.nominalVoltage>220/380 V</cim:IBDACLineSegment.nominalVoltage>
<cim:IBDACLineSegment.nameIBD>9</cim:IBDACLineSegment.nameIBD>
<cim:IBDACLineSegment.physicalPlacementKind>S</cim:IBDACLineSegment.physicalPlacementKind>
<cim:IBDACLineSegment.property>IBERDROLA (PROPIEDAD DE LA
EMPRESA)</cim:IBDACLineSegment.property>
<cim:IBDACLineSegment.IBDSecondarySubstationName>CONCHA URKIJO-
ZUBIAG</cim:IBDACLineSegment.IBDSecondarySubstationName>
<cim:IBDACLineSegment.segmentNumber>2</cim:IBDACLineSegment.segmentNumber>
<cim:IBDACLineSegment.IBDSecondarySubstationID>200000260</cim:IBDACLineSegment.IBDSecondarySub
stationID>
<cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Underground"/>
<cim:Equipment.EquipmentContainer rdf:resource="#eo_circuit_76979584"/>
</cim:IBDACLineSegment>
</dm:forwardDifferences>
<dm:reverseDifferences rdf:parseType="Statements">
<rdf:Description rdf:about="#eo_cable_77012730">
58 | 130
PROJECT
NL.407802575-NH.407802590_77012731_A"/>
NL.407802575-NH.407802590_77012731_B"/>
NL.407802575-NH.407802590_77012731_C"/>
NL.407802575-NH.407802590"/>
</rdf:Description>
</dm:reverseDifferences>
</dm:DifferenceModel>
</rdf:RDF>
FIGURE 27 EXAMPLE OF THE DIFFERENCE CIM RDF XML FORMAT
5.1.2 DISTRIBUTION NETWORK MODEL WITHOUT TOOL LIMITATIONS
The objective of this section is to study if the standard CIM model is enough for representing the data
model requirements of section 5.1.1 defined by Iberdrola for the LVNMS of the Spanish demo, in the
case of not limitations in the tool for generating CIM RDF XML files. Section 5.1.1 showed that this
limitation was solved using new classes. This section presents that only few new classes, with few
attributes, are necessary to be added, thanks to the application of the resources of the standard CIM
model.
The data model requirements of the LVNMS covers the electrical view and the asset view of a low
voltage distribution network from the secondary substation to the consumers. The related data with
these requirements are the attributes of the new classes defined in section 5.1.1.
Figure 28 shows the results of the application of the CIM modelling to cover the electrical view of the
data requirements of the LVNMS. The blue boxes represent objects based on classes that inherit from
the CIM class EquipmentContainer class, as substations or voltage levels. The green boxes represent
objects that inherit from the CIM class ConductingEquipment as disconnectors or fuses. The red points
represent the terminals of the ConductingEquipment objects. The terminals are also objects of class
Terminal. The grey circle with segments represents the ConnectivityNode objects that connect terminals
of different conducting equipment.
The secondary substation is represented by the box Substation_CDT1 that is an object of the CIM class
Substation. The substation has 3 voltage levels: VoltageLevel_13200 that represents the level of 13200
V; VoltageLevel_400_1 associated to the low voltage output of transformer 1 (TR1); and
VoltageLevel_400_2 associated to the low voltage of transformer 2 (TR2) if it exists. These voltages
levels are represented by objects of the CIM class VoltageLevel. The VoltageLevel_13200 is organized in
5 bays: Bay_AT_TR1 and Bay_AT_TR2 associated to the high voltage input of transformer TR1 and TR2;
Bay_AT_1, Bay_AT_2 and Bay_AT_3 associated to medium voltage lines that connect the substation
with other substations. Each bay is an object of the CIM class Bay. An object of the class BusbarSection
connects the bays. It represents the busbar section.
The VoltageLevel_400_1 has 5 bays associated with 5 low voltage distribution lines connected by a
BusbarSection object. Each bay has a fuse (an object of the CIM class Fuse). Each line is also an object of
59 | 130
PROJECT
the CIM class EquipmentContainer. Also, each line has associated a set of consumer boxes represented
by objects of the CIM class EnergyConsumer, that are connected by objects of the CIM class
ACLineSegments. Each ACLineSegment object represents a physical segment of the low voltage line.
Only Line_1 has been outlined in Figure 28. VoltageLevel_400_2 has a similar organization.
Substation_CTD1
VoltageLevel_13200
Bay_AT_TR1 Bay_AT_1 Bay_AT_2 Bay_AT_3 Bay_AT_TR2
LB22
LB12
LB3
LB4
LB5
GD12 GD3 GD4 GD5 GD22
F1
F3
LB11
LB21
GD11 GD21
TR2
TR1
VoltageLevel_400_1 VoltageLevel_400_2
D2
D1
Bay_1 Bay_5 Bay_6 Bay_10

F_7
F_10
F_8
F_9
F_2
F_3
F_4
F_5
F_6
F_1
ACLS_1_2 ACLS_1_1
Line_1 Line_MV1 Line_MV2 Line_MV3 Disconnector

PowerTransformer
ACLS_MV1_1
ACLS_MV2_1
ACLS_MV3_1
ACLS_1_4
ACLS1
LoadBreakerSwitch ACLineSegment
ACLS_1_3
BusbarSection
EC1
ACLS_MV1_2
EnergyConsumer
ACLS_MV2_2
ACLS_MV3_2
EC_1_2
ConnectivityNode
Fuse
Terminal
EC_1_1
GroundDisconnector
FIGURE 28 GRAPHICAL REPRESENTATION OF A DISTRIBUTION NETWORK USING THE CIM MODEL
60 | 130
PROJECT
Figure 29 and Figure 30 show the used standard CIM classes for representing the data requirements of
the LVNMS. Only 2 new classes have been added: IBD2FuseInfo and IBD2PowerTransformerInfo
represented by green boxes. Also, the extended CIM classes used in section 5.1.1, represented by blue
boxes, has been added to the figures for comparing both approaches. Figure 30 shows that the majority
of the added classes from the CIM standards are related with the asset view. So, this CIM modelling
shows the power of the standard CIM model. But, it is not enough, new classes must be included in the
future for covering the description of elements of the distribution network, more of them related with
the asset view. Nevertheless, the CIM provides methods for dealing with this gap until the arrival of new
editions of the standard CIM model.
61 | 130
PROJECT
cl a ss I B D2
+Assets
P SRTy pe A sset
GEP SRRol e
0..*

+Location 0..1
P ow er Sy st emResour ce +PowerSystemResources
0..*
+Location
0..* Loca t i on
0..1
+ConnectivityNodeContainer 1 +EquipmentContainer +Equipments Equi pment

0..1 0..*
Li ne
Subst a t i on
+Substation 1

Bay
C onnect or
Ener gy C onsumer
+Terminals
+Terminals
0..* 0..*

+Terminal 0..1
B usba r Sect i on
+Switch
Sw i t ch
P r ot ect edSw i t ch 0..* Sw i t chP ha se

Tr a nsf or mer End
+TransformerEnd 1 P ow er Tr a nsf or mer
+PowerTransformer 0..1
Loa dB r ea k Sw i t ch
Fuse
+RatioTapChanger0..1
Ra t i oTa pC ha nger
Di sconnect or
Gr oundDi sconnect or
+PowerTransformerEnd 0..*
P ow er Tr a nsf or mer End I B DFuseLV
FIGURE 29 CIM CLASSES FOR REPRESENTING THE ELECTRICAL VIEW OF THE DISTRIBUTION NETWORK
62 | 130
PROJECT
cl a ss I B D2
+AssetInfo
+Assets A sset I nf o
+Asset
A sset 0..1
0..*
0..* +AssetInfo 0..1
+Assets
+Asset
+Assets0..*0..1
0..*
+ProductAssetModel 0..1
+ProductAssetModel
0..1 P r oduct A sset M odel P ow er Tr a nsf or mer I nf o
+Location 0..1 +ProductAssetModels 0..*

O r ga ni sa t i onRol e
Loca t i on
I B D2P ow er Tr a nsf or mer I nf o
+Manufacturer 0..1
M a nuf a ct ur er Sw i t chI nf o
+OrganisationRoles 0..*
Equi pment A sset O r ga ni sa t i onRol e I B D2FuseI nf o
+Equipments
0..* W i r eI nf o
+Ownerships 0..*
O w ner shi p +Ownerships

+AssetOwner
0..*
0..1 A sset O w ner
C a bl eI nf o
W or k Loca t i on
+UsagePoints 0..*
U sa geP oi nt
+UsagePoints 0..*
+ServiceLocation 0..1
Ser v i ceLoca t i on C r ew
FIGURE 30 CIM CLASSES FOR REPRESENTING THE ASSET VIEW OF THE DISTRIBUTION NETWORK
Table 16 indicates the attributes of the standard CIM model that represent the attributes of the new
classes defined in section 5.1.1. The added classes, IBD2PowerTransformerInfo that inherits from
PowerTransformerInfo and IBD2Fuse that inherits from SwitchInfo, have added only a few parameters
to the existing classes.
TABLE 16 TRANSLATION OF THE ATTRIBUTES OF THE NEW CLASSES DEFINED AT SECTION 5.1.1
New class name New attributes Standard CIM class
provinceCode ServiceLocation (stateOrProvince)

town ServiceLocation (townDetail)
IBDSecondarySubstation direction ServiceLocation (streetDetail)
postalCode ServiceLocation (postalCode)
functionKind PSRType
63 | 130
PROJECT
physicalLocationKind ServiceLocation (type)

electricalConfigurationKind ProductAssetModel
status Asset (inUseState)
manufacturer Manufacturer
maintenanceResponsible Crew
accessMethod ServiceLocation (accessMethod)
property Ownership
dataBaseID Asset (utcNumber)
position Terminal
positionKind ServiceLocation
positionStatus Asset (inUseState)
mvConnectionKind Terminal
mvConnectionSection CableInfo
mvConnectionMaterial CableInfo
IBDDistributionTransfomer ratedS PowerTransformerEnd (ratedS)
outputKind IBD2PowerTransformerInfo
physicalPlacementKind ServiceLocation
refrigerantKind IBD2PowerTransformerInfo
connectionKind PowerTransformerEnd (vectorGroup)
regulationRange RatioTapChanger
tapStep RatioTapChanger
embeddedFuse Fuse
IBDSecondarySubstationID Terminal
position Terminal
cabinet Terminal
fuseKind IBD2FuseInfo
IBDFuseLV
fuseDescription IBD2FuseInfo
manufacturerModel ProductAssetModel
nominalCurrent SwitchInfo
nominalVoltage VoltageLevel
position Terminal
cabinet Terminal
cableKind CableInfo
IBDLowVoltageLine
phaseWireCount Terminal
layingKind CableInfo
section CableInfo
headMaterial CableInfo
IBDACLineSegment IBDSecondarySubstationID Terminal
64 | 130
PROJECT
IBDSecondarySubstationName Terminal
nameIBD Terminal
physicalPlacementKind Asset
segmentNumber Terminal
cableKind CableInfo
Conductor.length ACLineSegment
property Ownership
maximumCurrent CableInfo
layingKind Asset
neutral Terminal
phases Terminal
nominalVoltage Terminal
provinceCode ServiceLocation (stateOrProvince)
town ServiceLocation (townDetail)
street ServiceLocation (streetDetail)
streetNumber ServiceLocation (streetDetail)
bisData ServiceLocation (streetDetail)
bisKind ServiceLocation (streetDetail)
nameIBD Asset
IBDSecondarySubstationID Terminal
IBDACLineSegmentID Terminal
customerCount UsagePoint
contractedPower UsagePoint
threePhaseCustomerCount UsagePoint
specialNeedCustomerCount UsagePoint
IBDEnergyConsumer generationCustomerCount UsagePoint
less15kwCustomerCount UsagePoint
less15kwContractedPower UsagePoint
between15kwAnd50kwCustomerCount UsagePoint
between15kwAnd50kwContractedPower UsagePoint
greater50kWCustomerCount UsagePoint
greater50kWContratedPower UsagePoint
generationContractCount UsagePoint
generatedPower UsagePoint
generationKind UsagePoint
secundarySubstationDistance Terminal
maximumCurrent UsagePoint
connectionKind Terminal
direction ServiceLocation (streetDetail)
65 | 130
PROJECT
accessMethodKind ServiceLocation (streetDetail)

accessMethod ServiceLocation (streetDetail)
supplyKind UsagePoint
internalExternal Asset
phaseCode Terminal
neutralConductor Terminal
fuseRatedCurrent SwitchInfo
status Asset (inUseState)
insulationKind CableInfo
fuseKind IBD2FuseInfo
fuseClass IBD2FuseInfo
fuseSize IBD2FuseInfo
physicalPlacementKind ServiceLocation (type)
incomingCableKind Terminal
incomingCableLength Terminal
outcomingCableKind Terminal
mainConsumptionKind UsagePoint
amiBillingReadyKind UsagePoint
Figure 31 to Figure 33 show examples of the RDF XML translation of the new classes defined in section
5.1.1 to standard CIM classes. In the case of consumer box, the elaborated attributes of
IBDEnergyConsumer, as less15kwCustomerCount or between15kwAnd50kwContractedPower, has been
substituted by the detailed information per consumer using the CIM class UsagePoint. This detail is
important for making the difference between the elaborated summary that the electrical engineer
needs and how the data is recorded in the system. From the point of view of recording, the important
goal is to have all the information in a way that permits in the future the elaboration of different figures.
In the case of ServiceLocation, the GIS information has been included for connecting to a GIS database.
Another approach is using the Location at the Terminal object for connecting with SCADA diagrams
using the IEC 61970-453 [23] .
<cim:Substation rdf:about="#_CTD200004790">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_CTD"/>
</cim:Substation>

<cim:Asset rdf:about="#_ASSET_CTD200004790">
<cim:IdentifiedObject.name>LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.utcNumber>200004790</cim:Asset.utcNumber>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790"/>
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_CTD"/>
<cim:Asset.inUseState>inUse</cim:Asset.inUseState>
<cim:Asset.Location rdf:resource="#_SERVICELOCATION_CTD200004790"/>
<cim:Asset.Ownership rdf:resource="#_OWNERSHIP_100_IBERDROLA"/>
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CTD200004790"/>
</cim:Asset>
66 | 130
PROJECT


<cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790">
<cim:ProductAssetModel.manufacturer rdf:resource="#_MANUFACTURER1"/>
<cim:IdentifiedObject.name>CTD</cim:IdentifiedObject.name>
<cim:ProductAssetModel.modelNumber>CONVENCIONAL</cim:ProductAssetModel.modelNumber>
</cim:ProductAssetModel>

<cim:ServiceLocation rdf:about="#_SERVICELOCATION_CTD200004790">
<cim:Location.geoInfoReference>GIS entry 1</cim:Location.geoInfoReference>
<cim:Location.mainAddress>
<cim:mainAddress>
<cim:postalCode>48001</cim:postalCode>
<cim:mainAddress.townDetail>
<cim:townDetail>
<cim:townDetail.name>BILBAO</cim:townDetail.name>
<cim:townDetail.stateOrProvince>BIZKAIA</cim:townDetail.stateOrProvince>
</cim:townDetail>
</cim:mainAddress.townDetail>
<cim:mainAddress.streetDetail>
<cim:streetDetail>
<cim:streetDetail.type>CALLE</cim:streetDetail.type>
<cim:streetDetail.name>LEDESMA</cim:streetDetail.name>
<cim:streetDetail.number>10 BIS</cim:streetDetail.number>
<cim:streetDetail.buildingName/>
<cim:streetDetail.addressGeneral>ENTRAD POR
BERASTE</cim:streetDetail.addressGeneral>
</cim:streetDetail>
</cim:mainAddress.streetDetail>
</cim:mainAddress>
</cim:Location.mainAddress>
<cim:Location.type>EDIFICIO SOTANO</cim:Location.type>
<cim:ServiceLocation.accessMethod>CAJETIN CON LLAVES DEL PORTAL, EN EL PORTAL HAY
OTRO CAJETIN CON LLAVE DE ACCESO)</cim:ServiceLocation.accessMethod>
</cim:ServiceLocation>
FIGURE 31 RDF XML EXAMPLE OF THE TRANSLATION OF IBDSECONDARYSUBSTATION
<cim:PowerTransformer rdf:about="#_CTD200004790_TR1">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVTRANSFORMER"/>
<cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/>
<cim:PowerTransformer.vectorGroup>DYn11</cim:PowerTransformer.vectorGroup>

<cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_AT">
<cim:PowerTransformerEnd.PowerTransformer rdf:resource="#_CTD200004790_TR1"/>
<cim:TransformerEnd.BaseVoltage rdf:resource="#_BaseVoltage_13200"/>
<cim:TransformerEnd.Terminal rdf:resource="#_CTD200004790_TR1_T1"/>
<cim:TransformerEnd.endNumber>1</cim:TransformerEnd.endNumber>
<cim:PowerTransformerEnd.ratedS>
<cim:ratedS>
<cim:ratedS.value>630</cim:ratedS.value>
<cim:ratedS.multiplier>k</cim:ratedS.multiplier>
</cim:ratedS>
</cim:PowerTransformerEnd.ratedS>
<cim:TransformerEnd.RatioTapChanger rdf:resource="#_CTD200004790_TR1_AT_TAPCHANGER"/>
</cim:PowerTransformerEnd>
67 | 130
PROJECT


<cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_BT">

<cim:RatioTapChanger rdf:about="#_CTD200004790_TR1_AT_TAPCHANGER">
<cim:RatioTapChanger.highStep>5</cim:RatioTapChanger.highStep>
<cim:RatioTapChanger.lowStep>1</cim:RatioTapChanger.lowStep>
<cim:RatioTapChanger.neutralStep>1</cim:RatioTapChanger.neutralStep>
<cim:TapChanger.neutralU>13200</cim:TapChanger.neutralU>
<cim:RatioTapChanger.step>5</cim:RatioTapChanger.step>
<cim:RatioTapChanger.stepVoltageIncrement>2.5</cim:RatioTapChanger.stepVoltageIncrement>
</cim:RatioTapChanger>

<cim:Terminal rdf:about="#_CTD200004790_TR1_T1">
<cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber>
<cim:Terminal.phases rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.ABC"/>
<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_BAY_AT_TR1_OUT"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_TR1"/>
</cim:Terminal>

<cim:Terminal.phases rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.ABCN"/>
<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_VOLTAGELEVEL_400_1_IN"/>
</cim:Terminal>

<cim:Asset rdf:about="#_ASSET_CTD200004790_TR1">
<cim:IdentifiedObject.name>TRAFO 1 LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_TR1"/>
<cim:Asset.serialNumber>136457</cim:Asset.serialNumber>
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_TR"/>
<cim:IdentifiedObject.name>INVENTARIO TRAFO 1 LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.type>TRANSFORMADOR DE DISTRIBUCIÓN DE BAJA TENSIÓN</cim:Asset.type>
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CTD200004790_TR1"/>
</cim:Asset>

<cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790_TR1">
<cim:ProductAssetModel.modelNumber>INTERIOR</cim:ProductAssetModel.modelNumber>
<cim:IBDPowerTransformerInfo rdf:about="#_ASSETINFO_TR">
<cim:IdentifiedObject.name>TRANSFORMADOR DE DISTRIBUCIÓN</cim:IdentifiedObject.name>
<cim:IBDPowerTransformerInfo.refrigerantKind>OIL</cim:IBDPowerTransformerInfo.refrigerantKind>
<cim:IBDPowerTransformerInfo.class>B1B2</cim:IBDPowerTransformerInfo.class>
</cim:IBDPowerTransformerInfo>
FIGURE 32 RDF XML EXAMPLE OF THE TRANSLATION OF IBDDISTRIBUTIONTRANSFORMER

<cim:Fuse rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_F_1">
68 | 130
PROJECT
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVFUSE"/>
<cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_BAY_1"/>
</cim:Fuse>

<cim:Asset rdf:about="#_ASSET_CTD200004790_VOLTAGELEVEL_400_1_F_1">
<cim:IdentifiedObject.name>FUSIBLE LINEA 1</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/>
<cim:Asset.SwitchInfo rdf:resource="#_FUSEINFO_TYPE1"/>
</cim:Asset>

<cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_T1">
<cim:Terminal.ConnectivityNode
rdf:resource="#_CN_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/>
</cim:Terminal>

rdf:resource="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_1"/>
</cim:Terminal>
<cim:SwitchInfo rdf:about="#_FUSEINFO_TYPE1">
<cim:IdentifiedObject.name>FUSIBLE DE SALIDA 250</cim:IdentifiedObject.name>
<cim:SwitchInfo.breakingCapacity>250</cim:SwitchInfo.breakingCapacity>
<cim:material>copper</cim:material>
</cim:SwitchInfo>
FIGURE 33 RDF XML EXAMPLE OF THE TRANSLATION OF IBDFUSELV

<cim:EnergyConsumer rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1">
<cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/>
<cim:PowerSystemResource.PSRType rdf:resource="#_PSRTYPE_LVCONSUMERBOX"/>
<cim:Equipment.UsagePoints rdf:resource="#_CAJA_3131739_PROFILE_CUSTOMER1"/>
</cim:EnergyConsumer>

<cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1_T1">
<cim:Terminal.ConductingEquipment
rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1"/>
</cim:Terminal>

<cim:Asset rdf:about="#_ASSET_CAJA_3131739">
<cim:IdentifiedObject.name>CAJA 3131739</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_ENERGYCONSUMER"/>
<cim:Asset.Location rdf:resource="#_SERVICELOCATION_CAJA_3131739"/>
69 | 130
PROJECT
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CAJA_3131739"/>
</cim:Asset>

<cim:ServiceLocation rdf:about="#__SERVICELOCATION_CAJA_3131739">
<cim:mainAddress>
<cim:townDetail>
</cim:townDetail>
<cim:streetDetail>
<cim:streetDetail.addressGeneral/>
</cim:streetDetail>
</cim:mainAddress>
<cim:Location.type>PATIO MANZANA</cim:Location.type>
<cim:ServiceLocation.accessMethod>POR VIVIENDA XXX</cim:ServiceLocation.accessMethod>

<cim:Asset rdf:about="#_ASSET_CAJA_3131739_FUSE">
<cim:Asset.IBDFuseInfo rdf:resource="#_FUSEINFO_TYPE2"/>
<cim:Asset.PowerSystemResources>#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1</cim:Asset.P
owerSystemResources>
</cim:Asset>

<cim:UsagePoint rdf:about="#_CAJA_3131739_PROFILE_CUSTOMER1">
<cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-
cim17#PhaseCode.ABCN"/>
<cim:UsagePoint.nominalServiceVoltage>400</cim:UsagePoint.nominalServiceVoltage>
<cim:UsagePoint.estimatedLoad>85</cim:UsagePoint.estimatedLoad>
<cim:isSdp>true</cim:isSdp>
<cim:UsagePoint.ratedCurrent>30</cim:UsagePoint.ratedCurrent>
<cim:UsagePoint.servicePriority>NORMAL</cim:UsagePoint.servicePriority>
<cim:UsagePoint.connectionState rdf:resource="http://iec.ch/TC57/2016/CIM-schema-
cim17#UsagePointConnectedKind.logicallyDisconnected"/>
</cim:UsagePoint>
<cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.AN"/>
<cim:isSdp>false</cim:isSdp>
cim17#UsagePointConnectedKind.connected"/>
70 | 130
PROJECT
</cim:UsagePoint>
FIGURE 34 RDF XML EXAMPLE OF THE TRANSLATION OF IBDENERGYCONSUMER
Figure 31 to Figure 34 also show how the data has been organized to provide data confidentiality:
 The electrical view using classes that inherit from EquipmentContainer and
ConductingEquipment that represent the topology and the electrical parameters of the
elements, without reference to location information. A third part can receive this information for
running, for instance, a power flow analysis, in an anonymous way.
 The asset view with separation between locations and other asset data. Also, asset data could be
managed without reference to specific locations if the ServiceLocation objects are not used.
Annex I provides a full example of low voltage distribution network using the CIM RDF XML format.
Notice that IDs (example: “_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1”) are not compliant
with IEC 61970-552. For example, a good ID is “_f692ed67-51a3-48a4-85ae-994173b5202f”.
Nevertheless, IDs as “CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1” has been used in the
examples in order to simplified to the reader the cross-referencing.
The comparison of section 5.1.1 and section 5.1.2 show that is easy to establish the automatic
translation between the two solutions. Some engineers have a complaint about the flexibility of the
CIM. It just the opposite, the fallacy is to try to obtain a unique static CIM model. It is not possible, we
don’t know the new requirements of the future networks; so, it is impossible to have this universal
model. The advantage of using CIM is not only the complete model of the current electrical networks
but also the ability to model future requirements and to establish relationships between different
models. The base of the CIM model is the semantic web techniques as ontologies, ontology alignment,
or automatic reasoning, that brings powerful tools for modelling and translating.
5.2 SWEDISH DEMO

The use of the CIM in the Swedish demo is similar to the Spanish demo: a LVNMS is going to be
deployed and the LVNMS input data uses the CIM XML RDF format. So, an application must convert the
data from the existing Vattenfall databases to the LVNMS. However, the Swedish approach to the CIM
model is more similar to section 5.1.2 than section 5.1.1, because it tries to minimize the use of the class
extension mechanism. In fact, all the Vattenfall data requirements have been fulfilled without the
addition of new classes to the standard CIM model.
Figure 35 and Figure 36 show the CIM classes used by the Swedish demo in comparison with the Spanish
demo. Grey boxes represent CIM classes used by the Swedish and the Spanish demo. Blue boxes
correspond to the new classes added in the Spanish demo (see section 5.1.1). Green boxes correspond
to the 2 new classes (IBD2PowerTransformerInfo and IBD2FusesInfo) added in section 5.1.2 and to the
standard CIM classes that section 5.1.2 only uses. Pink boxes correspond to the standard CIM classes
used in the Swedish demo and in section 5.1.2. Orange boxes are the standard classes only used by the
Swedish demo.
71 | 130
PROJECT
The Swedish demo has a little issue because it uses the class SwitchInfo that is part of the CIM model
but it’s not standard. It belongs to the informative package InfIEC61968 that has the next associated
comment: “This package and its subpackages contain informative (unstable) elements of the model,
expected to evolve a lot or to be removed, and not published as IEC document yet. Some portions of it
will be reworked and moved to normative packages as the need arises, and some portions may be
removed. WG14 does not generate documentation for this informative portion of the model.” So, this
issue added to the necessity for adding to new classes in section 5.1.2, clearly shows that the CIM model
needs to be upgraded with new classes that fulfil the asset information requirements. Even so, the RDF
organization of the CIM model permits the addition of new classes using the inheritance without
affecting existing classes or applications that work with existing standard classes. The reusability and the
scalability are essential parts of the CIM model.
72 | 130
PROJECT
cl a ss I B DGEv 1
+Assets
P SRTy pe A sset
GEP SRRol e
0..*
C oor di na t eSy st em
+CoordinateSystem 0..1 +Location
+Locations 0..* 0..1
P ow er Sy st emResour ce +PowerSystemResources
0..*
+Location
+Location
0..* Loca t i on
+PositionPoints
0..1
1
P osi t i onP oi nt 0..*
+ConnectivityNodeContainer 1 +EquipmentContainer +Equipments Equi pment

0..1 0..*
Li ne
Subst a t i on
+Substation 1

Bay
C onnect or
Ener gy C onsumer
+Terminals
+Terminals
0..* 0..*

+Terminal 0..1
B usba r Sect i on
+Switch
Sw i t ch
P r ot ect edSw i t ch 0..* Sw i t chP ha se

Tr a nsf or mer End
+TransformerEnd 1 P ow er Tr a nsf or mer
+PowerTransformer 0..1
Loa dB r ea k Sw i t ch B r ea k er Jumper
Fuse
+RatioTapChanger0..1
Ra t i oTa pC ha nger
Di sconnect or
Gr oundDi sconnect or
+PowerTransformerEnd 0..*
P ow er Tr a nsf or mer End I B DFuseLV
FIGURE 35 CIM CLASSES OF THE SWEDISH DEMO AND COMPARISON WITH THE SPANISH DEMO (ELECTRICAL VIEW)
73 | 130
PROJECT
cl a ss I B DGEv 1
+Assets +AssetInfo
+Asset A sset I nf o
A sset
0..* 0..1
0..*
+Assets
+Asset
+Assets0..*0..1
0..* +AssetInfo 0..1
+ProductAssetModel 0..1
+ProductAssetModel
0..1 P r oduct A sset M odel P ow er Tr a nsf or mer I nf o
+Location 0..1 +ProductAssetModels 0..*

O r ga ni sa t i onRol e
Loca t i on
I B D2P ow er Tr a nsf or mer I nf o
+Manufacturer 0..1
M a nuf a ct ur er Sw i t chI nf o
+OrganisationRoles 0..*
Equi pment A sset O r ga ni sa t i onRol e I B D2FuseI nf o
+Equipments
0..* W i r eI nf o
+Ownerships 0..*
O w ner shi p +Ownerships

+AssetOwner
0..*
0..1 A sset O w ner
C a bl eI nf o
O l dSw i t chI nf o
C oncent r i cNeut r a l C a bl eI nf o
B r ea k er I nf o
W or k Loca t i on
+UsagePoints 0..*
U sa geP oi nt
+UsagePoints 0..*
+ServiceLocation 0..1
Ser v i ceLoca t i on C r ew
FIGURE 36 CIM CLASSES OF THE SWEDISH DEMO AND COMPARISON WITH THE SPANISH DEMO (ASSET VIEW)
Figure 37 to Figure 41 give details of the CIM RDF XML format used by the Swedish demo.
<cim:Substation rdf:ID="_f49acfcc-b7ef-4442-a2b4-340123589825">
<cim:IdentifiedObject.mRID>f49acfcc-b7ef-4442-a2b4-340123589825</cim:IdentifiedObject.mRID>
<cim:PowerSystemResource.Location rdf:resource="#_72261d6e-5a2d-4c4e-ab0d-ba7cf105c31d" />
<cim:PowerSystemResource.PSRType rdf:resource="#_35053982-00f0-4167-a3ff-dc7551e101b2" />
<cim:IdentifiedObject.name>XCC000002</cim:IdentifiedObject.name>
<cim:IdentifiedObject.description>KB</cim:IdentifiedObject.description>
</cim:Substation>
<cim:Location rdf:ID="_72261d6e-5a2d-4c4e-ab0d-ba7cf105c31d">
<cim:IdentifiedObject.mRID>72261d6e-5a2d-4c4e-ab0d-ba7cf105c31d</cim:IdentifiedObject.mRID>
<cim:Location.CoordinateSystem rdf:resource="#_06aa62a3-4ee4-4cdc-9167-bd50e0296cc0" />
<cim:Location.mainAddress></cim:Location.mainAddress>
<nb:Location.rotation>0</nb:Location.rotation>
74 | 130
PROJECT
</cim:Location>
<cim:PositionPoint rdf:ID="_265c865b-cc12-4209-93cc-fb64da5964b4">
<cim:PositionPoint.Location rdf:resource="#_72261d6e-5a2d-4c4e-ab0d-ba7cf105c31d" />
<cim:PositionPoint.xPosition>1452340.25</cim:PositionPoint.xPosition>
<cim:PositionPoint.yPosition>6320240.5</cim:PositionPoint.yPosition>
<cim:PositionPoint.sequenceNumber>1</cim:PositionPoint.sequenceNumber>
</cim:PositionPoint>
FIGURE 37 RDF XML EXAMPLE OF SECONDARY SUBSTATION
<cim:PowerTransformer rdf:ID="_69b8806c-26dd-4065-9491-fda148be2ddc">
<cim:IdentifiedObject.mRID>69b8806c-26dd-4065-9491-fda148be2ddc</cim:IdentifiedObject.mRID>
<cim:PowerSystemResource.Location rdf:resource="#_7112ac3e-1b3a-4dad-b4af-892ce146ed41" />
<cim:Equipment.EquipmentContainer rdf:resource="#_8a2b914b-fd22-43af-bb3b-450899ec8d8d" />
<cim:PowerSystemResource.Assets rdf:resource="#_f39517c5-aa03-4df8-804f-4ad43d994a23" />
<cim:Asset rdf:ID="_f39517c5-aa03-4df8-804f-4ad43d994a23">
<cim:IdentifiedObject.mRID>f39517c5-aa03-4df8-804f-4ad43d994a23</cim:IdentifiedObject.mRID>
<cim:Asset.AssetInfo rdf:resource="#_2583a424-cebb-4ed7-9679-9bdf33632c95" />
<cim:Asset.OrganisationRoles rdf:resource="#_b12d9f7f-af15-4aca-8046-1b60ff4a94d9" />
<cim:IdentifiedObject.name>6TBN 100-12</cim:IdentifiedObject.name>
<cim:Asset.type>DT</cim:Asset.type>
<cim:Asset.serialNumber></cim:Asset.serialNumber>
<cim:Asset.lifecycle>
<cim:LifecycleDate>
<cim:manufacturedDate></cim:manufacturedDate>
<cim:installationDate></cim:installationDate>
</cim:LifecycleDate>
</cim:Asset.lifecycle>
</cim:Asset>
<cim:PowerTransformerInfo rdf:ID="_2583a424-cebb-4ed7-9679-9bdf33632c95">
<cim:IdentifiedObject.mRID>2583a424-cebb-4ed7-9679-9bdf33632c95</cim:IdentifiedObject.mRID>
<cim:AssetInfo.AssetModel rdf:resource="#_d3b50d58-4939-4a3c-a2df-ebed9e683103" />
<cim:IdentifiedObject.name>KONCAR - 6TBN 100-12</cim:IdentifiedObject.name>
</cim:PowerTransformerInfo>
<cim:ProductAssetModel rdf:ID="_d3b50d58-4939-4a3c-a2df-ebed9e683103">
<cim:IdentifiedObject.mRID>d3b50d58-4939-4a3c-a2df-ebed9e683103</cim:IdentifiedObject.mRID>
<cim:ProductAssetModel.Manufacturer rdf:resource="#_78561b26-ba85-4322-99cc-aa789bd1a820" />
<cim:IdentifiedObject.name>KONCAR - 6TBN 100-12</cim:IdentifiedObject.name>
<cim:Manufacturer rdf:ID="_78561b26-ba85-4322-99cc-aa789bd1a820">
<cim:IdentifiedObject.mRID>78561b26-ba85-4322-99cc-aa789bd1a820</cim:IdentifiedObject.mRID>
<cim:IdentifiedObject.name>KONCAR</cim:IdentifiedObject.name>
</cim:Manufacturer>
FIGURE 38 RDF XML EXAMPLE OF TRANSFORMER
75 | 130
PROJECT
<cim:Fuse rdf:ID="_28115786-8094-4400-90e4-54122c007e19">
<cim:IdentifiedObject.mRID>28115786-8094-4400-90e4-54122c007e19</cim:IdentifiedObject.mRID>
<cim:PowerSystemResource.Location rdf:resource="#_442b455e-601b-481d-b924-4f102c802f53" />
<cim:Equipment.EquipmentContainer rdf:resource="#_56c05e00-20a3-481f-a1bb-b6146a42ec0c" />
<cim:ConductingEquipment.BaseVoltage rdf:resource="#_dc7face4-2e1f-4768-96d7-ccb91b42463c" />
<cim:IdentifiedObject.name>NA</cim:IdentifiedObject.name>
<cim:Switch.ratedCurrent>35</cim:Switch.ratedCurrent>
</cim:Fuse>
FIGURE 39 RDF XML EXAMPLE OF FUSE
<cim:ACLineSegment rdf:ID="_b7f52c4c-29d3-4b3e-93e9-f121e3e2dca9">
<cim:IdentifiedObject.mRID>b7f52c4c-29d3-4b3e-93e9-f121e3e2dca9</cim:IdentifiedObject.mRID>
<cim:PowerSystemResource.Location rdf:resource="#_b464287b-5bd0-4d25-a446-0eab87944f3c" />
<cim:PowerSystemResource.PSRType rdf:resource="#_9ca184f0-3008-417a-bf19-e189f2055336" />
<cim:PowerSystemResource.Assets rdf:resource="#_4674e849-7a02-49c8-881c-88362f0a5cc5" />
<cim:IdentifiedObject.name></cim:IdentifiedObject.name>
<cim:Conductor.length>6</cim:Conductor.length>
<cim:ACLineSegment.b0ch>0</cim:ACLineSegment.b0ch>
<cim:ACLineSegment.bch>2.82743334E-07</cim:ACLineSegment.bch>
<cim:ACLineSegment.r0>0.04392</cim:ACLineSegment.r0>
<cim:ACLineSegment.x0>0.00192</cim:ACLineSegment.x0>
<cim:Asset rdf:ID="_4674e849-7a02-49c8-881c-88362f0a5cc5">
<cim:IdentifiedObject.mRID>4674e849-7a02-49c8-881c-88362f0a5cc5</cim:IdentifiedObject.mRID>
<cim:Asset.AssetInfo rdf:resource="#_3aa8bc87-0646-41c5-91fc-698ad55e89c0" />
<cim:Asset.OrganisationRoles rdf:resource="#_b12d9f7f-af15-4aca-8046-1b60ff4a94d9" />
<cim:IdentifiedObject.name>N1XE-U4G10</cim:IdentifiedObject.name>
<cim:Asset.type>KA</cim:Asset.type>
<cim:Asset.serialNumber></cim:Asset.serialNumber>
<cim:Asset.lifecycle>
<cim:LifecycleDate>
<cim:manufacturedDate></cim:manufacturedDate>
<cim:installationDate></cim:installationDate>
</cim:LifecycleDate>
</cim:Asset.lifecycle>
</cim:Asset>
<cim:ConcentricNeutralCableInfo rdf:ID="_3aa8bc87-0646-41c5-91fc-698ad55e89c0">
<cim:IdentifiedObject.mRID>3aa8bc87-0646-41c5-91fc-698ad55e89c0</cim:IdentifiedObject.mRID>
<cim:AssetInfo.AssetModel rdf:resource="#_446ec369-712c-48a6-ab06-cc44bc3e2234" />
<cim:IdentifiedObject.name>1 - N1XE-U4G10</cim:IdentifiedObject.name>
<cim:WireInfo.material>copper</cim:WireInfo.material>
<cim:Wireinfo.coreRadius>0.00178415042592281</cim:Wireinfo.coreRadius>
<cim:Wireinfo.strandCount></cim:Wireinfo.strandCount>
<cim:ConcentricNeutralCableInfo.neutralStrandRadius>0.00178415042592281</cim:ConcentricNeutralCableInfo.n
eutralStrandRadius>
<cim:ConcentricNeutralCableInfo.neutralStrandCount>1</cim:ConcentricNeutralCableInfo.neutralStrandCount>
<cim:Wireinfo.ratedCurrent>95</cim:Wireinfo.ratedCurrent>
76 | 130
PROJECT
</cim:ConcentricNeutralCableInfo>
FIGURE 40 RDF XML EXAMPLE OF LINE SEGMENT
<cim:EnergyConsumer rdf:ID="_b2fb0e82-76c2-4263-8be7-e709fe7a9dd1">
<cim:IdentifiedObject.mRID>b2fb0e82-76c2-4263-8be7-e709fe7a9dd1</cim:IdentifiedObject.mRID>
<cim:PowerSystemResource.Location rdf:resource="#_58aab9d0-cb6b-4b31-9887-48003c0e4c91" />
<cim:UsagePoint rdf:ID="_b89280f8-7ce5-4226-8979-a31a127b1c34">
<cim:IdentifiedObject.mRID>b89280f8-7ce5-4226-8979-a31a127b1c34</cim:IdentifiedObject.mRID>
<cim:UsagePoint.Equipments rdf:resource="#_b2fb0e82-76c2-4263-8be7-e709fe7a9dd1" />
<cim:IdentifiedObject.name>000887624003330448</cim:IdentifiedObject.name>
</cim:UsagePoint>
FIGURE 41 RDF XML EXAMPLE OF ENERGY CONSUMER
Table 17 shows a detailed comparison of the used attributes for the same standard CIM classes at the
Swedish demo and the Spanish demo. The Spanish demo prefers to link asset objects with power system
resource objects and Swedish demo prefers the opposite approach: power system resources with
assets. The Spanish approach guaranty better the confidentiality.
TABLE 17 COMPARISON OF USED ATTRIBUTES IN SOME STANDARD CLASSES
Standard CIM class Attributes used by the Swedish demo Attributes used by the Spanish demo
ACLineSegment mRID length
Location PSRType
PSRType EquipmentContainer
BaseVoltage
Assets
name
length
b0ch
bch
r
r0
x
x0
Asset mRID name
AssetInfo utcNumber
OrganisationRoles PowerSystemResources
name AssetInfo
type inUseState
77 | 130
PROJECT
serialNumber Location
manufacturedDate Ownership
installationDate ProductAssetMod
EnergyConsumer mRID EquipmentContainer
Location PSRType
BaseVoltage UsagePoints
UsagePont mRID phaseCode
Equipments nominalServiceVoltage
name estimatedLoad
isSdp
ratedCurrent
servicePriority
connectionState
Table 18 summarizes the differences between the CIM modelling of the Spanish demo and the Swedish
demo. Both demos have a detailed representation of the electrical topology. However, the Swedish
demo has a higher description of the electrical parameters of the electrical components, except in the
case of consumers. The Spanish demo has a detailed profile of consumption and generation in the case
of consumers. Also, the asset details are more in the Spanish demo that in the Swedish demo. For
example, the Spanish provide full information about the location of the asset and the crew in charge of
the asset. In other hand, the Spanish demo uses GML for network geometry, whilst the Swedish demo
uses the built in CIM classes.
TABLE 18 COMPARISON BETWEEN SPANISH AND SWEDISH CIM MODELLING
Aspect Spanish demo Swedish demo
Electrical topology High High
Electrical parameters Medium High
Asset data High Medium
SCADA graphics Low Medium
Geographical information Medium Low
78 | 130
PROJECT
5.3 POLISH DEMO

The Polish demo uses the CIM XML format. It uses two sets of XML schemas: one is related to metering
and the other, with the transfer of electrical objects. Following sections describe these two sets.
5.3.1 METERING
The Polish demo uses the following XML schemas based on IEC 61968-9 [10] for exchanging information
related to smart meter readings:
 MeterReadings.xsd,
 GetMeterReadings.xsd,
 MeterReadSchedule.xsd,
 GetMeterReadSchedule.xsd.
Figure 42 to Figure 45 show the layout of these schemas.
FIGURE 42 XML SCHEMA OF METERREADINGS
FIGURE 43 XML SCHEMA OF GETMETERREADINGS
79 | 130
PROJECT
FIGURE 44 XML SCHEMA OF GETMETERREADSCHEDULE
FIGURE 45 XML SCHEMA OF METERREADSCHEDULE
Some XML schemas used by the Polish demo are simplifications of the original schemas defined in IEC
61968-9. For example, schema in Figure 42 is derived from the original MeterReadings schema (Figure
46). Despite the simplifications, the schemas are compliant with the relevant IEC standards.
80 | 130
PROJECT
FIGURE 46 ORIGINAL XML SCHEMA OF METERREADINGS DEFINED BY IEC 61968
Also, the Polish demo uses the messages defined by IEC 61968-100 [11] for transferring data defined by
the XML schemas. Figure 47 shows a full example of reading requests. The yellow colour highlights the
parameters of the request: meter represented by the usage points, type of measurement represented
by the ReadingType and interval represented by the TimeSchedule.
81 | 130
PROJECT

<tns:GetMeterReadings xsi:schemaLocation="http://ksd.energa.pl/AMI/GetMeterReadings/xsd
xsd/GetMeterReadingsMessage_Ksd.xsd" xmlns:tns="http://ksd.energa.pl/AMI/GetMeterReadings/xsd"
xmlns:ksd="http://ksd.energa.pl/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ksd:ApplicationArea>
<ksd:Sender>
<ksd:LogicalId>aa</ksd:LogicalId>
<ksd:Component>aa</ksd:Component>
<ksd:Task/>
<ksd:ReferenceId/>
<ksd:Confirmation>0</ksd:Confirmation>
</ksd:Sender>
<ksd:CreationDateTime>2014-01-01T12:00:00+01:00</ksd:CreationDateTime>
<ksd:BODId>ABC-123</ksd:BODId>
</ksd:ApplicationArea>
<tns:DataArea>
<ns1:GetMeterReadings xmlns:ns1="http://iec.ch/TC57/2011/GetMeterReadingsMessage"
xmlns="http://iec.ch/TC57/2011/schema/message" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iec.ch/TC57/2011/GetMeterReadingsMessage
xsd/GetMeterReadingsMessage.xsd">
<ns1:Header>
<Verb>get</Verb>
<Noun>MeterReadings</Noun>
<Revision>1.0</Revision>
<Context>TESTING</Context>
<Timestamp>2014-01-01T12:00:00+01:00</Timestamp>
<Source>SCADA</Source>
<AsyncReplyFlag>false</AsyncReplyFlag>
<AckRequired>false</AckRequired>
<MessageID>ABC-123</MessageID>
</ns1:Header>
<ns1:Request>
<ns2:GetMeterReadings xmlns:ns2="http://iec.ch/TC57/2011/GetMeterReadings#"
xsi:schemaLocation="http://iec.ch/TC57/2011/GetMeterReadings# xsd/GetMeterReadings.xsd">
<ns2:ReadingType>
<ns2:Names>
<ns2:name>0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.38.0</ns2:name>
</ns2:Names>
</ns2:ReadingType>
<ns2:ReadingType>
<ns2:Names>
<ns2:name>0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0</ns2:name>
</ns2:Names>
</ns2:ReadingType>
<ns2:ReadingType>
<ns2:Names>
<ns2:name>0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.63.0</ns2:name>
</ns2:Names>
</ns2:ReadingType>
<ns2:ReadingType>
<ns2:Names>
<ns2:name>0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.63.0</ns2:name>
</ns2:Names>
</ns2:ReadingType>
<ns2:TimeSchedule>
<ns2:scheduleInterval>
<ns2:end>2014-01-01T12:00:00.0Z</ns2:end>
82 | 130
PROJECT
<ns2:start>2014-01-01T11:00:00.0Z</ns2:start>
</ns2:scheduleInterval>
</ns2:TimeSchedule>
<ns2:UsagePoint>
<ns2:mRID>PL0012312312312312:*</ns2:mRID>
</ns2:UsagePoint>
<ns2:UsagePoint>
<ns2:mRID>PL0023423423423412:*</ns2:mRID>
</ns2:UsagePoint>
</ns2:GetMeterReadings>
</ns1:Request>
</ns1:GetMeterReadings>
</tns:DataArea>
</tns:GetMeterReadings>
FIGURE 47 REQUEST OF METER READINGS
Figure 48 shows a correct answer to the request. The yellow colour highlights the answer with the
readings recorded by the meter at the usage point. More details about the construction of the message
will provided in the next section.
<tns:GetMeterReadingsResponse xsi:schemaLocation="http://ksd.energa.pl/AMI/GetMeterReadings/xsd
xsd/GetMeterReadingsMessage_Ksd.xsd" xmlns:tns="http://ksd.energa.pl/AMI/GetMeterReadings/xsd"
xmlns:ksd="http://ksd.energa.pl/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ksd:ApplicationArea>
<ksd:Sender>
<ksd:LogicalId>aa</ksd:LogicalId>
<ksd:Component>aa</ksd:Component>
<ksd:Task/>
<ksd:ReferenceId>ABC-123</ksd:ReferenceId>
<ksd:Confirmation>0</ksd:Confirmation>
</ksd:Sender>
<ksd:CreationDateTime>2014-01-01T12:00:01+01:00</ksd:CreationDateTime>
<ksd:BODId>XYZ-123</ksd:BODId>
</ksd:ApplicationArea>
<ksd:Reply>
<ksd:ReplyCode>OK</ksd:ReplyCode>
<ksd:ReplyDescription>Brak bledow</ksd:ReplyDescription>
</ksd:Reply>
<tns:DataArea>
<ns1:MeterReadingsResponseMessage xmlns:ns1="http://iec.ch/TC57/2011/GetMeterReadingsMessage"
xmlns="http://iec.ch/TC57/2011/schema/message" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iec.ch/TC57/2011/GetMeterReadingsMessage
xsd/GetMeterReadingsMessage.xsd">
<ns1:Header>
<Verb>reply</Verb>
<Noun>MeterReadings</Noun>
<Revision>1.0</Revision>
<Context>TESTING</Context>
<Timestamp>2014-01-01T12:00:01+01:00</Timestamp>
<Source>AMI</Source>
<AckRequired>false</AckRequired>
<MessageID>XYZ-123</MessageID>
<CorrelationID>ABC-123</CorrelationID>
</ns1:Header>
83 | 130
PROJECT
<ns1:Reply>
<Result>OK</Result>
</ns1:Reply>
<ns1:Payload>
<ns2:MeterReadings xmlns:ns2="http://iec.ch/TC57/2011/MeterReadings#"
xsi:schemaLocation="http://iec.ch/TC57/2011/MeterReadings# xsd/MeterReadings.xsd">
<ns2:MeterReading>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
<ns2:value>8</ns2:value>
</ns2:Readings>
<ns2:UsagePoint>
<ns2:mRID>PL0012312312312312:*</ns2:mRID>
</ns2:UsagePoint>
</ns2:MeterReading>
<ns2:MeterReading>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:Readings>
</ns2:Readings>
<ns2:UsagePoint>
<ns2:mRID>PL0023423423423412:*</ns2:mRID>
</ns2:UsagePoint>
</ns2:MeterReading>
</ns2:MeterReadings>
84 | 130
PROJECT
</ns1:Payload>
</ns1:MeterReadingsResponseMessage>
</tns:DataArea>
</tns:GetMeterReadingsResponse>
FIGURE 48 RESPONSE WITH READINGS
5.3.2 ELECTRIC OBJECTS
The Polish demo uses a set of XML schemas for forwarding the electrical object states (connectors,
measurements, warnings) and sending controls. These schemas have been developed from the CIM
model using the guidelines defined by IEC 62361-100 [24] . This represents another way of extending
the CIM. Based on the CIM UML model and using a tool, as the CIMTool3, the classes and the attributes
to be transferred have been selected and the schemas have been automatically generated.
The following schemas have been generated, among others:
 Measurements.xsd for transferring analog and discrete measurements,
 Commands.xsd for switch commands,
 SwichingPlans.xsd for FDIR (Fault Detection, Isolation & Restoration) sequences,
 Outages.xsd for information about potential occurrence of outages.
Figure 49 shows the used CIM classes for building the Measurement.xsd and Figure 50 shows the layout
of the schema. In the case of AnalogValue the following attributes has been selected:
 mRID from the parent class IdentifiedObject,
 timeStamp from the parent class MeasurementValue,
 MeasurementValueQuality from the associated class MeasurementValueQuality (not
represented at Figure 49),
 value from AnaloValue.
The identifier of the measurement point is in the header of the message
3
CIMTool is an open source tool that supports the Common Information Model (CIM) available at http://wiki.cimtool.org/Download.html. CIMTool can:
read and merge CIM and local UML models in XMI form, browse models and check inconsistencies, generate equivalent OWL ontologies, create and edit
profiles, create model extensions and map models to each other, generate XML schemas, OWL and RDFS ontologies for profiles and validate instances
against profiles (including very large CIM/XML instances).
85 | 130
PROJECT
FIGURE 49 CIM CLASSES FOR FORWARDING OBJECT STATES
86 | 130
PROJECT
FIGURE 50 SCHEMA MEASUREMENTS.XSD
Figure 51 shows the most important classes that participate in commands for the switch state control,
and Figure 52 represents the schema of Commands.xsd
87 | 130
PROJECT
FIGURE 51 CIM CLASSES FOR SWITCH STATE COMMANDS
FIGURE 52 SCHEMA COMMANDS.XSD
Figure 53 presents the classes and attributes that are used to send the FDIR sequences. FDIR sequences
are provided in a form of an ordered list of switches (breakers) which need to be opened or closed.
Figure 54 shows the used XML schema SwichingPlans.xsd for forwarding the sequences.
88 | 130
PROJECT
FIGURE 53 CIM CLASSES FOR FORWARDING FDIR SEQUENCES
89 | 130
PROJECT
FIGURE 54 SCHEMA SWITCHINGPLANS.XSD
Figure 55 shows the classes and attributes that are used to send information about potential occurrence
of outages, and Figure 56 presents the schema Outages.xsd for transferring the occurrences.
90 | 130
PROJECT
FIGURE 55 CIM CLASSES FOR POTENTIAL OUTAGE INFORMATION EXCHANGE
FIGURE 56 SCHEMA OUTAGES.XSD
91 | 130
PROJECT
The IEC 61968-100 stablishes tree levels for the XML schemas: the data level, the message level, the
transport level. These levels work independently and uses the “any” structure for communicating one
level with the other level. The main advantage is the independent development of the XML schemas.
But, it makes more complex the validation of the XML files, because each section of the XML file must be
validated with a different schema. In the case of the Polish demo, in order to simplify this validation, a
set of schemas that join schemas of the different levels has been developed. The used method has been
to substitute the “any” structure with the name of the schema to be used. For instance, the
transmission of measurement data needs a message for request measurements and other message for
transferring the measurement values. Figure 57 and Figure 58 represent the schema
GetMeasurements.xsd for the request, and ChangedMeasurements.xsd for automatic transferring of
measurements. Notice that ChangedMeasurements.xsd has included the structure of the Message.xsd
defined by IEC61968-100, and the payload has the structure of Measurement.xsd defined by Figure 50.
FIGURE 57 SCHEMA GETMEASUREMENTSKSD.XSD FOR GETTING MEASUREMENTS
92 | 130
PROJECT
FIGURE 58 SCHEMA CHANGEDMEASUAREMENTSKSD.XSD FOR SENDING THE MEASUREMENTS
The full schemas that the Polish demo uses, among others, are:
 GetMeasurementsKsd.xsd
 ReceiveMeasurementsKsd.xsd
 GetSwitchingPlansKsd.xsd
 ReceiveSwitchingPlansKsd.xsd
 ExecuteCommandsKsd.xsd
 GetCimXmlKsd.xsd
 ReceiveCimXmlKsd.xsd
The use of the GetCimXmlKsd.xsd and ReceiveCimXmlKsd.xsd schemas allows to request and transfer
CIM RDF XML or CIM XML documents in a compressed form. Figure 59 shows the layout of
GetCimXmlKsd.xsd.
93 | 130
PROJECT
FIGURE 59 SCHEMA GETCIMXML FOR REQUESTING CIM RDF XML OR CIM XML DOCUMENTS
Figure 60 shows an example of message for sending measurements using the

ChangedMeasurementsKsd schema defined in Figure 58. A message (ChangedMeasurements) is sent
after the occurrence of an object state change event. The field RerefenceID identifies the measurement
point.
<SOAP-ENV:Body>
<ksdrmeasxsd:ChangedMeasurements xsi:type="ksdrmeasxsd:ChangedMeasurements_Type">
<ksdxsdupgrid:ApplicationArea>
<ksdxsdupgrid:Sender>
<ksdxsdupgrid:LogicalId>a</ksdxsdupgrid:LogicalId>
<ksdxsdupgrid:Component>b</ksdxsdupgrid:Component>
<ksdxsdupgrid:Task/>
<ksdxsdupgrid:ReferenceId>A25621</ksdxsdupgrid:ReferenceId>
<ksdxsdupgrid:Confirmation/>
</ksdxsdupgrid:Sender>
<ksdxsdupgrid:CreationDateTime>2016-08-30T07:32:36+03:00</ksdxsdupgrid:CreationDateTime>
<ksdxsdupgrid:BODId>A25621</ksdxsdupgrid:BODId>
</ksdxsdupgrid:ApplicationArea>
<ksdrmeasxsd:DataArea>
<iecmeas:ChangedMeasurements>
<iecmeas:Header>
<iecmessageupgrid:Verb>changed</iecmessageupgrid:Verb>
<iecmessageupgrid:Noun>Measurements</iecmessageupgrid:Noun>
<iecmessageupgrid:Timestamp>2016-08-30T07:32:36+03:00</iecmessageupgrid:Timestamp>
<iecmessageupgrid:MessageID>A25621</iecmessageupgrid:MessageID>
</iecmeas:Header>
<iecmeas:Payload>
<mikmeas:Measurements>
<mikmeas:AnalogValue xsi:type="mikmeas:AnalogValue">
<mikmeas:mRID>_4ce8c346fac34956ab5ce16195d31470</mikmeas:mRID>
<mikmeas:timeStamp>2016-08-24T10:24:24+03:00</mikmeas:timeStamp>
<mikmeas:MeasurementValueQuality ref="8589934593"/>
<mikmeas:value>15.6940002</mikmeas:value>
</mikmeas:AnalogValue>
<mikmeas:mRID>_d6f0cde9666d43b7ab7388e867464158</mikmeas:mRID>
94 | 130
PROJECT
<mikmeas:mRID>_4ce8c346fac34956ab5ce16195d31470</mikmeas:mRID>
<mikmeas:mRID>_d6f0cde9666d43b7ab7388e867464158</mikmeas:mRID>
</mikmeas:Measurements>
</iecmeas:Payload>
</iecmeas:ChangedMeasurements>
</ksdrmeasxsd:DataArea>
</ksdrmeasxsd:ChangedMeasurements>
</SOAP-ENV:Body>
FIGURE 60 MESSAGE FOR SENDING MEASUREMENTS
Figure 61 shows an example of message Createcommands. With this message, SCADA system sends a
control request to the DMS system.
<SOAP-ENV:Body>
<ksdexcomxsd:CreateCommands xsi:type="ksdexcomxsd:CreateCommands_Type">
<ksdxsdupgrid:ApplicationArea>
<ksdxsdupgrid:Sender>
<ksdxsdupgrid:LogicalId>a</ksdxsdupgrid:LogicalId>
<ksdxsdupgrid:Component>b</ksdxsdupgrid:Component>
<ksdxsdupgrid:Task/>
<ksdxsdupgrid:ReferenceId>A26</ksdxsdupgrid:ReferenceId>
<ksdxsdupgrid:Confirmation>1</ksdxsdupgrid:Confirmation>
</ksdxsdupgrid:Sender>
<ksdxsdupgrid:CreationDateTime>2016-10-25T15:07:36+02:00</ksdxsdupgrid:CreationDateTime>
<ksdxsdupgrid:BODId>A26</ksdxsdupgrid:BODId>
</ksdxsdupgrid:ApplicationArea>
<ksdexcomxsd:DataArea>
<ieccommsg:CreateCommands>
<ieccommsg:Header>
<iecmessageupgrid:Verb>create</iecmessageupgrid:Verb>
<iecmessageupgrid:Noun>Commands</iecmessageupgrid:Noun>
<iecmessageupgrid:Timestamp>2016-10-25T15:07:36+02:00</iecmessageupgrid:Timestamp>
<iecmessageupgrid:MessageID>A26</iecmessageupgrid:MessageID>
</ieccommsg:Header>
<ieccommsg:Payload>
<mikcom:Commands>
<mikcom:Command xsi:type="mikcom:Command">
<mikcom:mRID>_56efb501628f4e6f9f1e10384d2e54aa</mikcom:mRID>
<mikcom:timeStamp>2016-10-25T15:07:36+02:00</mikcom:timeStamp>
<mikcom:value>2</mikcom:value>
</mikcom:Command>
</mikcom:Commands>
95 | 130
PROJECT
</ieccommsg:Payload>
</ieccommsg:CreateCommands>
</ksdexcomxsd:DataArea>
</ksdexcomxsd:CreateCommands>
</SOAP-ENV:Body>
FIGURE 61 MESSAGE FOR SENDING COMMANDS
96 | 130
PROJECT
6. PRACTICAL GUIDELINE FOR USING THE CIM

The experience and the lessons learned about using the CIM in WP2 and the deployment of the CIM in
the demos has generated the following practical guideline:
 First step: study the CIM with an open mind view. The CIM is the beginning for developing new
applications and for guarantying the compatibility with future applications. Many electrical
engineers see the power system data as a set parameter tables, with many relationships
between them that the expert only knows. The goal of the CIM is to explicit these relationships
in a way than both experts and computers around the world can manage. It’s important to know
in the first approach that the CIM is more than a new format for expressing the data. The CIM
permits a unified view of topology, functional, asset, maintenance, graphics, etc., of the power
systems, ready for growing up, for being deployed for many manufactures and for supporting
new intelligent algorithms. And if the standard CIM classes do not support a specific
requirement, the CIM model has a method for solving using the class extension. The added
classes could be easily transformed to the future standard classes thanks to the RDF language.
 Second step: select between the CIM RDF XML format and the CIM XML format or both for
communicating applications. The CIM RDF XML format is recommended in the case of deploying
a new system that covers electrical view, asset view, SCADA graphics, power flow analysis, etc.
Although the CIM only specifies interfaces between applications, it is recommended that the
development of the kernel of this new system uses the CIM modelling and the RDF triple
philosophy. So, future new classes or new relationships between classes could be added in a
smooth way. For example, if in the future is necessary to add new parameters for defining the
behavior of the power transformer, the attributes could be added without affecting the existing
applications using a class that inherits from the existing standard Power Transformer class. The
CIM XML format is used when a simple set of information as meter readings, assets data, etc.,
needs to be transferred from one to other application.
 Third step in the case of the CIM RDF XML format: select the set of classes that are going to be
implemented. Before defining a new class, it is necessary to try to reuse the existing classes.
Perhaps, this one of the main problem of using the CIM: a lot of flexibility combined with a not
easy way for discovering the relations between classes and the real attributes that a class has.
There is a lack in the market about tools that permit electric engineers using the CIM without a
deep knowledge about object oriented modelling.
 Third step in the case of the CIM XML format: select the set of XML schemas that are going to be
used. As in the case of the CIM RDF XML, before generating new schemas is necessary to take
advantage of the powerful set of schemas defined by IEC 61968 series. Don’t mind about the size
of the XML documents, the use of compression solves the issue without the need of using
complex and non-scalar binary formats or similar.
97 | 130
PROJECT
7. CONCLUSIONS
This document has proved that the CIM technology is a mature technology, although there are some
aspects that must be improved.
The CIM has provided a common language to the project. From the point of the demos and from the
point of view of the component development, the CIM has established a common vocabulary and a
common knowledge of the distribution power systems. This is important because the electrical
distribution systems have historically followed different development in each country. For instance,
names are different due to the country language. Another example: the document has proved that the
use of the CIM facilitates the comparison of the solutions (solutions more centred in the asset view,
more centred in the meter view, more centred in the electrical view, etc.). Also, this common view has
facilitated the definition of the WP2 component interfaces in order to be deployed in different demos.
Another aspect where the CIM has shown its power is the adaptability to the particular requirements
without losing the essence. It is the case of using CIM at the Spanish demo and at the Swedish demo for
feeding the LVNMS with data from different databases. Both LVNMSs use the CIM as input file format.
Although both LVNMSs has been provided by the same company, GE, the data requirements of each
demo were different. The Spanish demo is more centred in the consumer profile, and the Swedish demo
in the electrical part. Also, the tools that get the information from the databases have different
limitations. Both cases have been successfully solved using CIM. In the case of the Spanish demo it was
necessary to extend the CIM model with the mechanisms that the own CIM provides. The Swedish demo
did not need extensions. Furthermore, an alternative to the Spanish CIM profile has been designed for
limiting the use of new classes. Some engineers have complaints about this flexibility because they think
that the different solutions are not compatible. It is an error. First, the different versions or profiles
share more than 80% of the classes; second, new classes are really not new classes because frequently
they inherit the majority of their attributes from existing classes; third, it is impossible to have an
electrical model that records the present and future requirements of the electrical networks. The
advantage of using CIM is not only the complete model of the current electrical networks, but also the
ability to model future requirements and to establish relationships between different models. The base
of the CIM model is the semantic web techniques as ontologies, ontology alignment, or automatic
reasoning, that brings powerful tools for modelling and translating.
This document has also displayed some disadvantages of working with the CIM. The main one is the
development of CIM solutions using only as input the IEC standard documents (PDF documents that
cannot be copied). The IEC must provide the codes of the models as the UML models or the CIM XML
schemas. Another negative aspect is the learning curve of the CIM model. The model is fractioned in
hundreds of classes with many relationships between classes. New tools are necessary that permit an
engineer with a non-deep object oriented programming background to deal with this issue.
98 | 130
PROJECT
REFERENCES
UPGRID DOCUMENTS
[1] D1.3 - Report on standards and potential synergies WP1 UPGRID project. 2015.
[2] D2.6 - Software of Load and Generation Forecasting. 2016.
EXTERNAL DOCUMENTS
[3] IEC 61970-301:2013-12, Energy management system application program interface (EMS-API) – Part
301: Common information model (CIM) base.
[4] IEC 61968-11, Application integration at electric utilities – System interfaces for distribution
management – Part 11: Common information model (CIM) extensions for distribution.
[5] IEC 62325-301, Framework for energy market communications – Part 301: Common information
model (CIM) extensions for markets.
[6] IEC 61968-3:2004, Application integration at electric utilities - System interfaces for distribution
management - Part 3: Interface for network operations.
management - Part 4: Interfaces for records and asset management.
management - Part 6: Interfaces for maintenance and construction.
management - Part 8: Interfaces for customer operations.
[10] IEC 61968-9:2013, Application integration at electric utilities – System interfaces for distribution
management – Part 9: Interfaces for meter reading and control.
[11] IEC 61968-100:2013, Application integration at electric utilities – System interfaces for distribution
management – Part 100: Implementation profiles.
[12] ‘RDF 1.1 Primer’. [Online]. Available: https://www.w3.org/TR/2014/NOTE-rdf11-primer-
20140624/. [Accessed: 31-May-2016].
99 | 130
PROJECT
[13] IEC 61970-501:2006, Energy management system application program interface (EMS-API) - Part
501: Common Information Model Resource Description Framework (CIM RDF) schema.
552: CIM XML Model exchange format.
[15] IEC 62325-451-1:2013, Framework for energy market communications - Part 451-1:
Acknowledgement business process and contextual model for CIM European market.
[16] IEC 62325-451-2:2014, Framework for energy market communications - Part 451-2: Scheduling
business process and contextual model for CIM European market.
[17] IEC 62325-451-3:2014, Framework for energy market communications - Part 451-3: Transmission
capacity allocation business process (explicit or implicit auction) and contextual models for European
market.
[18] IEC 62325-451-4:2014, Framework for energy market communications - Part 451-4: Settlement and
reconciliation business process, contextual and assembly models for European market.
[19] IEC 62325-451-5:2015, Framework for energy market communications - Part 451-5: Problem
statement and status request business processes, contextual and assembly models for European market
[20] IEC 62325-451-6:2016. Framework for energy market communications - Part 451-6: Publication of
information on market, contextual and assembly models for European style market.
[21] IEC 61970-456:2013. Energy management system application program interface (EMS-API) - Part
456: Solved power system state profiles.
[22] Common Information Model Primer: Third Edition, EPRI, Palo Alto, CA, 2015.
453: Diagram layout profile.
[24] IEC 62361-100:2016. Power systems management and associated information exchange -
Interoperability in the long term - Part 100: CIM profiles to XML schema mapping.
[25] C. Ivanov, "The Way to Exchange: What Is the Common Information Model? [Guest Editorial]," in
IEEE Power and Energy Magazine, vol. 14, no. 1, pp. 22-28, Jan.-Feb. 2016.
[26] C. Ivanov, T. Saxton, J. Waight, M. Monti and G. Robinson, "Prescription for Interoperability: Power
System Challenges and Requirements for Interoperable Solutions," in IEEE Power and Energy Magazine,
vol. 14, no. 1, pp. 30-39, Jan.-Feb. 2016.
[27] S. Neumann, F. Wilhoit, M. Goodrich and V. M. Balijepalli, "Everything's Talking to Each Other:
Smart Meters Generate Big Data for Utilities and Customers," in IEEE Power and Energy Magazine, vol.
14, no. 1, pp. 40-47, Jan.-Feb. 2016.
100 | 130
PROJECT
[28] J. Britton, P. Brown, J. Moseley and M. Bunda, "Optimizing Operations with CIM: Today's Grid
Relies on Network Analysis (and a Lot of Data)," in IEEE Power and Energy Magazine, vol. 14, no. 1, pp.
48-57, Jan.-Feb. 2016.
[29] G. R. Gray, J. Simmins, G. Rajappan, G. Ravikumar and S. A. Khaparde, "Making Distribution
Automation Work: Smart Data Is Imperative for Growth," in IEEE Power and Energy Magazine, vol. 14,
no. 1, pp. 58-67, Jan.-Feb. 2016.
[30] L. O. Osterlund et al., "Under the Hood: An Overview of the Common Information Model Data
Exchanges," in IEEE Power and Energy Magazine, vol. 14, no. 1, pp. 68-82, Jan.-Feb. 2016.
[31] M. McGranaghan, D. Houseman, L. Schmitt, F. Cleveland and E. Lambert, "Enabling the Integrated
Grid: Leveraging Data to Integrate Distributed Resources and Customers," in IEEE Power and Energy
Magazine, vol. 14, no. 1, pp. 83-93, Jan.-Feb. 2016.
101 | 130
PROJECT
102 | 130
PROJECT
ANNEXES
103 | 130
PROJECT
ANNEX I MATCHING TABLES BETWEEN COMPONENT DATA

MODEL REQUIREMENTS AND THE CIM
TABLE 19 to TABLE 29 describe the translation of the data requirements gathered in the functionalities
defined in WP2 into the data classes that the CIM model provides. The “CIM class” column indicates the
CIM class that best suits the data requirement. The “CIM attribute” column indicates an attribute inside
the class that represents the data in the case of a simple data requirement. The column “WP2Cs”
indicates the keyword of the WP2 component where the translation is going to be applied. The “CIM
communication mechanism” column indicates the typical CIM mechanism to transmit a set of this kind
of data, using the nomenclature defined in section 2.2:
 CIM RDF XML.
 CIM XML. In this case, the XML schema is indicated.
TABLE 19: PRIMARY SUBSTATION MV DATA

CIM
Nº Data Description CIM class CIM attribute communication WP2Cs
mechanism
Analog S2.1.1-
1 Voltage the transfomers in the primary CIM RDF XML
AnalogValue A
substation.
Measured voltages on the LV side of
Analog S2.1.1-
2 Voltage the transfomers in the primary CIM RDF XML
AnalogValue A
substation.
Measured voltages at other points in Analog S2.1.1-
3 Voltage CIM RDF XML
the primary substation AnalogValue A
Active Analog S2.1.1-
power flow AnalogValue A
the primary substation
5 CIM RDF XML
power flow transformers in the primary AnalogValue A
substation
Analog S2.1.1-
AnalogValue A
primary substation
7 the LV side of the transformers in the CIM RDF XML
power flow AnalogValue A
primary substation
Reactive through the LV side of the Analog S2.1.1-
8 CIM RDF XML
power flow transformers in the primary AnalogValue A
substation
104 | 130
PROJECT
CIM
mechanism
Analog S2.1.1-
9 Current flow LV side of the transformers in the CIM RDF XML
AnalogValue A
primary substation
Discrete S2.1.1-
DiscreteValue A
elements elements
Measured status
Status of
(connected/disconnected) of the Discrete S2.1.1-
11 shunt CIM RDF XML
dynamically controlled shunt DiscreteValue A
capacitor
capacitors
Tap changer Measured position of the Discrete S2.1.1-
12 CIM RDF XML
position dynamically controlled tap changers DiscreteValue A
Date and
time of each Date and time information of the
4 AnalogValue
variable temperature, active and reactive timeStamp CIM RDF XML All
DiscreteValue
(UTC, UNIX power measurement
Timestamp)
TABLE 20: MV FEEDERS DATA

CIM
mechanism
Active Analog
1 each of the MV feeders departing CIM RDF XML S2.1.1-A
power flow AnalogValue
from the primary substation
Reactive through each of the MV feeders Analog
2 CIM RDF XML S2.1.1-A
power flow departing from the primary AnalogValue
substation
Measured current flow through each
Analog
3 Current flow of the MV feeders departing from CIM RDF XML S2.1.1-A
AnalogValue
the primary substation
Discrete
4 switching dynamically controlled switching CIM RDF XML S2.1.1-A
DiscreteValue
elements elements
4
105 | 130
PROJECT
Date and
5 AnalogValue
5 variable temperature, active and reactive timeStamp CIM RDF XML All
DiscreteValue
Timestamp)
TABLE 21: SECONDARY SUBSTATION MV RELATED DATA

CIM
CIM
attribute
mechanism
Analog S2.1.1-
1 Voltage the transformer in the secondary CIM RDF XML
AnalogValue A
substation
S2.1.1-
Active Analog A
power flow AnalogValue S2.1.3-
the secondary substation
B
3 CIM RDF XML
power flow transformers in the secondary AnalogValue A
substation
Analog S2.1.1-
AnalogValue A
Active Forecasted active power at Analog
5 CIM RDF XML
Reactive Forecasted active power at Analog
6 CIM RDF XML
Discrete S2.1.1-
DiscreteValue A
elements elements
Date and
6 AnalogValue
8 variable temperature, active and reactive timeStamp CIM RDF XML All
DiscreteValue
Timestamp)
5
6
106 | 130
PROJECT
TABLE 22: SECONDARY SUBSTATION LV RELATED DATA

CIM
CIM
attribute
mechanism
S2.1.1-
Measured voltage at the LV side of A
Analog
1 Voltage the transformer in the secondary CIM RDF XML S2.1.3-
AnalogValue
substation A
WP8
S2.1.1-
Measured active power flow
A
Active power through the LV side of the Analog
2 CIM RDF XML S2.1.3-
flow transformers in the secondary AnalogValue
A
substation
S2.2.2
S2.1.1-
A
Reactive power through the LV side of the Analog
3 CIM RDF XML S2.1.3-
flow transformers in the secondary AnalogValue
A
substation
S2.2.2
Analog S2.1.1-
4 Current flow LV side of the transformers in the CIM RDF XML
AnalogValue A
Forecasted active power at Analog
Active power
secondary substation for those AnalogValue S2.1.1-
5 demand CIM RDF XML
substations with no measurements MeasurementV A
forecast
available alueSource
Forecasted active power at Analog
Reactive power
secondary substation for those AnalogValue S2.1.1-
6 demand CIM RDF XML
substations with no measurements MeasurementV A
forecast
available alueSource
S2.1.1-
B
S2.1.2
Measured single-phase voltages at Analog S2.1.3-
7 Phase Voltages CIM RDF XML
the secondary substation AnalogValue A
S2.1.4
S2.1.3-
B
S2.1.1-
B
Active Power Measured active power flow per Analog
8 CIM RDF XML WP8
Flow phase at the secondary substation AnalogValue
S2.1.3-
B
107 | 130
PROJECT
S2.1.1-
B
Reactive Power Measured reactive power flow per Analog
9 CIM RDF XML WP8
Flow phase at the secondary substation AnalogValue
S2.1.3-
B
Measured current per phase at the Analog
10 Current CIM RDF XML S2.1.4
secondary substation AnalogValue
CIM RDF XML
Smart meter
Detection of online, offline and CIM XML:
11 communication ComMedia status S2.1.4
inactive smart meters. EndDeviceEvents
status
.xsd
Date and time
CIM RDF XML
of each Date and time information of the
7 AnalogValue CIM XML: All
12 variable (UTC, temperature, active and reactive timeStamp
DiscreteValue EndDeviceEvents WP8
UNIX power measurement
.xsd
Timestamp)
Secondary
mRID S2.1.3-
Substation (LV Identification information of the LV
13 IdentifiedObject name CIM RDF XML A
node) name node
WP8
and code
Alternative
Geographical data (utm coordinates Alternative 1:
Secondary 1: S2.1.3-
or other geographic information) to Location
14 Substation geoInfoRef CIM RDF XML A
obtain adequate weather Alternative
Coordinates erence WP8
information 2:PositionPoint
Type of S2.1.3-
Urban (U), concentrated rural (CR),
15 Secondary Asset type CIM RDF XML A
disperse rural (DR)
Substation WP8
Electrical
characteristics
TransformerEnd S2.1.3-
16 of the Nominal power ratedS
Info A
secondary
substations
This value must
be calculated
Number of from the
clients number of
Number of clients at the S2.1.3-
17 downstream of objects of the CIM RDF XML
transformation centre A
each secondary class type Meter
substation associated to a
secondary
substation
7
108 | 130
PROJECT
TABLE 23: LV FEEDERS RELATED DATA

CIM
CIM
attribute
mechanism
Measured active power flow per phase
1 in the LV feeder(s) of the secondary CIM RDF XML
Power Flow AnalogValue B
substation
Measured reactive power flow per
Reactive Analog S2.1.1-
2 phase in the LV feeder(s) of the CIM RDF XML
Power Flow AnalogValue B
Date and
8 AnalogValue
3 variable temperature, active and reactive power timeStamp CIM RDF XML All
DiscreteValue
(UTC, UNIX measurement
Timestamp)
TABLE 24: LV CABINETS RELATED DATA

CIM
CIM
Nº Data Description CIM class communicatio WP2Cs
attribute
n mechanism
S2.1.1-
B
Measured single-phase voltages at Analog S2.1.2
1 Phase Voltages CIM RDF XML
the LV cabinets AnalogValue S2.1.4
S2.1.3-
B
S2.1.1-
Active Power
Measured active power flow per Analog B
2 Flow CIM RDF XML
phase at the LV cabinets AnalogValue S2.1.3-
B
S2.1.1-
Reactive Power Measured reactive power flow per Analog B
3 CIM RDF XML
Flow phase at the LV cabinets AnalogValue S2.1.3-
B
Measured current per phase at the LV Analog
4 Current CIM RDF XML S2.1.4
cabinets AnalogValue
CIM RDF XML
Smart meter
Detection of online, offline and CIM XML:
5 communication ComMedia status S2.1.4
inactive smart meters. EndDeviceEve
status
nts.xsd
8
109 | 130
PROJECT
Date and time

CIM RDF XML
of each Date and time information of the
9 AnalogValue timeSta CIM XML:
6 variable (UTC, temperature, active and reactive All
DiscreteValue mp EndDeviceEve
UNIX power measurement
nts.xsd
Timestamp)
TABLE 25: CUSTOMER SMART METERS RELATED DATA

N CIM communication
Data Description CIM class CIM attribute WP2Cs
º mechanism
Measured
S2.1.1
Active active power
S2.1.3-
power at end user CIM XML:
1 MeterReading A
demand connection MeterReadings.xsd
S2.2.2
(kW) point per
WP8
phase
Measured
reactive S2.1.1
Reactive
power at end S2.1.3-
power CIM XML:
2 user MeterReading A
demand MeterReadings.xsd
connection S2.2.2
(kW)
point per WP8
phase
Power
Prosumer’s S2.1.3-
generation CIM XML:
3 generation MeterReading A
from the MeterReadings.xsd
(kW) WP8
client side
Demand
profile for the
consumers in
the group for
each day type
Total considered.
ReadingQualityType. CIM XML:
4 demand The day type MeterReading S2.2.1
category= Projected MeterReadings.xsd
profile might be a
combination
of season and
workday/
weekend/
holiday
9
110 | 130
PROJECT
N CIM communication
º mechanism
This value must be
calculated from
Number of
the number of
Number of consumers CIM XML:
5 objects of the class S2.2.1
Consumers belonging to UsagePointGroups.xsd
type UsagePoint
the group
associated to a
UsagePointGroup
Price profile
Electricity charged for CIM XML:
6 Tariff S2.2.1
Tariff the consumed PricingStructureConfig.xsd
electricity
Forecasted
active power
at end user
Active
connection S2.1.1
power ReadingQualityType. CIM XML:
7 point per MeterReading S2.1.3-
demand category= Estimated MeterReadings.xsd
phase if no B
forecast
real
measurement
s are available
Smart Meter Identification
S2.1.3-
(LV node) information of CIM XML:
8 MeterReading mRID A
name and the Smart MeterConfig.xsd
WP8
code Meter
Smart Meter ID of the
S2.1.3-
(LV node) upstream CIM XML:
9 TransformerTank mRID A
name and Secondary UsagePointConfig.xsd
WP8
code Substation
Geographical
data (utm
coordinates or
Geographica other
CIM XML:
l location of geographic UsagePointLocatio
10 UsagePointLocationConfig.xs S2.1.3
the Smart information) n
d
Meter to obtain
adequate
weather
information
111 | 130
PROJECT
N CIM communication
º mechanism
kW
Maximum S2.1.3
power in the S2.1.3-
Contracted Consumer and A
CIM XML:
11 Power of Producer UsagePoint ratedPower S2.1.3.
UsagePointConfig.xsd
Prosumer contract. B
Mean and S2.2.1
variance WP8
values
S2.1.3-
Nominal nominalServiceVoltag CIM XML:
12 380V, 230V UsagePoint A
Voltage level e UsagePointConfig.xsd
WP8
Urban (U),
Location concentrated
13 type of the rural (CR), S2.1.3
Smart Meter disperse rural
(DR)
S2.1.1.
B
Measured
Phase CIM XML: S2.1.2.
14 single-phase MeterReading
Voltages MeterReadings.xsd S2.1.4
voltages
S2.1.3.
B
Measured
Active S.1.1.B
active power CIM XML:
15 Power Flow MeterReading S2.1.3.
flow per MeterReadings.xsd
B
phase
Measured
S.1.2
Reactive reactive CIM XML:
16 MeterReading S2.1.3.
Power Flow power flow MeterReadings.xsd
B
per phase
Status of the
CIM XML:
17 ICP status internal UsagePoint connectionState S2.1.4
UsagePointConfig.xsd
switch
112 | 130
PROJECT
N CIM communication
º mechanism
Date and time
information of
Date and
the
time of each
10 temperature, CIM XML: All
18 variable MeterReading timeStamp
active and MeterReadings.xsd WP8
(UTC, UNIX
reactive
Timestamp)
power
measurement
If the suggested classes in TABLE 26 are not enough, the CIM model should be extended.
TABLE 26: CONSUMPTION/GENERATION PATTERNS AND HOME EQUIPMENT RELATED DATA

CIM communication
mechanism
Air conditioning
and heating PanDemandResponse avgLoadAdjustment CIM XML: S2.1.3-
1 --
consumption* (it uses %) EndDeviceControl.xsd A
(kWh/year)
Hot water
PanDemandResponse avgLoadAdjustment CIM XML: S2.1.3-
2 consumption* --
(it uses %) EndDeviceControl.xsd A
(kWh/year)
Thermal
collectors PanDemandResponse avgLoadAdjustment CIM XML: S2.1.3-
3 --
installed* (it uses %) EndDeviceControl.xsd A
(kWh/year).
Type of air
conditioning*:
Heat pump
(HP), electric
PanDemandResponse CIM XML: S2.1.3-
4 heaters (H), -- appliance
EndDeviceControl.xsd A
Boiler (B),
Cooling system
(AC), Thermal
collectors (TC)
kWh/hour or S2.1.3-
PanDemandResponse CIM XML:
5 Energy stored kWh/year or appliance A
EndDeviceControl.xsd
kWh/…). WP8
10
113 | 130
PROJECT
CIM communication
mechanism
Time flexibility
End-user
characterized by CIM XML: S2.2.1-
6 preferences: EndDeviceControl scheduledInterval
the duration, start EndDeviceControl.xsd B
Time flexibility
and end time
Price band where
End user
the user is CIM XML: S2.2.1-
7 preferences: PanPricingDetail
available for EndDeviceControl.xsd B
price thresholds
control
Maximum and
minimum power
Band of comfort ReadingQualityType. CIM XML: S2.2.1-
8 consumption the MeterReading
levels category= Projected MeterReadings.xsd B
user is available
for control
Technical
Smart Plug characteristics of PanDemandResponse CIM XML: S2.2.1-
9 appliance
rated power the appliances EndDeviceControl.xsd B
with smart plugs
Penetration
percentage of
each shiftable
PanDemandResponse avgLoadAdjustment CIM XML:
10 Shiftable loads load type: 1) S2.2.1
(it uses %) EndDeviceControl.xsd
washing machine,
2) dishwasher,
3)dryer
Power profile of
Power profile of ReadingQualityType. CIM XML:
11 each shiftable MeterReading S2.2.1
shiftable loads category= Projected MeterReadings.xsd
load type
The probability
profile of the end
Start time
user to switch on PanDemandResponse CIM XML:
12 likelihood of startDateTime S2.2.1
the considered EndDeviceControl.xsd
shiftable loads
device at each
time step.
Penetration
percentage of
each thermal load PanDemandResponse avgLoadAdjustment CIM XML:
13 Thermal load S2.2.1
type: 1) air- (it uses %) EndDeviceControl.xsd
conditioner, 2)
space-heater
Power for each
Nominal power thermal load type. ReadingQualityType. CIM XML:
14 MeterReading S2.2.1
of thermal loads Mean and category= Projected MeterReadings.xsd
variance values
114 | 130
PROJECT
CIM communication
mechanism
Cooling efficiency
(EER) and heating
efficiency (COP)
indicating the
ratio of cooling or
heating provided
Efficiency of MeterReading ReadingQualityType. CIM XML:
15 by a unit relative S2.2.1
thermal loads (new reading type) category= Projected MeterReadings.xsd
to the amount of
electrical input
required to
generate it. Mean
and variance
values.
Temperature set
Comfort
point for each
temperature set MeterReading ReadingQualityType. CIM XML:
16 thermal device S2.2.1
point of thermal category= Projected MeterReadings.xsd
type. Mean and
loads
variance values
Outdoor Outdoor
MeterReading ReadingQualityType. CIM XML:
17 temperature temperature S2.2.1
category= Projected MeterReadings.xsd
profile profile.
Size of the
household
Building type (square MeterReading ReadingQualityType. CIM XML:
18 S2.2.1
(size) meters).Mean (new reading type) category= Projected MeterReadings.xsd
and variance
values.
Percentage of
buildings
belonging to each
building type: 1)
old, un-insulated,
2) old, insulated,
3) old,
Building type MeterReading ReadingQualityType. CIM XML:
19 weatherized, 4) S2.2.1
(insulation) (new reading type) category= Projected MeterReadings.xsd
old, retrofit
upgraded, 5)
moderately
insulated, 6) very
well insulated, 7)
extremely well
insulated.
115 | 130
PROJECT
CIM communication
mechanism
Date and time
Date and time
information of the
of each
11 temperature, CIM XML:
20 variable (UTC, MeterReading timeStamp All
active and MeterReadings.xsd
UNIX
reactive power
Timestamp)
measurement
TABLE 27: MV STATIC DATA

CIM
CIM
Number Data Description CIM class communication WP2Cs
attribute
mechanism
Electrical Impedance and length of
1 characteristics of the line segments in the ACLineSegment CIM RDF XML S2.1.1-A
lines network
Electrical Impedance at the high
2 characteristics of and low voltage sides and PowerTransformer CIM RDF XML S2.1.1-A
transformers transformation ratio
Electrical Shunt impedance/
3 characteristics of reactive power injection ShuntCompensator CIM RDF XML S2.1.1-A
shunt capacitors of the capacitor bank
Connectivity of the lines,
Terminal
4 Network topology transformers and shunt CIM RDF XML S2.1.1-A
ConnectivityNode
capacitors
CIM model distinguishes between UsagePoint and Consumer. A consumer could manage more than one
UsagePoints and its main role is business.
TABLE 28: LV STATIC DATA

CIM CIM communication
Number Data Description CIM class WP2Cs
attribute mechanism
Connection of S2.1.2
Connectivity of end users Transform CIM XML:
1 end users per mRID S2.1.4
to phases and feeders erTank UsagePointConfig.xsd
phase S2.2.3
S2.1.1-B
Geographical Coordinates of the CIM XML: S2.1.2
UsagePoin
2 location of grid’s consumers or network UsagePointLocationCo S2.1.3
tLocation
equipment area nfig.xsd S2.1.4
S2.2.3
11
116 | 130
PROJECT
Grid’s equipment Status of the grid status S2.1.1-B

3 current operation equipment and other Asset CIM RDF XML S2.1.2
status controllable devices S2.1.4
DSO special
Customer CIM XML:
contracts with Identification of resources
4 Agreemen CustomerAgreementC S2.1.2
consumers and controlled by the DSO
t onfig.xsd
producers
DiscreteVa value
S2.1.2
Information about the lue
5 Grid topology CIM RDF XML S2.1.3
current network topology (switch
S2.1.4
positions)
Technical Maximum and minimum
Operation
6 characteristics of power of controllable CIM RDF XML S2.1.2
alLimits
grids equipment equipment
List of priority considering
DSO merit order the type of equipment to
ControlAr
7 of equipment control (Tap changer, CIM RDF XML S2.1.2
ea
actuation Storage, microgeneration,
loads)
Detailed database Matched to the related SS
of LV network and from the point of view CIM XML:
8 Customer S2.1.5
customers of the Maintenance and CustomerConfig.xsd
available repairment activities.
Geographical location of
the asset
Asset characteristics:
- Number
- Technical
characteristics of the
asset
- Manufacturer
- Installation or
replacement date
Detailed database
- Last inspection date
9 of LV network Asset CIM RDF XML S2.1.5
Asset reliability:
assets available
- Types of failure
- Failure rate
Average time required to
repair asset
- Average fault location
time
- Average fault location
arrival time
- Average fault repair
time
117 | 130
PROJECT
Average times of arriving geoInfoRef

Geographic from crew site location to erence CIM RDF XML
information of different points of (CIM XML:
10 the LV networks, network. Location UsagePointLocationCo S2.1.5
linked with the Distances from crew site nfig.xsd for
assets location to different points customers)
of network.
Geographical location of
the crew
- Number of operators
forming each crew
- Technical qualification
Maintenance/rep of the team personnel
air crews location - Number of vehicles
11 Crew CIM RDF XML S2.1.5
at specific sites in - Technical
the LV network characteristics
- Age
Available crew material
resources as cranes and
tools for specific fault
repair tasks
Indicates the probability of
Fault Location fault occurrence and S2.1.4
12 Asset CIM RDF XML
Service identifies the probable S2.1.5
location.
The minimum information
required is:
 Timestamp (UTC, Unix
timestamp).
 Duration (s).
 Customers affected
(ID).
 Components involved
(description of
List of historical components).
13 faults registered  Fault cause and failure Incident CIM RDF XML WP8
per demo area mode (description).
 Any other information
useful and available in
the characterization of
the faults.
 Time for fault location
and isolation (s).
 Possible economic
impact of energy does
not supply.
118 | 130
PROJECT
TABLE 29: OUTPUT DATA OF EXISTING STATE ESTIMATOR

CIM CIM communication WP2Cs
Number Data Description CIM class
attribute mechanism
Estimated voltages at the S2.2.1
1 Voltage SvVoltage v CIM RDF XML
network nodes
Estimated voltage S2.2.1
2 Voltage angle SvVoltage angle CIM RDF XML
angles at the network nodes
Estimated currents at the Analog S2.2.1
3 Current CIM RDF XML
network branches AnalogValue
Estimated current S2.2.1
Analog
4 Current angle angles at the network CIM RDF XML
AnalogValue
branches
Active power Estimated active power flows S2.2.1
5 SvPowerFlow P CIM RDF XML
flow at the network branches
Reactive power Estimated reactive power S2.2.1
6 SvPowerFlow q CIM RDF XML
flow flows at the network branches
Estimated active power S2.2.1
Active power
7 injections at the network SvInjection pInjection CIM RDF XML
demand
branches
Estimated reactive power S2.2.1
Reactive power
8 injections at the network SvInjection qInjection CIM RDF XML
demand
branches
Difference between the S2.2.1
Estimation By
9 estimated values and
errors calculation
measured values
119 | 130
PROJECT
ANNEX II CIM XML RDF EXAMPLE OF A LOW VOLTAGE

DISTRIBUTION NETWORK IN THE SPANISH EXAMPLE
<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<rdf:RDF xmlns:dm="http://iec.ch/2002/schema/CIM_difference_model#" xmlns:cim="http://iec.ch/TC57/2010/CIM-
schema-cim15#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">



<cim:Substation rdf:about="#_CTD200004790">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_CTD"/>
</cim:Substation>

<cim:Asset rdf:about="#_ASSET_CTD200004790">
<cim:IdentifiedObject.name>LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790"/>
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_CTD"/>
<cim:Asset.Location rdf:resource="#_SERVICELOCATION_CTD200004790"/>
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CTD200004790"/>
</cim:Asset>

<cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790">
<cim:IdentifiedObject.name>CTD</cim:IdentifiedObject.name>
<cim:ProductAssetModel.modelNumber>CONVENCIONAL</cim:ProductAssetModel.modelNumber>

<cim:ServiceLocation rdf:about="#_SERVICELOCATION_CTD200004790">
<cim:mainAddress>
<cim:townDetail>
</cim:townDetail>
<cim:streetDetail>
<cim:streetDetail.addressGeneral>ENTRAD POR
BERASTE</cim:streetDetail.addressGeneral>
</cim:streetDetail>
</cim:mainAddress>
120 | 130
PROJECT
<cim:Location.type>EDIFICIO SOTANO</cim:Location.type>
<cim:ServiceLocation.accessMethod>CAJETIN CON LLAVES DEL PORTAL, EN EL PORTAL HAY OTRO
CAJETIN CON LLAVE DE ACCESO)</cim:ServiceLocation.accessMethod>








<cim:VoltageLevel rdf:about="#_CTD200004790_VOLTAGELEVEL_13200">
<cim:IdentifiedObject.name>CONJUNTO CELDAS AT (13200 V)</cim:IdentifiedObject.name>
<cim:VoltageLevel.BaseVoltage rdf:resource="#_BaseVoltage_13200"/>
<cim:VoltageLevel.Substation rdf:resource="#_CTD200004790"/>
</cim:VoltageLevel>

<cim:VoltageLevel rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1">
<cim:IdentifiedObject.name>BAJA TENSIÓN 1</cim:IdentifiedObject.name>
</cim:VoltageLevel>

<cim:VoltageLevel rdf:about="#_CTD200004790_VOLTAGELEVEL_400_2">
<cim:IdentifiedObject.name>BAJA TENSIÓN 2</cim:IdentifiedObject.name>
</cim:VoltageLevel>








<cim:Bay rdf:about="#_CTD200004790_BAY_1">
<cim:IdentifiedObject.name>CELDA1</cim:IdentifiedObject.name>
<cim:Bay.Substation rdf:resource="#_CTD200004790"/>
<cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/>
</cim:Bay>

</cim:Bay>

</cim:Bay>

121 | 130
PROJECT
</cim:Bay>

</cim:Bay>








<cim:PowerTransformer rdf:about="#_CTD200004790_TR1">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVTRANSFORMER"/>
<cim:PowerTransformer.vectorGroup>DYn11</cim:PowerTransformer.vectorGroup>

<cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_AT">
<cim:PowerTransformerEnd.ratedS>
<cim:ratedS>
<cim:ratedS.value>630</cim:ratedS.value>
<cim:ratedS.multiplier>k</cim:ratedS.multiplier>
</cim:ratedS>
</cim:PowerTransformerEnd.ratedS>
<cim:TransformerEnd.RatioTapChanger rdf:resource="#_CTD200004790_TR1_AT_TAPCHANGER"/>

<cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_BT">

<cim:RatioTapChanger rdf:about="#_CTD200004790_TR1_AT_TAPCHANGER">
<cim:RatioTapChanger.highStep>5</cim:RatioTapChanger.highStep>
<cim:RatioTapChanger.lowStep>1</cim:RatioTapChanger.lowStep>
<cim:RatioTapChanger.neutralStep>1</cim:RatioTapChanger.neutralStep>
<cim:TapChanger.neutralU>13200</cim:TapChanger.neutralU>
<cim:RatioTapChanger.step>5</cim:RatioTapChanger.step>
<cim:RatioTapChanger.stepVoltageIncrement>2.5</cim:RatioTapChanger.stepVoltageIncrement>
</cim:RatioTapChanger>

122 | 130
PROJECT
<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_BAY_AT_TR1_OUT"/>
</cim:Terminal>

<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_VOLTAGELEVEL_400_1_IN"/>
</cim:Terminal>

<cim:Asset rdf:about="#_ASSET_CTD200004790_TR1">
<cim:IdentifiedObject.name>TRAFO 1 LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_TR1"/>
<cim:Asset.serialNumber>136457</cim:Asset.serialNumber>
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_TR"/>
<cim:IdentifiedObject.name>INVENTARIO TRAFO 1 LEDESMA LEKERIKA</cim:IdentifiedObject.name>
<cim:Asset.type>TRANSFORMADOR DE DISTRIBUCIÓN DE BAJA TENSIÓN</cim:Asset.type>
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CTD200004790_TR1"/>
</cim:Asset>

<cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790_TR1">
<cim:ProductAssetModel.modelNumber>INTERIOR</cim:ProductAssetModel.modelNumber>





<cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_IN">
<cim:ConnectivityNode.ConnectivityNodeContainer
rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/>
</cim:ConnectivityNode>




<cim:Disconnector rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1">
<cim:IdentifiedObject.name>SECCIONADOR SALIDA TRAFO 1</cim:IdentifiedObject.name>
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVTRANSFORMER_DISCONNECTOR"/>
</cim:Disconnector>
<cim:Terminal.ConnectivityNode rdf:resource="#__CN_CTD200004790_VOLTAGELEVEL_400_1_IN"/>
<cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_D1"/>
</cim:Terminal>
<cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_D1"/>
</cim:Terminal>
123 | 130
PROJECT





<cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR">




<cim:BusbarSection rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR">
<cim:IdentifiedObject.name>BARRA DE BAJA TRAFO 1</cim:IdentifiedObject.name>
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVBUSBAR"/>
</cim:BusbarSection>
<cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR_T1">
rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR"/>
</cim:Terminal>







<cim:Fuse rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_F_1">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVFUSE"/>
<cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_BAY_1"/>
</cim:Fuse>

<cim:Asset rdf:about="#_ASSET_CTD200004790_VOLTAGELEVEL_400_1_F_1">
<cim:IdentifiedObject.name>FUSIBLE LINEA 1</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/>
<cim:Asset.SwitchInfo rdf:resource="#_FUSEINFO_TYPE1"/>
</cim:Asset>

</cim:Terminal>

124 | 130
PROJECT
</cim:Terminal>





<cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_1">




<cim:Line rdf:about="#_CTD200004790_VOLTAGELEVEL_400_LINE_1">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVLINE"/>
</cim:Line>

<cim:Asset rdf:about="#_ASSET_CTD200004790_LINE_1">
<cim:IdentifiedObject.name>LINEA 1</cim:IdentifiedObject.name>
<cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1"/>
</cim:Asset>

<cim:ACLineSegment rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1">
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVSEGMENT"/>

<cim:Asset rdf:about="#_ASSET_CTD200004790_LINE_1_S1">
<cim:IdentifiedObject.name>SEGMENTO 1</cim:IdentifiedObject.name>
rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1"/>
<cim:Asset.CableInfo rdf:resource="#_CABLEINFO_LINE_TYPE1"/>
</cim:Asset>

<cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1_T1">
</cim:Terminal>
125 | 130
PROJECT
</cim:Terminal>

rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/>

<cim:ACLineSegment rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2">
<cim:PowerSystemResource.PSRType rdf:resource="#_PSRTYPE_LVSEGMENT"/>

<cim:Asset rdf:about="#_ASSET_CTD200004790_LINE_1_S2">
<cim:IdentifiedObject.name>SEGMENTO 2</cim:IdentifiedObject.name>
<cim:Asset.CableInfo rdf:resource="#_CABLEINFO_LINE_TYPE1"/>
</cim:Asset>
</cim:Terminal>
</cim:Terminal>





rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/>




<cim:EnergyConsumer rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1">
<cim:PowerSystemResource.PSRType rdf:resource="#_PSRTYPE_LVCONSUMERBOX"/>
126 | 130
PROJECT


<cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1_T1">
</cim:Terminal>

<cim:Asset rdf:about="#_ASSET_CAJA_3131739">
<cim:IdentifiedObject.name>CAJA 3131739</cim:IdentifiedObject.name>
<cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_ENERGYCONSUMER"/>
<cim:Asset.Location rdf:resource="#_SERVICELOCATION_CAJA_3131739"/>
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CAJA_3131739"/>
</cim:Asset>

<cim:ServiceLocation rdf:about="#__SERVICELOCATION_CAJA_3131739">
<cim:mainAddress>
<cim:townDetail>
</cim:townDetail>
<cim:streetDetail>
<cim:streetDetail.addressGeneral/>
</cim:streetDetail>
</cim:mainAddress>
<cim:Location.type>PATIO MANZANA</cim:Location.type>
<cim:ServiceLocation.accessMethod>POR VIVIENDA XXX</cim:ServiceLocation.accessMethod>

<cim:Asset rdf:about="#_ASSET_CAJA_3131739_FUSE">
<cim:Asset.IBDFuseInfo rdf:resource="#_FUSEINFO_TYPE2"/>
<cim:Asset.PowerSystemResources>#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1</cim:Asset.P
owerSystemResources>
</cim:Asset>
<cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-
cim17#PhaseCode.ABCN"/>
127 | 130
PROJECT
<cim:UsagePoint.isSdp>true</cim:UsagePoint.isSdp>
<cim:UsagePoint.ratedCurrent>30</cim:UsagePoint.ratedCurrent>
cim17#UsagePointConnectedKind.logicallyDisconnected"/>
</cim:UsagePoint>
<cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.AN"/>
<cim:UsagePoint.isSdp>false</cim:UsagePoint.isSdp>
cim17#UsagePointConnectedKind.connected"/>
</cim:UsagePoint>







<cim:PSRType rdf:about="#_PSRTYPE_CTD">
<cim:IdentifiedObject.name>CENTRO DE TRANSFORMACIÓN DE
DISTRIBUCIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVTRANSFORMER">
<cim:IdentifiedObject.name>TRANSFORMADOR DE CENTRO DE TRANSFORMACIÓN DE
DISTRIBUCIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVTRANSFORMER_DISCONNECTOR">
<cim:IdentifiedObject.name>SECCIONADOR GENERAL BAJA TENSÏON CENTRO DE
TRANSFORMACIÓN DE DISTRIBUCIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVBUSBAR">
<cim:IdentifiedObject.name>BARRA DE CUADRO DE BAJA TENSIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVFUSE">
<cim:IdentifiedObject.name>FUSIBLE CABECERA LINEA DE BAJA TENSÏON</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVSEGMENT">
<cim:IdentifiedObject.name>SEGMENTO DE LINEA DE BAJA TENSIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LV_LINE">
<cim:IdentifiedObject.name>LINEA DE BAJA TENSIÓN</cim:IdentifiedObject.name>
</cim:PSRType>
<cim:PSRType rdf:about="#_PSRTYPE_LVCONSUMERBOX">
<cim:IdentifiedObject.name>CAJA GENERAL</cim:IdentifiedObject.name>
</cim:PSRType>





128 | 130
PROJECT




<cim:BaseVoltage rdf:about="#_BaseVoltage_230">
<cim:BaseVoltage.nominalVoltage>230</cim:BaseVoltage.nominalVoltage>
</cim:BaseVoltage>
</cim:BaseVoltage>
</cim:BaseVoltage>






<cim:Manufacturer rdf:about="#_MANUFACTURER1">
<cim:IdentifiedObject.name>MANUFACTURER 1</cim:IdentifiedObject.name>
</cim:Manufacturer>
<cim:Manufacturer rdf:about="#_MANUFACTURER2">
<cim:IdentifiedObject.name>MANUFACTURER 2</cim:IdentifiedObject.name>
</cim:Manufacturer>







<cim:AssetOwner rdf:about="#_OWNER_IBERDROLA">
<cim:IdentifiedObject.name>Iberdrola</cim:IdentifiedObject.name>
</cim:AssetOwner>
<cim:Ownership rdf:about="#_OWNERSHIP_100_IBERDROLA">
<cim:Ownership.share>100</cim:Ownership.share>
<cim:Ownership.AssetOwner rdf:resource="_OWNER_IBERDROLA"/>
</cim:Ownership>




<cim:Crew rdf:about="#_CREW_BRIGADABILBAO">
<cim:IdentifiedObject.name>BRIGADA BILBAO</cim:IdentifiedObject.name>
</cim:Crew>




<cim:AssetInfo rdf:about="#_ASSETINFO_CTD">
<cim:IdentifiedObject.name>CENTRO DE TRANSFORMACIÓN</cim:IdentifiedObject.name>
</cim:AssetInfo>
<cim:AssetInfo rdf:about="#_ASSETINFO_ENERGYCONSUMER">
<cim:IdentifiedObject.name>CENTRO DE TRANSFORMACIÓN</cim:IdentifiedObject.name>
</cim:AssetInfo>
<cim:CableInfo rdf:about="#_CABLEINFO_LINE_TYPE1">
<cim:IdentifiedObject.name>LINEA DE BAJA TENSIÓN DE TIPO1</cim:IdentifiedObject.name>
129 | 130
PROJECT
<cim:WireInfo.diameterOverCore>240</cim:WireInfo.diameterOverCore>
<cim:WireInfo.material>copper</cim:WireInfo.material>
<cim:AssetInfo.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CABLE_TYPE_1"/>
</cim:CableInfo>
<cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CABLE_TYPE_1">
<cim:IdentifiedObject.name>CABLE</cim:IdentifiedObject.name>
<cim:ProductAssetModel.modelNumber>XZ1-AL 1X240</cim:ProductAssetModel.modelNumber>
<cim:usageKind>distributionUnderground</cim:usageKind>
<cim:IBDPowerTransformerInfo rdf:about="#_ASSETINFO_TR">
<cim:IdentifiedObject.name>TRANSFORMADOR DE DISTRIBUCIÓN</cim:IdentifiedObject.name>
<cim:IBDPowerTransformerInfo.refrigerantKind>OIL</cim:IBDPowerTransformerInfo.refrigerantKind>
<cim:IBDPowerTransformerInfo.class>B1B2</cim:IBDPowerTransformerInfo.class>
</cim:IBDPowerTransformerInfo>
<cim:SwitchInfo rdf:about="#_FUSEINFO_TYPE1">
<cim:IdentifiedObject.name>FUSIBLE DE SALIDA 250</cim:IdentifiedObject.name>
<cim:material>copper</cim:material>
</cim:SwitchInfo>
<cim:IBDFuseInfo rdf:about="#_FUSEINFO_TYPE2">
<cim:IdentifiedObject.name>FUSIBLE DE CAJA 125</cim:IdentifiedObject.name>
<cim:IBDFuseInfo.class>GT (FUSION LENTA)</cim:IBDFuseInfo.class>
<cim:IBDFuseInfo.size>PENDIENTE</cim:IBDFuseInfo.size>
</cim:IBDFuseInfo>
</rdf:RDF>
130 | 130

Attachment 0 PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Attachment 0 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Ref.

Real proven solutions to enable active demand and distributed

WP 2 – Innovative Distribution Grid Use

2015 The UPGRID Consortium

PROGRAMME H2020 – Energy Theme

GRANT AGREEMENT NUMBER 646.531

PROJECT ACRONYM UPGRID

TYPE (DISTRIBUTION LEVEL) ☐Public

DUE DELIVERY DATE 31/12/2016

DATE OF DELIVERY 30/12/2016

STATUS AND VERSION V1.2

NUMBER OF PAGES 130

WP / TASK RELATED WP2 / T2.3

WP / TASK RESPONSIBLE COMILLAS

AUTHOR (S) José Antonio Rodríguez Mondéjar (COMILLAS),

PARTNER(S) CONTRIBUTING Vattenfall, GE, Iberdrola, ITE, Energa, IEN, Powel

FILE NAME UPGRID_D2.4 Report on the implementation of

VERS. ISSUE DATE CONTENT AND CHANGES

0.0 1/10/2016 Initial draft with TOC

0.1 1/12/2016 First draft by the partners

1.0 12/12/2016 First version of the document (for official review)

1.2 21/12/2016 Integration of the reviewer comments

EXECUTIVE SUMMARY _________________________________________________________________ 4

2.3 CIM PROFILES _________________________________________________________________________ 23

5.2 SWEDISH DEMO _______________________________________________________________________ 71

6. PRACTICAL GUIDELINE FOR USING THE CIM _____________________________________________ 97

FIGURE 1 EXAMPLE OF CIM CLASSES AND RELATIONSHIPS ........................................................................16

FIGURE 25 RDF XML EXAMPLE OF IBDENERGYCONSUMER ........................................................................56

FIGURE 53 CIM CLASSES FOR FORWARDING FDIR SEQUENCES ..................................................................89

TABLE 25: CUSTOMER SMART METERS RELATED DATA _____________________________________110

ABBREVIATIONS AND ACRONYMS

CIM Common Information Model

DMS Distribution Management System

EMS Energy Management Systems

ENTSO-E European Network of Transmission System Operators for Electricity

EPRI Electric Power Research Institute

FDIR Fault Detection, Isolation & Restoration

GML Geography Markup Language

LVNMS Low Voltage Network Management System

RDF Resource Description Framework

SCADA Supervisory Control and Data Acquisition

SQL Structured Query Language

UML Unified Modelling Language

XML eXtensible Markup Language

2. BRIEF INTRODUCTION TO CIM

2.1 THE CIM MODEL

C onnect i v i t y NodeC ont a i ner

+VoltageLevels 0..* +BaseVoltage 0..1

+Bays 0..* 0..*

FIGURE 1 EXAMPLE OF CIM CLASSES AND RELATIONSHIPS

2.2 COMMUNICATION OF THE CIM DATA

2.2.1 CIM RDF XML

FIGURE 2 BASIC RDF MODEL

FIGURE 3 EXAMPLE OF A CIM RDF TRIPLE

In the case of the CIM, RDF is used in two levels:

FIGURE 5 EXAMPLE OF A DIFFERENCE CIM RDF FILE (SOURCE IEC 61970-552)

2.2.2 CIM XML

FIGURE 7 METER READINGS XML SCHEMA (SOURCE: IEC 61968-9)

 IEC 61968-8: Interface for customer operations.

FIGURE 8 MESSAGE ORGANIZATION (SOURCE: IEC 61968-100)

2.3 CIM PROFILES

+ acceptanceTest: AcceptanceTest [0..1]

FIGURE 10 CLASS ASSET