Role of CIM for Power System Model Exchange: Europe - ENTSO-E Experience with CIM CIM Users Group February 26, 2013 Melbourne, Australia Chavdar Ivanov, PhD Research and Development Senior Advisor, ENTSO-E

41 TSOs, 34 countries534 million citizens served 305,000 km of transmission lines 950 GW generation 3,300 TWh/year demand 440 TWh/year exchanges ENTSO-E represents the European Transmission System Operators

ENTSO-E has a significant role in delivering European energy and climate change objectives Key activities set out in Regulation 714/2009 (on cross-border electricity trade, part of the 3 rd Internal Energy Market Package) Deliver network codes binding to all network users (Comitology) Ten-Year Network Development Plan “TYNDP” Enable internal market (“market coupling”) R&D Roadmap (fully included in EEGI – the SET Plan) Through its members deliver the infrastructure to: Deliverable markets to function Secure energy supply Meet climate change objectives with RES

Drivers for pan-European grid development Sustainability More renewables far from loads New electricity uses (mobility with electricity, heat pumps...) Competitiveness / Market integration Optimal resources sharing More long distance trans-European flows Security of Supply Continuity of supply of remote/isolated areas Prevent large disturbances

Milestones for European grid development

Time horizons addressed in the Network Codes:  Year ahead: outage coordination (NC OPS), Forward Capacity Calculation (NC FCA)  Month ahead: Forward Capacity Calculation (NC FCA), Regional Operational Security Assessment (current business needs)  Week ahead: Regional Operational Security Assessment (NC OPS)  Two days ahead: Capacity Calculation for D-1 market (NC CACM)  Day ahead: Operational Security assessment, model corrections and assessment of remedial actions (NC OPS), Capacity Calculation for Intraday market (NC CACM)  Intraday: Regional Operational Security Assessment (NC OPS)  Updates for outage plans upon request by Outage planning agents  Regional security assessment requires at least Common Grid Models for the whole synchronous area

Definitions ConsistencyInterpretation  Data has to be collected  Data has to be maintained  Data needs to be reused by different systems for different studies

ENTSO-E and CIM - history  : TSOs identified the need for more detailed exchange; thinking on improving data exchanges  : interactions with IEC and CIMug and decisions on direction towards CIM  2009: 1st profile for network model exchange; In parallel market effort on CIM are increasing  :  Development process for profile 2 (current CGMES)  Series of interoperability tests – to prove vendors‘ implementation of profile 1 -to valudate draft standards and support development  Dec 2013: Approval of teh Common Grid Model Exchange Standard (CGMES)

Why CIM is important for TSOs and ENTSO-E?; ENTSO-E legal obligations  TYNDP development process requires consistent data  Network codes require – Common Grid Model  TSOs exchanges require HVDC, dynamics, operational level details to be exchanged, etc.  The data consistency between planning, operation, market systems will be improved over time if a harmonized common conceptual model is used  Better common studies if a common data exchange language available. Huge benefits for TSO cooperation  More and more important to have frequent and reliable exchange in the frame of system operation

Identified gaps/issues and relates measures ENTSO-E profile 1 (UML14v02) while IEC CIM14 (UML14v15) Process to discuss issues in IEC and CIMug Description of profiles; rules definition ENTSO-E will work with OCL rules as much as possible; clearer profiles Vendors are not obliged to test CIM exports/imports when changing tool version ENTSO-E Conformity Assessment Process Standardisation is voluntary Link with R&D projects is weak “Maturity” of tools user friendliness Projects to support standardisation; Interactions with R&D projects and vendors

CGMES approval On 18 Dec 2013 ENTSO-E Assembly approved the Common Grid Model Exchange Standard (CGMES) v CGMES is approved as a baseline data exchange standard for the EU operational and market Network Codes CACM : Capacity Allocation an Congestion Management FCA : Forward Capacity Allocation OS : Operational Security OPS : Operational Planning & Scheduling CGMES will also be used for system development studies data exchanges including ENTSO-E Ten Year Network Development Plan related studies

