## 5 Result and Discussion
### Results from the Customer Survey
#### 5.2.2 Part 2: RESOLVD Value Propositions  
Part 2 comprised two types of questions. The first one was a list of high-level questions to grasp and validate the overall objectives of the project. These included the need to improve observability of the LV grid, the ability to integrate multiple LV grid components (such as the legacy system and upcoming IoT technologies), exploit flexibility of distributed energy storage and improved decision support tools (forecasting, scheduling and event detection). In this regard, the results from the respondents showed that there was an urgent need (within five years) to improve the decision support tools and observability of the LV grid (see Figure 8). Meanwhile, the flexibility and ability to integrate multiple LV grid components would be relevant in 5-10 years. Indeed, this depends on the availability of infrastructure and resources at the respondents' premises and their plan to reach a high penetration of DERs. It is interesting to note also, from the pareto analysis presented previously in Figure 5, that the possibility of managing distributed energy storage was seen as relevant and prioritized, but that more than 60% of the respondents' (DSOs) left this question as being most relevant in 5-10 years time. This could have been associated with the still manageable share of distributed renewable generation throughout the territory; thus, an urgent need of energy storage was mostly associated with the pace of the decarbonization of the grids. Figure 7: Customers’ responses to (**a**) the level of observability in their operation area and (**b**) the method of fault detection. The second part of the questions solely focused on the H2020 RESOLVD value propositions and were designed with the intention to validate and create synergy between the H2020 RESOLVD technology developers and the target customers (DSOs). For this reason, the same value propositions were analyzed using S&R, targeting the technology developers. Figure 9 shows the responses on the relevancy and urgency of the H2020 RESOLVD value propositions. About 70% of the respondents believed that three of the value propositions (i.e., improved capability to prevent congestion and over/under voltage issues, improved power quality and improved fault detection and critical event prevention) would be relevant in the coming five years, with importance shown by technology developers in the S&R results as well. Cybersecurity issues were also ranked to be relevant in the near future but had a lower CFI in the S&R results. One reason for this could have been that most customers (DSOs) have their own internal cybersecurity service, as this was revealed on the survey conducted, and other technology developers have limited knowledge of cybersecurity and have different perceptions. According to the responses, value propositions related to islanding mode were likely to be more relevant in a 10-15-year timeframe. For the local reactive power injection capability and reducing technical losses value propositions, the DSOs were mostly split between less than five years and a 10-15-year timeframe. A probable reason for this split could have been due to differences in the renewable penetration rate in customers' operating regions. Figure 8: High-level DSO demands pertaining to the RESOLVD objectives. Figure 9: Customer responses to the urgency and relevancy of the RESOLVD value propositions. The DSOs' responses showed that the RESOLVD value propositions were relevant in overcoming the existing and future challenges at the LV grid level. However, the urgency of the value proposed varied among the respondents. In general, the responses from the customer survey (DSOs) and S&R analysis (mostly technology developers) complemented each other on most of the value propositions. This indicates synergy between technology developers' expectations pertaining to the RESOLVD solution and market needs. However, the results from both methods had small variations on a couple of the value propositions.