Info session Users Group 10 th September 2019 Contents 1. - - PowerPoint PPT Presentation

info session
SMART_READER_LITE
LIVE PREVIEW

Info session Users Group 10 th September 2019 Contents 1. - - PowerPoint PPT Presentation

Info session Users Group 10 th September 2019 Contents 1. Introduction 2. Balancing 3. Generalities 4. Connection 2 1. Introduction Objective of this presentation 17/05/2018 29/04/2019 Elias submission of Federal Trajectory


slide-1
SLIDE 1

Info session – Users’ Group

10th September 2019

slide-2
SLIDE 2
  • 1. Introduction
  • 2. Balancing
  • 3. Generalities
  • 4. Connection

Contents

2

slide-3
SLIDE 3
  • 1. Introduction
slide-4
SLIDE 4

Objective of this presentation

17/05/2018 Elia’s submission of Federal Grid Code proposal 29/04/2019 Publication of new Federal Grid code During this trajectory, Elia provided ad hoc support to the FPS, involving relevant experts Trajectory managed by FPS Economy Objective Inform the Users’ Group about the major changes in the Federal Grid Code, in order to better identify impacts for each user

slide-5
SLIDE 5

5

FGC overall structure

FGC 22/04/2019

Titre Ier Généralités Titre II Données de planification du réseau Titre III Raccordement au réseau Titre IV Accès au réseau Titre V Comptages et mesures Titre VI Modalités spécifiques entre le gestionnaire du réseau de transport et les gestionnaires de réseau de distribution ou de transport local de la zone de réglage Titre VII Enregistrement des données Titre VIII Dispositions finales

FGC 19/12/2002

Partie 1re Généralités. Partie 2. Données de planification du réseau de transport. Partie 3. Raccordement. Partie 4. Accès au réseau de transport d’un utilisateur du réseau de transport. Partie 5. Equilibre. Partie 6. Conduite du réseau de transport. Partie 7. Comptages et mesures. Partie 8. Modalités spécifiques entre le gestionnaire de réseau de transport et les gestionnaires de réseau public de distribution. Partie 9. Règles applicables aux gestionnaires des CDS, raccordés au réseau de transport et à leurs relations avec le gestionnaire de réseau de transport. Partie 10. Enregistrement des données. Partie 11. Dispositions finales

slide-6
SLIDE 6
  • 2. Balancing
slide-7
SLIDE 7

Structure and Roles

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

Part 4 - Access

Alignment with reality:

  • Role of ACH
  • ACH contract
  • New access point in ACH contract

+ access to the Grid

  • Drop-off procedure

Part 5 - Balancing

  • Impacted mainly by EBGL and

CACM/FCA

  • Cleaned up to avoid overlaps with

NCs  articles relative to cross- border capacity allocation are deleted

  • Clarification/separation of different

Roles (BRP, ACH, BSP…)

Part 6 - Grid operation

  • Impacted by SOGL & E&R
  • In line with Icaros’ future Vision
  • + transitory dispositions
slide-8
SLIDE 8

Theme: Access to the Grid

8

Elia’s proposal (17/5/2018)

  • Split of ACH and BRP Roles
  • Split up/clarification of
  • Procedure to become ACH (and sign an ACH contract)
  • Procedure/conditions to request access to the grid and add an access point to an ACH contract
  • Description of elements included in ACH contract (including reference to Flexible Access)
  • Terminology alignment with tariffs: “Subscription” replaced by “Power Put At Disposal”
  • Deletion of “old” articles relative to free reactive cone and back-up connection
  • Elia will propose a Drop-off Procedure* in ACH contract within 1 year after the EiF of the FGC

Modifications in published FGC

  • Addition of Drop-off procedure

Related articles/sections: Part 5, Book 1 to 5 (art. 199 222)

New New New

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC

New New New New

slide-9
SLIDE 9

Theme: Balancing responsibilities

Elia’s proposal (17/5/2018)

  • Split of roles: BRP / CIPU owner / BSP
  • No content change in BRP responsibilities but some aspects have been clarified / aligned to practice:
  • Description of BRP responsibility :