CGMES content CGMES is a superset of draft IEC standards to be issued for IEC CIM16 CGMES was developed in the last 4 years and covers: Bus-branch and node-breaker representation Exchange of solved and unsolved load flow models (combinations of equipment, topology, steady state hypothesis and state variables profiles) Exchange of diagram layout Exchange of geographical location (GIS) Exchange of dynamics models Significant update of transformer modeling was done and HVDC representation was introduced

CGMES documentation Main page on CIM – linklink Version is available herehere Information on CGMES conformity process will be available herehere The documentation includes the following: Main document – standard, which defines the framework and sets rules HTML documents – exported for each profile belonging to the CGMES. Specific profile rules are defined in these documents HTML Enterprise Architect export – identical view of the UML model as in EA RDFS export – RDF schema for each profile belonging to the CGMES XMI export – directly exported from EA; contains all profiles CGMES issue list – this list should be used to report issues on the CGMES. Issues should be sent to

Activities related to CGMES implementation CGMES Implementation Roadmap – internal document which defines a series of projects and tasks to implement CGMES and reach a stage when CGMES based exchanges are put in operation CERTI-I – internal project: Phase I (2013) List necessary use cases; Develop requirements for test models to be used in conformity assessment program Identify options for conformity assessment Phase II (Jan-May 2014) Develop conformity assessment program for the selected option CERTI-II – internal project with vendor participation: Duration: Jan-Jun 2014 Deliverables: Develop test models/data to be used in the conformity assessment program. Currently assessment of offers Develop test procedures (test scripts) to be used in the conformity tests PROFI – internal project Duration: Jan – July 2014 Objective to further develop CGMES (issue new version) to address all (the most urgent) requirements defined in the Network codes (CGMES currently covers 73% of the requirements) IEC WG13 will be kept informed on the CIM extensions proposals coming form this projects. Discussions will be arranged in the frame of the liaison with IEC. Dynamics profile implementation Objective: harmonized implementation of the CGMES dynamics profile by vendors An effort launched in Dec Expected finalization in Sep- Oct 2014 Vendors participating in the effort: DIgSILENT (Power Factory), Tractebel/RTE (Eurostag), CESI (SICRE), BCP (Neplan), Siemens (PSS/ODMS, PSS/E, Netomac), CEPS (own tool) Interoperability testing IOP 2014 – will be held in Brussels in the week of 14 July 2014 Other tasks TSOs activities to gather different data to satisfy requirements for the data exchanges (requirements in the Network codes, TYNDP and other needs).

IOP in 2014 – the two objectives Testing of the commercial releases of the tools Conformity testing for tools using CGMES v – the process to be prepared in the frame of conformity assessment program Testing of the CGMES extensions established in PROFI project Testing of the interoperability of the updated CGMES version – a standard vetting type of IOP tests to validate the new version of the CGMES; Vendors using prototype tools as usual

ENTSO-E IOP site in the CIMug

ENTSO-E Conformity Assessment Program  Under development – to be ready for IOP – July 2014  Policy  Test configurations – “golden” models  Test procedures and clear assessment rules  Simplified approach to be applied at first stage Main stages:  Vendor issues conformity declaration  Vendor requests ENTSO-E Conformity Assessment  ENTSO-E performs Conformity Assessment  ENTSO-E issues an Opinion which is publicly available  TSOs use tested tools (which have positive ENTSO-E Opinion) in the data exchanges

ENTSO-E Network Modelling Database 18 ENTSO-E Secretariat TSOTSO Sharing TSO’s To be Situation As Is Situation ? TIE-LINE Management TIE-LINE Management ASSEMBLING Network Model ASSEMBLING Network Model NETWORK MODEL Collection NETWORK MODEL Collection IOP Model VALIDATION Model VALIDATION Consolidated Platform eTerraSource Before After

Situations management

Assembling management