320 likes | 329 Views
ENTSO-E CIM implementation. Olivier Aine. CIM user group 7 June 2018, Ljubljana. Content. What is ENTSO-E? Network codes implementation Why ENTSO-E uses the CIM? Success stories and lessons learnt Future developments. What is ENTSO-E. Our network. “Enabling the energy transition”.
E N D
ENTSO-E CIM implementation Olivier Aine CIM user group 7 June 2018, Ljubljana
Content • What is ENTSO-E? • Network codes implementation • Why ENTSO-E uses the CIM? • Success stories and lessons learnt • Future developments
Our network “Enabling the energy transition”
ENTSO-E in numbers 1 136 795 MW net generation capacity 43 TSOs, 36 countries 3 597,1TWh electricity consumpion 500+ million citizens served 478 132 km cross-frontier transmission lines 424 139 GWh of electricity exchanged between TSOs
2009 2014 2017 2020 2025 4.0 1.0 2.0 3.0 5.0 NC implementation Clean Energy Package draft Data platforms and tools Work products 2.0 Board strategy for more leadership in energy transition NC implemented New codes on cybersecurity and flexibility? Regional cooperation CEP entry into force Foundation Development of mandates: codes, TYNDP In the middle of implementation of the Clean Energy Package…?
The code families https://www.youtube.com/watch?v=GUjRJ_a93Pc
Timelines 2009 2017 2018 2019 2020 2021 2022 2023 Network codes 2015 2016 … Capacity Allocation and Congestion Management CACM implementation Forward Capacity Allocation FCA implementation • Third Energy Package Electricity Balancing EBGL implementation System Operation SOGL implementation
Projects from the codes Market • Imbalance Netting EU platform • Replacement Reserve EU platform • Automatic Restoration Reserve EU platform • Manual Restoration Reserve EU platform • Cross Zonal Capacity Allocation for balancing • Single Allocation Platform • Harmonised Physical Transmission Right Nomination Rules • Day ahead and Intraday Market Coupling • Coordinated Capacity Calculation (including flow based) • Common Grid Model Methodology • Publications to ACER • Coordinated Security Analysis • IGM/CGM merging for Y-1, DA and ID including boundary management • Operational Planning Data Environment (OPDE) • Outage Planning Coordination (Pan-European and regional) • Short-Medium Term Adequacy Assessment forecast • Pan-European Verification Function Operation
Two examples of projects Electricity balancing Common Grid Model
Electricity Balancing FCR • Automatic activation • Up to 15 minutes aFRR • Automatic activation • 30 s to 15 min mFRR • Semi-automatic ormanual activation • Min. 15 min RR • Semi-automatic ormanual activation • Min. 15 min Δf Frequency(50 Hz) Total balancing energy (idealized) Balancingenergy t0+45 min t0+5 min t0 t0+30 s t0+15 min Time Sync.area Affected TSO
Offer which must beactivated (activation call) Bids CZcapacity Satisfied imbalance needs Demands Electricity Balancing TSO 1 All TSOs governance … EUplatform EUplatform EUplatform Used cross-border capacity TSO N BSPs TSO 1 BSPs … Settlement BSPs TSO N BSPs European platforms coordinate balancing energy activation requests of TSOs. Communication with national BSPs remains local. Platform describes business processes on European level supported by different functions potentially performed by different IT systems. Page 14
Common Grid Model • Merging IGM to CGM • Enable services from the Regional Security Coordinators
CGM dependent Business Processes Individual Grid Model (IGM) production IGM validation IGMs Merge CGM publication Execute Operational Services Network Security Analysis Boundery Manage-ment Master Date Network Model Loca l Quality Control OutagePlanning OutagePlanning Pan European VerificationFunction (PEVF) EMS / Operational Planning Market data Market data Short Term Adequancy Network Planning CGM Aligment Function Regional Security Coordination Transmission System Operator Capacity Alocation
Grid Model across Time Horizons • Grid Planning • Market & Operational Planning • Capacity & Security • Grid extension • Maintenance • Security • Execution • Day ahead • Year ahead • Week ahead • Real-time • Month ahead • Intraday Confidence level
ECP ECCo SP EDX Based on MADES (IEC 62325-503)
Why ENTSO-E uses the CIM ESMP and CGMES
So why should we use the CIM? https://transparency.entsoe.eu/ https://tyndp.entsoe.eu/
So why should we use the CIM? • Question appeared already in 2009 when ENTSO-E was mandated to build the Transparency Platform and the Ten-Year-Network-Development-Plan (TYNDP) • In these two projects, 43 TSOs needs to send their data to a central platform (which need to understand them) • Therefore, a standardized format is needed for the data exchanges. • In 2012, ENTSO-E choose to use the CIM
How ENTSO-E became a proactive user of the CIM • ENTSO-E has Working Groups of TSOs expert to work on the data formats and liaises with IEC TC57 WG13-WG14 and WG16 • ENTSO-E maintains close collaboration with Network code drafting, implementation project and CIM profile development • ENTSO-E follows step-by-step approach from use case to sequence diagram to profile
1: ENTSO-E WGs and liaisons Liaisons with IEC TC57 WG 13/14/16 CIM Expert Group (EDI+CGM WP2) Liaison with IEC TC57 WG 10 AhG 61850 (Hierarchy)
2: ENTSO-E collaboration structure IEC/CENELEC ENTSO-E Standardization process Draft the Network Codes Draft profiles in WGs Liaison D implement NC projects Regulated by ACER / NRAs Maintenance requests
3: ENTSO-E step-by-step approach GenericUse Cases (GUC)
CIM profile for the balancing ATC (ECAN) XB Capacity MOL* (ERRP) remaining XB capacity TSO 1 Offer which must be activated & needs satisfied Incremental XB schedules EU balancing Platform Res bid* (ERRP) Bids Schedule (ESS) BSPs BSPs BSPs BSPs TSO 1 Reporting doc . . . . . . Needs Verificationplatform Transparency balancing Energy Account Transparencyplatform Settlement process TSO n TSO n
CGMES profile for IGM / CGM merging TS IEC 61970-600-1 – Energy Management System Application Program Interface (EMS-API) – Part 600-1: Common Grid Model Exchange Specification (CGMES) – Structure and rules (proposed IEC 61970-600-1 TS) TS IEC 61970-600-2 – Energy Management System Application Program Interface (EMS-API) – Part 600-2: Common Grid Model Exchange Specification (CGMES) – Exchange profiles specification (proposed IEC 61970-600-2 TS) CGMES IEC 61968-4 IEC 61970-552 IEC 61970-301 IEC 61970-302 IEC 61970-452 IEC 61970-453 IEC 61970-457 IEC 61970-456 EQ [.xml] SSH [.xml] SV [.xml] TP [.xml] EQ_BD [.xml] TP_BD [.xml]
All our CIM profiles are on ENTSOE.EU https://www.entsoe.eu/digital/common-information-model/ https://www.entsoe.eu/publications/electronic-data-interchange-edi-library/
Challenges and future developments • More and more business process link the grid model and the electricity market • CGMES was first built for grid planning, some further improvement will be needed for system operation • Even when there's none left, there are still some: after the network codes will come the Clean energy package (4th package) • Clean Energy Package is more oriented towards DSO: • Network codes on distributed flexibilities? • CIM for retail market? • CGMES for DSO use cases? • CIM to support TSO/DSO data exchanges? • ENTSO-E participates to the H2020 EU funded project TDX ASSIST • ENTSO-E participates to the SGTF on data format and procedures
Thank you Olivier Aine – olivier.aine@entsoe.eu