dario consolato frazzetta entso-e use of cim cim@entso-e ... · iec 61970-552 iec 61970-301 iec...

June 2017

Dario Consolato Frazzetta

CIM@ENTSO-EENTSO-E use of CIM

& CGMES case

ENTSO-E at a glance

Network codes require standards

ENTSO-E chose CIM

CGMES case

Third IEM Package recognises the importance of TSO cooperation

41+1 TSOs from 35 countries

532millioncitizens served

1020 GWgeneration

313 Thousand Kmof transmission lines

Ten-Year Network Development Plans

Adequacy forecasts

Market Platforms

Network Codes

ENTSO-E was created in 2009 with a legal mandate

Ten-Year Network Development Plans

Network Codes development and implementation

We build markets

Regional cooperation and Adequacy forecast

Policy adviser to ACER and the Commission

ENTSO-E’s main tasks

3 ConnectionNetwork Codes 3 Market

Network Codes 4 OperationalNetwork Codes

set requirements for:

- Generators

- Demand-side

- HVDC connections

set market rules for:

- Day ahead/intraday & Capacity calculation

- Long-term timeframes

- System balancing

set common rules for:

- Assessing adequacy

- Planning outages

- System security

- Emergency situations

Internal Electricity Market

… day-ahead market coupling…

…paving the way for offshore wind…

…regional security coordination initiatives…

Network Codes: the Foundations of the IEM

ENTSO-E at a glance


ENTSO-E chose CIM

CGMES case

3 ConnectionNetwork Codes 3 Market

Network Codes 4 OperationalNetwork Codes

set requirements for:

- Generators

- Demand-side

- HVDC connections

set market rules for:

- Day ahead/intraday & Capacity calculation

- Long-term timeframes

- System balancing

set common rules for:

- Assessing adequacy

- Planning outages

- System security

- Emergency situations

Market data exchanges:

IEC 62325 (CIM)

CENELEC 50549

…

Common Grid Model Exchange Specification:

IEC 61970 (CIM)

Implementing Network Codes requires standards

ENTSO-E application development framework

•Business Requirement Specification

•Identification of Generic Use Cases

Network codes drafting

•Map GUCs to SGAM

•Security and privacy evaluation

•Locate requirements for standards

Standardization analysis •Identify existing standards

and new gaps

•Definition of standardization projects

Standardization preliminary phase

•Work on existing, modified and new standards, including profiles

•Close collaboration with Network Codes implementation projects

Standardization preparatory phase •Test on functions and

interoperability

•Publication of standards in IEC and/or CENELEC

Standardization approval phase

GenericUse

Cases (GUC)

ENTSO-E at a glance


ENTSO-E chose CIM

CGMES case

European adoption of CIM

UCTE-DEFENTSO-E creation (2009)

ENTSO-E shift to CIM

(2014)

Market 62325 series and CGMES

2.4.15 (Today)

Future…

CIM is one of the pillars of Smart Grid, for grid management and market communication

Generation

Transmission

Distribution

DER

Customer

Process

Field

Station

Operation

Enterprise

Market

Domains

Zones

(Home, Building,

Industry, EV, Mobility)

(Hierarchy)

CIM (IEC 61968, IEC 61970, IEC 62325)

Energy Management Systems

Distribution Management

Market Communication

One example: IEC 62325 Methodology

informationmodel

contextualmodel

messageassemblymodel

messageimplementationsyntactic model

regionalcontextual

models

documentcontextual

models

CIM

style marketprofile 1

style marketprofile n

…

schedulecontextual

model

bidcontextual

model

…

schedule assemblymodel

bid assemblymodel

xsd xsd

profiling derivation

implementation derivation

301

351

451-n

Future challenges

Clean energy package

• New set of regulations that will require standards

Link R&D project with standardization

• European Union funded projects

Network code implementation

• Connection network codes

• Market network codes

• Operation network codes, including CGMES

ENTSO-E at a glance


ENTSO-E chose CIM

CGMES case

Click to edit Master title styleThe Common Grid Model

Click to edit Master title styleIntroduction on the merging process

https://youtu.be/0bm4hqINTyI

Click to edit Master title styleProblem statement

Imagine you want to forecast the behaviour of the European grid for a given point in time in order to assess the risks for security of supply and to calculate the available transmission capacity for trading energy, then you need to rely on data for which a lot of different parties are responsible:

Long distance and cross-border transmission of electrical energy, transmission grid behaviour

Consumption prognoses, dispersed generation, DSO grid behaviour

Production/consumption of electrical energy

TSOs: Modelling grid components, network

topology, historical data

DSOs: Modelling grid components,

network topology, load forecast, DER, RES

Click to edit Master title styleEvery TSO is collecting data and can provide a piece of the puzzle

Cross border transactions do not reflect the actual flows of energy in the grid! (Unfortunately physics don’t follow economic laws)

Bo

un

dar

y

Transmission grid

Distribution gridEnergy in/out

Energy in/out

