smart rural grid€¦ · upc francesc girbau cga brian sutherland deliverable beneficiaries wp /...

Smart_Rural_Grid FP7 project – Grant agreement nº. 619610

0011This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement no. 619610.

Smart_Rural_Grid

"Smart ICT-enabled Rural Grid innovating resilient electricity distribution

infrastructures, services and business models"

Deliverable nº: D5.1

Deliverable name: Database concept

Version: 1.4

Release date: 22/09/2014

Dissemination level: PU (PU, PP, RE, CO, Internal)

Status: Draft

Author: KISTERS

Contributors UPC, CGA, EYPESA

Executive summary

This deliverable describes the used database concept for the Smart_Rural_Grid project, the Common Information Model (CIM) and the used CIM classes.


Deliverable D 5.1 Database concept, Version 1.4 of 45

Document history

Version Date of issue Content and changes Edited by

1.0 12/09/2014 Draft version Volker Bühner,

Ralf Scharnow

1.1 16/09/2014 Review Francesc Girbau Llistuella

1.2 16/09/2014 Adapted to comments of reviewers Volker Bühner,

Ralf Scharnow

1.3 19/09/2014 Adapted to comments of reviewers Volker Bühner,

Ralf Scharnow

1.4 21/09/2014 Review completed Volker Bühner,

Ralf Scharnow

Peer reviewed by:

Partner Contributor

EYPESA Ramón Gallart

UPC Francesc Girbau

CGA Brian Sutherland

Deliverable beneficiaries

WP / Task Responsible

T 4.1 ZIV

T 5.3, 5.4 KISTERS

T 6.1 CGA

T 8 SMARTIO



Table of contents

1 Introduction ...................................... .................................................................... 7

2 Market role model and markets ..................... ...................................................... 8

2.1 The European market role model (ENTSO-E) 8

2.2 Energy only markets 11

2.3 Reserve power and ancillary service markets 12

2.4 Grid fees 13

2.5 Transparency requirements 14

2.6 Future and local markets 16

2.7 Implications for the Smart Rural Grid project 17

3 Solution Concept .................................. .............................................................. 19

3.1 Pilot installation - EYPESA 19

3.2 Pilot simulation – SWRO 20

3.3 Implication for the database concept 21

4 The CIM Concept ................................... ............................................................. 23

4.1 CIM Motivation 23

4.2 CIM and the Smart Rural Grid project 25

4.3 Used CIM classes and packages 26

4.3.1 Topology 28

4.3.2 Sub Station and IDPR 29

4.3.3 Switches 30

4.3.4 Set Points 32

4.3.5 Measurements 33

4.3.6 IDPR 37

4.3.7 Power Transformer 39

4.3.8 Line segments 39

4.3.9 EquivalentInjection 41

4.3.10 Generation 41

4.3.11 Loads 42

5 Annex ............................................. ..................................................................... 43



5.1 CIM classes, tables 43

5.1.1 Description of Measurements properties 43

5.1.2 ACDCConverter details 43

5.2 CIM Voltage Source Converter 44

5.3 StaticVarCompensator 45



Abbreviations and Acronyms

Acronym Description

APX Amsterdam Power Exchange

BMS Battery Management System

CA Consortium Agreement

CFS Certificate on the financial statements

CGMES Common Grid Model Exchange Standard of ENTSO-E (CGMES_2: version 2 of this standard)

CHP Combined Heat and Power

CIM Common Information Model (IEC)

CSC Current source converter

CO Dissemination Confidential, limited to project participants

D Deliverable

DPLC Digital Power Line Carrier

DoW Description of work (annex I of the Grant Agreement)

EC European Commission

EMS Energy Management System

EEX European Energy Exchange (future market)

EPEX European Power Exchange (spot market)

EXAA Energy Exchange Austria

FDR Final financial distribution report

GA Grant Agreement

ID Internal discussion or report

IDPR Intelligent Distributed Power Router

LV Low Voltage level (<= 400V)

MM Meeting Minutes

MR WPL monthly report

MV Medium Voltage level (>400V, e.g. 10kV voltage level)

OTC Other the counter (bilateral)

PC Project Coordinator

PFR Project Final Report

PMC Project Management Committee

PO Project Officer

PP Dissemination restricted to other FP7 Programme participants



Acronym Description

PPR Partner’s periodic report (contractual, M12, M24, M36)

PR Partner’s progress report (internal, at M6, M18, M30)

PT Project presentation

PU Dissemination Public

QM Quality Management

QR WPL Quarterly report

RE Dissemination restricted to a group specified by the consortium

RTU Remote terminal unit

TMT Technical Management Team

ToC Table of Contents

TS Time sheet

UML United Modelling Language

VSC Voltage source converter

WP Work package

WPL Work package leader



1 Introduction

The Smart_Rural_Grid project is aimed at developing an innovative smart grid

approach targeted to the particular conditions of rural energy distribution networks.

These special conditions include the type of grid assets, the addressed markets and

