Energy Energy Networks. Networks Association. Association. Insert presentation title here. The Voice of the Networks

Transcription

1 The Voice of the Networks Energy Energy Networks Networks Association Association Open Networks Project Workstream 1 Product 12 (Update Section 12.3) Insert presentation title here Name Position Date

2 Context Product 12.3 is aimed at a review of ongoing enforcement of existing requirements for data exchange primarily between DERs and DNOs. The scope of his section includes for: a). review of existing Code requirements for DER data exchange. b). Understand how each DNO & SO manages/requests DER data and enforces compliance. c). Understand DNO/IDNO data exchange requirements. d). Understand how enforcement for non-compliance between DNOs and TO is achieved. e). Determine if DER size is relevant and affects data requirements. 2 The Voice of the Networks

3 Product Questionnaire Purpose: Part of the scope of Product 12 seeks to review and potentially propose new processes and requirements for planning data sharing between SO- DNOs-DERs. As such the questionnaire is aimed at trying to gain an understanding of current practices in each DNO area, to gather learning for potential inclusion in Product proposals. Audience: We envisage the questionnaire to be answered by a combination of Connections, Customer Service and Asset Management personnel depending on each DNO structure. Key definitions: We define DER to include generation and storage. Data includes, technical and Ownership/Operational details. 3 The Voice of the Networks

4 Main findings summary Majority of DNO s have a consistent approach in terms of their requirements for minimum information as part of a compliant application (see slide 6 for detail). Overall the view was that data presently provided at application stage is sufficient for initial planning/design purposes, although there was concern over the general standard/quality of technical data sometimes provided (e.g. fault level infeed data). Most DNO s concentrate on provision of all relevant data (see slide 14 for detail) before connections are energised. However data gaps can appear where there is conflict between completion of the data gathering exercise and where customer service compliance issues arise (e.g. connection/energisation deadlines). Especially the case where there are high volumes of connections. Consensus from questionnaire was that most (but not all) DNO s have limited or no data exchange with DER s (& IDNO s) following energisation of the connection. Future smart network operation will require improved more regular data exchange mechanisms between DNO s, DER s & IDNO s While not a direct feedback from the questionnaire, discussions around this Product have highlighted potential for overlap or linkage with other work that is ongoing. Theses include GC 0106, GC 0117 and WS2 Product 6 (Guidance on Post Connection Changes) 4 The Voice of the Networks

5 Q1 Purpose: We would like to understand current requirements on data exchanges Q1.1 Could you outline the data required from DER and IDNOs and the process followed by you to gather this information. A. Apply for connection B. After commissioning. A. Apply for connection Summary of responses Most DNO's require the following at time of application: 1. ENA form (and supplementary form if required) 2. Single Line diagram (SLD) 3. Site location plan 4. Landowner consent 5. Fault level infeed 6. Capacity (Export/Import) For demand applications there may be additional/different information depending upon what's being installed. There is a general view that the information provided at application stage is quite often sketchy, often to a poor standard and subject to change. Many DNO's comment that they require further detailed information before energisation. 5 The Voice of the Networks

6 Supplementary comments following further review of responses to the question - what is minimum information? Most DNO s consider minimum information for a compliant application for a metered quotation to be as per the requirements of SLC15A section 3.48 which includes: i. Customer name and address ii. iii. iv. Site address Site plans to indicate site boundary and layout of site including proposed location of substation(s) Proposed metering point (s) location v. Suitable letter of authority vi. vii. viii. ix. Date connection required Maximum capacity (kva) and each metering point to be connected Technical details of any electricity generator that is required to operate in parallel with the supply Technical details of any customer owned equipment that is likely to cause disturbance to the electricity supply. In addition to the above minimum information most DNO s also require the application to include a reasonable indication of the fault level infeed from a DER. Not really possible to determine from responses how hard this is pushed for by DNOs. One DNO specified that it requested Standard Planning Data as per the DCode at application stage which in addition to the above SLC15A requirements could be deemed as a requirement for a higher level of technical data. Is there a need for consideration that DCode Standard Planning Data is the absolute minimum information requirements at application for quotation stage,as a means of plugging data gaps? 6 The Voice of the Networks

