report on the implementation of the cim as the reference
TRANSCRIPT
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant
agreement No 646.531
Report on the implementation of the CIM as the reference data model for the project
D2.4
2015 The UPGRID Consortium
WP 2 – Innovative Distribution Grid Use
Cases and Functions
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
D.2.1 REPORT ON THE IMPLEMENTATION OF THE CIM AS THE REFERENCE DATA MODEL FOR THE PROJECT
2 | 129
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
STATUS AND VERSION V1.0
NUMBER OF PAGES 129
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 D_2_4 Report on the implementation of the CIM as
the reference data model for the project v1.2
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
3 | 129
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
1.2c 1/12/2017 Deliverable set up as “Public” according to the UPGRID
Amendment 1
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
4 | 129
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 fulfil the
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
5 | 129
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.
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
6 | 129
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 _____________________________________________ 96
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
7 | 129
7. CONCLUSIONS ____________________________________________________________________ 97
REFERENCES ________________________________________________________________________ 98
ANNEX I MATCHING TABLES BETWEEN COMPONENT DATA MODEL REQUIREMENTS AND THE CIM
103
ANNEX II CIM XML RDF EXAMPLE OF A LOW VOLTAGE DISTRIBUTION NETWORK IN THE SPANISH
EXAMPLE 119
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
8 | 129
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
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
9 | 129
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
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
10 | 129
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 ................ 93
FIGURE 60 MESSAGE FOR SENDING MEASUREMENTS ............................................................................... 95
FIGURE 61 MESSAGE FOR SENDING COMMANDS ...................................................................................... 95
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
11 | 129
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 _____________________________________________103
TABLE 20: MV FEEDERS DATA _________________________________________________________104
TABLE 21: SECONDARY SUBSTATION MV RELATED DATA ___________________________________105
TABLE 22: SECONDARY SUBSTATION LV RELATED DATA ____________________________________106
TABLE 23: LV FEEDERS RELATED DATA __________________________________________________108
TABLE 24: LV CABINETS RELATED DATA _________________________________________________108
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
12 | 129
TABLE 25: CUSTOMER SMART METERS RELATED DATA _____________________________________109
TABLE 26: CONSUMPTION/GENERATION PATTERNS AND HOME EQUIPMENT RELATED DATA _____111
TABLE 27: MV STATIC DATA ___________________________________________________________114
TABLE 28: LV STATIC DATA ___________________________________________________________115
TABLE 29: OUTPUT DATA OF EXISTING STATE ESTIMATOR __________________________________117
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
13 | 129
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
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
14 | 129
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.
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
15 | 129
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.
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
16 | 129
FIGURE 1 EXAMPLE OF CIM CLASSES AND RELATIONSHIPS
class Ma in
Bay
Equipment
IdentifiedObject
PSRTy pe
IdentifiedObject
Power Sy stemResour ce
ACDCTerminal
Ter mina l
EquipmentConta iner
IdentifiedObject
BaseVoltage
Connect iv ity NodeConta iner
VoltageLev el
Substa t ion
IdentifiedObject
SubGeogr aphica lRegion
IdentifiedObject
Geogr aphica lRegion
Conduct ingEquipment
+EquipmentContainer
0..1
+Equipments
0..*
+Region 0..1
+Substations 0..*
+BaseVoltage 0..1
+ConductingEquipment
0..*
+Region 0..1
+Regions 0..*
+Bays
0..*
+Substation
0..1
+VoltageLevel
0..* +BaseVoltage 1
+PowerSystemResources
0..*
+PSRType
0..1
+Substation 1
+VoltageLevels 0..*
+VoltageLevel 0..1
+Bays 0..*
+Terminals
0..*
+ConductingEquipment
1
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
17 | 129
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.
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
18 | 129
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:
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
19 | 129
• 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"> <!-- Delete Transformer --> <dm:reverseDifferences rdf:parseType="Statements"> <cim:PowerTransformer rdf:about="#_41bb4445-6756-43fa-9e5a-48B6cd71790e"> <!--…all properties of the transformer follows here…--> </cim:PowerTransformer> <!--…all parts of the transformer follows here….--> </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.
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
20 | 129
<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)
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
21 | 129
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.
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
22 | 129
• 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.
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
23 | 129
<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.
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
24 | 129
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] .
cla ss AssetsOv er v iew
IdentifiedObject
Asset
+ 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]
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
25 | 129
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
• Transport layer for SMs provided data 4-
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
• IP convergence sublayer
PRIME 1.3.6
• 4-32 convergence sub-layer
• SMs profile
SNMPv3 for MIB collection
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)
Used proprietary protocols
Development of new protocols / Development of
extensions to a standard protocol / protocol
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
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
26 | 129
TABLE 2: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE PORTUGUESE DEMO
DEMO BASE DEMO DEVELOPED UNDER UPGRID
Used standard protocols Proposed standard protocols to be used
IEC60870-5-104
• Light Protocol Implementation Document
(LPID) for IEC 60870-5-104 defined by EDP
Distribuição
IEC60870-5-104
• Light Protocol Implementation Document
(LPID) for IEC 60870-5-104 defined by EDP
Distribuição
PRIME
• Version 1.3.6 established by PRIME Alliance
• PRIME MAC & PHY layers (PLC)
• PRIME 4-32 convergence sub-layer
PRIME
• Version 1.3.6 established by PRIME Alliance
• PRIME MAC & PHY layers (PLC)
• PRIME 4-32 convergence sub-layer
DLMS/COSEM
• EDP Box data model – EDP companion for
DLMS/COSEM
DLMS/COSEM
• EDP Box data model – EDP companion for
DLMS/COSEM
Web services SOAP (STG-DC 3.1.c)
• Central System – DTC interface based on DC
INTERFACE SPECIFICATION, v3.1.c, authored by
Iberdrola but currently under the responsibility of
the Prime Alliance
• EDP profile with specific Orders (Bnn) and
Reports (Snn) - WS_STG.DTC_perfil.EDP_v5.13
Web services SOAP (STG-DC 3.1.c)
• Central System – DTC interface based on DC
INTERFACE SPECIFICATION, v3.1.c, authored by
Iberdrola but currently under the responsibility of
the Prime Alliance
• EDP profile with specific Orders (Bnn) and
Reports (Snn) - WS_STG.DTC_perfil.EDP_v5.13
FTP (RFC959) FTP (RFC959)
MODBUS over serial line
• MODBUS APPLICATION PROTOCOL
SPECIFICATION, V1.1b for HAN interface of the
EDP Box
MODBUS over serial line
• MODBUS APPLICATION PROTOCOL
SPECIFICATION, V1.1b for HAN interface of the
EDP Box
Used proprietary protocols
Development of new protocols / Development of
extensions to a standard protocol / protocol
profiles to be developed (and Possible
standardization process)
HAN interface
• Data model and communication protocol for
the HAN interface of the EDP Box
N/A
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
27 | 129
TABLE 3: CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE SWEDISH DEMO
DEMO BASE DEMO DEVELOPED UNDER UPGRID
Used standard protocols Proposed standard protocols to be used
OSGP ETSI GS OSG 001 - Open Smart Grid Protocol for
both measurements and events between SM<->DC<-
>AMI Head End system
OSGP
GS2* - Message based protocol for measurement
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.
GS2
XML - Message based protocol for events from SM from
AMI Head End system and Vattenfall PER-system
(PerformanceEventReport system)
XML
PLC - Power Line Communication, using both A and C
band, and different frequencies. Communication
carrier between the SM and DC.
PLC
GPRS/3G - Communication between the field installed
IED, e.g. DC, and telecommunication service provider
hardware environment
GPRS/3G/CDMA
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
Used proprietary protocols
Development of new protocols / Development of
extensions to a standard protocol / protocol
profiles to be developed (and Possible
standardization process)
N/A N/A
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
28 | 129
TABLE 4 CLASSIFICATION OF THE MOST RELEVANT PROTOCOLS IN THE POLISH DEMO
DEMO BASE DEMO DEVELOPED UNDER UPGRID
Used standard protocols Proposed standard protocols to be used
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
book – 8th edition. Technical report. DLMS User
Association, 2014
COSEM Identification System and Interface Classes.
Blue Book – 12th edition. Technical report. DLMS
User Association, 2014.
IEEE 1815 Std.: IEEE Standard for Electric Power
Systems Communications—Distributed Network
Protocol (DNP3). Revised edition, 2012
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
Used proprietary protocols
Development of new protocols / Development of
extensions to a standard protocol / protocol profiles
to be developed (and Possible standardization
process)
DC-SAP (Data Concentrator - Simple Acquisition
Protocol)
DLMS/COSEM Extensions for PRIME PLC LV
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.
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
29 | 129
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
2013-05 Ed4
(CIM model v14)
• 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.
• New StateVariables package has been added to support exchange of network model
• 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. – Datatypes ShortLength and LongLength were removed and replaced with Length.
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
30 | 129
– Load, CustomerLoad, and InductionMotorLoad. – Subtypes of ConformLoad and NonConFormLoad
• Various editorial changes to clean up the UML model.
IEC 61970-301
2013-12 Ed5
(CIM model v15)
• Transformer models have been modified to be consistent for use by distribution and
transmission purposes. Additionally, the tap changer model was updated to more
clearly reflect the intended usage without relying upon rules for which attributes are
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
Ed6 draft (CIM
model v16)
• New model for grounding including Petersen coils.
• Models for HVDC
• Addition of Static Var Compensation models.
• 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
translation. The “CIM class” column indicates the CIM class that best suits the data requirement. The “CIM
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
31 | 129
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
Nº Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
1 Voltage
Measured voltages on the HV side of
the transformer in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
2 Active
power flow
Measured active power flow through
the HV side of the transformers in
the secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
S2.1.3-
B
3 Reactive
power flow
Measured reactive power flow
through the HV side of the
transformers in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
4 Current flow
Measured current flow through the
HV side of the transformers in the
secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
5
Active
power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementValu
eSource
CIM RDF XML S2.1.1-
A
6
Reactive
power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementValu
eSource
CIM RDF XML S2.1.1-
A
7
Status of
switching
elements
Measured status (open//close) of the
dynamically controlled switching
elements
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
8
Date and
time of each
variable1
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue timeStamp CIM RDF XML All
1 It is supposed the Time Stamp included in the records which contain the considered related data.
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
32 | 129
Nº Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
(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
Nº Data Description CIM class CIM attribute CIM communication
mechanism WP2Cs
1
Active
power
demand
(kW)
Measured
active power
at end user
connection
point per
phase
MeterReading CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
A
S2.2.2
WP8
2
Reactive
power
demand
(kW)
Measured
reactive
power at end
user
connection
point per
phase
MeterReading CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
A
S2.2.2
WP8
3
Prosumer’s
generation
(kW)
Power
generation
from the client
side
MeterReading CIM XML:
MeterReadings.xsd
S2.1.3-
A
WP8
4
Total
demand
profile
Demand
profile for the
consumers in
the group for
each day type
considered.
The day type
might be a
combination
of season and
workday/
weekend/
holiday
MeterReading ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
5 Number of
Consumers
Number of
consumers
belonging to
the group
This value must
be calculated
from the number
of objects of the
CIM XML:
UsagePointGroups.xsd S2.2.1
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
33 | 129
Nº Data Description CIM class CIM attribute CIM communication
mechanism WP2Cs
class type
UsagePoint
associated to a
UsagePointGroup
6 Electricity
Tariff
Price profile
charged for
the consumed
electricity
Tariff CIM XML:
PricingStructureConfig.xsd S2.2.1
7
Active
power
demand
forecast
Forecasted
active power
at end user
connection
point per
phase if no
real
measurements
are available
MeterReading ReadingQualityType.
category= Estimated
CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
B
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 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
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
34 | 129
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:ACLineSegment.r>3.416</cim:ACLineSegment.r> <cim:ACLineSegment.x>27.749</cim:ACLineSegment.x> <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:ACLineSegment>
<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:IdentifiedObject.name>T2</cim:IdentifiedObject.name>
</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.
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
35 | 129
<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.
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
36 | 129
<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:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>6.72</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>1.22</ns2:value> <ns2:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>8</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:UsagePoint>
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
37 | 129
<ns2:mRID>PL0012312312312312:*</ns2:mRID> </ns2:UsagePoint> </ns2:MeterReading> <ns2:MeterReading> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>4.52</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:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>7.32</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>0.42</ns2:value> <ns2:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>7.40</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </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.
<?xml version="1.0" encoding="UTF-8"?> <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>
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
38 | 129
<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.
<?xml version="1.0" encoding="UTF-8"?> <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:name>PrimaryName</m:name> </m:NameType> </m:Names> <m:UsagePointLocation> <m:Names> <m:name>LOC1234</m:name> <m:NameType> <m:name>PrimaryName</m:name> </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.
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
39 | 129
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])
DT name Date
(year)
Date
(Month
1-12)
Date (day
1-31)
Energy
value (h1)
Energy
value (h2) …
Energy
value (hx)
DT 1 Year 1 Month 1 Day 1 Value 1 Value 1 … Value 1
DT 1 Year 1 Month 1 Day 2 Value 2 Value 2 … Value 2
DT 1 … … … … … … …
DT 1 Year x Month y Day z Value n Value n … Value n
DT 2 Year 1 Month 1 Day 1 Value 1 Value 1 … Value 1
… … … … … … … …
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
(year)
Date
(Month
1-12)
Date (day
1-31)
Temperature
value (h1)
Temperature
value (h2) …
Temperature
value (hx)
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
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
40 | 129
TABLE 10. STRUCTURE EXAMPLE OF THE ENERGYFORECAST.OUT DATA FILE (SOURCE: [2])
DT name Date
(year)
Date
(Month) Date (day)
Energy value
(h1)
Energy value
(h2) …
Energy value
(hx)
DT 1 y m Day d Empty forecast (d,h2) … forecast (d,hx)
DT 1 y m Day d+1 forecast (d+1,h1)
forecast (d+1,h2) … forecast (d+1,hx)
DT 1 y m Day d+2 forecast (d+2,h1)
Empty … Empty
DT 2 y m Day d Empty forecast2 (d,h2) … forecast2 (d,hx)
… … … … … … … …
DT M y m Day d+2 forecastM (d+2,h1)
Empty … Empty
TABLE 11. STRUCTURE EXAMPLE OF THE ENERGYERROR.OUT INPUT DATA FILE (SOURCE: [2])
DT name Date
(year)
Date
(Month) Date (day)
Error value
(h1) Error value (h2) … Error value (hx)
DT 1 y m Day d Empty forecast (d,h2) … forecast (d,hx)
DT 1 y m Day d+1 forecast (d+1,h1)
forecast (d+1,h2) … forecast (d+1,hx)
DT 1 y m Day d+2 forecast (d+2,h1)
Empty … Empty
DT 2 y m Day d Empty forecast2 (d,h2) … forecast2 (d,hx)
… … … … … … … …
DT M y m Day d+2 forecastM (d+2,h1)
Empty … Empty
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
41 | 129
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.
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
42 | 129
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.
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
43 | 129
TABLE 13 DESCRIPTION OF THE USED VALUES IN READING TYPE
Forward energy Reverse energy Temperature
Field Number
Field name Value Value description Value Value description Value Value description
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
5 flowDirection 1 Energy supplied by the utility
19
Energy is produced and backfed onto the utility network.
0 not applicable
6 Commodity 1 All types of electricity metered quantities
1
All types of electricity metered quantities
0 not applicable
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:
<?xml version="1.0" encoding="UTF-8"?> <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>
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
44 | 129
<timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 12</value> <ReadingType ref="0.0.0.4.19.1.12.0.0.0.0.0.0.0.0.3.72.0"/> </Readings> <Readings> <timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 13</value> <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> <timeStamp>2001-12-17T09:00:00Z</timeStamp> <value>Value 21</value> <ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/> </Readings> <Readings> <timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 22</value> <ReadingType ref="0.0.0.4.1.1.12.0.0.0.0.0.0.0.0.3.72.0"/> </Readings> <Readings> <timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 23</value> <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:
<?xml version="1.0" encoding="UTF-8"?> <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.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/> </Readings> <Readings> <timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 12</value> <ReadingType ref="0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/> </Readings> <Readings> <timeStamp>2001-12-17T10:00:00Z</timeStamp> <value>Value 13</value> <ReadingType ref="0.0.0.0.0.0.46.0.0.0.0.0.0.0.0.0.23.0"/> </Readings>
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
45 | 129
</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] ).
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
46 | 129
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
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
47 | 129
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.
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
48 | 129
- 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.
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
49 | 129
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
demo
Portuguese
demo
Swedish
demo
Polish demo WP2
components
CIM RDF XML (full model) Yes Yes Yes
CIM RDF XML (difference
model)
Yes Yes
CIM XML Yes Yes
CIM Model extensions Yes
CIM XML schema
extensions
Yes
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.
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
50 | 129
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
CIM class)
New attributes
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
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
51 | 129
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
physicalPlacementKind
segmentNumber
cableKind
Conductor.length
property
manufacturer
maximumCurrent
layingKind
neutral
phases
nominalVoltage
IBDEnergyConsumer EnergyConsumer provinceCode
town
street
streetNumber
bisData
bisKind
nameIBD
IBDSecondarySubstationID
IBDACLineSegmentID
customerCount
contractedPower
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
52 | 129
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
physicalPlacementKind
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.
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
53 | 129
FIGURE 19 USED CIM CLASSES IN THE INTERFACE BETWEEN EXISTING SYSTEM AND THE LVNMS
cla ss IBDGE
Substa t ion
EquipmentConta iner
Connect iv i ty NodeConta iner
Power Sy stemResour ce
Bay
ACLineSegment
Conductor
Conduct ingEquipment
Equipment
Asset
Switch
Busba r Sect ion
Connector
CableInfo
Wir eInfo
Asset Info
Connect iv i ty Node
Fuse
Line
Tr ansfor mer End
PSRTy pe
Ter mina l
VoltageLev el
Ener gy Consumer
Ener gy Connect ion
IBDFuseLV
IBDSecondar y Substa t ion
ACLineSegmentPhase
SwitchPhase
IBDACLineSegment
IBDLowVoltageLine
GEPSRRole
IBDEner gy Consumer
Tr ansfor mer TankEnd
+PowerSystemResources 0..*
+PSRType 0..1
+Substation 1
+VoltageLevels 0..*
+Switch
1+SwitchPhase
0..*
+VoltageLevel 0..1+Bays 0..*
+Terminals 0..*
+ConductingEquipment 1
+Assets 0..*
+AssetInfo 0..1
+TransformerEnd 0..*
+Terminal 0..1
+EquipmentContainer
0..1
+Equipments
0..*
+Terminals 0..*
+ConnectivityNode 0..1
+Assets
0..*
+PowerSystemResources
0..*
+ACLineSegmentPhases 0..*
+ACLineSegment 1
+ConnectivityNodes 0..*
+ConnectivityNodeContainer 1
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
54 | 129
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.electricalConfigurationKind> <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
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
55 | 129
<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.aliasName>9</cim:IdentifiedObject.aliasName> <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:Conductor.length>13.00</cim:Conductor.length> <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.IBDSecondarySubstationID> <cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Overhead"/> <cim:ConductingEquipment.BaseVoltage rdf:resource="#BaseVoltage_0.380"/> <cim:Equipment.EquipmentContainer rdf:resource="#eo_circuit_75164516"/>
</cim:IBDACLineSegment>
FIGURE 24 RDF XML EXAMPLE OF IBDACLINESEGMENT
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
56 | 129
<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:IdentifiedObject.aliasName>3141630</cim:IdentifiedObject.aliasName> <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.IBDSecondarySubstationID> <cim:IBDEnergyConsumer.customerCount>3</cim:IBDEnergyConsumer.customerCount> <cim:IBDEnergyConsumer.threePhaseCustomerCount>2</cim:IBDEnergyConsumer.threePhaseCustomerCount> <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.secundarySubstationDistance> <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
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
57 | 129
between the single phase view and the 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"/> <cim:SwitchPhase.phaseSide2 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-cim15#SinglePhaseKind.A"/> <cim:SwitchPhase.Switch rdf:resource="#eo_isolating_eqpt_inst_76784472"/> </cim:SwitchPhase> <cim:SwitchPhase rdf:ID="SwitchPhase_76784475_C"> <cim:SwitchPhase.normalOpen>false</cim:SwitchPhase.normalOpen> <cim:IdentifiedObject.name>76784475_C</cim:IdentifiedObject.name> <cim:SwitchPhase.phaseSide1 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-cim15#SinglePhaseKind.C"/> <cim:SwitchPhase.phaseSide2 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-cim15#SinglePhaseKind.C"/> <cim:SwitchPhase.Switch rdf:resource="#eo_isolating_eqpt_inst_76784472"/> </cim:SwitchPhase> <cim:SwitchPhase rdf:ID="SwitchPhase_76784474_B"> <cim:SwitchPhase.normalOpen>false</cim:SwitchPhase.normalOpen> <cim:IdentifiedObject.name>76784474_B</cim:IdentifiedObject.name> <cim:SwitchPhase.phaseSide1 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-cim15#SinglePhaseKind.B"/> <cim:SwitchPhase.phaseSide2 rdf:resource="http://iec.ch/TC57/2010/CIM-schema-cim15#SinglePhaseKind.B"/> <cim:SwitchPhase.Switch rdf:resource="#eo_isolating_eqpt_inst_76784472"/> </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.aliasName>8</cim:IdentifiedObject.aliasName> <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: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_6371"/> </cim:IBDFuseLV>
FIGURE 26 3-PHASE VIEW OF A FUSE
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
58 | 129
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"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-NL.407802580-NH.407887210_77012731_A"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-NL.407802580-NH.407887210_77012731_B"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-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:Conductor.length>47.00</cim:Conductor.length> <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.IBDSecondarySubstationID> <cim:PowerSystemResource.PSRType rdf:resource="#PSRType_Underground"/> <cim:ConductingEquipment.BaseVoltage rdf:resource="#BaseVoltage_0.380"/> <cim:Equipment.EquipmentContainer rdf:resource="#eo_circuit_76979584"/> </cim:IBDACLineSegment> </dm:forwardDifferences> <dm:reverseDifferences rdf:parseType="Statements">
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
59 | 129
<rdf:Description rdf:about="#eo_cable_77012730"> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-NL.407802575-NH.407802590_77012731_A"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-NL.407802575-NH.407802590_77012731_B"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-NL.407802575-NH.407802590_77012731_C"/> <cim:Asset.PowerSystemResources rdf:resource="#eo_cable_segment_inst_77012729-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
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
60 | 129
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
LB1
1TR
1F1
LB1
2
LB3
GD3
LB4
LB5
LB2
1F3
LB2
2
GD21GD11
GD12 GD4 GD5 GD22
F_1
F_2
F_3
VoltageLevel_13200
Bay_AT_TR1 Bay_AT_TR2Bay_AT_1 Bay_AT_2 Bay_AT_3
VoltageLevel_400_1
Bay_1
AC
LS_1
_1A
CLS
_1_2
AC
LS_1
_4
AC
LS_1
_3EC
_1_1
EC_1
_2
Line_1
F_4
F_5
Bay_5
TR2
F_6
F_7
F_8
VoltageLevel_400_2
Bay_6
F_9
F_1
0
Bay_10
PowerTransformer
LoadBreakerSwitch
BusbarSection
Fuse
GroundDisconnector
AC
LS1
ACLineSegment
EC1 EnergyConsumer
ConnectivityNode
Terminal
Disconnector
D2
D1
AC
LS_M
V1
_1A
CLS
_MV
1_2
AC
LS_M
V3
_1A
CLS
_MV
3_2
AC
LS_M
V2
_1A
CLS
_MV
2_2
Line_MV1 Line_MV2 Line_MV3
FIGURE 28 GRAPHICAL REPRESENTATION OF A DISTRIBUTION NETWORK USING THE CIM MODEL
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
61 | 129
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.
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
62 | 129
FIGURE 29 CIM CLASSES FOR REPRESENTING THE ELECTRICAL VIEW OF THE DISTRIBUTION NETWORK
class IBD2
Substa t ion
EquipmentConta iner
Connect iv ity NodeConta iner
Power Sy stemResour ce
Bay
ACLineSegment
Conductor
Conduct ingEquipment
Equipment
Asset
P r otectedSwitch
Switch
Busbar Sect ion
Connector
Connect iv ity Node
Disconnector
Fuse
Line
LoadBr eakSwitch
Loca t ion
Power Tr ansfor mer
Power Tr ansfor mer End
Tr ansfor mer End
PSRTy pe
Ra t ioTapChanger
Ter mina l
VoltageLev el
Ener gy Consumer
Ener gy Connect ion
Gr oundDisconnector
IBDFuseLV
IBDSecondar y Substa t ion
ACLineSegmentPhase
SwitchPhase
IBDACLineSegment
IBDLowVoltageLine
GEPSRRole
IBDEner gy Consumer
Tr ansfor mer TankEnd
+ACLineSegmentPhases 0..*
+ACLineSegment 1
+PowerSystemResources 0..*
+PSRType 0..1
+Switch
1+SwitchPhase
0..*
+EquipmentContainer
0..1
+Equipments
0..*
+PowerTransformer 0..1
+PowerTransformerEnd 0..*
+Terminals 0..*
+ConductingEquipment 1
+TransformerEnd 1
+RatioTapChanger0..1
+TransformerEnd 0..*
+Terminal 0..1
+ConnectivityNodes 0..*
+ConnectivityNodeContainer 1
+Substation 1
+VoltageLevels 0..*
+VoltageLevel 0..1+Bays 0..*
+Assets
0..*
+PowerSystemResources
0..*
+Assets 0..*
+Location 0..1
+Location
0..1
+PowerSystemResources
0..*
+Terminals 0..*
+ConnectivityNode 0..1
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
63 | 129
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
IBDSecondarySubstation
provinceCode ServiceLocation (stateOrProvince)
town ServiceLocation (townDetail)
direction ServiceLocation (streetDetail)
postalCode ServiceLocation (postalCode)
functionKind PSRType
class IBD2
Equipment
Asset
CableInfo
Wir eInfo
Asset Info
AssetOwner
AssetOr ganisa t ionRole
Or ganisa t ionRole
Cr ew
Loca t ion
Ser v iceLoca t ion
Wor kLoca t ion
Manufactur er
Owner ship
Power Tr ansfor mer InfoP r oductAssetModel
SwitchInfo
UsagePoint
IBD2FuseInfo
IBD2Power Tr ansfor mer Info
+ProductAssetModels 0..*
+Manufacturer 0..1
+Assets 0..*
+OrganisationRoles 0..*
+UsagePoints 0..*
+Equipments0..*
+Ownerships 0..*
+Asset 0..1
+Asset
0..*
+ProductAssetModel
0..1
+ServiceLocation 0..1
+UsagePoints 0..*
+ProductAssetModel 0..1
+AssetInfo 0..1
+Ownerships
0..*+AssetOwner
0..1
+Assets
0..*
+AssetInfo
0..1
+Assets 0..*
+Location 0..1
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
64 | 129
physicalLocationKind ServiceLocation (type)
electricalConfigurationKind ProductAssetModel
status Asset (inUseState)
manufacturer Manufacturer
maintenanceResponsible Crew
accessMethod ServiceLocation (accessMethod)
property Ownership
dataBaseID Asset (utcNumber)
IBDDistributionTransfomer
position Terminal
positionKind ServiceLocation
positionStatus Asset (inUseState)
mvConnectionKind Terminal
mvConnectionSection CableInfo
mvConnectionMaterial CableInfo
manufacturer Manufacturer
ratedS PowerTransformerEnd (ratedS)
outputKind IBD2PowerTransformerInfo
physicalPlacementKind ServiceLocation
refrigerantKind IBD2PowerTransformerInfo
connectionKind PowerTransformerEnd (vectorGroup)
regulationRange RatioTapChanger
tapStep RatioTapChanger
embeddedFuse Fuse
IBDFuseLV
IBDSecondarySubstationID Terminal
position Terminal
cabinet Terminal
fuseKind IBD2FuseInfo
fuseDescription IBD2FuseInfo
manufacturer Manufacturer
manufacturerModel ProductAssetModel
nominalCurrent SwitchInfo
IBDLowVoltageLine
nominalVoltage VoltageLevel
position Terminal
cabinet Terminal
cableKind CableInfo
phaseWireCount Terminal
layingKind CableInfo
section CableInfo
headMaterial CableInfo
IBDACLineSegment IBDSecondarySubstationID Terminal
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
65 | 129
IBDSecondarySubstationName Terminal
nameIBD Terminal
physicalPlacementKind Asset
segmentNumber Terminal
cableKind CableInfo
Conductor.length ACLineSegment
property Ownership
manufacturer Manufacturer
maximumCurrent CableInfo
layingKind Asset
neutral Terminal
phases Terminal
nominalVoltage Terminal
IBDEnergyConsumer
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
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)
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
66 | 129
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> <!--Asset view of the 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>
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
67 | 129
<!--Model of the substation--> <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> <!--Location of the substation--> <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:PowerTransformer> <!--High voltage side--> <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>
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
68 | 129
<!--Low voltage side--> <cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_BT"> <cim:PowerTransformerEnd.PowerTransformer rdf:resource="#_CTD200004790_TR1"/> <cim:TransformerEnd.BaseVoltage rdf:resource="#_BaseVoltage_400"/> <cim:TransformerEnd.Terminal rdf:resource="#_CTD200004790_TR1_T2"/> <cim:TransformerEnd.endNumber>2</cim:TransformerEnd.endNumber> </cim:PowerTransformerEnd> <!--Tap changer of the high voltage side--> <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> <!--High voltage terminal (correspond to 3 phases)--> <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> <!--Low voltage terminal (correspond to 3 phases + neutral phase)--> <cim:Terminal rdf:about="#_CTD200004790_TR1_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <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.ConductingEquipment rdf:resource="#_CTD200004790_TR1"/> </cim:Terminal> <!--Asset view of the transfomer--> <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.inUseState>inUse</cim:Asset.inUseState> <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> <!--Model of the transformer--> <cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790_TR1"> <cim:ProductAssetModel.manufacturer rdf:resource="#_MANUFACTURER2"/> <cim:ProductAssetModel.modelNumber>INTERIOR</cim:ProductAssetModel.modelNumber>
</cim:ProductAssetModel>
<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"> <cim:Switch.normalOpen>false</cim:Switch.normalOpen>
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
69 | 129
<cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVFUSE"/> <cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_BAY_1"/> </cim:Fuse> <!--Asset view of the 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> <!--Terminal 1 of the fuse - neutral phase doesn't have fuse--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_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_VOLTAGELEVEL_400_1_BUSBAR"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/> </cim:Terminal> <!--Terminal 2 of the fuse--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_T2"> <cim:Terminal.sequenceNumber>2</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_VOLTAGELEVEL_400_1_LINE1_1"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_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:Equipment.UsagePoints rdf:resource="#_CAJA_3131739_PROFILE_CUSTOMER2"/> </cim:EnergyConsumer> <!--The terminal of the consumer box 1--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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_LINE1_2"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1"/> </cim:Terminal> <!--Asset view of the consumer box 1--> <cim:Asset rdf:about="#_ASSET_CAJA_3131739"> <cim:IdentifiedObject.name>CAJA 3131739</cim:IdentifiedObject.name> <cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1"/> <cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_ENERGYCONSUMER"/> <cim:Asset.utcNumber>3131739</cim:Asset.utcNumber> <cim:Asset.Location rdf:resource="#_SERVICELOCATION_CAJA_3131739"/>
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
70 | 129
<cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CAJA_3131739"/> </cim:Asset> <!--Location of the consumer box 1--> <cim:ServiceLocation rdf:about="#__SERVICELOCATION_CAJA_3131739"> <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/> </cim:streetDetail> </cim:mainAddress.streetDetail> </cim:mainAddress> </cim:Location.mainAddress> <cim:Location.type>PATIO MANZANA</cim:Location.type> <cim:ServiceLocation.accessMethod>POR VIVIENDA XXX</cim:ServiceLocation.accessMethod> </cim:ServiceLocation> <!--Asset view of the fuse of the consumer box 1--> <cim:Asset rdf:about="#_ASSET_CAJA_3131739_FUSE"> <cim:Asset.IBDFuseInfo rdf:resource="#_FUSEINFO_TYPE2"/> <cim:Asset.inUseState>inUse</cim:Asset.inUseState> <cim:Asset.PowerSystemResources>#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1</cim:Asset.PowerSystemResources> </cim:Asset> <!--Profile of consumer 1 of the consumer box 1--> <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> <!--Profile of consumer 2 of the consumer box 1--> <cim:UsagePoint rdf:about="#_CAJA_3131739_PROFILE_CUSTOMER2"> <cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.AN"/> <cim:UsagePoint.nominalServiceVoltage>231</cim:UsagePoint.nominalServiceVoltage> <cim:UsagePoint.estimatedLoad>85</cim:UsagePoint.estimatedLoad> <cim:isSdp>false</cim:isSdp> <cim:UsagePoint.servicePriority>NORMAL</cim:UsagePoint.servicePriority>
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
71 | 129
<cim:UsagePoint.connectionState rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#UsagePointConnectedKind.connected"/> </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.
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
72 | 129
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.
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
73 | 129
FIGURE 35 CIM CLASSES OF THE SWEDISH DEMO AND COMPARISON WITH THE SPANISH DEMO (ELECTRICAL VIEW)
class IBDGEv 1
Substa t ion
EquipmentConta iner
Connect iv ity NodeConta iner
Power Sy stemResour ce
Bay
ACLineSegment
Conductor
Conduct ingEquipment
Equipment
Asset
Br eaker
P r otectedSwitch
Switch
Busbar Sect ion
Connector
Connect iv ity Node
Disconnector
FuseJumper
Line
LoadBr eakSwitch
Loca t ion
Posit ionPoint
Power Tr ansfor mer
Power Tr ansfor mer End
Tr ansfor mer End
PSRTy pe
Ra t ioTapChanger
Ter mina l
VoltageLev el
Ener gy Consumer
Ener gy Connect ion
Coor dina teSy stem
Gr oundDisconnector
IBDFuseLV
IBDSecondar y Substa t ion
ACLineSegmentPhase
SwitchPhase
IBDACLineSegment
IBDLowVoltageLine
GEPSRRole
IBDEner gy Consumer
Tr ansfor mer TankEnd
+Locations 0..*+CoordinateSystem 0..1
+Assets
0..*
+PowerSystemResources
0..*
+ConnectivityNodes 0..*
+ConnectivityNodeContainer 1
+Assets 0..*
+Location 0..1
+Substation 1
+VoltageLevels 0..*
+PowerSystemResources 0..*
+PSRType 0..1
+VoltageLevel 0..1+Bays 0..*
+Terminals 0..*
+ConductingEquipment 1
+PowerTransformer 0..1
+PowerTransformerEnd 0..*
+Switch
1+SwitchPhase
0..*
+Location
1+PositionPoints
0..*
+Location
0..1
+PowerSystemResources
0..*
+EquipmentContainer
0..1
+Equipments
0..*
+TransformerEnd 0..*
+Terminal 0..1
+TransformerEnd 1
+RatioTapChanger0..1
+Terminals 0..*
+ConnectivityNode 0..1
+ACLineSegmentPhases 0..*
+ACLineSegment 1
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
74 | 129
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>
class IBDGEv 1
Equipment
Asset
Br eaker Info
Concentr icNeutr a lCableInfo
CableInfo
Wir eInfo
Asset Info
AssetOwner
AssetOr ganisa t ionRole
Or ganisa t ionRole
Cr ew
Loca t ion
Ser v iceLoca t ion
Wor kLoca t ion
Manufactur er
Owner ship
Power Tr ansfor mer InfoP r oductAssetModel
SwitchInfo
UsagePoint
OldSwitchInfo
IBD2FuseInfo
IBD2Power Tr ansfor mer Info
+ProductAssetModel 0..1
+AssetInfo 0..1
+Ownerships
0..*+AssetOwner
0..1
+Assets 0..*
+OrganisationRoles 0..*
+Assets 0..*
+Location 0..1 +ProductAssetModels 0..*
+Manufacturer 0..1
+ServiceLocation 0..1
+UsagePoints 0..*
+Assets
0..*
+AssetInfo
0..1
+UsagePoints 0..*
+Equipments0..*
+Ownerships 0..*
+Asset 0..1
+Asset
0..*
+ProductAssetModel
0..1
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
75 | 129
</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:IdentifiedObject.name>T1</cim:IdentifiedObject.name>
</cim:PowerTransformer>
<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:ProductAssetModel>
<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
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
76 | 129
<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.normalOpen>false</cim:Switch.normalOpen> <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:ConductingEquipment.BaseVoltage rdf:resource="#_dc7face4-2e1f-4768-96d7-ccb91b42463c" /> <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.r>0.01098</cim:ACLineSegment.r> <cim:ACLineSegment.r0>0.04392</cim:ACLineSegment.r0> <cim:ACLineSegment.x>0.00048</cim:ACLineSegment.x> <cim:ACLineSegment.x0>0.00192</cim:ACLineSegment.x0>
</cim:ACLineSegment>
<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.neutralStrandRadius> <cim:ConcentricNeutralCableInfo.neutralStrandCount>1</cim:ConcentricNeutralCableInfo.neutralStrandCount>
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
77 | 129
<cim:Wireinfo.ratedCurrent>95</cim:Wireinfo.ratedCurrent>
</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:ConductingEquipment.BaseVoltage rdf:resource="#_dc7face4-2e1f-4768-96d7-ccb91b42463c" />
</cim:EnergyConsumer>
<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
Location
PSRType
BaseVoltage
Assets
name
length
b0ch
bch
r
r0
x
x0
length
PSRType
EquipmentContainer
Asset mRID
AssetInfo
OrganisationRoles
name
type
name
utcNumber
PowerSystemResources
AssetInfo
inUseState
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
78 | 129
serialNumber
manufacturedDate
installationDate
Location
Ownership
ProductAssetMod
EnergyConsumer mRID
Location
BaseVoltage
EquipmentContainer
PSRType
UsagePoints
UsagePont mRID
Equipments
name
phaseCode
nominalServiceVoltage
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
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
79 | 129
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
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
80 | 129
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.
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
81 | 129
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.
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
82 | 129
<?xml version="1.0" encoding="UTF-8"?> <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>
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
83 | 129
<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.
<?xml version="1.0" encoding="UTF-8"?> <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>
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
84 | 129
<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: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:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>6.72</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>1.22</ns2:value> <ns2:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>8</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:UsagePoint> <ns2:mRID>PL0012312312312312:*</ns2:mRID> </ns2:UsagePoint> </ns2:MeterReading> <ns2:MeterReading> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>4.52</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:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>7.32</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.38.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>0.42</ns2:value> <ns2:ReadingType ref="0.0.0.12.1.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:Readings> <ns2:timeStamp>2014-01-01T11:00:00.0Z</ns2:timeStamp> <ns2:value>7.40</ns2:value> <ns2:ReadingType ref="0.0.0.12.19.1.37.0.0.0.0.0.0.0.0.3.63.0"/> </ns2:Readings> <ns2:UsagePoint> <ns2:mRID>PL0023423423423412:*</ns2:mRID> </ns2:UsagePoint> </ns2:MeterReading> </ns2:MeterReadings>
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
85 | 129
</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).
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
86 | 129
FIGURE 49 CIM CLASSES FOR FORWARDING OBJECT STATES
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
87 | 129
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
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
88 | 129
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.
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
89 | 129
FIGURE 53 CIM CLASSES FOR FORWARDING FDIR SEQUENCES
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
90 | 129
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.
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
91 | 129
FIGURE 55 CIM CLASSES FOR POTENTIAL OUTAGE INFORMATION EXCHANGE
FIGURE 56 SCHEMA OUTAGES.XSD
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
92 | 129
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
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
93 | 129
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.
FIGURE 59 SCHEMA GETCIMXML FOR REQUESTING CIM RDF XML OR CIM XML DOCUMENTS
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
94 | 129
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:AnalogValue xsi:type="mikmeas:AnalogValue"> <mikmeas:mRID>_d6f0cde9666d43b7ab7388e867464158</mikmeas:mRID> <mikmeas:timeStamp>2016-08-29T14:31:22+03:00</mikmeas:timeStamp> <mikmeas:MeasurementValueQuality ref="8589934593"/> <mikmeas:value>15.2069998</mikmeas:value> </mikmeas:AnalogValue> <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.6789999</mikmeas:value> </mikmeas:AnalogValue> <mikmeas:AnalogValue xsi:type="mikmeas:AnalogValue"> <mikmeas:mRID>_d6f0cde9666d43b7ab7388e867464158</mikmeas:mRID> <mikmeas:timeStamp>2016-08-29T14:31:22+03:00</mikmeas:timeStamp> <mikmeas:MeasurementValueQuality ref="8589934593"/> <mikmeas:value>15.1999998</mikmeas:value> </mikmeas:AnalogValue> </mikmeas:Measurements> </iecmeas:Payload> </iecmeas:ChangedMeasurements>
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
95 | 129
</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> </ieccommsg:Payload> </ieccommsg:CreateCommands> </ksdexcomxsd:DataArea> </ksdexcomxsd:CreateCommands> </SOAP-ENV:Body>
FIGURE 61 MESSAGE FOR SENDING COMMANDS
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
96 | 129
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 PowerTransformer 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.
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
97 | 129
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.
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
98 | 129
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.
[7] IEC 61968-4:2007, Application integration at electric utilities - System interfaces for distribution
management - Part 4: Interfaces for records and asset management.
[8] IEC 61968-6:2015, Application integration at electric utilities - System interfaces for distribution
management - Part 6: Interfaces for maintenance and construction.
[9] IEC 61968-8:2015, Application integration at electric utilities - System interfaces for distribution
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].
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
99 | 129
[13] IEC 61970-501:2006, Energy management system application program interface (EMS-API) - Part
501: Common Information Model Resource Description Framework (CIM RDF) schema.
[14] IEC 61970-552:2016, Energy management system application program interface (EMS-API) - Part
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.
[23] IEC 61970-453:2014, Energy management system application program interface (EMS-API) - Part
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.
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
100 | 129
[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.
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
101 | 129
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
102 | 129
ANNEXES
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
103 | 129
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
Nº Data Description CIM class CIM attribute
CIM
communication
mechanism
WP2Cs
1 Voltage
Measured voltages on the HV side of
the transfomers in the primary
substation.
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
2 Voltage
Measured voltages on the LV side of
the transfomers in the primary
substation.
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
3 Voltage Measured voltages at other points in
the primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
4 Active
power flow
Measured active power flow through
the HV side of the transformers in
the primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
5 Reactive
power flow
Measured reactive power flow
through the HV side of the
transformers in the primary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
6 Current flow
Measured current flow through the
HV side of the transformers in the
primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
7 Active
power flow
Measured active power flow through
the LV side of the transformers in the
primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
8 Reactive
power flow
Measured reactive power flow
through the LV side of the
transformers in the primary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
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
104 | 129
Nº Data Description CIM class CIM attribute
CIM
communication
mechanism
WP2Cs
9 Current flow
Measured current flow through the
LV side of the transformers in the
primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
10
Status of
switching
elements
Measured status (open//close) of the
dynamically controlled switching
elements
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
11
Status of
shunt
capacitor
Measured status
(connected/disconnected) of the
dynamically controlled shunt
capacitors
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
12 Tap changer
position
Measured position of the
dynamically controlled tap changers
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
Date and
time of each
variable4
(UTC, UNIX
Timestamp)
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue timeStamp CIM RDF XML All
TABLE 20: MV FEEDERS DATA
Nº Data Description CIM class CIM attribute
CIM
communication
mechanism
WP2Cs
1 Active
power flow
Measured active power flow through
each of the MV feeders departing
from the primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
2 Reactive
power flow
Measured reactive power flow
through each of the MV feeders
departing from the primary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
3 Current flow
Measured current flow through each
of the MV feeders departing from
the primary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
4
Status of
switching
elements
Measured status (open//close) of the
dynamically controlled switching
elements
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
5 Date and
time of each
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue timeStamp CIM RDF XML All
4 It is supposed the Time Stamp included in the records which contain the considered related data.
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
105 | 129
variable5
(UTC, UNIX
Timestamp)
TABLE 21: SECONDARY SUBSTATION MV RELATED DATA
Nº Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
1 Voltage
Measured voltages on the HV side of
the transformer in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
2 Active
power flow
Measured active power flow through
the HV side of the transformers in
the secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
S2.1.3-
B
3 Reactive
power flow
Measured reactive power flow
through the HV side of the
transformers in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
4 Current flow
Measured current flow through the
HV side of the transformers in the
secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
5
Active
power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementValu
eSource
CIM RDF XML S2.1.1-
A
6
Reactive
power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementValu
eSource
CIM RDF XML S2.1.1-
A
7
Status of
switching
elements
Measured status (open//close) of the
dynamically controlled switching
elements
Discrete
DiscreteValue CIM RDF XML
S2.1.1-
A
8
Date and
time of each
variable6
(UTC, UNIX
Timestamp)
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue timeStamp CIM RDF XML All
5 It is supposed the Time Stamp included in the records which contain the considered related data.
6 It is supposed the Time Stamp included in the records which contain the considered related data.
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
106 | 129
TABLE 22: SECONDARY SUBSTATION LV RELATED DATA
Nº Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
1 Voltage
Measured voltage at the LV side of
the transformer in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
S2.1.3-
A
WP8
2 Active power
flow
Measured active power flow
through the LV side of the
transformers in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
S2.1.3-
A
S2.2.2
3 Reactive power
flow
Measured reactive power flow
through the LV side of the
transformers in the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
S2.1.3-
A
S2.2.2
4 Current flow
Measured current flow through the
LV side of the transformers in the
secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
A
5
Active power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementV
alueSource
CIM RDF XML S2.1.1-
A
6
Reactive power
demand
forecast
Forecasted active power at
secondary substation for those
substations with no measurements
available
Analog
AnalogValue
MeasurementV
alueSource
CIM RDF XML S2.1.1-
A
7 Phase Voltages Measured single-phase voltages at
the secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
S2.1.2
S2.1.3-
A
S2.1.4
S2.1.3-
B
8 Active Power
Flow
Measured active power flow per
phase at the secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
WP8
S2.1.3-
B
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
107 | 129
7 It is supposed the Time Stamp included in the records which contain the considered related data.
9 Reactive Power
Flow
Measured reactive power flow per
phase at the secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
WP8
S2.1.3-
B
10 Current Measured current per phase at the
secondary substation
Analog
AnalogValue CIM RDF XML S2.1.4
11
Smart meter
communication
status
Detection of online, offline and
inactive smart meters. ComMedia status
CIM RDF XML
CIM XML:
EndDeviceEvents
.xsd
S2.1.4
12
Date and time
of each
variable7 (UTC,
UNIX
Timestamp)
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue timeStamp
CIM RDF XML
CIM XML:
EndDeviceEvents
.xsd
All
WP8
13
Secondary
Substation (LV
node) name
and code
Identification information of the LV
node IdentifiedObject
mRID
name
CIM RDF XML
S2.1.3-
A
WP8
14
Secondary
Substation
Coordinates
Geographical data (utm coordinates
or other geographic information) to
obtain adequate weather
information
Alternative 1:
Location
Alternative
2:PositionPoint
Alternative
1:
geoInfoRef
erence
CIM RDF XML
S2.1.3-
A
WP8
15
Type of
Secondary
Substation
Urban (U), concentrated rural (CR),
disperse rural (DR) Asset type CIM RDF XML
S2.1.3-
A
WP8
16
Electrical
characteristics
of the
secondary
substations
Nominal power TransformerEnd
Info ratedS
S2.1.3-
A
17
Number of
clients
downstream of
each secondary
substation
Number of clients at the
transformation centre
This value must
be calculated
from the
number of
objects of the
class type Meter
associated to a
CIM RDF XML S2.1.3-
A
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
108 | 129
TABLE 23: LV FEEDERS RELATED DATA
Nº Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
1 Active
Power Flow
Measured active power flow per phase
in the LV feeder(s) of the secondary
substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
2 Reactive
Power Flow
Measured reactive power flow per
phase in the LV feeder(s) of the
secondary substation
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
3
Date and
time of each
variable8
(UTC, UNIX
Timestamp)
Date and time information of the
temperature, active and reactive power
measurement
AnalogValue
DiscreteValue timeStamp CIM RDF XML All
TABLE 24: LV CABINETS RELATED DATA
Nº Data Description CIM class CIM
attribute
CIM
communicatio
n mechanism
WP2Cs
1 Phase Voltages Measured single-phase voltages at
the LV cabinets
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
S2.1.2
S2.1.4
S2.1.3-
B
2
Active Power
Flow
Measured active power flow per
phase at the LV cabinets
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
S2.1.3-
B
3 Reactive Power
Flow
Measured reactive power flow per
phase at the LV cabinets
Analog
AnalogValue CIM RDF XML
S2.1.1-
B
S2.1.3-
B
4 Current Measured current per phase at the LV
cabinets
Analog
AnalogValue CIM RDF XML S2.1.4
8 It is supposed the Time Stamp included in the records which contain the considered related data.
secondary
substation
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
109 | 129
5
Smart meter
communication
status
Detection of online, offline and
inactive smart meters. ComMedia status
CIM RDF XML
CIM XML:
EndDeviceEve
nts.xsd
S2.1.4
6
Date and time
of each
variable9 (UTC,
UNIX
Timestamp)
Date and time information of the
temperature, active and reactive
power measurement
AnalogValue
DiscreteValue
timeSta
mp
CIM RDF XML
CIM XML:
EndDeviceEve
nts.xsd
All
TABLE 25: CUSTOMER SMART METERS RELATED DATA
N
º Data Description CIM class CIM attribute
CIM communication
mechanism WP2Cs
1
Active
power
demand
(kW)
Measured
active power
at end user
connection
point per
phase
MeterReading CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
A
S2.2.2
WP8
2
Reactive
power
demand
(kW)
Measured
reactive
power at end
user
connection
point per
phase
MeterReading CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
A
S2.2.2
WP8
3
Prosumer’s
generation
(kW)
Power
generation
from the
client side
MeterReading CIM XML:
MeterReadings.xsd
S2.1.3-
A
WP8
4
Total
demand
profile
Demand
profile for the
consumers in
the group for
each day type
considered.
The day type
might be a
combination
of season and
workday/
MeterReading ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
9 It is supposed the Time Stamp included in the records which contain the considered related data.
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
110 | 129
N
º Data Description CIM class CIM attribute
CIM communication
mechanism WP2Cs
weekend/
holiday
5 Number of
Consumers
Number of
consumers
belonging to
the group
This value must be
calculated from
the number of
objects of the
class type
UsagePoint
associated to a
UsagePointGroup
CIM XML:
UsagePointGroups.xsd S2.2.1
6 Electricity
Tariff
Price profile
charged for
the consumed
electricity
Tariff CIM XML:
PricingStructureConfig.xsd S2.2.1
7
Active
power
demand
forecast
Forecasted
active power
at end user
connection
point per
phase if no
real
measurement
s are available
MeterReading ReadingQualityType.
category= Estimated
CIM XML:
MeterReadings.xsd
S2.1.1
S2.1.3-
B
8
Smart
Meter (LV
node) name
and code
Identification
information
of the Smart
Meter
MeterReading mRID CIM XML:
MeterConfig.xsd
S2.1.3-
A
WP8
9
Smart
Meter (LV
node) name
and code
ID of the
upstream
Secondary
Substation
TransformerTank mRID CIM XML:
UsagePointConfig.xsd
S2.1.3-
A
WP8
10
Geographic
al location
of the Smart
Meter
Geographical
data (utm
coordinates
or other
geographic
information)
to obtain
adequate
weather
information
UsagePointLocatio
n
CIM XML:
UsagePointLocationConfig.x
sd
S2.1.3
11
Contracted
Power of
Prosumer
kW
Maximum
power in the
Consumer
and Producer
UsagePoint ratedPower CIM XML:
UsagePointConfig.xsd
S2.1.3
S2.1.3-
A
S2.1.3.
B
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
111 | 129
N
º Data Description CIM class CIM attribute
CIM communication
mechanism WP2Cs
contract.
Mean and
variance
values
S2.2.1
WP8
12
Nominal
Voltage
level
380V, 230V UsagePoint nominalServiceVoltag
e
CIM XML:
UsagePointConfig.xsd
S2.1.3-
A
WP8
13
Location
type of the
Smart
Meter
Urban (U),
concentrated
rural (CR),
disperse rural
(DR)
S2.1.3
14 Phase
Voltages
Measured
single-phase
voltages
MeterReading CIM XML:
MeterReadings.xsd
S2.1.1.
B
S2.1.2.
S2.1.4
S2.1.3.
B
15
Active
Power Flow
Measured
active power
flow per
phase
MeterReading CIM XML:
MeterReadings.xsd
S.1.1.B
S2.1.3.
B
16 Reactive
Power Flow
Measured
reactive
power flow
per phase
MeterReading CIM XML:
MeterReadings.xsd
S.1.2
S2.1.3.
B
17 ICP status
Status of the
internal
switch
UsagePoint connectionState CIM XML:
UsagePointConfig.xsd S2.1.4
18
Date and
time of each
variable10
(UTC, UNIX
Timestamp)
Date and time
information
of the
temperature,
active and
reactive
power
measurement
MeterReading timeStamp CIM XML:
MeterReadings.xsd
All
WP8
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
10 It is supposed the Time Stamp included in the records which contain the considered related data.
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
112 | 129
Nº Data Description CIM class CIM attribute CIM communication
mechanism WP2Cs
1
Air
conditioning
and heating
consumption*
(kWh/year)
-- PanDemandResponse
avgLoadAdjustment
(it uses %)
CIM XML:
EndDeviceControl.xsd
S2.1.3-
A
2
Hot water
consumption*
(kWh/year)
-- PanDemandResponse
avgLoadAdjustment
(it uses %)
CIM XML:
EndDeviceControl.xsd
S2.1.3-
A
3
Thermal
collectors
installed*
(kWh/year).
-- PanDemandResponse
avgLoadAdjustment
(it uses %)
CIM XML:
EndDeviceControl.xsd
S2.1.3-
A
4
Type of air
conditioning*:
Heat pump
(HP), electric
heaters (H),
Boiler (B),
Cooling system
(AC), Thermal
collectors (TC)
-- PanDemandResponse
appliance
CIM XML:
EndDeviceControl.xsd
S2.1.3-
A
5 Energy stored
kWh/hour or
kWh/year or
kWh/…).
PanDemandResponse
appliance
CIM XML:
EndDeviceControl.xsd
S2.1.3-
A
WP8
6
End-user
preferences:
Time flexibility
Time flexibility
characterized by
the duration,
start and end
time
EndDeviceControl scheduledInterval CIM XML:
EndDeviceControl.xsd
S2.2.1-
B
7
End user
preferences:
price
thresholds
Price band
where the user
is available for
control
PanPricingDetail CIM XML:
EndDeviceControl.xsd
S2.2.1-
B
8 Band of
comfort levels
Maximum and
minimum power
consumption
the user is
available for
control
MeterReading ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd
S2.2.1-
B
9 Smart Plug
rated power
Technical
characteristics
of the
appliances with
smart plugs
PanDemandResponse
appliance
CIM XML:
EndDeviceControl.xsd
S2.2.1-
B
10 Shiftable loads Penetration
percentage of
PanDemandResponse
avgLoadAdjustment
(it uses %)
CIM XML:
EndDeviceControl.xsd S2.2.1
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
113 | 129
Nº Data Description CIM class CIM attribute CIM communication
mechanism WP2Cs
each shiftable
load type: 1)
washing
machine, 2)
dishwasher,
3)dryer
11
Power profile
of shiftable
loads
Power profile of
each shiftable
load type
MeterReading ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
12
Start time
likelihood of
shiftable loads
The probability
profile of the
end user to
switch on the
considered
device at each
time step.
PanDemandResponse
startDateTime
CIM XML:
EndDeviceControl.xsd S2.2.1
13 Thermal load
Penetration
percentage of
each thermal
load type: 1) air-
conditioner, 2)
space-heater
PanDemandResponse
avgLoadAdjustment
(it uses %)
CIM XML:
EndDeviceControl.xsd S2.2.1
14
Nominal power
of thermal
loads
Power for each
thermal load
type. Mean and
variance values
MeterReading ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
15 Efficiency of
thermal loads
Cooling
efficiency (EER)
and heating
efficiency (COP)
indicating the
ratio of cooling
or heating
provided by a
unit relative to
the amount of
electrical input
required to
generate it.
Mean and
variance values.
MeterReading
(new reading type)
ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
16
Comfort
temperature
set point of
thermal loads
Temperature set
point for each
thermal device
type. Mean and
variance values
MeterReading
ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
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
114 | 129
Nº Data Description CIM class CIM attribute CIM communication
mechanism WP2Cs
17
Outdoor
temperature
profile
Outdoor
temperature
profile.
MeterReading
ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
18 Building type
(size)
Size of the
household
(square
meters).Mean
and variance
values.
MeterReading
(new reading type)
ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
19 Building type
(insulation)
Percentage of
buildings
belonging to
each building
type: 1) old, un-
insulated, 2) old,
insulated, 3) old,
weatherized, 4)
old, retrofit
upgraded, 5)
moderately
insulated, 6)
very well
insulated, 7)
extremely well
insulated.
MeterReading
(new reading type)
ReadingQualityType.
category= Projected
CIM XML:
MeterReadings.xsd S2.2.1
20
Date and time
of each
variable11
(UTC, UNIX
Timestamp)
Date and time
information of
the
temperature,
active and
reactive power
measurement
MeterReading timeStamp CIM XML:
MeterReadings.xsd All
TABLE 27: MV STATIC DATA
Number Data Description CIM class CIM
attribute
CIM
communication
mechanism
WP2Cs
1
Electrical
characteristics of
lines
Impedance and length of
the line segments in the
network
ACLineSegment
CIM RDF XML S2.1.1-A
11 It is supposed the Time Stamp included in the records which contain the considered related data.
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
115 | 129
2
Electrical
characteristics of
transformers
Impedance at the high
and low voltage sides and
transformation ratio
PowerTransformer
CIM RDF XML S2.1.1-A
3
Electrical
characteristics of
shunt capacitors
Shunt impedance/
reactive power injection
of the capacitor bank
ShuntCompensator
CIM RDF XML S2.1.1-A
4 Network topology
Connectivity of the lines,
transformers and shunt
capacitors
Terminal
ConnectivityNode
CIM RDF XML S2.1.1-A
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
Numbe
r Data Description CIM class
CIM
attribute
CIM communication
mechanism
WP2C
s
1 Connection of end
users per phase
Connectivity of end users
to phases and feeders
Transform
erTank mRID
CIM XML:
UsagePointConfig.xsd
S2.1.2
S2.1.4
S2.2.3
2
Geographical
location of grid’s
equipment
Coordinates of the
consumers or network area
UsagePoin
tLocation
CIM XML:
UsagePointLocationCo
nfig.xsd
S2.1.1
-B
S2.1.2
S2.1.3
S2.1.4
S2.2.3
3
Grid’s equipment
current operation
status
Status of the grid
equipment and other
controllable devices
Asset
status
CIM RDF XML
S2.1.1
-B
S2.1.2
S2.1.4
4
DSO special
contracts with
consumers and
producers
Identification of resources
controlled by the DSO
Customer
Agreemen
t
CIM XML:
CustomerAgreementC
onfig.xsd
S2.1.2
5 Grid topology Information about the
current network topology
DiscreteVa
lue
(switch
positions)
value
CIM RDF XML
S2.1.2
S2.1.3
S2.1.4
6
Technical
characteristics of
grids equipment
Maximum and minimum
power of controllable
equipment
Operation
alLimits
CIM RDF XML S2.1.2
7
DSO merit order of
equipment
actuation
List of priority considering
the type of equipment to
control (Tap changer,
Storage, microgeneration,
loads)
ControlAr
ea
CIM RDF XML S2.1.2
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
116 | 129
8
Detailed database
of LV network
customers
available
Matched to the related SS
and from the point of view
of the Maintenance and
repairment activities.
Customer
CIM XML:
CustomerConfig.xsd S2.1.5
9
Detailed database
of LV network
assets available
Geographical location of
the asset
Asset characteristics:
- Number
- Technical
characteristics of the
asset
- Manufacturer
- Installation or
replacement date
- Last inspection date
Asset reliability:
- Types of failure
- Failure rate
Average time required to
repair asset
- Average fault location
time
- Average fault location
arrival time
- Average fault repair
time
Asset
CIM RDF XML S2.1.5
10
Geographic
information of the
LV networks,
linked with the
assets
Average times of arriving
from crew site location to
different points of
network.
Distances from crew site
location to different points
of network.
Location
geoInfoRef
erence CIM RDF XML
(CIM XML:
UsagePointLocationCo
nfig.xsd for
customers)
S2.1.5
11
Maintenance/repa
ir crews location at
specific sites in the
LV network
Geographical location of
the crew
- Number of operators
forming each crew
- Technical qualification
of the team personnel
- Number of vehicles
- Technical
characteristics
- Age
Available crew material
resources as cranes and
tools for specific fault
repair tasks
Crew
CIM RDF XML S2.1.5
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
117 | 129
12 Fault Location
Service
Indicates the probability of
fault occurrence and
identifies the probable
location.
Asset
CIM RDF XML S2.1.4
S2.1.5
13
List of historical
faults registered
per demo area
The minimum information
required is:
• Timestamp (UTC, Unix
timestamp).
• Duration (s).
• Customers affected
(ID).
• Components involved
(description of
components).
• Fault cause and failure
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.
Incident
CIM RDF XML WP8
TABLE 29: OUTPUT DATA OF EXISTING STATE ESTIMATOR
Number Data Description CIM class CIM
attribute
CIM communication
mechanism
WP2Cs
1 Voltage Estimated voltages at the
network nodes SvVoltage v CIM RDF XML
S2.2.1
2 Voltage angle Estimated voltage
angles at the network nodes SvVoltage angle CIM RDF XML
S2.2.1
3 Current Estimated currents at the
network branches
Analog
AnalogValue CIM RDF XML
S2.2.1
4 Current angle
Estimated current
angles at the network
branches
Analog
AnalogValue CIM RDF XML
S2.2.1
5 Active power
flow
Estimated active power
flows at the network
branches
SvPowerFlow P CIM RDF XML
S2.2.1
6 Reactive
power flow
Estimated reactive power
flows at the network
branches
SvPowerFlow q CIM RDF XML
S2.2.1
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
118 | 129
7 Active power
demand
Estimated active power
injections at the network
branches
SvInjection pInjection CIM RDF XML
S2.2.1
8 Reactive
power demand
Estimated reactive power
injections at the network
branches
SvInjection qInjection CIM RDF XML
S2.2.1
9 Estimation
errors
Difference between the
estimated values and
measured values
By
calculation
S2.2.1
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
119 | 129
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#"> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--Secondary substation description start--> <!----> <cim:Substation rdf:about="#_CTD200004790"> <cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_CTD"/> </cim:Substation> <!--Asset view of the 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> <!--Model of the substation--> <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> <!--Location of the substation--> <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>
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
120 | 129
</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> <!----> <!--Secondary substation description end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--Voltage levels of secondary substation CTD200004790 start--> <!----> <!--Voltage level: High--> <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> <!--Voltage level: Low Positition 1--> <cim:VoltageLevel rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1"> <cim:IdentifiedObject.name>BAJA TENSIÓN 1</cim:IdentifiedObject.name> <cim:VoltageLevel.BaseVoltage rdf:resource="#_BaseVoltage_13200"/> <cim:VoltageLevel.Substation rdf:resource="#_CTD200004790"/> </cim:VoltageLevel> <!--Voltage level: Low Positition 2--> <cim:VoltageLevel rdf:about="#_CTD200004790_VOLTAGELEVEL_400_2"> <cim:IdentifiedObject.name>BAJA TENSIÓN 2</cim:IdentifiedObject.name> <cim:VoltageLevel.BaseVoltage rdf:resource="#_BaseVoltage_400"/> <cim:VoltageLevel.Substation rdf:resource="#_CTD200004790"/> </cim:VoltageLevel> <!----> <!--Voltage levels of secondary substation CTD200004790 end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--LV Bays of TR1 of substation CTD200004790 start--> <!----> <!-- Bay 1--> <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> <!-- Bay 2--> <cim:Bay rdf:about="#_CTD200004790_BAY_2"> <cim:IdentifiedObject.name>CELDA2</cim:IdentifiedObject.name> <cim:Bay.Substation rdf:resource="#_CTD200004790"/> <cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:Bay> <!-- Bay 3--> <cim:Bay rdf:about="#_CTD200004790_BAY_3"> <cim:IdentifiedObject.name>CELDA3</cim:IdentifiedObject.name> <cim:Bay.Substation rdf:resource="#_CTD200004790"/> <cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:Bay> <!-- Bay 4--> <cim:Bay rdf:about="#_CTD200004790_BAY_4">
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
121 | 129
<cim:IdentifiedObject.name>CELDA4</cim:IdentifiedObject.name> <cim:Bay.Substation rdf:resource="#_CTD200004790"/> <cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:Bay> <!-- Bay 5--> <cim:Bay rdf:about="#_CTD200004790_BAY_5"> <cim:IdentifiedObject.name>CELDA5</cim:IdentifiedObject.name> <cim:Bay.Substation rdf:resource="#_CTD200004790"/> <cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:Bay> <!----> <!--LV Bays of TR1 of substation CTD200004790 start--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--LV transformer TR1 description start--> <!----> <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:PowerTransformer> <!--High voltage side--> <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> <!--Low voltage side--> <cim:PowerTransformerEnd rdf:about="#_CTD200004790_TR1_BT"> <cim:PowerTransformerEnd.PowerTransformer rdf:resource="#_CTD200004790_TR1"/> <cim:TransformerEnd.BaseVoltage rdf:resource="#_BaseVoltage_400"/> <cim:TransformerEnd.Terminal rdf:resource="#_CTD200004790_TR1_T2"/> <cim:TransformerEnd.endNumber>2</cim:TransformerEnd.endNumber> </cim:PowerTransformerEnd> <!--Tap changer of the high voltage side--> <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> <!--High voltage terminal (correspond to 3 phases)--> <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"/>
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
122 | 129
<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_BAY_AT_TR1_OUT"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_TR1"/> </cim:Terminal> <!--Low voltage terminal (correspond to 3 phases + neutral phase)--> <cim:Terminal rdf:about="#_CTD200004790_TR1_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <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.ConductingEquipment rdf:resource="#_CTD200004790_TR1"/> </cim:Terminal> <!--Asset view of the transfomer--> <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.inUseState>inUse</cim:Asset.inUseState> <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> <!--Model of the transformer--> <cim:ProductAssetModel rdf:about="#_PRODUCTASSETMODEL_CTD200004790_TR1"> <cim:ProductAssetModel.manufacturer rdf:resource="#_MANUFACTURER2"/> <cim:ProductAssetModel.modelNumber>INTERIOR</cim:ProductAssetModel.modelNumber> </cim:ProductAssetModel> <!----> <!--LV transformer TR1 description end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--Connectivity node between LV terminal of transformer and terminal 1 of disconnector--> <cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_IN"> <cim:ConnectivityNode.ConnectivityNodeContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:ConnectivityNode> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--LV global disconnector definition start--> <!----> <cim:Disconnector rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1"> <cim:IdentifiedObject.name>SECCIONADOR SALIDA TRAFO 1</cim:IdentifiedObject.name> <cim:Switch.normalOpen>false</cim:Switch.normalOpen> <cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVTRANSFORMER_DISCONNECTOR"/> </cim:Disconnector> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_D1"/> </cim:Terminal> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <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_BUSBAR"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_D1"/> </cim:Terminal>
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
123 | 129
<!----> <!--LV global disconnector definition end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--Connectivity node between between terminal 2 of disconnector and terminal 1 of the fuse of each bay--> <cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR"> <cim:ConnectivityNode.ConnectivityNodeContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:ConnectivityNode> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--LV busbar definition start--> <!----> <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:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:BusbarSection> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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_BUSBAR"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_BUSBAR"/> </cim:Terminal> <!----> <!--LV busbar definition end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--Fuse definition start--> <!----> <cim:Fuse rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"> <cim:Switch.normalOpen>false</cim:Switch.normalOpen> <cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVFUSE"/> <cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_BAY_1"/> </cim:Fuse> <!--Asset view of the 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> <!--Terminal 1 of the fuse - neutral phase doesn't have fuse--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_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_VOLTAGELEVEL_400_1_BUSBAR"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/> </cim:Terminal> <!--Terminal 2 of the fuse--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_D1_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <cim:Terminal.phases rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.ABC"/>
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
124 | 129
<cim:Terminal.ConnectivityNode rdf:resource="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_1"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_F_1"/> </cim:Terminal> <!----> <!--Fuse definition end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--Connectivity node between terminal 2 of the fuse of bay 1 and terminal 1 of segment 1 of line 1--> <cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_1"> <cim:ConnectivityNode.ConnectivityNodeContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:ConnectivityNode> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--Line definition start--> <!----> <cim:Line rdf:about="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"> <cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVLINE"/> <cim:Bay.VoltageLevel rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1"/> </cim:Line> <!--Asset view of the 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> <!--Segment 1 of the line--> <cim:ACLineSegment rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1"> <cim:Conductor.length>3.2</cim:Conductor.length> <cim:PowerSystemResource.PSRType rdf:resource="#_TYPE_LVSEGMENT"/> <cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/> </cim:ACLineSegment> <!--Asset view of the segment 1--> <cim:Asset rdf:about="#_ASSET_CTD200004790_LINE_1_S1"> <cim:IdentifiedObject.name>SEGMENTO 1</cim:IdentifiedObject.name> <cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1"/> <cim:Asset.CableInfo rdf:resource="#_CABLEINFO_LINE_TYPE1"/> <cim:Asset.Ownership rdf:resource="#_OWNERSHIP_100_IBERDROLA"/> </cim:Asset> <!--Terminal 1 of the segment 1--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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_LINE1_1"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1"/> </cim:Terminal> <!--Terminal 2 of the segment 1--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <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_LINE1_2"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S1"/>
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
125 | 129
</cim:Terminal> <!--Connectivity node for connecting terminal 2 of segment 1 and terminal 1 of segment 2--> <cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_2"> <cim:ConnectivityNode.ConnectivityNodeContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/> </cim:ConnectivityNode> <!--Segment 2 of the line--> <cim:ACLineSegment rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2"> <cim:Conductor.length>4.6</cim:Conductor.length> <cim:PowerSystemResource.PSRType rdf:resource="#_PSRTYPE_LVSEGMENT"/> <cim:Equipment.EquipmentContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/> </cim:ACLineSegment> <!--Asset view of the segment 2--> <cim:Asset rdf:about="#_ASSET_CTD200004790_LINE_1_S2"> <cim:IdentifiedObject.name>SEGMENTO 2</cim:IdentifiedObject.name> <cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2"/> <cim:Asset.CableInfo rdf:resource="#_CABLEINFO_LINE_TYPE1"/> <cim:Asset.Ownership rdf:resource="#_OWNERSHIP_100_IBERDROLA"/> </cim:Asset> <!--Terminal 1 of the segment 2--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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_LINE1_2"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2"/> </cim:Terminal> <!--Terminal 2 of the segment 2--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2_T2"> <cim:Terminal.sequenceNumber>2</cim:Terminal.sequenceNumber> <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_LINE1_2"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_S2"/> </cim:Terminal> <!----> <!--Line definition end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--Connectivity node between terminal 2 of the segmento 2 of line 1 and energy consumer 1--> <cim:ConnectivityNode rdf:about="#_CN_CTD200004790_VOLTAGELEVEL_400_1_LINE1_2"> <cim:ConnectivityNode.ConnectivityNodeContainer rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_LINE_1"/> </cim:ConnectivityNode> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!--Consumer box 1 definition start--> <!----> <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:Equipment.UsagePoints rdf:resource="#_CAJA_3131739_PROFILE_CUSTOMER2"/> </cim:EnergyConsumer>
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
126 | 129
<!--The terminal of the consumer box 1--> <cim:Terminal rdf:about="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1_T1"> <cim:Terminal.sequenceNumber>1</cim:Terminal.sequenceNumber> <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_LINE1_2"/> <cim:Terminal.ConductingEquipment rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1"/> </cim:Terminal> <!--Asset view of the consumer box 1--> <cim:Asset rdf:about="#_ASSET_CAJA_3131739"> <cim:IdentifiedObject.name>CAJA 3131739</cim:IdentifiedObject.name> <cim:Asset.PowerSystemResources rdf:resource="#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1"/> <cim:Asset.AssetInfo rdf:resource="#_ASSETINFO_ENERGYCONSUMER"/> <cim:Asset.utcNumber>3131739</cim:Asset.utcNumber> <cim:Asset.Location rdf:resource="#_SERVICELOCATION_CAJA_3131739"/> <cim:Asset.ProductAssetModel rdf:resource="#_PRODUCTASSETMODEL_CAJA_3131739"/> </cim:Asset> <!--Location of the consumer box 1--> <cim:ServiceLocation rdf:about="#__SERVICELOCATION_CAJA_3131739"> <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/> </cim:streetDetail> </cim:mainAddress.streetDetail> </cim:mainAddress> </cim:Location.mainAddress> <cim:Location.type>PATIO MANZANA</cim:Location.type> <cim:ServiceLocation.accessMethod>POR VIVIENDA XXX</cim:ServiceLocation.accessMethod> </cim:ServiceLocation> <!--Asset view of the fuse of the consumer box 1--> <cim:Asset rdf:about="#_ASSET_CAJA_3131739_FUSE"> <cim:Asset.IBDFuseInfo rdf:resource="#_FUSEINFO_TYPE2"/> <cim:Asset.inUseState>inUse</cim:Asset.inUseState> <cim:Asset.PowerSystemResources>#_CTD200004790_VOLTAGELEVEL_400_1_LINE_1_EC1</cim:Asset.PowerSystemResources> </cim:Asset> <!--Profile of consumer 1 of the consumer box 1--> <cim:UsagePoint rdf:about="#_CAJA_3131739_PROFILE_CUSTOMER1"> <cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.ABCN"/>
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
127 | 129
<cim:UsagePoint.nominalServiceVoltage>400</cim:UsagePoint.nominalServiceVoltage> <cim:UsagePoint.estimatedLoad>85</cim:UsagePoint.estimatedLoad> <cim:UsagePoint.isSdp>true</cim:UsagePoint.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> <!--Profile of consumer 2 of the consumer box 1--> <cim:UsagePoint rdf:about="#_CAJA_3131739_PROFILE_CUSTOMER2"> <cim:UsagePoint.phaseCode rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#PhaseCode.AN"/> <cim:UsagePoint.nominalServiceVoltage>231</cim:UsagePoint.nominalServiceVoltage> <cim:UsagePoint.estimatedLoad>85</cim:UsagePoint.estimatedLoad> <cim:UsagePoint.isSdp>false</cim:UsagePoint.isSdp> <cim:UsagePoint.servicePriority>NORMAL</cim:UsagePoint.servicePriority> <cim:UsagePoint.connectionState rdf:resource="http://iec.ch/TC57/2016/CIM-schema-cim17#UsagePointConnectedKind.connected"/> </cim:UsagePoint> <!----> <!--EnergyConsumer definition end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!-- PSR Type: Iberdrola codes--> <!----> <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> <!----> <!-- PSR Type end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++-->
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
128 | 129
<!-- Base Voltage definitions: 230V, 400V, 13200V--> <!-- B3 voltage category has been assumed--> <!----> <cim:BaseVoltage rdf:about="#_BaseVoltage_230"> <cim:BaseVoltage.nominalVoltage>230</cim:BaseVoltage.nominalVoltage> </cim:BaseVoltage> <cim:BaseVoltage rdf:about="#_BaseVoltage_400"> <cim:BaseVoltage.nominalVoltage>400</cim:BaseVoltage.nominalVoltage> </cim:BaseVoltage> <cim:BaseVoltage rdf:about="#_BaseVoltage_13200"> <cim:BaseVoltage.nominalVoltage>13200</cim:BaseVoltage.nominalVoltage> </cim:BaseVoltage> <!----> <!-- Base Voltage definition end--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!-- Asset manufacturer start--> <!----> <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> <!----> <!-- Asset manufacturer end--> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!-- Asset property information--> <!----> <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> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!-- Crew information--> <!----> <cim:Crew rdf:about="#_CREW_BRIGADABILBAO"> <cim:IdentifiedObject.name>BRIGADA BILBAO</cim:IdentifiedObject.name> </cim:Crew> <!----> <!--+++++++++++++++++++++++++++++++++++++++++++++++++--> <!-- Generic information of assets--> <!----> <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>
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
129 | 129
<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:ProductAssetModel.manufacturer rdf:resource="#_MANUFACTURER2"/> <cim:IdentifiedObject.name>CABLE</cim:IdentifiedObject.name> <cim:ProductAssetModel.modelNumber>XZ1-AL 1X240</cim:ProductAssetModel.modelNumber> <cim:usageKind>distributionUnderground</cim:usageKind> </cim:ProductAssetModel> <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:SwitchInfo.breakingCapacity>250</cim:SwitchInfo.breakingCapacity> <cim:material>copper</cim:material> </cim:SwitchInfo> <cim:IBDFuseInfo rdf:about="#_FUSEINFO_TYPE2"> <cim:IdentifiedObject.name>FUSIBLE DE CAJA 125</cim:IdentifiedObject.name> <cim:SwitchInfo.breakingCapacity>125</cim:SwitchInfo.breakingCapacity> <cim:IBDFuseInfo.class>GT (FUSION LENTA)</cim:IBDFuseInfo.class> <cim:IBDFuseInfo.size>PENDIENTE</cim:IBDFuseInfo.size> </cim:IBDFuseInfo> </rdf:RDF>