CIMug Milan 2010, June 15-18thGuillaume Lapierre-Ganivet

CIM Gateway

Overview

■ The overall goal of this project

■ CIM Object model generation

■ Applications

■ Perspectives

2

Overall goal:Exchange data in CIM XML

4

Old vs. New format

■ Breakthrough technology

■ Extending content of exchange formats

■ Overall quality is improved

Exchange data in CIM XML

5

Other TSOs

ENTSO-E Projects

TSOConsortium

Regions

Operationalprocesses

System studiesprocessesDACF

Referencecases

D2CF(planned)

Snapshots

Others on request

Planning

Variousstudies

Mid-term Long-term

Systemextension

ENTSO-E

TSO 1, TSO 2 , …

TSO 3, TSO 4TSO 5, …

TSO 6, TSO 7, …

- frequent

Others such as wind integration

- regular, but not frequent

- on request

CIM compliance at stake

■ IEC standard

■ CIM XML Model Exchange – 61970-452(-456)

■ ENTSO-E CIM Model Exchange Profile

6

Topology

State

Equipment

7

ENTSO-E CIM Model Exchange Profile

■ Equipment■ Topology■ State

variables

State Variables

TSO Topology

TSO Equipment Model

ACLineSegment

ControlArea

CurrentLimit

CurveData

EnergyConsumer

FossilFuel

GeneratingUnit

GeographicalRegion

HydroGeneratingUnit

HydroPump

MutualCoupling

NuclearGeneratingUnit

OperationalLimitSet

PhaseTapChanger

PowerTransformer

RatioTapChanger

ReactiveCapabilityCurve

RegulatingControl

SeriesCompensator

ShuntCompensator

SubGeographicalRegion

Substation

SvPowerFlow SvShuntCompensatorSections SvTapStepSvVoltage

Switch

SynchronousMachine

Terminal

Terminal (about)

ThermalGeneratingUnit

TieFlow

TopologicalIsland

TopologicalNode

TransformerWinding

VoltageLevel

VoltageLimit

WindGeneratingUnit

UCTE Common Objects BaseVoltage OperationalLimitType

ControlAreaGeneratingUnit

LoadResponseCharacteristic

CIM object model generation

Requirements & Specifications

9

■ Automatically generatedCIM Model C++ library

■ Read / Write XML instances

■ Useful to check profile consistency

■ Evolutive on demandand multi-platforms

10

XML specifications

■ XML Metadata Interchange

■ Web Ontology Language

■ Resource Description Framework

11

Available tools and technologies

■ DOM vs. SAX

■ Apache Velocity

■ CIMTool

■ CIMDesk

Principle scheme

12

Applications:Achieve consistency& inter-operability

14

CIM profile and internal format

■ Obtaining 'bijectivity'

■ Support former fonctionalities

■ Merged, Partial and ... Incremental

■ Unique and persistent IDs

15

Validation of tools and data

■ Inter Operability (IOP) tests

■ ENTSO-E Migration process

■ CIMDesk

■ Bug reports

Perspectives

17

And then …

■ No more UCTE DEF files

■ Upcoming CIM versions

■ Parser and writer at no cost

■ Large range of profiles

Any questions?