BRP foresees and puts in place all reasonable means to be balanced + reactive balancing + precisions for offshore

  • TSO activates Balancing means according to a merit order fixed in Balancing Rules
  • TSO submits Balancing Rules to CREG after public consultation
  • Overview of all BRP tasks/responsibilities (available 24h; signing CIPU* …)
  • Possibility for pooling between 2 BRPs
  • Grid losses are compensated by BRPs
  • Possible schemes with multiple BRPs exhaustively described per access point (NIER/NOER, GIER/GOER…)
  • BRP Designation by ACH (+ duration, procedure in case there is no BRP (BRP  ACH  GU) …)
  • How nominations are made & obligation to provide a balanced program in DA & possibility for TSO to reject/suspend nominations…
  • Procedure to become BRP (Registry of BRPs, T&C BRP + BRP Contract conditions, timings, documents and guarantees to provide…) (has been aligned with current practice)

Modifications in published FGC

  • Text has been cleaned up to avoid overlap for some obligations with content of T&C BRP which is under CREG’s competency according to EBGL

 In practice, balancing responsibility and specifications on nominations have been deleted

New Art 199 New Art 200 New Art 201 New Art 202-203 New Art 204-205 New Art 206-209 New New New New Art 214-222 New Art 210-213 DELETED DELETED Details DELETED DELETED New

Related articles/sections: Part 5, Book 1 to 5 (art. 199 222)

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC

New New New

+ subject to T&C BRP

slide-10
SLIDE 10

Theme: Balancing Ancillary Services

10

Elia’s proposal (17/5/2018)

  • Text was simplified and cleaned up compared to 2002 version of FGC, as most elements are fixed by the EBGL or SOGL
  • E.g.: EBGL states that the provision of balancing services follows market rules (tender…)
  • SOGL describes the characteristics of FCR, aFRR, mFRR….
  • New structure:
  • Ancillary services split into: 1) Balancing A.S. (FCR, aFRR, mFRR ) 2) other A.S (Mvar, RSP,

) 3) eventual future SA developed in accordance with NCs/law

  • TSO submits T&C BSP to CREG in accordance with EBGL (art. 4&6); BSP signs a BSP contract where he commits to respect T&Cs
  • Obligation to bid up/down available power for all PGMs & storage ≥ 25 MW
  • Balancing Volume dimensioning
  • FCR volume to be reserved is fixed at EU level
  • TSO submits to the CREG methodology to identify needs and “optimal needs  means” conform EBGL dispositions
  • If reservation period ≥ 1 year, results have to be submitted as well.
  • BSP obligation to bid at least the reserved volume: BSP puts everything in place to respect this obligation (e.g. via secondary market…)
  • If TSO anticipates an issue (e.g.: because BSPs didn’t respect their obligation), he launches fallback procedures (“in LFC BOA”)

Modifications in published FGC

  • More details regarding the elements that have to be submitted to the CREG for approval

New Art 223 New Art 224-225 New Art 226 New Art 228-229 New Art 231 New Art 232 New New New

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC

New New

Related articles/sections: Part 5, Book 6; (art. 223 232)

New

Otherwise results have to be notified DSP

slide-11
SLIDE 11
  • Text was reviewed to be in line with SOGL and with future vision of Mvar, BS and Icaros
  • “Other AS” = Mvar, RSP,

& Congestion Management

  • New structure:

1. Mvar

  • TSO submits T&Cs VSP where to CREg where compensation modalities are based on financial guidelines of competent authority
  • Mandatory Participation of units capable to regulate Mvar; voluntary for other assets if technically capable
  • Modalities for participation for GUs in DSO/CDS grid and coordination with DSO/CDSO are defined in T&C VSP
  • Participation of those GUs is conditioned in any case to the agreement of DSO/CDSO and to the respect of their technical/operational motivated limitations

2. RSP

  • TSO submits T&C RSP to the CREG for approval
  • No obligation to participate (open to TSO GUs but also GUs of DSO/CDS)
  • Participation of those GUs is conditioned in any case to the agreement of DSO/CDSO and to the respect of their technical/operational motivated limitations

3. 4. Congestion management: TSO submits congestion rules to the CREG in accordance with art. 23 §2 36 of E-law

Theme: Other Ancillary Services

11

