Presentation of ENTSO-e Draft Connection Codespublications.elia.be/upload/UG_upload/4I7GVHN41W.pdf · 30/05/12 Final draft approval by ENTSO-e 25/10/12 Final draft approval by ENTSO-e

Presentation of ENTSO-e DraftConnection Codes

Requirements for Generators&Requirements for Distribution Network Companies and Demand Facilities

1

Jonathan Sprooten

February 21, 2012

Agenda• Framework and process of the NC on connection• Scope of the Network Codes

• Network Code Requirements for Generators• Categorization• Graded approach of the requirements and Examples of requirements• Compliance and notification procedure

• Network Code on Demand Connection• Scope of the DCC• Important New definitions• Examples of requirements• Compliance and notification procedure

223/02/2012

Network Codes: framework and process

Comitology (where appropriate)

EC In consultation with all stakeholders resulting in legally binding NC

Assessment of NC

ACER Recommendation of NC to EC

Develop NC (12 month period)

ENTSO-E In consultation with stakeholders according to FWGL

Request for draf ting NC

EC According to FWGL submitted by ACER

Develop FWGL (6 month period)

ACER In consultation with ENTSO-E, stakeholders, with input from Ad-HocExpert Group

Request for draf ting FWGL

EC On a topic identified in art.8 (6) of Regulation EC 714/2009

Development ofFWGL

Development ofNC

323/02/2012

Network Codes: framework and process

Requirements for generators Demand Connection CodeDec ’10 Framework Guidelines on Network Connections draft

Mar ’11 First public draft and informalpublic consultation

20/7/11 Framework Guidelines on Network Connections final version

29/7/11 Letter EC to start procedure Dec’11 Letter EC to start procedure

Nov/Dec ‘11 Informal communication withstakeholders

27/10/11 Second Draft completed 31/12/11 First Draft Completed

12/01/12 –26/01/12

Internal Consultation

13/11/11 Draft approval by ENTSO-e 13/03/12 Draft approval by ENTSO-e

24/01/12 –20/03/12

Start of Public Consultation April/May12

Start of Public Consultation

30/05/12 Final draft approval by ENTSO-e 25/10/12 Final draft approval by ENTSO-e

• Network Code should be applied within 3 years following its publication

423/02/2012




523/02/2012

Scope of the Network Codes:« cross-border » network issuesEC Regulation 714/2009 Article 8 (7) defines that “the network codes shall be developedfor cross-border network issues and market integration issues and shall be withoutprejudice to the Member States’ right to establish national network codes which donot affect cross-border trade”.The term “cross-border network issue” itself is not defined by this EC Regulation.

Targets of the EC 3rd legislative package for the internal electricity market, are:• 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

Choice of the Drafting Team (DT)All requirements that contribute to maintaining, preserving and restoring system securityin order to facilitate proper functioning of the internal electricity market shall be regardedas “cross-border network issues”.

623/02/2012

Scope of the Network Codes:Technical ability of the units / Operational requirements /Participation to paid-for services• Requirements = technical ability of the generating units

• with a long-term view towards system needs(no change required in the near future that could have been anticipated)

• = Connection Requirements

• Operational requirements given by the relevant Network Operator might differ, but theyneed to be within the range of the Network Code.

• Example: units must be able to withstand a df/dt of 2 Hz/s, but it is commonpractice in LV/MV Networks to request a ROCOF relay set to 0,5 Hz/s (anti-islanding protections)

• The participation to and remuneration for ancillary services are not in scope.• The financial incitation for low reactive energy of demand units is not in the scope.

• Is it beneficial for the final user to impose technical abilities for ancillary services orto let the market decide whether to invest or not?

• Position paper in preparation by the WG Ancillaries of the Market Committee, thishighlight some market failures

723/02/2012

What is a Significant Grid User?

