1. Compliance with the RfG
24 July 2017

2. Agenda Agenda 1 Welcome etc 1030 2 Introduction and background etc
Agenda 1
Welcome etc
1030 2
Introduction and background etc
1035 3
Type A – general requirements and testing
1100 4
Type B – general requirements, testing and simulations
1130 5
Type C - general requirements, testing and simulations
1200
Lunch
1230 6
Compliance documentation
1300 7
Implementation challenges
1315 8
Connexion/compliance processes
1330 9
Discussion and next steps 
1400 10
Finish
1430

3. Introduction
Compliance, as in the existing GB arrangements, remains the responsibility of the generator. The generator has to demonstrate compliance to the relevant system operator.
Compliance requirements need to be clearly articulated by the network operators
Although much of the RfG is familiar, there are new challenges – especially for distribution connected generation
The network licensees are working on specifying how compliance can be demonstrated in GB
The network licensees are very keen that the issues, especially the new ones, are discussed and debated with stakeholders.
Two stages of formal public consultation are expected probably in early and late Autumn
Issues will be debated and drafting approach formulated in the GC0102 workgroup (which will include RfG, HVDC and DCC)
Purpose of today is to help interested parties get up to speed and to try to ensure the formal WG process starts off on the right foot – it is not to debate the requirements.
As such today’s approach is fairly high level on general process rather than specific details of individual technical issues. It will only cover RfG and not HVDC nor DCC

4. Background The RfG has three main effects on compliance:
For transmission connected, and the largest distribution connected (eg >50MW), limited effects (broadly similar to current GB Compliance Process)
For Types A, B and C (assuming Distribution connected), new compliance and simulation requirements, particularly with respect to basic capabilities and fault ride through
The (possible) introduction of the Equipment Certificate regime
Note on Banding:
Likely to be 0 < A < 1MW < B < 10MW < C < 50MW < D
Or could be 0 < A < 1MW < B < 50MW < C < 75MW < D
And in either case anything connected at >110kV is D irrespective of size.

5. Background (2) The relevant parts of the RfG are:
Article Operational Notification
Article Compliance Monitoring
Article Compliance testing for synchronous
Article Compliance testing for PPMs
Article Compliance simulation for synchronous
Article Compliance simulations for PPMs
Network Licensees (ie NGET SO and the DNOs) often referred to as Relevant System Operator – ie SO or DNO as appropriate

6. The Requirements at a Glance
Technical Requirements
Type A
Type B
Type C
Type D
Operation across range of frequencies •
Rate of change of System Frequency (ROCOF)
Limited Frequency Sensitive Mode Over Frequency (LFSM-O)
Output Power with falling Frequency
Logic Interface (input port) to cease active power production
Conditions for automatic reconnection
Ability to reduce Active Power on instruction
Fault Ride Through and Fast Fault Current Injection
Conditions for automatic reconnection following disconnection
Protection and Control
Operational Metering
Reactive Capability
Active Power Controlability
Frequency Response including LFSM-U
Monitoring
Robustness
System Restoration / Black Start
Simulation Models
Rates of Change of Active Power
Earthing
Enhanced Reactive Capability and control
Voltage Ranges
Enhanced Fault Ride Through
Synchronisation
Excitation Performance

7. Type A

8. Type A
Full connexion requirements will be codified in G99 (and G98 for fully type tested Type A)
As far as possible technical requirements will be based on EN and TS
Additional GB connexion process and legal requirements included
Testing and compliance requirements will be included in G99/98.
Note that Types B and C will also be included in G99

9. Type A Requirements Requirement Proposed GB Parameters Frequency Range
47 Hz – 47.5Hz – 20 Seconds
47.5 Hz – 49 Hz – 90 minutes
49 – 51 Hz – Unlimited
51 – 51.5Hz – 90 minutes
51.5 – 52 Hz – 15 minutes
ROCOF
1Hzs-1 measured over 500ms window
LFSM-O
Frequency Threshold – 50.4Hz
Droop – less than 10%
Delay – no greater than 2s
Output Power with falling frequency
Threshold – 49.5Hz
5% Active Power output drop permitted between 49.5Hz and 47Hz
Logic Interface
Automatic Reconnection
Frequency Range 47 – 52Hz (as per G83/G59)
Maximum Active Power increase (as per G83/G59)

