4th Stakeholder Workshop Federal Grid Code and General .../media/files/Elia/users-group/WG Belgian...

4th Workshop: Federal Grid Code

and General Requirements – DAY 1

Implementation European Network Codes

Royal Library (KBR)

Brussels, 6 February 2018

Planning of the day

4th Workshop Federal Grid Code and General Requirements

9:00 Welcome and coffee

9:15 Introduction and Federal Grid Code (Part I)

11:00 Break

11:15 Federal Grid Code (Part II)

12:45 Lunch

13:30 Federal Grid Code (Part III)

15:00 Break

15:15 Presentation draft CBA and derogation proposal

17:00 End

2

Draft agenda 4th Workshop (6 & 7/2/2018)


Tuesday 6th February Wednesday 7th February

1. Federal Grid Code

• Market aspects

• Metering

• Definitions (market)

Federal Grid Code

• DSO aspects

• Offshore

• Connection (incl. CDS)

2. Presentation package approach General Requirements NC RfG, DCC and

HVDC

3. Stakeholder feedback Stakeholder feedback

3

DAY 1

1. Introduction

2018 mei jul sep nov 2018 mrt mei

Workshop 1

22/9/2017

Workshop 2

23/11/2017

Workshop 3

18/12/2017

Workshop 4

6-7/2/2018

WG BG

19/6/2017

Submission: - FTR proposal - general req. - ABCD proposal

17/5/2018

Public consultation limits ABCD

19/5/2017 – 20/6/2017 Public consultation FTR and Gen Req.

15/3/2018 - 15/4/2018

Planning and agenda workshops

with focus on Federal Grid Code and general requirements

“Normal” WG BG meetings

“Normal” WG Bal meetings

“Normal” WG EMD/SO meetings

The normal UG Working Groups can work in support of the FTR workshops, e.g. for discussing topics for which it

is too early to discuss concrete amendment proposals (e.g. non-NC “wish-list”).

WG BG

04/9/2017

WG BG

07/11/2017

WG BG

01/12/2017


Full scope Info Session

12/3/2018

• Task Force “Implementation Network Codes” has ended.

• 4 dedicated workshops for discussing:

• Federal Grid Code impact and amendment proposals

• Progress on general requirements

• All interested parties are welcome.

• All workshop material will be distributed prior

to the workshop allowing preparation by all

parties + everything will be published on elia.be

WG BG

23/1/2018

WG BG

23/2/2018

CuRe Network Codes Workshop

29/3/2018

5

Public consultation

4th Workshop Federal Grid Code and General Requirements 9

2018 2018 mrt apr mei jun

Submission FGC and GR 17/5/2018

Submission T&C BRP/BSP 18/6/2018

15/3 - 15/4 Public consultation FGC

15/3 - 22/4 Public consultation GR

15/3 - 15/5 Public consultation T&C BRP/BSP

Consultation period extended

with one additional week

Proposal Public consultation Submission

Federal Grid Code FRA + NED FRA + NED

General Requirements ENG FRA + NED (+ ENG)

T&C BRP FRA + NED FRA + NED

T&C BSP ENG FRA + NED

2. Federal Grid Code

2.1 Proposal Federal Grid Code:

Market aspects

4th Stakeholder Workshop Federal Grid Code and General Requirements (DAY 1)

Anna Tsiokanos

6th February 2018

Agenda

1. Non-balancing Ancillary Services

1. Mvar

2. Restoration services ( Black start)

2. Offshore Storm Risk mitigation measures

3. Icaros

4. Emergency and Restoration

5. Miscellaneous


Wrap up: New Structure of FGC


Title 4 Access

CH. article content

1 142-155 How to become BRP/ACH

2 156-160 Balancing responsibilities

(BRP/TSO)

2 161-162 Grid Losses

3; 4 163-175 Access to the Grid

+subscription

5 176-184 Interconnections

6; 7; 8 185-204 BFU ( + signes CIPU)

9; 10 204-209 Reactif & secours

11; 12 210-230 Nominations( +CIPU)

13 231-266 A.S. (Rx,Mvar,BS,conj)

14 267-297 CIPU

15 297-311 Conduite du réseau

16 312-315 Emergency + Restoration

17 317-319 renewable

Title 4.2 Access

Ch. article content

New 1 ACH responsibilities &

How to become ACH

