ENTSOE IOP CIM for System Development and Operations

ENTSO-E IOP “CIM for System Development and Operations” 2011 kick off web conference, 31 January 2011 17: 00 – 18: 00 h CET 31 January 2011, Brussels ENTSO-E | 31 January 2011

Participants – call attendees are marked in green Chavdar Ivanov (ENTSO-E); Giatgen Cott (NEPLAN); Chuck Dubose (Siemens); Michael Ford (Siemens); Sam Phillipson (Siemens); Roberto Zacheo (CESI); Maurizio Quadrio (CESI); Ferdinando Parma (CESI); Dario Frazzetta (CESI) Jean-Baptiste Heyberger (RTE); Christian Merckx (Tractebel); Lars-Ola Osterlund (Ventyx/ABB); Torbjorn Ericson (Ventyx/ABB); Alan Mc. Moran (Open Grid Systems); Dirk Cremer (FGH); Herbrt Falk (SISCO); Rahul Khare (Ventyx/ABB); Mostafa Khadem (Ventyx/ABB); Ingemung Nordanlycke (Intercompro); Bojan Ivanovic (EPS); Kendall Demaree (Alstom Grid); Stefano Vassena (Alstom Grid); Jay Britton (Alstom Grid); Thibault Dufaour (Alstom Grid); Eric Lambert (EDF); Domenique Marcadet (EDF); Christoph Schmid (DIg. SILENT); Perry Krol (TIBCO); Mic Hussey (TIBCO); Feng Chen (GE); Devin Van Zandt (GE); Anupam Gopal (GE); James Cronen (GE); Surendra Puchalapalli (GE); Margaret Goodrich (SISCO); Terry Saxton (Xtensible); Arnold de. Vos (Langdale) Jun Zhu (Power Info) Nebojsa Jovic (EKC) Djordje Dobrijevic (EKC) Zoran Vujasinovic (EKC) Zvonko Gorecan (DMSGROUP) Lajos Martinovic (DMSGROUP) Dragan Tomic (DMSGROUP) Guillaume Lapierre-Ganivet (RTE) Michael Heine (PSI) Bernd Kammerling (PSI) Anjen Maizener

Agenda • • • ENTSO-E IOPs – short introduction, roadmap, objectives Profile, UML IOP organizational issues – teleconferences schedule, date, Share. Point

Important ENTSO-E decisions Ø 1 Oct 2009: System Development Committee (SDC) agreed that CIM/XML will be used in ENTSO-E data exchanges related to SDC activities (system studies, planning data exchanges) Ø 2 Sep 2009: System Operations Committee (SOC) recommends: Ø Regional Group Continental Europe: The change from the UCTE format to CIM was decided by the UCTE Steering Committee. The goal is to switch to the new format before the end of 2010 at the latest (DACF exchanges) Ø Other Regional Groups to consider implementation of the standard with an aim of the pan. European harmonization Ø 2 Dec 2009: SDC and SOC: Approved the roadmap for future development and implementation of updates of the CIM/XML format Ø 11 Dec 2009: SDC, SOC and Market Committee: Approved ENTSO-E CIM Interoperability tests Ø 18 Nov 2010: SDC and SOC decision on the (draft) 2 nd edition of the profile: https: //www. entsoe. eu/index. php? id=42&no_cache=1&tx_ttnews%5 btt_news%5 d=83

ENTSO-E Secretariat serves as a central function of coordination, maintenance 5 and support of Common Information Model (CIM) related issues and therefore, it is the interface to international organizations International organizations: IEC, EPRI, CIMug, … ENTSO-E Data Expert Group - Discussion on Committees/WGs requests; - Information on IEC opinion; - Possible solutions - etc. SG NMFT in RG CE WG System Development Committee - Liaisons, - Submitting ENTSO-E needs, - Participation in the discussion, - etc Secretariat - Maintenance ENTSO-E CIM tools; - contacts with providers Requests that concern CIM must be submitted to Secretariat Operations Committee CIM tools CIMdesk; Migration Converter Market Committee NM&D WG EDI WGs defining needs