10. Type A Under RfG Compliance is with respect to the Module not the Unit
The Unit is the device generating electricity; the Module is the sum of the Units
For synchronous the indivisible components (ie which cannot run separately) form the Module; for asynchronous the sum of units is the Module.
Manufacturer Type Test Certificates or equivalent (eg Equipment Certificates) lend themselves well to unit tests (eg a Generating Unit or Power Park Unit)
For Type A, the requirements all relate to frequency which are easy to test at a Unit level.
Type tests or Equipment Certificates etc are a valuable tool for assessing Type A Generators both for manufacturers / Test Institutes and for Network Operators based on volume
For Type A Generating Plant, the Generating Plant Owner will need to supply additional information as required under Article 30 (ie the Equipment Certificate is a subset of the Installation Document)

11. Type A - Testing
Frequency Range Tests – 47 – 52 Hz – Tests applied to confirm operation over the frequency range for the required durations
Rate of change of Frequency Tests – 1Hzs-1 measured over a 500ms period – Test to demonstrate plant withstand capability up to 1Hzs-1 measured over a 500ms period.
Output Power with falling frequency – Frequency injections applied to the control system to demonstrate the Active Power output falls no more than pro-rata with frequency. (This can be demonstrated as part of the frequency range assessment).

12. Type A - Testing
Limited Frequency Sensitive Mode – Over Frequency Tests – Tests injected to demonstrate de-loading at frequencies in excess of 50.4Hz with a droop of 10% or less
Logic Interface – Test applied to demonstrate the plant can cease production in 5 seconds
Automatic reconnection - Tests applied to demonstrate automatic reconnection within frequency and ranges and maximum ramp rate

13. Type B