Elia’s proposal (17/5/2018) Modifications in published FGC

  • Mvar: the principle that financial principles are set by competent authority is deleted
  • RSP: the TSO will have to describe need, volume and choice of Restoration services in Restoration plan
  • Congestion management: content of congestion rules is deleted

New Art 234 New Art 234-237 New Art 238 New Art 241 DELETED New Art 237 New

  • Restoration plan contains methodology to determine the Restoration services & volume of each that are needed, taking into account islanding and back-up

generator resources

New Details DELETED

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

Related articles/sections: Part 6, Book 1; (art. 233 241)

New

DSP

New

3. DSP (+/- idem RSP)

slide-12
SLIDE 12

Theme: ICAROS

Elia’s proposal (17/5/2018)

  • Concerned assets:

1) PGM B,C,D connected to transport grid (directly or via CDS) 2) storage units B,C,D connected to transport grid (directly or via CDS) 3) demand facilities directly connected to transport grid 4) group of demand facilities within a CDS connected to transport grid

  • 1. OPA
  • Categories 1) 2) and 3) are obliged to provide Outage Planning
  • GU is OPA but he can appoint a 3rd party as OPA
  • Content of T&C OPA (cost-based remuneration; how GU appoints OPA, granularity and characteristics of data exchange…)
  • Obligation for OPA to notify TSO asap in case of total or partial FO
  • 2. SA
  • Mandatory for assets of type 1) and 2), exemption* for 3) & 4) (taking into account art. 52.2 (a) of SOGL). If a demand unit participates to SA, then TSO can ask schedules on this unit
  • GU is SA but he can appoint a 3rd party as SA
  • If asset covered by SA obligations already participates to balancing AS  SA = GU or BSP
  • Redispatching : SA of assets of type 1) and 2) put at Elia’s disposal up/downwards available margin for redispatching

voluntaty participation to redispatching for other assets (via SA and if applicable agreement of (C)DSO)

  • Content of T&C SA (ex. Cost-based remuneration, data characteristics, how GU appoints SA…)  framework for what the T&C will specify
  • Specific situations:
  • In case of schedule deviation, Elia may ask return to schedule and if no return, apply penalties
  • Obligation for SA to communicate to TSO any forced outage/production reduction (to come or that just happened) due to storm on offshore parks
  • After storm coordination with TSO is mandatory to re-inject
  • Interactions between all roles:
  • Schedules of SA, planning of OPA, nominations of BRP & bids of BSP must be coherent  Elia can reject, ask for adaptation or even adapt those in case of incoherency
  • Transitory modalities:
  • For units >= 25 MW, SA and OPA = BRP via CIPU contract till gradual transfer towards SA/OPA, according to modalities proposed by Elia (and approved by CREG)
  • First T&C OPA/SA submitted 6 months after EIF FGC
  • For all the rest,enters into force at the same date as art. 192 of SOGL (March ‘19)

New Art 242 New Art 246-249 New Art 25-252 New Art 253 New Art 247

New

New Art 243-245 DELETED DELETED New Art 377

12

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

Completely new text in line with the Icaros’ vision: it replaces old art. 267-297 of 2002 version of FGC

Related articles/sections: Part 6, Book 2 (art. 242 253)

slide-13
SLIDE 13

Theme: E&R

Elia’s proposal (17/5/2018)

  • Important principles of 2002/2015 have been kept (ministerial decree for plan de délestage, Mvar/Mw actions, clients prioritaires…)
  • But the new FGC has been cleaned up to avoid overlaps with E&R Network Code

Conduite du Réseau : no change compared to 2002

  • GU has to ask TSO before proceeding to maneuvers that have an impact on the grid security
  • Real-time data exchange between GU & TSO (Position of important elements such as circuit breakers MW, Mvar to/from grid…) as defined in connection contract
  • In case of abnormal functioning that can impact grid security, the GU informs TSO (and the opposite). Measures launched by TSO to avoid propagation are priority