Bo

un

dar

y

Boundary Boundary Boundary

Click to edit Master title styleBoundary agreements can glue the IGMs together

Boudary AD Boundary BC

BoundaryAB

TSO A TSO B

DSO C

~

DSO D

~

Boundary AE Boundary BF

Boundary

EF

TSO E TSO F~

~

Click to edit Master title styleOnly when we merge all pieces (IGMs) together we can see the actual flows

• Loop flow• Transit flow

Click to edit Master title styleIn order to do this we need to:

• Collect al the model parts (IGMs) and information about boundary connections

• Compensate for missing information (if applicable)

• Check the plausibility of the assumptions and check the format in which the data has been provided (so it can be processed correctly)

• Align the energy balance (what is produced, what is consumed and what is scheduled to be exchanged) for each IGM provided by each TSO

• Perform some model improvement (i.e. get rid of inconsistencies)

• Calculate the system state for the whole grid and for each synchronous area

Click to edit Master title styleThe expected system state depends on when you look at it

Grid extension Maintenance Capacity & Security

Year ahead Month ahead Week ahead Day ahead Real-time

ExecutionSecurity

Intraday

Market & Operational PlanningGrid Planning

Confidence level

Click to edit Master title style

Contingency Analysis/ Assessment of the effectiveness of Remedial Actions

Capacity Calculations

Response to a disturbance in the time domain (Dynamic Stability Analysis)

Impact of planned unavailabilities

Steady State System condition(CGM) for the target timestamp

Quality Assurance Gate

Merging process)

Common Grid Model

Alignment (forecast):• Netted Area AC positions

• Aggregated netted external

schedules (HVDC)

Pre-market closure day ahead Individual Grid Models

Week ahead Individual Grid Models

Month ahead Individual Grid Models

Year ahead Individual Grid Models

Post-market closure day ahead Individual Grid Models

Intraday Individual Grid Models

Years ahead Individual Grid Models

Short term Adequacy

Real-time snapshot data

TSO’s Individual Grid Models are expressed as CIM EQ models for a business day and SSH/TP instances

for every reference point in time

Pan European Verification

function (market results):• Netted Area AC positions

• Aggregated netted external

schedules (HVDC)

Business processes and time horizons

Click to edit Master title styleThe CGM lifecycle

Apply agreed flows on HVDC links and calculate steady state solution while enforcing net position for bidding zone/scheduling area (“Area Interchange Control”)

Initialize the grid situation for the date time of interest using the information from the previous time horizon Update your own network

model (projects) and modelling assumptions (energy injections, monitoring limits, controls and switching states) with new information

Issue changed model parts

Update boundary data if applicable in agreement with neighbour TSO

Collect updated model parts from other TSOs

Assemble the pan-European CGM and calculate steady state solution, issue the Area Interchange instructions

Update the model parts in your observability area and calculate steady state solution, using the Area Interchange Instructions

Run security analysis and solve overloads by implementing preventive remedial actions

Click to edit Master title styleThe DNA of an IGM

Physical model valid for the study

Device status initialization/ Edit

Control settings initialization/ Edit

Monitoring initialization/ Edit

Energy Injection Initialization/ Edit

Equipment model (EQ):

- Connectivity- Impedances- Component behaviour- Containment- Associations- Identification- Physical limits/ratings

Steady State Hypothesis (SSH):

- Device status• Switch status• Branch end• Tap positions

- Control settings• Voltage regulation• Flow regulation

- Monitoring• Variable Operating

limits- Energy injections

• Energy consumption• Bulk generation• DER• RES

Topology processing

Power Flow Solving

Algorithm

State Variables (SV):

- Complex voltages

- Bus injections- Tap positions

Topology (TP):

- Topological Nodes

- Topological Islands

IGM

TSO tool

As-built network

construction

Network operating practice

Energy allocation to

devices

Planned construction

Measurements

Planned maintenance

Forced unavailability

Weather conditions

Energy Schedules

Energy Forecasts

Click to edit Master title styleThe Common Grid Model Exchange Specification

Based op CIM 16 (UML16v29):

• IEC 61970-552 : CIM XML Model Exchange Format

• IEC 61970-301 : Common Information Model (CIM) Base

• IEC 61970-302 : Common Information Model (CIM) for Dynamics Specification

• IEC 61970-452 : CIM Static Transmission Network Model Profiles

• IEC 61970-453 : Diagram Layout Profile

• IEC 61970-456 : Solved Power System State Profiles

• IEC 61970-457 : Common Information Model (CIM) for Dynamics Profile

• IEC 61970-501 : Common Information Model Resource Description Framework (CIM RDF) schema

• IEC 61968-4 : Application integration at electric utilities – System interfaces for distribution management - Part 4: Interfaces for records and asset management.

Click to edit Master title styleCGMES 2.4 consists of a number of coherent profiles

IEC 61970-457

Dynamic (Transient model)

DY

IEC 61970-453

Diagram LayoutDL

