Network Codes Overview 1 st SEM RA/TSO Stakeholder Forum Mark Lane - - PowerPoint PPT Presentation

▶
network codes
SMART_READER_LITE
LIVE PREVIEW

Network Codes Overview 1 st SEM RA/TSO Stakeholder Forum Mark Lane - - PowerPoint PPT Presentation

Oct 18, 2022 320 likes •1.26k views

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

slide-1
SLIDE 1

Network Codes Overview

1st SEM RA/TSO Stakeholder Forum Mark Lane 17 January 2013

slide-2
SLIDE 2

Overview of Current & Future Network Codes

  • Requirements for Generators

(RfG)

  • Demand Connection Code

(DCC)

  • HVDC Connection Code

(HVDC)

  • Connection Procedures

(CP)

Connection Related Codes

  • Operational Security Network

(OS)

  • Operational Planning & Scheduling

(OPS)

  • Load Frequency Control & Reserves

(LFCR)

  • Operational Procedures in an Emergency

(EP)

  • Staff Training

(ST)

System Operation Related Codes

  • Capacity Allocation & Congestion Management (CACM)
  • Forward Capacity Allocation

(FCA)

  • Balancing Network Code

(BAL)

Market Related Codes

slide-3
SLIDE 3

Order of Work on Network Codes

HVDC High Voltage Direct Current Connection requirements BAL Electricity Balancing FCA Forward Capacity Allocation LFCR Load Frequency Control and Reserves OPS Operational Planning and Scheduling OS Operational Security DCC Demand Connection Code CACM Capacity Allocation and Congestion Management RfG Requirement for Generators

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

Therefore current Network Codes developed in this order

slide-4
SLIDE 4

Network Codes

ID

DA/ID link to Governance guideline

DA CC

All market codes link to transparency regulation

FCA

FCA Linked to MIFID

BAL DCC

Both linked to energy efficiency directive

RfG

All connection codes linked to existing standards

HVDC

CP

Linked to smart grid initiatives through DSR All connection codes link to BAL

All connection codes link to OS

EP

CC link to OS/OPS due to CGM

LFCR closely linked to BAL

OS OPS ST

LFCR

LFCR/OS closely linked

CACM

Code Overview

slide-5
SLIDE 5

Network Codes

System Operation Related Codes Update SEM RA/TSO Stakeholder Forum

Liam Ryan 17 January 2013

slide-6
SLIDE 6

System Operation Related Network Codes

slide-7
SLIDE 7

Purpose of the Operational Security

To set common rules for ensuring the operational security of the pan European power system.

slide-8
SLIDE 8

Operational Security Network Code Contents

  • 1. General provisions: Subject matter and scope, Definitions, Regulatory aspects,

Recovery of costs, Confidentiality obligations

Articles 1-5

  • 2. Requirements

Short circuit management Frequency control management Power flows management Voltage control and reactive power management Contingency Analysis and handling System states Protection Dynamic Stability Management

  • 6. Final provisions

Annex I Incidents Classification Scale

Articles 32-33 Article 11 Article 9 Article 7 Article 10 Article 12 Article 8 Article 13 Article 6

Data exchange

  • 3. Data exchange

Articles 14-27

Operational training and certification

  • 4. Training

Article 28

Responsibilities, Testing, Analysis (incl. PI)

  • 5. Compliance

Articles 29-31

slide-9
SLIDE 9

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-10
SLIDE 10

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-11
SLIDE 11

Network Code Development Operational Security Code

2012 / 13

Scoping

Step 1

Drafting

Step 2

Internal Approvals

Step 3

Public Consultation

Step 4

Analysis & updating

Step 5/6

Internal Approvals

Step 7

ACER approval & Comitology

Step 8

DT Kick Off Start (EC Letter) 1st Draft Code Updated Draft Code

  • 4. Stakeholder Workshop

Updated Code for approval

  • 3. Stakeholder Workshop

