THEME [ENERGY.2012.7.1.1] Integration of Variable Distributed Resources in Distribution Networks (Deliverable 6.1) Guidelines for validation activities Lead Beneficiary: EDP Distribuição
1 Contents 1 Contents... 2 2 List of tables... 3 3 List of abbreviations... 4 4 Authors... 5 5 Introduction... 7 6 Requirements for the demonstration... 8 6.1 SF1- Load forecast... 8 6.2 SF2- RE forecast... 10 6.3 SF3- State estimation... 12 6.4 SF4 Voltage control... 14 6.5 SF5 Technical Virtual Power Plant... 16 6.6 SF9 Advanced Protection Systems... 19 7 Conclusions... 21
2 List of tables Table 6.1 Functional specifications for SF1 software interface.... 9 Table 6.2 - Functional specifications for SF2 software interface... 11 Table 6.3 Functional specifications for SF3 software interface... 13 Table 6.4 Functional specifications for SF4 software interface... 15 Table 6.5 Methodology for validation of SF5... 18 Table 6.6 Methodology for validation of SF9... 20
3 List of abbreviations DER- distributed energy resources MV- medium voltage LV- low voltage GUI- graphical user interface
4 Authors Name E-mail Partner Diogo Alves Lopes diogo.alveslopes@edp.pt EDP Distribuição Pedro Godinho Matos pedro.godinhomatos@edp.pt EDP Distribuição Aires Messias aires.messias@edp.pt EDP Distribuição Ana Carina Morais Anacarina.morai@edp.pt EDP Distribuição Pedro Gama pedro.gama@edp.pt EDP Distribuição Miguel Louro miguel.louro@edp.pt EDP Distribuição Cláudio Mesquita claudioosorio.mesquita@edp.pt EDP Distribuição Ricardo Prata ricardo.prata@edp.pt EDP Distribuição Huilian Liao huilian.liao@manchester.ac.uk University of Manchester Ricardo Bessa ricardo.j.bessa@inescporto.pt INESC Porto Jorge Pereira jpereira@inescporto.pt INESC Porto André Madureira andre.g.madureira@inescporto.pt INESC Porto Nuno Silva nuno.silva@efacec.com EFACEC Access: Project Consortium European Commission Public x
Status: Draft version Submission for approval x Final version
5 Introduction The following functionalities will be validated in the test site: SF1- Load forecast; SF2- Renewable energy forecast; SF3- State estimation; SF4- Voltage control; SF5 Technical Virtual Power Plant; SF9 Advanced Protection Planning. Most of these functionalities will comprise installation of equipment, software development, and measurements collection from the network within a certain refresh rate that can range from close to real time (every 15 minutes) to a daily value. The variety of measurements collected, amount and refresh rate depend on the requirements of each of the functionalities and the smart meter infrastructure that is installed in each of the specific locations chosen for demonstration, within the geographical location of test site. The purpose of this document is to describe the requirements for the demonstration: For SF1, SF2, SF3, SF4, the final output of the demonstration will consist of a software interface built according to functional specifications defined in this document. It is also important to mention that for these functionalities, additional equipment in the network will be installed in order to assure the necessary conditions for testing. Deliverable D6.2 will describe these details along with the demonstration architecture, networks for validation (within the chosen test site), and communication specifications. For SF5 and SF9 the validation will consist of a methodology that is also described in this document, along with several simulations and data analysis. For further detail regarding the technical detail of the functionalities, the following deliverables can be consulted: D2.3, D3.1, D3.2, D3.3, D3.4, D3.5 and D4.3.
6 Requirements for the demonstration This section describes in detail the guidelines and specifications for the validation of each one of the functionalities. 6.1 SF1- Load forecast This demonstration will consist on the development of an application with the characteristics displayed in Table 6.1. This functionality will require collecting values from secondary substation in a close to real time basis. The software tool uses the algorithm developed according to the Sustainable methodology (Deliverable 3.1). Requirement ID SF1_1 Description The application will be able to perform the functionalities of learning and validation, which will be executed based on historical data of 2 months. This is a necessary procedure before performing prediction. The application will include a chart that demonstrates load. This chart will contain three data series: SF1_2 One data series with the real load value (active power, MW) on the primary substation (on the medium voltage side); One data series with the one-day-ahead forecasted load value (active power, MW) on the primary substation (on the medium voltage side); One data series with the half-hour-ahead forecasted load value (active power, MW) on the primary substation (on the medium voltage side); The GUI application will offer the possibility to customize: The maximum time horizon of the forecast (with a 24 hours limit).
The GUI will adapt accordingly to these modifications. There will also be the possibility to customize the time axis (by default it will be equivalent to the forecast update) to one of the following possibilities: Last Days/week; Last month; show probabilistic forecast (on/off); SF1_3 SF1_4 SF1_5 The application will include a bar chart that indicates, for each x-axis unit, the forecast error according to forecasting accuracy KPIs defined in D2.4 (level 4 KPIs-forecast improvement defined in section 5.9). The application will be able to retrieve data from a FTP server created to store real data collected from the network. The refresh rate of the data will be between 30 and 60 minutes. It will also incorporate weather data from a different source. The application will also store all the historical values during the simulation: Forecasted values for all time horizons; Real values for all time horizons; Error metrics (KPIs) for all time horizons (the application will have the possibility to display these KPIs for a specific period, customizable by the user). The user will have the possibility to consult these historical values.. SF1_6 All the customizations mentioned in SF1_1-and SF1_2 will apply to both charts. Table 6.1 Functional specifications for SF1 software interface.
6.2 SF2- RE forecast This functionality will require collecting values from LV photovoltaic generation close to real-time. These measurements will be the input of a software tool that uses the algorithm developed according to the Sustainable methodology (Deliverable 3.2), will perform forecasts for each LV photovoltaic generation micro-generation units and its secondary substation. The functional requirements of the application are described in Table 6.2. Requirement ID Description The application shall include a plot that contains the following time series: SF2_1 Actual solar generation in each secondary substation/lv solar photovoltaic generation unit; Point forecast of solar generation for each secondary substation/ LV photovoltaic generation unit; Probabilistic forecast (i.e., set of quantiles) for each secondary substation/ LV photovoltaic generation unit. The GUI application will offer the possibility to customize: SF2_2 The maximum time horizon of the forecast (with a 60 hours limit). The GUI will adapt accordingly to these modifications. There will also be the possibility to choose between real-time and historical forecasts. Also, it will be possible to select the forecast target. By default the presented values will include secondary substations in Évora s with solar micro-generation. The user will be able to indicate a specific secondary substation for the forecast, by selecting a secondary substation name from a predefined list in a combo box format. The effects of all the filters will be applied to all time series.
The application shall include a bar chart that indicates, for each x-axis unit, the forecast error according to the KPI defined in D2.4. The following metrics shall be depicted: SF2_3 Normalized Mean Absolute Error Point Forecast; Normalized Root Mean Square Error Point Forecast; Calibration Probabilistic forecast; Sharpness Probabilistic forecast; Continuous Ranking Probability Score (CRPS) Probabilistic forecast; Improvement over a reference model Point and Probabilistic forecast; The application will be able to retrieve data from a webserver created to SF2_4 store real data collected from the LV photovoltaic generation unit. The refresh rate of the date will be defined according to the forecast update and it will have a minimum value of 5 minutes and a maximum of 60 minutes. The application will also store all historical data during the simulation: SF2_5 SF2_6 Forecast values for all time horizons; Real values for all time horizons; Error metrics for all time horizons. Historical data must be available to end user. All the customizations mentioned in SF2_1-and SF2_2 will apply to both charts. Table 6.2 - Functional specifications for SF2 software interface
6.3 SF3- State estimation This functionality will benefit from the installation of an SSC in a primary substation that will collect real data from MV network and perform the state estimation algorithm. The final output of the demonstration will consist of an application with the characteristics displayed in Table 6.3. Requirement ID Description The software will display the MV feeder under analysis, including: SF3_1 All the MV/LV nodes (secondary substations); The display should allow easy distinction between: o Secondary substations whose measurements are being collected from the network in near real time; o Secondary substations with pseudo measurements, generated with the help of the LV meters (by the autoencoder/aann). Within this study, a particular substation is going to be selected for this specific purpose. A schematic representation of the LV nodes from where the measurements are being collected in a near real time basis. A schematic representation of the LV nodes that provide only D-1 measurements that are being used for training the generation of pseudo measurements. For each of these nodes, the following values will be displayed: Active power values (P); Reactive power values (Q); Voltage magnitude values (V). By default, the SE algorithm will run at cyclically every 15 minutes. The SF3_2 application will allow the user to change the refresh rate of the algorithm. The user will also have the possibility to:
Manually run the state estimator at any time. Enable/disable the autorun. When a new state estimator run is activated, a communication failure can be simulated between the SSC and the secondary substation selected with the aim of using pseudo-measurement values generated based on LV values. After each SE run, the application will display the values obtained through the state estimator: SF3_3 Voltage magnitudes and phase angles at all nodes. Active and reactive injected power at each generation and load node. Active and reactive power flows at both sides of each line and transformer. Current flows at both sides of each line, transformer, and switch. Detection and removal of bad and conflicting data. Whenever a real measurement is available, the application will display these values. SF3_4 The application will have the ability to communicate with the secondary substation controllers installed on the field and these will serve as data sources The application will also store all the historical values during the simulation (i.e., the list of all simulations), for later analysis including: SF3_5 Date and time of the simulation; Network values o Pseudo measurements; o Real measurements; o Virtual measurements; o Estimated values; o State estimation accuracy The application should allow exporting the historical values into.csv format for further analysis. Table 6.3 Functional specifications for SF3 software interface
6.4 SF4 Voltage control The proof of concept of local voltage control will involve installing a complete solution of DER in the test site. Table 6.4 specifies the requirements for the proof of concept. Requirement ID Description The application will display the network s geographical scheme that will contain the customer s sites that are being monitored and included in the demonstration. For each site, the following values should be displayed: SF4_1 Voltage. Active power (consumption) average value based on collected energy values collected from smart meters. For the customers that also have generation installed, the installed capacity should also be displayed. Transformer Power and voltage will also be displayed. The application will also display EDP s owned sites that contain the DER (solar panels and batteries). For each one of these sites, the following values should be displayed: SF4_2 Active power production for each of the meter-controlled solar installation. Active power production/ consumption for each battery metercontrolled battery pack, indicating whether they re charging or discharging. The sites that are owned by EDP should be identified and highlighted allowing the user to easily identify them. The application will generate an event every time a set point is sent from a SF4_3 DTC to a DER. The user will be alerted trough a message/alarm, indicating the event registration: Each event must contain the following information:
Event number; Timestamp (date and time); Setpoint type (battery charging or discharging, PV active power increase or decrease); Setpoint value. SF4_4 The application will provide the possibility for the user to consult these events, searching by each one of its attributes. The application should store 6 months of historical data, storing all the values SF4_5 indicated in SF4_1, SF4_2, and SF4_3. It must allow the user to consult, search, and export these values in to a spreadsheet. SF4_6 The application should allow modification of the reference value for voltage and voltage deviation limits that are applied in the voltage control algorithm. SF4_7 The tool should provide all the necessary data for the calculation of KPIs defined in deliverable D2.4. It will provide the possibility to export the data for further analyzing (into.csv file format). Table 6.4 Functional specifications for SF4 software interface
6.5 SF5 Technical Virtual Power Plant In Portuguese legislation, there is no regulatory scope to send customers set points for load reduction or increase, except in specific situations: Portuguese regulatory framework includes the possibility of costumers volunteer themselves to have part of their peak load interrupted, if requested by the TSO, in situations where that interruption is necessary for system stability purposes. Under that situation, they have an interruptible contract, which provides a discount. The minimum peak power eligible for that scheme is 4 MW. Regarding wind farms, Portuguese legislation allows for wind farms to increase their installed capacity by 20% above the hosting capacity requested for their point of common coupling with the network, without altering their peak power delivered to the grid. In effect, that rule allowed to increase the energy delivered through the curtailment of the peak power that those wind farms produce). For this reason, SF5 demonstration will consist of a methodology that comprises customer surveys and simulations: EDPD will promote meetings with 1 or more customers with the characteristics specified in SF5_1. The information collected in the meeting will serve as an input to the TVPP simulations. The purpose is to try to assess if the participation of the customers in flexibility services could help optimize distribution network parameters. The methodology is described in Table 6.5. Requirement ID Description One or more customers will be selected to participate in this study. The target customers have the following characteristics: SF5_1 Significant amount of peak demand and contracted power values, having into the account the characteristics of the network that they are connected to.
Customers that, due to the nature of their business process, have the availability to shift a significate amount of consumption between several periods of the day. This implies that selected customer(s) is/are located in the MV network. EDPD will promote physical meetings with the customer(s) in order to try to assess the feasibility of the participation of the customer in the provision of services to the DSO (e.g., by stablishing a commercial agreement with a market operator such as an aggregator/vpp). In the meeting, the following information will be determined: SF5_2 How much consumption can be shifted (W) and for how many time (Wh); What are the hourly periods where consumption can be reduced and/or increased; How many hours ahead would a set point signal have to be sent, in order to assure the load shifting without any impact in the business process; What would be a reasonable compensation for the provision of this flexibility. With the information collected in SF5_2, EDP will perform several simulations in the network in order to determine the impact of the load shifting in network optimization parameters, namely: SF5_3 Voltage profile; Congestion management; Deferred distribution capacity investments; Loss reduction. Due to the resilience of test site MV Network, other scenarios have to be simulated in order to test the impact of the load shifting.
The following scenarios will be tested in the simulations, with actual loads (as is): High load consumption, low renewable production High load consumption, high renewable production Low load consumption, high renewable production Low load consumption, low renewable production The same simulations will be performed, considering scenarios with high load and renewable (wind and solar) growth. SF5_4 The outputs of this simulation will serve as an input to build a business case for the TVPP (in WP7). Table 6.5 Methodology for validation of SF5
6.6 SF9 Advanced Protection Systems The methodology for the validation of this functionality is described in Table 6.6. Requirement ID SF9_1 Description A protection unit will be installed in a selected primary substation (Évora) within the test site during an evaluation period. The installed protection has the following main characteristics: SF9_2 S Full-function line/feeder relay including frequency functions, synchro-check and fault locator o I Current relay o R Auto-reclosing and breaker failure o T Sensitive earth-fault protection and directionality o U Voltage functions Other key features: o Combined Protection, Control, Measurement and Recording o Compliant with State-of-the-art Standards o Multiple Communication Options o IEC 61131-3 Logic and PLC Programming o Watchdog and Self-monitoring o Local and Web-based Interface o Automation Studio Toolset for Engineering Four phase and earth-fault overcurrent stages, with cold-load pickup and optional directionality, provide correct fault discrimination and adequate coordination options. Two distinct voltage blocks of each type, and five distinct frequency blocks of each type enable full-function load shedding or other applications. Thermal overload function is provided for line applications. Four independent setting groups are available for each function, and can be interchanged by user command or logic condition dependent on system operation.
This is the same protection relay model as used on the proof-of-concept test within D4.3. Therefore, the relay will also have 4 configurable setting groups, which are fundamental for the implementation of the adaptive protection functionalities. SF9_3 All faults occurring on the MV feeder will be recorded and analyzed in order to assess the effectiveness of Sustainable approach to protection systems (SF9). This information will be used within test scenarios created in the laboratories of ICCS and INESC for comparison and validation of the data used on the fault and network modelling (D4.3) Table 6.6 Methodology for validation of SF9
7 Conclusions The purpose of this document is not only to specify requirements for the demonstration, but also to serve as reference for the process of software development and validation methodology execution. It takes into account the technical details of the functionalities, and the specific characteristics of the test sites. Deliverable D6.2 will add specific details regarding the demonstration, including: Demonstration architecture; Specific networks chosen for validation (within the chose test site); Communication specifications; Activities and procedures performed to allow for the demonstration.