Current ENTSO-E CIM/XML Profile Ø Current ENTSO-E Profile is the “UCTE CIM Profile” tested in UCTE IOP in March 2009 in Paris. THIS IS THE PROFILE THAT IS BEING IMPLEMENTED BY ENTSO-E MEMBERS. Ø Updates of this profile should follow the approved Roadmap Ø Proposals for changes are welcome and will be discussed within ENTSO-E, IEC and will be tested in the ENTSO-E IOP once agreed among IOP participants. Ø Current ENTSO-E CIM/XML profile is published on ENTSO-E web site (CIM part: http: //www. entsoe. eu/index. php? id=237) Ø A draft version of the second edition of the ENTSO-E CIM/XML profile was developed for the ENTSO-E interoperability test in July 2010. It is also available on the ENTSO-E web site (https: //www. entsoe. eu/fileadmin/user_upload/_library/resources/CIM/Interoperability_Tests/E NTSO-E_CIM_Model_Exchange_Profile_v 2_draft_7_IOPversion_12 July 2010. zip)

Roadmap for future implementation of CIM Ø The aim: to structure the implementation effort. No yearly implementation. An exception could be only if a change is introduced which is critical for ENTSO-E processes Ø The implementation process is foreseen to last one year. Ø On regular basis the implementation effort is foreseen every three years, if necessary. Ø Next versions of the ENTSO-E Profile have to be approved by System Development Committee (SDC). In case of changes that affect operational data, System Operations Committee (SOC) decision is also required. Ø SDC or SDC&SOC decision ensures one year implementation period. Coming into force date is fixed and mandatory for TSOs

ENTSO-E CIM Interoperability Tests Registered vendors Ø Ø Ø Ø Ø BCP Busarello + Cott + Partner AG (NEPLAN) Open Grid Systems (Cimphony) Intercompro AG (ISPEN) TIBCO (Intelli. EDGE) SISCO (UIB Adapter for PI-AF and UIB Core) Siemens Power Technologies International (PSS/ODMS) GE Energy (PSLF) EKC&DMS (Transmission Network Analyzer) RTE (Convergence) FGH (INTEGRAL 7) Tractebel and RTE (EUROSTAG) Ventyx/ABB (Network Manager SCADA/EMS) CESI (SPIRA; CRESO; SICRE) EPS (Power System Analyzer, PSA) PSI AG (PSIcontrol) DIg. SILENT Gmb. H (Power. Factory 14. 1) EDF R&D (GEDEON Database; CIMclipse; CIM-ENTSO-E Converters) Alstom Grid (e-terrasource) GE Energy Services (Enterprise Gateway) In addition to the above vendors, ABB (BMS CIM Explorer) requested to participate in the preparation leading up to the interoperability test. Zemiren (Cim. Contextor) will participate in the test and will support preparation of profiles to be used in the test.

ENTSO-E IOP Report Ø Finalized and published in mid August Ø Available on the ENTSO-E web site: https: //www. entsoe. eu/index. php? id=240 Ø Identified CIM issues were listed in the final report and submitted to IEC WG 13 for further discussion. The expectation is that CIM 15 will resolve most of the issues

CIM and ENTSO-E web site (www. entsoe. eu)

ENTSO-E CIM in the CIMug web site

ENTSO-E IOPs – test topics • • Interoperability using the last UML (v 15 + Dynamics + any modifications agreed among test participants) – new draft of the 2 nd edition of the profile Interoperability using 1 st edition of the profile, including naming convention Model Authority Sets (MAS) and file headers – therefore merging process Incremental exchange Exchange of short-circuit data Exchange of dynamic models (standard models, user-defined models, proprietary models) – Further developments in the part of dynamics are not expected due to lack of the time Exchange “operations to planning” – The goal: detailed model to be exported to fit to ENTSO-E profile and imported by planning applications

News from WG 13 • Expect to freeze UML for CIM 15 by this week – WG 13 meeting • • • Agreed to merge Dynamics package in the official UML Agreed that ENTSO-E IOP will propose necessary modifications on “short-circuit” data problem. We need a dedicated call for this purpose Ready to explain changes from CIM 14 v 15 to CIM 15: • All changes are documented by CIM model manager and will be presented to IOP participants

Profile, UML • • • We need all changes agreed early enough so that the profile is generated on time. The profile will be based on UML created by CIMContextor. Then xmi file could be imported in CIMTool and different profiles generated. The exact process will be drafted and present to you in the next call(s). Please inform me which kind of files you need – owl, etc….

IOP organizational issues – teleconferences schedule, date, Share. Point • • • Teleconferences: Day in a week – MONDAY; Time: 17: 00 h CET IOP – held in Brussels, ENTSO-E premises on 11 -15 July IOP duration: most probably 5 days CIMug site: there will be a site for this ENTSO-E IOPs. The subject line of all emails exchanged in the frame of ENTSO-E IOP should start with [ENTSO-E IOP]: Issues to be addressed in the IOP calls have to be sent to Chavdar before the call