Final Draft Code Submission to ACER

2011

01 02 03 04 05 06 07 08 09 10 11 12 01 02 03

1.Stakeholder Workshop

  • 2. Stakeholder Workshop

Updated Code for approval

  • 5. Stakeholder Workshop

2012 2013

slide-12
SLIDE 12

Public Consultation

  • Outline key issues that are of relevance to SEM participants

20 40 60 80 100 120 140 160 180 27 33 32 16 5 17 24 25 13 26 4 9 23 28 31 19 22 29 30 12 15 18 3 21 20 10 7 11 8 14 1 6 2 5 3 3 7 7 7 7 12 11 15 16 15 19 19 21 18 19 19 23 29 25 29 30 33 49 65 64 69 90 92 101 131 167 20 40 60 80 100 120 140 160 180 27 33 32 16 5 17 24 25 13 26 4 9 23 28 31 19 22 29 30 12 15 18 3 21 20 10 7 11 8 14 1 6 2 5 3 3 7 7 7 7 12 11 15 16 15 19 19 21 18 19 19 23 29 25 29 30 33 49 65 64 69 90 92 101 131 167

Definitions System States Subject Matter and Scope Testing and Investigation Voltage Ctrl & Reactive Power Mgmt Contingency Analysis and Handling Frequency Control Mgmt Power Flows Mgmt Data Exchange (245) Regulatory Aspects

1 2

Over 1200 comments

slide-13
SLIDE 13

Next steps

  • Work continuing to incorporate the requests
  • f stakeholders and ACER
  • Develop final version and submit to ACER by

the end of Feb 2013

slide-14
SLIDE 14

Operational Planning and Scheduling Network Code

(OP&S NC)

slide-15
SLIDE 15

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.

slide-16
SLIDE 16

Contents of OP&S Network Code

16

slide-17
SLIDE 17

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-18
SLIDE 18

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-19
SLIDE 19

Network Code Development Operational Planning and Scheduling Code

2012 / 13

Drafting

Step 2

Internal Approvals

Step 3

Public Consultation

Step 4

Analysis & updating

Step 5/6

Internal Approval

Step 7

ACER approval & Comitology

Step 8

Start (EC Letter) Updated Draft Code

  • 3. Stakeholder Workshop
  • 2. Stakeholder Workshop

Final Draft Code Submission to ACER

03 04 05 06 07 08 09 10 11 12 01 02 03 04 05 06

  • 1. Stakeholder Workshop

Updated Code for approval

  • 4. Stakeholder Workshop

2012 2013 Draft Code Draft Code

slide-20
SLIDE 20

Public Consultation

850 comments received

slide-21
SLIDE 21

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
slide-22
SLIDE 22

Network Codes Load Frequency Control & Reserves (LFC&R)

slide-23
SLIDE 23

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.

slide-24
SLIDE 24

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-25
SLIDE 25

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-26
SLIDE 26

LFC&R Network Code Contents

26

  • Frequency Quality
  • Load – Frequency Control Structure
  • Frequency Containment Reserves
  • Frequency Restoration Reserves
  • Replacement Reserves
  • Cross Border Reserves
  • Synchronous Time Control
  • Cooperation with DSO
slide-27
SLIDE 27

Network Code Development – LFC&R Code

2012 / 13

Drafting

Step 1 & 2

Internal Approvals

Step 3

Public Consultation

Step 4

Analysis & updating

Step 5/6

Internal Approvals

Step 7

ACER approval & Comitology

Step 8

Start of the Process 1st Draft Code Updated Code for approval

  • 3. Stakeholder Workshop

Updated Code for approval

  • 2. Stakeholder Workshop

Final Draft Code Submission to ACER

06 07 08 09 10 11 12 01 02 03 04 05 06 07

  • 1. Stakeholder Workshop

2nd Draft Code Draft Code for public consultation

  • 4. Stakeholder Workshop

2012 2013