ACER Framework Guideline on Electricity Grid Connection“The network code(s) developed according to these Framework Guidelines shall defineappropriate minimum standards and requirements applicable to all significant grid users.”“The minimum standards and requirements shall be defined for each type of significantgrid user and shall take into account the voltage level at the grid user’s connection point.The network code(s) shall specify the criteria and methodology for the definition ofsignificant grid users. These shall be based on a predefined set of parameters whichmeasure the degree of their impact on cross-border system performance via influence oncontrol area`s security of supply, including provision of ancillary services ("significancetest")…”

23/02/2012 8




923/02/2012

Network Code Requirements for Generators:Documentation & references• ENTSO-e Draft « Requirements for grid connection applicable to all Generators »

• 27/10/2011• Pilot code (Abbreviation = NC RfG)• Meant to become a EU Regulation• Contrarily to the RG CE Operation Handbook, there is no appendix with the

background for the establishment of the code

• Frequency Asked Questions• 23/11/2011• 25 FAQs

• Draft « Motivation and Approach »• 30/11/2011• Position paper

1023/02/2012

Categorization:Criteria for categorization (1)• By « technology »:

+ take into account specificities of either the primary source of energy and / or theconnection technology to make the best use of the inner capabilities without excludingany particular technology = equitable treatment of all generators

• primary source issue for access and paid-for ancillary services: out of scope• technology of the connection has a large influence on the capability

• DT: Synchronously connected or not synchronously connected(= through a power electronic interface)

• Asynchronous generators and DFIG are synchronously connected

• By size of the unit (MW or MVA thresholds ):+ investment in advanced technical abilities provides a better cost/benefit ratio for largerunits.+ for the system operator, there is also an impact of size on the system security.- the average size of units may change with the power generation mix

1123/02/2012

Categorization:Criteria for categorization (2)• By voltage level at the Connection Point (CP)

- Not ideal because the operator is entitled to impose a V-level according to the size ofthe unit. This might be based on short-circuit power (strength of the system) and theadmissible emission level (power quality).- how to handle small units installed by industrial load at high voltage ?- V-level specificities: earthing & protection philosophy, electrical distances &geographical impact of a disturbance very different across EU

• DT: differentiate units at VHV (≥ 110 kV)

1223/02/2012

Categorization:Choice of the DT• Type A : CP < 110 kV and Maximum Capacity is >= 400 W• Type B : CP < 110 kV and Maximum Capacity >= 1 MW (*)• Type C : CP < 110 kV and Maximum Capacity >= 50 MW (*)• Type D : CP >= 110 kV OR Maximum Capacity >= 75 MW (*)

(*) these power thresholds can be set lower but not higher by the TSO

13

General requirements for all types of generationunits

Synchronous

Requirements forSynchronouslyconnected units

Offshore

Requirements foroffshore

connected units

Power ParkModules

Requirements forNon -

synchronouslyconnected units

23/02/2012

Categorization:Choice of the DT• How to handle small units installed by industrial load at high voltage ?

• Massive derogation

• Why a specific category for offshore?• Definition: Offshore PPM = PPM having a Connection Point located offshore

• A PPM having a Connection Point located onshore falls in the onshorecategory all Belgian offshore wind

• Various configurations are considered (AC single CP, meshed AC, DC, hybrid,etc)

• Not all requirements apply to offshore and depends on the configuration

1423/02/2012




1523/02/2012

Graded Approach

Type D

Type C

Type B

Type A

Europe wide balancing services

Refined and controllable dynamic response

Automated response, operator control, information

Common failure mode for all plants (frequency)

• 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

23/02/2012 16

General RequirementsTitle Requirement type Type A Type B Type C Type DFREQUENCY RANGES Frequency stability X X X XLIMITED FREQUENCY SENSITIVE MODE (OVERFREQUENCY) Frequency stability X X X XRATE OF CHANGE OF FREQUENCY WITHSTAND CAPABILITY Frequency stability X X X XREMOTE SWITCH ON/OFF Frequency stability X XCONTROL SCHEMES AND SETTINGS System management X X XINFORMATION EXCHANGE System management X X XCAPABILITY OF RECONNECTION AFTER AN INCIDENTALDISCONNECTION DUE TO A NETWORK DISTURBANCE System restoration X X X

POWER/VOLTAGE QUALITY System management X XSYNCHRONISATION System management X XACTIVE POWER CONTROLLABILITY AND CONTROL RANGE Frequency stability X XDISCONNECTION DUE TO UNDERFREQUENCY Frequency stability X XFREQUENCY RESTORATION CONTROL Frequency stability X XFREQUENCY SENSITIVE MODE Frequency stability X XLIMITED FREQUENCY SENSITIVE MODE (UNDERFREQUENCY) Frequency stability X XMONITORING OF FREQUENCY RESPONSE Frequency stability X XLOSS OF STABILITY System management X XRATE OF CHANGE OF ACTIVE POWER System management X XSIMULATION MODELS System management X X

STEADY-STATE STABILITY Robustness ofGenerating Units X X

BLACK START System restoration X XCAPABILITY TO TAKE PART IN ISOLATED NETWORK OPERATION System restoration X XQUICK RE-SYNCHRONISATION System restoration X XRECONNECTION AFTER TRIPPING ONTO AUXILIARY SUPPLY System restoration X XSHORT CIRCUIT CONTRIBUTION Voltage stability X XHIGH/LOW VOLTAGE DISCONNECTION Voltage stability XVOLTAGE RANGES Voltage stability X…. …. … ….

23/02/2012 17

Specific Requirements for SynchronouslyConnected Units

Title Requirement type Type A Type B Type C Type D

POST FAULT ACTIVE POWER RECOVERY Robustness ofGenerating Units X X X

FAULT RIDE THROUGH CAPABILITY OF SYNCHRONOUSGENERATORS CONNECTED BELOW 110 kV

Robustness ofGenerating Units X X

REACTIVE POWER CAPABILITY (SIMPLE) Voltage stability XVOLTAGE CONTROL SYSTEM (SIMPLE) Voltage stability XCONSTANT OUTPUT AT TARGET ACTIVE POWER Frequency stability X XMAXIMUM POWER REDUCTION AT UNDERFREQUENCY Frequency stability X X

COORDINATION OF SPEED AND POWER CONTROL OFSYNCHRONOUS GENERATING UNITS System management X X

REACTIVE POWER CAPABILITY AT MAXIMUM ACTIVEPOWER Voltage stability X X

REACTIVE POWER CAPABILITY BELOW MAXIMUM ACTIVEPOWER Voltage stability X X

STEADY STATE VOLTAGE CONTROL Voltage stability X XTRANSIENT VOLTAGE CONTROL Voltage stability X XEXCITER SPECIFICATION Voltage stability XSTATOR CURRENT LIMITER Voltage stability XVOLTAGE CONTROL SYSTEM Voltage stability X

FAULT RIDE THROUGH CAPABILITY OF SYNCHRONOUSGENERATORS CONNECTED AT 110 kV OR ABOVE

Robustness ofGenerating Units X

POWER OSCILLATIONS DAMPING CONTROL Voltage stability XPOWER SYSTEM STABILIZER Voltage stability X

23/02/2012 18

Specific Requirements for Power ParkModules

Title Requirement type Type A Type B Type C Type DREACTIVE POWER CAPABILITY (SIMPLE) Voltage stability X X

POST FAULT ACTIVE POWER RECOVERY Robustness of GeneratingUnits X X X

REACTIVE CURRENT INJECTION Voltage stability X X XFAULT RIDE THROUGH CAPABILITY OF POWERPARK MODULES CONNECTED BELOW 110 kV

Robustness of GeneratingUnits X X

SYNTHETIC INERTIAL CAPABILITY Frequency stability X XPRIORITY TO ACTIVE OR REACTIVE POWERCONTRIBUTION Voltage stability X X

REACTIVE POWER CAPABILITY AT MAXIMUMACTIVE POWER Voltage stability X X

REACTIVE POWER CAPABILITY BELOWMAXIMUM ACTIVE POWER Voltage stability X X

REACTIVE POWER CONTROL MODES Voltage stability X XFAULT RIDE THROUGH CAPABILITY OF POWERPARK MODULES CONNECTED AT 110 kV ORABOVE

Robustness of GeneratingUnits X

23/02/2012 19




2023/02/2012

Structure of the Network Code

Generalprovisions

DefinitionsDefinitions

ScopeScope

Requirements

Generalrequirements

Generalrequirements

SynchronousGenerating

Units

SynchronousGenerating

Units

Power Parkmodules

Power Parkmodules

Offshore PowerPark modules

Offshore PowerPark modules

OperationalNotification

Procedure forConnection

New generatingunits

New generatingunits

Existinggenerating

units

Existinggenerating

units

Compliance

Compliancemonitoring

Compliancemonitoring

Compliancetesting

Compliancetesting

CompliancesimulationsCompliancesimulations

Derogations

RequestRequest

DecisionsDecisions

Final Provisions

Entry into forceand applicationof the Network

Code

Entry into forceand applicationof the Network

Code

23/02/2012 21

Interim operational notification

Final operational notification

Limited operational notification

- Itemized compliance statement- Detailed technical data- Manufacturer data & performance certificate- Simulation models

- Practical tests demonstrating compliance- Validation of simulation tests and studies

- Modification or loss of capacility- Equipment failure

Compliance & Operational notificationprocedure : New units

2223/02/2012

Compliance & Operational notificationprocedure: Derogations

For both new and existing units• Generator

• introduces request for derogation to the TSO (Incl. Detailed reasoning)• TSO

• can request an exemption from CBA to the National Regulator• provide the National Regulator with his assessment, possibly based on CBA

• National Regulator• informs the generator, TSO and ACER about the decision

International coordination• National Regulator

• keeps a register of derogations granted or rejected• Sends un update to ACER every 6 months

• ACER can emit an advise to National Regulators

23/02/2012 23




2423/02/2012

ENTSO-e Demand Connection Code:Documentation & references• ENTSO-e Draft « Demand Connection Code »

• 20/12/2011• Abbreviation = NC DCC• Meant to become a EU Regulation• Contrarily to the RG CE Operation Handbook, there is no appendix with the

background for the establishment of the code

• Drafting Team Working Draft « Demand Connection Code »• 07/02/2012

23/02/2012 25

Scope of DCC• Code Applicable for

• Some requirements for All (significant and non significant) Demand Facilities• Significant Demand Facilities• Some requirements for All All Distribution Networks• Transmission connected Distribution Networks

• Retroactive applications of requirements for Existing Demand Facilities/ orExisting Connected Distribution Networks1. TSO shall carry out a

• Quantitative cost-benefit analysis (socio-economic, internal market and cross-border trade benefits, integration of renewables)

• Proposal including an operational notification procedure and an appropriatetransition period for implementing the requirements.

• Public Consultation2. National Regulatory Authority takes decision

• Principle of superposition: In situations where generation and demand co‐exists• All demand requirements within this code will be evaluated on the basis that the

generation is not present.• The generation facility will have to comply with the requirements of the Network

Code Requirements for Generators

2623/02/2012




2723/02/2012

Some Important Definitions (1/2)

• Connection Point ‐ is the location at which- the Demand Facility is connected to a network- the Distribution Network is connected to a Transmission Network.

• Demand Unit ‐ a Demand Unit is an indivisible set of installations which canbe actively controlled by a Demand Facility Operator to moderate its electricalenergy demand. (…)

• Significant Demand Facility – Demand Facility which has the ability eithersingularly or when considered aggregated to impact on the cross‐bordersystem performance via influence on the control area’s security of supply. Forthe purposes of this network code this will be either a TransmissionConnected Demand Facility or a Demand Facility with Demand SideResponse, unless explicitly stated otherwise within the Network Code.

• Closed Distribution Network – A system (network) which distributeselectricity within a geographically confined industrial, commercial or sharedservices site and does not (…) supply household customers.

2823/02/2012

Some Important Definitions(2/2)

• Distribution Network – is an electrical system for the distribution of electricalpower from and to third party[s] connected to it, a transmission or anotherdistribution network, including Closed Distribution Networks.

• Distribution System Operator (DSO) ‐ An Regulated Distribution NetworkOperator (electricity) of Distribution Network assets.

• Transmission Network ‐ is an electrical Network for the Transmission ofelectrical power from and to third party[s] connected to it, including DemandFacilities, Distribution Networks or other Transmission Networks. This extent ofthis Network is defined at a national level.

• Demand Side Response (DSR) - Demand offered for the purposes of but notrestricted to providing Active or Reactive Power management, Voltage andfrequency regulation and System Reserve.

• Demand Aggregation – is a set of Demand Facilities which can be operated asa single facility for the purposes of offering one or more Demand Side Responseservices.

2923/02/2012




3023/02/2012

General Requirements

3123/02/2012

Title All

Dem

and

Faci

litie

s

Tem

pera

ture

Con

trolle

dD

eman

d Fa

cilit

y

Sig

nific

ant

Dem

and

Faci

lity

Sig

nific

ant

Dem

and

Faci

lity

abov

e 11

0kV

Clo

sed

Dis

tribu

tion

Net

wor

ks

All

Dis

tribu

tion

Net

wor

ks

Tran

smis

sion

Con

nect

edD

istri

butio

nN

etw

orks

Tran

smis

sion

Con

nect

edD

istri

butio

nN

etw

orks

abo

ve11

0kV

FREQUENCY RANGES X X X XVOLTAGE RANGES X XSHORT-CIRCUITREQUIREMENTS X XREACTIVE POWERREQUIREMENTS X XPROTECTION AND CONTROL X XLOW FREQUENCY DEMANDDISCONNECTION XDSR - ACTIVE POWERCONTROL (X) (X)DSR - REACTIVE POWERCONTROL (X) (X)DSR - TRANSMISSIONCONSTRAINT MANAGEMENT (X) (X)DSR - SYSTEM FREQUENCYCONTROL X (X) (X)POWER QUALITY X XSIMULATION MODELS X X

Example: Short-Circuit Requirements

3223/02/2012

• The Relevant Network Operator shall define the maximum value of short‐circuitCurrent that the Demand Facility and Distribution Network must be able tosupport.

• The Relevant TSO shall have the right to request information from the DSO,concerning the contribution in terms of short‐circuit current of Generation Unitsconnected to the Distribution Network.

Example: Reactive Power requirements(1/2)

3323/02/2012

• Is Defined in FWGL ACER Section 2.1

• Reactive power should be generated were needed : Quick CBA ofreactive power equipment on different voltage levels: More costeffective at lower voltage levels

Example: Reactive Power requirements(2/2)

3423/02/2012

• Defined in power (not energy) at the Connection Point Not present in Belgian RT/TR,

Cost penalty defined in reactive energy over 15min No maximum value for reactive power (or power factor)

For Significant Demand Facilities Without onsite generation 0.95 (ind)<Cos(phi)<1 With onsite generation 0.9 (ind)<Cos(phi)<0.9(cap)

For Transmission Connected Distribution Networks, (DSO and Closed DistributionSystems)

0.9 (ind)<Cos(phi)<0.9(cap) Capability to maintain 0MVAr exchange at nominal Voltage with a deadband of

5% of active power for a load exchange of no higher than 25% of the MaximumImport Capacity

TSO can request capability to maintain 0MVAr exchange at nominal Voltageaverage (within deadband of 5% of active power over the same period) for nolonger than 1h for a specified range of active power exchange

Example : Demand Disconnection/IslandMode for System Defense and DemandReconnection (1/2)

3523/02/2012

• With regard to Low Frequency Demand Disconnection devices:• For Distribution Network and Transmission connected Demand Facilities• Low Frequency (or alternatively if specified by the TSO, ROCOF) Disconnection of a percentage of

demand to be specified by the TSO

• Relays should monitor direction of active power flow

• With regard to Low Voltage Demand Disconnection devices (including OLTCblocking)

• Based on the TSO assessment

• Relays should monitor direction of active power flowµ

• Significant Demand Facilities and Transmission Connected Distribution Networks shall fulfill thefollowing requirement referring to reconnection of a Demand Facility or Transmission ConnectedDistribution Network:

Example : Disconnection/Island Mode(2/2)

3623/02/2012

Example : Demand ResponseRequirements (1/3)

3723/02/2012

• Framework Guidelines Grid Connection July 2011 Section 2.1.2The network code(s) shall set out necessary minimum standards and requirements to be followedwhen connecting a consumption unit to the grid, to enable demand response and/or participation ofconsumption units in other grid services, on a contractually-agreed basis.’

• On Voluntary basis• With regard to Demand Side Response Active Power Control and Reactive Power Control and

Transmission Constraint Management• For Demand Facilities and Closed Distribution Network Operator

• On Mandatory basis• With regard to Low Frequency Demand Response

• For temperature controlled devices (for example, fridges, freezers, heat pumps, immersion heaters)


3823/02/2012

• Demand Side Response Active Power Control, Reactive Power Control,Transmission Constraint Management

• TSO shall have the right to specify the network location, usage and/or scale

• One of the three methods:

• Modify demand usage ordered by command sent by NO• Modify demand usage with frequency and/or voltage control and pre‐alert signal sent by NO.

• For Voltage control, Disconnection/reconnection of static compensation facilities controlled byNO.

• The Demand Facility or Closed Distribution System shall be able to stay connected to the network dueto ROCOF up to 2Hz/s.

• Very fast Frequency Response - (i.e. Inertia/synthetic inertia) – if Any

• Demand Side Response System Frequency Control• For temperature controlled devices

• Device regulates between two sets points - stored energy between the points can be used to increaseor reduce these devices effective demand

• Deadband of frequency defined by TSO of the synchronous area


3923/02/2012

Freq

uenc

yTe

mpe

ratu

reTa

rget

Dem

and

Res

pons

e

Example: Simulation Models

4023/02/2012

• The models shall show the behavior of the Significant Demand Facilityand/or Transmission connected Distribution Network in both

• Steady‐state simulations

• Dynamic simulations (long term, short term, and electromagnetic transient) at the Connection Point

• For the purpose of dynamic simulations, the model provided shallcontain the following sub-models:

• Power control;• Voltage control;

• Demand Facility and Transmission connected Distribution Network protection models

• The constituent demand types, i.e. Industrial, Commercial, Domestic; and• Converter models as applicable.

• The Relevant Network Operator or Relevant TSO shall have the rightto require Significant Demand Facility and/or TransmissionDistribution Network recordings in order to compare the response ofthe model with these recordings




4123/02/2012

Interim operational notification

Final operational notification

Limited operational notification

- Itemized compliance statement- Detailed technical data- Manufacturer Data & Performance Type Certificate

(Report containing results from laboratory type testingfor temperature control devices)

- Simulation models (static and dynamic)

For Significant Demand Facilitiesand Transmission-connected Distribution Networks only- Practical tests demonstrating compliance- Validation of simulation tests and studies

- Modification or loss of capacility- Equipment failure

Compliance & Operational notificationprocedure :

4223/02/2012

Compliance & Operational notificationprocedure : DerogationsFor both new and existing Demand Facilities and Distribution Networks• Demand Facility and Distribution Networks

• introduces request for derogation to the TSO (Incl. Detailed reasoning)• TSO

• can request an exemption from CBA to the National Regulator• provides the National Regulator with his assessment, possibly based on CBA

• National Regulator• informs the Demand Facility and DSO, TSO and ACER about the decision

International coordination• National Regulator

• keeps a register of derogations granted or rejected• sends an update to ACER and ENTSO-e every 6 months

• ACER• emits advises to National Regulators

23/02/2012 43

Presentation of ENTSO-e DraftConnection Codes

Requirements for Generators&Requirements for Distribution Network Companies and Demand Facilities

44

Jonathan Sprooten

February 21, 2012

Documents

Presentation of ENTSO-e Draft Connection Codespublications.elia.be/upload/UG_upload/4I7GVHN41W.pdf · 30/05/12 Final draft approval by ENTSO-e 25/10/12 Final draft approval by ENTSO-e