7 Q1 Purpose: We would like to understand current requirements on data exchanges (cont d) Q1.1 B. After Commissioning Summary of responses A number of DNO's comment that the complete suite of detailed information is required prior to energisation and if this is incomplete it would delay energisation. There were mixed comments as to whether 'as built or as laid' plans and final SLD's are required before or after commissioning. One DNO always installs a power quality monitor following commissioning and one states there is no after commissioning process. Product group comment - maybe some confusion in responses as to whether energisation and commissioning are the same thing? 7 The Voice of the Networks

8 Q1 Purpose: We would like to understand current requirements on data exchanges (cont d) Q1.2 How do you enforce data provision from DERs and IDNOs A. before connection B. After commissioning A. Before connection Summary of responses Most DNO's will not 'start the clock' or deem application competent/compliant until minimum information is supplied. Some require 'all' data but there is no explanation or clear detail of exactly what 'all' data means. One DNO will assist the customer if they are struggling with relevant data (assume this to be electrical data) offering to use library or assumed values - although this is subject to accurate information being provided before energisation. If this impacts upon the connection cost this will be borne by the customer. B. After commissioning Summary of responses It seems common practice to ensure all data is received before energisation, otherwise energisation may be delayed. Therefore limited need for enforcement post energisation/commissioning, although some DNOs would accept 'as built' drawings post commissioning/energisation. Limited comment about enforcement with IDNOs. 8 The Voice of the Networks

9 Q1 Purpose: We would like to understand current requirements on data exchanges (cont d) Q1.3 How often do you request/receive updates on the data required from DER and IDNOs after commissioning? The DCode States the following: DDRC5.4.4 It is a requirement of the Distribution Planning and Connection Code that Registered Project Planning Data is updated by the User annually Summary of responses Responses to this question show a range of approaches. One DNO has set up a team to annually review Connection Agreements and confirm compliance. Another requests IDNO data for Wk24 submission for generators >5MW, while others have no set process for requesting updates, but rely upon the IDNO or DER initiating an update following changes to their installation. 9 The Voice of the Networks

10 Q1 Purpose: We would like to understand current requirements on data exchanges (cont d) Q1.4 Do you have granular data monitoring for each DER/IDNO site? Please state if this varies per Voltage level Summary of responses Granular data seems to be more available for sites connected at EHV & 132kV primarily via SCADA systems, which at the least provides half hourly averaging of amps and volts. Some systems include for full measurement of MW & Mvar. SCADA capabilities are less prevalent at 11kV (& LV) with data mainly being available from half hourly metering. A number of DNOs require permanent power quality monitoring at DER sites. 10 The Voice of the Networks

11 Q1 Purpose: We would like to understand current requirements on data exchanges (cont d) Q1.5 Do you request an annual data exchange with the IDNO above any requirements specified in the DCUSA, the Bilateral Connection Agreement or the Distribution Code? Summary of responses Majority of DNOs do not request or carry out an annual data exchange with the IDNO. However one DNO does annually request a load projection from all demand EDCM customers. 11 The Voice of the Networks

12 Q2 Purpose: We would like to understand what happens in the event of non-compliance of the required data outlined in Q1.1 Q2. Please outline the process followed in the event of non-compliance of the required data outlined in Q1.1 Summary of Responses Majority of DNO's would not deem an application compliant if minimum information is not provided and would not start the clock. If an application is compliant but further detailed information is required before energisation, and this is not provided, then non-compliance at this stage would result in a delay to final commissioning and energisation. Therefore non-compliance in most instances (where related to new connections) would result in a practical and potentially commercial/financial implication for the customer. 12 The Voice of the Networks