3 163-173 New AP to a ACH contract

4 174-175 Subscription

“Puissance mise à disposition”

9; 10 204-209 Reactif & secours

Title 4.1 Balancing

Ch. article content

2 157-160 Balancing (BRP/TSO + BSP)

2 156 BRP responsibilities

2 161-162 Grid Losses

6; 7; 8 185-204 BFU ( +temp signes CIPU)

11; 12 210-230 Nominations( +BFU+ CIPU)

1 142-155 How to become

BRP/ACH

5 176-184 Interconnections

13 231-266 balancing A.S.

Title 4.3 Grid operation

Ch. article content

13 231-266 Non balancing A.S. (Mvar,BS,conj)

14 267-297 CIPU

15 297-311 Conduite du réseau

17 317-319 Renewable

16 312-315 Emergency + Restoration

~55%

~35%

~10%

3

+ Storm Risk

As is : Articles 257 -259 of FGC:

257:

• TSO determines technical specifications of service

(availability and delivery)

• Service constituted through a call for tender/competition

procedure

• TSO fixes modalities for availability and delivery in

contract

• If not enough volume offered, TSO may appoint

producers which are obliged to offer at reasonable price

258 & 259:

• Technical specifications for the delivery of the service

depending on type of unit (réglante/non réglante)

Mvar


4

In practice not used; Art. 12 quinuies Elaw foresees Royal decree

Changing context:

• New connexion requirements on Mvar capability < RFG

• Currently not enough Mvar offered/ no liquid market

• Mvar procurement mechanism will be analysed and reorganised in

2018 (incentive )

• EU benchmark made in this context

• Design currently discussed with stakeholders

Implications for FGC: Framework describing main principles

while keeping enough open possibilities for review of mechanism

in 2018. [ see extract art 257 of proposed draft]

§1& 2: Introduction of Terms and Conditions which are consulted &

regulated

Open possibilities for mechanism (call for tender/ standard contract…)

Financial principles to be determined (competent authority)

§3&4: Increase participation:

mandatory for assets submitted to capability obligation

voluntary for others

Grid user or 3rd party (Voltage Service Provider)

As is : Articles 261 -264

• 261: Black Start definition

• 262: TSO determines technical specifications of service

and means needed to participate to restoration of grid

• 263:

• Service constituted through a call for

tender/competition procedure

• TSO fixes modalities for availability and delivery in

contract

• 264: contracts determine availability and activation

modalities

Black Start


7

Changing context:

• RFG and E&R

• Several possible Restoration Services (BS capability, house loading islanding…)

• capability obligation for some assets (ex: art 15.5.c of RFG for new PGM C)

• Terms and Conditions for Restoration service Providers (E&R, by end 2018)

• Currently no liquid market

• Black Start procurement mechanism will be analysed and reorganised in

2018 (incentive )

Implications for FGC: Framework describing main principles while keeping enough open possibilities

for review of mechanism in 2018. [see new art 261-264 of draft proposal]

261. Definition of Restoration Service

262. TSO describes technical specs, participation conditions & mechanism in Terms and Conditions RSP (cf foreseen by E&R)

Open possibilities for mechanism (call for tender/ negociated procedure, other …)

Financial principles to be determined ex ante (competent authority)

263. Mandatory participation for assets submitted to capability obligation, voluntary for others *

264. Link contract & T&C

Offshore mitigation – proposed operational process

8

Ex ante:

• 157: BRP must foresee means to balanced.

Add: Right for Elia to request / challenge /

impose means.

187+148: remind that a BRP he should be

requested to prove/comply with art 157 when he

becomes BRP/is designated on an AP

151: Reinforce existing right for Elia to suspend

BRP who does not foresee/maintain his technical

capability foreseen in art 157§2.

connexion: possibility for TSO to request in

connexion contract specific data exchange (wind

measurement)

During event:

• SOGL framework:

• By 18 m TSO has to develop a LFCBA

• LFCBA contains dimensioning methodology but

also several procedures (ex: exhausted reserves,

escalation procedure…)

234 : framework for start LFCBA procedures ex:

• when bal. capacity is missing due to BSPs (not

offered or unavailable)

• Abnormal imbalance (>> dimensioned need ) due

to BRPs who didn’t anticipate such situations or

other exceptional phenomenon

Ex Post :

307bis: in case of stop due to

storm the S.A must receive

