Network Codes Overview 1 st SEM RA/TSO Stakeholder Forum Mark Lane 17 January 2013
Overview of Current & Future Network Codes • Operational Security Network (OS) System • Operational Planning & Scheduling (OPS) Operation • Load Frequency Control & Reserves (LFCR) Related Codes • Operational Procedures in an Emergency (EP) • Staff Training (ST) • Requirements for Generators (RfG) Connection • Demand Connection Code (DCC) Related Codes • HVDC Connection Code (HVDC) • Connection Procedures (CP) • Capacity Allocation & Congestion Management (CACM) Market Related • Forward Capacity Allocation (FCA) Codes • Balancing Network Code (BAL)
Order of Work on Network Codes Through a ‘Priority List’ agreed upon through consultation with ACER/ENTSO-E Decided By EC ENTSO- E’s 3 year work plan Influenced by and informs RfG Requirement for Generators CACM Capacity Allocation and Congestion Management DCC Demand Connection Code OS Operational Security Therefore current OPS Operational Planning and Scheduling Network Codes LFCR Load Frequency Control and Reserves developed in this order FCA Forward Capacity Allocation BAL Electricity Balancing HVDC High Voltage Direct Current Connection requirements
Code Overview Both linked HVDC to energy RfG efficiency directive Linked to All smart grid connection CP DCC initiatives codes link through to BAL DSR All All Network DA/ID link to connection ID BAL connection Governance codes linked codes link Codes guideline to existing to OS standards LFCR All market closely codes link to CACM DA LFCR OS transparency linked to regulation BAL LFCR/OS OPS ST FCA CC closely linked CC link to EP FCA Linked OS/OPS due to MIFID to CGM
Network Codes System Operation Related Codes Update SEM RA/TSO Stakeholder Forum Liam Ryan 17 January 2013
System Operation Related Network Codes
Purpose of the Operational Security To set common rules for ensuring the operational security of the pan European power system.
Operational Security Network Code Contents 1. General provisions : Subject matter and scope, Definitions, Regulatory aspects, Articles 1-5 Recovery of costs, Confidentiality obligations System states Article 6 Short circuit Frequency control management management Contingency Analysis and handling Article 11 Article 7 Article 9 Article 12 Article 13 2. Requirements Dynamic Stability Protection Article 10 Article 8 Management Voltage control and Power flows reactive power management management 3. Data exchange Data exchange Articles 14-27 Operational training and certification 4. Training Article 28 5. Compliance Responsibilities, Testing, Analysis (incl. PI) Articles 29-31 6. Final provisions Annex I Incidents Classification Scale Articles 32-33
Stages of Network Code Development (I) • Identify a structure. Step 1- Scoping • Discuss key issues. • Ensure a common understanding • Draft text to meet the structure Engage with Step 2 - Drafting • Discuss & refine • Share with stakeholders & listen to views stakeholders, • Develop supporting material EC & ACER throughout Step 3 - Internal • Get comments (avoid detail) from Committees & WGs • Update code before committee approval Approvals • Seek Assembly approval to consult Step 4 - Public • 2 month consultation • Listen to views (national and at EU level) Consultation • Get ready for next steps (don’t stop work)
Stages of Network Code Development (II) Step 5 - Analysis • Review comments & listen to views • Develop reasons to change or not to change things of responses • Identify key issues Step 6 - Updated • Update the text to reflect comments (be open) Engage with • Develop supporting material Drafting • Resolve contentious issues stakeholders, • Manage member states EC & ACER throughout Step 7 - Internal • Get comments (avoid detail) from Committees & WGs • Update code before committee approval Approvals • Seek Assembly approval Step 8 - Final • Submit supporting documents and code to Assembly Submission • Submit approved code to ACER
Network Code Development Operational Security Code 2012 / 13 DT Kick Off Start (EC Letter) 1.Stakeholder Workshop 1 st Draft Code 2. Stakeholder Workshop Updated Draft Code 3. Stakeholder Workshop Updated Code for approval 4. Stakeholder Workshop 5. Stakeholder Workshop Updated Code for approval Final Draft Code Submission to ACER 2011 01 02 03 04 05 06 07 08 09 10 11 12 01 02 03 2013 2012 Scoping Drafting Internal Public Analysis & updating Internal ACER Approvals Consultation approval & Approvals Comitology Step 7 Step 1 Step 2 Step 3 Step 4 Step 5/6 Step 8
Public Consultation 167 2 167 2 131 6 131 6 101 1 • 101 1 Outline key issues that are of relevance to SEM participants Definitions 92 14 92 14 90 8 90 8 69 11 69 11 64 7 System States 64 7 65 10 65 10 49 20 33 49 21 20 Subject Matter and Scope 30 3 33 21 29 18 30 3 25 15 29 18 Testing and Investigation 29 12 25 15 23 30 29 12 19 29 23 30 Voltage Ctrl & Reactive Power Mgmt 19 22 19 29 19 18 19 22 21 31 19 18 28 19 Contingency Analysis and Handling 19 23 21 31 15 9 19 28 16 4 19 23 Frequency Control Mgmt 15 26 15 9 11 13 16 4 12 25 15 26 Power Flows Mgmt 7 24 11 13 7 17 12 25 7 5 7 24 7 16 Regulatory Aspects 7 17 3 32 3 7 33 5 Over 1200 comments 5 27 7 16 Data Exchange (245) 3 32 0 20 40 60 80 100 120 140 160 180 3 33 5 27 0 20 40 60 80 100 120 140 160 180 1 2
Next steps • Work continuing to incorporate the requests of stakeholders and ACER • Develop final version and submit to ACER by the end of Feb 2013
Operational Planning and Scheduling Network Code (OP&S NC)
Purpose of the Operational Security Sets requirements, ranging from the year ahead timeframe to real time , for assessing the adequacy and operational security of the interconnected power system and for planning outages required by TSO’s and grid users when they have cross borders impacts on power flows.
Contents of OP&S Network Code 16
Stages of Network Code Development (I) • Identify a structure. Step 1- Scoping • Discuss key issues. • Ensure a common understanding • Draft text to meet the structure Engage with Step 2 - Drafting • Discuss & refine • Share with stakeholders & listen to views stakeholders, • Develop supporting material EC & ACER throughout Step 3 - Internal • Get comments (avoid detail) from Committees & WGs • Update code before committee approval Approvals • Seek Assembly approval to consult Step 4 - Public • 2 month consultation • Listen to views (national and at EU level) Consultation • Get ready for next steps (don’t stop work)
Stages of Network Code Development (II) Step 5 - Analysis • Review comments & listen to views • Develop reasons to change or not to change things of responses • Identify key issues Step 6 - Updated • Update the text to reflect comments (be open) Engage with • Develop supporting material Drafting • Resolve contentious issues stakeholders, • Manage member states EC & ACER throughout Step 7 - Internal • Get comments (avoid detail) from Committees & WGs • Update code before committee approval Approvals • Seek Assembly approval Step 8 - Final • Submit supporting documents and code to Assembly Submission • Submit approved code to ACER
Network Code Development Operational Planning and Scheduling Code 2012 / 13 Start (EC Letter) Final Draft Code Submission to ACER Draft Code 1. Stakeholder Workshop Draft Code 2. Stakeholder Workshop Updated Draft Code 3. Stakeholder Workshop 4. Stakeholder Workshop Updated Code for approval 03 04 05 06 07 08 09 10 11 12 01 02 03 04 05 06 2012 2013 Drafting Internal Public Analysis & ACER Internal Approvals Consultation updating approval & Approval Comitology Step 4 Step 5/6 Step 2 Step 3 Step 7 Step 8
Public Consultation 850 comments received
What’s next? • Review comments & listen to views for consultation • Identify key issues • Work continuing to incorporate the requests of stakeholders and ACER • Develop final version and submit ACER by the end of March 2013
Network Codes Load Frequency Control & Reserves (LFC&R)
Purpose of the Load Frequency Control & Reserves NC • To set out coordinated and clearly specified load frequency control processes and rules regarding the levels and location of reserves (back-up) which TSOs need to hold .
Stages of Network Code Development (I) • Identify a structure. Step 1- Scoping • Discuss key issues. • Ensure a common understanding • Draft text to meet the structure Engage with Step 2 - Drafting • Discuss & refine • Share with stakeholders & listen to views stakeholders, • Develop supporting material EC & ACER throughout Step 3 - Internal • Get comments (avoid detail) from Committees & WGs • Update code before committee approval Approvals • Seek Assembly approval to consult Step 4 - Public • 2 month consultation • Listen to views (national and at EU level) Consultation • Get ready for next steps (don’t stop work)
Recommend
More recommend