BOOK 4: Defense & Restoration Plan:

  • TSO proposes, CREG provides advice and Minister approves elements of NC E&R art. 4.2 c, d, g (list of SGUs + measures; HP SGUs + disconnection/reconnection; test plan)
  • Defense plan
  • TSO submits defense plan to Minister after concertation of CREG and FPS Economy ; Minister approves it after CREG’s advice & in coordination with Minister of Economy
  • Defense plan describes actions MW and Mvar to be taken by all existing units ≥ 25 MW
  • TSO is allowed to cut off/modify connections to the grid, connections with other grids (DSO) in the control area and inter-connections + to suspend market activities
  • Defense plan is included in all contracts
  • TSO proposes, CREG advices and Minister fixes a “plan de délestage” obliging TSO to cut-off connections, reduce consumption of some GUs and restrict consumption for

certain purposes

  • TSO cooperates with DSOs to execute this plan and to reset the connections with priority
  • Restoration plan
  • TSO submits Restoration plan to Minister after concertation of CREG and FPS Economy ; Minister approves after CREG’s advice & in coordination with Minister of Economy
  • Restoration plan describes MW and Mvar actions to be taken by all existing units ≥ 25 MW
  • Defense plan is included in all contracts
  • Restoration plan contains a methodology to determine the need of Restoration services, the choice of services & volume of each, and this taking into account islanding and

back-up generator resources

  • TSO can do tests of Defense and Restoration Plan at own costs

New Art 254-256 New Art 259-263 New Art 262 New Art 263 New Art 259

13

New Art 261 Reminder Art 237

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED New

Related articles/sections: Part 6, Book 3 & 4; (art. 254 263)

slide-14
SLIDE 14
  • 3. Generalities
slide-15
SLIDE 15

Generalities: approval of regulated contracts

Theme Ref. FGC 19/12/2002 Elia's proposal 17/5/2018 FGC 22/04/2019 approval of regulated contracts Art 4 Art 6 list of contracts (include also T&C BSP, OPA, SA, info exchange) idem; specification legal basis for power to approve; SOK added Other evaluation criteria for approval of T&C : limited to reliability, efficiency and safety of the grid deleted 1 month 60 days for approval a reasonable time / provision on making the access right dependent on the compliance with this FGC, conclusion of the necessary contracts deleted / Art 11: confidentiality article completed to cope also with subcontracting issues deleted (for lack of legal basis: royal decree consulted in council of ministers) Theme Ref. FGC 19/12/2002 Elia's proposal 17/5/2018 FGC 22/04/2019 formalities, derogations and approval process Art 16 §2 insertion of specific provision on formal exchanges with CREG art 21 / derogation disposition limited to question where request must be filed: CREG (art 23) involvement of FOD which is consulted (and has 3 months for that) / Elia sends results of public consultation for requests for approval of regulated contracts to FOD, which must react within 5 working days (when MS has the right to be consulted or when foreseen by FCA or CACM) CREG sends these results to FOD, which must react within 15 calendar days (but has 5 days to confirm willingness to react)

DELETED New New DELETED New New New New

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

slide-16
SLIDE 16

Generalities: emergency

Theme Ref. FGC 19/12/2002 Elia's proposal 17/5/2018 FGC 22/04/2019 art 12 art 19 onwards definition of emergency situation (based on regional GC, without prejudice to NC) (art 13) definition of emergency situation deleted; focus on description of grid states, monitored by Elia / definition of force majeure (CACM based)(art 14) definition of force majeure deleted art 14 description of suspension

  • f obligations and its

consequences, without prejudice to E&R suspension and restoration of activities (mainly references to E&R)

DELETED DELETED

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

slide-17
SLIDE 17
  • 4. Connection
slide-18
SLIDE 18

Technical Requirements for Connection

18

Elia’s proposal (17/5/2018)

  • Mention of the role of relevant TSO to fix technical requirements up to Type A for the entire control zone
  • Individual derogations’ process for specific technical requirements or in specific situation (islanding, stability issue, RES & WKK)
  • Listing all technical requirements for new installations

Modifications in published FGC

  • No mention of the role of relevant TSO to fix technical requirements up to Type A for the entire control zone: No legal basis for Elia, as RTSO, to

impose technical requirements on all grid users in the control area (incl. in a CDS). The technical requirements are limited to installations connected to transmission grid (≥ 110kV)

  • Clarification of the localization of the connection point & of the interface point
  • Derogations foreseen in Art 71 § 3-6: strictly limited to CNCs cases: less large criteria / other procedures for granting derogations than in the