authorisation of TSO before

reinjecting in grid. TSO may also

impose restrictions ….

198: SA obligations taken by

BRP during transitory period

through CIPU &/or BRP

contract. 4th Workshop Federal Grid Code and General Requirements

Changing perspective


Present

ARP

Future

Outage Planning

Agent

Scheduling Agent

BSP

Roles introduced by GL SO

Role introduced by

GL EB

CIPU

Redispatching

flexibility Scheduling

Free balancing

bids

Availability

plans

Redispatching

flexibility Scheduling

Free balancing

bids

Availability

plans

Large

Generation

(TSO-

connected)

Generation

TSO/DSO

Load

Storage

Red Zones Mechanism

Congestion Risk Indicator (CRI)

Regulatory approach

10

EU GL

(SO GL & KORRR, EB GL)

- Introduction of Outage Planning

Agent and Scheduling Agent

- Responsibilities

- Scope of data exchange:

New FGC

- Focus on fundamental principles

- Set framework for T&C

Current FGC

- content of the CIPU contract in an

elaborated way: list of procedures

and modalities

Imposed requirements

without exemptions

Imposed requirements with

exemption possibility

Proposed requirements &

processes

Formalize exemptions

Confirm use

Terms & Conditions

- Elaboration of design principles


TSO-connected TSO-connected CDS-connected TSO-

connected

(incl. CDS)

DSO-connected

Asset type PGM D

PGM C PGM B PGM D PGM C PGM B Demand

facility

PGM C PGM B

Unavailabilit

y plan

Obliged Obliged Obliged Proposed* Proposed* Proposed* If Xborder

relevant Proposed* Proposed*

Scheduling

in DA

Obliged Obliged Obliged Proposed* Proposed* Proposed* Proposed* Proposed* Proposed*

Scheduling

in ID


TSO-connected TSO-connected CDS-connected TSO-

connected

(incl. CDS)

DSO-connected

Asset type PGM D

PGM C PGM B PGM D PGM C PGM B Demand

facility

PGM C PGM B

Unavailabilit

y plan

Obliged Obliged Obliged Proposed* Proposed* Proposed* Proposed** Proposed* Proposed*

Scheduling

in DA


Scheduling

in ID


GL SO on operational information exchange:

Outage Planning & Scheduling Obligations per asset type

11

* Obliged unless otherwise provided by TSO

**lighter unavailability plan unless if Xborder relevant in which case same un.plan as for PGMs

Need confirmed by Elia

Under discussions with

DSOs

Out of scope FGC

Article 267describes scope of chapter and the assets concerned (connected to federal grid, behind GU installations or in CDSO)

Article 268 on outage planning obligations : assets obliged + what info to be provided

Article 272 for scheduling obligations: assets obliged/exempted + info to be provided 4th Workshop Federal Grid Code and General Requirements

Proposal on roles


Outage Planning

Agent

Scheduling

Agent

Outage Planning

Scheduling

Bidding for

redispatching

* Note 1: The official responsibility for the bidding for redispatching lies with the scheduling agent (either GU or BSP). If the GU is the scheduling agent, in practice the task to enter the bidding

information on the platform for Elia may be delegated to the BSP (who also enters the bidding information for balancing) if GU and BSP agree to do so.

* Note 2: In case of Gflex contract: Grid User always has the responsibility for decremental flex; incremental flex could be commercialized via another market party

Grid User or other market party appointed by the Grid User

Grid User or the FSP/BSP appointed by the Grid User *

Articles 268 & 269 for outage planning agent

Article 272 & 273 for scheduling agent

II. Outage planning

268.What assets and what information

PGM + Storage BCD ; demand facilities

269.Roles : OPA= GU or 3rd party

Announced to TSO in connexion contract or contract with CDSO

270. +271 T&C structure + associated contract

Eventual remunerations are cost reflective

308. Additional dispositions coming from existing FGC

OPA has to inform TSO asap in case of F.O of the asset

Chapter III: structure and main content

13

III. Scheduling and Redispatching

272.What assets and what

PGM + Storage BCD ; demand facilities are exempted

273.Roles : SA = GU or 3rd party ;

if BSP: SA = GU or BSP

274.Bidding of remaining available flex to TSO

Mandatory for PGM/storage +Voluntary for demand assets (by SA)

275.+276 T&C structure + associated contract