13 Q3 Purpose: We would like to understand if the data required and compliance is dependent on the DER/IDNOs connection capacity above and beyond G59 and G83 Q3.1 Could you outline the data required from DER in the following instances and if this data varies per capacity requested/installed. A). Upon application for connection B). After commissioning A). Upon application for connection Summary of responses Responses primarily considered difference in size for generation DERs with the split around whether G59 or G83 documentation is applicable. For G59 connections all information being required before energisation. B). After commissioning Summary of responses Most DNO's following commissioning look for confirmation of actual size of equipment installed as very often this can be different to initial application. It would be expected that generally this would be a reduction rather than an increase. 13 The Voice of the Networks

14 Supplementary comments following further review of responses to the question - what is all information Questionnaire responses showed that it was common practice for DNO s to require that all data was required before energisation; the definition of all data was unclear. However the inference is that it includes confirmation of the data originally submitted at application stage plus any amendments that may have taken place as project progresses towards energisation. The DER also has to show compliance with G59 (where appropriate), and that PQ and stability assessments (where necessary) have been completed. There was consideration also of the data required for completing Connection Agreements. Therefore a further definition of all data includes the following: i. A completed ENA application form or DNO demand data sheets ii. customer details iii. consultant details iv. import and export capacities v. Confirmed fault level infeed data (fault level data for individual machine, generation type and machine parameters, transformer data) vi. single line diagram vii. location plan with co-ordinates for sub-station viii. land owner consent letter. ix. Connection date x. G59 certificates xi. PQ pre-commissioning reports (G5/4, P28, Stability analysis (if required)) xii. Site operational contact data for completion of Connection Agreement. Overall the view from comments received was that the data presently asked for was sufficient for planning needs, although it is clear that there is concern over the standard of technical data received. Often where customer service issues come to the fore this can take priority over completion of the data gathering process, which can lead to data gaps which are difficult to address following energisation. For generation DERs the introduction of G99 may help address these issues although there is no equivalent for demand DERs. 14 The Voice of the Networks

15 Q3 Purpose: We would like to understand if the data required and compliance is dependent on the DER/IDNOs connection capacity above and beyond G59 and G83 (cont d) Q3.2 What current reporting procedures do you follow for individual sites Summary of responses Of the information provided there was a mixed response. There is some confusion over the context of the question. However other responses included for recording of information internally but seems to be limited structure around how and when data is reported. Q3.3 Do you believe that current G59 and G83 data requirements for different size DER is sufficient for planning/operating the network? If not, please state what changes would you suggest (Note: There will be a new version of these codes as G98 and G99, we will check if your suggestion has already been implemented in these versions) Summary of responses Overall view is that data presently asked for is sufficient/reasonable for planning purposes. Although concern has been raised over the quality of data provided at times and that there is some ambiguity over fault level contribution from inverter based technologies. Little information was received/provided about operational practices. This information is likely to become more critical as the move towards DSO type networks progresses. 15 The Voice of the Networks

16 Supplementary comments regarding data presently provided and is this sufficient for future operation of the network As mentioned in previous slides, overall view was that the data presently provided by DER s is sufficient for planning purposes. However there is concern over the quality of data, and that data gaps can appear where there is conflict between completion of the data gathering process and where customer service compliance issues arise. This is especially so where there are high volume connections at the lower capacities, which can move the focus away for ensuring all necessary data relating to the connection is available. Presently the network is designed to give a high degree of operational freedom to the customer - generally they can use their demand and generating equipment without any restrictions. No operational timescale or planning data is required as the ability to operate across their operating range is considered at the application design stage. Future network operation will require accurate understanding of DER operational practices and commercial markets as the need to meet/balance network requirements at DNO level is increased. There will be an increased need for as close to real time operational data as possible and forecast data. Presently the data exchange between DNO s and DER s and DNO s and IDNO s tends to be primarily at application stage and lead up to energisation with very limited data interaction following energisation. Mechanisms will need to be considered and fully understood to address this for future smart network operation. 16 The Voice of the Networks