business cases and the available communication bandwidth.

Chapter 2 analyses the addressable business cases and lists stakeholder and market

roles which have to be taken into account for the communication concept of a Smart

Rural Grid. The required communication between the several stakeholders and their

involved systems results in a solution concept with several control levels that is

described in Chapter 3. The Common Information Modell (CIM) is introduced and

motivated in Chapter 4, as well as the used classes for the project.



2 Market role model and markets

This chapter describes the different business cases for a smart rural grid and its

components, like the power router. In general it can be distinguished between those

business cases for the Distribution Network Operator (DNO) and those for a sales, a

retail company or an Energy Service Company (ESCo).

2.1 The European market role model (ENTSO-E)

The “European Network of Transmission System Operators for Electricity” (ENTSO-E)

has developed and described a harmonized electricity market role model to facilitate

the dialogue between the market participants by identifying the roles and their tasks

and responsibilities. In this document and in the Smart Rural Grid project the market

roles are used as described in the ENTSO-E model [1] and displayed in the following

picture as an UML diagram:

[1] www.entsoe.eu, file “harmonised-role-model-2014-01_approved.pdf



Figure 1: ENTSO-E market model [1]



For this project the following stakeholders have been identified [1]:

Role name Description

Control Area Operator

Responsible for:

1. The coordination of exchange programs between its related Market Balance Areas and for the exchanges between its associated Control Areas.

2. The load frequency control for its own area. 3. The coordination of the correction of time deviations.

Balance Responsible Party

A party that has a contract proving financial security and identifying balance responsibility with the Imbalance Settlement Responsible of the Market Balance Area entitling the party to operate in the market. This is the only role allowing a party to nominate energy on a wholesale level. Additional information: The meaning of the word "balance" in this context signifies that that the quantity contracted to provide or to consume must be equal to the quantity really provided or consumed. Equivalent to "Program responsible party" in the Netherlands. Equivalent to "Balance group manager" in Germany. Equivalent to "market agent" in Spain.

Consumer A party that consumes electricity. This is a type of party connected to the grid.

System Operator

A party that is responsible for a stable power system operation (including the organisation of physical balance) through a transmission grid in a geographical area. The System Operator will also determine and be responsible for cross border capacity and exchanges. If necessary he may reduce allocated capacity to ensure operational stability. Transmission as mentioned above means "the transport of electricity on the extra high or high voltage network with a view to its delivery to final customers or to distributors. Operation of transmission includes as well the tasks of system operation concerning its management of energy flows, reliability of the system and availability of all necessary system services." Additional obligations may be imposed through local market rules.

Producer A party that produces electricity. This is a type of party connected to the grid.

Energy Service Company (ESCo)

A natural or legal Person that delivers Energy services and/or other Energy Efficiency Improvement Measures in a user's facility or premises, and accepts some degree of financial risk in so doing. The payment for the services delivered is based (either wholly or in part) on the achievement of Energy Efficiency improvements and on the meeting of the other agreed performance criteria.

Table 1: Stakeholders and market roles



2.2 Energy only markets

Power future, spot and intraday markets are energy only markets where parties bid and

ask the scheduled delivery of electrical power. The market place is either bilateral

“other-the-counter” (OTC) or an exchange stock market like the EPEX, APX, EXAA or

EEX. The products are defined in power per time in terms as a schedule. This could

vary from a single 15 minute contract to an annual base. The price for each product

varies other the time. By storing electrical energy, generating power in high price

periods and shifting load in times of lower price (Demand Side Management – DSM)

this volatility of prices could be used to generate business models. The following

figures show the EPEX spot price and the distribution function over the year 2013:

Figure 2: EPEX power spot price for 2013



Figure 3: Distribution of EPEX power spot price for 2013

Beside shifting generation and load in time due to forecasted prices this flexibility could

be used intraday to avoid penalties. It is the task of a balance responsible party to

balance in every time step of 15 minutes between the consumption and generation.

Actually this has to be done day ahead and described by a schedule. Due to forecast

errors and unpredictable outages deviations between the real situation and the day

before predicted schedule are normal. These deviations result in charges for each

deviation in each 15 minute time step. It is a business case to use generation and load

flexibility to minimize these deviations during the day, based on a short term forecast

and the knowledge of the actual load and generation situation.

2.3 Reserve power and ancillary service markets

Besides offering power as energy only the flexibility of generation or load could be used

also on reserve power markets. These are quite different in the European countries but

could be summarized as spinning or non-spinning reserve. Here a price is paid for the

provision of power and a second price for the later delivery on a TSO request.



Figure 4: Example of secondary reserve (spinning reserve), energy price, 2013

In the meantime virtual power plants and reserve power pool allow the aggregation of

smaller generators to address the markets in competition with large scale single power

plants. Especially for CHP the provision of reserve power is often already included in

investment calculations and thus a needed business case in the later operation.

The different reserve power products are examples for ancillary services. Other

services are frequency control, black start capability, grid loss compensation, voltage