Eventual remunerations are cost reflective

Return to program may be requested by TSO if deviation

306.-307bis: Additional dispositions 306. SA communicates set point to TSO

307. If risk: Return to schedule + costs for SA

307. Bis: If offshore windfarm stops production due to weather perturbation, TSO

must agree before reinjection to the grid and can impose operational restrictions

I. Scope (what assets, what grid(s))

article

section

IV. Interactions Info from OPA, SA, BRP, BSP have to be consistent and coherent GU has a role

Elia may reject/ask to adapt or adapt programs



Emergency & Restoration

Approach: Create enough framework and fix important elements while keeping enough open possibilities for 2018.

adapt FGC when contradictions or redundancies

precise some elements of NC in FGC

keep some Belgian specificities

Let open elements that have to be analysed in 2018 (with stakeholders)

Context • A whole NC has entered into force regarding that topic

• A consequent implementation action plan has to be performed (including public consultations ) by end of 2018

• Current FGC foresees +/- 5 articles on emergency situations, in which the legal framework is set

• In 2015, it has been adapted in order to be more compliant with adequacy issues

Plan de Sauvegarde (art 312-13)

• No consultation; CREG notified

• HL structure + some actions (MW/Mvar/ disconexion of borders)

• Among actions “plan de délestage”

• Priority to some grid elements (hospitals…)

in coordination with DSOs for those elements


Emergency plans and procedures

NC E&R

FGC – royal decree

System Defence Plan

• Public consultation

• Detailed technical requirements and actions • Ex: Under and Over frequency

• Ex: 45 % of load & 8 levels of disconnection

• Focus on fast/automatic and manual measures but no/few

references to adequacy procedures • art. 21 refers to slow adequacy measures in DA/ID

• art 11.5 “SDP contains at least following actions …”)

• Reference to load shedding (plan) without concrete description

of it

• Detailed/strong (RT) reporting obligations

Restoration Plan

Idem SDP regarding level of detail & requirements

Plan de reconstitution (art 314-15)

• CREG is consulted

• TSO can mobilise capable units (MW/Mvar)

or (dis) connect Gus for system integrity

Ministerial Decree

Not included in

NC E&R

Proposal 1: keep articles 312-316

• Maintain role of Minister for load shedding

• Maintain priority to some elements (hospitals, call centers, ancillaries) but don’t make link with HP SGU

• Align (wording, public consultation) and refer to NC E&R for technical actions

pénurie ph. soudain


When to activate System Defence Plan: FGC provides reasons and situations while NC refers to operational parameters

NC E&R

FGC – royal decree

Proposal 2:

Add that SDP can be started as foreseen by art 13 of EU NC E&R but also/or in particular in case of situations

such as described in art 303 of FGC.

• “évènements soudains” + “pénurie” & “menace de pénurie”

• Art 303: TSO may launch SDP if:

• Risk of pénurie

• In case of emergency situation (wars…, phénomène soudain, pénurie)

• that were not forecastable in exploitation procedures

• that cannot be solved by normal tools/means

• Even if such situations called upon by others

• After evaluations of the state of the system

• SDP can be started if:

• frequency, voltage or power flow issues (13.2)

• emergency state ( operational limits exceeded) (13.2.a)

• If Operational security analysis requires some measures (as

foreseen in art 21 of E&R) (13.2.b )

Doesn’t explicitly cover all

adequacy measures (ex. W-1

procedure)

2.2. Proposal Federal Grid Code:

Metering


6th February 2018

The federal technical regulation (FGC) provides broad definitions:

• “Mesure: l’enregistrement, à un instant donné, d’une valeur physique par un équipement

de mesure

• Equipement de mesure: tout équipement pour effectuer des comptages et/ou des

mesures afin de permettre au gestionnaire de réseau de remplir ses missions tels que

compteurs, appareils de mesure, transformateurs de mesure ou équipement de

télécommunication y afférents

• Donnée de mesure: donnée obtenue par comptage ou mesure au moyen d’un

équipement de mesure

• Comptage: l’enregistrement par un équipement de mesure, par période de temps, de la

quantité d’énergie active ou réactive injectée ou prélevée sur le réseau “

The metering and measurement (“comptages et mesures”) are covered by the title V

Metering (and measurement) in the federal technical

regulation


Technical expert’ point of view :

