Guidance Notes For Power Park Modules Issue 5 (GB User)
Guidance Notes For Power Park Modules Issue 5 (GB User)
Modules
GB Users - Issue 5
June 2024
These Guidance Notes have been prepared by the National Grid Electricity System Operator (ESO)
to describe to Generators and other Users on the system how the Grid Code Compliance Processes
is intended to work. Throughout this document National Grid refers to National Grid ESO unless
explicitly stated otherwise.
These Guidance Notes are prepared, solely, for the assistance of prospective Generators
connecting directly to the National Electricity Transmission System or Large Embedded Power
Stations. In the event of dispute, the Grid Code and Bilateral Agreement documents will take
precedence over these notes.
Small and Medium Embedded Power Stations should contact the relevant Distribution Network
Operator (DNO) for guidance.
These Guidance Notes are based on the Grid Code, Issue 6, Revision 23, effective from the 22 April
2024. They have been developed from Issue 4 of the Guidance Note of October 2021 and reflect
the major changes brought about by Grid Code revisions to facilitate compliance with the European
Requirements for Generators.
Definitions for the terminology used this document can be found in the Grid Code. The Electricity
Customer Connections Manager (see contact details) will be happy to provide clarification and
assistance required in relation to these notes and on Grid Code compliance issues.
ESO welcomes comments including ideas to reduce the compliance effort while maintaining the
level of confidence. Feedback should be directed to the ESO Electricity Connection Compliance
team at:
Disclaimer: This document has been prepared for guidance only and does not contain all the
information needed to comply with the specific requirements of a Bilateral Agreement with National
Grid. Please note that whilst these guidance notes have been prepared with due care, National Grid
does not make any representation, warranty or undertaking, express or implied, in or in relation to
the completeness and or accuracy of information contained in these guidance notes, and
accordingly the contents should not be relied on as such.
© National Grid 2024
Foreword ................................................................................................................ 1
Contents................................................................................................................. 2
Abbreviations ......................................................................................................... 5
Introduction ............................................................................................................ 9
Protection Requirements...................................................................................... 19
Islanding Protection ......................................................................................................................... 19
Appendices .......................................................................................................... 21
Appendix D: Power Park Unit Performance Registration and Fault Ride Through
............................................................................................................................. 54
Scope .............................................................................................................................................. 54
Generic Power Park Unit Type Validation ....................................................................................... 54
Background to Generic Power Park Unit Type Validation............................................................... 54
Confidentiality Provisions ................................................................................................................ 55
Areas Suitable for Manufacturer’s Data & Performance Report ..................................................... 56
Submitting Data into the Register of Manufacturer’s Data & Performance Report ......................... 57
Summary of Grid Code Fault Ride Through Requirements ............................................................ 57
‘Mode A’ Requirements - first 140msec of a fault ........................................................................... 57
‘Mode B’ Requirements - fault period beyond the first 140msec .................................................... 58
Requirements for Induction Generators .......................................................................................... 58
Fault Ride Through Testing ............................................................................................................. 59
This section includes a list of the abbreviations that appear in this document.
Abbreviation Description
AVC Automatic Voltage Control (on transformers)
AVR Automatic Voltage Regulator
BA / BCA Bilateral Agreement / Bilateral Connection Agreement
BC Balancing Code
BM / BMU Balancing Mechanism / Balancing Mechanism Unit
CC / CC.A Connection Conditions / Connection Conditions Appendix
CCGT Combined Cycle Gas Turbine
CP Compliance Processes
CSC Current Sourced Converter
CUSC Connection and Use of System Code
DC Direct Current
DCS Distributed Control System
DNO Distribution Network Operator
DMOL Design Minimum Operating Level
DPD Detailed Planning Data
DRC Data Registration Code
EDL/EDT Electronic Data Logging / Electronic Data Transfer
ELEXON Balancing and Settlement Code Company
ESO Electricity System Operator
FON Final Operational Notification
FRT Fault Ride Through
FSM Frequency Sensitive Mode
GB Great Britain
GCRP Grid Code Review Panel
GEP Grid entry point
ION Interim Operational Notification
LSFM Limited Frequency Sensitive Mode
LON Limited Operational Notification
MEL Maximum Export Limit
To achieve Operational Notification, the Generator, the company owning and operating a Power
Park, must demonstrate compliance with the Grid Code and Bilateral Agreement. The Grid Code is
a generic document which specifies requirements regardless of local conditions. The Bilateral
Agreement is a site-specific document agreed by ESO and the Generator, which for technical
reasons, may specify additional/alternative requirements or specific parameters within a range
indicated in the Grid Code. The total requirements placed on Generators are therefore the
aggregation of those specified in the Grid Code and Bilateral Agreement.
This particular edition of the guidance notes has been written for new distributed generation
technologies (such as Power Park Modules) referred to in the Grid Code as Power Parks. The
guidance notes contents are based on experience gained from wind turbines, but similar
arrangements are expected to apply to other renewable technologies. An additional document exists
that expands on guidance specifically for Electricity Storage modules. Guidance for conventional
synchronous plants and HVDC converter equipment is provided separately.
For existing connections (connected prior to 27 April 2019)1 the Generator will be deemed a GB
User and the new ECC user requirements will not apply. However, if an existing power station
undertakes a significant modification to its plant or apparatus new requirements may become
applicable. For example, should an existing wind turbine be replaced by a new model of turbine this
will be required to meet the ECC.
Generators may, if they wish, suggest alternative tests or studies, which they believe will
demonstrate compliance in accordance with the requirements placed on themselves and ESO.
Where an existing power station plans undertakes a modification to its plant or apparatus this should
be discussed with the ESO connection account manager at the earliest opportunity as the extent of
the modification could result in the application of the new ECC requirement to an existing connection.
The table below set out ESO’s expectation for some typical modifications, for specific advice please
contact ESO using the details in Appendix E.
The final decision on whether a modification is deemed to apply EU Code User or GB User
requirements lies with the regulator, Ofgem in the event of dispute.
1. Generators with an agreed purchase contract for main plant items evidenced to ESO before November 2018 could still be
existing GB Users regardless of the connection date to the system.
8 New Generator changes its Yes – ECC Compliant if main plant not ordered.
Connection Date beyond April No – CC Compliant if main plant has been ordered and
2019. ESO informed by November 2018.
Table 1: Examples of modifications to existing sites and how they might be handled
Generators should note that using registered manufacturer data does not guarantee Grid Code
compliance for a Power Park Module but does indicate that the Power Park Unit is capable of
achieving Grid Code compliance in the appropriate area. Any Generator wishing to use
manufacturer data is advised to contact ESO early in the compliance process to determine if the
information held in the Register of Manufacturer’s Data & Performance Report is appropriate and
sufficient in each case. This approach can be used for information relating to the dynamic model of
a turbine or park controller and the data and reports associated with fault ride through type tests.
While Generators may not see the Manufacturer’s Data & Performance Report information, they
must ensure that the correct reference is used as the same provisions will apply to this data as a
normal Data Registration Code or a User Data File Structure submission. The Manufacturer’s Data
& Performance Report reference given by the Power Park Unit manufacturer will contain the
following:
• Manufacturer name.
• Power Park Unit type.
• Date; and
• The relevant report version number.
The user should then reference the document in the appropriate place in the User Data File
Structure. For example, in case of fault ride through studies, assuming suitable fault ride through
information is available in a Manufacturers Data and Performance report, the user can enter the
following sentence:
“This information has been submitted generically to ESO and can be found in the ESO Register of
Manufacturer’s Data & Performance Report under document reference
“manufacturerX_10MWturbinetype1_22Aug08_reportver001”
Compliance Process
The process for Generators to demonstrate compliance with the Grid Code and Bilateral Agreement
is included in the Grid Code Compliance Processes (CP). In addition to the process and details of
the documentation that is exchanged to control the process, an appendix to the Compliance
Processes includes the technical details of the simulation studies that a Generator should carry out.
The Compliance Processes cross reference with other sections of the Grid Code, namely the
Planning Code (PC), the Connection Conditions (CC) and Operating Code 5 (OC5). Similarly, the
European Compliance Processes cross reference with other sections of the Grid Code, namely the
Planning Code (PC) and the European Connection Conditions (ECC).
The PC sets out the data and information that a Generator is required to submit prior to connection
and then maintain during the lifetime of the power station. The format for submission of the majority
of this information is set out in the Data Registration Code (DRC).
The OC5 sets out the technical details of the tests which ESO recommends to demonstrate
compliance with the Grid Code.
The technical requirements for a GB plant is based on its size at the connection point. These are
categorised as follows:
Point of Compliance
In concept Generators define the boundary at which compliance is demonstrated at the Grid Entry
Point or User System Entry point if connected to a Distribution System. This is the ownership
boundary between the Generating Company assets and the public network. This is often the
termination point in compact switchgear owned by a network licensee of a short cable owned by the
Generator. In practical terms, if the cable has negligible impact on performance, then metering for
Generator Control systems and signals for compliance assessment can be at the Generator end of
this short cable. If the cable is considered as having a material effect on performance, then control
and signal metering needs to be at the network owner’s end of the cable. As a rule of thumb
connection cables of less than 500m can be considered as negligible. Where cable lengths are
significant line compensation may be considered as an alternative to taking signals directly from the
connection point.
• A Compliance Statement and a User Self Certification of Compliance signed by the user. If
there are any requirements that have not been met, then a statement of these should be
submitted, together with a copy of the derogation.
• Detail of any changes to relevant Planning Code data (both Standard Planning Data and
Detailed Planning Data) and DRC schedules
In case all requirements have been satisfactorily fulfilled, ESO will issue the user with a FON and
the user can continue operation as before. In case of embedded plants, the notification will also be
sent to the relevant Transmission Owner. However, in the case where requirements are not fulfilled
and the user is deemed non-compliant, ESO will issue them a LON, and the relevant process will
be followed. It may be that some restriction is imposed, until the user resolves the issues.
The simulations must be based on the validated models supplied to ESO in accordance with Grid
Code Planning Code Appendix section 5.4.2 (PC.A.5.4.2 and PC.A.9) and are to be submitted
before issuing ION. Fault Ride Through studies are encouraged to be done using electromagnetic
transient (EMT) models.
In GC-0141, additional requirements have been added for Fault Ride Through studies, where non-
standard operating scenarios are taken into consideration. These requirements can be found in
CP.A.3.5.
Model Submission
To comply with the planning code requirements of the Grid Code, Users are required to provide to
ESO, a validated model(s) which adequately represent the dynamic performance of their systems
as demonstrated during the compliance process.
For connections in possession of a FON or an EON before the 1st of September 2022 the
requirements detailed in PC.A.5.4.2 (a to h) of the Grid Code still apply.
For future connections, or those that had started the compliance process but had not received an
EON by 1st September 2022 the modelling requirements detailed under PC.A.9 of the Grid Code
apply.
For the avoidance of doubt, the User is also required to comply with any additional modelling
requirements that might be included in the BCA, regardless of the planning code modelling section
applicable to the connection.
For detailed recommendations and advice on the model(s) submission aimed at complying with
PC.A.9 of the Grid Code please refer to “Guidance Notes on Modelling Requirements – GC0141
Grid Code Modification” by following the link below.
Compliance Tests
Tests identified in OC5.A.3 of the Grid Code are designed to demonstrate, where possible, that the
relevant provisions of the Grid Code and Bilateral Agreement have been met. However if the test
requirements described in OC5.A.3 are at variance with the Bilateral Agreement or the test
For each test to be carried out the description and purpose of the test to be carried out, results
required, the relevant Grid Code clause(s) and criteria of assessment are given in OC5. The
Generator is responsible for drafting test procedures for the power station as part of the compliance
process prior to the issue of the Interim Operational Notification (ION). Grid Code OC5 and the
appendices of these guidance notes provide outline test schedules which may assist the Generator
with this activity.
ESO may require further compliance tests or evidence to confirm site-specific technical
requirements (in line with the Bilateral Agreement) or to address compliance issues that are of
particular concern. Additional compliance tests, if required, will be identified following ESO’s review
of submissions of User Data File Structure (UDFS).
The tests are carried out by the Generator, or by their agent, and not by ESO. However, ESO may
witness some of the tests if agreed during the compliance process. Tests should be completed
following the test procedures supplied in the UDFS prior to the issue of the FON unless otherwise
agreed by ESO.
The Generator should also provide suitable digital monitoring equipment to record all relevant test
signals needed to verify the Power Park Module performance in parallel with ESO recording
equipment.
The station is responsible for providing the listed signals to the User's and ESO's recording
equipment. For ESO purposes, the signals provided are required to be in the form of dc voltages
within the range -10V to +10V (see CC.6.6.2.2). The input impedance of the ESO equipment is in
the region of 1MOhm and its loading effect on the signal sources should be negligible.
The station should advise ESO of the signals and scaling factors prior to the test day. A form of a
typical test signal schedule is shown below:
Reactive Power Output Mvar -8V to +8V - Reg Capacity to +Reg Capacity
At sites where there are multiple Power Park Modules it may be advantageous for the Power Park
developer to cable the signals for several Power Park Modules to a single point. This may allow
simultaneous testing of multiple Power Park Modules maximising usage of periods of high wind and
shortening overall test times. Where possible the person initiating the test injection signal (usually
the manufacturer), the test co-ordinator (usually the owner) and the ESO monitoring signals should
be in the same room to minimise co-ordination issues during witness testing.
The Power Park developer must inform ESO if the signal ground (0V) is not solidly tied to earth or
of any other potential problems which may impact on the quality of the signals to be recorded.
With Power Park Modules, where sometimes real time analogue signals cannot be outputted from
the control scheme, the Grid Code OC5.A.1.3(a) allows for the basic signals to be supplied directly
from transducers connected to CTs/VTs on the interface circuit. The transducer(s) should be
permanently installed at the Users location to easily allow safe testing at any point in the future, and
to avoid a requirement for recalibration of the CTs / VTs. All the signals should then be available
from the Power Park control systems as a download once the testing has been completed as
described in OC5.A.1. 3(b) and (c).
For offshore Power Park Modules, the control and signals for the witnessing of all testing should
be available at the onshore connection (Interface) point to avoid the risks associated with offshore
working. For offshore Power Park Modules the real time signals for witnessing tests are measured
at the onshore Interface Point as illustrated in the following diagram and mentioned in
OC5.A.1.3.2(iii).
NGET
Stat
com
Where these signals are provided to ESO, it should be done in a consistent electronic format with a
time stamp in a numerical format which can be interpreted in Excel. To facilitate efficient analysis
the test results should include signals requested by ESO set out in the columns order as indicated
in the tables in Appendix G.
• Signals for non-witness tests should be provided in excel format and in the order and format
presented in Appendix G unless otherwise agreed, in advance, with ESO.
• Where any additional test signals to those indicated in the tables are presented these
should only be added with the agreement of ESO and be entered within the files as
additional columns to the right of the required signals.
• Where a signal cannot be provided, and this has been agreed with ESO in advance of the
tests, a blank column should be retained within the data.
• Where additional signals are included or the signals are presented but not in the
arrangement detailed above the data may be rejected and the customer will be asked to
resubmit the data in the agreed format.
June 2024 | Guidance Notes for Power Park Modules 16
Compliance Test Log sheet
Where test results are completed without any ESO presence but are relied upon as evidence of the
compliance they should be accompanied by a log sheet. This sheet should be legible, in English
and detail the items in Appendix G.
• A suitable interface which allows ESO a view of the key test parameters graphically in real-
time from the ESO office in Warwick. This would effectively provide the view of tests
currently achieved by ESO connecting its recording equipment while at site.
• Where ESO has decided to allow testing without real-time witnessing for compliance testing
with lower materiality, such as repeat tests. In such circumstances manufacturers or
developers must provide all the test data to ESO in the standard format set out in the
guidance note complete with an appropriate test log sheet.
• Where ESO has decided that the design of a Generators plant and apparatus is
standardised, and the compliance can be evidenced by reference to a generic set of tests
completed and accepted previously. This could be reference to Equipment Certificates
where these have been accepted by ESO. This process will be offered provided in ESO’s
opinion it does not pose a material risk in terms of the specific site installations.
ESO will raise this during the compliance process and are open to suggestions from Developers.
For manufacturers looking to suggest options or develop systems to facilitate remote witnessing
please discuss with your compliance contact or contact ESO using the details in this guidance note.
Even though different Power Park Modules may be comprised of the same Power Park Unit type,
differences in performance can result. Submitting a Register of Manufacturer’s Data & Performance
Report reference can therefore not be a guarantee of compliance, and the suitability of the reference
should be discussed with ESO as part of the normal compliance process.
Interim Operation
As there may be a considerable period between commissioning the first and last power Park Unit
within a module, the Grid Code Compliance Processes (CP) provides two capacity restrictions
during commissioning. These restrictions are managed by items included in the Interim Operation
Notification (ION). The Generator is required to complete basic voltage control and frequency
response tests and have the results approved by ESO in order to have the capacity restrictions
released.
The Generator should be aware that this interface with ESO transmission planning will normally be
available in weekday working hours only. As best practice, the Generator should advise the ‘ESO
Control Centre’ and in Scotland the relevant Transmission Owner, or Distribution Network Operator
(if embedded) of the times and nature of the proposed tests at the earliest stage possible and where
possible with 28 days’ notice. If there is insufficient notice or information provided by the Generator,
then the proposed testing may not be allowed to proceed.
The Generator should provide details of all the protection devices fitted to the Power Park Module
and Power Park Units together with settings and time delays, including:
Under / Over Voltage protection Number of stages, trip characteristics, settings and time
delays
Over Current Protection Element types, characteristics, settings and time delays
Islanding Protection (see below) Type, description, settings and time delays
Table 4: List of some protection details to be submitted
Islanding Protection
ROCOF protection should be disabled for directly connection and if islanding protection is
required, an inter-tripping scheme is recommended. For Embedded generation, Islanding
protection should be set in line with the G59/G99 requirement.
As stated in CC.6.1.3, the System Frequency could rise to 52Hz or fall to 47Hz. The generator
must continue to operate within this Frequency range for at least the periods of time given in
CC.6.1.3, unless ESO has specified any other requirements. Plant Owners will be responsible for
protecting their equipment. If the frequency range is outside the range 52Hz to 47Hz, it is up to
the Plant Owner to decide whether to disconnect their apparatus in England and Wales, non-
synchro and PPM in Scotland shall be tripped according to the Grid Code.
With respect to harmonics, the Grid Code CC.6.1.5(a) requires that the Electromagnetic
Compatibility Levels for harmonic distortion on the Transmission System from all non-linear sources
under both planned outage and fault outage conditions, (unless abnormal conditions prevail) shall
comply with the compatibility levels given in Appendix A of Engineering Recommendation G5/4. The
Grid Code further requires that the planning criteria contained within Engineering Recommendation
G5/4 be applied for the connection of non-linear sources to the Transmission System, which result
in harmonic limits being specified for these sources in the relevant Bilateral Agreement.
With respect to voltage fluctuations, it is also a requirement of the Grid Code that voltage fluctuations
are kept within the levels given in Grid Code CC.6.1.7 and/or Table 1 of Engineering
Development schemes with non-linear element(s) are assessed by the Transmission Owner for their
expected impact on the harmonic distortion and voltage fluctuation levels. For harmonic voltage
distortion, the process detailed in Stage 3 of Engineering Recommendation G5/4 is applied. For the
voltage fluctuation, the principles outlined in Engineering Recommendation P28 issue 2 are used,
with contribution from the Power Park being calculated according to the International
Electrotechnical Commission standard IEC61400-21.
Specific information required for the assessment of harmonic voltage distortion and voltage
fluctuation is detailed in Grid Code DRC.6.1.1. Any component design parameters for planned
reactive compensation for the Power Park Module as detailed in Grid Code PC.A.6.4.2 should also
be included giving due attention to tuned components.
For Power Parks Modules that are to be connected to Distribution Systems, Distribution Network
Operators may undertake similar assessments to comply with the requirements of the Distribution
Code in terms of harmonic distortion and voltage fluctuation.
In summary, the first part of the requirement is for the Power Park Module to be capable of operating
with no reactive power transfer to the public power system (with a tolerance within +/-5% of active
power output) from zero power output to full output. The second part of the requirement is for the
Power Park Module to be capable of operating with a range of reactive power outputs when
producing more than 20% real power. This reactive power capability at the connection point (or HV
side of the connection transformer for a “Transmission” connection site in Scotland) is illustrated in
the Figure 1 in CC.6.3.2.
Below 20% real power output, the Power Park Module may continue to modulate reactive power
transfer under voltage control or switch to zero reactive power transfer. If there is a switch to zero
reactive power transfer, the Grid Code requires that there is a smooth transition between Voltage
Control at active power levels greater than 20% and reactive power control at active power levels
less than 20%.
Further clauses of Grid Code CC.6.3.2 include some variations to the Reactive Capability
requirements relating to older Power Park Modules completed before 1 January 2006.
Grid Code CC.6.3.4 states that the reactive power capability must be fully available at all system
voltages in the range 5% of nominal. Generators connected at 33kV or below, are only required to
meet the relaxed voltage/reactive capability envelope shown by CC.6.3.4 Figure 4. This relaxation
recognises that the power park developer does not have control of a transformer tapchanger to
control voltages within his network. The CC.6.3.4 capability is not normally tested but is
demonstrated by simulation.
In the event that during system incidents (i.e. the voltage is <95% or >105%) plant should deliver
the maximum (lagging or leading respectively) reactive power possible, whilst remaining within its
design limits.
The development of the MSA table for offshore schemes differs from that onshore and is discussed
later in this chapter.
The MSA for the offshore plant is based on the reactive power at the Commercial Boundary (which,
as per the definition in the CUSC, is at the HV side of the offshore transformer). As mentioned above,
even though CC.6.3.2. requires zero reactive power at the Offshore Grid Entry Point, other schemes
may be agreed with the ESO and OFTO. As such, these schemes are broadly divided into four
scheme categories, listed in the table below, and the MSAs are defined accordingly.
Testing
Reactive Power at IP Reactive Power at OGEP MSA
Requirement
Sch. 1 Provided wholly by the 0 MVAr, provided by Zero OC5.A.3.8
OFTO Offshore PPM. Cable gain
compensated by assets
(such as shunt reactors)
Sch. 2 Provided wholly by the Some reactive power Yes (see OC5.A.3.4
OFTO provided by Offshore PPM to discussion
compensate for cable gain below)
Sch. 3 Provided wholly by Some reactive power Yes OC5.A.3.4
Offshore PPM (on behalf of provided by Offshore PPM to
OFTO) cover for both cable gain
and to fulfil requirements at
IP
Sch. 4 Provided in part by OFTO Some reactive power Yes OC5.A.3.4
and in part by Offshore provided by Offshore PPM to
PPM cover for both cable gain
and to fulfil requirements at
IP
Table 6: Schemes of Offshore PPMs
Scheme 1 is the recommended scheme in the Grid Code. Since the PPM provides zero reactive
power at the OGEP, the MSA is a table of zeroes.
In Scheme 2, the PPM provides reactive power at the OGEP to compensate for the cable gain.
However, since it does not contribute to reactive power at the TIP, the MSA table has little
significance.
Schemes 3 and 4 are where the PPM contributes, at least in part, to reactive power at the TIP. The
MSA tables are drafted depending on the reactive power at the commercial boundary.
When carrying out the reactive capability tests at the Transmission Interface Point (TIP) onshore,
the measurements for the output from the offshore wind turbines should also be requested. This will
help establish the full picture.
The aim of the test is to capture performance of the Power Park Module at or as close to full output
as possible recognising there are the obvious issues with wind forecasting. In order that the
Generator has maximum opportunity to take advantage of periods of high wind/Tidal Flow/Sunlight
etc and recognising the steady state nature of these tests, the Reactive Capability test is not usually
witnessed by a ESO compliance engineer.
Grid Code OC.5.A.3.4.1 sets a minimum power output level for carrying out the tests of 85% of
Registered Capacity. If the Power Park Module output is below this, the test should not be scheduled
or attempted. Assuming power output is greater than 85% output with a good forecast for the hour
ahead then the test can commence. Some variability in output below the 85% may be accepted. For
the tests at maximum power, the available output should not fall below 50%, as indicated by
OC.5.A.3.4.5.
In order to demonstrate that a Power Park Module can satisfy the reactive capability requirements
it is necessary to perform reactive capability tests as set out in OC5.A.3.4.5. An example of a
corresponding test schedule is shown below.
Notes
1. If the Power Park Module does not provide voltage control below 20% active power output then
test 6 should be carried out to demonstrate smooth transition to within the required reactive power
envelope.
2. If the Power Park Module provides voltage control down to zero active power output then tests 7
and 8 should be performed
Reactive Capability tests are not normally witnessed by ESO so where a Generator is recording the
tests they should record details such as the HV system voltage and transformer tap position and
equipment in service, as applicable, across the test period.
For offshore PPMs, Schemes 1 and 2, there is an additional requirement to show that the reactive
power at the OGEP is as designed (OC5.A.3.8). where the transformer is tapped and it is shown
that the PPM can still provide the reactive power at the OGEP as per design.
Summary of Requirements
The generic requirements for voltage control are set out in the Grid Code Connection Conditions
with any site-specific variations included in the Bilateral Agreement. This section summarises the
key requirements using the generic values included in the Grid Code.
Grid Code CC.6.3.8 requires provision of a continuously acting automatic voltage control which is
stable at all operating points. The point of voltage control is the Grid Entry Point or User System
Entry Point if Embedded.
• CC.A.7.2.2.2 The voltage set point should be adjustable over a range of 5% of nominal
with a resolution of better than 0.25%.
• CC.A.7.2.2.3 The voltage control system should have a reactive slope characteristic which
must be adjustable over a range of 2 to 7% with a resolution of 0.5%. The initial setting
should be 4%.
• CC.A.7.2.3.1 The speed of response to a step change should be sufficient to deliver 90% of
the reactive capability within 1 second, with any oscillations damped out, so that the peak-
to-peak oscillations in reactive power settle down to less than 5% of the change in steady-
state reactive power within a further 2 seconds.
• CC.A.7.2.2.5 The control system should deliver any reactive power output correction due
from the voltage operating point deviating from the slope characteristic within 5 seconds.
• CC.A.7.2.2.6 The Power Park Module must continue to provide voltage control through
reactive power modulation within the designed capability limits over the full connection point
voltage range 10% (CC.6.1.4) however the full reactive capability (CC.6.3.2) is only
required to be delivered in line with CC.6.3.2 and Figure CC.A.7.2.2(b) or Figure 4 of
CC.6.3.4 if applicable.
• Grid Code figures CC.A.7.2.2(b) and CC.A.7.2.2(c) illustrate the operational envelope
required.
The Generator must provide ESO with a transfer block diagram illustrating the Power Park Module
voltage control scheme and include all associated parameters. This forms part of Schedule 1 of the
Data Registration Code and should be included in part 3 of the User Data File Structure (UDFS).
The information will enable ESO to review the suitability of the proposed test programme to
demonstrate compliance with the Grid Code.
The ESO Control Centre issues voltage control instructions to all Balancing Market participants. For
Power Park Modules the usual instruction is to alter Target Voltage set point and should be carried
out in the usual 2 minutes required for Ancillary Service instructions. The slope may also be varied
by control instruction, but the Generator has up to a week to complete the change. Slope is usually
expected to be set at 4%. The procedures for Voltage Control instructions are included in Grid Code
Balancing Code (BC) 2.
Transient Response
The Grid Code CC.A.7.2.3.1 sets out a number of criteria for acceptable transient voltage response.
The two Figures below illustrate responses from two different control philosophies that would be
considered as meeting the Grid Code.
Figure B.1 illustrates a control scheme which employs a constant speed of response.
1.200 Any oscillations should be less than 5% (peak to peak) of the change in reactive
power, within 2s of achieving 90% response
1.000
90% of the required change in Reactive Capability should occur within 1 second.
0.800
0.600
0.400
0.2s Maximum Dead Time
0.200
0.000
0.00 1.00 2.00 3.00 4.00 5.00 6.00
Time (Seconds)
Figure B.1
1.200 Any oscillations should be less than 5% (peak to peak) of the steady state change in reactive
power, within 2s of achieving 90% response.
1.000
90% of the required change in Reactive Capability should occur within 1 second.
0.800
0.600
0.400
0.2s Maximum Dead Time
0.200
0.000
0.00 1.00 2.00 3.00 4.00 5.00 6.00
Time (Seconds)
Figure B.2
Both Figures B.1 and B.2 are examples of acceptable responses. Both graphs show the response
to two steps, one to initiate a 1pu and the other a 0.5pu change in reactive capability. The graphs
show how a variable and constant rate of change both can allow the system to achieve the objective.
In both cases the dead time is less than 200ms and 90% of the reactive capability (i.e., 90% of 0.95
power factor at full load or 32.9% MVAr as measured as a proportion of rated power at any other
load) is achieved in 1 second. The maximum oscillation in reactive power, in terms of peak-to-peak
value, is limited to less than 5% of the change in steady-state reactive power within 2 seconds.
Note: The Grid Code states that the reactive response to a change should be “linearly increasing”.
For technologies where this may not be appropriate (e.g., capacitor switching), provided the
performance is equal to or faster than shown above it will be acceptable.
As a result, Power Park Modules in Scotland with a completion date before January 2006 the point
of Voltage Control may be at the Power Park Unit terminals and appropriate intermediate busbar, or
connection point as defined in the Bilateral Agreement.
For “Transmission Connected” Power Park Modules in Scotland the Grid Code specifies the Mvar
requirement at the HV side of the 33/132 kV or 33/275 kV or 33/400 kV transformer (CC.6.3.2 (c))
Reactive Voltage
Capability Control
CC.6.3.2 CC.6.3.8
The following example illustrates derivation of the reactive capability at the 33 kV point for a 151MW
Power Park Module with a maximum capability of 150 MW, the 0.95 power factor corresponds to
49.3 MVars.
The maximum lagging capability requirement at the LV will be when the active power generation is
at 100% as reactive absorption in transformer is greatest.
The maximum leading capability will be at 50% generation due to the shape of the requirement
characteristic below 50% active power.
-43.6
18
It can be seen that the Qmax and Qmin at the 33kV busbar are not symmetrical so the slope is set
for the capacitive capability and is then continued for the inductive range. This is the same
philosophy for a typical Static Var Compensator. When the slope is 4%, for a voltage change of 0.04
pu, the MVar at LV should change from 0 MVar to 75.3 MVar at the LV. This slope line should be
then extended in the opposite direction only as far as to provide -43.6 MVar, i.e. the maximum
leading capability. However, the voltage change needed to produce –43.6 MVar would be a voltage
increase less than 0.04 pu. It should be noted that when the reactive power at the LV is 0 MVar, at
rated MW, there will be an intake from the transmission system of about 19 MVars.
LV pu voltage
1.00
4% Slope
0.96
-43.6MVAr 0 75.3MVAr
Leading MVAr Lagging MVAr
(equiv. 0.95pf at HV) (equiv. 0.95pf at HV)
Operationally as Qmax varies with the amount of plant in service in accordance with CC.6.3.2 the
voltage control slope should be recalculated to reflect the revised Qmax.
Consider the above example with the Power Park Module having 60 Power Park Units capable of
contributing 60 MVars (i.e., 1 Mvar per Power Park Unit) and a static compensation source capable
of delivering 20 MVar giving a total capability of 80 MVar. With all plant in service the voltage control
slope should be based on 75.3MVar as shown in the diagram. With the static compensation source
Where steps can be initiated using network tap changers, the Generator will need to coordinate with
the host Transmission or Distribution Network Operator. Consideration should also be given to
switching the associated tap changer Automatic Voltage Control (AVC) from auto to manual for the
duration of the test.
The following generic procedure is provided to assist Generators in drawing up their own site specific
procedures for the ESO Module Voltage Control Tests. ESO may ask for steps to the Voltage
Reference greater than those shown below within the guidelines of Engineering Recommendation
P28.
In the case of Power Park Modules that do not provide voltage control down to zero Active Power
a test to demonstrate the smooth transition from voltage control mode to unity Power Factor shall
be carried out. The Power Park Module voltage setpoint should be altered to produce lagging
Reactive Power or absorbing leading Reactive Power at a low Active Power level where voltage
control is provided. The Power Park Module Active Power should then be reduced to zero Active
Power as a ramp over a short period (60 seconds is suggested).
Where the voltage control system includes either discretely switched shunt capacitors/reactors or
bias capacitors to provide part of the reactive capability, the test program should demonstrate the
performance when these are switched.
ESO will not permit PSS commissioning until the tuning methodologies and study results used in
any PSS settings proposal have been provided to ESO. A report on the PSS tuning should be
provided along with the proposed test procedure in the User Data File Structure (Part 3). Based on
the information submitted, ESO will meet with the Generator to discuss and agree the initial PSS
settings for commissioning.
The suitability of the tuning of any PSS is checked in both the time and frequency domains. In the
time domain, testing is achieved by applying a small voltage step change on a module basis.
Comparisons are made between performance with and without the power system stabiliser in
service.
For analysis in the frequency domain, a bandwidth-limited (200mHz-3Hz) random noise injection
should be made to the Power Park Module voltage reference. The generator should provide a
suitable band limited (200mHz-3Hz) noise source to facilitate noise injection testing. The random
noise injection will be carried out with and without the PSS in service to demonstrate damping. The
PSS gain should be continuously controllable (i.e. not discrete components) during testing.
The suitability of the PSS gain will also be assessed by increasing the gain in stages to 3x the
proposed setting.
The following generic procedure is provided to assist Generators in drawing up their own site-
specific procedures for the ESO PSS Tests.
The Grid Code sets out Frequency Control requirements in a number of separate places, notably
the Glossary & Definitions (GD), the Connection Conditions (CC) and Balancing Code (BC) 3. This
section summarises the key requirements.
The GD of the Grid Code defines Primary, Secondary and High frequency response including the
requirement that the response is progressively delivered with increasing time.
CC.6.3.3 of the Grid Code specifies that the Power Park Module must be capable of maintaining a
minimum level of active power (see Figure 2 of CC.6.3.3 (b)) in the frequency range 47Hz to 50.5Hz.
CC.6.3.7 of the Grid Code specifies the minimum frequency control capability, in particular the
frequency control must be:
Grid Code Figure CC.A.3.1 specifies a minimum requirement for frequency response of 10% of
Registered Capacity achievable for Primary, Secondary and High Frequency response. This
minimum value is designed to ensure that plant provides a suitable contribution to maintain
frequency correction when connected to the system and selected to Frequency Sensitive Mode
(FSM) and response capability in excess of 10% is encouraged.
The speed of response is an important criterion and the Grid Code Figures CC.A.3.2 and CC.A.3.3
indicate typical responses from plant with no delay in response from the start of the frequency
deviation. Practically there is a permissible deadband and ESO accepts a delay of up to but not
exceeding 2 seconds before measurable response is seen from a generating unit in response to a
frequency deviation.
BC3 of the Grid Code specifies how plant should be operated and instructed to provide frequency
response. The section also sets out the requirements on how all plant should respond to the system
frequency rising above 50.4/50.5Hz, by progressively reducing output power.
Details of the tests required for the preliminary and main governor response tests are provided in
OC5.A.3.6 but additional guidance is provided in this Appendix including outline test procedures.
Limited Frequency Sensitive Mode is the default mode used when not instructed by ESO to
provide Frequency Response Services. In this mode the Power Park Module is not required to
provide any increase in active power output if frequency reduces below 50Hz and is only required
to maintain active power output in accordance with CC.6.3.3. However, the Power Park Module is
required to respond to high frequencies above 50.4Hz beyond which the Module must reduce the
active power output by a minimum of 2% of output for every 0.1Hz rise above 50.4Hz (see figure
C1). Should this cause power output to be forced below Designed Minimum Operating Level (DMOL)
then the Power Park Module may disconnect after a time if operation is not sustainable. However
for Power Park Modules, it is acceptable for individual Power Park Units to be disconnected, in order
to achieve further power reductions without tripping the module.
95% of Output
Frequency Sensitive Mode is used when control room instructs the user to provide frequency
response services. In this mode the Power Park Module must adjust the active power output in
response to any frequency change according to the agreed droop characteristic (between 3-5%).
For the purposes of the Mandatory Services Agreement the frequency response performance is
measured in terms of the response achieved after a given duration. Between the band of 49.5 Hz
and 50.5 Hz, the plant is required to contribute at least 10% of capacity in either direction for a large
enough frequency change. It is recommended, however, that the plant’s contribution within this band
is not restricted.
When system frequency exceeds 50.5Hz, the Power Park Module must further reduce output by a
minimum of 2% of output for every 0.1Hz rise above 50.5Hz (see figure C2). Should this cause
power the output to be forced below the Designed Minimum Operating Level (DMOL) then the Power
Park Module may disconnect from the system after a time if operation is not sustainable. However,
When system frequency falls below 49.5Hz, it is recommended that the plant further increases its
output as per Figure C2, until it reaches maximum available capacity.
Active Power
MSOL/MRL
Target Frequency
CC.6.3.7(d), BC.3.4.2
Target Frequency
All Balancing Market Units (BMUs), irrespective of the plant type (conventional, wind, thermal or
CCGT, directly Grid Connected or Embedded), are required to have the facility to set the levels of
generator output power and frequency. These are generally known as Target MW and Target
Frequency settings.
The ESO Control Centre instructs all Active Balancing Market Unit to operate with the same Target
Frequency, normally 50.00 Hz. In order to adjust electric clock time the System Operator may
instruct Target Frequency settings of 49.95Hz or 50.05Hz. However, under exceptional
circumstances, the instructed settings could be outside this range. The Grid Code requires a
minimum setting range from 49.90Hz to 50.10Hz.
90% 54
85% 53.5
80% 53
Frequency (Hz)
% of Rated MW
75% 52.5
70% 52
65% 51.5
60% 51
CCL
55% 50.5
Selected for Frequency Response
at CCL = 55% of Rated MW Frequency Response Deselected
50% 50
45% 49.5
Time
0 5 10 15 20 25 30
MEL FPN Pavail MW 0.2 Hz dip MW 0.5 Hz dip Freq 0.2 Hz dip Freq 0.5 Hz dip
Notes:
The Maximum Export Limit (MEL), is declared to ESO as a Balancing Mechanism parameter
effectively equivalent to ‘Pavail’ which should be updated whenever the ‘Pavail’ changes by more
than 5% or 5MW. The Final Physical Notification (FPN) is the generated power profile submitted to
ESO for a ½ hour period before gate closure. Gate closure is one hour ahead of real time. The
Capped Committed Level (CCL) is the power level at which a Power Park Module operates when
selected for frequency response.
To demonstrate compliance, the Power Park Module should self-dispatch for 30 minutes at a load
significantly below the Maximum Export Level (MEL). The active power output and power available
should be recorded with a sampling rate not less than once per minute.
In order to verify the plant behaviour, it is essential that the module is tested in normal operating
modes. A frequency disturbance can be simulated by injecting the required frequency variation
signals to the frequency reference/feedback summing junction. The results obtained from reducing
frequency ramps will be used to verify primary and secondary frequency response. Similarly the
results obtained from increasing ramps will be used to verify the high frequency response. Robust
and stable response to islanding events can be demonstrated by injecting large and rapid frequency
disturbances and observing the response. The recommended tests are shown in Grid Code
OC5.A.3.6 Figures 1 and 2.
Ideally the signal will be software programmable with start/stop initiation via local or remote software
interfaces or local digital inputs. Alternatively, the signals should be a ±10V analogue input where 1
volt represents 0.2 Hz frequency change.
The above signals should be available at all control nodes within the Power Park controller network,
so that if appropriate and applicable, injection can take place on a single Power Park Unit or the
central controller.
Frequency
Feedback
In principle, the maximum capacity available for low frequency response is determined by the
‘deload’ level from MEL. It is assumed that the low frequency response obtained from the ‘deload’
points tested above will not be substantially different when the MEL is at other values below RC
provided the equivalent ‘deload’ from MEL is used (i.e. 70% RC would be undertaken at a load point
of MEL minus 30% of RC). If this is not the case the Generator must inform ESO and further tests
may be required. Similarly, the high frequency response should be similar at all MEL levels unless
the response was to encroach upon the SEL.
OC5.A.3.6 sets out the minimum power output and Power Park Unit availability for testing to be
carried out. However, ESO reserves the right to request a repeat of the tests at up to 100% of RC if
the response is shown to be non-linear or monitoring of frequency response delivery by ESO shows
deviations from the submitted frequency response data table.
Pre 70% Tests in Limited Frequency Sensitive Mode for Large Power
Park Modules
Preliminary LFSM test applies to large Power Park Modules with a registered capacity of 100MW or
more. With large multi-module power stations there may be a considerable delay before final
frequency response testing can be carried out. To control the risk to the system during this period
Grid Code OC5.A.3.3.1 requires two tests in Limited Frequency Sensitive mode to be completed
before 70%, but at least 50%, of the module has been commissioned.
With the Power Park Module running with all the turbines in service (100%) and then deloading to
MLP4, the following frequency injections should be applied:
The recorded results (e.g., Freq. injected, MW, Pavail, wind speed and control signals) should be
sampled at a minimum rate of 1 Hz to allow ESO to assess the plant performance from the initial
transients (seconds) to the final steady state conditions (which may typically take 2-3 minutes
depending on the plant design). The number of turbines in service should also be stated. Reference
power may also be included to help in understanding turbine behaviour.
The preliminary frequency response test results should be sent to ESO for assessment at least two
weeks prior to the final witnessed tests.
5. Response Tests at Load Point MLP3 (DMOL+ 0.6 x (80% MEL - DMOL)
(a) Operate the plant at MLP3.
(b) Conduct tests 15 to 17 as shown in OC5.A.3.6 Figure 1 and record plant responses.
1 Record plant MLP 6 condition including levels for module MW output, ambient wind
speed, and direction.
2 Change power park controller to manual and increase active power output to
maximum.
4 Reset power park controller to normal operating mode and allow MLP 6 condition to
be established
Plant in FSM
+2.0 Hz * Part of
• Inject +2.0* Hz frequency rise over 1 sec
functionality test
BC1 • Hold until conditions stabilise3 for islanding
-2.0 Hz
• Remove the injection signal over 1 sec4 CC.6.3.7 (c)(i)
• Hold until conditions stabilise at MLP 6
Plant in FSM
+0.6 Hz Part of
• Inject +0.6 Hz frequency rise over 30 sec
functionality test
BC2 • Hold until conditions stabilise3 for BC.3.7.1
-0.6 Hz
• Remove the injection signal over 30 sec4
Plant in FSM
No injection Check for live
L • Record normal system variation in frequency and frequency
active power of the generating unit over at least measurement
10 minutes. Load setpoint at maximum.
Switch to Limited Frequency Sensitive Mode
Plant in LFSM
+2.0 Hz Part of
• Inject +2.0* Hz frequency rise over 1 sec
functionality test
BC3 • Hold until conditions stabilise3 for islanding
-2.0 Hz
• Remove the injection signal over 1 sec 4 CC.6.3.7 (c)(i)
• Hold until conditions stabilise at MLP 6
Plant in LFSM
+0.6 Hz Part of
BC4 • Inject +0.6 Hz frequency rise over 30 sec
functionality test
• Hold until conditions stabilise3 for BC.3.7.2
-0.6 Hz
* This will generally be +2.0Hz unless an injection of this size causes a reduction in plant output that
takes the operating point below Designed Minimum Operating Level in which case an appropriate
injection should be calculated in accordance with the following:
For example 0.9Hz is needed to take an initial output 65% to a final output of 20%. Calculation of
the injected step should be as shown in the example given below
In addition, the Manufacturer’s Data and Performance Reports can provide a route for detailed data
that Power Park Unit manufacturers regard as commercially sensitive to be sent directly to ESO
without publication to the User(s).
National Grid
Figure D3 illustrates the process for referencing and using ‘generic’ data. Each project can, where
appropriate, reference information held in the ESO generator equipment Register of Manufacturer’s
Data & Performance Report substituting information that they are required to submit before
connecting to the National Electricity Transmission System and in lieu of some aspects of Grid Code
testing. Developers will not have access to this information from ESO and the only requirement is to
obtain the correct reference from the manufacturer. If no relevant or insufficient data is held in the
Register of Manufacturer’s Data & Performance Report then the data must be provided in full by the
developer.
National Grid
MD&P Register
reference
Figure D3 – The generic data (red arrow) is referenced but cannot be seen by the developer.
There will still be some requirement for site specific data (yellow arrow)
Confidentiality Provisions
Data submitted by developers under the Data Registration Code (Grid Code) is protected by the
confidentiality agreement contained in the Connection and Use of System Code (CUSC) and System
Please note that ESO cannot sign individual manufacturer’s confidentiality agreements as they may
not cover the following aspects which are necessary to participate in the generic compliance
process.
The following aspects are typical of the provisions of a confidentiality agreement between a
manufacturer and ESO in relation to registering generic Manufacturers Data and Performance
Reports information with ESO.
• This agreement has been written to reflect the confidentiality provisions in the CUSC which
deals with the confidentiality of data as between ESO and Developers generally. ESO will
NOT however be permitted to release this ‘generic’ information back to developers (with the
exception of the generic information document reference as originally submitted) which is
unlike data submissions received through the normal project chain.
• Some aspects of data must be passed to other Transmission System Operators and
Owners in GB for system operation and design reasons as per the System Operator and
Transmission Owner Code (STC).
• The ‘Purpose’ as defined in the Agreement reflects the purposes for which ESO do (and are
permitted under the CUSC) to use information provided to ESO by developers through the
normal project chain.
• The agreement is subject to the laws of England & Wales because the entire framework
within which this data will be used is structured around English law and if the data was
directly provided by a Developer it would be subject to English law.
• Company Policy requires ESO business areas to adopt information and records
management procedures that comply with all relevant legal requirements and are consistent
with best practice as applied to their business needs. The records management procedure
for this area provides that this data must be kept for 7 years after the data is last used. This
therefore requires that the data should be kept for a period equating to the life of any plant it
refers to plus a period of 7 years. This is in line with normal project data submissions direct
from developers.
• ESO may pass back information (e.g. computer models) to the manufacturer but does not
accept any liability in respect of its accuracy.
If this agreement is not signed then the standard Grid Code data requirements apply and all data
will need to be provided through the project chain. Failure to supply adequate data by either of these
methods will result in non-compliance by the developer with the GB Grid Code and possible
disconnection or denial of permission to connect to the GB transmission system.
To achieve registration for the item Fault Ride Through capability a series of tests and data
submissions will be developed to demonstrate the performance characteristics of a single Power
Park Unit. Details of these tests and submissions are to be agreed between the Power Park Unit
manufacturer and ESO. ESO may wish to witness some or all of these tests.
In order to be considered for registration, the Power Park Unit manufacturer should submit a report
to ESO outlining the details and results as appropriate for its consideration. Each report should have
an appropriate reference including manufacturer name, type of report (e.g. Fault Ride Through etc.),
Power Park Unit type, date and report version number to permit referencing in future projects or for
updates.
ESO will, following submission of all required reports and data, confirm to the Power Park Unit
manufacturer in writing whether the Power Park Unit report has been accepted. Once accepted the
Manufacturer’s Data & Performance Report Register status will be updated to indicate the
acceptance in respect of the relevant Grid Code requirement.
The Grid Code ‘fault ride through’ requirements apply to all faults on the 275kV or 400kV National
Electricity Transmission System. The requirements vary depending on the type of fault and the
Supergrid voltage profile (duration of fault or voltage dip).
These requirements can be conveniently referred to in the context of two separate fault modes (A &
B, which are respectively covered by CC.6.3.15.1(a) and CC.6.3.15.2(b) of the Grid Code).
Throughout this period the Power Park Module is required to remain transiently stable and
connected for all Supergrid phase voltages down to a minimum of 0%. It should also generate the
maximum possible reactive current without exceeding the transient rating limit of the Power Park
Module or any constituent element.
Within 0.5 seconds, following fault clearance and restoration of the Supergrid voltage to at least 90%
of nominal, the Power Park Module must restore the Active Power output to at least 90% of the level
available immediately before the fault.
Although the voltage will begin to recover upon fault clearance (within 140msec) it may not
necessarily reach 90% voltage within the 140msec period as illustrated in the Appendix of the
Connection Conditions (CC.A.4A.2). If the Supergrid Voltage has not restored to at least 90% within
140msec then the remaining fault period can be assumed to have a balanced retained voltage and
that ‘Mode B’ requirements will then apply for the remainder of the fault period.
GC-0141 has added the requirement that the Power Park Module stay connected and remain stable
for up to 30min, following a fault-ride-through event.
Throughout this period the Power Park Module is required to remain transiently stable and
connected. It must maintain Active Power at least in proportion to the retained balanced Supergrid
Voltage and generate the maximum possible reactive current without exceeding the transient rating
limit of the Power Park Module or any constituent element.
Within 1 second, following fault clearance and restoration of the Supergrid voltage to at least 90%
of nominal, the Power Park Module must restore the Active Power output to at least 90% of the level
available immediately before the fault. Once again, appropriately damped active power oscillations
shall be acceptable provided the total energy delivered during the period of the oscillation shall be
90% or more.
The worst-case duration for which Mode B requirements apply can be calculated by taking the lowest
voltage occurring after the first 140msec and finding where it intersects the profile illustrated in
CC.A.4A.3.
GC-0141 has added the requirement that the Power Park Module stay connected and remain stable
for up to 30min, following a fault-ride-through event.
ESO expects the tests to replicate each fault type (3-phase, phase-phase, two-phase to earth and
single-phase to earth) with varying magnitudes. The tests should illustrate any changes in
characteristics or internal operating modes that depend upon fault severity. For example DFIG wind
turbines that utilise crowbar or similar devices should implement tests that illustrate the crowbar
inception operating level and any consequential Power Park Unit characteristics, such as active and
reactive power fault contribution and power recovery characteristic.
• Rated MW
• 70% MEL when MEL is greater than or equal to Rated MW
• SEL when SEL is no greater than DMOL.
Fault Ride Through testing involves applying simulated fault conditions, by applying short circuits,
into known impedances to real systems. Compliance with fault ride through may be demonstrated
by test conditions which are different to those specified in this sub section and different to the
requirements specified in the grid code, provided:
The purpose of the tests is to characterise the Power Park Unit such that its limit of operation for
retained voltage (at the terminals of the Power Park Unit) is known. At the end of the test the results
should indicate the level of voltage depression the unit can with stand for the times specified. Whilst
the volts are depressed the Power Park Unit should deliver power in the same proportion as the
volts and then recover once volts are restored.
The tests should be performed on a single Power Park Unit using the test circuit shown below.
Power
Supply Protective Generator Park Unit
Connection Line Impedance Connection
Breaker Breaker Breaker
Protective
Line Impedance
Configurable
(ph to ph or
ph to earth)
Short Circuit
Impedance
Figure D5
• Operate the Power Park Unit (PPU) at nominal volts and Mode A
appropriate output.
• Apply a 2ph to earth short circuit reducing the volts to
0%
• Operate the Power Park Unit (PPU) at nominal volts and Mode A
appropriate output.
• Apply a phase to phase short circuit reducing the volts to
0%
• Operate the Power Park Unit (PPU) at nominal volts and Mode B
appropriate output.
• Apply a reduction in 3ph voltage to 30%
11 • Hold the voltage at 30% for the corresponding time in
Figure D4
• Increase the voltage to 90%
• Hold until conditions stabilise or a minimum of 3 minutes
Please note that this is just a guide and manufacturers are free to have their own designs and
techniques to achieve the same effect on the system.
Several scenarios (high and low system frequency and various wind variations) are covered for each
of four different operating points, to help explain how the response should be provided.
MW SET POINT
PAVAIL
MW DEMAND
ACTUAL MW
SYSTEM FREQUENCY
50.5
PAVAIL MW DEMAND
50.015 ACTUAL MW SYSTEM HZ
MW SET POINT
MW DEMAND
ACTUAL MW
SYSTEM FREQUENCY
50.2
50.015
Scenario 3 – Instructed to Frequency Sensitive Mode (from Limited Frequency Sensitive Mode)
while system frequency is already high.
MW DEMAND
SYSTEM FREQUENCY
50.2
50.015
PAVAIL MW DEMAND
ACTUAL MW SYSTEM HZ
MW SET POINT
PAVAIL
ACTUAL MW
No response Time
SYSTEM FREQUENCY
50.5
PAVAIL MW DEMAND
ACTUAL MW SYSTEM HZ
50.015
MW SET POINT
The green dots indicate where the system frequency passes from below 50Hz to above 50Hz. At
this point the Power Park Module control system should take and hold the corresponding MW output
value at that instant as the Power Park Module set-point. The Power Park Module should then
regulate in relation (wind conditions permitting) to that set-point until such times as the frequency
falls below 50Hz (red dots), the unit is instructed back into Limited Frequency Sensitive Mode or the
unit is instructed to a new de-loaded level
Set set-point
50.0
Reset set-point
49.8
0 30 60
Time (minutes)
PAVAIL
MW SET POINT
MW DEMAND
ACTUAL MW
50.5
SYSTEM FREQUENCY
50.0 MW SET POINT
PAVAIL MW DEMAND
ACTUAL MW SYSTEM HZ
PAVAIL
MW DEMAND
ACTUAL MW
MW SET POINT
PAVAIL
ACTUAL MW
SYSTEM FREQUENCY MW SET POINT
50.0
MW DEMAND
SYSTEM HZ
49.5
MW DEMAND
PAVAIL
ACTUAL MW
PAVAIL
50.4 ACTUAL MW
MW SET POINT
MW DEMAND
50.0
SYSTEM HZ
SYSTEM FREQUENCY
50.8
50.4
PAVAIL MW SET POINT
ACTUAL MW MW DEMAND SYSTEM HZ
PAVAIL
MW SET POINT
MW DEMAND
ACTUAL MW
PAVAIL
50.4 ACTUAL MW
MW SET POINT
50.0 MW DEMAND
SYSTEM HZ
PAVAIL
MW SET POINT
MW DEMAND
ACTUAL MW
PAVAIL
50.4 ACTUAL MW
MW SET POINT
50.0 MW DEMAND
SYSTEM HZ
Summary
When de-loaded in GB the Power Park Module is instructed to a set MW value rather than a delta
MW value from available MW (PAVAIL). While this may cause variability in the headroom for
frequency response it allows the system to be balanced in an effective manner when large amounts
of wind generation are connected (known as system balancing rather than frequency response).
For Frequency Sensitive Mode at full load the Power Park Module should take and hold the operating
point (MW value) at the instance the system frequency crosses from below 50.015 to above
50.015Hz as the set-point.
Limited Frequency Sensitive Mode at all times the Power Park Module should take and hold the
operating point (MW value) at the instance the system frequency crosses from below 50.4 to above
50.4Hz as the set-point.
For Frequency Sensitive Mode at a de-loaded value the Power Park Module should take the
instructed MW value as the set-point.
The guidance here applies to the behaviour of the complete Power Park Module. If frequency
controllers are implemented on individual turbines then variations to the suggestions here may have
to be made to achieve the desired aims at the point of connection.
The Power Park Module operator is still required to submit Final Physical Notification (FPN) and
Maximum Export Limit (MEL) data as normal. The MEL figure submitted to ESO should be updated
each time it differs from the available power by the greater of 5MW or 5% to ensure that the volume
of available response can be correctly calculated.
In some cases however, the maximum fault level may include contributions from other generation
embedded between the Point of Connection and the Supergrid. Consequently, the apparent
impedance derived by the maximum fault level may be lower than the actual impedance. This will
provide a worst case scenario. The maximum fault level data at the point of connection is readily
available and is therefore a reasonable place to start. If this conservative impedance estimate is too
arduous more detailed work will be needed to obtain a better impedance estimate.
For Power Parks with a point of connection to the Supergrid, the technique described below is still
appropriate however the equivalent impedance (described above) is removed.
In this conservative and simplified case, the network beyond the point of connection is represented
by, a controlled Thevenin source and equivalent impedance. The equivalent impedance is derived
from the maximum fault level at the point of connection.
The type validation tests were based on benchmarking the Power Park Unit at a node selected by
the manufacturer. The impedance between the point of connection and the ‘type validation node’
must reflect the equivalent aggregated impedance of the Power Park between the point of
connection and the same node.
The remaining impedance is the impedance between the ‘type validation node’ and the point at
which the model representation begins (model interface node). In some cases the type validation
node and the model interface node will be the same point and this impedance will not be included.
This simplified network can be implemented in a power system analysis package of the Developers
choice using the voltage dips specified in Studies 3.1 & 3.2. The results at node ‘A’ are then
compared to the type validation results to confirm ride through capability. The validity of the
generator model’s contribution to the retained voltage also needs to be confirmed by ensuring that
the contribution at ‘B’ is comparable with the results obtained during the type validation tests for the
equivalent profile at ‘A’.
The negative sequence network is identical to the positive sequence network except that the
generator model and the impedance between the ‘type validation node’ and the model interface
node are replaced with an equivalent negative sequence estimate obtained during the type
validation tests.
Point Of
Connection
Negative Sequence
Voltage at Super Grid
Solving the load flow for the above network using a voltage source corresponding to the negative
sequence magnitude at the Supergrid results in a negative sequence voltage estimate at the type
validation node (‘A’). The results at node ‘A’ are then compared to the type validation results to
confirm ride through capability.
Equivalent Circuit between Supergrid Busbar and Power Park Module Point of Connection
(showing transformer vector groups):
[For CC.6.3.15.1(c) assume system ‘nps’ impedance pre-and post-fault such that CC.6.1.6 limits
met]
# Columns may be left blank but the column must still be included in the files
# Columns may be left blank but the column must still be included in the files
# Columns may be left blank but must still be included in the files
In addition to the above, any material changes during the test, e.g., any Generating Units that
trip/start, changes to tap positions, etc, should be recorded
There are a number of different departments within National Grid that will be involved with this
connection. The initial point of contact for National Grid will be your allocated Customer
Connection Contract Manager for your Bilateral Agreement. If you are unsure of who your
allocated Customer Connection Contract Manager is then the team can be contacted on
[email protected].
For any correspondence relating to testing on the system following the Grid Code the IET process
should be followed with notifications made to the ‘.Box.Tranreq’ email address for England and
Wales connections and ‘.Box.TR.Scotland’ for all connections in Scotland.
Contact Address:
National Grid ESO, National Grid House, Warwick Technology Park, Gallows Hill, Warwick CV34
6DA