Elia’s proposal

  • Minor modifications on the new technical requirements imposed to the new grid users (generation, demand and distribution grids) compared with

FGC proposal of May 2018: migration of obligation to communicate the total capacity of reactive power to the TSO during the connection process (last al. of Art. 89 § 1 => new § 6 + idem Art 92 § 4 & Art 99 § 5) ; Art 90: one precision on “gabarit de creux de tension »

  • Existing technical requirements (Art. 36 to 69): no changes with former FGC

Comments

  • No technical requirements applicable to Types A or B connected at distribution or local transmission, in the BE control zone

=> Need to explicitly mention technical requirements in the regional grid codes, in application to the General Requirements as approved by the regional authorities

  • To review/write technical appendices to connection contracts listing the technical requirements applicable to Types A to D : used during the orientation and

details studies

  • New technical requirements for storage to develop
  • Several types of derogations : class derogation and individual possible derogations

Related articles/sections Part 3, Book 1 ; Title 1 (esp. art 35); Title 2 (art. 36 to 69 – similar to former FGC); Title 3 (70 to 135)

Old art 38 / New 35 Old art 74 / New 35 Old art 73-138 / New 70-135 Old art 38 / New 35 Old art 39 / New 36 §2 Old art 74 / New 71 §3-6 Old art 73-138 / New 70-135 Old art 39-72 / New 36-69

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED New DELETED New New New

slide-19
SLIDE 19

Substantial modernization

19

Comments

  • Specific rules for DSOs & INFRABEL
  • Elia works on drafting guidelines on criteria of substantial modernization, to be submitted for advise to CREG (art 162 § 1-2)
  • Compliance test protocol to be created
  • Partial compliance list to be created
  • CREG to fix “jurisprudence” on need for a new connection contract or revised contract

Elia’s proposal 17/5/2018 Published FGC 29/4/2019 Procédure: 1.Le TSO fixe et rend disponible sur son site internet la liste des éléments techniques essentiels à évaluer dans l’étude de modernisation. 2.Le TSO examine si la demande de raccordement concerne une modernisation substantielle des installations ou un remplacement d'équipements affectant les capacités techniques des installations 3.Si tel est le cas, l'étude de détail évalue le caractère substantiel de la modernisation ou du remplacement (volet modernisation) en évaluant certains critères:

  • tout changement de technologie ayant pour conséquence d’augmenter la production d’électricité

nominale et de passer vers le seuil supérieur B, C ou D

  • l’ampleur de l’augmentation de la production nominale
  • le renouvellement d’un ou plusieurs éléments techniques essentiels de l'installation (le placement

de pièces de rechange à l'identique n'est pas visé) 1.Conformité:

  • totale: si passage vers le seuil supérieur B, C ou D ou si l'augmentation de la production nominale

est >50%

  • partielle si l'augmentation de la production nominale est >20% et <50%

5.Le TSO notifie sans délai à la CREG l'étude de modernisation + proposition de conformité + modifications du contrat qui en découlent 6.La CREG évalue dans les 10 jours si la proposition est complète. Dans les 30 jours, la CREG approuve/rejette la proposition du TSO (caractère substantiel + conformité + modifications du contrat). Elle peut aussi revoir la proposition Procédure: 1.Le TSO élabore des lignes directrices et les notifie pour avis à la CREG, avec une copie pour avis à la DG Energie qui transmet son avis à la CREG et au TSO dans le mois 2.Durant l'étude de détail, le TSO examine si la modernisation est substantielle en appliquant les critères suivants:

  • tout changement de technologie ayant pour conséquence d’augmenter la production

d’électricité nominale et de passer vers le type supérieur C ou D

  • l’ampleur de l’augmentation de la production nominale
  • le renouvellement d’un ou plusieurs éléments techniques essentiels de l'installation (le

placement de pièces de rechange à l'identique n'est pas visé) 3.Si un nouveau contrat de raccordement est requis, le TSO notifie la CREG 4.La CREG décide si un nouveau contrat est requis ou une révision du contrat existant 5.L'étude de détail indique les résultats et, le cas échéant, la décision de la CREG