« • Le comptage (« metering » in English) permet la mesure de l’énergie dont l’unité pour

la partie active est [kWh].

On utilise les données de comptage à diverses fins : la facturation de l’accès, mais

également les contrôles d’activation/disponibilité des services auxiliaires, le calcul des

volumes de déséquilibre, l’établissement des vecteurs de charge/production dans le cadre

des études de développement de réseau, etc.

• Les mesures (« measurement » in English), si elle concerne la puissance active, ont

l’unité [kW]. Il existe bien d’autres mesures sur le réseau : courant [A], tension [V],

puissance réactive [kVAr], fréquence [Hz], ... Utilisées à des fins opérationnelles

(protection, contrôle-commande, dips recording etc…) mais également (à titre d’exception)

être utilisées dans le cadre de la facturation, notamment dans le cas de données de

comptage manquantes ou erronées. »

Technical experts’ point of view


• No separate chapter on metering and/or measurements in the NC’s

• However, requirements, protection schemes, parameter settings defined in the NC’s or

to be defined by the TSO (in cooperation with grid user) or agreed with grid user on

basis of the NC’s

• Conclusion: Even if we take into account the broader definition of measurements, all

articles were already covered by the technical requirements -> the FGC does not need

to be modified in order to comply with the NC. We have clarified in the text that it is “in

accordance with the applicable legislation” (including the NC’s) for the sake of clarity.

Metering and measurements in the NC’s


Opportunity to modify the FGC in order to reflect current practices:

• Narrow the scope of the definition of “équipement de mesure”: “tout équipement pour

effectuer des comptages et/ou des mesures pour permettre au GRT de remplir ses

missions” -> “tout équipement pour effectuer des comptages et/ou des mesures tels que

compteurs, appareils dont la fonction principale consiste à mesurer, transformateurs de

mesure ou équipements de télécommunication y afférents »

• Clarify the location of the measurement devices: make distinction between measurement

devices located on the connection point/those located behind the connection point and

those used in order to supply ancillary services/ those used for the access (head meter)

• Clarify the title of ownership of the measurement devices, the technical regulations to be

complied with

• Clarify the regime in case of seal’s breach, significant error

• Transition provision

• Unsignificant modifications on the form

Wish list

16

2.3. Proposal Federal Grid Code:

Definitions


Thierry D’hoore

6th February 2018

Concrete methodology followed:

1. Verification of all defintions

2. Decide what to do with existing definitions and non defined terms in FTR (also

similar terms):

Most of NC defined terms are self-sufficient => removal conflicting definitions,

replacement of terms, alignment

A lot of the NC defined terms are new => no need to repeat definition, use new wording

Sometimes need of alignment with other definitions (e.g. in E-law) which are not

necessarily conflicting

Reminder methodology

18

Result: amendments to art 1

• Insertion of ‘legislation applicable’: includes rules, methodologies, guidelines, standards

and principles

• ‘Gestionnaire de réseau de transport’=> reference to E-law, splitting up in relevant TSO

and relevant SO

• Insertion of ‘code de réseau européen’ => reference to complete title and acronyme

• ‘charge’ => reference to art 41 §3 FGC

• Insertion of ‘réseau fermé industriel’ and ‘réseau fermé de distribution’ by ref to federal

and regional legislation (exc. Bxl)

• ‘puissance de charge’ removed

• Insertion of ‘réseau fermé industriel’ and ‘réseau fermé de distribution’

• ‘puissance active’ and ‘puissance réactive’ removed (redundant with RFG)

Art. 1 FGC

19

• ‘Pnom’ to be removed: see Pmax in RFG

• ‘système électrique’ linked to control area

• ‘composant du système électrique’ : no confusion with transmission system element (def

30° SOGL) nor relevant grid element (def 85° SOGL)

• Insertion ‘point d’interconnexion’

• ‘utilisateur du réseau’: ref to capacity of GU: PGFO, DFO, LTSO, DSO, HVDC system O,

DC PPM O, SPMO, in as far as these installations and systems are connected to TS

(tbc)

• ‘raccordement’: definition maintained, but insertion of specification as to LTS and public

DS: ‘secondary of TFO’

• ‘point de raccordement’: scope: PGM, DF, LTS, DS, HVDC system, DC PPM, SPM;

insertion of specific characteristics of BE connection: connection behind connection

point; for DSO/LTSO: interconnection point; details, including on connection, in