IEC 61970- 452

Network Equipment and Connectivity

EQ-CO

Short- CircuitEQ-SC

Operation(Node- Breaker)

EQ-OP

IEC 61970-456

TopologyTP

Geographical Location

GL

Boundary equipment

EQ-BD

Boundary topology

TP-BD

State VariableSV

Steady State

Hypothesis

SSH

refref

ref

ref

ref

ref

ref

ref

opt. ref

opt.ref

opt. ref

opt. ref

opt. ref

VariantInvariant

Click to edit Master title styleCGMES data is stored in RDF XML instance files

EQ data instance files contain information about equipment behaviour and connectivity, identification is done via rdf:IDs (UUID). Names are mandatory, but can be fake

SSH data instance files contain no information about equipment behaviour and connectivity, but contain actual values (set points, schedules, switch positions, …).Identification is done indirectly via external references (rdf: about), using UUIDs

TP data instance files contain no information about equipment behaviour and connectivity, but contain only associations between nodes (necessary for calculations) and terminals. Identification is done indirectly via external references (rdf: about), using UUIDs

SV data instance files contain no information about equipment behaviour and connectivity, but contain calculated values only.Identification is done indirectly via external references (rdf: about), using UUIDs

Click to edit Master title styleChallenges ahead

✓ Getting everyone connected to the new network

✓ Interoperability means more than using the same standard: testing is very important, but so is verification of the interpretation and using the same algorithm settings

✓ Preparing for an industrialized process means a high level of harmonization in meta data

✓ Interfacing and aligning “other” business processes, such as scheduling and coordination of planned unavailability and remedial actions

✓ Business continuity

✓ Security: Confidentiality, Integrity and Availability of data

Click to edit Master title styleCGMES

IEC 61970-552 IEC 61970-301 IEC 61970-302 IEC 61970-452 IEC 61970-453 IEC 61970-456 IEC 61970-457 IEC 61968-4

CGMES

Draft Standards based on CIM 16 - UML16v25

• NEW! Transformer Model• NEW! Shunt Compensator model• NEW! HVDC model• Steady State Hypothesis profile• Dynamics profile• Diagram Layout profile• Geographical Layout profile• Other more …

Click to edit Master title styleCGMES

EQ

TP

SSH

SV

Boundary EQ

Boundary TP

Click to edit Master title styleCGMES Extensions

Click to edit Master title styleTen Year Development Plan

NMD

CGMESCGMES CGMES

Planning grids

• Quality Gates• Scenario/Case storage

• Merging• Load Flow calculations• Contingency analysis

EU Panel Model

Click to edit Master title styleOperational Processes

Coordinated Security AnalysisBe prepared for the drop out of each of the elements in the grid. Plan remedial actions across country borders for ciritical cases.

Outage Planning CoordinationMaximize availability of transmission grid through cross-border coordination of planned outages on equipment.

Coordinated Capacity CalculationMaximize avaialble capacity for cross-border trading while ensuring the security of the grid.

Short and Medium Term AdequacyAssess the adequacy of the grid for short and medium term demand.


OP

DE

The OPDE Vision

Mo

del

ling

Too

ls

Bo

un

dar

y M

anag

emen

t

Mer

gin

g To

ols

PEV

F

CG

MA

QA

Po

rtal

(EH

FTP

Ser

ver)

ECP4 / EDXEnergy Communication Protocol V.4

+ ENTSO-E Data Exchange

OPDE Communication MiddlewareData exchange service bus with services like publish / subscribe based on secure, fast and reliable messaging through AMQP + MADES2.

ATOMAll TSO Operational, Market and Planning Data Network

NetworkPan-European private network based on TSO owned backbone network for non-real-time operational and market-operations related data.

Central Services for the CGM delivery process, provided by ENTSO-E via OPDE:QA PortalBoundary ManagementPan-European Verification FunctionCommon Grid Model Alignment

OPDMCentral

Operational Planning Data ManagementSmart file storage and management for Operational Planning Data

OP

DM

OP

DM

OP

DM

OP

DM

OP

DM

OP

DM

OP

DM

TSO / RSC Applications

Centrally providedApplications / Services

Click to edit Master title styleInteroperability Challenges

(✓) Highest score in interoperability(5) Load flow results converging (blank) only import possible, no converging load flow

CGMES

Click to edit Master title styleConformity Assessment Scheme

Click to edit Master title styleStandardization activities

TC 57 WG 13 Liaison type D

CIM CGMES

61970-600-1 61970-600-2

Technical Specification

CGMES

Click to edit Master title styleFuture scenarios

NMD OPDE

CGMES 2.4.15 CGMES 2.5

Conformity Assessment Scheme

CAS 1.1.3 CAS 2.0


?

Dario Consolato FrazzettaSystem Development Advisor

[email protected]

mailto:[email protected]

dario consolato frazzetta entso-e use of cim cim@entso-e ... · iec 61970-552 iec 61970-301 iec...

Documents