slide-28
SLIDE 28

Key Areas for Participants

  • Requirements on Reserve Providers
  • Exchange of Reserves between Synchronous Areas
  • Frequency Quality Evaluation
  • Your input to the Public consultation is essential
slide-29
SLIDE 29

What’s next?

  • Issue paper for publication consultation for 2 months, beginning of Feb

2013

  • Stakeholder workshop early Feb
slide-30
SLIDE 30

Thank you

slide-31
SLIDE 31
slide-32
SLIDE 32

RfG Network Code

1st SEM RA/TSO Stakeholder Forum Mark Norton 17 January 2013

slide-33
SLIDE 33

DCC

Both linked to energy efficiency directive

RfG

All connection codes linked to existing standards

HVDC

All connection codes link to BAL

CP

All connection codes link to OS Linked to smart grid initiatives through DSR

  • RfG was developed first
  • Followed by DCC
  • Soon HVDC will begin & CP

will follow

  • These codes link into (and

are influenced by) several important policy areas

  • And are also related to

existing standards Some of the more substantial links to others codes are;

  • Electricity Balancing; and
  • Operational Security

Grid Connection Codes

slide-34
SLIDE 34

Stages of Network Code Development (Pilot I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet perceived objectives of the FWGL (ERGEG)
  • Discuss & refine
  • Share with stakeholders

Step 2 - Drafting

  • Get comments from Committees & WGs
  • Update code principles before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 3 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps

Step 4 – Public Consultation Engage with stakeholders, EC & ACER throughout

slide-35
SLIDE 35

Stages of Network Code Development (Pilot II)

  • Review comments & listen to views
  • Develop reasons to change principles or not to change things
  • Identify key issues

Step 5 - Analysis of responses

  • Create the text to reflect comments (be open) working with user

group

  • Develop supporting material
  • Resolve contentious issues

Step 6 – Drafting of Network Code text

  • Review FWGL implications on RfG
  • Adjust Code text
  • Discuss with Stakeholders in User group and bilateral

Step 7 - Issue of draft FWGL from ERGEG

  • Get comments from Committees & WGs
  • Update code principles before committee approval
  • Seek Assembly approval to consult

Step 8 - Internal Approvals

Engage with stakeholders, EC & ACER throughout

slide-36
SLIDE 36

Stages of Network Code Development (Pilot III)

  • Listen to views (national and at EU level)
  • Get ready for next steps

Step 9 – 2nd Public Consultation on Draft Network Code

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 10 - Analysis of responses

  • Review FWGL implications on RfG
  • Adjust Code text
  • Discuss with Stakeholders in User group and bilateral

Step 11 - Issue of Final FWGL from ERGEG

  • Create the text to reflect comments (be open) working with user

group

  • Develop supporting material
  • Resolve contentious issues

Step 12 – Drafting of Network Code text

Engage with stakeholders, EC & ACER throughout

slide-37
SLIDE 37

Stages of Network Code Development (Pilot IV)

  • Get comments from Committees & WGs
  • Update code principles before committee approval
  • Seek Assembly approval to consult

Step 13 - Internal Approvals

  • Finish pilot project
  • Publish final draft
  • Provide proposals for future procedure of code development

Step 14 – Publish final code

Engage with stakeholders, EC & ACER throughout

slide-38
SLIDE 38

Stages of Network Code Development (I)

  • Newly formed ACER provides FWGL

Step 1 – Issue of FWGL

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 2- Scoping

  • Adjust draft pilot code text to meet objectives of the FWGL
  • Discuss & refine
  • Share with stakeholders

Step 3 - Drafting

  • Get comments from Committees & WGs
  • Update code principles before committee approval
  • Seek Assembly approval to consult

Step 4 - Internal Approvals

Engage with stakeholders, EC & ACER throughout

slide-39
SLIDE 39

Stages of Network Code Development (II)

  • 3 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps

Step 5 – Public Consultation

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 6 - Analysis of responses

  • Create the text to reflect comments (be open) working with user group
  • Develop supporting material
  • Resolve contentious issues

Step 7 – Drafting of Network Code text

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 8- Internal Approvals

  • Approval of supporting documents and code to Assembly
  • Submit approved code to ACER

Step 9 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-40
SLIDE 40

Network Code Development

Start (EC letter) Public consultation

07 08 09 10 11 12 01 02 03 04 05 06 07 08

2011

  • 1. Workshop

Stakeholders End (delivery to ACER) ENTSO-E Public Workshop ENTSO-E approval for consultation Irish Public Workshop

  • 2. Workshop

Stakeholders 2.EWEA Meeting

  • 2. Woekshop with DSOs
  • 1. Workshop DSOs

1.EWEA Meeting EUR 2012 EPIA

  • 3. Workshop DSOs
  • 3. Workshop

Stakeholders

slide-41
SLIDE 41

Objective/Scope of the Code

To define “Significant Grid User” consistent with the FWGL and other network codes and to develop functional specifications that are applicable to different Generators, from 800W upwards. The requirements should be non-discriminatory, and utilise the inherent capabilities of Generators to ensure or improve power system security and enhance market integration and wind energy penetration.

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 41

slide-42
SLIDE 42
  • Generator capabilities are formulated from a system

performance perspective, independent from technology

  • Need to be able to cope with evolutions in generation mix
  • Significance is regarded per requirement

Significant users

Type D Type C Type B Type A

Wide-scale network operation and stability including European-wide balancing services Stable and controllable dynamic response capabilities covering all operational network states Automated dynamic response and resilience to operational events including system operator control Basic capabilities to withstand wide-scale critical events; limited automated response/operator control

slide-43
SLIDE 43

Significant users

Network Code gives max. thresholds at synchronous system level

  • Criteria based on voltage level (> 110kV  Type D) and

MW capacity (table)

  • Decision at national level by National Regulatory

Authority

Synchronous Area maximum capacity threshold from which on a Generating Unit is of Type B maximum capacity threshold from which on a Generating Unit is of Type C Continental Europe 0.1 MW 10 MW Nordic 1.5 MW 10 MW Great Britain 1 MW 10 MW Ireland 0.1 MW 5 MW Baltic 0.1 MW 5 MW

slide-44
SLIDE 44

General provisions

Definitions Scope

Requirements

General requirements Synchronous Generating Units Power Park modules Offshore Power Park modules

Operational Notification Procedure for Connection

New generating units Existing generating units

Compliance

Compliance monitoring Compliance testing Compliance simulations

Derogations

Request Decisions

Final Provisions

Entry into force and application

  • f the Network

Code

Contents of Code

slide-45
SLIDE 45

Key Areas for Participants

  • At present stage in ACER approval phase, no further consultation is

expected until comitology.

slide-46
SLIDE 46
slide-47
SLIDE 47

DCC Network Code

1st SEM RA/TSO Stakeholder Forum Mark Norton 17 January 2013

slide-48
SLIDE 48

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft principles to meet the FWGL
  • Discuss & refine
  • Share with DSO TEG & bilateral with stakeholders
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code principles before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 3 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps

Step 4 – Stage 1 Public Consultation Engage with stakeholders, EC & ACER throughout

slide-49
SLIDE 49

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change principles or not to change things
  • Identify key issues

Step 5 - Analysis of responses

  • Create the text to reflect comments (be open) working with DSO

TEG and user group

  • Develop supporting material
  • Resolve contentious issues

Step 6 – Drafting of Network Code text

  • 3 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps

Step 7 – Stage 2 Public Consultation

  • n Draft
  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 8 - Analysis of responses

Engage with stakeholders, EC & ACER throughout

slide-50
SLIDE 50

Stages of Network Code Development (III)

  • Update the text to reflect comments on draft code
  • Develop supporting material
  • Resolve contentious issues

Step 9 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 10 - Internal Approvals

  • Present changes in network code post stage 2 consultation
  • Explain rational and drivers for change
  • Consultation before and preparation for ACER FWGL compliance phase

Step 11 – Public information session

  • Approval of supporting documents and code to Assembly
  • Submit approved code to ACER

Step 12 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-51
SLIDE 51

Network Code Development

FWGL Grid Connection Public consultation

07 08 09 10 11 12 01 02 03 04 05 06 07 08 09 10 11 12

2012 2013

ENTSO-E legal evaluation

Public Worshop Stage 2 End (delivery to ACER) ENTSO-E approval final version ENTSO-E approval for consultation ACER Meeting FWGL Grid Connection ENTSO-E approval for consultation Public consultation 2.DSO TEG drafting meeting

  • 1. DSO TEG drafting meeting
  • 3. DSO TEG drafting meeting
  • 4. DSO TEG drafting meeting

ACER Meeting

  • 3. DSO TEG drafting meeti
  • 5. DSO TEG drafting meeting
  • 1. IFIEC meeting
  • 6. DSO TEG drafting meeting

1.CECED meeting Public Worshop Stage 1

  • 2. DSO TEG/User meeting
  • 1. DSO TEG/User meeting
  • 7. DSO TEG drafting meeting

Irish Public Worshop Stage 2

  • 3. DSO TEG/User meeting

ENTSO-E legal evaluation ENTSO-E legal evaluation

  • 5. DSO TEG/User meeting
  • 4. DSO TEG/User meeting

ACER Meeting Public information session

slide-52
SLIDE 52

Objective/Scope of the Code

To define “Significant Grid User” consistent with the FWGL and other network codes and to develop functional specifications that are applicable to different Demand users, notably Transmission Connected Demand Facilities and DSOs, and Demand Side Response. The requirements should be non-discriminatory, and utilise the inherent capabilities of Demand Users to ensure or improve power system security and enhance market integration and wind energy penetration.

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 52

slide-53
SLIDE 53

General provisions

Definitions Scope

Requirements

Transmission Connected Demand Facilities Transmission Connected Distribution Networks Demand with DSR APC/RPC/TCM DSR SFC

Operational Notification Procedure for Connection

New Demand Facilities and Distribution Networks Existing Demand Facilities and Distribution Networks

Compliance

Compliance monitoring Compliance testing Compliance simulations

Derogations

Request Decisions

Final Provisions

Entry into force and application of the Network Code

Network Code structure

Contents of Code

slide-54
SLIDE 54

Key Areas for Participants

  • As code now submitted to ACER, participants have an opportunity to

attend ACERs workshop on the DCC on the 24th Jan 2013 in Slovenia.

  • Assuming successful approval of the compliance with the FWGL

then subsequent to this during the comitology phase

slide-55
SLIDE 55
slide-56
SLIDE 56

HVDC Network Codes

1st SEM RA/TSO Stakeholder Forum Salim Temtem/Mark Norton 17 January 2013

slide-57
SLIDE 57

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-58
SLIDE 58

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-59
SLIDE 59

Network Code Development – HVDC Code

01 02 03 04-05 05-06 06-07 08 09-10 11-12 01 02 03 2013

Scoping

Step 1

Drafting

Step 2

Internal Approvals

Step 3

Public Consultation

Step 4

Analysis & updating

Step 5/6

Internal Approvals

Step 7

ACER approval & Comitology

Step 8

DT Kick Off Start (EC Letter) 1.Stake holder Input Submission to ACER

slide-60
SLIDE 60

Objective/Scope of the Code

To define “Significant Grid User” consistent with the FWGL and other network codes and to develop functional specifications that are applicable to different HVDC and DC connected offshore PPM configurations. The requirements should be non-discriminatory, and utilise the inherent capabilities of HVDC systems and DC connected offshore PPMs to ensure or improve power system security and enhance market integration and wind energy penetration.

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 60

slide-61
SLIDE 61

Cross-border issues and signifiant Grid User

(EC) 714/2009 – Art. 8 (7)

  • “The network codes shall be developed for cross-border network issues and market integration issues and

shall be without prejudice to the Member States’ right to establish national network codes which do not affect cross-border trade”

  • The network code(s) developed according to these Framework Guidelines shall define appropriate minimum

standards and requirements applicable to all significant grid users.”

Context 3rd Energy Package

  • supporting the completion and functioning of the internal market in electricity and cross-border trade
  • facilitating the targets for penetration of renewable generation
  • maintaining security of supply

Rfg definition

  • All requirements that contribute to maintaining, preserving and restoring system security in order to

facilitate proper functioning of the internal electricity market within and between synchronous areas, and to achieving cost efficiencies through technical standardization shall be regarded as “cross-border network issues and market integration issues”.

Title of presentation | Author | Date | Page 61

slide-62
SLIDE 62

Types of HVDC and DC offshore Power Park Module

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 62

slide-63
SLIDE 63

A

HVDC Code TYPE -A- -B- -C- DC connection

B DC Connection SZA - SZB DC-Connection OS-SZ C Embedded DC within one SZ

slide-64
SLIDE 64

D-A

HVDC Code TYPE -D- (A, B or C as Multiterminal)

D DC Connection SZA – SZB Multiterminal DC-Multiterminal Connection OS-SZ D Embedded Multiterminal DC within one SZ D

D-B D-C

slide-65
SLIDE 65

F

HVDC Code TYPE -E- -F- -G- -H- Offshore PPMs

E DC connected OS (AC) PPMs Hybrid connected OS (AC) PPMs G DC GRID connected OS (AC) PPMs DC GRID connected OS (DC) PPMs H

DC Grid

slide-66
SLIDE 66

Example of Requirements

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 66

slide-67
SLIDE 67

Example of requirement

67

General provisions

Definitions Scope

Mandatory Requirements

Frequency Voltage Stability Connection and Disconnection Short Circuit Current Protection and Control

Non-Mandatory Requirements

Reactive Power BlackStart Power Quality Synthetic Inertia

Compliance

Compliance monitoring Compliance testing Compliance simulations Information exchange. Cooperation

These are preliminary requirements and are subject to change and consultation

slide-68
SLIDE 68

Network Code requirements

  • The Network Code lays down requirements and specific parameters
  • E.g. Frequency per area

Exhaustive requirements (Prescriptive)

  • The Network Code gives a coherent approach to formulate requirements
  • Avoids divergence of requirements throughout Europe
  • Specific setting of parameters based on a given legal framework, e.g. NRA

approval, consultation, in mutual agreement, other Network Codes, …

  • E.g. reactive power provision

Non-Exhaustive requirements (Framework )

  • High level requirement on functionality
  • Specific implementation prescribed by other agreements, national legislation,

Network Codes, …

  • E.g. information exchange or cooperation

Principle requirements (Process)

Title of presentation | Author | Date | Page 68

slide-69
SLIDE 69

Key Areas for Participants

  • Call for interest to join the user group is coming shortly on the

ENTSO-E website.

slide-70
SLIDE 70

What is the expectation of the audience for this Code?

HVDC Connection and DC connected Offshore Power Park Module Requirements | Salim Temtem | 24/10/2012 | Page 70

slide-71
SLIDE 71
slide-72
SLIDE 72

Network Codes CACM

1st SEM RA/TSO Stakeholder Forum Mark Lane 17 January 2013

slide-73
SLIDE 73

ID

DA/ID link to EC Governance guideline

DA

CC link to OS/OPS due to CGM

CC

All market codes link to transparency regulation

FCA

FCA Linked to MIFID

BAL

All connection codes link to BAL

  • Capacity Allocation and

Congestion Management was the first market code to be developed

  • Followed by Forward Capacity

Allocation

  • The Electricity Balancing code will

begin shortly.

  • All market related codes tie into

transparency regulation

  • Day Ahead & Intra Day are closely

linked to Governance Guideline

  • FCA has strong links to MIFID

These codes have direct links to

  • thers;
  • BAL to all connection codes
  • Also to LFCR operational code
  • Capacity Calculation links to

both OS and OPS

Market Based Codes

BAL closely linked to LFCR

slide-74
SLIDE 74

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-75
SLIDE 75

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-76
SLIDE 76

Network Code Development – CACM

06 07 08 09 10 11 12 01 02 03 04 05 06 07 08 09 10 11 12 2012 2013

Analysis & updating

Step 5/6

Internal Approvals

Step 7

ACER approval & Comitology

Step 8

  • 2. Stakeholder Workshop

Updated Code for approval Final Draft Code Submission to ACER ACER Formal Reasoned Opinion EC/ACER/ENTSO-E meeting ACER/ENTSO-E working meeting

slide-77
SLIDE 77
  • 2. Governance:

CACM Network Code Contents (final)

77

  • 1. General

Provisions:

Articles 1-8

  • 2. Requirements
  • 5. Final Provisions

Article 97

  • 4. Transitional

Arrangements

Capacity Calculation Articles 13-36 Bidding Zones Articles 37-40 Redispatching & Countertrading Articles 41 Algorithm Development / Amendment Articles 42-44 Day Ahead Market Articles 45-58 Intraday Electricity Market Articles 59-71 Roles & Responsibilities Articles 9-12 Clearing & Settlement Articles 72-75 Firmness Articles 76-80 Congestion Income Distribution Articles 81-82 XB Redispatching or Countertrading Cost Sharing Methodology Articles 83-84 CACM Costs Articles 85-90 Intraday arrangements Articles 91-93 Objectives & Provisions

  • f intraday arrangement

Island Systems with Central Dispatch Article 96 Articles 94-95 Subject Matter & Scope, Definitions, Confidentiality obligations, CACM objectives, Consultation, Publication CACM methods, Transparency, Regulatory approvals

slide-78
SLIDE 78

Other Developments

  • Governance Guideline

– meeting on 25 Jan

  • CEMC

– non-NWE TSOs

  • Bidding Zone pilot study

– Bidding Zone review of CWE, Denmark-West, CEE, Switzerland & Italy

  • Cross-Border Redispatch

– ACER/ENTSO-E joint task force – next meeting 29 Jan

slide-79
SLIDE 79
slide-80
SLIDE 80

Network Codes Balancing

1st SEM RA/TSO Stakeholder Forum Mark Lane 17 January 2013

slide-81
SLIDE 81

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-82
SLIDE 82

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-83
SLIDE 83

Network Code Development – Balancing

06 07 08 09 10 11 12 01 02 03 04 05 06 07 08 09 10 11 12 01 2012 2013

DT Kick Off Start (EC Letter) Scoping

Step 1

Drafting

Step 2

Internal Approvals

Step 3

Public Consultation

Step 4

Submission to ACER Analysis & updating

Step 5/6

Internal Approval

Step 7

ACER approval & Comitology

Step 8

  • 1. Stakeholder Workshop
  • 2. Stakeholder Workshop
  • 3. Stakeholder Workshop

Submission to MC

2014

  • 1. Stakeholder Advisory Group
  • 2. Stakeholder Advisory Group
  • 3. Stakeholder Advisory Group
  • 4. Stakeholder Advisory Group

1st Draft Code Submission to Assembly

slide-84
SLIDE 84

Other Developments Balancing Pilot Project(s)

  • AESAG – June 2012 – request ENTSO-E to develop pilot project for

balancing

1. Test the feasibility of the balancing target model and intermediate steps established in the ACER Framework Guidelines on Electricity Balancing. 2. Evaluate the associated implementation impact. 3. Report on the experience gained.

  • ToR being developed by ENTSO-E
  • Call for pilot project nominations expected shortly with deadline for

nominations likely by summer

slide-85
SLIDE 85
slide-86
SLIDE 86

Network Codes FCA

1st SEM RA/TSO Stakeholder Forum Mark Lane 17 January 2013

slide-87
SLIDE 87

Stages of Network Code Development (I)

  • Identify a structure.
  • Discuss key issues.
  • Ensure a common understanding

Step 1- Scoping

  • Draft text to meet the structure
  • Discuss & refine
  • Share with stakeholders & listen to views
  • Develop supporting material

Step 2 - Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval to consult

Step 3 - Internal Approvals

  • 2 month consultation
  • Listen to views (national and at EU level)
  • Get ready for next steps (don’t stop work)

Step 4 - Public Consultation

Engage with stakeholders, EC & ACER throughout

slide-88
SLIDE 88

Stages of Network Code Development (II)

  • Review comments & listen to views
  • Develop reasons to change or not to change things
  • Identify key issues

Step 5 - Analysis

  • f responses
  • Update the text to reflect comments (be open)
  • Develop supporting material
  • Resolve contentious issues
  • Manage member states

Step 6 - Updated Drafting

  • Get comments (avoid detail) from Committees & WGs
  • Update code before committee approval
  • Seek Assembly approval

Step 7 - Internal Approvals

  • Submit supporting documents and code to Assembly
  • Submit approved code to ACER

Step 8 - Final Submission

Engage with stakeholders, EC & ACER throughout

slide-89
SLIDE 89

Network Code Development – FCA

06 07 08 09 10 11 12 01 02 03 04 05 06 07 08 09 10 11 12 2012 2013

Scoping

Step 1

Drafting

Step 2

Internal Approvals

Step 3

Public Consultation

Step 4

Analysis & updating

Step 5/6

Internal Approvals

Step 7

ACER approval & Comitology

Step 8

DT Kick Off Start (EC Letter)

  • 1. Stakeholder Advisory Group
  • 2. Stakeholder Advisory Group

1st Draft Code

  • 3. Stakeholder Advisory Group
  • 1. Stakeholder Workshop

Updated Code for approval

  • 2. Stakeholder Workshop

Final Draft Code Submission to ACER

  • 4. Stakeholder Advisory Group

Preliminary Draft Code Missing sections sent to SAG

slide-90
SLIDE 90

Network Code Development – FCA

January 2013 February 2013 March 2013 Q1 2013

Drafting

Step 2

Internal Approvals

Step 3

  • 3. Stakeholder Advisory Group
  • 4. Stakeholder Advisory Group

FCA DT Meeting Submission to MC Revised draft to SAG FCA DT Meeting FCA DT Meeting Submission to Assembly ACER/ENTSO-E bilateral

slide-91
SLIDE 91
  • 2. Governance:

FCA Network Code Draft Contents (1/10/12)

91

  • 1. General

Provisions:

  • 2. Requirements
  • 5. Final Provisions
  • 4. Transitional

Arrangements

Capacity Calculation Bidding Zones Forward Capacity Allocation Allocation Platforms & Secondary Trading Roles & Responsibilities Allocation Rules Firmness Congestion Income Distribution Cost Recovery Regional Allocation Platforms Subject Matter & Scope, Definitions, Confidentiality obligations, Consultation, Publication of information, Transparency of information, Regulatory approvals Regional Allocation Rules Transitional arrangements in CACM Delegation of roles Stakeholder Committee CGM, CC Methodologies, CC Process, Biennial Reports Options for XB risk hedging, PTR Nomination, Processes/Operation Establishment, Tasks, Requirements Introduction, Requirements

slide-92
SLIDE 92

Other Developments MiFID II

  • 3 December – Council compromise

– Exempts auction offices – Secondary markets may not be covered under exemption

slide-93
SLIDE 93