connection agreement

Art. 1 FGC

20

• ‘contrat de raccordement’ removed for redundant with ‘convention de raccordement’

RFG;

• Terms related to ‘responsable d’accès’ => ‘responsable d’équilibre’ (BRP)

• ‘contrat d’accès’ : exclusion of GU that is public SO / HVDC system owner

• ‘point d’accès: inclusive term: injection/offtake from PGM, DF, SPM, CDS connected to

transmission system

• ‘unité de production’ removed: redundant with ‘unité de producion d’électricité’/PGM in

RFG

• ‘parc non-synchrone de stockage’ (SPM): new concept (not network code related)

• ‘suivi du prélèvement’ removed: will be described in mission of BRP

• ‘équipement de mesure’ : definition limited to settlement

• ‘directive 96/92’ replaced by ‘directive 2009/72’

Art. 1 FGC

21

• Insertion of SPM related definitions:

• ‘Etat de chargement (SOC)’ :the measure of the amount of the available capacity

expressed in percentage points (0% = empty; 100% = full).

• ‘Taux de rampe de rechargement maximal’ (Rch): the maximum ramping that the

SPM is capable of achieving during charging expressed in MW/minute.

• ‘Taux de rampe de déchargement maximal’ (Rdis) the maximum ramping that the

SPM is capable of achieving during discharging expressed in MW/minute

• New/existing: application also on other installations out of scope of NC (SPM)

Art. 1 FGC

22

Package approach:

thresholds ABCD, derogations and

real-time information exchange


Proposed class derogation 1

• Type D PGM having a 0.8𝑘𝑊 ≤ 𝑃𝑀𝐴𝑋𝐶𝑎𝑝𝑎𝑐𝑖𝑡𝑦

< 0.25 𝑀𝑊 will follow the same requirements as type A PGM

• Type D PGM having a 0.25 𝑀𝑊 ≤ 𝑃𝑀𝐴𝑋𝐶𝑎𝑝𝑎𝑐𝑖𝑡𝑦

< 25𝑀𝑊 will follow the same requirements as type B PGM

Proposed class derogation 2

For PGM with 250𝑘𝑊 ≤ 𝑃𝑀𝐴𝑋𝐶𝑎𝑝𝑎𝑐𝑖𝑡𝑦

< 1𝑀𝑊, a derogation will be requested for the following ‘robustness’ requirements:

• 14(3) a&b - Fault Ride Through (FRT).

• 17(3) - Providing post-fault active power recovery (SPGM)

• 20(2) b&c. - Providing fast fault current (PPM)

• 20(3) a&b. - Providing post-fault active power recovery (PPM)

Packaged approach

Classification of derogation options


Individual derogation (for a unit…) Class derogation (for all units…)

Voltage level > 70kV ≤70kV > 70kV ≤70kV

Connection Elia grid Within

CDS

Elia Grid DSO grid Within

CDS

Elia CDSO Elia (C/)DSO

NC

requirements

(**)

Relevant

SO

indiv. unit

Elia

CREG

Indiv. unit

CDSO

CREG

Indiv. unit

Elia

VREG

CWaPE

Brugel

Indiv. unit

DSO (*)

VREG

CWaPE

Brugel

Indiv. unit

CDSO (*)

VREG

CWaPE

Brugel

Elia

N/A

CREG

CDSO

Elia

CREG

Elia

N/A

VREG

CWaPE

Brugel

(C/)DSO

Elia

VREG

CWaPE

Brugel

Relevant

TSO

Indiv. unit

Elia

CREG

Indiv. unit

Elia

CREG

Indiv. unit

Elia

VREG

CWaPE

Brugel

Indiv. unit

Elia

VREG

CWaPE

Brugel

Indiv. unit

Elia

VREG

CWaPE

Brugel

Elia

N/A

CREG

////// Elia

N/A

VREG

CWaPE

Brugel

/////

Art. 62 of NC RfG

Art. 52 of NC DCC

Art. 79 of NC HVDC

Art. 63 of NC RfG

Art. 53 of NC DCC

Art. 80 of NC HVDC

Green = requested by

Blue = assessed by

Red = granted by

• Individual derogation: assessment by relevant system operator in coordination with the relevant TSO and any

affected adjacent DSO or DSOs

