Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL...
Transcript of Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL...
![Page 1: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/1.jpg)
Deliverable 5.2
PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1
AND 2)
—
October 2019
This project has received funding from the European Union’s Horizon 2020 research and
innovation programme
under grant agreement n° 691777
Ref. Ares(2020)451922 - 24/01/2020
![Page 2: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/2.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 2
Document Information
Programme Horizon 2020 – Cooperation / Energy
Project acronym FutureFlow
Grant agreement number 691777
Number of the Deliverable D5.2
WP/Task related [WP5 / T 5.2]
Type Report
Confidentiality Public
Date of delivery [25.10.2019]
Status and Version Version 1.0
Number of pages 130 pages
Document Responsible GEN-I
Authors: Rok Lacko, GEN-I
Luka Nagode, GEN-I
Leon Maruša, EIMV
Andraž Andolšek, CyberGrid
Miha Kopač, CyberGrid
Reviewers: Darko Kramar, ELES
Document management
No Chapter Subchapter Responsible
1 Introduction GEN-I
2 Approach GEN-I
3 Coordination of all the partners for the test GEN-I
4 Preparation of test signals for the test EIMV
5 Preparation of BSP for the test CYBERGRID
6 Preparation of participating units GEN-I
7 Overseeing the tests GEN-I, EIMV, CYBERGRID
8 List of all the tests performed GEN-I
9 Annexes Documents for project partners
Gen-I
Documents for units
Gen-I
UC1 tests GEN-I, EIMV, CYBERGRID, SAP
UC2 tests GEN-I
![Page 3: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/3.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 3
![Page 4: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/4.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 4
Contents
Document Information .......................................................................................................... 2
Contents .............................................................................................................................. 4
Glossary ............................................................................................................................... 8
Abbreviations ....................................................................................................................... 9
Executive summary ............................................................................................................ 10
1 Introduction ....................................................................................................... 12
1.1 Document organisation .......................................................................................................................... 12 1.2 Relation to other tasks and work packages ........................................................................................... 13
2 Approach............................................................................................................ 13
3 Coordination of all partners for the test ................................................................ 14
4 Preparation of test signals for the test and testing procedures ............................... 14
4.1 Prequalification testing procedures ....................................................................................................... 14 4.2 UC2 testing procedures ........................................................................................................................... 15
5 Preparation of BSP for the test ............................................................................. 16
5.1 All the necessary adjustments before each separate test ...................................................................... 16
6 Preparation of participating units ........................................................................ 18
6.1 Preparation of document for each separate participating unit ............................................................. 18 6.2 Incorporating feedback from the units into test plans .......................................................................... 18
7 Overseeing the tests ............................................................................................ 19
7.1 Usual test routine .................................................................................................................................... 19 7.2 Troubleshooting during the test ............................................................................................................. 19
8 List of all the tests performed .............................................................................. 21
8.1 Use case 1 tests ....................................................................................................................................... 21 8.2 Use case 2 tests ....................................................................................................................................... 21
9 Conclusions ........................................................................................................ 22
Annex 1: Documents for partners about the tests .................................................................. 23
Wednesday 29.8. ..................................................................................................................................................... 23 Thursday 30.8. ......................................................................................................................................................... 28
Annex 2: Documents for notifying participating units ............................................................ 34
Annex 3: Reports on UC1 tests .............................................................................................. 36
Annex 3.1 UC1.L1 pilot test report .......................................................................................................................... 36 Annex 3.2 UC1.L2 pilot test report .......................................................................................................................... 41 Annex 3.3 UC1.L3 pilot test report .......................................................................................................................... 49 Annex 3.4 UC1.L4 pilot test report .......................................................................................................................... 57
Annex 4: Info about all tests performed (prequalification and UC2) with a short comment about
the test .............................................................................................................................. 61
Annex 4.1: Test ID number 1 ................................................................................................................................... 61
![Page 5: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/5.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 5
Annex 4.2: Test ID number 2 ................................................................................................................................... 62 Annex 4.3: Test ID number 3 ................................................................................................................................... 62 Annex 4.4: Test ID number 4 ................................................................................................................................... 63 Annex 4.5: Test ID number 5 ................................................................................................................................... 63 Annex 4.6: Test ID number 6 ................................................................................................................................... 64 Annex 4.7: Test ID number 7 ................................................................................................................................... 64 Annex 4.8: Test ID number 8 ................................................................................................................................... 65 Annex 4.9: Test ID number 9 ................................................................................................................................... 65 Annex 4.10: Test ID number 10 ............................................................................................................................... 66 Annex 4.11: Test ID number 11 ............................................................................................................................... 66 Annex 4.12: Test ID number 12 ............................................................................................................................... 67 Annex 4.13: Test ID number 13 ............................................................................................................................... 67 Annex 4.14: Test ID number 14 ............................................................................................................................... 68 Annex 4.15: Test ID number 15 ............................................................................................................................... 68 Annex 4.16: Test ID number 16 ............................................................................................................................... 69 Annex 4.17: Test ID number 17 ............................................................................................................................... 69 Annex 4.18: Test ID number 18 ............................................................................................................................... 70 Annex 4.19: Test ID number 19 ............................................................................................................................... 70 Annex 4.20: Test ID number 20 ............................................................................................................................... 71 Annex 4.21: Test ID number 21 ............................................................................................................................... 71 Annex 4.22: Test ID number 22 ............................................................................................................................... 72 Annex 4.23: Test ID number 23 ............................................................................................................................... 72 Annex 4.24: Test ID number 24 ............................................................................................................................... 73 Annex 4.25: Test ID number 25 ............................................................................................................................... 73 Annex 4.26: Test ID number 26 ............................................................................................................................... 74 Annex 4.27: Test ID number 27 ............................................................................................................................... 74 Annex 4.28: Test ID number 28 ............................................................................................................................... 75 Annex 4.29: Test ID number 29 ............................................................................................................................... 75 Annex 4.30: Test ID number 30 ............................................................................................................................... 76 Annex 4.31: Test ID number 31 ............................................................................................................................... 76 Annex 4.32: Test ID number 32 ............................................................................................................................... 77 Annex 4.33: Test ID number 33 ............................................................................................................................... 77 Annex 4.34: Test ID number 34 ............................................................................................................................... 78 Annex 4.35: Test ID number 35 ............................................................................................................................... 78 Annex 4.36: Test ID number 36 ............................................................................................................................... 79 Annex 4.37: Test ID number 37 ............................................................................................................................... 79 Annex 4.38: Test ID number 38 ............................................................................................................................... 80 Annex 4.39: Test ID number 39 ............................................................................................................................... 80 Annex 4.40: Test ID number 40 ............................................................................................................................... 81 Annex 4.41: Test ID number 41 ............................................................................................................................... 81 Annex 4.42: Test ID number 42 ............................................................................................................................... 82 Annex 4.43: Test ID number 43 ............................................................................................................................... 82 Annex 4.44: Test ID number 44 ............................................................................................................................... 83 Annex 4.45: Test ID number 45 ............................................................................................................................... 83 Annex 4.46: Test ID number 46 ............................................................................................................................... 84 Annex 4.47: Test ID number 47 ............................................................................................................................... 84 Annex 4.48: Test ID number 48 ............................................................................................................................... 85 Annex 4.49: Test ID number 49 ............................................................................................................................... 85 Annex 4.50: Test ID number 50 ............................................................................................................................... 86 Annex 4.51: Test ID number 51 ............................................................................................................................... 86 Annex 4.52: Test ID number 52 ............................................................................................................................... 87 Annex 4.53: Test ID number 53 ............................................................................................................................... 87 Annex 4.54: Test ID number 54 ............................................................................................................................... 88
![Page 6: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/6.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 6
Annex 4.55: Test ID number 55 ............................................................................................................................... 88 Annex 4.56: Test ID number 56 ............................................................................................................................... 89 Annex 4.57: Test ID number 57 ............................................................................................................................... 89 Annex 4.58: Test ID number 58 ............................................................................................................................... 90 Annex 4.59: Test ID number 59 ............................................................................................................................... 90 Annex 4.60: Test ID number 60 ............................................................................................................................... 91 Annex 4.61: Test ID number 61 ............................................................................................................................... 91 Annex 4.62: Test ID number 62 ............................................................................................................................... 92 Annex 4.63: Test ID number 63 ............................................................................................................................... 92 Annex 4.64: Test ID number 64 ............................................................................................................................... 93 Annex 4.65: Test ID number 65 ............................................................................................................................... 93 Annex 4.66: Test ID number 66 ............................................................................................................................... 94 Annex 4.67: Test ID number 67 ............................................................................................................................... 94 Annex 4.68: Test ID number 68 ............................................................................................................................... 95 Annex 4.69: Test ID number 69 ............................................................................................................................... 95 Annex 4.70: Test ID number 70 ............................................................................................................................... 96 Annex 4.71: Test ID number 71 ............................................................................................................................... 96 Annex 4.72: Test ID number 72 ............................................................................................................................... 97 Annex 4.73: Test ID number 73 ............................................................................................................................... 97 Annex 4.74: Test ID number 74 ............................................................................................................................... 98 Annex 4.75: Test ID number 75 ............................................................................................................................... 98 Annex 4.76: Test ID number 76 ............................................................................................................................... 99 Annex 4.77: Test ID number 77 ............................................................................................................................... 99 Annex 4.78: Test ID number 78 ............................................................................................................................. 100 Annex 4.79: Test ID number 79 ............................................................................................................................. 100 Annex 4.80: Test ID number 80 ............................................................................................................................. 101 Annex 4.81: Test ID number 81 ............................................................................................................................. 101 Annex 4.82: Test ID number 82 ............................................................................................................................. 102 Annex 4.83: Test ID number 83 ............................................................................................................................. 102 Annex 4.84: Test ID number 84 ............................................................................................................................. 103 Annex 4.85: Test ID number 85 ............................................................................................................................. 103 Annex 4.86: Test ID number 86 ............................................................................................................................. 104 Annex 4.87: Test ID number 87 ............................................................................................................................. 105 Annex 4.88: Test ID number 88 ............................................................................................................................. 105 Annex 4.89: Test ID number 89 ............................................................................................................................. 106 Annex 4.90: Test ID number 90 ............................................................................................................................. 106 Annex 4.91: Test ID number 91 ............................................................................................................................. 107 Annex 4.92: Test ID number 92 ............................................................................................................................. 107 Annex 4.93: Test ID number 93 ............................................................................................................................. 108 Annex 4.94: Test ID number 94 ............................................................................................................................. 108 Annex 4.95: Test ID number 95 ............................................................................................................................. 109 Annex 4.96: Test ID number 96 ............................................................................................................................. 109 Annex 4.97: Test ID number 97 ............................................................................................................................. 110 Annex 4.98: Test ID number 98 ............................................................................................................................. 110 Annex 4.99: Test ID number 99 ............................................................................................................................. 111 Annex 4.100: Test ID number 100.......................................................................................................................... 111 Annex 4.101: Test ID number 101.......................................................................................................................... 112 Annex 4.102: Test ID number 102.......................................................................................................................... 112 Annex 4.103: Test ID number 103.......................................................................................................................... 113 Annex 4.104: Test ID number 104.......................................................................................................................... 113 Annex 4.105: Test ID number 105.......................................................................................................................... 114 Annex 4.106: Test ID number 106.......................................................................................................................... 114 Annex 4.107: Test ID number 107.......................................................................................................................... 115
![Page 7: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/7.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 7
Annex 4.108: Test ID number 108.......................................................................................................................... 115 Annex 4.109: Test ID number 109.......................................................................................................................... 116 Annex 4.110: Test ID number 110.......................................................................................................................... 116 Annex 4.111: Test ID number 111.......................................................................................................................... 117 Annex 4.112: Test ID number 112.......................................................................................................................... 118 Annex 4.113: Test ID number 113.......................................................................................................................... 118 Annex 4.114: Test ID number 114.......................................................................................................................... 119 Annex 4.115: Test ID number 115.......................................................................................................................... 119 Annex 4.116: Test ID number 116.......................................................................................................................... 120 Annex 4.117: Test ID number 117.......................................................................................................................... 120 Annex 4.118: Test ID number 118.......................................................................................................................... 121 Annex 4.119: Test ID number 119.......................................................................................................................... 121 Annex 4.188: Test ID number 188.......................................................................................................................... 122 Annex 4.189: Test ID number 189.......................................................................................................................... 122 Annex 4.190: Test ID number 190.......................................................................................................................... 123 Annex 4.191: Test ID number 191.......................................................................................................................... 123 Annex 4.196: Test ID number 196.......................................................................................................................... 124 Annex 4.197: Test ID number 197.......................................................................................................................... 124 Annex 4.198: Test ID number 198.......................................................................................................................... 125 Annex 4.199: Test ID number 199.......................................................................................................................... 125 Annex 4.200: Test ID number 200.......................................................................................................................... 126 Annex 4.201: Test ID number 201.......................................................................................................................... 126 Annex 4.202: Test ID number 202.......................................................................................................................... 127 Annex 4.203: Test ID number 203.......................................................................................................................... 127 Annex 4.204: Test ID number 204.......................................................................................................................... 128 Annex 4.205: Test ID number 205.......................................................................................................................... 128 Annex 4.206: Test ID number 206.......................................................................................................................... 129 Annex 4.207: Test ID number 207.......................................................................................................................... 129 Annex 4.208: Test ID number 208.......................................................................................................................... 130 Annex 4.209: Test ID number 209.......................................................................................................................... 130 Annex 4.210: Test ID number 210.......................................................................................................................... 131 Annex 4.211: Test ID number 211.......................................................................................................................... 131 Annex 4.212: Test ID number 212.......................................................................................................................... 132 Annex 4.213: Test ID number 213.......................................................................................................................... 132 Annex 4.214: Test ID number 214.......................................................................................................................... 133 Annex 4.215: Test ID number 215.......................................................................................................................... 133 Annex 4.216: Test ID number 216.......................................................................................................................... 134 Annex 4.217: Test ID number 217.......................................................................................................................... 134 Annex 4.218: Test ID number 218.......................................................................................................................... 135 Annex 4.219: Test ID number 219.......................................................................................................................... 135 Annex 4.220: Test ID number 220.......................................................................................................................... 136 Annex 4.221: Test ID number 221.......................................................................................................................... 136 Annex 4.228: Test ID number 220.......................................................................................................................... 137 Annex 4.229: Test ID number 221.......................................................................................................................... 137 Annex 4.230: Test ID number 220.......................................................................................................................... 138
![Page 8: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/8.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 8
Glossary Refer to ENTSO-E glossary, https://www.entsoe.eu/data/data-portal/glossary/Pages/home.aspx.
![Page 9: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/9.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 9
Abbreviations Acronym Term Acronym Term
ACE Area Control Error (≡ FRCE) IN Imbalance Netting
aFRR Automatic frequency restoration reserve IP Imbalance Price
AGC Automated Generation Control IS Imbalance Settlement
AMF Available Maximum Flow ISP Imbalance Settlement Period
ANF Already Nominated Flow IT Information Technologies
ATC Available Transfer Capacity JAO Joint Allocation Office
BRP Balance Responsible Party KPI Key performance indicator
BSP Balancing Service Provider LFC Load-frequency control
C&I Commercial and industrial LFCR Load-frequency Control & Reserve
CACM Capacity Allocation and Congestion Management MC Market Coupling
CAF Common Activation Function MCP Market Clearing price
CB Critical Branch mFRR Manual Frequency Restoration Reserve
CEE Central-East Europe MOL Merit Order List
CGM Common grid model MP Marginal Price
CMO Common Merit Order MRC Multi-Regional Coupling
CMOL Common Merit Order List MW Megawatt
CO Critical Outage MWh Megawatt-hour
CWE Central-West Europe NC Network Code
CZC Cross Zonal Capacity NPP Nuclear Power Plant
D-1 Day-ahead NRA National Regulatory Authority
D-2 Two-days ahead NTC Net Transfer Capacity
DG Distributed generation OH Operational Handbook
DR Demand response OL Open Loop
DSM Demand side management OPF Optimal Power Flow
EA Explicit Auction PFC Power Flow Colouring
EB Electricity Balancing PFD Power Flow Decomposition
EC European Commission PI Proportional-Integral
ENTSO-E European Network of TSOs for Electricity PTDF Power Transfer Distribution Factors
EU European Union RAM Remaining Available Margin
FAT Full Activation Time RES Renewable energy sources
FB Flow-based RR Replacement Reserves
FCFS First come - first served RD Redispatching
FCR Frequency Containment Reserves RSC Regional Security Coordinator
FF FutureFlow SEE South-East Europe
FRCE Frequency Restoration Control Error ( ACE) SHB Slovenia-Croatia-BiH (Control block)
FRM Flow Reliability Margin SO, SysOp System Operation
FRR Frequency Restoration Reserves SO GL System Operation Guidelines
GCC Grid Control Cooperation Fmax Maximum Flow
GCT Gate Closure Time TPP Thermal Power Plant
GL Guideline TSC TSO Security Cooperation
GSK Generation Shift Key TSO Transmission system operator
HPP Hydro Power Plant WP Work Package
ID Intra-day XB Cross-Border
![Page 10: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/10.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 10
Executive summary
Within WP5 the retailers and aggregators had a very responsible and critical duty to engage
sufficient number of prosumers and distributed generators that are capable to take part in a very
complex aFRR process. Their motivation had to be maintained over a one year long experiment
since the tests were not executed continuously, but in sequences. The participation of the
prosumers and distributed generators, technically equipped for their participation in the aFRR was
the prerequisite for the field pilot tests subject to this deliverable.
This deliverable describes the pilot test in a separate control areas (without cross-border
integration and its effects), i.e. in the control area of ELES, APG, Mavir and Transelectrica. Within
each participating control zone involved in the pilot, these tests were performed based on the use
cases defined in WP4 with the prosumers and distributed generators recruited within task 5.1. Due
to the isolated nature of the tests, the prototype flexibility aggregation platform developed in WP2
had therefore ran separately within different regulatory regimes and their subsequent technical
constraints.
The aggregator GEN-i prepared and coordinated test procedures with TSOs and other involved
partners in line with the use case definitions. The test procedures were carried out over a full year
for use case 1 and two full quarters for use case 2 in order to measure the data leading to valuing
the performance indicators dedicated to each use case.
In general the approach and steps taken in the pilot tests were the following:
- Preparation of the test procedures and test signals. On a weekly basis GEN-I prepared
the initial test schedules with all the pilot tests included. EIMV prepared in advance the test
signals and other procedures needed. The reason for this was that in some cases additional
units were added or existing ones could not participate and consequently the maximum
available power of the whole pool of units was changing from week to week.
- Preparation of the Balance Service Providers for the tests. To achieve best use of
available units Gen-I was in direct contact with all unit owners on a regular basis. Since
these units never before participated on the aFRR market and due to its complexity, a lot
of effort was needed to adjust their control systems in a way that they were able to
successfully follow the setpoints in a 2-second resolution.
- Preparation of participating units. For each participating unit a separate test document
was created. The feedback of the unit owner was also an essential part of the test and
important information for general findings in the project.
- Overseeing the tests. Through a well prepared plan of procedures, the combined team of
Gen-I, EIMV, Cybergrid and other, managed to successfully carry out 220 individual tests.
All planned pilot tests from Use case 1 and Use case 2 were executed before the end of
March 2019. Some tests with better DR/DG forecasts were repeated in September and
October 2019.
The results of all individual test are transparently presented in the continuation of this report. Each
individual test lasted 120 minutes, which in total amounted to a total of 312 hours of operational
testing. All 156 use case 2 tests were finished successfully, out of which compliance with aFRR
quality requirements was 75%, 70%, 40% and 27% in Slovenia, Austria, Hungary and Romania,
![Page 11: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/11.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 11
respectively. In some cases the response of the pool of units was exactly as expected according to
the predefined criteria, in some cases not as good, but in general it was demonstrated that the
responses of the participating DR/DG units can fulfil strict demand of 5 minute full activation time
(FAT). During the additional pilot tests using solar and wind power plants it became clear that the
forecast for a specific unit can deviate a lot on, in particular on a day with unpredictable weather.
There was only a limited number of those units in the pool, so on a larger sample of units a better
accuracy would be expected.
Based on the experiences gained with the pilot tests we were able to estimate the minimum
standard for the portfolio of prosumers in order to adequately conduct the aFRR pilot tests
according to the needs and the criteria of the TSOs.
The further analysis of pilot tests performed will be covered in D4.3 and D6.1.
![Page 12: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/12.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 12
1 Introduction
Work package 5 (WP5) deals with performing first part of the tests that were defined in WP4.
Its objectives are therefore:
• Introduce all the preparation that had to be done in testing various parts of the system
• Introduce all the effort of project partners that went into performing the tests
• To briefly show the results of the performed tests. The assessment of pilot tests is done in
D4.3. Impact analysis of the performed tests is done in D6.1.
Table 1: Task 5.2 and 5.3
WP5 DEFINITION OF USE CASES AND KPIS, AND ASSESSMENT OF PILOT TESTS
WP leader:
Deliverables
Task 5.2 Use case 1 Gen-I D5.2
Task 5.2 Use case 2 Gen-I D5.2
Task 5.3 Use case 3 Gen-I D5.3
Task 5.3 Use case 4 Gen-I D5.3
This document (Deliverable 5.2) deals with the first two among the listed WP5 tasks, i.e. describes
how Use case 1 and 2 tests were performed. Use case 3 and 4 are described in Deliverable 5.3.
1.1 Document organisation
The document is organised through the following key chapters:
• Introduction – provides the introductory descriptions, document organisation and
relations with other Tasks and Work Packages.
• Approach – provides the information on the tasks and the approach applied
• Coordination of all partners for the test (GEN-I)
• Preparation of test signals for the test (EIMV)
• Preparation of BSP for the test (CyberGRID) – provides info on the necessary adjustments
before each separate test
• Preparation of participating units (GEN-I) – describes how requesting weekly capacity
availability, preparing plan for the tests, preparation of documents for informing partners
and preparation of document for each separate participating unit was donw
• Overseeing the test (GEN-I, EIMV, CyberGRID) – introduces usual test routine and
troubleshooting during the test
• List of all the tests performed (Gen-I) – describes all Use case 1 and Use case 2 tests
![Page 13: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/13.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 13
1.2 Relation to other tasks and work packages
This deliverable is related to the work performed/to be performed, within the:
Previous work being done within the Work Package 4:
• Assessment of pilot tests
Ongoing work within the Work Package 4 / Task 4.1.
• Where KPIs are defined consistently and simultaneously with the description of the four
Use Cases
Forthcoming work within the
• Work Package 4 / Task 4.3, where KPIs will be used for the assessment of the pilot tests
• Work Package 6, Impact analysis of pilot tests
2 Approach
Following the signal for aFRR was something that none of participating units have done before. That is why the approach to them had to be very insightful with frequent communication between
everyone involved. The preparation for each week of the pilot test was done in three phases:
1) Gen-I, EIMV and CyberGrid agree upon which tests will be performed
2) Gen-I prepares and distributes weekly test plan to inform all partners in the project 3) Gen-I prepares personalized weekly test plan for each technical unit, its customer relations
team distributes that plan to all participating clients
That way everyone was regularly informed of what was happening and the tests did not catch
anyone unprepared. The approach proved to be very successful, since it left enough time for
feedback regarding proposed changes and potential unavailability of the units.
![Page 14: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/14.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 14
3 Coordination of all partners for the test Gen-I first prepared an approximate calendar of pilot tests. The initial plan was then adjusted for a
week in advance every end of the week. After Gen-I, EIMV and Cybergrid agreed on proposed test
IDs, dates of execution and units participating, Gen-I prepared an overview document for all the
partners included in the pilot tests. An example of the document that presented all of the critical
information for partners participating in the pilot tests can be found in “
Number of tests
List of prequalification tests List of Use case 2 tests
1. TC.1 UC2_AB-01_ID-01
2. TC.2 UC2_AB-01_ID-02
3. TC.3 UC2_AB-01_ID-03
4. TC.4 UC2_RE-01_ID-01
5. TC.5 UC2_RE-01_ID-02
6. TC.6 UC2_DC-01_ID-01
7. TC.7 UC2_DC-01_ID-02
8. TC.8 UC2_DC-01_ID-03
9. TC.9 UC3_AB-01_ID-01
10. TC.10 UC3_AB-01_ID-02
11. TC.11 UC3_AB-01_ID-03
12. TC.12 UC3_RE-01_ID-01
13. TC.13 UC3_RE-01_ID-02
14. TC.14 UC3_DC-01_ID-01
15. UC3_DC-01_ID-02
16. UC3_DC-01_ID-03
17. UC3_AT-01_ID-01
18. UC3_AT-01_ID-02
19. UC3_AT-01_ID-03
20. UC3_AT-01_ID-04
21. LFC controller settings check
4 Conclusions
Through a well prepared plan of procedures, the combined team of Gen-I, EIMV, Cybergrid and
everyone else successfully followed the plan for performing the pilot tests. All planned pilot tests
from Use case 1 and Use case 2 were performed before the end of March 2019. Due to the potential
of improving test results with better DR/DG forecasts, some pilot test were repeated in October
2019.
The estimated initial results show that the responses of the participating DR/DG units can fulfil strict
demand of FAT (full activation time) in 5 min. During additional pilot tests using solar and wind power
plants it became clear that the forecast for a specific unit can deviate a lot on a day with
unpredictable weather. There was only a handful of those units in the pool, so on a larger sample of
![Page 15: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/15.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 15
units a better accuracy would be expected.
The further analysis of pilot tests performed will be covered in D4.3 and D6.1.
![Page 16: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/16.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 16
Annex 1: Documents for partners about the tests”.
The document included the following information:
- Date and hour of the tests
- TSO zone
- Name of the test
- Shape of the signal
- Calculated activated energy for 15min intervals
The document had to be sent at least two days before the planned pilot tests.
For additional pilot tests the whole process had to be repeated.
5 Preparation of test signals for the test and testing
procedures Each test signal was prepared and coordinated with partners before the test execution. The reason for
this was gradual testing maturity which developed over the course of prequalification testing up to
more complex UC2 and UC3 tests. The signals for prequalification, UC2 and UC3 testing were standard
ones already chosen in D4.1. The preparation and management of the tests however turned out to be
extremely good practice since we could change the operational parameters of the tested VPPs (setting
bids, changing unit’s priorities, changing unit types, etc.) to test for even more marginal cases. For
example if we would execute a specific test we could try to include more renewables with different
bids and analyse what were the responses and if they were adequate enough to cover the requested
ACE. This kind of procedure gave us the idea as to how far a certain VPP can be pushed for marginal
operations.
5.1 Prequalification testing procedures
The preparation of test signals were executed with different procedures, depending on their type
(prequalification, UC2 or UC3).
In prequalification testing we used signals described in D4.1 (Chapter 6.1, Appendix 2). The testing
started with simple signals and moved onward to more complexed ones so the issues with VPP
activations could be resolved in between the separate tests. As such we executed prequalification
testing firstly once a week, once or twice a day and when major issues were addressed and resolved
we increased the testing frequency to twice a week, once or twice a day. For prequalification each VPP
(i.e. one VPP in each of the four available CZs), we executed tests that had a duration of 2 hours per
test. The setpoint signals sent to VPP) were the following:
- TC.1: Positive square
- TC.2: Negative square
- TC.3: Positive double square
- TC.4: Negative double square
- TC.5: Positive ramps
- TC.6: Negative ramps
- TC.7: Positive ramp- step
![Page 17: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/17.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 17
- TC.8: Negative ramp step
- TC.9: Positive double ramp
- TC.10: Negative double ramp
- TC.11: Alternating square
- TC.12: Alternating squares
- TC.13: Alternating triangles
- TC.14: Alternating triangle
Specific signal to use on the test day was agreed between the partners before the testing took place.
For each test GEN-I has calculated the required energy and sent the agreed bids to DEMO site, where
the prequalification signals were prepared. The prequalification signals did not require entire DEMO
platform to be running, only the parts necessary to send the setpoint and receive the response (open-
loop control). Setpoint signals were manually prepared according to bids sent by GEN-I and streamed
from local database over IEC-104 channel to VPPs, which were responding. Monitoring took place over
Grafana software at DEMO site, which showed the VPPs responses and envelope boundaries.
According to these GEN-I got a feeling as to what they would need to adjust in order for the next test
to perform even better. This procedures were repeated for each prequalification test and the
intermediate issues that occurred were resolved in the meantime.
5.2 UC2 testing procedures
UC2 test signals included usage of DEMO platform with LFC controllers, local optimization function and
prearranged bidding. The practice was that a few days in advance a test case for VPP was selected
based on units performances. GEN-I sent bids to EIMV and they were put into DEMOx simulator which
yielded setpoint results for the given scenario for the specific VPP based on the VPP model that was
built into DEMOx simulator. This setpoint was returned to GEN-I who calculated energies and reserved
the capacities with DR/DGs. On the day of the test the setpoint was streamed to VPP from DEMO site
and DEMO site was providing monitoring for the response. This was possible due to the nature of UC2
tests, which state that the cross-border exchange is not possible between CZs. As a result each VPP
activation can be treated separately and therefore we could provide open-loop control for VPPs. This
had the additional advantage as the resulted VPP activations could then be imported back into DEMOx
simulator to validate for the VPP models that turned out to perform quite excellent. The closed-loop
control with DEMOx operating in real-time was also checked but the additional flexibility was given to
VPPs with the described open-loop control since issues with DEMOx real-time communication
instability had to be addressed during UC2 testing.
Testing took place twice a week, two times a day.
For additional pilot tests the intensity was higher: three times a week, two times a day.
![Page 18: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/18.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 18
6 Preparation of BSP for the test
6.1 All the necessary adjustments before each separate test
The tests were separated into 2 groups.
The first group of use cases – UC1 was about the prequalification tests, where basic
activations were tested and the setpoint profile was usually rather simple.
The second group is about the use-cases UC2 and UC3 tests. These simulated realistic
events while using all four VPP (SI, AT, HU, RO). The setpoint received from emulated TSOs
was dynamic in nature.
The procedures that cyberGRID personnel performed while testing both groups of use
cases were similar.
Before all the tests, internal adding of new resources and testing was performed in parallel
whenever new resources were contracted by the GEN-I. When a new resource was
introduced, GEN-I sent a file containing the properties of the new resource. The resource
was then added to the appropriate VPP (control zone) according to its properties. Some of
the properties described below were added to each resource:
− The name of the resource and the region where it is placed.
− The positive installed capacity/consumption. The negative installed capacity/feed-
in.
− The resource facility type (generator, consumer or prosumer).
− Maximum positive and negative flexibility.
− The required addressing for the forecasting algorithm (IEC104).
− The required addressing for the c (IEC104).
− The new resource was added to an existing resource account with its contact
person, phone, email and region.
After the resource was entered into the system, it was first internally tested by GEN-I and
cyberGRID to make sure all the signals were exchanged successfully (there were around 10
signals per resource) before using it in the upcoming use-cases. Internal tests were usually
performed by 2 persons, one from each partner. The cyberGRID person informed the GEN-
I about recently received signal and GEN-I confirmed the signal values at the side of the
customer-resource. All signals were tested in the similar matter. After signal test was
successful, an internal test activation was performed for approximately few minutes to see
that everything works as planned.
For a complete determination of the test, all conditions described below had to be met.
The partners had to conclude, which VPP will be used for the test. The date and time of the
test were needed to be set beforehand.
GEN-I sent the list of all available resources that were used in the upcoming individual tests
(due to the contract not all resources were available all the time for testing).
![Page 19: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/19.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 19
The list contained the available capacities, priorities in the internal merit order and the
prices for each resource. Each VPP (control zone) had its separate data set.
Along with the resources and available capacities, GEN-I sent a graph representing the
prediction of the activated resource along with predicted behaviour for the particular test.
The list also included a table representing the time and sum of energy during the test, the
negative bid size and the positive bid size (MW).
The received data was processed by cyberGRID. Each resource was reconfigured and
prepared for the test in all determined VPPs.
The configuration included:
− Activating the resource by placing it in the active pool (group)
− Entering the available nominal capacity for each resource. This is the maximum
positive and negative capacity in MW for a resource.
− Setting the communication failure delay (delay before resource shows error and
triggers the alarm).
− Setting the minimum activation time of a resource.
− Setting the time between two activations. The time to pass before the resource can
be used for an activation again.
All resources had to be ordered by priority in accordance to the “dispatching priority list”.
Priorities were divided into negative and positive priorities. The resources were then
configured appropriately based on the type of priority it had.
For the prequalification tests, bids had to be calculated manually. For each calculation,
crucial data had to be known in advance.
The date of the test, time when the test took place, volume of the bid, the capacity price
and the energy price. The “artificial” bids were then entered for each VPP.
During the UC2 and UC3 testing, the bids were automatically calculated by the VPP. For this
feature, proper configurations were demanded.
Every hour, the data was processed, and new bids were generated.
The bids were sent to the TSO cloud to participate in tender. Finally, the bids were
automatically inserted by the acceptance of the bid from the TSO cloud into the particular
VPPs.
Approximately 30 minutes before each test, all participants joined in a Skype meeting
where everything was double-checked as described in above description. The Skype
meeting lasted until the end of the test.
Each VPP started sending the reporting & validation data to TSO. With this the VPP was
ready to be activated.
While monitoring the test, CyberGRID checked the incoming and outgoing setpoint, the
available capacity of the activated resources and the measurement of a specific resource.
Based on the data, the graph representing it, was observed.
On the graph, two separate sets of data were controlled. The sum of all active resources
![Page 20: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/20.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 20
and each resource individually. If there was any inaccuracy, it was immediately reported
through Skype and fixed during the test if possible. If not possible, the source was located
and fixed before the next test.
After the test was conducted, a report was prepared. The report included all the events
from the test.
A complete overview of the test was examined on the graph, where resource response
(measurement), absolute negative and absolute positive capacity were inspected.
Test data was sent to the other participants in a CSV (comma separated values) format file.
The file was based on the parameters given. The readings were separated into columns for
timepoint, measurement, baseline, positive capacity, negative capacity, absolute positive
and negative capacity, setpoint and incoming setpoint.
7 Preparation of participating units Participating in pilot testing for aFRR was a completely new experience for all the technical units that
joined Future Flow project. Because of that frequent communication and immediate problem solving
was very important for keeping up the good relations with everyone involved. A big part of that
effort was on the Gen-I customer relations team, who was in regular contact with the unit owners.
Every week all the units planned to participate in the pilot tests received a personalized document
informing them about:
- Test name, date and hour of activation,
- Expected contracted available power,
- Estimated regulation energy and
- Estimated operating time.
- Total hours of operation they already achieved (to compare it with contracted 60h),
- Total hours of their availability (to compare it with contracted 2016h)
This was important so they knew that they were not exceeding the agreed participation.
7.1 Preparation of document for each separate participating unit
The document for individual units can be found in “Annex 2: Documents for notifying participating
units”. It was prepared immediately after the preparation of the document for partners has finished.
After preparation it was distributed to all of the contact addresses that participating units have
provided.
7.2 Incorporating feedback from the units into test plans
Upon receipt of the document, the parties reported back in case of unavailability due to various
reasons. That way all units with planned unavailability were excluded from the tests in advance.
When testing very dynamic signals Gen-I received complaints about a very high number of extremely
short activations. Together with EIMV a filter for the initial signal was implemented, so the problem
was solved on a higher level. Internal regulations of the units after the change had no more problems
![Page 21: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/21.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 21
with following the desired setpoints.
8 Overseeing the tests
8.1 Usual test routine
During the test, all participants were in a Skype meeting.
The Skype meeting started before the test for additional preparation. The additional preparation
meant confirming the unit order for the activation, verifying the signals (measurement and capacities)
for each unit. If the units were not responding the customers were reached and informed about the
problems. At the beginning of the test, when all the necessary data was confirmed, the setpoint was
sent and the activation started. The data of each unit was constantly checked from two perspectives.
The logs, where raw data was presented and the graph where the data was shown with a line. The two
had to be corresponding.
8.2 Troubleshooting during the test
CyberGRID troubleshooting:
Troubleshooting on DEMO site has took place when test failures have occurred. Here are failures that
occurred most often and were addressed during or after the testing:
- IEC-104 communication failures: Due to unstable operation of IEC-104 communication
gateway (unexpected timeouts, communication dropping, unsorted packets, etc.), the
application had to be debugged and checked. Since we used a closed-source application and
the vendor was not providing the requested support we had no choice but to transition into
our own solution. An additional IEC-104 gateway application was developed, tested and
deployed into production by EIMV development team. This provided stable communication
for further testing and resolved IEC-104 issues.
- Prequalification test: During some tests it occurred that responses were not properly scaled,
meaning the VPP has underperformed or overperformed by a certain amount of power. This
was traced back to human factor since prequalification tests were manually triggered, the
operator has improperly set the gain coefficients. This was resolved with double checking the
values set by different individuals. Since prequalification tests were only for pre-check of
units responses before UC2 and UC3 tests, there was no need for automatization of the task.
However it was identified that if this should be used in production the gain setting procedure
should be automated, where information from automatic bids should be sent;
- Server unavailability: This happened due to network communication failure or server
restarting or updating. It is suggested that in production there should be backup servers on
different site that are ready to take over the role of main server if the main server would
become unavailable. Similar solutions are already used in most of today’s SCADA systems for
TSOs;
- Expired bids: This happened when bit was sent from CyberGrid manually rather than
automatically after the GCT. The sent bid was rejected by FF cloud. The issue was not
addressed since GCT was a limitation made with purpose to reject late bids.;
![Page 22: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/22.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 22
![Page 23: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/23.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 23
9 List of all the tests performed
9.1 Use case 1 tests
In the Use case 1, a total of six tests was performed.
The levels tested were:
• Level 1: BSP- DR/DG
• Level 2: DEMO site – BSP
• Level 3: FF Cloud – DEMO site
• Level 4: TSO – DEMO site
• Level 5: Cybersecurity testing
• Level 6: Scalability testing
Detailed description of results for level 1 to 4 can be found in Annex 3: Reports on UC1 tests.
Description of level 5 and 6 is part of the Deliverable D4.3.
9.2 Use case 2 tests
List of all the tests performed, can be found in the table below. Details about each test can be found
in Annex 4: Info about all tests performed (prequalification and UC2) with a short comment about the
test.
Table 2: List of tests performed
Number of tests
List of prequalification tests List of Use case 2 tests
1. TC.1 UC2_AB-01_ID-01
2. TC.2 UC2_AB-01_ID-02
3. TC.3 UC2_AB-01_ID-03
4. TC.4 UC2_RE-01_ID-01
5. TC.5 UC2_RE-01_ID-02
6. TC.6 UC2_DC-01_ID-01
7. TC.7 UC2_DC-01_ID-02
8. TC.8 UC2_DC-01_ID-03
9. TC.9 UC3_AB-01_ID-01
10. TC.10 UC3_AB-01_ID-02
11. TC.11 UC3_AB-01_ID-03
12. TC.12 UC3_RE-01_ID-01
13. TC.13 UC3_RE-01_ID-02
14. TC.14 UC3_DC-01_ID-01
15. UC3_DC-01_ID-02
16. UC3_DC-01_ID-03
17. UC3_AT-01_ID-01
18. UC3_AT-01_ID-02
19. UC3_AT-01_ID-03
![Page 24: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/24.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 24
20. UC3_AT-01_ID-04
21. LFC controller settings check
10 Conclusions
Through a well prepared plan of procedures, the combined team of Gen-I, EIMV, Cybergrid and
everyone else successfully followed the plan for performing the pilot tests. All planned pilot tests
from Use case 1 and Use case 2 were performed before the end of March 2019. Due to the potential
of improving test results with better DR/DG forecasts, some pilot test were repeated in October
2019.
The estimated initial results show that the responses of the participating DR/DG units can fulfil strict
demand of FAT (full activation time) in 5 min. During additional pilot tests using solar and wind power
plants it became clear that the forecast for a specific unit can deviate a lot on a day with
unpredictable weather. There was only a handful of those units in the pool, so on a larger sample of
units a better accuracy would be expected.
The further analysis of pilot tests performed will be covered in D4.3 and D6.1.
![Page 25: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/25.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 25
Annex 1: Documents for partners about the tests A template for notifying partners in the project is introduced and explained.
Example of a weekly test plan for informing all participating partners (for week 35):
Plan of FutureFlow tests for week 35
Every test has a grapf of which unit will be activated and another graph defining the specifics of the
activation signal. On priority ladder 1 means the highest priority and 20 the lowest one.
Wednesday 29.8.
Tests at 13:00
Slovenia test TC.3v2
Use-case: 2
Scenario: 7
Description: Activation signal, positive step, half/full power
Positive Bid size [MW]
0,8
Positive reserve
Priority 1
ID BI_295
Available
Flexibility [MW] 0,8
Energy [MWh] 0,800
Running time [min] 90
![Page 26: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/26.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 26
Time SUM of energy (MWh)
Hours H1 0,57
H2 0,23
15 min intervals
1 0,09
2 0,10
3 0,19
4 0,20
5 0,11
6 0,10
7 0,01
8 0,00
Austria test RE-01_ID-01_APG
Use-case: 2
Group ID: RE-01
Group of Scenario: Day characteristics of ACE open loop changes
Scenario ID: ID-01
Test scenario: Open loop ACE on regular day
Control zone: APG
Positive Bid size [MW]
1
Negative bid size [MW]
2
![Page 27: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/27.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 27
Positive reserve
Priority 1
ID AT_18
Available
Flexibility [MW] 1
Energy [MWh] 0,578
Running time [min] 35
Negative reserve
Priority 1 2
ID AT_35 AT_18
Available
Flexibility [MW] -0,15 -2
Energy [MWh] -0,213 -2,613
Running time [min] 85 85
![Page 28: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/28.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 28
Time SUM of energy (MWh)
Hours H1 -1,86
H2 -0,38
15 min intervals
1 -0,47
2 -0,41
3 -0,49
4 -0,50
5 0,15
6 0,11
7 -0,14
8 -0,50
Romania test TC.1
Use-case: 2
Scenario: 1
Description: Activation signal, positive step off/on/off, full power
Positive Bid size [MW]
0,05
Positive reserve
Priority 1
ID RO_292
Available
Flexibility [MW] 0,05
Energy [MWh] 0,093
Running time [min] 111
![Page 29: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/29.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 29
Table with detailed info about the test:
Time SUM of energy (MWh)
Hours H1 0,048
H2 0,044
15 min intervals
1 0,011
2 0,013
3 0,013
4 0,013
5 0,013
6 0,013
7 0,013
8 0,007
![Page 30: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/30.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 30
Thursday 30.8.
Tests at 13:00
Slovenia test DC-01_ID-01_ELES
Use-case: 2
Group ID: DC-01
Group of Scenario: DR/DG bid positions
Scenario ID: ID-01
Test scenario: Open loop ACE on regular day
Control zone: ELES
Positive Bid size [MW]
5,5
Negative bid size [MW]
4
Positive reserve
Priority 1 2 3 4
ID BI_282 BI_155 BI_152 BI_295
Available
Flexibility [MW] 3 1 0,85 0,8
Energy [MWh] 1,712 0,552 0,464 0,350
Running time [min] 35 33 33 33
![Page 31: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/31.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 31
Negative reserve
Priority 1 2 3 4 5 6 7 8 9
ID BI_282 BI_248 BI_245 BI_250 BI_164 BI_254 BI_261 BI_227 BI_246
Available
Flexibility [MW] -1 -0,417 -0,312 -0,5 -0,5 -0,73 -0,4 -0,5 -0,417
Energy [MWh] -1,412 -0,584 -0,434 -0,691 -0,687 -0,991 -0,532 -0,187 0,000
Running time [min] 85 84 84 83 83 82 80 80 0
![Page 32: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/32.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 32
Time SUM of energy (MWh)
Hours H1 -0,20
H2 -2,24
15 min intervals
1 1,21
2 -0,49
3 0,08
4 -1,00
5 -0,21
6 -1,00
7 -0,57
8 -0,47
Austria test DC-01_ID-01_APG
Use-case: 2
Group ID: DC-01
Group of Scenario: DR/DG bid positions
Scenario ID: ID-01
Test scenario: Open loop ACE on regular day
Control zone: APG
Positive Bid size [MW]
1
Negative bid size [MW]
2
![Page 33: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/33.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 33
Positive reserve
Priority 1
ID AT_18
Available
Flexibility [MW] 1
Energy [MWh] 0,578
Running time [min] 35
Negative reserve
Priority 1 2
ID AT_35 AT_18
Available
Flexibility [MW] -0,15 -2
Energy [MWh] -0,213 -2,613
Running time [min] 85 85
![Page 34: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/34.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 34
Time SUM of energy (MWh)
Hours H1 -1,86
H2 -0,38
15 min intervals
1 -0,47
2 -0,41
3 -0,49
4 -0,50
5 0,15
6 0,11
7 -0,14
8 -0,50
Romania test TC.3
Use-case: 2
Scenario: 7
Description: Activation signal, positive step, half/full power
Positive Bid size [MW]
0,1
Positive reserve
Priority 1
ID RO_292
Available
Flexibility [MW] 0,1
Energy [MWh] 0,100
Running time [min] 90
![Page 35: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/35.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 35
Time SUM of energy (MWh)
Hours H1 0,072
H2 0,028
15 min intervals
1 0,011
2 0,013
3 0,023
4 0,025
5 0,014
6 0,013
7 0,002
8 0,000
![Page 36: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/36.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 36
Annex 2: Documents for notifying participating units A template for notifying participating units in the project is introduced and explained.
Example of a weekly plan for a single participating unit:
![Page 37: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/37.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 37
![Page 38: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/38.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 38
Annex 3: Reports on UC1 tests
Annex 3.1 UC1.L1 pilot test report
Use Case Nr. 1
Use Case Title Testing of building blocks and the IT prototype solution
Tested Level Level 1: BSP- DR/DG
Level 2: DEMO site – BSP
Level 3: FF Cloud – DEMO site
Level 4: TSO – DEMO site
Level 5: Cybersecurity testing
Level 6: Scalability testing
Tested Session Session 1: Communications connectivity
Session 2: Bidding
Session 3: Imbalance netting and pre-netting
Session 4: Activation
Session 5: FAT Tests
Session 6: Cybersecurity testing
Session 7: Scalability testing
Level Test Objective Measurement and control signals from aFRR aggregation platform to
DR/DG to enable activation of DR/DG sources according to aFRR
aggregation platform requests and track the performance (e.g.
delivered power, set point tracking) of each DR/DG
Session Test Objective Communications, data flow between BSP-DR/DG. BSP is hosting
aFRR flexibility platform, from where tests are initiated.
Establishment of basic cyber security mechanisms.
Activation commands from aFRR aggregation platform, between
BSP-DR/DG. DR/DG reacts to activations with changing operational
setpoint of delivered power.
Testers
Rok Lacko (GEN-I)
Andraž Andolšek (cyberGRID)
Reviewers Matjaž Dolinar (ELES)
![Page 39: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/39.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 39
Date of test
Overview of Tests Results
1.1 Tests log
The IEC-60870-5-104 communication protocol was tested on BSP platform from 1.1.2019 to
1.2.2019.
1.2 Rationale for decision
After executing a test, the decision is defined according to the following rules:
•OK: The test sheet is set to "OK" state when all steps are in "OK" state. The real result is compliant
to the expected result.
•NOK: The test sheet is set to "NOK" state when all steps of the test are set to "NOK" state or when
the result of a step differs from the expected result.
•Partial OK [POK]: The test sheet is set to "Partial OK" state when at least one step of the test is set
to "NOK" state or when the result of a step is partially compliant to the expected result. Keep it or
remove. Source of inconsistencies: criteria to set if result is Partial OK may be qualitative
•NOT RUN: Default state of a test sheet not yet executed.
•NOT COMPLETED [NOCO]: The test sheet is set to "Not Completed" state when at least one step of
the test is set "Not Run" state.
1.3 Overall assessment of tests
Incoming data (monitoring direction)
• Energy consumption [OK]
• Availability – positive [OK]
• Availability – negative [OK]
• Lower limit of controllable range [OK]
• Upper limit of controllable range [OK]
• Activation confirmation [OK]
Outgoing data (control direction)
• Start/Stop activation sequence [OK]
• Activation Set-point [OK]
• General interrogation [OK]
Real-time operation, measured values are updated on 2s. [OK]
![Page 40: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/40.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 40
Tests were performed on all 4 instances of aFRR aggregation platform (Slovenia, Austria, Hungary,
Romania) [OK]
IEC 60870-5-104 was tested according to its standard specification. [OK]
Statistics about tests:
• 100 % of tests [OK]:
o Total number: 48 (12 tests for 4 VPPs)
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
• 0 % of tests [PEN]:
o In progress: 0
• 0 % of tests [NOK]:
o In progress: 0
• 0 % of tests [POK]:
o In progress: 0
• 0 % of tests [NOCO]:
o Total number: 0
1.4 Impact of test environment
Tests were successfully performed with simulated as well as real VPPs on BSP site. In both cases
DR&DG as well as VPPs performed OK.
![Page 41: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/41.jpg)
This project has received funding from the European Union’s Horizon 2020 research and innovation programme
under grant agreement n° 691777
Detailed Tests Results
Group ID Group of Scenarios Scenario ID Test Scenario Expected Result Comm. Direction Location Test Comments Test Result
CC-01 Communication ID-01 BSP-DR/DG connectivity, IEC
104
Data flow established BSP-DR/DG, bidirectional BSP, DR/DG or
VPP provider
Connectivity between
BSP-DR&DG [OK]
100% OK
CC-02 Cybersecurity ID-01 BSP-DR/DG connectivity with
security mechanisms, IEC 104
Securing data flows
(measurement,
control)
BSP-DR/DG, bidirectional BSP, DR/DG or
VPP provider
Connectivity between
BSP-DR&DG [OK]
100% OK
CC-03 Semantics ID-01 BSP-DR/DG semantic
interoperability, IEC 104
Semantic model of
data flows
(measurement,
control)
BSP-DR/DG, bidirectional BSP, DR/DG or
VPP provider
Interoperability
between BSP-DR&DG
[OK]
100% OK
CC-04 Activation ID-01 Send measurements Data received DR/DG-BSP BSP Measurements [OK] 100% OK
ID-02 Send availability, positive Data received DR/DG-BSP BSP Availability-positive
[OK]
100% OK
ID-03 Send availability, negative
Data received DR/DG-BSP BSP Availability-negative
[OK]
100% OK
ID-04 Send Lower limit of
controllable range, absolute
value
Data received DR/DG-BSP BSP Lower limit of
controllable range [OK]
100% OK
ID-05 Send Upper limit of
controllable range, absolute
value
Data received DR/DG-BSP BSP Upper limit of
controllable range [OK]
100% OK
AC-01 Activation, basic ID-01 Send Activation Start/Stop Received BSP-DR/DG DR/DG Activation start/stop
[OK]
100% OK
AC-02 Activation, varying ID-01 Send Setpoint, absolute value Received BSP-DR/DG DR/DG Setpoint [OK] 100% OK
AC-03 Activation, monitoring ID-01 Valid response from DR/DG Received BSP-DR/DG DR/DG Response from DR&DG
[OK]
100% OK
![Page 42: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/42.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 42
Defect Tracking Log
Defect No. Defect Description Steps to reproduce Priority (high/low/medium)
Status (discarded/fixed/in
progress/on hold/new)
1
2
3
4
![Page 43: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/43.jpg)
This project has received funding from the European Union’s Horizon 2020 research and innovation programme
under grant agreement n° 691777
Annex 3.2 UC1.L2 pilot test report
Use Case Nr. 1
Use Case Title DR/DG integration within each of the four control zones
independently
Tested Level Level 1: BSP- DR/DG
Level 2: DEMO site – BSP
Level 3: FF Cloud – DEMO site
Level 4: TSO – DEMO site
Level 5: Cybersecurity testing
Level 6: Scalability testing
Tested Session Session 1: Communications connectivity
Session 2: Bidding
Session 3: Imbalance netting and pre-netting
Session 4: Activation
Session 5: FAT Tests
Session 6: Cybersecurity testing
Session 7: Scalability testing
Level Test Objective Activation commands for power delivery from bids, measurement of
activated bids
Session Test Objective Communications, data flow between FutureFlow DEMO site-BSP.
FutureFlow DEMO site is hosting demonstration TSO platform (LFC
controllers, CAFx) from where tests are initiated. BSP is hosting aFRR
aggregation platform. Establishment of basic cyber security
mechanisms.
Bidding functionality between DEMO site-BSP hosted aFRR flexibility
platform. Bids and acknowledgements are exchanged.
Imbalance netting (Control Option1) and pre-netting (Control
Option2) functionality between FutureFlow DEMO site-BSP hosted
aFRR aggregation platform. BSP reacts to different setpoint signals
due to netting with changing operational setpoints of selected bids.
Activation of functionality between DEMO site-BSP hosted aFRR
flexibility platform. BSP reacts to different setpoint signals due to bid
activations with changing operational setpoints of selected bids.
![Page 44: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/44.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 44
Bid products with different FAT (standard, specific, mixed products)
and their activations between FutureFlow DEMO site-BSP hosted
aFRR aggregation platform. BSP reacts to different bid activations
that have different FAT with changing operational setpoints of those
bids.
Testers
Andraž Andolšek (cyberGRID)
Leon Maruša (EIMV), Aleš Časar (EIMV), Vladimir Djurica(EIMV)
Reviewers
Date of test 29.3.2018
Overview of Tests Results
1.1 Tests log
The IEC 60870-5-104 client (Matrikon IEC 60870 OPC client 1.0.5.0) software was tested at DEMO site
and IEC 60870-5-104 servers (software ??? version ???) software were tested at BSP on 5.4.2018.
The MQTT broker (Mosquitto broker 3.1.1) software was tested at DEMO site and CyberGrid MQTT
client was tested at BSP on 5.4.2018.
Note: Text in this color marks tests for option 2, which were mutually agreed not to be the subject of
real-time tests.
1.2 Rationale for decision
After executing a test, the decision is defined according to the following rules:
• OK: The test sheet is set to OK state when all steps are in "OK" state. The real result is
compliant to the expected result.
• NOK: The test sheet is set to not-OK state when all steps of the test are set to "NOK" state or
when the result of a step massively differs from the expected result.
• POK: The test sheet is set to partial-OK state when at least one step of the test is set to "NOK"
state or when the result of a step is partially compliant to the expected result. Source of
inconsistencies: criteria to set if result is Partial OK may be qualitative.
• NIM: The test sheet is set to not implemented state if it was discovered that such a test or
some steps of the test were not relevant to be implemented due to changes in the
configuration or certain functionality was seen as useless and was therefore discarded.
1.3 Overall assessment of tests
IEC-104 communication was checked for the following functionalities:
• The following IEC-104 values were checked for communications and semantics (for all 4
![Page 45: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/45.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 45
pools):
o Power setpoint [OK]
o Power setpoint loopback [OK]
o Upper regulation value [OK]
o Lower regulation value [OK]
o Baseline scheduled power [OK]
o Baseline power expectation [OK]
o Activated aFRR power [OK]
o Measured aFRR power [OK]
o Enabled pool flag [OK]
• Real-time operation, measured values are updated on 2s. [OK]
• Setpoints for all 4 pools were sent from DEMO site, received on BSP and sent back to DEMO
site as setpoint loopback value. [OK]
• Quality statuses of sent/received messages are good. [OK]
• All 4 pools have reacted on sent setpoint with activated power. [OK]
• All 4 pools have reacted on sent setpoint with activated power in the desired FAT
(Prequalification tests). [OK]
MQTT communication was checked for the following functionalities:
• Bid sending (from BSP) and receiving (on DEMO site) (standard/specific/mixed bids). [POK]:
o Specific and mixed bids were not tested since tested BSP does not use these types
of bids.
• Bid acknowledgement (from DEMO site to BSP) (standard/specific/mixed bids). [POK]:
o Specific and mixed bids were not tested since tested BSP does not use these types
of bids.
• Bid conformation (from DEMO site to BSP) (standard/specific/mixed bids). [POK]:
o Specific and mixed bids were not tested since tested BSP does not use these types
of bids.
Statistics about tests:
• 100 % of tests [OK]:
o Total number: 13 (+2 tests waiting for CyberGrid comments)
o Number of Critical: 1 (IEC-104 communication problem [RESOLVED])
o Number of Major: 0
o Number of Minor: 2 (Problem with IEC-104 tags data types [RESOLVED], Testing of
standard bids communication over MQTT)
o Number of enhancements: 2 (IEC-104 communication debugged and upgraded, data
types for IEC-104 were changed from non-timetagged to timetagged)
• [NOK]:
o Total number: 0
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
![Page 46: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/46.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 46
o Number of enhancements: 0
• [POK]:
o Total number: 0
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
• [NIM]:
o Total number: 4
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
1.4 Impact of test environment
Tests were successfully performed with simulated as well as real VPPs on BSP site. In both cases
DEMO site as well as BSP site performed OK.
![Page 47: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/47.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 47
Detailed Tests Results
Group ID Group of Scenarios Scenario ID Test Scenario Expected Result Comm. Direction Location Test Comments Test Result
CC-01 Communication ID-01 FutureFlow DEMO site-BSP
connectivity, IEC 104
Data flow established DEMO site-BSP,
bidirectional
BSP, DR/DG Connectivity between
DEMO site and BSP
[OK]. All hosts and
ports established.
100 % [OK]
ID-02 FutureFlow DEMO site-BSP
connectivity, MQTT
Data flow established DEMO site-BSP,
bidirectional
BSP, DR/DG Connectivity between
DEMO site and BSP
[OK]. All hosts and
ports established.
100 % [OK]
CC-02 Cybersecurity ID-01 FutureFlow DEMO site-BSP
connectivity with security
mechanisms, IEC 104
Securing data flows
(measurement,
control)
DEMO site-BSP,
bidirectional
BSP, DR/DG There were problems
with encryption
application due to
wrong configuration.
The problem was
resolved and
communication was
successfully retested.
100 % [OK]
ID-02 FutureFlow DEMO site-BSP
connectivity with security
mechanisms, MQTT
Securing data flows
(measurement,
control, bids)
DEMO site-BSP,
bidirectional
BSP, DR/DG or
VPP provider
Security mechanisms
were implemented and
checked [OK].
100 % [OK]
CC-03 Semantics ID-01 FutureFlow DEMO site-BSP
semantic interoperability, IEC
104
Semantic model of
data flows
(measurement,
control)
DEMO site-BSP,
bidirectional
BSP, DR/DG All IEC-104 tags were
successfully tested.
Tests have shown the
need of different data
types as firstly defined.
Data types were
changed from non-
timetagged to
timetagged. The
problem was resolved
and communication
was successfully
retested.
100 % [OK]
![Page 48: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/48.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 48
ID-02 FutureFlow DEMO site-BSP
semantic interoperability,
MQTT
Semantic model of
data flows
(measurement,
control, bids)
FutureFlow DEMO site-
BSP, bidirectional
BSP, DR/DG Messages were tested
according to designed
semantic model, data
flows were checked for
inconsistencies, none
were found [OK].
100 % [OK]
BD-01
Place bids on the trading
platform
ID-01
aFRR aggregation platform
operator sends the bids to the
DEMO site bid forwarding
function
FutureFlow DEMO site
bid forwarding
function receives the
bids from aFRR
aggregation platform
BSP FutureFlow DEMO
site
BSP Bids were successfully
sent from BSP to DEMO
site [OK].
100 % [OK]
ID-02 Acknowledge of reception of
bid message
Message received BSP FutureFlow DEMO
site
FutureFlow
DEMO site
Acknowledge
messages were
successfully sent from
DEMO site to BSP [OK].
100 % [OK]
ID-03 Confirmation of acquired bids Trader is able to
observe the acquired
bids
FutureFlow DEMO site
BSP
BSP Bids were confirmed if
GTC limit was not
exceeded and rejected
otherwise [OK].
100 % [OK]
IM-01 Imbalance netting,
Control option 1
ID-01 ACE quality, imbalance netting
followed by CAF optimization.
Netting scenarios between
control zones [none, 1-1, 1-2,
1-3, arbitrary].
Lower aFRR activation,
depending on the
netting capacities.
FutureFlow DEMO site -
BSP
FutureFlow
DEMO site
ACE signal was
successfully reduced
due to aFRR
activations, UC2 and
UC3 tests describe the
details [OK].
100 % [OK]
IM-02 Pre- netting,
Control option 2
ID-02 ACE quality, pre-netting followed by CAF optimization.
Pre-netting scenarios between
control zones [none, 1-1, 1-2,
1-3, arbitrary].
Lower aFRR activation,
depending on the pre-
netting capacities.
FutureFlow DEMO site -
BSP
FutureFlow
DEMO site
Pre-neting was not
executed since Control
option 2 was not
implemented in real-
time testing but only in
simulations.
[NIM]
IM-02 Pre- netting,
Control option 2
ID-03 ACE quality, with proportional
or algorithm decision pre-
netting volume, pre-netting followed by CAF optimization.
Border cases of equal zonal
MW pre-netting options. Pre-
netting scenarios between
The same ACE quality,
regardless of type of
pre-netting selected.
FutureFlow DEMO site -
BSP
FutureFlow
DEMO site
Pre-neting was not
executed since Control
option 2 was not
implemented in real-
time testing but only in
simulations.
[NIM]
![Page 49: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/49.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 49
control zones [none, 1-1, 1-2,
1-3, arbitrary].
ACT-01 Receive setpoints and
evaluate setpoints. BSP
receives setpoint from
FutureFlow DEMO site
and checks if it is within
defined limits.
ID-01 BSP receives and validates
set-point from DEMO site
The user can view set-
point send from DEMO
site
FutureFlow DEMO site →
BSP
BSP CyberGrid fills out this
field.
CyberGrid fills out
this field.
ID-02 Setpoint in BSP's control
module is changing or
refreshing every 2s
Setpoint in BSP's
control module does
change/refresh every
2s
FutureFlow DEMO site →
BSP
BSP CyberGrid fills out this
field.
CyberGrid fills out
this field.
ACT-02 Communicate pool
values to DEMO site in
real time. BSP transmits
required data on the
pool level to the DEMO
site
ID-01 BSP sums individual
measured values – pool
Summed pool values
are available in BSP's
control module or sent
to FutureFlow DEMO
site
BSP→ FutureFlow DEMO
site
BSP Pool values were sent
over IEC-104 and
checked at DEMO site
[OK].
100 % [OK]
ID-02 DEMO site receives summed
pool values
FutureFow DEMO site
receives summed pool
values
BSP→ FutureFlow DEMO
site
FutureFlow
DEMO site
Summed pool values
were checked, and
compared with values
on BSP side [OK].
100 % [OK]
FAT-01 Bid products with
different FAT
ID-01 Standard. Analyzing influence
to ACE and social welfare
performance.
realized FAT FutureFlow DEMO site →
BSP
BSP Standard bids were
tested and validated to
have impact on
reducing ACE when
activated. FAT was a
constant 15 min.
100 % [OK]
ID-02 Specific. Analyzing influence
to ACE and social welfare
performance.
realized FAT FutureFlow DEMO site →
BSP
BSP Specific bids with
different FAT were not
implemented, since
BSPs don’t use this
functionality at all.
[NIM]
ID-03 Mixed products. Analyzing
influence to ACE and social
welfare performance.
realized FAT FutureFlow DEMO site →
BSP
BSP Mixed bids with
different FAT were not
implemented, since
[NIM]
![Page 50: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/50.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 50
Defect Tracking Log
BSPs don’t use this
functionality at all.
Defect No. Defect Description Steps to reproduce Priority (high/low/medium)
Status (discarded/fixed/in
progress/on hold/new)
1 Originally defined IEC-104 data types are non-
timetagged, therefore if values stay the same it’s
not possible to see if they are still in data flow,
since there is no information, when the value was sent/received.
1. Change data types from non-
timetagged to timetagged.
low fixed
2 IEC-104 communication is unstable due to
encrypting application. The result is automatic closing of communications on multiple pools and
therefore not receiving/sending any values in both directions.
1. Debug the existing encrypting
application or, 2. use different encrypting
application.
high fixed
3
4
![Page 51: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/51.jpg)
This project has received funding from the European Union’s Horizon 2020 research and innovation programme
under grant agreement n° 691777
Annex 3.3 UC1.L3 pilot test report
Pilot test report - internal
Use Case Nr. 1
Use Case Title DR/DG integration within the four control zones coupled with
Cross Zonal Capacity
Tested Level Level 1: BSP- DR/DG
Level 2: DEMO site – BSP
Level 3: FF Cloud – DEMO site
Level 4: TSO – DEMO site
Level 5: Cybersecurity testing
Level 6: Scalability testing
Tested Session Session 1: Communications connectivity
Session 2: Bidding
Session 3: Imbalance netting and pre-netting
Session 4: Activation
Session 5: FAT Tests
Session 6: Cybersecurity testing
Session 7: Scalability testing
Level Test Objective Exchange of measurement and control signals to CAF extension
implementation in FF Cloud platform. Bid activations and set point
commands
Session Test Objective Communications, data flow between FF Cloud-FutureFlow DEMO
site. FF Cloud is hosting CAFx. FutureFlow DEMO site is hosting
demonstration TSO platform (LFC controllers, CAFx). Tests are
initiated from either side. Establishment of basic cyber security
mechanisms.
Bidding functionality between FF Cloud platform-FutureFlow DEMO
site. FutureFlow DEMO site transparently sends bids received from
BSP (aFRR aggregation platform) to FF Cloud. Bids and
acknowledgements are exchanged.
Testers Gabriel Tianu (SAP)
![Page 52: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/52.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 52
Leon Maruša (EIMV), Aleš Časar (EIMV), Janko Koležnik (EIMV)
Reviewers Matjaž Dolinar (ELES)
Date of test 29.3.2018
Overview of Tests Results
1.1 Tests log
During testing of bids multiple MQTT clients ware tested including MQTT DEMO SAP module, MQTT
bidBroker module, MQTT CZC parser and a bid generator. All of the above are written in Java and
are located at the DEMO site. The versions of these programs are 2.0.0. MQTT DEMO SAP module is
the core of the communication between the DEMO platform and the HANA Cloud. MQTT bidBroker
module is responsible for inserting bids into the MySQL database. MQTT CZC parser parses cross
zonal capacities and forms XML files from historical recorded ATC capacities and at the same time
sends them from the DEMO platform to the HANA Cloud. Test bids were generated using a bid
generator which was coded as a simulator only for the purpose of testing.
1.2 Rationale for decision
After executing a test, the decision is defined according to the following rules:
• OK: The test sheet is set to OK state when all steps are in "OK" state. The real result is
compliant to the expected result.
• NOK: The test sheet is set to not-OK state when all steps of the test are set to "NOK" state or
when the result of a step massively differs from the expected result.
• POK: The test sheet is set to partial-OK state when at least one step of the test is set to "NOK"
state or when the result of a step is partially compliant to the expected result. Source of
inconsistencies: criteria to set if result is Partial OK may be qualitative.
• NIM: The test sheet is set to not implemented state if it was discovered that such a test or
some steps of the test were not relevant to be implemented due to changes in the
configuration or certain functionality was seen as useless and was therefore discarded.
1.3 Overall assessment of tests
Qualitative overall assessment of tests:
• MQTT communication was checked on the following topics:
o Pre-balancing cycle operation:
▪ 4 control zones standard bids submit [OK]
▪ 4 control zones standard bids acknowledge [OK]
▪ 4 control zones specific bids submit [OK]
▪ 4 control zones specific bids acknowledge [OK]
![Page 53: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/53.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 53
▪ 4 control zones CZC-ATC submit [OK]
▪ 4 control zones CZC-ATC acknowledge [OK]
▪ 4 control zones CZC-PTDF submit [NIM]:
• Target model for real-time tests performed with CZC-ATC model of
the border, therefore CZC-PTDF tests didn’t need to be
implemented.
▪ 4 control zones CZC-PTDF acknowledge [NIM] :
• Target model for real-time tests performed with CZC-ATC model of
the border, therefore CZC-PTDF tests didn’t need to be
implemented.
o Balancing cycle (real-time) operation (only for Control option 1):
▪ 4 control zones imbalance calculation from LFC (DEMO site -> FF cloud).
[OK]
▪ 4 control zones correction signals from cloud optimizer (FF cloud -> DEMO
site). [OK]
• Testing of HMI on FF cloud for monitoring:
o Monitoring of bids in FF cloud. [OK]
o Monitoring of CZC data in FF cloud. [OK]
• All bidding tests of sending data from DEMO site to FF cloud with standard bids passed, for
positive, negative, and single bids [OK]
• All bidding tests of receiving data on FF cloud from DEMO site with standard bids passed,
for positive, negative, and single bids [OK]
• All bidding tests of sending data from DEMO site to FF cloud with specific bids passed for
positive, negative, and single bids [OK]
• Bidding tests of receiving data on FF cloud from DEMO site with specific bids passed, for
positive, negative, and single bids [OK]
• Tests of accessing FF cloud platform’s HMI from DEMO site for bids and CZC monitoring –
status: Pending [OK]
• All messages exchanged in MQTT envelope were successfully secured with TLS [OK]
• All semantics transmitted and received on messages were checked [OK]
Quantitative overall assessment of tests:
Statistics about tests:
• [OK]:
o Total number: 15
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
• [NIM]:
o Total number: 1
o Number of Critical: 0
![Page 54: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/54.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 54
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
1.4 Impact of test environment
Initial tests were performed with bid simulator on DEMO site. The bids were simulated as they
would occur in real conditions as the unpredicted bid info was also successfully tested (e.g. wrong
format, bad XML schema in the message, etc.). Testing was also done with real VPP bids sent to
DEMO site and forwarded to FF Cloud, no functional difficulties were discovered.
![Page 55: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/55.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 55
Detailed Tests Results
Group ID Group of Scenarios Scenario ID Test Scenario Expected Result Comm. Direction Location Test Comments Test Result
CC-01 Communication ID-01 FF CLOUD platform-DEMO site
connectivity, MQTT,
measurements
Data flow established FF CLOUD platform→
DEMO site, DEMO site →
FF CLOUD platform
DEMO site, FF
CLOUD
platform
Connectivity between
FF cloud and DEMO
site [OK], testing
measurement topics
[OK].
100 % [OK]
ID-02 FF CLOUD platform-DEMO site
connectivity, MQTT, control
Data flow established FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
Connectivity between
FF cloud and DEMO
site [OK], testing
control topics [OK].
100 % [OK]
ID-03 FF CLOUD platform-
FutureFlow DEMO site
connectivity, MQTT, bids
Data flow established FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
All bids were
successful exchanged
[OK].
100 % [OK]
ID-04 FF CLOUD platform-
FutureFlow DEMO site
connectivity, HTTPS, HMI
Data flow established FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
Data flows established
and tested. HMI is
accessible. Connection
is encrypted with
HTTPS.
100 % [OK]
CC-02 Cybersecurity ID-01 FF CLOUD platform-
FutureFlow DEMO site
connectivity with security
mechanisms, MQTT
Securing data flows
(measurements,
control, bids)
FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
All messages are
secured with MQTT-
TLS,
transmitting/receiving
[OK] on both sides.
100 % [OK]
ID-02 FF CLOUD platform-
FutureFlow DEMO site
connectivity with security
mechanisms, HTTPS
Securing data flows,
HMI
FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
Exchanging traffic is
encrypted with HTTPS.
100 % [OK]
CC-03 Semantics ID-01 FF CLOUD platform-
FutureFlow DEMO site
semantics, MQTT,
measurements
Semantic model of
data flows classified,
stored in local DB on
CLOUD, DEMO.
FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
MQTT measurements
were checked and
validated according to
semantic data flow
model [OK].
100 % [OK]
ID-02 FF CLOUD platform- Semantic model of FF CLOUD platform→ FutureFlow MQTT measurements 100 % [OK]
![Page 56: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/56.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 56
FutureFlow DEMO site
semantics, MQTT, control
data flows classified,
stored in local DB on
CLOUD, DEMO.
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
DEMO site, FF
CLOUD
platform
were checked and
validated according to
semantic data flow
model [OK].
ID-03 FF CLOUD platform-
FutureFlow DEMO site
semantics, MQTT, bids
Semantic model of
data flows classified,
stored in local DB on
CLOUD, DEMO.
FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
Bid submit (std bid):
• positive qty [OK]
• negative qty [OK]
• single [OK]
• multiple [OK]
Bid acknowledge (std
bid):
• accepted – [OK]
• rejected – [OK]
All info confirmed and
[OK].
Bid submit (spec bid):
• positive qty [OK]
• negative qty [OK]
• single [OK]
• multiple [OK]
Bid acknowledge (spec
bid):
• accepted – [OK]
• rejected – [OK]
All info confirmed and
[OK].
100 % OK
ID-04 FF CLOUD platform-
FutureFlow DEMO site
semantics, HTTPS, HMI
Semantic model of
data flows classified,
HMI commands proper
response.
FF CLOUD platform→
FutureFlow DEMO site,
FutureFlow DEMO site →
FF CLOUD platform
FutureFlow
DEMO site, FF
CLOUD
platform
HMI tested for
responsiveness all
correct. Traffic
commands/responses
secured with HTTPS.
100 % [OK]
BD-01 Bidding ID-01 Bids in control zones [1, 2, 3,
4], positive, negative, single /
multiple unit generate
multiple bids, random bids
price distribution
CMOL constructed with
all bids.
FutureFlow
DEMO site
CMOL was constructed
from bids that FF cloud
has received [OK]
100 % [OK]
BD-02 Bid pricing ID-01 Bids with equal prices in
control zones [1, 2, 3, 4].
CMOL bids
construction,
FutureFlow
DEMO site
CMOL was constructed
from bids that FF cloud
100 % [OK]
![Page 57: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/57.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 57
distribution. has received, bids with
equal prices were also
activated [OK]
ID-02 Positive and negative prices
per control zones [1, 2, 3, 4].
CMOL bids
construction,
distribution.
FutureFlow
DEMO site
For all four control
zones positive bids
with positive prices
and negative bids with
positive or negative
prices were tested
[OK].
100 % [OK]
BD-03 Bid rejection ID-01 Bids send with different FAT
than the one valid for
respective TSO:
CMOL constructed only
from bids with proper
FAT parameters.
FutureFlow
DEMO site
Specific bids were
checked, but this
functionality was not
implemented as FAT
limitation was not
needed for this case.
[NIM]
ID-02 Limited transfer capacity on
control zone pairs [1-2, 2-3, 3-
4], multiple combinations.
CMOL constructed only
from bids from control
zones with available
transfer capacities.
FutureFlow
DEMO site
If borders were
congested FF Cloud
algorithm did not
activate bid for cutoff
CA. Checked for all
three border pairs
when congested.
100 % [OK]
ID-03 No transfer capacity on
control zone pairs [1-2, 2-3, 3-
4], multiple combinations.
CMOL constructed only
from bids from control
zones with transfer
capacities.
FutureFlow
DEMO site
This case was
performed on all UC2
tests were borders had
0 transfer capacity,
only local bids were
activated for local CAs.
[OK]
100 % [OK]
![Page 58: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/58.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 58
Defect Tracking Log
Defect No. Defect Description Steps to reproduce Priority (high/low/medium)
Status (discarded/fixed/in
progress/on hold/new)
1
2
3
4
![Page 59: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/59.jpg)
This project has received funding from the European Union’s Horizon 2020 research and innovation programme
under grant agreement n° 691777
Annex 3.4 UC1.L4 pilot test report
Pilot test report - internal
Use Case Nr. 1
Use Case Title DR/DG integration, with possibility of switching among BSPs
Tested Level Level 1: BSP- DR/DG
Level 2: DEMO site – BSP
Level 3: FF Cloud – DEMO site
Level 4: TSO – DEMO site
Level 5: Cybersecurity testing
Level 6: Scalability testing
Tested Session Session 1: Communications connectivity
Session 2: Bidding
Session 3: Imbalance netting and pre-netting
Session 4: Activation
Session 5: FAT Tests
Session 6: Cybersecurity testing
Session 7: Scalability testing
Level Test Objective Exchange of measurement and control signals from SCADA to enable
real time FutureFlow DEMO site operation of LFC and CAF extension.
Data from all TSOs are exchanged and four LFC models tested
Session Test Objective Communications, data flow between TSO-FutureFlow DEMO site.
Information exchange comprises SCADA measurements of ACE, tie
lines power flows and setpoints of selected conventional units.
Testers
Andrej Matko (ELES)
Leon Maruša (EIMV)
Reviewers
Date of test 5.4.2018
![Page 60: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/60.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 60
Overview of Tests Results
1.1 Tests log
The vOPCClient software (version 2.2) was installed and tested in the ELES SCADA DMZ. NMEA server
(version 1.3) was installed and tested on DEMO site. Testing was executed on 5.4.2018.
1.2 Rationale for decision
After executing a test, the decision is defined according to the following rules:
• OK: The test sheet is set to OK state when all steps are in "OK" state. The real result is
compliant to the expected result.
• NOK: The test sheet is set to not-OK state when all steps of the test are set to "NOK" state or
when the result of a step massively differs from the expected result.
• POK: The test sheet is set to partial-OK state when at least one step of the test is set to "NOK"
state or when the result of a step is partially compliant to the expected result. Source of
inconsistencies: criteria to set if result is Partial OK may be qualitative.
• NIM: The test sheet is set to not implemented state if it was discovered that such a test or
some steps of the test were not relevant to be implemented due to changes in the
configuration or certain functionality was seen as useless and was therefore discarded.
1.3 Overall assessment of tests
OPC DA 3.0 communication was checked for the following functionalities:
• The following OPC tags were checked for communication and semantics on SCADA and OPC
client side:
o SCADA_opc:: Open_loop_ACE_ELES [OK]
o SCADA_opc:: Raw_ACE_ELES [OK]
o SCADA_opc:: Filtered_ACE_ELES [OK]
o SCADA_opc:: Pcorr_ELES [OK]
o SCADA_opc:: aFRR_ELES [OK]
• Real-time operation, values sent from SCADA are updated on 2s. [OK]
NMEA communication was checked for the following functionalities:
• The following NMEA tags were checked for communication and semantics on OPC client and
RT-server side:
o NMEA:: Open_loop_ACE_ELES [OK]
o NMEA:: Raw_ACE_ELES [OK]
o NMEA:: Filtered_ACE_ELES [OK]
o NMEA:: Pcorr_ELES [OK]
o NMEA:: aFRR_ELES [OK]
• Real-time operation, values sent from OPC client are updated on 2s. [OK]
Statistics about tests:
![Page 61: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/61.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 61
• 100 % of tests [OK]:
o Total number: 2
o Number of Critical: 0
o Number of Major: 0
o Number of Minor: 0
o Number of enhancements: 0
• 0 % of tests [NOK]
• 0 % of tests [POK]
• 0 % of tests [PEN]
• 0 % of tests [NC]
1.4 Impact of test environment
First phase: Individual components on DEMO site were firstly tested with simulated data, no errors
were raised during these tests.
Second phase: All components (on SCADA DMZ and on DEMO site) were tested with real data and
real communication, no errors were raised during these tests.
![Page 62: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/62.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 62
Detailed Tests Results
Defect Tracking Log
Group ID Group of Scenarios Scenario ID Test Scenario Expected Result Comm. Direction Location Test Comments Test Result
TD-01 Communication ID-01 TSO-FutureFlow DEMO site
connectivity, OPC DA/NMEA
Data flow established TSO-FutureFlow DEMO
site, bidirectional
TSO,
FutureFlow
DEMO site
Communication was
successfully
established and tested.
100 % [OK]
TD-02 Semantics ID-01 TSO-FutureFlow DEMO site
semantic interoperability,
OPC DA/NMEA
Semantic model of
data flows
(measurement,
control)
TSO-FutureFlow DEMO
site, bidirectional
TSO,
FutureFlow
DEMO site
All values were
checked to be
corrected and updated
on 2s.
100 % [OK]
Defect No. Defect Description Steps to reproduce Priority
(high/low/medium)
Status
(discarded/fixed/in
progress/on
hold/new)
1
2
3
4
![Page 63: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/63.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 63
Annex 4: Info about all tests performed (prequalification and
UC2) with a short comment about the test
Annex 4.1: Test ID number 1
Test ID number Date of test Name of test Control zone Comments
1 25.4.2018
10.00 TC.1 ELES OK
![Page 64: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/64.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 64
Annex 4.2: Test ID number 2
Test ID number Date of test Name of test Control zone Comments
2 25.4.2018
13.00 TC.2 ELES OK
Annex 4.3: Test ID number 3
Test ID number Date of test Name of test Control zone Comments
3 9.5.2018 10.00 TC.3 ELES test failed, did not
follow setpoint
![Page 65: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/65.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 65
Annex 4.4: Test ID number 4
Test ID number Date of test Name of test Control zone Comments
4 9.5.2018 10.00 TC.2_f APG test failed, no
response
Annex 4.5: Test ID number 5
Test ID number Date of test Name of test Control zone Comments
5 9.5.2018 13.00 TC.4 ELES
test failed, not
enough available
power
![Page 66: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/66.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 66
Annex 4.6: Test ID number 6
Test ID
number
Date of
test
Name of test Control zone Comments
6 10.5.2018
10.00 TC.5 ELES
test failed, problems with
baseline calculation and unit
behaviour
Annex 4.7: Test ID number 7
Test ID
number
Date of
test
Name of test Control zone Comments
7 10.5.2018
13.00 TC.6 ELES OK
![Page 67: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/67.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 67
Annex 4.8: Test ID number 8
Test ID
number
Date of
test
Name of test Control zone Comments
8 23.5.2018
10.00 TC.7 ELES
test failed, problems with unit
behaviour
Annex 4.9: Test ID number 9
Test ID
number
Date of
test
Name of test Control zone Comments
9 23.5.2018
13.00 TC.8 ELES OK
![Page 68: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/68.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 68
Annex 4.10: Test ID number 10
Test ID
number
Date of
test
Name of test Control zone Comments
10 23.5.2018
13.00 TC.1 APG test failed
Annex 4.11: Test ID number 11
Test ID
number
Date of
test
Name of test Control zone Comments
11 23.5.2018
13.00 TC.4 MAVIR
test failed, problems with unit
behaviour
![Page 69: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/69.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 69
Annex 4.12: Test ID number 12
Test ID
number
Date of
test
Name of test Control zone Comments
12 24.5.2018
10.00 TC.9 ELES test failed
Annex 4.13: Test ID number 13
Test ID
number
Date of
test
Name of test Control zone Comments
13 24.5.2018
10.00 TC.2_f2 APG test failed
![Page 70: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/70.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 70
Annex 4.14: Test ID number 14
Test ID
number
Date of
test
Name of test Control zone Comments
14 24.5.2018
13.00 TC.10 ELES OK
Annex 4.15: Test ID number 15
Test ID
number
Date of
test
Name of test Control zone Comments
15 24.5.2018
13.00 TC.6 MAVIR
test failed, problems with unit
behaviour
![Page 71: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/71.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 71
Annex 4.16: Test ID number 16
Test ID
number
Date of
test
Name of test Control zone Comments
16 30.5.2018
10.00 TC.9 ELES OK
Annex 4.17: Test ID number 17
Test ID
number
Date of
test
Name of test Control zone Comments
17 30.5.2018
10.00 TC.2 APG OK
![Page 72: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/72.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 72
Annex 4.18: Test ID number 18
Test ID
number
Date of
test
Name of test Control zone Comments
18 30.5.2018
14.00 TC.8_f MAVIR Test failed
Annex 4.19: Test ID number 19
Test ID
number
Date of
test
Name of test Control zone Comments
19 31.5.2018
10.00 TC.11 ELES
OK (but not enough wind for
negative bid)
![Page 73: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/73.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 73
Annex 4.20: Test ID number 20
Test ID
number
Date of
test
Name of test Control zone Comments
20 6.6.2018
10.00 TC.12 ELES
OK (but one unit had load
swing)
Annex 4.21: Test ID number 21
Test ID
number
Date of
test
Name of test Control zone Comments
21 6.6.2018
10.00 TC.5 APG OK
![Page 74: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/74.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 74
Annex 4.22: Test ID number 22
Test ID
number
Date of
test
Name of test Control zone Comments
22 6.6.2018
13.00 TC.8 MAVIR
test failed, problems with unit
behaviour
Annex 4.23: Test ID number 23
Test ID
number
Date of
test
Name of test Control zone Comments
23 7.6.2018
10.00 TC.13 ELES
OK (but one unit had load
swing)
![Page 75: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/75.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 75
Annex 4.24: Test ID number 24
Test ID
number
Date of
test
Name of test Control zone Comments
24 7.6.2018
10.00 TC.6 APG OK
Annex 4.25: Test ID number 25
Test ID
number
Date of
test
Name of test Control zone Comments
25 7.6.2018
13.00 TC.10 MAVIR Test failed
![Page 76: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/76.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 76
Annex 4.26: Test ID number 26
Test ID
number
Date of
test
Name of test Control zone Comments
26 13.6.2018
10.00 TC.14 ELES OK
Annex 4.27: Test ID number 27
Test ID
number
Date of
test
Name of test Control zone Comments
27 13.6.2018
10.00 TC.3 APG OK
![Page 77: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/77.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 77
Annex 4.28: Test ID number 28
Test ID
number
Date of
test
Name of test Control zone Comments
28 14.6.2018
10.00 TC.6v2 ELES
test failed, problems with unit
behaviour
Annex 4.29: Test ID number 29
Test ID
number
Date of
test
Name of test Control zone Comments
29 14.6.2018
10.00 TC.4 APG OK
![Page 78: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/78.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 78
Annex 4.30: Test ID number 30
Test ID
number
Date of
test
Name of test Control zone Comments
30 20.6.2018
10.00 TC.7 APG OK
Annex 4.31: Test ID number 31
Test ID
number
Date of
test
Name of test Control zone Comments
31 20.6.2018
10.00 TC.8v2 MAVIR
test failed, problems with unit
behaviour
![Page 79: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/79.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 79
Annex 4.32: Test ID number 32
Test ID
number
Date of
test
Name of test Control zone Comments
32 21.6.2018
10.00 TC.8 APG
test failed, problems with unit
behaviour
Annex 4.33: Test ID number 33
Test ID
number
Date of
test
Name of test Control zone Comments
33 21.6.2018
10.00 TC.10v2 MAVIR
test failed, problems with unit
behaviour
![Page 80: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/80.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 80
Annex 4.34: Test ID number 34
Test ID
number
Date of
test
Name of test Control zone Comments
34 27.6.2018
13.00 TC.9 APG
test failed, problems with unit
behaviour
Annex 4.35: Test ID number 35
Test ID
number
Date of
test
Name of test Control zone Comments
35 28.6.2018
13.00 TC.10 APG OK
![Page 81: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/81.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 81
Annex 4.36: Test ID number 36
Test ID
number
Date of
test
Name of test Control zone Comments
36 4.7.2018
13.00 TC.11 APG test failed, IEC104 problems
Annex 4.37: Test ID number 37
Test ID
number
Date of
test
Name of test Control zone Comments
37 5.7.2018
13.00 TC.12 APG OK
![Page 82: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/82.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 82
Annex 4.38: Test ID number 38
Test ID
number
Date of
test
Name of test Control zone Comments
38 11.7.2018
13.00
UC2_AB-
01_ID-01 ELES
OK (2min spikes are too fast for
units)
Annex 4.39: Test ID number 39
Test ID
number
Date of
test
Name of test Control zone Comments
39 11.7.2018
13.00 TC.13 APG OK
![Page 83: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/83.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 83
Annex 4.40: Test ID number 40
Test ID
number
Date of
test
Name of test Control zone Comments
40 12.7.2018
13.00
UC2_AB-
01_ID-02 ELES OK until 15.00
Annex 4.41: Test ID number 41
Test ID
number
Date of
test
Name of test Control zone Comments
41 12.7.2018
13.00 TC.14 APG OK
![Page 84: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/84.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 84
Annex 4.42: Test ID number 42
Test ID
number
Date of
test
Name of test Control zone Comments
42 18.7.2018
13.00
UC2_AB-
01_ID-03 ELES test failed
Annex 4.43: Test ID number 43
Test ID
number
Date of
test
Name of test Control zone Comments
43 18.7.2018
13.00
UC2_AB-
01_ID-01 APG OK
![Page 85: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/85.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 85
Annex 4.44: Test ID number 44
Test ID
number
Date of
test
Name of test Control zone Comments
44 19.7.2018
13.00
UC2_RE-
01_ID-01 ELES
test failed, problems with unit
behaviour
Annex 4.45: Test ID number 45
Test ID
number
Date of
test
Name of test Control zone Comments
45 19.7.2018
13.00
UC2_AB-
01_ID-02 APG
test failed, baseline got
displaced
![Page 86: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/86.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 86
Annex 4.46: Test ID number 46
Test ID
number
Date of
test
Name of test Control zone Comments
46 22.8.2018
13.00
AB-01_ID-
03_APG APG
test failed, baseline got
displaced, but looks ok from
unit's perspective
Annex 4.47: Test ID number 47
Test ID
number
Date of
test
Name of test Control zone Comments
47 22.8.2018
13.00 TC.2 Transelectrica OK
![Page 87: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/87.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 87
Annex 4.48: Test ID number 48
Test ID number Date of test Name of test Control zone Comments
48 23.8.2018
13.00
RE-01_ID-
02_ELES ELES
OK (one short
spike of unit 282)
Annex 4.49: Test ID number 49
Test ID number Date of test Name of test Control zone Comments
49 23.8.2018
13.00
RE-01_ID-
02_APG APG OK
![Page 88: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/88.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 88
Annex 4.50: Test ID number 50
Test ID number Date of test Name of test Control zone Comments
50 23.8.2018
13.00 TC.4 Transelectrica OK
Annex 4.51: Test ID number 51
Test ID number Date of test Name of test Control zone Comments
51 29.8.2018
13.00 TC.3v2 ELES OK
![Page 89: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/89.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 89
Annex 4.52: Test ID number 52
Test ID
number
Date of
test
Name of test Control zone Comments
52 29.8.2018
13.00
RE-01_ID-
01_APG APG OK
Annex 4.53: Test ID number 53
Test ID
number
Date of
test
Name of test Control zone Comments
53 30.8.2018
13.00
DC-01_ID-
01_ELES ELES
test failed, ok responses, but
not enough available negative
potential
![Page 90: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/90.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 90
Annex 4.54: Test ID number 54
Test ID
number
Date of
test
Name of test Control zone Comments
54 30.8.2018
13.00
DC-01_ID-
01_APG APG OK
Annex 4.55: Test ID number 55
Test ID
number
Date of
test
Name of test Control zone Comments
55 5.9.2018
13.00
DC-01_ID-
02_ELES ELES
OK (with some problems with
units)
![Page 91: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/91.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 91
Annex 4.56: Test ID number 56
Test ID
number
Date of
test
Name of test Control zone Comments
56 5.9.2018
13.00
DC-01_ID-
02_APG APG
OK (unrealistic fast signal
spikes)
Annex 4.57: Test ID number 57
Test ID
number
Date of
test
Name of test Control zone Comments
57 6.9.2018
13.00
DC-01_ID-
03_ELES ELES OK
![Page 92: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/92.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 92
Annex 4.58: Test ID number 58
Test ID
number
Date of
test
Name of test Control zone Comments
58 12.9.2018
13.00 TC.6 Transelectrica
OK (apart from clouds
influencing power output and
unit being unavailable too
soon)
Annex 4.59: Test ID number 59
Test ID
number
Date of
test
Name of test Control zone Comments
59 13.9.2018
13.00 TC.13 Transelectrica
OK (apart from unit for positive
power being unavailable too
soon)
![Page 93: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/93.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 93
Annex 4.60: Test ID number 60
Test ID
number
Date of
test
Name of test Control zone Comments
60 19.9.2018
13.00 TC.8 Transelectrica test failed
Annex 4.61: Test ID number 61
Test ID
number
Date of
test
Name of test Control zone Comments
61 20.9.2018
13.00 TC.12 Transelectrica test failed
![Page 94: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/94.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 94
Annex 4.62: Test ID number 62
Test ID
number
Date of
test
Name of test Control zone Comments
62 26.9.2018
13.00 TC.8v2 Transelectrica
OK (apart from clouds
influencing power output)
Annex 4.63: Test ID number 63
Test ID
number
Date of
test
Name of test Control zone Comments
63 27.9.2018
13.00 TC.12v2 Transelectrica
OK (apart from clouds
influencing power output)
![Page 95: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/95.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 95
Annex 4.64: Test ID number 64
Test ID
number
Date of
test
Name of test Control zone Comments
64 10.10.2018
13.00 TC.8v2 APG Ne response
Annex 4.65: Test ID number 65
Test ID
number
Date of
test
Name of test Control zone Comments
65 11.10.2018
13.00 TC.10 Transelectrica
Solid response at start, then
power generation from solar
panels did not return to
previous value, would need
better forecast
![Page 96: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/96.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 96
Annex 4.66: Test ID number 66
Test ID
number
Date of
test
Name of test Control zone Comments
66 11.10.2018
13.00 TC.9v2 APG test failed
Annex 4.67: Test ID number 67
Test ID
number
Date of
test
Name of test Control zone Comments
67 17.10.2018
13.00
AB-01_ID-
02_APGv2 APG OK
![Page 97: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/97.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 97
Annex 4.68: Test ID number 68
Test ID
number
Date of
test
Name of test Control zone Comments
68 17.10.2018
13.00 TC.9 Transelectrica OK
Annex 4.69: Test ID number 69
Test ID
number
Date of
test
Name of test Control zone Comments
69 17.10.2018
13.00 TC.5v2 ELES OK, overshoot with first spike
![Page 98: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/98.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 98
Annex 4.70: Test ID number 70
Test ID
number
Date of
test
Name of test Control zone Comments
70 18.10.2018
13.00 TC.11 Transelectrica not OK- renewables fluctuating
Annex 4.71: Test ID number 71
Test ID
number
Date of
test
Name of test Control zone Comments
71 18.10.2018
13.00 TC.6v3 ELES
OK, little overshoot with
second and forth spikes
![Page 99: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/99.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 99
Annex 4.72: Test ID number 72
Test ID
number
Date of
test
Name of test Control zone Comments
72 24.10.2018
13.00 TC.14 Transelectrica not OK- renewables fluctuating
Annex 4.73: Test ID number 73
Test ID
number
Date of
test
Name of test Control zone Comments
73 24.10.2018
13.00 TC.11v2 APG OK
![Page 100: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/100.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 100
Annex 4.74: Test ID number 74
Test ID
number
Date of
test
Name of test Control zone Comments
74 24.10.2018
13.00
AB-01_ID-
03_ELESv2 ELES OK, few spikes
Annex 4.75: Test ID number 75
Test ID
number
Date of
test
Name of test Control zone Comments
75 25.10.2018
13.00 TC.11v2 Transelectrica
OK, overshoot at start (first
5min)
![Page 101: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/101.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 101
Annex 4.76: Test ID number 76
Test ID
number
Date of
test
Name of test Control zone Comments
76 25.10.2018
13.00
AB-01_ID-
03_APGv2 APG OK
Annex 4.77: Test ID number 77
Test ID
number
Date of
test
Name of test Control zone Comments
77 25.10.2018
13.00
RE-01_ID-
01_ELESv2 ELES OK
![Page 102: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/102.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 102
Annex 4.78: Test ID number 78
Test ID
number
Date of
test
Name of test Control zone Comments
78 15.11.2018
13.00 TC.8v3 APG
test failed, positive reg instead
of negative mid test
Annex 4.79: Test ID number 79
Test ID
number
Date of
test
Name of test Control zone Comments
79 15.11.2018
13.00 TC.5 Transelectrica
test failed, no response at forth
spike
![Page 103: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/103.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 103
Annex 4.80: Test ID number 80
Test ID
number
Date of
test
Name of test Control zone Comments
80 21.11.2018
13.00 HU_TC.1 MAVIR OK, few drops mid regulation
Annex 4.81: Test ID number 81
Test ID
number
Date of
test
Name of test Control zone Comments
![Page 104: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/104.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 104
81 21.11.2018
13.00
UC2_AB-
01_ID-01_TEL Transelectrica
not Ok, stopped following the
signal, run out of water
Annex 4.82: Test ID number 82
Test ID
number
Date of
test
Name of test Control zone Comments
82 22.11.2018
13.00 HU_TC.2 MAVIR OK
Annex 4.83: Test ID number 83
Test ID
number
Date of
test
Name of test Control zone Comments
![Page 105: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/105.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 105
83 5.12.2018
10.00 HU_TC.3 MAVIR OK
Annex 4.84: Test ID number 84
Test ID
number
Date of
test
Name of test Control zone Comments
84 5.12.2018
13.00 HU_TC.5 MAVIR OK, few spikes
Annex 4.85: Test ID number 85
Test ID
number
Date of
test
Name of test Control zone Comments
![Page 106: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/106.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 106
85 5.12.2018
13.00
UC2_AB-
01_ID-
01_TEL_v2
Transelectrica test failed, no response
Annex 4.86: Test ID number 86
Test ID
number
Date of
test
Name of test Control zone Comments
86 6.12.2018
10.00 HU_TC.4 MAVIR test failed
![Page 107: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/107.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 107
Annex 4.87: Test ID number 87
Test ID
number
Date of
test
Name of test Control zone Comments
87 6.12.2018
13.00 HU_TC.6 MAVIR
test failed, first spike not
regulated,
Annex 4.88: Test ID number 88
Test ID
number
Date of
test
Name of test Control zone Comments
88 6.12.2018
13.00
UC2_AB-
01_ID-02_TEL Transelectrica test failed, no response
![Page 108: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/108.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 108
Annex 4.89: Test ID number 89
Test ID
number
Date of
test
Name of test Control zone Comments
89 12.12.2018
13.00 HU_ALL MAVIR not enough power in pool
Annex 4.90: Test ID number 90
Test ID
number
Date of
test
Name of test Control zone Comments
90 12.12.2018
13.00 SL_ALL ELES OK, bad second part of the test
![Page 109: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/109.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 109
Annex 4.91: Test ID number 91
Test ID
number
Date of
test
Name of test Control zone Comments
91 12.12.2018
13.00 AT_ALL APG OK
Annex 4.92: Test ID number 92
Test ID
number
Date of
test
Name of test Control zone Comments
92 12.12.2018
13.00 RO_ALL Transelectrica test failed, no response
![Page 110: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/110.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 110
Annex 4.93: Test ID number 93
Test ID
number
Date of
test
Name of test Control zone Comments
93 13.12.2018
13.00 HU_ALL_v2 MAVIR
not OK, deviation from req
energy
Annex 4.94: Test ID number 94
Test ID number Date of test Name of test Control zone Comments
94 13.12.2018
13.00 SL_ALL_v2 ELES OK
![Page 111: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/111.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 111
Annex 4.95: Test ID number 95
Test ID number Date of test Name of test Control zone Comments
95 13.12.2018
13.00 AT_ALL_v2 APG
OK, two small
spikes
Annex 4.96: Test ID number 96
Test ID number Date of test Name of test Control zone Comments
96 13.12.2018
13.00 RO_ALL_v2 Transelectrica
test failed, wrong
response
![Page 112: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/112.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 112
Annex 4.97: Test ID number 97
Test ID number Date of test Name of test Control zone Comments
97 19.12.2018
13.00 HU_ALL_v3 MAVIR OK
Annex 4.98: Test ID number 98
Test ID
number
Date of
test
Name of test Control zone Comments
98 19.12.2018
13.00 SL_ALL_v3 ELES OK
![Page 113: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/113.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 113
Annex 4.99: Test ID number 99
Test ID
number
Date of
test
Name of test Control zone Comments
99 19.12.2018
13.00 AT_ALL_v3 APG OK
Annex 4.100: Test ID number 100
Test ID
number
Date of
test
Name of test Control zone Comments
100 20.12.2018
13.00 HU_ALL_v4 MAVIR OK
![Page 114: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/114.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 114
Annex 4.101: Test ID number 101
Test ID
number
Date of
test
Name of test Control zone Comments
101 20.12.2018
13.00 SL_ALL_v4 ELES OK
Annex 4.102: Test ID number 102
Test ID
number
Date of
test
Name of test Control zone Comments
102 20.12.2018
13.00 AT_ALL_v4 APG OK
![Page 115: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/115.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 115
Annex 4.103: Test ID number 103
Test ID
number
Date of
test
Name of test Control zone Comments
103 9.01.2019
10.00
UC2_AB-
01_ID-
01_MAVIR
MAVIR not following setpoint
Annex 4.104: Test ID number 104
Test ID
number
Date of
test
Name of test Control zone Comments
104 9.01.2019
10.00
UC2_AB-
01_ID-
01_TELv3
Transelectrica test failed, missing some
responses
![Page 116: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/116.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 116
Annex 4.105: Test ID number 105
Test ID
number
Date of
test
Name of test Control zone Comments
105 9.01.2019
13.00
UC2_AB-
01_ID-
02_MAVIR
MAVIR not OK, deviation from req
energy
Annex 4.106: Test ID number 106
Test ID
number
Date of
test
Name of test Control zone Comments
106 9.01.2019
13.00
UC2_AB-
01_ID-
02_TELv3
Transelectrica test failed, response just at first
signal
![Page 117: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/117.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 117
Annex 4.107: Test ID number 107
Test ID
number
Date of
test
Name of test Control
zone
Comments
107 10.01.2019
10.00
UC2_AB-01_ID-
03_MAVIR MAVIR OK, except last 10 min
Annex 4.108: Test ID number 108
Test ID
number
Date of
test
Name of test Control zone Comments
108 10.01.2019
10.00
UC2_AB-
01_ID-03_TEL Transelectrica test failed, no response
![Page 118: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/118.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 118
Annex 4.109: Test ID number 109
Test ID
number
Date of
test
Name of test Control zone Comments
109 10.01.2019
13.00
UC2_RE-
01_ID-
01_MAVIR
MAVIR Test failed, second part not
following the signal
Annex 4.110: Test ID number 110
Test ID
number
Date of
test
Name of test Control zone Comments
![Page 119: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/119.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 119
110 10.01.2019
13.00
UC2_RE-
01_ID-01_TEL Transelectrica test failed, no second response
Annex 4.111: Test ID number 111
Test ID
number
Date of
test
Name of test Control zone Comments
111 16.01.2019
10.00
UC2_RE-
01_ID-
02_MAVIR
MAVIR OK
![Page 120: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/120.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 120
Annex 4.112: Test ID number 112
Test ID
number
Date of
test
Name of test Control zone Comments
112 16.01.2019
10.00
UC2_RE-
01_ID-02_TEL Transelectrica test failed
Annex 4.113: Test ID number 113
Test ID
number
Date of
test
Name of test Control zone Comments
113 16.01.2019
13.00
UC2_DC-
01_ID-01 MAVIR test failed
![Page 121: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/121.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 121
Annex 4.114: Test ID number 114
Test ID
number
Date of
test
Name of test Control zone Comments
114 16.01.2019
13.00
UC2_DC-
01_ID-01 Transelectrica test failed
Annex 4.115: Test ID number 115
Test ID
number
Date of
test
Name of test Control zone Comments
115 17.01.2019
10.00
UC2_DC-
01_ID-02 MAVIR OK
![Page 122: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/122.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 122
Annex 4.116: Test ID number 116
Test ID
number
Date of
test
Name of test Control zone Comments
116 17.01.2019
10.00
UC2_DC-
01_ID-02 Transelectrica test failed, no second response
Annex 4.117: Test ID number 117
Test ID
number
Date of
test
Name of test Control zone Comments
117 17.01.2019
13.00 METRO_TEST MAVIR test failed
![Page 123: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/123.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 123
Annex 4.118: Test ID number 118
Test ID
number
Date of
test
Name of test Control zone Comments
118 30.01.2019
10.00 TC.12 MAVIR OK
Annex 4.119: Test ID number 119
Test ID
number
Date of
test
Name of test Control zone Comments
119 31.01.2019
10.00 TC.12_metro MAVIR not OK, a lot of oscilating
![Page 124: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/124.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 124
Annex 4.188: Test ID number 188
Test ID
number
Date of
test
Name of test Control zone Comments
188 20.03.2019
10:00
UC2_AB-
01_ID-02 APG OK
Annex 4.189: Test ID number 189
Test ID
number
Date of
test
Name of test Control zone Comments
189 20.03.2019
10:00
UC2_AB-
01_ID-02 ELES
OK - there was not enought
positive reserve available
![Page 125: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/125.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 125
Annex 4.190: Test ID number 190
Test ID
number
Date of
test
Name of test Control zone Comments
190 20.03.2019
10:00
UC2_AB-
01_ID-02 MAVIR OK
Annex 4.191: Test ID number 191
Test ID
number
Date of
test
Name of test Control zone Comments
191 20.03.2019
10:00
UC2_AB-
01_ID-02 Transelectrica
Test failed - power plant not
following the signal
![Page 126: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/126.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 126
Annex 4.196: Test ID number 196
Test ID
number
Date of
test
Name of test Control zone Comments
196 29.03.2019
10:00 AT_ALL_29.3. APG OK - one spike at 10:55
Annex 4.197: Test ID number 197
Test ID
number
Date of
test
Name of test Control zone Comments
197 29.03.2019
10:00 SL_ALL_29.3. ELES OK - small spike around 10:34
![Page 127: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/127.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 127
Annex 4.198: Test ID number 198
Test ID
number
Date of
test
Name of test Control zone Comments
198 29.03.2019
10:00 HU_ALL_29.3. MAVIR
OK - short power output drop
at 11:15
Annex 4.199: Test ID number 199
Test ID
number
Date of
test
Name of test Control zone Comments
199 29.03.2019
10:00 RO_ALL_29.3. Transelectrica test failed
![Page 128: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/128.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 128
Annex 4.200: Test ID number 200
Test ID
number
Date of
test
Name of test Control zone Comments
200 18.09.2019
10:00 UC.2 test ELES OK
Annex 4.201: Test ID number 201
Test ID
number
Date of
test
Name of test Control zone Comments
201 18.09.2019
10:00 UC.2 test Transelectrica Failed
![Page 129: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/129.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 129
Annex 4.202: Test ID number 202
Test ID
number
Date of
test
Name of test Control zone Comments
202 18.09.2019
13:00 UC.2 Transelectrica Failed - signal fail
Annex 4.203: Test ID number 203
Test ID
number
Date of
test
Name of test Control zone Comments
203 18.09.2019
13:00 UC.2 ELES Failed - signal fail
![Page 130: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/130.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 130
Annex 4.204: Test ID number 204
Test ID
number
Date of
test
Name of test Control zone Comments
204 19.09.2019
10:00 UC.4 ELES
ok, but sometimes not enough
power delivered
Annex 4.205: Test ID number 205
Test ID
number
Date of
test
Name of test Control zone Comments
205 19.09.2019
10:00 UC.4 Transelectrica ok
![Page 131: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/131.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 131
Annex 4.206: Test ID number 206
Test ID
number
Date of
test
Name of test Control zone Comments
206 19.09.2019
13:00 UC.6 ELES ok but slow response
Annex 4.207: Test ID number 207
Test ID
number
Date of
test
Name of test Control zone Comments
207 19.09.2019
13:00 UC.6 Transelectrica ok but slow response
![Page 132: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/132.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 132
Annex 4.208: Test ID number 208
Test ID
number
Date of
test
Name of test Control zone Comments
208 24.09.2019
10:00 UC.8 ELES Ok
Annex 4.209: Test ID number 209
Test ID
number
Date of
test
Name of test Control zone Comments
209 24.09.2019
10:00 UC.8 Transelectrica fail - too much power delivered
![Page 133: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/133.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 133
Annex 4.210: Test ID number 210
Test ID
number
Date of
test
Name of test Control zone Comments
210 24.09.2019
13:00 UC.10 ELES Ok
Annex 4.211: Test ID number 211
Test ID
number
Date of
test
Name of test Control zone Comments
211 24.09.2019
13:00 UC.10 Transelectrica fail - too much power delivered
![Page 134: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/134.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 134
Annex 4.212: Test ID number 212
Test ID
number
Date of
test
Name of test Control zone Comments
212 25.09.2019
10:00 UC.12 ELES ok
Annex 4.213: Test ID number 213
Test ID
number
Date of
test
Name of test Control zone Comments
213 25.09.2019
10:00 UC.12 Transelectrica ok
![Page 135: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/135.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 135
Annex 4.214: Test ID number 214
Test ID
number
Date of
test
Name of test Control zone Comments
214 25.09.2019
13:00 UC.14 ELES ok
Annex 4.215: Test ID number 215
Test ID
number
Date of
test
Name of test Control zone Comments
215 25.09.2019
13:00 UC.14 Transelectrica fail
![Page 136: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/136.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 136
Annex 4.216: Test ID number 216
Test ID
number
Date of
test
Name of test Control zone Comments
216 26.09.2019
10:00
UC2_RE-
01_ID-01 ELES ok
Annex 4.217: Test ID number 217
Test ID
number
Date of
test
Name of test Control zone Comments
217 26.09.2019
10:00
UC2_RE-
01_ID-01 Transelectrica fail, no signal
![Page 137: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/137.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 137
Annex 4.218: Test ID number 218
Test ID
number
Date of
test
Name of test Control zone Comments
218 26.09.2019
13:00
UC2_DC-
01_ID-01 ELES ok
Annex 4.219: Test ID number 219
Test ID
number
Date of
test
Name of test Control zone Comments
219 26.09.2019
13:00
UC2_DC-
01_ID-01 Transelectrica fail, no signal
![Page 138: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/138.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 138
Annex 4.220: Test ID number 220
Test ID
number
Date of
test
Name of test Control zone Comments
220 1.10.2019
10:00
UC2_DC-
01_ID-03 ELES ok
Annex 4.221: Test ID number 221
Test ID
number
Date of
test
Name of test Control zone Comments
221 1.10.2019
10:00
UC2_DC-
01_ID-03 Transelectrica fail, no signal
![Page 139: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/139.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 139
Annex 4.228: Test ID number 228
Test ID
number
Date of
test
Name of test Control zone Comments
228 17.10.2019
10:00:00 FF test FINAL ELES partially successful
Annex 4.229: Test ID number 229
Test ID
number
Date of
test
Name of test Control zone Comments
229 17.10.2019
10:00:00 FF test FINAL APG OK
![Page 140: Deliverable 5.2 PILOT TESTING WITHIN EACH …...Deliverable 5.2 PILOT TESTING WITHIN EACH CONTROL ZONE (USE CASES 1 AND 2) — October 2019 This project has received funding from the](https://reader035.fdocuments.in/reader035/viewer/2022071015/5fce49db0dd85507ba38d85b/html5/thumbnails/140.jpg)
FutureFlow, Deliverable 1.3, Data needed to implement the common activation function | page 140
Annex 4.230: Test ID number 230
Test ID
number
Date of
test
Name of test Control zone Comments
230 17.10.2019
10:00:00 FF test FINAL Transelectrica failed