Related articles/sections Part 3, Book 1 ; Title 2 Art 159 – 161 – 162

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED DELETED DELETED New DELETED New DELETED

slide-20
SLIDE 20

Flexible Access

20

Elia’s proposal (17/5/2018) Modification in published FGC

Related articles/sections Part 3, Book 2 ; Titles 1, 2 Art 145, 160 § 2-3 Art 170

  • References of flexible access during the orientation and detailed studies
  • No definition of flexible access in art. 2 but new article with a new regime describing the procedure to apply in case of flexible access
  • Title I: definition (copy paste of TR VREG):
  • possible for all new units
  • TSO decides during connection study whether classic/flexible capacity
  • for definitive Flexible Access regulator must approve
  • Title III: References of flexible access during the orientation and detailed studies:
  • connection provisions
  • + same modalities for offshore chapter
  • Title IV: Possibility to use Flexible Access in case of congestion
  • Important note : FGC does not describe remuneration modalities  legal framework needed

Old art 1 Old art 148, 162 / New 145, 160 §2-3 New art 170 Old art 144 et al. Old art 255

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

New

New New

slide-21
SLIDE 21

Compliance verification & tests

21

Elia’s proposal (17/5/2018) Modification in published FGC Comments

New principle:

  • Tests and simulations performed by the owner of the installation. This task may be outsourced to a third party
  • In certain circumstances a certificate is allowed to prove conformity
  • TSO shall perform tests and simulations for compliance verification for security, fiability and efficacity of the grid

=> Process for compliance verification

When are tests and simulations necessary (mostly described in CNCs):

  • In case of commissionning of a new installation/unit (operational notification procedure)
  • In case of a new connection to the transmission system
  • In case of doubt (for example after an incident)
  • In case of extension/replacement/modernisation of an installation or unit
  • Tests - on demand simulations - recurrent confirmation asked

Related articles/sections Part 3, Book 2, Title 4 (Art. 172 - 179); Title 5 (Art. 180 – 186)

  • High-level description of the operational compliance notification procedure (EON, ION, FON) for connection of any type of installations

Reference to this general procedure for the storage installations

  • Description of the procedure for tests realisation by grid user
  • Rules related to tests and simulations for compliance verification for security, fiability and efficacity of the grid, to be perfomed by TSO
  • Major change on operational notification procedure (EON, ION, FON) : No description of the procedure for connection of

installations => text is now limited to the storage : CNCs considered as complete and of direct implementation of any other type

  • f installations
  • No changes in procedure for tests realisation by the grid user and compliance verification by the TSO
  • New rule on the TSO costs for compliance verification : reference to the electricity law

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED DELETED New New New New

slide-22
SLIDE 22

Closed Distribution System

22

Elia’s proposal (17/5/2018) Modifications in published FGC

Related articles/sections Part 9

  • Art. 339 - 353
  • Comprehensive set of rules for CDS, written in collaboration with CDSOs
  • Rules on relations between CDSO and TSO, connection of CDS user, access to CDS-grid, market participation of the CDS user and rules for BRPs in CDS,

energy allocation between BRPs in CDS, data exchanges between TSO and CDSO, metering and settlement in CDS Suppression on any reference to rules regarding

  • connection of CDS user & access to CDS-grid : exclusive competence of regional level
  • data exchanges between TSO and CDSO : exhaustive description in CNCs – no need to add any rule or precision

Legend: introduced by Elia in its proposal in 2018 modified by SPF in new FGC deleted by SPF in new FGC

New New DELETED

New

DELETED

slide-23
SLIDE 23

Thank you!

slide-24
SLIDE 24

General requirements - Status

10th September 2019

slide-25
SLIDE 25

Theme New / Existing

25

Related articles/sections Art 35

Federal level

The regional governments first needed to give the regional regulators the competency to publish a decision.

Regional level

  • art. 35 §7-8 of new FGC:
  • The contract for buying the main component must be signed before 27/4/2019 for a unit to be considered as existing
  • Then, Elia is notified within 3 months and a request for recognition is introduced at the CREG within 6 months
  • CWaPE decision:

Une unité est considérée comme existante “si le propriétaire de cette unité a conclu un contrat définitif et contraignant pour l’achat du composant principal de production au plus tard deux mois après la date de publication sur le site internet de la CWaPE de la décision d’approbation des exigences d’application générale visées à l’article 7 du Code de réseau RfG [ou DCC]. »

  • VREG decision:

“Een elektriciteitsproductie-eenheid wordt als bestaand in de zin van artikel 4.2 van de netcode RfG beschouwd, als ten laatste 2 maanden na de datum van publicatie op de website van de VREG van de beslissing van de goedkeuring van de algemene toepassingseisen zoals bedoeld in artikel 7 van de netcode RfG:

  • a. aangesloten is op het elektriciteitsdistributienet, het plaatselijk

vervoernet van elektriciteit of een gesloten distributienet, of

  • b. de eigenaar van de elektriciteitsproductie-installatie een

definitief en bindend contract heeft gesloten voor de aankoop van het belangrijkste onderdeel van de productieinstallatie, en dit ten laatste 3 maanden na de datum van publicatie op de website van de VREG van de hogervermelde beslissing, gemeld heeft aan de bevoegde netbeheerder (of beheerder van het gesloten distributienet) en aan de transmissienetbeheerder.”

  • BRUGEL decision:

« Les installations de production d’électricité ainsi que les installations de consommation visées respectivement par le règlement (UE) 2016/631 et le règlement (UE) 2016/1833 seront considérées comme « nouvelles » au sens des codes établis par ces règlements qu’après deux mois suivant la publication de l’approbation de BRUGEL des propositions d’exigences d’application générale soumises par les gestionnaires de réseau compétents selon les mêmes codes de réseau. »

slide-26
SLIDE 26
  • Legal / related to competences:

26

General Requirements – Main comments from regional regulators

Legal applicability Connection of production units Connection of demand units Transmission General Requirements Federal Grid Code General Requirements Federal Grid Code Local Transmission General Requirements General Requirements Distribution C10/11 General Requirements

  • Legal applicability and link between General Requirements and C10/11
  • On federal level: No approval decision
  • f General Requirements. All

connection requirements related to transmission will be completely integrated in FGC

  • On regional level: Approval of General

Requirements and C10/11 by regional regulators

  • As C10/11 is more exhaustive than Gen. Req. RfG, DSOs will formally submit their non-exhaustive requirements

in C10/11 to regional regulators

  • Clarity of applicable requirements for grid users will be a priority
  • Requirements for /within CDS
  • TSO/DSO have not the right to submit requirements for assets within CDS  All references to CDS will be removed

from the General Requirements

  • However, as a CDSO is a Grid User of the transmission/local transmission/distribution grid, Elia’s or DSOs’

connection requirements will apply at the interconnection point between the CDS and the transmission/local transmission/distribution grid and CDSO ensures (via his own requirements for his CDS-GU’s) that the CDS meets its

  • bligations
  • Regional regulators are considering introducing in their future Grid Codes that if a CDSO does not submit his Gen.
  • Req. the Gen. Req. /C10/11 are applicable by default.
slide-27
SLIDE 27
  • Requests for clarification/need to be more specific:
  • mandatory provision to RSO of technical capabilities when they exceed min. requirement

 Clarify that those capabilities should be put at disposal of TSO/DSO if no technical/economic impact (already in RfG/DCC)

  • be more specific regarding the future documents where some requirements will be further described
  • Wording / translations / language abuses
  • Content : only two

General Requirements – Main comments from regional regulators

27

Cogen Vlaanderen contacted concerned authorities requesting for modifications in FGC and Gen. Req.:

  • 1. Modification of standard

temperature (to 0°C) to assess the admissible maximum power reduction with falling frequency Modified in FGC Proposed as modification in Gen. Req. RfG and C10/11

  • 2. Modification of response time for gas turbines in case of increasing or

decreasing frequency

  • A pragmatic approach was proposed :
  • Current FGC requirements (which are compliant with Implementation Guidance

Document) are maintained as default requirements

  • For gas turbines and internal combustion engines that can’t apply the default

requirements, an alternative solution aligned with German standardization documents is offered Proposed as modification in regional Gen. Req. RfG and C10/11