Distributed Intelligence for Cost-Effective and Reliable Distribution Network Operation Deliverable (D) No: 5.1 DISCERN semantic model to transfer developed solutions to DSOs and to facilitate their integration Author: Arshad Saleem, KTH Date: 20.05.2014 Version: 3.0 www.discern.eu The research leading to these results has received funding from the European Union Seventh Framework Programme (FP7/2007-2013) under grant agreement No. 308913. Confidential (N): N
53
Embed
Deliverable (D) No: 5.1 DISCERN semantic model to transfer …€¦ · · 2014-06-04Enterprise Architect model file, ... standards IEC 61970/61968/62325. The CIM is maintained by
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Distributed Intelligence for Cost-Effective and Reliable Distribution Network Operation
Deliverable (D) No: 5.1
DISCERN semantic model to transfer developed solutions to DSOs and to facilitate their integration
PU, Public PP, Restricted to other program participants (including the Commission Services) RE, Restricted to other a group specified by the consortium (including the Commission Services) CO, Confidential, only for members of the consortium (including the Commission Services)
Status In Process In Revision Approved
Further information www.discern.eu
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 5 of 53
Executive Summary
This document together with the accompanying DISCERN Semantic Model, in the form of an
Enterprise Architect model file, are the formal deliverable D5.1 in WP5 of the DISCERN Project. The
work documented in this deliverable has been carried out in task T.5.1 Creation of DISCERN
Semantic Model by Mapping the Demo Projects with CIM and refining it to Integrate new Smart Grid
Functions. The objective of task T5.1 was to create a semantic model by mapping the DISCERN
leading Use Cases with the IEC 61970/61968 and refining it to integrate the DISCERN smart grid
functions. The main scope of the D5.1 is to document the methodology and results of task T5.1.
In WP1 of DISCERN project the DSOs participating in the consortium identified a set of smart grid
functions, named DISCERN sub-functionalities. Roles of leaders, learners and listeners were
associated as well to the each sub-functionality. These sub-functionalities and roles are explained
further in section 1.2.2. The purpose of task T5.1 was to enable partner DSOs to create a semantic
model for the leading sub-functionalities.
A semantic information model is used to describe data types and relationships between them within an
information system. Integration and interoperability is achieved by making the different interacting
applications adhering to the same semantic model, so that these applications use common terms for
referring to the same concepts. The most widely accepted semantic information model within the
scope of electric power systems is the Common Information Model (CIM) defined in the series of
standards IEC 61970/61968/62325. The CIM is maintained by the IEC TC 57 as a Unified Modelling
Language (UML) model containing the semantics to achieve interoperability in a broad range of
energy management functionalities, such as network operations, asset management and electricity
markets.
Task T5.1 analysed to what extend the CIM enable interoperability in DISCERN leading sub-
functionalities. Moreover, the task proposed extensions in the CIM with the aim of representing the
concepts of DISCERN leading sub-functionalities that are not included in the original standard model.
A systematic methodology was adopted for the work in this task. The core aspects of the methodology
included following steps:
- Subtask T5.1.1 designed a template for leading demo project data model collection. A
template based upon the CIM packages was prepared, compiling all the CIM packages, classes
and attributes to be evaluated and prioritized by DSOs.
- In T5.1.2, the template designed in the sub-task T5.1.1 was circulated to be filled out by
DSOs. Within this activity the most relevant classes of the CIM were identified and
suggestions were made to compensate the missing functionality in CIM.
- In subtask T5.1.3 a first version of DISCERN Semantic Model, (DISCERNSmartDCIM) was
prepared based on the information collected from DSOs and trying to cover the gaps that
prevent from mapping the smart functionalities that DSOs have identified as necessary.
- Finally, subtask T5.1.4 took into account comments and feedback from DSOs in order to
cover still remaining gaps in the semantic model and produced a final version of the
DISCERN semantic model.
The DISCERN Semantic Model is an important step towards the DISCERN goals of achieving
optimal level of intelligence in European distribution networks and suggesting mechanisms for
knowledge sharing among the DSOs. It creates a common understanding, approach and mechanism
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 6 of 53
for creating a consistent and standardized set of semantics in the form of the CIM-based classes and
class relationships for the DISCERN leading sub-functionalities.
This deliverable is an input for T5.2, where learning DSOs will check whether the created DISCERN
Semantic Model is capable of representing their learning functionalities. Results of T5.1 aim to
produce a descriptive semantic model that describes data types and relationships between them within
a system in order to achieve integration and interoperability in DISCERN solutions
Moreover, results from this activity are aimed at producing feedback for standardization activity for
CIM, in particular for the working groups WG13 and WG14 of the IEC TC 57.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 7 of 53
Table of contents Executive Summary ................................................................................................................................. 5 Table of contents ..................................................................................................................................... 7 List of figures ........................................................................................................................................... 8 List of tables ............................................................................................................................................ 9 Abbreviations and Acronyms ................................................................................................................. 10 1. Introduction .................................................................................................................................... 11
1.1 Scope of the Document ......................................................................................................... 11 1.2 Background............................................................................................................................ 12
1.2.1 Information Modelling in Electric Power Systems ......................................................... 12 1.2.2 DISCERN sub-functionalities ......................................................................................... 16
2 Methodology .................................................................................................................................. 19 2.1 Template design and collection of data ................................................................................. 19 2.2 Draft of the Semantic Model .................................................................................................. 21 2.3 Collection DSO feedback ...................................................................................................... 21 2.4 Preparation of final DISCERN semantic model ..................................................................... 21
3 DISCERN SmartDCIM and summary of DSO inputs .................................................................... 22 3.1 GNF leading sub-functionality – PRICE project .................................................................... 22 3.2 IBDR leading sub-functionality – PRICE project .................................................................. 23 3.3 SSEPD leading sub-functionality - Thames Valley project .................................................... 23 3.4 RWE leading sub-functionality – Future Energy Grids and Smart Operator projects ........... 24 3.5 VTF leading sub-functionality - SmartGrid Gotland project .................................................. 25 3.6 Summary of the DISCERN demo site inputs ......................................................................... 25
4 DISCERN CIM Extensions ............................................................................................................ 26 4.1 DISCERN CIM extension 1 – GNF use cases on LV/MV supervision .................................. 26
4.1.1 B6 MV distribution grid monitoring and operation of telecontrolled switchgears - GNF 27 4.1.2 B7bd LV grid monitoring for future power quality analysis- GNF .................................. 30
4.2 DISCERN CIM extension 2- IBDR use cases on LV monitoring and calculation of technical and non-technical losses ................................................................................................................... 34
4.3 DISCERN CIM extension 3- SSEPD use cases on LV Supervision ..................................... 39 4.3.1 B7bd SSEPD MV Controller .......................................................................................... 39
4.4 DISCERN CIM extension 4 - VTF use case on Optimized AMR Data Collection ................. 43 4.4.1 B9a AMR Data Collection and Analysis - VTF .............................................................. 44
5 Conclusion and summary of results .............................................................................................. 49 6 References .................................................................................................................................... 50
This chapter describes scope, background and structure of the work presented in this deliverable.
1.1 Scope of the Document
This document together with the accompanying DISCERN Semantic Model are the formal deliverable
D5.1 in WP5 of the DISCERN Project. The work documented in this deliverable has been carried out
in task T.5.1 Creation of DISCERN Semantic Model. The deliverable primarily covers the semantic
model for the DISCERN leading sub-functionalities. Results of this work will provide direct input to task
T5.2 where the DISCERN semantic model will be evaluated for application in DISCERN learning sub-
functionalities.
The work presented here also provides input to the tasks T5.3 and T7.1 by developing a consistent
and standardized set of terminologies through the semantic models and to be used in the design of
the technical architecture. This input is though indirect and is served via the task T5.2. The Leading,
Learning and Listening sub-functionalities are designed in WP1 of the project [D1.1]. They will be
described later in this section. Two important accompanying parts of the deliverable are:
a. DISCERN SmartDCIM: A semantic model for the DISCERN leading sub-functionalities
developed in Enterprise Architect tool and provided as .eap file. This is provided as Annex A.
b. Filled survey consisting of prioritized classes from IEC TC 57 Common Information Model
(CIM) for representing DSICERN leading sub-functionalities. This is provided as Annex B.
This chapter provides a background to the work presented in the deliverable, highlighting some of the
key requirements on the work from the DISCERN Description of Work (DoW) [DOW]. In addition, the
scope and structure of the document is described.
Structure of this document is as follows:
- Rest of this section provides a background of common information modelling in electric power
systems and introduction to the DISCERN sub-functionalities
- Section 2 describes the methodology used in developing the DISCERN Semantic Model
- Section 3 presents summary of DSO input to the DISCERN Semantic Model including review
of the CIM for applicability in their use cases
- Section 4 presents the semantic model of the individual DISCEN leading Use Cases
- Section 5 provides summary of results and conclusions
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 12 of 53
-
1.2 Background
1.2.1 Information Modelling in Electric Power Systems
Efficient operation of the modern distribution networks requires a high degree of communication and interaction among many diverse systems and functions operated by diverse actors. This means that there is an increasing need for power companies to exchange data on a regular basis in order to ensure the reliable operation of interconnected power networks. Traditionally, power companies use a variety of different formats to store their data and information on assets, operations and work scheduling in a proprietary internal schema for information representation, storage and exchange. In such a scenario, different terminologies may be used to describe the same artefacts of the power system. Therefore a descriptive semantic model is used to describe data types and relationships between data types within a system. Integration and interoperability is achieved by making the different interacting applications adhere to the same semantic model. Figure 1 below shows a descriptive view of the information models and standards currently present in electric power industry.
Figure 1 Information model for enterprise integration.
The Common Information Model (CIM) is an abstract model of the major objects in an electricity utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object, classes and attributes, along with their relationships, the CIM facilitates the integration of software applications developed independently by different vendors. It facilitates integration by defining a common language (i.e., semantics and syntax) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. The CIM is defined in three standards: the IEC 61970, which is focused on the systems that manage transmission networks; the IEC 61968, which is focused on the systems that manage distribution networks; and the IEC 62325, which describes the CIM-based messages for exchanging information about electricity markets. Each standard defines a part (or subset of packages) of the model. The IEC 61970-301 defines the CIM Base model, which represents the required concepts for exchanging information about the management of transmission networks. Figure 2 shows the packages included in this standard. Package consists of a certain number of classes where each class represents an artefact in the electric power system [IEC 61970-301].
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 13 of 53
Figure 2 IEC 61970 packages (CIM Base Model)
These packages are mainly used to represent: electric power systems (Wires, Topology), the associated SCADA and protection systems, including the corresponding measurements and control data (SCADA, Protection, Meas, ControlArea), the generation plants (Generation), and the information about outage and loads (Outage, LoadModel). The IEC 61968-11 is the DCIM model, which includes additional packages for representing the required concepts for the management of distribution networks (Figure 3 I), such as: asset management (Assets, AssetModel), information about work management and network extensions (Work), information about customer billing (Customer), and metering and load control (Metering, LoadControl, PaymentMetering). It also includes an extension of the Wires package for representing typical distribution network equipment (WiresExt) [McMooran2007].
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 14 of 53
Figure 3 IEC 61968 packages (DCIM Model)
Finally, the IEC 62325-301 adds three new packages for expressing data about electricity markets. The MarketCommon package defines concepts that are required in all type of markets, and the other two packages include specific concepts for different types of electricity markets. The MarketManagement package is used when the electricity market is mainly based on regulated third party access, i.e. when transmission system operators have to allow any electricity supplier non-discriminatory access to the transmission network. Meanwhile, the MarketOperations package is focused on US-Style electricity market, which is mainly characterized by day-ahead unit commitment by a market operator, intraday and real-time balancing through central dispatch, and settlement based on locational marginal prices [Uslar2012, Uular2013].
Figure 4 IEC 62325 packages (CIM extensions for electricity markets)
Each of the above presented standards, and therefore each part of the CIM model, is developed and maintained by different working groups of experts within the IEC TC 57: WG13 is responsible for IEC 61970, WG 14 is responsible for IEC 61968, and WG16 is responsible for IEC 62325. Each working
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 15 of 53
group discusses the possible modelling extensions and modifications of its corresponding part of the model on a regular basis, usually weekly. Nevertheless, due to the existing dependencies between the different parts, the three working groups have to synchronize their versions in order to generate an annual combined version, which is maintained as an UML model in the Sparx Enterprise Architect (EA). Given the scope of DISCERN sub-functionalities (mainly focused on enhancing efficiency in day-to-day distribution grid operations – see [D4.2]), DISCERN Semantic Model will be based on the CIM Base Model defined in the standard IEC 61970-301 and the DCIM Model defined in the standard IEC 61968-11.
Figure 5 shows an extract of the CIM Base Model (packages Core, Wire, Topology) including some of
the most relevant classes for representing electric networks in CIM. For instance, circuit breakers are
represented in CIM as instances of cim:Breaker class included in Wires package. This class derives
from cim:ProtectedSwitch, which represents switches associated to protection equipment. In
turn, cim:ProtectedSwitch derives from the class that represents all types of switches,
cim:Switch. Lastly, cim:Switch is a subclass of cim:ConductingEquipment, which belongs to
Core package and represents a generic piece of conducting equipment. The connection between
different pieces of conducting equipment are represented in CIM with instances of cim:Terminal
and cim:ConnectivityNode classes, which belong to Core package [IEC 61968-11].
Figure 5 CIM Example, Conducting Equipment and Connectivity class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 16 of 53
1.2.2 DISCERN sub-functionalities
One of the main objectives of the DISCERN project is “the enhancement of European distribution grids with technical and organisational solutions for the optimal level of Smart Grid intelligence”. In order to address this objective, partners of the DISCERN project are sharing information about existing and developing solutions in order to primarily develop new functionalities at individual demo sites. Moreover, they also assess and compare performance of the different solutions at five demonstration sites across Europe (see Figure 6 below). WP1 of the project has produced a refined set of smart grid functions to be demonstrated or simulated by DSO partners across Europe (see Figure 7). The selected smart grid functions are a representative set of advance functions in distribution system monitoring and control across Europe. It is intended that it will facilitate the European DSOs in evaluating and comparing different technological and architectural options to determine the best balance between reliability, cost efficiency, replicability and scalability for their operations [D1.1].
Figure 6 Overview of the DISCERN demonstration sites
It also provides technological support to express requirements, make architecture and design and compare alternate solutions for the selected smart grid functions.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 17 of 53
Figure 7 Overview of the DISCERN sub-functionalities
For each chosen sub-functionality associated roles of Leader, Learner and Listener (3L) have been defined in order to facilitate the knowledge sharing amongst the partner DSOs. A DSO takes on one of the roles (leader, learner or listener) in relation to a specific sub-functionality. Then, the chosen role defines the level of commitment that the DSO is assuming. The role of a leading DSO is to be a mentor on a certain sub-functionality. Leading projects are characterized by the fact that the respective DSO has already developed and implemented a solution for the specific Smart Grid sub-functionality. The learning DSOs are the ones who will implement the technical solution of a sub-functionality within the scope of DISCERN. This means the DSOs that bring forward their demonstration sites for learning activities will evaluate new solutions through simulations and pilot installations. The listening DSOs will follow sub-functionalities on which they have not made any considerations regarding the concrete implementation yet but who are keen to take results from the DISCERN project into consideration . The Semantic model described in this deliverable correspond to the leading DISCERN sub-functionalities and will be analysed and used in task T5.2 Evaluation of Semantic Model Applicability for Learning Use Cases by the DISCERN demo projects and thereby serving important objectives of the knowledge sharing in the project. The DISCERN Semantic Model is intended to allow a common, consistent, and standardized definition of the semantics for the DISCERN sub-functionalities. This will facilitate crucial task of sharing and comparing solutions by the DSO parts. Figure 8 below shows a descriptive example of the requirement of knowledge sharing in the 3L scenario.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 18 of 53
Figure 8 Knowledge sharing among DISCERN 3L roles
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 19 of 53
2 Methodology
A systematic methodology was defined and adopted in order to carry out the development of the DISCERN Semantic Model. The work was divided into four structured sub tasks. Figure 9 below shows a canonical view of the subtask order.
Figure 9 Task T5.1 work methodology
2.1 Template design and collection of data
Subtask T5.1.1 carried out the template design for DSOs data model collection. A template based upon the CIM packages from IEC 61970-301 and IEC 61968-11 was prepared, compiling all the CIM
packages, classes and attributes to be evaluated by DSOs (see Figure 10).
Collection of Data from DSOs based on
a questionnaire
Preparation of a draft semantic
model
DSOs check whether the
semantic model fulfills the needs of
their demos site
Feedback is collected from DSOs and final version of the semantic model
is produced
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 20 of 53
Figure 10 CIM and DCIM core packages a basis for the template in T51.1 The purpose of this template was to collect CIM related information from the DSO demo sites. Using the template, DSOs were asked to follow simple rules to score each CIM class with the probability to
be used in order to represent their demo sites (see Figure 11).
Figure 11 Process of prioritization of CIM/DCIM classes Also it let DSOs specify requirements in the sub-functionalities which are not covered currently by the CIM (see Figure 12).
Figure 12 Template for the CIM extension suggestions
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 21 of 53
To facilitate the evaluation of CIM model by DSOs a literature review on the CIM was performed. For this purpose most relevant references found on CIM [McMooran2007, Uslar2013, Uslar2011] were shared with partners with the aim of helping to introduce the DSOs to the basics of CIM modelling and to create a common understanding of it. The template was circulated and filled by DSOs. Within this activity the most relevant classes of CIM for representing DISCERN leading sub-functionalities were identified.
2.2 Draft of the Semantic Model
In subtask T5.1.2, after a detailed review of the leading use cases prepared in task T4.2 [D4.2], and with the prioritized CIM classes in mind, new CIM model extensions were identified in order to provide it with the necessary classes and relationships to map all the DISCERN leading sub-functionalities. As a result of this process, a first version of DISCERN Semantic Model for Distribution (DISCERN SmartDCIM) was prepared based on both the information collected from DSOs with regard to class prioritization and after proposing extensions to cover those gaps that prevent DSOs from mapping the smart functionalities. Figure 13)
Figure 13 DISCERNSmartDCIM maintained in Enterprise Architect (EA)
2.3 Collection DSO feedback
In subtask T5.1.3 the first version of the semantic model was shared with partner DSOs. A thorough process of collecting feedback over the draft version was done and the feedback was reviewed in order to check whether the current extended model meets the specific needs of each DSO. Collection of CIM/DCIM extensions from literature survey [Brunel2011, GEEnvironment2013] was also provided in order to evaluate their applicability for leading use cases. A review was done for these extensions as well.
2.4 Preparation of final DISCERN semantic model
Finally, subtask T5.1.4 took into account comments and feedback from DSOs in order to cover still remaining gaps in the semantic model and produced a final version of the DCIM. The results were then incorporated into the final version of the semantic model.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 22 of 53
3 DISCERN SmartDCIM and summary of DSO inputs
The DISCERN Semantic Model is primarily based upon the CIM IEC 61970/61968, however it also extends CIM in order to address widely discussed interoperability issues in the smart grid [IECSGCG2011] and to incorporate additional leading demo site requirements. This required adding definitions for additional concepts which are not part of the CIM but needed for the implementation of DISCERN smart functions i.e., the sub-functionalities. Section 3 describes particular inputs from each of the DSO partners to the CIM standard. In particular it presents suggestions brought forward by the demo projects as extensions to the standard in order to support the leading sub-functionalities.
3.1 GNF leading sub-functionality – PRICE project
The following table shows the requirements identified to represent GNF leading use cases:
Table 2 GNF leading use case requirements
CIM Solution Comment
Medium Voltage Supervisor
The description of a protection equipment (ProtectionEquipment) or a fault indicator (FaultIndicator) is not enough.
Possible extension of CIM-DCIM model. The behaviour of the extension must include: - Sensor behaviour: current and voltage transformer. - Fault indicator behaviour: phase to phase fault detection parameters, phase to ground detection parameters. - RTU behaviour: fault alarms, current events, voltage events, equipment status, voltage measurements, current measurements, power measurements, digital outputs.
Low voltage Supervisor The meter behaviour is not enough to cover the Low Voltage Supervisor
Possible extension of CIM-DCIM model. The behaviour of the extension must include: - Measurement of low voltage current, voltage, distortion, power and energy of the transformer substation and per output cable (low voltage supervisor).
Transformer substation / secondary substation
Similar to a substation It could be an specialization of substation
GIS link Attribute IEC61968.Common.Location.geoInfoReference
Original from CIM: (if applicable) Reference to geographical information source, often external to the utility.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 23 of 53
THD (from Low Voltage Supervisor)
The measurementKind attribute of readingType (readingType appears in 61968-11 and values of measurementKind in 61968-9) could be the solution.
Another solution is to define a new type in a package equivalent to domain package. There are two ways of defining new types: readingType and measurementType.
Voltage imbalance Similar solution as THD Similar comment as THD
3.2 IBDR leading sub-functionality – PRICE project
The following table shows the requirements identified to represent IBDR demo site.
Table 3 IBDR demo site requirements
Demo Site Requirement CIM Solution Comment
CalculationCore
Generation training simulation packages provides classes primarily for generation related artefacts for simulation and educational purposes
Some classes are needed to locate the algorithms used in the Use Cases. The “Calculation Core” would be an upper/abstract class.
LossesCalculator The above as well as the Operations package provide classes for some operations related plans
Represent the processes needed to calculate the technical and not technical losses
Estimator The above as well as the Operations package provide classes for some operations related plans
Should contain all the processes need to operate the information needed to estimate the consumption
3.3 SSEPD leading sub-functionality - Thames Valley project
The following table shows the requirements identified to represent SSEPD demo site.
Special classes may be needed for aggregation of energy profiles at the substation level for the further analysis
EndPoint Monitor
Metering Package of IEC 61968 provides several classes of metering related entities.
Specific monitor classes required to represent end point real time measurements for energy profile calculations
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 24 of 53
FrontEnd Processor SCADA specific classes in the package SCADA
Information objects required to present SCADA frontend calculations and transfer to BAU applications in the B7bd use case
3.4 RWE leading sub-functionality – Future Energy Grids and Smart
Operator projects
The following tables show the requirements identified to represent RWE demo sites.
Table 5 RWE demo site requirements
Demo Site Requirement CIM Solution Comment
SMARTOPERATOR
Class for Batteries is needed
No General Support for Battery/Storage data is yet available through ShuntCompenstor may be considered for utilization
As an option the extension EnergyStorage_Brunel_Hargreaves Has been reviewed for possible application.
Class for weather data is needed No General Support for Weather/climate data is yet available
There is were some works about harmonizing CIM with Weather Data Models, so it should be possible to represent this information somehow. Otherwise, an extension could be also proposed. (RS). As an option the extension EnvironmentalData_EPRI_mcmorran has been reviewed for possible application. Though most of the classes in this extension are related to alarms and contingencies whereas requirement is more for forecast related classes.
Future Energy Grids
Missing Class: Calculated voltage values
A class describing the following is required: Calculated voltage value at the noralgic node for the middle voltage. The definition of measurementValueSource is enough to solve this issue
Missing Class: Aggregated Voltage values
The definition of measurementValueSource is enough to solve this issue
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 25 of 53
3.5 VTF leading sub-functionality - SmartGrid Gotland project
Table 6 VTF demo site requirements
Demo Site Requirement CIM Solution Comment
Class for representing AMI Head End
CIM Package Metering and enclosed classes Metering:EndDevice, Metering:UsagePoint
DISCERNSmartDCIM:: AmiHeadEnd
Class for representing Performance Evaluation (PER) Reporting Database
The CIM Core Package contains reporting related class ReportingGroup and ReportingSuperGroup. These are mostly for reporting of Events and Alarms etc
Class for representing Meter Data Management System (MDMS)
CIM Package Metering and enclosed classes Metering:EndDevice, Metering:UsagePoint
DISCERNSmartDCIM:: MeterDataManagementSystem The metering package should be further extended for missing functionality
Class for representing the Physical System Component in line with the CIM modelling methodology
CIM provides general packages Assets: AssetContainerfor.
DISCERNSmartDCIM:: InformationSystemDevice It is considered that the CIM Assets:AssetContainer should be extended for the required functionality
3.6 Summary of the DISCERN demo site inputs
While analysing the applicability of the CIM/DCIM model for their demo sites, DSOs have identified a number of potential requirements currently not fully covered by the standard. This has been described in detail in the previous sub sections. These requirements are primarily in the areas of GIS, storage, weather data, results of analysis/algorithms and simulations, and MV/LV monitoring related entities. These DSOs have either produced suggestions for new classes and attributes to represent the missing concepts and/or have reviewed current suggestions from the literature. This work will continue and it will be further analysed and refined in task T5.2 when the use cases of leaders and learners will be compared and the applicability of the DISCERN Semantic Model will be analysed. It is important to note that the level of detail of suggestions from demo sites’ inputs varies depending on the progress DSOs have made on their demo projects so far and the amount of information available at hand. It is expected that with the course of project these will be further detailed especially when the work on specification of technical architecture in tasks T5.3 and T7.1 is done.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 26 of 53
4 DISCERN CIM Extensions
This section describes proposal for the CIM/DCIM extensions based upon the input from DSOs. First part of each following sub-section describes a summary of the proposed extensions and the rest describes details from its implementation in the Enterprise Architect tool. For the RWE’s leading subfunctionalities activities are in the process for collecting some of the information that is required for establishing a final semantic model. Therefore a final semantic model for RWE will be produced in the task T5.2 and a study shall analyse how existing extensions from literature review [Brunel2011, GEEnergy2013] can be potentially used in RWE leading subfunctionalities.
4.1 DISCERN CIM extension 1 – GNF use cases on LV/MV supervision
The GNF leading sub-functionalities B6 and B7bd are aimed at MV and LV respectively. B6 is based on distribution grid monitoring and operation of tele-controlled MV switchgears; while B7bd deals with LV grid monitoring for future power quality analysis. After reviewing the packages and classes currently present in CIM IEC 61970-301 and IEC 61968-11, some extensions have been identified in order to fully represent the sub-functionalities led by GNF. The following table shows the extensions proposed by GNF.
Table 7 GNF CIM/DCIM extension proposal
PACKAGE/Extention CLASS Attribute CLASS DESCRIPTION
DISCERNSmartDCIM
This packet has been included following the IEC 61968-11 recommendations: "If an extension is made in UML model, such extension should be made in a different package as a separate model layer or context rather than be added or modified into CIM model directly. A “targetNamespace” tagged value may be used for this purpose if such extension is meant for an XSD generation."
FaultPassageIndicator
Device that indicates the presence and direction of a fault current in the cables where the device is located.
phaseCurrentLimit Phase current threshold for poly-phase faults (Imax).
Required settings: 500 A / 250 A / 130 A
groundCurrentLimit
Residual current threshold for phase-ground faults (I0). Adjustable: 0,4 - 2 A with steps of 0.1 A
groundVoltageLimit Residual voltage threshold for phase-ground faults (U0).
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 27 of 53
Fixed: 0.02 p.u. referred to U0.max
voltageAbsence Absence of voltage threshold (Uaus). Settings: 6 kV phase.
currentAbsence Absence of current threshold (Iaus). Settings: 5A.
faultDetectionTime Time to detect fault (T0). Fixed: 50 ms.
voltageAbsencePerTime Time to consider absence of voltage/current (T1). Fixed: 15 s.
voltageAbsenceMinTime
Minimum time of absence of voltage/current (T2). Adjustable: 1 - 25 s with steps of 1s
resetTime Timed reset (T4) . Settings: 3 min - 240 min.
LVSupervisor
This IED collects voltage and current measures from sensors in the LV side of secondary substations, perform registrations of energy (meter), measures and events, and generate alarms when some voltages or currents are out of margins.
MVSupervisor Medium Voltage Supervisor
SecondarySubstation
An assembly of High Voltage Switchgear, Transformer and LV Switchgear in an enclosure where the lower voltage is 400/230V. The definition includes transformer substation.
The proposed classes have been represented in Enterprise Architect program, and the required relationships have been created for the functionalities aimed at MV network monitoring and control as well as LV monitoring.
4.1.1 B6 MV distribution grid monitoring and operation of telecontrolled switchgears - GNF
For the implementation of sub-functionality B6 related to MV distribution grid monitoring and operation of telecontrolled switchgears, new classes have been proposed for CIM extensions. These new classes are:
MV supervisor
FaultPassageIndicator
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 28 of 53
4.1.1.1 MVSupervisor
Type: Class AuxiliaryEquipment Status: Proposed. Version 1.0. Phase 1.0. Package: LVMVSupervisor Keywords: Detail: Created on 07/10/2013. Last modified on 05/02/2014. GUID: {8BD255D9-915A-4ecb-BE19-BBA2E49AD7A1} Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public MVSupervisor
Public AuxiliaryEquipment
Association Unspecified
Public Supervisor MVSupervisor
Public RemoteUnit RemoteUnit
Association Unspecified
Public Supervisor MVSupervisor
Public CurrentTransformer CurrentTransformer
Association Unspecified
Public Supervisor MVSupervisor
Public PotentialTransformer PotentialTransformer
Association Unspecified
Public Supervisor MVSupervisor
Public FaultIndicator FaultIndicator
4.1.1.2 FaultPassageIndicator
Type: Class FaultIndicator Status: Proposed. Version 1.0. Phase 1.0. Package: LVMVSupervisor Keywords: Detail: Created on 14/10/2013. Last modified on 04/02/2014. GUID: {241A2F5D-4813-41b1-8E8C-AEB1028282DD} Device that indicates the presence and direction of a fault current in the cables where the device is located. Custom Properties
isActive = False
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 29 of 53
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public FaultPassageIndicator
Public FaultIndicator
Attributes
Attribute Notes Constraints and tags
currentAbsence CurrentFlow Public
Absence of current threshold (Iaus). Settings: 5A.
Default:
faultDetectionTime Time Public
Time to detect fault (T0). Fixed: 50 ms. Default:
groundCurrentLimit CurrentFlow Public
Residual current threshold for phase-ground faults (I0). Adjustable: 0,4 - 2 A with steps of 0.1 A
Default:
groundVoltageLimit PU Public
Residual voltage threshold for phase-ground faults (U0). Fixed: 0.02 p.u. referred to U0.max
Default:
phaseCurrentLimit CurrentFlow Public
Phase current threshold for poly-phase faults (Imax). Required settings: 500 A / 250 A / 130 A
Absence of voltage threshold (Uaus). Settings: 6 kV phase.
Default:
voltageAbsenceMinTime Time Public
Minimum time of absence of voltage/current (T2). Adjustable: 1 - 25 s with steps of 1s
Default:
voltageAbsencePerTime Time Public
Time to consider absence of voltage/current (T1). Fixed: 15 s.
Default:
The Figure 14 below shows the relationships among the proposed classes in DISCERN for this functionality (in yellow), and existing CIM classes (in light brawn).
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 30 of 53
Figure 14 GNF B6 class diagram
4.1.2 B7bd LV grid monitoring for future power quality analysis- GNF
For the implementation of sub-functionality B7bd related to LV grid monitoring for further power quality analysis, the following new classes have been proposed for CIM extensions:
LVsupervisor
SecondarySubstation
class MVSuper v isor
MVSuper v isor
Fault Indica tor
RemoteUnit
+ remoteUnitType :RemoteUnitType [0..1]
IdentifiedObject
RemotePoint
RemoteContr ol
+ actuatorMaximum :Float [0..1]
+ actuatorMinimum :Float [0..1]
+ remoteControlled :Boolean [0..1]
RemoteSour ce
+ deadband :Float [0..1]
+ scanInterval :Seconds [0..1]
+ sensorMaximum :Float [0..1]
+ sensorMinimum :Float [0..1]
IdentifiedObject
Measur ementVa lue
+ sensorAccuracy :PerCent [0..1]
+ timeStamp :DateTime [0..1]
Sensor
Cur r entTr ansfor mer
+ accuracyClass :String [0..1]
+ accuracyLimit :PerCent [0..1]
+ coreBurden :ActivePower [0..1]
+ ctClass :String [0..1]
+ usage :String [0..1]
Sensor
Potent ia lTr ansfor mer
+ accuracyClass :String [0..1]
+ nominalRatio :Float [0..1]
+ ptClass :String [0..1]
+ type :PotentialTransformerKind [0..1]
FaultPassageIndicator
+ currentAbsence :CurrentFlow
+ faultDetectionTime :Time
+ groundCurrentLimit :CurrentFlow
+ groundVoltageLimit :PU
+ phaseCurrentLimit :CurrentFlow
+ resetTime :Time
+ restorationTime :Time
+ voltageAbsence :Voltage
+ voltageAbsenceMinTime :Time
+ voltageAbsencePerTime :Time
Auxil ia r y Equipment
Equipment
Connection between electrical network
and measurements/alarms/controls
AssetContainer
EndDev ice
+ amrSystem :String [0..1]
+ installCode :String [0..1]
+ isPan :Boolean [0..1]
+ isVirtual :Boolean [0..1]
+ timeZoneOffset :Minutes [0..1]
Ana logVa lue
Ana log
IdentifiedObject
Measur ement
+ measurementType :String [0..1]
+ phases :PhaseCode [0..1]
+ unitMultiplier :UnitMultiplier [0..1]
+ unitSymbol :UnitSymbol [0..1]
IdentifiedObject
Power Sy stemResour ce
Discr ete
IdentifiedObject
Va lueAlia sSet
IdentifiedObject
Va lueToAlia s
Discr eteVa lue
The use case does
not define a register
function. The
association with
EndDevice could
provide this
function.
IdentifiedObject
ACDCTer mina l
+ connected :Boolean [0..1]
+ sequenceNumber :Integer [0..1]
Data collector is out
of the scope of the
CIM model
(communication
model).
+Supervisor
0..1
+RemoteUnit 0..1
+RemotePoints 0..*
+RemoteUnit 1
+MeasurementValue 1
+RemoteSource 0..1
+PowerSystemResource 0..1
+Measurements 0..*
+Supervisor
0..1
+FaultIndicator
0..*
+Measurements 0..*
+Terminal 0..1
+Analog
1
+AnalogValues
0..*
+ValueAliasSet 0..1
+Discretes 0..*
+ValueAliasSet
1
+Values
1..*
+Discrete
1+DiscreteValues
0..*
+Supervisor
0..1
+CurrentTransformer 0..*
+Supervisor
0..1
+PotentialTransformer 0..*
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 31 of 53
4.1.2.1 LVSupervisor
Type: Class Meter Status: Proposed. Version 1.0. Phase 1.0. Package: LVMVSupervisor Keywords: Detail: Created on 20/10/2013. Last modified on 04/02/2014. GUID: {410FE823-F617-4958-9291-048522B01DC9} This IED collects voltage and current measures from sensors in the LV side of secondary substations, perform registrations of energy (meter), measures and events, and generate alarms when some voltages or currents are out of margins. Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public LVSupervisor
Public Meter
Association Unspecified
Public LVSupervisor LVSupervisor
Public SecondarySubstation SecondarySubstation
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 32 of 53
4.1.2.2 SecondarySubstation
Type: Class Substation Status: Proposed. Version 1.0. Phase 1.0. Package: LVMVSupervisor Keywords: Detail: Created on 20/10/2013. Last modified on 04/02/2014. GUID: {6C4C2B21-AE53-4140-93B3-BD1F66015EDF} An assembly of High Voltage Switchgear, Transformer and LV Switchgear in an enclosure where the lower voltage is 400/230V. The definition includes transformer substation. Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public SecondarySubstation
Public Substation
Association Unspecified
Public LVSupervisor LVSupervisor
Public SecondarySubstation SecondarySubstation
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 33 of 53
The Figure 15 below shows the relationships among the proposed classes for this functionality (in
yellow) and existing CIM classes (in light brawn).
Figure 15 GNF B7bd class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 34 of 53
4.2 DISCERN CIM extension 2- IBDR use cases on LV monitoring and calculation of technical and non-technical losses
IBDR leading sub-functionalities B6 and B9b address MV automation level and calculation of technical and non-technical losses in LV distribution grid respectively. After reviewing the packages and classes currently present in CIM IEC 61970-301 and IEC 61968-11, some extensions have been identified in order to fully represent the sub-functionalities lead by IBDR. The suggestions for extensions are mainly three new classes which are related to calculations. These classes are needed to locate the algorithms used in the Use Case. The first class, “CalculationCore” would be an upper/abstract class. The other two, “Estimator”” and “LossesCalculator” would link below the latter through an inheritance relation. The “Estimator” should contain all processes needed to operate the information to estimate the consumption. The second one, “Losses Calculator” would represent the processes needed to calculate the technical and not technical losses.
Table 8 IBDR CIM/DCIM extension proposal
PACKAGE/Extension CLASS Attribute CLASS DESCRIPTION
DISCERNSmartDCIM
This packet has been included following the IEC 61968-11 recommendations: "If an extension is made in UML model, such extension should be made in a different package as a separate model layer or context rather than be added or modified into CIM model directly. A “targetNamespace” tagged value may be used for this purpose if such extension is meant for an XSD generation."
Calculation Core
Upper/abstract class to aggregate the two classes Estimatorand Losses Calculator
Estimator
This class will contain all the processes need to operate the information needed to estimate the consumption. The information flow, mainly previous Smart Meter reports, is represented in the model by the link established between “PowerSystemResource” and “Calculator Core”
Losses Calculator
This class should represent the processes needed to calculate the technical and not technical losses. The information path needed, basically to perform power flow calculations (electrical measurements and network parameters) is also represented by the link between “PowerSystemResource” and “Calculation Core”.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 35 of 53
4.2.1 B6 MV Automation Level Decision - IBDR
For the implementation of IBDR leading sub-functionality B6 related to optimal level of MV network automation, following new classes have been proposed for CIM extensions:
4.2.1.1 CalculationCore
Type: Class Status: Proposed. Version 1.0. Phase 1.0. Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-07. Last modified on 2014-03-07. GUID: {2EA46990-EC48-4b86-940A-52EC43B20E4B} Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public Estimator
Public Calculation Core
Association Source -> Destination
Public Devices required to analyze area PowerSystemResource
Public Calculation Core
Generalization Source -> Destination
Public Losses Calculator
Public Calculation Core
The Figure 16 below shows the relationships among the proposed classes for this functionality (in yellow) and existing CIM classes (in light brawn).
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 36 of 53
Figure 16 IBDR B6 class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 37 of 53
4.2.2 B9b Calculation of technical and non-technical losses- IBDR
For the implementation of IBDR leading sub-functionality B9b related to calculation of technical and non-technical losses following additional classes are proposed for CIM extensions:
4.2.2.1 Estimator
Type: Class Software Simulation Status: Proposed. Version 1.0. Phase 1.0. Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-07. Last modified on 2014-03-07. GUID: {653AFD07-6E9B-4df5-9074-00A96D3156F8} Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public Estimator
Public Calculation Core
Association Source -> Destination
Public Estimator
Public Information required from devices Losses Calculator
4.2.2.2 LossesCalculator
Type: Class Software Simulation Status: Proposed. Version 1.0. Phase 1.0. Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-07. Last modified on 2014-03-07. GUID: {5C4C1694-529C-45c4-864E-0E84840D29D2} Estimation of the losses of the analyzed area Custom Properties
isActive = False
Connections
Connector Source Target Notes
Generalization Source -> Destination
Public Losses Calculator
Public Calculation Core
Association Source -> Destination
Public Estimation Algorithm
Public Information required from devices Losses Calculator
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 38 of 53
The Figure 17 below shows the relationships among the proposed classes for this functionality (in yellow) and existing CIM classes (in light brawn).
Figure 17 IBDR B9b class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 39 of 53
4.3 DISCERN CIM extension 3- SSEPD use cases on LV Supervision
SSEPD leading use case in the sub-functionality B7bd addresses LV networks monitoring at an
enhanced level and develops analytical approaches to both forecast power flows using scenarios and to
establish the optimal level of monitoring required to facilitate such forecasting. After reviewing the packages and classes currently present in CIM IEC 61970-301 and IEC 61968-11, some extensions have been identified in order to fully represent the sub-functionalities lead by SSEPD. The suggestion of the extension primarily is deals with three new classes related to substation and end-point (metering) measurements and front-end SCADA processing.
Table 9 SSEPD CIM/DCIM extension proposal
PACKAGE/Extention CLASS Attribute CLASS DESCRIPTION
DISCERNSmartDCIM
This packet has been included following the IEC 61968-11 recommendations: "If an extension is made in UML model, such extension should be made in a different package as a separate model layer or context rather than be added or modified into CIM model directly. A “targetNamespace” tagged value may be used for this purpose if such extension is meant for an XSD generation."
SubstationMonitor
Special classes may be needed for aggregation of energy profiles at the substation level for the further analysis
EndPointMonitor
Specific monitor classes required to represent end point real time measurements for energy profile calculations
FrontEndProcessor
Information objects required to present SCADA frontend calculations and transfer to BAU applications in the B7bd use case
4.3.1 B7bd SSEPD MV Controller
For the implementation of SSEPD leading sub-functionality B7bd related to flexible LV network monitoring and supervision following new classes have been proposed for CIM extensions:
4.3.1.1 EndPointMonitor
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-06. Last modified on 2014-03-06. GUID: {842F48E6-4DB7-4ce7-8B54-B0B903DA340D}
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 40 of 53
Custom Properties
isActive = False
Connections
Connector Source Target Notes
Association Unspecified
Public EndPointMonitor
Public EndDevice
Attributes
Attribute Notes Constraints and tags
remoteUnitType RemoteUnitType Public [0..1]
Type of remote unit. Default:
4.3.1.2 FrontEndProcessor
Type: Class Status: .Version . Phase . Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-06. Last modified on 2014-03-06. GUID: {C6EBBE31-C2E8-45dc-968B-26AC2E121B62} Custom Properties
isActive = False
Connections
Connector Source Target Notes
Association Unspecified
Public FrontEndProcessor
Public CommunicationLink
Attributes
Attribute Notes Constraints and tags
remoteUnitType RemoteUnitType Public [0..1]
Type of remote unit. Default:
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 41 of 53
4.3.1.3 SubstationMonitor
Type: Class Status: .Version . Phase . Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-06. Last modified on 2014-03-06. GUID: {4B56E936-F706-4d07-B089-48185CD3F8DC} Custom Properties
isActive = False
Connections
Connector Source Target Notes
Association Unspecified
Public SubstationMonitor
Public RemoteUnit
Association Unspecified
Public SubstationMonitor
Public Sensor
Association Unspecified
Public SubstationMonitor
Public CommunicationLink
Attributes
Attribute Notes Constraints and tags
remoteUnitType RemoteUnitType Public [0..1]
Type of remote unit. Default:
The Figure 18 below shows the relationships among the proposed classes for this functionality (in yellow) and existing CIM classes (in light brawn).
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 42 of 53
Figure 18 SSEPD B7bd class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 43 of 53
4.4 DISCERN CIM extension 4 - VTF use case on Optimized AMR
Data Collection
Vattenfall acting as a leader of use case named Optimized AMR data collection and analysis using virtualized as well as physical concentrators. After reviewing the packages and classes currently present in CIM IEC 61970-301 and IEC 61968-11, some extensions have been identified in order to fully represent the sub-functionalities lead by Vattenfall. The suggestion of the extension in this case is based on five new classes related to system objects responsible for aggregate, manage, analyze and alarm handling. These are described below:
Table 10 SSEPD CIM/DCIM extension proposal
PACKAGE/Extension CLASS Attribute CLASS DESCRIPTION
DISCERNSmartDCIM
This packet has been included following the IEC 61968-11 recommendations: "If an extension is made in UML model, such extension should be made in a different package as a separate model layer or context rather than be added or modified into CIM model directly. A “targetNamespace” tagged value may be used for this purpose if such extension is meant for an XSD generation."
MeterConcentrator
Asset that performs the metering concentrator role off one or several meter(s). Used for single point access to information from one or several meters.
AmiHeadEnd
A system for data management of meter readings, events and alarms. Not all events collected from the smart meters and Meter Data Concentrator are exported to the Enterprise systems. The system monitors the data collection from the communication system.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 44 of 53
PerformanceEvaluationReportingDatabase
An in-house developed web based application and database to handle the events, alarms and to follow up the collection performance of meter readings, according to the terms and conditions in the data collection service contract Integrated with AMI Head end (Titanium) by VPN tunnel using XML file format.
MeterDataManagementSystem
Meter Data Management System for all meters, as well as customer information (from CIS) and information of how the meter is related to the secondary substations. The system also is the data warehouse for all the meter readings, except for those customers (>63A fuse) obliged to have an hourly meter.
InformationSystemDevice
Container for system devices that represent a physical system device component.
4.4.1 B9a AMR Data Collection and Analysis - VTF
For the implementation of Vattenfall leading sub-functionality B9a case named Optimized AMR data collection and analysis using virtualized as well as physical concentrators following new classes have been proposed for CIM extensions:
4.4.1.1 MeterConcentrator
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-19. Last modified on 2014-03-21. GUID: { C6EBBE31-C2E8-45dc-768B-26AC2E121B62}
Custom Properties
Connections
Connector Source Target Notes
Association Public Public
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 45 of 53
Connector Source Target Notes
Source -> Destination MeterReading MeterConcentrator Name: collected by Association Unspecified
Public Meter
Public MeterConcentrator
Association Source -> Destination
Public EndDeviceEvent
Public MeterConcentrator
Name: reported to
Association Source -> Destination
Public MeterConcentrator
Public AmiHeadEnd
Name: report to
Association Source -> Destination
Public MeterConcentrator
Public AmiHeadEnd
Name: managed by
Association Source -> Destination
Public MeterConcentrator
Public AmiHeadEnd
Name: submit meter readings to
Genaralization Source -> Destination
Public MeterConcentrator
Public InformationSystemDevice
Attributes
Attribute Notes Constraints and tags
Operators
Attribute Notes Constraints and tags
getMeterReading Public
To realize on demand readings function call
Default
setMeterPowerOnStatus Public
To realize the power on/off function Default
forwardReport To forward reports (Alarms & Events) from Meter
Default
4.4.1.2 AmiHeadEnd
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: Detail: Created on 2014-03-20. Last modified on 2014-03-21. GUID: { C6EBBE31-C2F8-45dc-968B-26AC2E121B62} Custom Properties
Connections
Connector Source Target Notes
Association Source-> Destination
Public MeterConcentrator
Public AmiHeadEnd
Name: report to
Association Source-> Destination
Public MeterConcentrator
Public AmiHeadEnd
Name: managed by
Association Public Public Name: submit meter
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 46 of 53
Connector Source Target Notes
Source-> Destination MeterConcentrator AmiHeadEnd readings to Generalization Source-> Destination
Public AmiHeadEnd
Public InformationSystemDevice
Association Destination -> Source
Public AmiHeadEnd
Public MeterDataManagementSystem
Name: obtain meter readings from
Association Source-> Destination
Public AmiHeadEnd
Public PerformanceEvaluationReportingDatabase
Name: obtain meter readings from
Attributes
Attribute Notes Constraints and tags
Default:
Operators
Attribute Notes Constraints and tags
filterGeneralEvents Private operator that realize a function (filter out specified events)
Default
forwardMeterReadings Public operator that forwards meter readings from Meter concentrator to MDMS
Default
forwardReport Public Operator that handles what reports that will be forward by using filterGeneralEvents().
Default
getMeterReading Public operator that gets an on-demand reading from meters via the meter concentrator.
Default
4.4.1.3 PerformanceEvaluationReportingDatabase
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: None Detail: Created on 2014-03-20. Last modified on 2014-03-21. GUID: { C6EBBE31-C2F8-45dc-967B-26AC2E121B62} Custom Properties
Connections
Connector Source Target Notes
Association Source-> Destination
Public AmiHeadEnd
Public PerformanceEvaluationReportingDatabase
Name: provide meter information to
Generalization Source-> Destination
Public PerformanceEvaluationReportingDatabase
Public InformationSystemDevice
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 47 of 53
Attributes
Attribute Notes Constraints and tags
None
4.4.1.4 MeterDataManagementSystem
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: None Detail: Created on 2014-03-20. Last modified on 2014-03-21. GUID: { C6EBBE31-C2F8-44dc-968B-26AC2E121B62} Custom Properties
Connections
Connector Source Target Notes
Association Destination -> Source
Public AmiHeadEnd
Public MeterDataManagementSystem
Name: obtain meter readings from
Generalization Source-> Destination
Public MeterDataManagementSystem
InformationSystemDevice
Attributes
Attribute Notes Constraints and tags
4.4.1.5 InformationSystemDevice
Type: Class Status: . Version . Phase . Package: DISCERNSmartDCIM Keywords: None Detail: Created on 2014-03-18. Last modified on 2014-03-21. GUID: { C6EBBE31-C2E8-45dc-968B-26AC2E121B62} Custom Properties
Connections
Connector Source Target Notes
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 48 of 53
Connector Source Target Notes
Generalization Source-> Destination
Public MeterConcentrator
Public InformationSystemDevice
Generalization Source-> Destination
Public AmiHeadEnd
Public InformationSystemDevice
Generalization Source-> Destination
Public PerformanceEvaluationReportingDatabase
Public InformationSystemDevice
Generalization Source-> Destination
Public MeterDataManagementSystem
Public InformationSystemDevice
Generalization Source-> Destination
Public InformationSystemDevice
Public AssetContainer
Attributes
Attribute Notes Constraints and tags
None
The Figure 19 below shows the relationships among the proposed classes for this functionality (in yellow) and existing CIM classes (in light brawn).
Figure 19 VTF B9a class diagram
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 49 of 53
5 Conclusion and summary of results
DISCERN Semantic Model is an important step towards the DISCERN goals of achieving optimal level of intelligence in European distribution networks and suggesting mechanisms for knowledge sharing among the DSOs. It creates an understandable approach and methodology for creating common, consistent and standardized set of semantics in the form of the CIM/DCIM based classes and relationships for the DISCERN leading sub-functionalities.
The leading use cases were aligned with CIM/DCIM standards. Packages/classes of this standard information model were prioritized for the application in each of the leading sub-functionality. Requirements were identified in the application of sub-functionalities that were currently not covered in the standard. In order to fulfil these requirements either suggestions have been made for extension of the standard with new classes or existing extensions proposed in the literature have been reviewed for application.
The main results of this work are:
- General common understanding and familiarization to the CIM IEC 61970-301 and IEC 61968-11 for all DISCERN DSO partners with different levels of existing experience have been gained. This will make easier for DSOs to define interoperable solutions based on a standard information model.
- Alignment of the DISCERN information model to the CIM/DCIM for all selected leading use cases
- Identification of relevant/prioritized classes from CIM
- Identification of missing classes in CIM that need to be added (extended) in order to support the DISCERN leading demo projects and enhancement of CIM
- Systematic, coherent and standardized definition of DISCERN demo project information models i.e., in the form of CIM extensions
- The above will enable a systematic and consistent way of comparing the related partner solutions with the DISCERN project
- Standardized documentation of the information models of all selected use cases of the related demo projects
- Finally standardized CIM modelling of the DSO use cases will produce coherent and seamless knowledge repository in the project and enable important DISCERN objective of the knowledge sharing among the partner DOSs
The resulting DISCERN semantic model will be an input to task T5.2 where it will be evaluated for the application in learning sub-functionalities. The consistent and standardized definition of information models will help to compare the leading sub-functionalities with learning sub-functionalities in a systematic and coherent way. Therefore it will assist in the crucial task of comparing different solutions in the DISCERN project.
The results of this work will be also an input to tasks T5.3 and T7.1 where the technical architecture specification will be developed for the DISCERN project.
Moreover, the results of this task are aimed at producing feedback for standardization activity for CIM in particular for the working groups WG13 and WG14 of the IEC technical committee TC 57. This feedback will be summarized once DISCERN learning solutions have been aligned to the DISCERN semantic model.
D5.1 DISCERN Semantic Model
DISCERN_WP5_D5.1_20140521 V31 Page 50 of 53
6 References
6.1 Project documents
[DOW] – DISCERN Description of Work
[D1.1] – Deliverable 1.1: “List of agreed KPIs with associated metrics and refined smart grids
functionalities list”
[D4.2] – DISCERN Deliverable D4.2 New system functionality
6.2 External documents
[IEC 61970-301] – IEC 61970-301 Energy management system application program interface (EMS-
API) - Part 301: Common information model (CIM) base
[IEC 61968-11] – Application integration at electric utilities - System interfaces for distribution
management - Part 11: Common information model (CIM) extensions for distribution
[McMooran2007] – McMorran, Alan W. "An introduction to iec 61970-301 & 61968-11: The common
information model." University of Strathclyde (2007)
[Brunel2011] – Novel processes for smart grid information exchange and knowledge representation
using the IEC common information model. http://bura.brunel.ac.uk/handle/2438/7671
[GEEnvironment2013] – CIM for Environmental Data: A CIM Extension for Environment data.
Available through: https://cimphony.com/content/2013/01/cim-for-environmental-data/
[Uslar2012] – M. Uslar, M. Specht, S. Rohjans, J. Trefke, and J.M. Gonzalez Vazquez,The Common
Information Model (CIM): IEC 61968/61970 and 62325 - A practical introduction to the CIM Series
(Power Systems Series), vol. 66, Springer Berlin Heidelberg, 2012.
[Uslar2013] – M. Uslar, M. Specht, C. Dänekas, J. Trefke, S. Rohjans, J.M. González, C. Rosinger,
and R. Bleiker, Standardization in Smart Grids –Introduction to IT-Related Methodologies,
Architectures and Standards, (Power Systems Series), Springer Berlin Heidelberg, 2013.
[IEC 62357] – IEC 62357: TC 57 Architecture – Part 1: reference architecture for TC 57, IEC TC57
Standard, Sept. 2009.
[IEC SGCG2011] – Smart Grid Coordination Group (SGCG) Report on Standardization Gaps
Prioritization for the Smart Grid, version 1.2, CEN, CENELEC,and ETSI, Nov. 2011.