control and reactive power balancing.

2.4 Grid fees

The DSO has to pay a special network use fee for the highest 1/4h-power peak of the

year to the TSO. Since this fee is for medium voltage often in the range of some 10.000

EUR/MW the generators and loads (or a pool of them) could minimize this peak by an

active load and generation management. To address this business case these hours of

high grid load have to been forecasted.

Most regulatory frameworks for the definition of grid fees assume still a constant load

while the real load behaves volatile, as the following figure shows:



Figure 5: Assignment of grid fees in relation to assumed (left) and real (right) grid load

As a result time variable grid fees are in discussion to motivate a more grid friendly

behaviour of loads and generation. Therefore a communication between the DSO and

the loads and generators would be required, at least to broadcast a price / fee signal in

quasi real time.

2.5 Transparency requirements

The enormous increase of dispersed electrical power generators, renewable and CHP,

have led to a situation for the TSO, where the actual grid situation is more complicate

to predict. As a result additional transparency requirements for smaller generators have

been published by several regulation authorities. On the European level the ENTSO-E

reserve resource process (ERRP) is an example for this, as shown in the following

figure [2]:

[2] www.entsoe-eu, file “errp2-guide-v5r0_approved.pdf



Figure 6: ENTSO-E reserve resource process (ERRP) [2]

Within this process there are basically four roles participating:

� The Resource Provider (RP) who may supply the reserves and provide the daily market schedules for consumption and generation.

� The Reserve Allocator (RA), who informs the market of reserve requirements, receives tenders against the requirements, determines what tenders meet requirements and assigns the tenders.

� The System Operator (SO) who has to ensure that the network under his responsibility is capable of satisfying the delivery of the market requirements and can respect its security requirements. In this context there may be System Operator - System Operator interactions.

� The Merit Order List Responsible (MOL-Responsible) manages the available tenders for all Acquiring System Operators and establishes the order in which the tendered reserves can be activated.



As a result several time series and information have to be sent by the asset operator to

the TSO. In case of the German regulation [3] about 15 time series for every generator

with more than 10 MW have to be transmitted:

Figure 7: Required times series for ERRP in the German market [3]

Actually there is a discussion about including also medium voltage and in the future

maybe also low voltage generators. So this might also be relevant for IDPR.

2.6 Future and local markets

Several studies, like the German “dena system service study 2030”, published

September 2014, expect local markets to occur in the near future. This is especially the

case for local ancillary services like shown in [4]:

[3] Bundesnetzagentur (German regulatory authority), BK6-13-200

[4] B.M Buchholz, V. Buehner: “Provision of Ancillary Services by RES”, CIGRE C6-116-210, Paris, 2010



Ancillary serviceTSO DSO generators loads storages TSO DSO generators loads storages

Frequency control x x x x xSpinning reserve x x x x xStanding reserve x x pumped hydro x x x x xVoltage control x x x x x x x xreactive power balancing x x x x x x xBlack start capability x x pumped hydro x x x xGrid loss compensation x x x x x x x

status quo smart grids

Table 2: Actual (left) and proposed future (right) allocation of ancillary services [4]

Therefore the DSO may also get the task of building a local market place for those

products which may then be offered by ESCo or a Balance Responsible Party (BRP):

Figure 8: Local markets and the role of DSO and BRP

2.7 Implications for the Smart Rural Grid project

The several business cases with different markets and the transparency requirements

led to a variety of different time series and master data which have to be exchanged

with different market roles and counterparties. Not only actual or measured data but

also forecasted values, prices, counterparty information and topology relations have to

be handled. Therefore several standards and format definitions have been already

launched on European and national levels. As a consequence not only technical

information but also price and market role information must be handled by a common

database concept. The name of the used parameters and the way of representing



information should be in line with common used standards. This implies an object

orientated description which also allows the later definition of yet undefined

parameters.



3 Solution Concept

The choice of a database concept is directly related to the used overall solution

concept. As already stated in the projects proposal we are going to apply a 4 level

approach:

TSO ESCO Markets

Virtual Power Plant: Forecasting, Optimization, Scheduling

Grid control centre / SCADAEnergy market systems /

Balancing group

IDPR, CHP, inverter control (RES), battery control, tap settings

Single asset (generator, load, storage)

Role: retail-tradingRole: DSO

1

2

3

4

Control

level

TSO and National

markets level

High voltage

DSO and Regional

markets level

Medium voltage

Local level

Low voltage

Rural Smart Grid

Control Centre

Central

Street level

Asset

Figure 9: Control level of the system

3.1 Pilot installation - EYPESA

In the case of EYPESA the new devices will be monitored to study their behaviour and

get to conclusions based on the parameters that are determined functional modes of

each case, restrictions, stress efficiency of the telecommunications network, resources,

and operations in control centre room.

The following solution concept will be applied. In terms of the partner’s responsibilities