(*) if the derogation for RfG requirements concerns a type C or D PGM connected to a (closed) distribution system, the relevant SO’s assessment must be

accompanied by an assessment of the request for derogation by the relevant TSO. (art. 62(5) RfG)

(**) the Connection Network Codes consist of exhaustive and non-exhaustive requirements. These requirements are to be determined by the relevant SO

or relevant TSO.

Derogations are “granted by” relevant regulating authority based on known competencies.

However, as mentioned in the derogations criteria, defined by all regulators, each derogation request should be sent

(via the relevant SO) to CREG and relevant regional regulator (if the latter is applicable)

25

Classification of derogation options


Class derogation (for all units…)

Voltage level > 70kV ≤70kV

Connection Elia CDSO Elia (C/)DSO

NC

requirements* Relevant

SO

Elia

N/A

CREG

CDSO

Elia

CREG

Elia

N/A

VREG

CWaPE

Brugel

(C/)DSO

Elia

VREG

CWaPE

Brugel

Relevant

TSO

Elia

N/A

CREG

////// Elia

N/A

VREG

CWaPE

Brugel

/////

Green = requested by

Blue = assessed by

Red = granted by

Derogation 1: Type A or B requirements

for units <25 MW installed ≥ 110 kV

(usually considered as type D)

*Based on ENTSO-E IGD document: ‘Parameters of Non-exhaustive requirements’:

https://www.entsoe.eu/Documents/Network%20codes%20documents/NC%20RfG/161116_IGD_General%20guidance%20on%20pa

rameters_for%20publication.pdf

Non-exhaustive req.: Defined by

Relevant TSO

Non-Exhaustive req.: Defined by

Relevant SO, in coordination with TSO

Derogation 2: Type A requirements for units

250kW – 1 MW (usually considered type B) for

some robustness topics:

• 14(3)a&b - Fault Ride Through (FRT).

• 17(3) - Providing post-fault active power

recovery (SPGM)

• 20(3). - Providing post-fault active power

recovery (PPM)

• 20(2)b&c. - Providing fast fault current (PPM)

26

RfG shall apply 3 years after eif of RfG NC 17/5/2016 + 3y = 17/5/2019

Regulatory authority shall adopt a decision concerning any request for a derogation within six months from the day after it

receives the request. 17/11/2018 + 6m = 17/5/2019

Art 61,3 : 3.The regulatory authority may decide that power-generating modules for which a request for a derogation has

been filed pursuant to Articles 62 or 63 do not need to comply with the requirements of this Regulation from which a

derogation has been sought from the day of filing the request until the regulatory authority's decision is issued.

https://www.entsoe.eu/Documents/Network codes documents/NC RfG/161116_IGD_General guidance on parameters_for publication.pdf



Proposal (aligned between Elia and the DSOs)

New units are required to provide real-time data

Existing PGM type B units that have the technical capability to deliver RT data

should deliver these RT data

Existing PGM type B units that do NOT have the technical capability to deliver

RT data are not required to deliver these RT data no retro-active investment

required

Interpretation of real-time:

“For data related to automatic load-frequency control processes & flexible generation, it

shall not be longer than 10 s. For other purpose, it shall be as fast as possible and in any

case not longer than one minute.

Telecontrol capability is embedded in interface box that is part of 1st connection field

No one-off investment cost but a recurring yearly cost

If no interface box is available, ELIA will install this.

Type B Real-time communication requirements


A minimum list of signals to be exchanges is defined in the general requirements for

TSO-connected units

Depending on the technology and location in the network, additional signals may be

required by the TSO to be exchanged. Examples (not exhaustive)

o Wind park – measured wind speed at nacelle height to allow wind forecast improvement,

topology of the internal network (reactive compensators,...)

o Pumping station – Measure of the water level/energy available

Exhaustive list is to be defined during connection process

Information exchange - Type B, C and D [ Art 14.5d]


Presented in WS 3 on 18/12

Many thanks for your attention!

ELIA SYSTEM OPERATOR

Boulevard de l'Empereur 20

1000 Brussels

+32 2 546 70 11

info@ elia.be

www.elia.be

An Elia Group company

4th Stakeholder Workshop Federal Grid Code and General .../media/files/Elia/users-group/WG Belgian...

Documents

Transcript of 4th Stakeholder Workshop Federal Grid Code and General .../media/files/Elia/users-group/WG Belgian...