14. Type B Power Generating Module Requirements
Note that all the Type A requirements will be required for Type B too.
Requirement
Proposed GB Parameters
Active Power Reduction
Logic Interface
Fault Ride Through
Proposed Voltage Against Time Curves addressed as part of GC0100 (available from
Conditions for Automatic Reconnection
Covered by GC0102 System Management / Compliance Workgroup but would generally be considered to follow current practice
Protection and control
Operational Metering

15. Type B SPGM and PPM Requirements
Proposed GB Parameters
Synchronous
Reactive Capability
0.95 PF lead to 0.95 PF lag at Connection Point unless otherwise specified by NGET or Network Operator (See GC0048 and GC
Constant Alternator terminal voltage control
Capability required but functionality adjustable depending upon application and agreed with Network Operator – see GC0048 at link above
Active Power Recovery
See GC0100 – A minimum of 90% Active Power to be restored within 0.5 seconds would be required
Power Park Modules
0.95 PF lead to 0.95 PF lag at Connection Point unless otherwise specified by NGET or Network Operator (See GC0048 and GC0101 at link above)
Fast Fault Current Injection
See GC0100 – two Options Proposed

16. Compliance – Type B
Under RfG (Article 32), the Type B (and Type C) Compliance Process requires submission of a PGMD (Power Generating Module Document)
Evidence of co-ordination of Protection and Control Settings
Itemised Statement of Compliance
Detailed Technical data of the PGM as required by the Relevant System Operator
Manufacturers’ data and/or equipment certificates where they are relied on as evidence of compliance
Compliance Reports demonstrating steady state and dynamic performance as required by Chapters 2, 3 and 4 of Title IV including actual measured values
Studies demonstrating steady state and dynamic performance as required as required by Chapters 5, 6 or 7 of Title IV to the level of detail required by the Relevant System Operator
The Relevant System Operator on acceptance of a complete and adequate PGMD shall issue a Final Operational Notice (FON) to the Power Generating Facility Owner.

17. Type B Synchronous Compliance Tests
LFSM – O – can be done as factory tests or on site by injecting the control system (Art )
G99 protection requirements – normally done on site – but compliance could be done by manufacturers, with minimum trip testing on site
The above tests will be specified in G99 (and the G Code)
Simulations
LFSM – O –simulation models to be validated against the test above (Art 51.1 and 51.2)
FRT – simulation model to be validated against tests (either manufacturers’ or site) (Art and Art 51.3)
The above simulations will be specified in G99 (and the G Code)
Information, including type testing information etc from manufacturers will also be specified in G99 (Art 32.2)

18. Type B PPM Compliance Tests
LFSM – O – can be done as factory tests or on site by injecting the control system (Art 47)
G99 protection requirements – normally done on site but compliance could be done by manufacturers, with minimum trip testing on site
The above tests will be specified in G99 (and the G Code)
Simulations
LFSM – O –simulation models to be validated against the test above (Art 54.2)
FRT – simulation model to be validated against tests (either manufacturers’ or site) (Art , Art 43.3)
FFCI – (Art 54.3)
Post Fault Active Power Recovery (Art 54.5)
The above simulations will be specified in G99 (and the G Code)
Information, including type testing information etc from manufacturers will also be specified in G99 (Art 32.2)

19. Type C

20. Type C Power Generating Module Requirements
Note that all the Type A & B requirements will be required for Type C too.
Requirement
Proposed GB Parameters
Active Power Setpoint
Covered by GC0087 and GC0101 Workgroups – see
Limited Frequency Sensitive Mode Under Frequency LFSM_U
Proposed settings addressed as part of GC0087 and GC0101 Workgroups – see link above
Frequency Sensitive Operation
Monitoring
Will be covered by GC0102 System Management Workgroup
Robustness
System Restoration / Black Start
Proposed settings addressed as part of GC0087 and GC0101 Workgroups - see link above
Simulation Models
current GB practice anticipated to apply - will be covered by GC0102 System Management Workgroup – Note the Compliance process requires simulation models for Type B and above
Rate of change of Active Power
Neutral Point Earthing

21. Type C SPGM and PPM Requirements
Proposed GB Parameters
Synchronous
Enhanced Reactive Capability
0.92 PF lead to 0.92 PF lag at Connection Point (See GC0048 and GC0101) see
Power Park Modules
0.95 PF lead to 0.95 PF lag at Connection Point unless (See GC0048 and GC100) see link above
Control Performance
Voltage Control proposed – (See GC0048 and GC0101) see link above
Priority for reactive or active power during faults
Covered as part of Fault Ride Through GC0100 Consultation see
Power Oscillation Damping
Covered as part of Fault Ride Through GC0100 Consultation

22. Compliance – Type C
Under RfG, the (Type B and) Type C Compliance Process requires submission of a PGMD (Power Generating Module Document)
Evidence of co-ordination of Protection and Control Settings
Itemised Statement of Compliance
Detailed Technical data of the PGM as required by the Relevant Network Operator
Manufacturers’ data and/or equipment certificates where they are relied on as evidence of compliance
Compliance Reports demonstrating steady state and dynamic performance as required by Chapters 2, 3 and 4 of Title IV including actual measured values
Studies demonstrating steady state and dynamic performance as required as required by Chapters 5, 6 or 7 of Title IV to the level of detail required by the System Operator
The Relevant System Operator on acceptance of a complete and adequate PGMD shall issue a FON to the Power Generating Facility Owner.
For Type C Power Generating Modules – Simulation Models are required as defined under Art 15(6)

23. Type C – Testing As for Type B, plus: Synchronous Tests
LFSM – U - can be done on site by injecting the control system (Art 45.2)
FSM - can be done on site by injecting the control system (Art 45.3)
Reactive Power Capability – can be tested on site (Art 45.7)
Power Park Modules Tests
Active Power Controllability – can be done on site (Art 48.2)
LFSM – U – can be done on site (Art 48.3)
FSM – can be done on site (Art 48.4)
Reactive power capability – can be tested on site (Art 48.6)
Voltage Control, Reactive Power Control or Power Factor Control (System Operator to determine) - can be done on site – Art 48.7 – 48.9

24. Type C – Simulation As for Type B, plus: Synchronous - Simulations
LFSM – U (Art 52.2)
FSM (Art 52.3)
Reactive Power Capability (Art 52.5)
Power Park Modules - Simulations
LFSM – U (Art 55.2)
FSM (Art 55.3)
Reactive Power Capability (Art 55.6)
Power Oscillation Damping (Art 55.7)

25. Compliance Documentation

26. Power Generating Module Documents
The RfG requires a PGMD for all Type B and C.
In GB the concept will also be applied to Type A – although the RfG calls this an Installation Document
The ID will call for evidence (ie references) of Equipment Certificates or manufacturers type testing information
Type A and B will need to produce information in the format already in use in G83 and G59 – although of course updated to reflect new RfG technical and administrative requirements in G98 and G99.
T connected generators already produce relevant compliance data in a structured format for NGET – in GC in the Grid Code – User Data File Structure provided by NGET (UDFS)
Embedded Type C will probably need something similar to the NGET approach, although a subset of it – to be documented in G99.
In other words the ID or PGM will be specified in G98 and G99 for D connected Type A to C

27. Implementation Challenges

28. Type A
RfG prominently expects Equipment Certificates to be used for mass market generating modules
No clear route for manufacturers to set up an Equipment Certificate regime.
ENTSO-e have suggested via the European Stakeholder Committee that national solutions should be found to ensuring compliance
Art 30.2(g) allows for manufacturers’ compliance information in a form other than Equipment Certificates
Key compliance requirements for Type A are the frequency range capabilities, LFSM-O characteristic and G98/G99 protection requirements.
These will be specified in G98/G99 much as the protection requirements currently are in G59/G83

29. Compliance – Type B and C
Under RfG (Article 32), the Type B (and Type C) Compliance Process requires submission of a PGMD (Power Generating Module Document)
Evidence of co-ordination of Protection and Control Settings
Itemised Statement of Compliance
Detailed Technical data of the PGM as required by the Relevant Network Operator
Manufacturers’ data and/or equipment certificates where they are relied on as evidence of compliance
Compliance Reports demonstrating steady state and dynamic performance as required by Chapters 2, 3 and 4 of Title IV including actual measured values
Studies demonstrating steady state and dynamic performance as required by Chapters 5, 6 or 7 of Title IV to the level of detail required by the System Operator
The Relevant System Operator on acceptance of a complete and adequate PGMD shall issue a FON to the Power Generating Facility Owner.
Note Art 15(6(c)) requires submission of Simulation models for Type C and above yet the Compliance process requires the results from simulation models for Type B and above.

30. Examples of current process

31. Transmission Connected

32. Current Compliance Process
Users self certify compliance with the relevant requirements
Compliance Statement
Signed Compliance Frontsheet
Evidence review and tests
Licence Condition C14.
National Grid confirms compliance has been achieved by a check of the evidence provided.
Process is coordinated by Connection Compliance team who issue the Operational Notifications

33. Grid Code Compliance applies to…..
All Large and Medium Power Stations in Great Britain
10MW in SHETL, 30MW in SP and 50MW in E&W
All Offshore Transmission Systems
All generation technologies
Coal
Oil
Gas
CHP
Wind
Wave
Biomass
HVDC
Others

34. Recent Combine Cycle timeline Large Power Station >100MW in E&W
Pre–Connect
ION issue
FON
Signed Connection Agreement with Final Completion Date but actual first Synch Mar 2016
1st Compliance meeting
1st UDFS submission
Final UDFS submission
O/C Voltage Control test
Witness tests first visit AVR / PSS
Witness tests final visit Governor
FON anticipated Summer 2017
April 2008
April 2015
May 2012
May 13
Jan 16
Feb 16
23rd Mar 16
25th May 16
8th Aug 16
- 6yrs* 0*
-35 months*
-23 months*
-2 months
-1 month
+2 months
+5 months
+1 year

35. Recent windfarm timeline - Large PS between 50MW and 100MW in Scotland
Pre–Connect
ION issue
FON
Signed Connection Agreement with Final Completion Date
1st Compliance meeting
1st UFDS submission
4th & final UDFS submission
20% Voltage Control test
20% Operational restriction lifted
Preliminary frequency response tests
Witness tests first attempt
Reactive capability tests completed
VC & FR witness tests passed
FON anticipated Summer 2017
March 2006
Sept 16
June 15
Jan 16
July 16
August 16
1st Sept 16
5th Sept 16
9th Sept 16
9th Nov 16
16th Nov 16
5th Jan 17
11th Jan 17
-10.5yrs
-15 months
- 8 months
-2 months
-1 month
+2 months
+4 months
+1 year

36. Compliance Process
Signing a Connection Agreement starts the Compliance Process
Connection compliance will manage a multi-discipline team to work with the customer
The Team will include a Compliance Engineer responsible for technical assessment of the generator’s plant
The Compliance Engineer will work with the Generator and where applicable the Contractor to ensure compliance is demonstrated.

37. Operational Notifications
An Operational Notification (Op Not) is a formal notice that a party may connect to the NETS for the purpose of taking demand or export power.
NGET issues Operational Notifications in its capacity as National Electricity Transmission System Operator.
Energisation Operational Notification (EON)
Issued once demonstrating all necessary pre-connection requirements to allow connection and energisation of assets to the transmission system.
Interim Operational Notification (ION)
Issued once demonstrated that it has fulfilled all necessary pre-synchronisation requirements to allow the plant to synchronise to, and use, the NETS for the export of power or dynamic reactive power.
Includes a Schedule of Unresolved Compliance Issues which will need to be satisfied following synchronisation.
Final Operational Notification (FON)
Issued once to satisfactorily demonstrated that all items identified in the Schedule of Unresolved Compliance Issues on an ION are concluded.

38. Pre-Connection Compliance Process – Before ION
Signed Agreement to Connect
Compliance mgts Submission of: Data/Models &
simulations
Permission to Connect Power Plant (ION)
Typically 1 – 3 years

39. Post Connection Compliance Process – After ION
Signed Agreement to Connect
Permission to Connect Power Plant
Typically 1 – 3 years
Power Plant deemed Compliant
Owner Commissions Plant
&
Completes Compliance Tests
Permission to Connect Power Plant (ION)
Typically 6 – 18 months
Compliance mtgs Submission of: Data/Models &
simulations

40. Distribution Connected Types A to C

41. Development of Approach
The following slides suggest high level approaches to be taken
Details are open for discussion and agreement
Key principles are to look for the most efficient implementation that complies with new and existing legal requirements
Aim is to get approach completed, documented and approved by May 18. That provides one year to make essential refinements before compliance is required in May 19.
Type D to follow very closely approach for Type C – this is our current working assumption – although an option would be to refer all Type D connexions to the Grid Code for technical requirements.

42. Type A – Article 30 – Content of the Installation Document
Connection location
Date of the Connection
The maximum capacity of the installation (kW)
Type of primary energy source
Is the technology an “Emerging Technology”
Reference to Equipment Certificates issued by the authorised certifier, or manufacturers’ equivalent references
Additional information received requested by the Relevant System Operator which has not been covered by the Equipment Certificate
Contact details of the Power Generating Facility Owner and their signatures

43. Type A LV connected
Manufacturer will complete tests as specified in EN50438 and/or G98
Information etc will be lodged with the ENA
Existing process:
If <16A per phase, installer completes the installation and notifies the DNO
If multiple units <16A in aggregate or <50kW type tested:
Customer/installer applies to DNO (Application form - includes type test reference)
DNO makes connexion offer etc
Customer accepts and then installs the unit(s)
Customer/installer confirms installed data to DNO using Installation Document and Site Summary Form

44. Type A LV connected Suggested process:
As currently but with one overall form with Staged sections for completion and sign off by Customer throughout duration of generator lifetime
STAGE 1 Standard Application Form (includes type tested reference)
STAGE 2 Installation Document
STAGE 3 Site Summary Form
STAGE 4 Modification Notification
STAGE 5 Decommissioning Notification
Stages 1, 2 & 3 in general can be combined into a single document

45. Type A not type tested and/or not LV connected
Suggested process:
STAGE 1 Standard Application Form
STAGE 2 Agreement of Installation and Commissioning Tests (as documented in G99 and/or EN50438 and/or TS (dependent on connexion voltage); agreement of commissioning arrangements and DNO will confirm if they are to be witnessed or not
STAGE 3 Installation Document (confirmation of commission tests and information)
STAGE 4 Site Summary Form
STAGE 5 Modification Notification
STAGE 6 Decommissioning Notification
Stage 1-4 can probably be combined in a single document

46. Type B and C Very like non-type-tested Type A
Customer will apply for connexion on standard application form – which can form part of the PGMD
Customer and installer will need to undertake the DNO tests as documented in G99 and/or TS 50549
DNO and customer will agree commissioning arrangements and DNO will confirm if they are to be witnessed or not
Commissioning tests undertaken and all information confirmed on PGMD
DNO will issue a Final Operational Notification to the customer

47. Discussion and next steps

48. Next Steps Continue to work up the detail in appropriate GC WGs
Decide approach to embedded Type D
Understand the opportunities for Equipment Certificates that might be opened up by the publication of EN (parts 1, 2 and 10).

49. Contact Details National Grid DNOs
Ian Nuttall
Tony Johnson
Franklin Roderick
DNOs
Mike Kay
David Spillett
Sarah Carter

50. GCRP and DRCP Working Groups
Freq Response
RfG
HVDC
DCC
TSOG
GC0087
GC0048
GC0090
GC0091
GC0095
System Operations
Previous
GCRP WG
Current
Joint WG
GC0096
GC0095
GC0097
GC0100
GC0101
GC0102
Storage
TERRE
GC0079
FRT
FFCI
Banding
Voltage
Reactive
Freq Requirements
Compliance
System Management
Op Metering etc
RoCoF

51. Process for joining WGs
Grid Code
Basic criteria for WG members are laid out in the Grid Code Governance Rules (part of the Grid Code) – GR.20.3.
A WG member needs to be nominated by a Grid Code User or by a GCRP member
The Grid Code administrator will provide a nomination form on request:
Distribution Code
Traditionally open to any party who can claim a reasonable interest in the subject matter
Membership arranged via any of:
DCRP members
WG Chairman
DCRP Secretary
DCRP Code Administrator