and interfaces between the partner`s systems it is already introduced in Deliverable D

2.4 “Integration with the control room”:



Local

EMSRTU-LC

RTU-TC

D

C

IDPR Sensors Switches

E

G H

EyPESA’s

Center Control

KISTERS

EMS

B

A

I

BMS

J

Distributed generation

Smart-

fuses

F

RTU-TC (Remote Terminal Unit

– Transfomer Center

RTU-TC (Remote Terminal Unit

– Local Controller

Figure 10: Solution concept

3.2 Pilot simulation – SWRO

In parallel to the pilot installation of EYPESA and taking the experiences from this

physical installation into account, SWRO will simulate the behaviour of the system with

real data.

Therefore the following use cases have been identified, which a common database

model must take into account:

• Simulation of power flows



• Influence of supplying reactive power

o allow to install more distributed generation

o avoiding invest for grid assets or extension

o reduce losses

• Influence of the installation of the IDPR (including batteries)

o allow to install more distributed generation, avoiding Invest, reduce

losses

o increase the flexibility in the local grid by the integration of local

generation (CHP, renewables, … )

o simulate use of reserve power (local and national markets)

• Compensate asymmetries, avoiding neutral loads

• Adjust the voltage as a function of feeding reactive power

• Manage and control the upstream network charges by using and control the

renewable energy resources in their own grid

• Restart grid after blackout (partial or total blackouts) by an auxiliary supply by

the IDPR and their attached batteries. They could for example maintain the

supply while other local generators power up and take over.

3.3 Implication for the database concept

Taking the requirements concerning the interface between the systems and the

common understanding of parameters into account these are basic requirements for a

common database model:

• The concept has to be open to yet undefined counterparts / systems,

parameters and structures. This promoted an object oriented solution, where

additional structures and parameters could be applied.

• The concept is not only a syntax describing parameters and relation but also a

commitment to an underlying physical model for individual objects. This is quite

obvious in case of the IDRP, which have to be addressed by different physical

models in different operation modes.



• To ensure later sales changes on a worldwide market and in the context of

commercial systems like SCADA, EMS and Smart-Meter-Systems an

international accepted standard should be used.



4 The CIM Concept

4.1 CIM Motivation

These days, systems like control centre, enterprise data administration, asset data

base etc. must integrate even though they are designed and built by different parties at

different times for different purposes. This is especially true with smart grid, which from

an IT point of view is dominated by integration requirements. At a minimum, integration

requires:

• a means of exchanging generic data.

• a mutually agreed semantic model, basically a common language.

In consequence without a common data model or concept data redundancies occur

and often the same data is repeated in various databases. If the data must be

changed, it is necessary to change the data in all relevant data base systems

simultaneously.

To improve this situation the IEC has standardized common data models (CIM) for data

management in distribution systems based on UML in IEC 61968. CIM, according to

IEC 61970 and its extension IEC 61968, offers the definitions for such a common

interface description.

Figure 11: Amount of needed data converters using (a) proprietary or (b) a common data format

Beside the reduced amount of connections and interfaces this is also a common

language which all connected systems are forced to understand:



Figure 12: CIM as a common language

The application of this standard can be made by an implementation of a CIM database,

which interfaces to the other work of system components according to the standardized

data format. With the help of a CIM database, no unnecessary redundant data must be

kept, because every component can fetch and write its data on demand. This protects

from inconsistent data e.g. missed synchronization processes in a system having

information distributed and kept in a redundant way. The CIM offers a worldwide unified

model with all the information needed for the planning and operation of the power

system management. Problem specific extensions can be added by need, which are

clearly identified as non-standard by the usage of own namespaces. The complete

model is available as an UML model, more precisely in a class model according to

UML specification. The packet based structure arranges all used classes according to

their field of application.

Several IEC working groups and the ENTSO-E use the CIM to define mutually

consistent standards for exchange of information.

This is the reason, why we have chosen CIM as the common database concept.

However, this is a theoretical approach to ensure the future sales chances of the

system as a whole and of individual parts like the power router in the context of larger

systems. In case of the pilot installation CIM is used to describe the semantic model

inside the KISTERS EMS to have an identical view on objects, how they relate to each

other, their attributes and parameters. As a result the understanding of objects by the

EMS of KISTERS and UPC respectively the OPF of KISTERS and UPC is consistent.



4.2 CIM and the Smart Rural Grid project

The way to model the grid is dependent on the IDPR mode (MASTER or SLAVE), the

needed granularity for different on-line calculations or off-line simulations and the range

of these calculations, in detail:

• Mode of the IDPR (MASTER, SLAVE)

• Whether or not the network is in an isolating state

• Power grid analysis requirements:

o Calculating only MV network (as seen by the SCADA system)

(IDPR in SLAVE modus)

o Calculating only MV and LV network (as seen by the SCADA system)

(IDPR in SLAVE modus)

o Calculating only parts of MV and LV network (in islanding mode, forming

a micro grid)

(IDPR in SLAVE or MASTER modus)

Figure 13: CIM modelling depending on use cases

Based on this classes the following calculations could be carried out (the emphasized

items are relevant to this project):

Mode

MASTER SLAVE

EqivalentInjection

no island

Only MV MV + LV

Load ACDCConverter

CsConverter

StaticVarCompentsator

island (MV) + LV

island (MV) + LV



� Power flow (Steady State Hypothesis: on-line and simulation, switching sequences)

� Short circuit calculation (symmetrical and asymmetrical)

� Optimal power flow (Q/V optimization, loss optimization)

� Power routing (Energy on demand)

� Dynamics

� Forecasts

� Power Quality (e.g. Jitter or more customer related the quality of service)

� Capacity calculations

� Estimating the capacity of resilience, e.g. according to faults in the mid voltage grid and the time an auxiliary supply by IDPR and attached batteries could be maintained.

� Harmonics

4.3 Used CIM classes and packages

This chapter defines the CIM classes for the Smart Rural Grid project. From the CIM

point of view the following information have to be exchanged and defined:

• Topology information

• Measurements (set points and commands)

• Wires (lines, switches, fuses)

• Storage (batteries)

• Generation

• IDPR operation modes

In the pilot installation (EYPESA) CIM will be used to describe the grid and all assets

inside the KISTERS EMS. The installed SCADA system of EYPESA does not support

CIM as an exchange format. Thus the interface between KISTERS EMS and EYPESA

SCADA will be implemented as a csv-file-exchange:



Different flows of information have to be defined:

Figure 14: CIM modelling depending on use cases

Table 3: Interfaces between the systems

From To What Format KISTERS EMS

KISTERS EMS

CIM classes, grid semantic information (internal use of KISTERS)

CIM

EYPESA control centre

KISTERS EMS

Grid semantic information (all static information including definition of measurements)

CSV


KISTERS EMS

Measurements / Switching states CSV

KISTERS EMS


Setpoints / Schedules CSV

RTU EYPESA control centre

Measurements / Switching states e.g. IEC 103, IEC 104


RTU Setpoints / Schedules, Switching states

e.g. IEC 103, IEC 104

Local DMS KISTERS EMS

No direct communication. The DMS sends measurements to RTU, RTU to EYPESA control centre and the control centre to KISTERS EMS.

-

KISTERS EMS

Local DMS No direct communication. KISTERS EMS sends setpoints to the EYPESA control centre which sends theses setpoints to the RTU and the RTI communicates with the local DMS.

-

CIM

csv



4.3.1 Topology

Topology is an extension to the Core Package that in association with the Terminal

class models connectivity that is the physical definition of how equipment is connected

together.

Figure 15: CIM UML topology model

CIM uses several classes to model topological connection. These are in general:

� Node

� Terminal

� Element (line segments, shunts, conductivity elements)

Topological relevant elements have one (shunts, loads), two (line segments) or three

(three winding transformer) associated Terminals, which connect the element to a



node. Measurements are also associated with terminals, but they use only zero or one

terminal. The direction of flow measurements is dependent on the terminal.

Topology modelling must be further distinguished between:

� Node/Breaker Model (Connectivity)

o Full real-time model

o Full topology

� Bus/Branch Model (Topological Nodes)

o Reduced model for planning (all switches are eliminated but the retained switches)

o Consolidated

In the Smart Rural Grid project the Node/Breaker Model is mandatory because for on-

line power flow analysis (Steady State Hypothesis) we need the status of switches,

measurements and other elements which are delivered by the RTU’s during runtime.

4.3.2 Sub Station and IDPR

The following example of a Sub Station (others may differ) shows some of the used

CIM classes:



Sym Vol Description

MV Manual disconnector

MV Fuse switch

LV Power switch, remote

operated

LV Smart fuse

Figure 16: Typical Sub Station

These CIM classes are defined in the following chapters. That listing shows the most

important objects, other objects, which might be necessary too, are omitted (e.g.

terminals, nodes, meters, bus bars, auxiliary elements).

4.3.3 Switches

CIM includes several classes for switches. For the project the disconnector, the (smart)

fuse and the breaker will be used. In the Smart_Rural_Grid project the treatment signal

for the Switch is mostly using 2 bits in order to identify open or close position and not

determent by position only. The RTU’s and, most important, the configuration of these

devices respectively their counterparts in the SCADA systems will respect this. In CIM

the status is simply a Boolean: open, that state is transmitted not by CIM in this project.

But if a CIM aware piece of software sends a CIM model over to another CIM aware

piece of software we use the open attribute.

CIM classes : Transformer, Measurement Switch Generation Load and others



4.3.3.1CIM Model

4.3.3.2Mapping of substation switches to CIM

Based on the real properties of the substation elements the project must define the

relationship to the corresponding CIM classes. This is called a mapping.

Sym Vol Description CIM parent class CIM main class

MV Manual

disconnector Switch Disconnector

MV Fuse switch Switch Fuse

LV Power switch Switch.ProtectedSwitch LoadBreakSwitch

Breaker

LV Smart fuse Switch No equivalent

yet

Table 4: Proposed mapping of switches of this project to CIM classes

“Smart fuse” definition: protects batteries for overcurrent, overvoltage, undervoltage protection, enable automatic battery recharging.



4.3.4 Set Points

4.3.4.1IDPR Set Points

Analogous set points of the IDPR

Description Units Format Availability

Active power setpoint [W] Real Slave

Reactive power setpoint [var] Real Slave

Voltage setpoint [V] Real Master

Frequency setpoint [Hz] Real Master

Digital set point of the IDPR


Harmonic current compensation enabling - Boolean Slave

Unbalance current compensation enabling - Boolean Slave

Reactive current compensation enabling - Boolean Slave

Table 5: Set point of the IDPR



4.3.4.2 Set Points definition in CIM

Figure 17: Controls in CIM (Setpoint and Command)

4.3.5 Measurements

4.3.5.1Measurements of the IDPR


Load active power phase R [W] Real Master/Slave

Load active power phase S [W] Real Master/Slave

Load active power phase T [W] Real Master/Slave

Load reactive power phase R [var] Real Master/Slave

Load reactive power phase S [var] Real Master/Slave

Load reactive power phase T [var] Real Master/Slave

Grid active power phase R [W] Real Master/Slave

Grid active power phase S [W] Real Master/Slave



Grid active power phase T [W] Real Master/Slave

Grid reactive power phase R [var] Real Master/Slave

Grid reactive power phase S [var] Real Master/Slave

Grid reactive power phase T [var] Real Master/Slave

Rated apparent power scale factor [pu] Real Master/Slave

Grid phase R voltage [V] Real Master/Slave

Grid phase S voltage [V] Real Master/Slave

Grid phase T voltage [V] Real Master/Slave

Grid frequency [Hz] Real Master/Slave

Battery voltage [V] Real Master/Slave

Battery current [A] Real Master/Slave

Table 6: Measurements of the IDPR

4.3.5.2IDPR Measurement topology

The property type measurementType (type String) shall contain the IDPR’s specific

measurements types. Because the IDPR is an electrical unit with one terminal unit, the

IDPR must be modelled as a more complex type as shown in:

Load side measurements

Impedance less CIM object

(ConductingEquipment)

Ter

min

al

Terminal

Terminal

Grid side measurements

CIM Node

Ter

min

al

Figure 18: IDPR measurements topology



4.3.5.3. Measurements in CIM

Figure 19: Measurements in CIM



4.3.5.4. XML Sample:

<cim:Analog rdf:ID="_D0E86D5181654BFDABCD81AD6F6A0E2E"> <cim:Analog.positiveFlowIn>true</cim:Analog.positiveFlowIn> <cim:Analog.normalValue>100.0</cim:Analog.normalValue> <cim:IdentifiedObject.name>Load_P</cim:IdentifiedObject.name> <cim:Measurement.measurementType>ActivePower</cim:Measurement.measurementType> <cim:Measurement.phases>ABC</cim:Measurement.phases> <cim:Measurement.MemberOf_PSR rdf:resource="#_ID_SUB2_LOAD1"/> <cim:Measurement.Terminal rdf:resource="#_LOADC5712A0D2F431594B0638457202CBC"/> <cim:Measurement.unitMultiplier>M</cim:Measurement.unitMultiplier> <cim:Measurement.unitSymbol>W</cim:Measurement.unitSymbol> </cim:Analog>

<cim:AnalogValue> <cim.AnalogValue.value>111.1</cim.AnalogValue.value> <cim.MeasurementValue.timeStamp>2014-07-20 00:00 MESZ</cim.MeasurementVaue.timeStamp> <cim.MeasurementValue.sensorAccuracy>90.0</cim.MeasurementVaue.sensorAccuracy> </cim:AnalogValue>

4.3.5.5. Mapping IDPR measurements to CIM

Description Meas. type phases Unit

multiplier Unit

symbol CIM

value CIM

terminal

Load active power phase R ActivePower A [W] Real Load side

Load active power phase S ActivePower B [W] Real Load side

Load active power phase T ActivePower C [W] Real Load side

Load reactive power phase R ReactivePower A [var] Real Load side

Load reactive power phase S ReactivePower B [var] Real Load side

Load reactive power phase T ReactivePower C [var] Real Load side

Grid active power phase R ActivePower A [W] Real Grid side

Grid active power phase S ActivePower B [W] Real Grid side

Grid active power phase T ActivePower C [W] Real Grid side

Grid reactive power phase R ReactivePower A [var] Real Grid side

Grid reactive power phase S ReactivePower B [var] Real Grid side

Grid reactive power phase T ReactivePower C [var] Real Grid side

Rated apparent power scale factor [pu] Real

Grid phase R voltage Voltage A [V] Real Grid side

Grid phase S voltage Voltage B [V] Real Grid side

Grid phase T voltage Voltage C [V] Real Grid side

Grid frequency Frequency [Hz] Real

Battery voltage DCVoltage [V] Real

Battery current DCCurrent [A] Real

Table 7: CIM mapping of measurements for IDPR



4.3.6 IDPR

The way of IDPR modelling is dependent on the IDPR mode (MASTER or SLAVE), the

needed granularity for different on-line calculations or off-line simulations and the range

of these calculations (see 4.2 CIM and the Smart Rural Grid project)

4.3.6.1IDPR as ACDCConverter

Figure 20: CIM class ACDCConverter

4.3.6.2IDPR as CsConverter (Current source converter CSC)

Defined in CGMES_2 (Common Grid Model Exchange Standard)

4.3.6.3IDPR as VsConverter (Voltage source converter VSC)

Defined in CGMES_2 (Common Grid Model Exchange Standard)



4.3.6.4IDPR as StaticVarCompensator (STATCOM)

In SLAVE mode the IDPR might be modelled as a CIM StaticVarCompensator,

delivering capacitive or inductive reactive power as necessary.

4.3.6.5 IDPR as a Load

In IDPR SLAVE mode the IDPR shall be modelled as a P/Q load because the set

points for P and Q are used to control power flow (power router mode). The actual

values of P and Q shall be measured as defined by the CIM classes for measurements.

4.3.6.6 IDPR as an Active Filter

In IDPR SLAVE the IDPR can work as an active filter.

4.3.6.7 IDPR as Injection

In IDPR MASTER mode the IDPR acts as a slack (or also named swing bus), so the

set points are only frequency and voltage, the flow through the IDPR is determined by

the connected grid (the voltage angle may be defined differently or measured to a

globally defined angle.

CIM model:

� EquivalentInjection

Consequences for power flow: For power calculation it is recommended that the slack

represents this injection with the maximum possible active and reactive power flow.

The IDPR might not fulfil this in a rural application there bigger renewable energy

generation might be installed. So there are additional requirements: the sum of all

loads and the losses must balance all injections (generators, slack) and the generation

should be known via measurements (smart meter) because the loads are mostly

unknown or estimated via load curves. A state estimator might have the advantage of

utilising additional voltage and angle measurement of renewable generation.

4.3.6.8 IDPR as a new CIM class

Another possibility is the definition of a profile for new CIM class, which includes the

different operation modes and combines them to one single description. The partners

will evaluate the chances for a proposal for a new CIM class which have to be send to

the IEC TC 57.



4.3.7 Power Transformer

Figure 21: CIM class PowerTransformer

4.3.8 Line segments

4.3.8.1 CIM Model

The CIM class ACLineSegment is used as the name implies to model AC line

segments by their Pi substitution network parameters.



Figure 22: CIM class ACLineSegement

4.3.8.2 ACLineSegment sample

<cim:ACLineSegment rdf:ID="_ID_LN2AC_ACLineSeg"> <cim:ACLineSegment.gch>0.0000498</cim:ACLineSegment.gch> <cim:ACLineSegment.bch>0.00048</cim:ACLineSegment.bch> <cim:ACLineSegment.r>0.215</cim:ACLineSegment.r> <cim:ACLineSegment.x>20.45</cim:ACLineSegment.x> <cim:ACLineSegment.g0ch>0.412</cim:ACLineSegment.g0ch> <cim:ACLineSegment.b0ch>0.03</cim:ACLineSegment.b0ch> <cim:ACLineSegment.r0>0.438</cim:ACLineSegment.r0> <cim:ACLineSegment.x0>0.502</cim:ACLineSegment.x0> <cim:Conductor.length>0</cim:Conductor.length> <cim:IdentifiedObject.name>LN2AC</cim:IdentifiedObject.name> <cim:IdentifiedObject.localName>LN2AC</cim:IdentifiedObject.localName> <cim:ConductingEquipment.BaseVoltage rdf:resource="#_ID_BaseVoltage_20KV"/> <cim:Equipment.MemberOf_EquipmentContainer rdf:resource="#_ID_LN2AC_Line"/> </cim:ACLineSegment>



4.3.9 EquivalentInjection

Figure 23: CIM class EquivalentInjection

4.3.10 Generation

Generation as defined by the CIM standard (currently CIM 16) stands for bulk

generation, not for renewable energies. For the time being the GeneratingUnit

(synchronous machines) or the EnergySource CIM classes may be used in

conjunction with active power, reactive power, voltage and angle measurements.



Figure 24: EnergySource (generation) and EnergyConsumer (loads)

4.3.11 Loads

Loads may be defined simply as EnergyConsumer class from the Wires package, if

the active and reactive power can be determined by other means (measurements). For

better load modelling CIM provides additional classes. If a daily load curves are known

then ConformLoad (extending EnergySource) can be used. ConformLoad

represent loads that follow a daily load change pattern where the pattern can be used

to scale the load with a system load.



5 Annex

5.1 CIM classes, tables

5.1.1 Description of Measurements properties

Class name Property name Type Description

Measurement measurementType String

Specifies the type of measurement. For example, this specifies if the measurement represents an indoor temperature, outdoor temperature, bus voltage, line flow, etc.

Measurement phases PhaseCode

Indicates to which phases the measurement applies and avoids the need to use 'measurementType' to also encode phase information (which would explode the types). The phase information in Measurement, along with 'measurementType' and 'phases' uniquely defines a Measurement for a device, based on normal network phase. Their meaning will not change when the computed energizing phasing is changed due to jumpers or other reasons. If the attribute is missing three phases (ABC) shall be assumed.

Measurement unitMultiplier UnitMultiplier The unit multiplier of the measured quantity.

Measurement unitSymbol UnitSymbol The unit of measure of the measured quantity.

MeasurementValue sensorAccuracy PerCent The limit, expressed as a percentage of the sensor maximum, that errors will not exceed when the sensor is used under reference

MeasurementValue timeStamp DateTime The time when the value was last updated

Analog maxValue Float Normal value range maximum for any of the MeasurementValue.values. Used for scaling, e.g. in bar graphs or of telemetered raw values.

Analog minValue Float Normal value range minimum for any of the MeasurementValue.values. Used for scaling, e.g. in bar graphs or of telemetered raw values.

Analog normalValue Float Normal measurement value, e.g., used for percentage calculations.

Analog positiveFlowIn Boolean

If true then this measurement is an active power, reactive power or current with the convention that a positive value measured at the Terminal means power is flowing into the related PowerSystemResource.

AnalogValue value Float The value to supervise.

AnalogLimit value Float The value to supervise against.

5.1.2 ACDCConverter details

IDPR as CsConverter (Current source converter CSC)

Definitions from CGMES_2 (Common Grid Model Exchange Standard):



Property name Type Unit Namespace Description

measurementType String CIM16

A unit with valves for three phases, together with unit control equipment, essential protective and switching devices, DC storage capacitors, phase reactors and auxiliaries, if any, used for conversion.

baseS ApparentPower Base apparent power of the converter pole.

idleLoss ActivePower Active power loss in pole at no power transfer. Converter configuration data used in power flow.

maxUdc Voltage

The maximum voltage on the DC side at which the converter should operate. Converter configuration data used in power flow.

minUdc Voltage Min allowed converter DC voltage. Converter configuration data used in power flow.

nomUdc Voltage

The nominal voltage on the DC side at which the converter is designed to operate. Converter configuration data used in power flow.

numberOfValves Integer Number of valves in the converter. Used in loss calculations.

ratedUdc Voltage

Rated converter DC voltage, also called UdN. Converter configuration data used in power flow.

resistiveLoss Simple_Float

Converter configuration data used in power flow. Refer to poleLossP.

switchingLoss PU

Switching losses, relative to the base apparent power 'baseS'. Refer to poleLossP.

valveU0 Voltage Valve threshold voltage. Forward voltage drop when the valve is conducting. Used in loss calculations, i.e. the switchLoss depend on

Property name Type Unit Namespace Description DC side of the current source converter (CSC). maxAlpha AngleDegrees

Maximum firing angle. CSC configuration data used in power flow.

maxGamma AngleDegrees

Maximum extinction angle. CSC configuration data used in power flow.

maxIdc CurrentFlow

The maximum direct current (Id) on the DC side at which the converter should operate. Converter configuration data use in power flow.

minAlpha AngleDegrees

Minimum firing angle. CSC configuration data used in power flow.

minGamma AngleDegrees

Minimum extinction angle. CSC configuration data used in power flow.

minIdc CurrentFlow

The minimum direct current (Id) on the DC side at which the converter should operate. CSC configuration data used in power flow.

ratedIdc CurrentFlow

Rated converter DC current, also called IdN. Converter configuration data used in power flow.

5.2CIM Voltage Source Converter

VsConverter (Voltage source converter VSC)

Definitions from CGMES_2 (Common Grid Model Exchang e Standard):

Property name Type Unit Namespace Description

DC side of the voltage source converter (VSC).

maxModulationIndex Simple_Float

The max quotient between the AC converter voltage (Uc) and DC voltage (Ud). A factor typically less than 1. VSC configuration data used

maxValveCurrent CurrentFlow

The maximum current through a valve. This current limit is the basis for calculating the capability diagram. VSC configuration data.

DC side of the voltage source converter (VSC).



5.3StaticVarCompensator

Class name Relation Type Namespace Description

RegulatingCondEq Geralization ConductingEquipment

A type of conducting equipment

that can regulate a quantity (i.e.

voltage or flow) at a specific point

in the network.

Class name Property name Type Unit Namespace Description

RegulatingCondEq controlEnabled Boolean CIM16 Specifies the regulation status of

the equipment. True is regulating,

false is not regulating.

StaticVarCompensator q ReactivePower Reactive power injection. Load sign

convention is used, i.e. positive sign

means flow out from a node.

Starting value for a steady state

solution.

smart rural grid€¦ · upc francesc girbau cga brian sutherland deliverable beneficiaries wp /...

Documents