#  1\. INTRODUCTION & PROJECT BACKGROUND

##  1.1. Scope of the document

This report presents the data management life cycle for the data to be
collected, processed and/or generated by the InterFlex project.

As part of making research data findable, accessible, interoperable and re-
usable (FAIR), the deliverable will include information on:

  * The handling of research data during & after the end of the project 

  

  * What data will be collected, processed and/or generated 

  

  * Which methodology & standards will be applied 

  

  * Whether data will be shared/made open access and 

  

  * How data will be curated & preserved (including after the end of the project). 

  

Within the InterFlex project, it may be necessary to limit access to certain
information, in accordance with the article 12 of the Electricity Directive by
guaranteeing that commercially sensitive information obtained in the course of
carrying out their business shall remain confidential, and that information
disclosed regarding their activities, which may be commercially advantageous,
shall be made available in a non-discriminatory manner.

The document will be updated over the course of the project whenever
significant changes arise, such as (but not limited to) new data, changes in
consortium policies (e.g. new innovation potential, decision to file for a
patent); changes in consortium composition and external factors (e.g. new
consortium members joining or old members leaving).

The DMP will be updated as a minimum in time with the periodic
evaluation/assessment of the project: M18 and M36.

##  1.2. Notations, abbreviations and acronyms

The table below provides an overview of the notations, abbreviations and
acronyms used in the document.

##  1.3. EU Expectations from InterFlex

InterFlex is a response to the Horizon 2020 Call for proposals LCE-02-2016
(“Demonstration of smart grid, storage and system integration technologies
with increasing share of renewables: distribution system”).

This Call addresses the challenges of the distribution system operators in
modernizing their systems and business models in order to be able to support
the integration of distributed renewable energy sources into the energy mix.
Within this context, the LCE-02-2016 Call promotes the development of
technologies with a high TRL (technology readiness level) into a higher one.

InterFlex explores pathways to adapt and modernize the electric distribution
system in line with the objectives of the 2020 and 2030 climate-energy
packages of the European Commission. Six demonstration projects are conducted
in five EU Member States (Czech Republic, France, Germany, The Netherlands and
Sweden) in order to provide deep insights into the market and development
potential of the orientations that were given by the call for proposals, i.e.,
demand-response, smart grid, storage and energy system integration.

With Enedis as the global coordinator and ČEZ Distribuce as the technical
director, InterFlex relies on a set of innovative use cases.

Six industry-scale demonstrators are being set up in the participating
European countries:

Through the different demonstration projects, InterFlex will assess how the
integration of the new solutions can lead to a local energy optimisation.
Technically speaking, the success of these demonstrations requires that some
of the new solutions, which are today at TRLs 57, are further developed
reaching TRLs 7-9 to be deployed in real-life conditions. This allows new
business models and contractual relationships to be evaluated between the DSOs
and the market players.

**Environment** : Through the optimisation of the local energy system, the
project generates benefits in terms of increased energy efficiency (load
shifts to off peak hours; optimized selfconsumption in case of prosumers,
increased awareness leading to active DSM and reduced electricity
consumption), power generation optimization (peak shaving, avoiding
electricity generation from carbonized peak load generation units) and
increased share of renewables (optimized integration of intermittent renewable
energy sources), resulting in the overall reduction of GHG emissions.

**Socio-economic** : The project stimulates the development of new services
for end-customers allowing for instance the development of demand response
service packages for small and large consumers as well as prosumers. The
provision of community storage solutions or the optimal use of multiple source
flexibilities should help to decrease the electricity bill without any
noticeable impact on the supply quality.

**Policy** : The Use cases of the project will help to

  * Formulate recommendations for micro grid operation (control schemes and observability), 

  

  * Elaborate an appropriate regulatory framework for self- consumption and storage solutions (community or individual residential storage) 

  

  * Provide guidelines on the participation of distributed resources in DSO operations (modifications of grid codes). 

  

_Figure 1: InterFlex Demo Map_

#  2\. DATA SUMMARY

##  2.1. Purpose of the data collection

The goal of the data collection is to design a structure for data
classification and define level of confidentiality and access rights for each
subcategory:

  * To evaluate the technical and financial performance of the 6 demonstrators and the InterFlex project 

  

  * To communicate properly on the demonstrators and the results of the InterFlex project 

  

  * To make sure the 6 demonstrators methodology and results are exploitable and replicable 

  

  * Without affecting the confidentiality of some data  1  2 

  

Data Subcategories

1

Level of

confidentiality

Owner of data

Recipient

2

Perime

ter of access

rights

Dissemination perimeter of data subcategories:

For each subcategory and each applicant recipien

t, owner can choose between:

Sharing detailed data

Sharing aggregated or

equivalent data

No sharing

_Figure 2 : Level of confidentiality and access rights_

Detailed system data need to be transformed before being exchanged with non-
authorized recipient:

  * **Detailed data** : Raw data 

  

  * **Aggregated data** : Aggregated data: Data based on detailed data that are aggregated at a sufficient level so that raw data can’t be identified(statistical law) with respect to competition laws 

  

  * **Equivalent data** : Data based on detailed data that are in an anonymous form or with modified values so that raw data can’t be identified 

  

##  2.2. Types and formats of generated or collected data

Different types of data are collected or generated within the InterFlex
Project:

Table 2: Data classification

##  2.3. Data Structure and utility

The data structure has been defined gathering and compiling all project data
and processes. It may evolve and be updated during the life of the project.

The actual structure for Actors and Data for the InterFlex project are listed
in the tables below:  
  
<table>  
<tr>  
<th>

**_Categories_ **

</th>  
<th>

**_Type_ **

</th>  
<th>

**_Subcategories_ **

</th>  
<th>

**_Definition and utility_ **

</th>  
<th>

**_Example_ **

</th> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

DSO

</td>  
<td>

Responsible for operating, ensuring the maintenance of and, if necessary,
developing the distribution system in a given area

</td>  
<td>

Avacon, CEZ, E.ON, Enexis, Enedis

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

Industrial partner

</td>  
<td>

All industrial partners involved in Interflex project at a DEMO level

</td>  
<td>

  * GE 

  

  * Siemens 

  

  * Schneider … 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

University and research partner

</td>  
<td>

All university or research partners

involved in Interflex project at a

DEMO level

</td>  
<td>

  * RWTH 

  

  * AIT etc 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

Retailer

</td>  
<td>

Licensed supplier of electricity to an end-user

</td>  
<td>

\- EDF - Engie...

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

Legal Client

</td>  
<td>

A legal client of a DSO that is involved at Demo scale

</td>  
<td>

  * Company producer 

  

  * Municipalities 

  

  * Tertiary service providers 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

Role

</td>  
<td>

Physical client

</td>  
<td>

A physical client of a DSO that is involved at Demo scale

</td>  
<td>

\- Residential client

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

Charging

facilities

</td>  
<td>

Facilities to charge electrical vehicles

</td>  
<td>

\- Charging facilities

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

DER installation

</td>  
<td>

Power plant that use renewable technology and are owned by a legal person

</td>  
<td>

  * Photovoltaics panels 

  

  * Biomass farm 

  

  * Wind power, … 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

In house device

</td>  
<td>

All devices working on electricity that can be find in a customer's dwelling.

</td>  
<td>

  * Heater 

  

  * Meter 

  

  * Local display 

  

  * Customer's battery 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

Communication

infrastructure

</td>  
<td>

All the infrastructure that are used for communication at all level (from

customer's place to power

command)

</td>  
<td>

\- Modem - Routers

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

Network device

</td>  
<td>

All devices placed on MV/LV network

for monitoring or gathering information on grid's situation or electrical
parameters values. It also include the IS associated

</td>  
<td>

  * Secondary Substation control infrastructure 

  

  * RTU : Remote terminal units 

  

  * Circuits breakers 

  

  * sensors 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

IS IT

</td>  
<td>

All the hardware and software associated, used at power command to control and
monitor the network

</td>  
<td>

  * SCADA 

  

  * Central database 

  

  * Control operation center 

  

</td> </tr>  
<tr>  
<td>

Actors

</td>  
<td>

System

</td>  
<td>

Interactive communication device

</td>  
<td>

All device used to interact with customers in order to involved him in the
Demo

</td>  
<td>

  * Web portal 

  

  * Display used for communication 

  

</td> </tr> </table>

_Table 3: List of actors_  
  
<table>  
<tr>  
<th>

**_Categories_ **

</th>  
<th>

**_Type_ **

</th>  
<th>

**_Subcategories_ **

</th>  
<th>

**_Definition and utility_ **

</th>  
<th>

**_Example_ **

</th> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Document

</td>  
<td>

Internal

document

</td>  
<td>

All the documentation made by Demo to run operation, to monitor and conduct
the project's good development

</td>  
<td>

  * Meeting minutes 

  

  * Report on the cost's impact of selected flexibility plans 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Document

</td>  
<td>

Interflex deliverable

</td>  
<td>

All the deliverables that Demo have to produce during the project's time as
agreed in the DOW

</td>  
<td>

  * Risk analysis 

  

  * Documentation on KPI 

  

  * Detailed use case - Report on technical 

  

experimentation, market research,

…

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Document

</td>  
<td>

Communication material

</td>  
<td>

All the documentation that describe the project to the public and can be put
on the future website

</td>  
<td>

  * Purpose of the DEMO (leaflet) 

  

  * Brief description of use case 

  

  * Location of use case 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Financial data

</td>  
<td>

Project financial data

</td>  
<td>

All the financial data that are produced during the project and that are used
to make financial report for European Commission and internal report

</td>  
<td>

  * Invoices 

  

  * Cost and time imputation 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Financial data

</td>  
<td>

Solution cost and selling price

</td>  
<td>

All the financial data that can be made concerning estimation prices of
solution for replication

</td>  
<td>

  * Unit product cost of hardware developed by Demo 

  

  * Sell price of the solution develop 

  

(software,…)

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Condition parameter

</td>  
<td>

All the external parameters that may influence the success of the use case

</td>  
<td>

  * Weather 

  

  * Time of day 

  

  * Day of week … 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Scenario assumption

</td>  
<td>

All the stated parameters that are necessary to determinate a scenario for the
use case

</td>  
<td>

  * Location of islanding 

  

  * Experiment's location 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Electrical parameter

</td>  
<td>

All the electrical parameters that are used to supervise the network and its
good state

</td>  
<td>

  * Intensity 

  

  * Voltage 

  

  * Frequency 

  

  * Quality 

  

</td> </tr> </table>  
<table>  
<tr>  
<th>

Data

</th>  
<th>

Parameter

</th>  
<th>

Algorithm, formula, rule, specific model

</th>  
<th>

All the intellectual data that are created during the project to made
software's contents

</th>  
<th>

  * Algorithm to optimize flexibility plan 

  

  * Simulation to determine location 

  

of circuit breaker

  * Voltage regulation algorithm 

  

</th> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Optimized value

</td>  
<td>

Values of parameters that optimized the use case or the demo‘s performance

</td>  
<td>

\- Optimization time of islanding

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Forecast data

</td>  
<td>

All the data used to forecast consumption or production of customer

</td>  
<td>

\- Forecast customer's consumption - Forecast photovoltaic panels' production

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Facility data

</td>  
<td>

Network topology

</td>  
<td>

All information on network devices and their location and interaction, mainly
coming from GIS (Geographic

Information System)

</td>  
<td>

  * Map of the network 

  

  * Substations location 

  

  * All the other data found in the GIS 

  

(Geographical Information System)

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Facility data

</td>  
<td>

Network state

</td>  
<td>

All information concerning the network's status (global or local) at a precise
moment useful to monitor the network

</td>  
<td>

  * Feeding situation in a distribution area 

  

  * State of network regarding Limit value violation 

  

  * Location of constraint 

  

  * Flexibility needs of DSO 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Facility data

</td>  
<td>

Customer's meter state and output

</td>  
<td>

All the information concerning customer’s meter state and outputs information

</td>  
<td>

\- Customer’s consumption or production

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Facility data

</td>  
<td>

Other device state and output

</td>  
<td>

All the information concerning device's state and outputs information

</td>  
<td>

  * State of charge of batteries 

  

  * Consumption data coming from meter 

  

  * Production data coming from meter 

  

  * State of charge of storage 

  

components

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Information exchanged between IS or sent to device

</td>  
<td>

All automated information sent between facilities in order to send information
or order for monitoring

</td>  
<td>

  * Order sent to breaker devices (open, close,…) 

  

  * Information on local network status coming from sensors - Order and roadmap sent to network devices (batteries, aggregator,…) 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Parameter

</td>  
<td>

Detailed specification on devices

</td>  
<td>

All detailed information (reference components, specification, process,…)
useful to build the devices

</td>  
<td>

  * Detailed specification of the telecommunication infrastructure 

  

  * Detailed specification of interactive sensor network 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Network data

</td>  
<td>

Network topology

</td>  
<td>

All information on network devices and their location and interaction, mainly
coming from GIS (Geographic

Information System)

</td>  
<td>

  * Map of the network 

  

  * Substations location 

  

  * All the other data found in the GIS 

  

(Geographical Information System)

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Network data

</td>  
<td>

Network state

</td>  
<td>

All information concerning the network's status (global or local) at a precise
moment useful to monitor the network

</td>  
<td>

  * Feeding situation in a distribution area 

  

  * State of network regarding Limit value violation 

  

  * Location of constraint 

  

  * Flexibility needs of DSO 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

KPI

</td>  
<td>

Data for KPI

(input raw data)

</td>  
<td>

All raw data that are used to calculate the final KPI

</td>  
<td>

  * Duration of experiment 

  

  * Customer response to DSO's 

  

demand

  * Electrical parameter used for KPI 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

KPI

</td>  
<td>

KPI (KPI values)

</td>  
<td>

All the KPI values and the way to calculate them

</td>  
<td>

  * Economic KPI 

  

  * System Efficiency KPI 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Customer data

</td>  
<td>

Customer

contract’s data

</td>  
<td>

All the data in customer's contact

that are used for contact or make payment

</td>  
<td>

  * Address 

  

  * Phone number 

  

  * Bank account details 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Customer data

</td>  
<td>

Information sent to /received from customer

</td>  
<td>

All the information and data that are exchanged between the DEMO and the
customer in order to involve customer in the experiment

</td>  
<td>

  * Customer's response to DSO's request to reduce consumption - Information and data available to customer in order to visualize its consumption 

  

  * Advices and encouragement sent to encourage a smart consumption 

  

</td> </tr>  
<tr>  
<td>

Data

</td>  
<td>

Customer data

</td>  
<td>

Customer

analysis (profile analysis, studies on client reactivity)

</td>  
<td>

All the data that are produced in order to better understand the customer's
behaviour regarding the possibility to adopt smarter habits in their
electricity consumption

</td>  
<td>

  * Customer's typology and behaviour patterns 

  

  * Analysis on customer's response to DSO's request 

  

</td> </tr> </table>

_Table 4: List of data_

#  3\. FAIR DATA

##  3.1. Making data findable, including provisions for metadata

In order to make data findable and usable, regarding the level of access
rights, rules have been defined to identify the data.

###  KPIs

####  Data concerned

  * All demo KPIs 

  

  * Common KPIs 

  

####  Characteristics

  * KPI values were created in order to be shared and published outside the Interflex project 

  

  * KPIs reflect the results of the demos and the InterFlex Project and are one of the main tools of the Technical Management 

  

  * For each KPI, the level of dissemination has been defined in the deliverable ‘D2.2 MinimalSetOfKPIs_CEZd_InterFlex_V1.0’ 

  

####  Rules/ Identification/Versioning

  * Decision has been taken that only calculated values will be put inside the data clearing house located on the Project Intranet. The data collection frequency and responsibilities for data collection are defined for each KPI in the deliverable ‘D2.2 MinimalSetOfKPIs_CEZd_InterFlex_V1.0’ o Data name 

    * Data ID 

  

    * Methodology for Data collection o Source/tools/Instruments for Data collection o Location of Data collection o Frequency of data collection o Data responsible data collection o KPI ID o KPI Name 

  

  

  * Each responsible for WP KPI collection is the WPL who collects the different KPIs in the database stored on the InterFlex Intranet, so the Technical Director can assess the project thanks to the KPI collection. 

  

  * Each Raw data and calculated value has an Object Identifier defined in deliverable ‘D2.2 MinimalSetOfKPIs_CEZd_InterFlex_V1.0’. 

  

###  InterFlex Deliverables

**_Data concerned_ **

\- List of deliverables defined in the Grant Agreement (or its amended
version)

####  Characteristics

\- Depending on the deliverable, perimeter of dissemination can be different -
A level of dissemination is already pre-defined in the Grant Agreement

####  Rules/ Identification/Versioning

  * Level of dissemination is chosen by the author and Technical committee validates the choice. Main deliverables and appendices may have different levels of confidentiality, especially if appendices are more detailed 

  

  * The deliverables are available on the Project Intranet and on the website for public audience 

  

  * Versioning and nomenclatures are defined in the deliverable ‘D10.1 ProjectManagementPlan_Enedis_InterFlex_V2.0’ 

  

###  Demo’s local Data

####  Data concerned

  * Internal documents 

  

  * Electrical parameters 

  

  * Forecast data 

  

  * Device state and outputs and information exchanged between facilities 

  

  * Customer analyses (profile analyses, studies on client reactivity…) 

  

####  Characteristics

  * Data used to run each of the Demos on a daily basis 

  

  * Data are with low added value outside source Demo, as Demos are running separately without overlap 

  

####  Rules to be applied

  * Data should stay at Demo level and be used only by Demo partners for the achievement of their activity 

  

  * If another partner outside Demo needs these data, a written request and explanation should be provided about the way he is going to use the data (Agreement form) 

  

> Sample data in an anonymous format can be sent only for illustration >
> Providing aggregated data should be the rule

  * A global description will be integrated inside deliverable 

  

###  Project Financial Data

####  Data concerned

  * Invoices 

  

  * Time spendings/imputations 

  

  * Cost/price 

  

  * Company internal financial documents 

  

####  Characteristics

  * Data can be at different levels of details 

  

  * Detailed data (cost by unit) are extremely sensitive 

  

  * Demos need to send financial data to Coordinator who will aggregates data to present a global cost statement covering all Demos and general expenses of each partner (for internal financial report) broken down to individual WPs 

  

####  Rules to be applied

  * Detailed data should stay in partner's accounting system 

  

  * Data sent to the Coordinator should be in the detailed level described in the template provided by Coordinator 

  

  * All data sent to Coordinator must be kept strictly confidential and must not be disseminated 

  

  * Coordinator aggregates data to present to the consortium 

  

  * Company internal financial information is not shared 

  

###  Network Data

####  Data concerned

  * Network topology 

  

  * Network state 

  

####  Characteristics

  * Network topology GIS information and Network state are highly confidential and sensitive 

  

  * Network state can be sensitive information as it can reveal grid's weakness and vulnerability 

  

####  Rules to be applied

  * Network topology with GIS information must not be shared except between DSOs 

  

  * If another partner needs network data, a written request and explanation should be provided about the way he is going to use the data (Agreement form) 

  

> Data in an anonymous format : equivalent data without indication of location
> can be sent

> Providing aggregated data should be the rule

###  Demo Customer Data

**_Data concerned_ **

  * Customer's meter data 

  

  * Customer's contract data 

  

**_Characteristics_ **

  * All this data are strictly under personal data protection (European and national laws) 

  

  * Detailed identification data (address, phone number,…) are sensitive information and must be secured 

  

**_Rules to be applied_ **

  * Customer's contract must never be sent 

  

  * As stated in laws : 

  

> Customer must have an access to this data

> Data must be protected and traceability of the use must be made

> Data can't be disclosed to anyone without the full consent of customers on
> usage and access rights

  * All this information has to be clearly stated in the customer's contract that is signed to enter project 

  

  * in order to send information to other partners if the need is clearly established, these data have to be delivered in an anonymous format 

  

(equivalent data) or aggregated format

  * The DSO must ensure to record these data in compliance with their national data protection regulations 

  

##  3.2. Making data openly accessible

Data that are used to manage the project within the consortium are stored on
the Project Intranet with a private login and password. This intranet is used
as a working tool for the sharing of documents related to InterFlex and
consists of a private area, accessible online to the project partners.

It allows the safe access to project information and reports, circulation of
preparatory and internal work, online exchanges and virtual communication
tools such as shared Agenda, Instant Messaging etc.

Groups and access roles have been defined in order to assure clearly
identified access rights.

_Figure 3: Tree view of the access rights of the Intranet_

Data that are public are accessible on the project website. Key words and
search tool are available in order to make the data more accessible.

Confidential data are identified with a confidential tag in order to protect
them.

The access rights per actors per data is described in the table below:

D2.4 Da

t

a Management Plan

Interflex

–

GA N°731289

Page

20

Table 5: Data classification

##  3.3. Making data interoperable

In order to identify and aggregate the data in an interoperable way the
InterFlex project uses the SGAM framework/ Use case methodology approach and
also the IEC PAS 62559 based template to describe in detail the Use Cases. See
deliverable D2.1.

The SGAM framework and its methodology are intended to present the design of
Smart Grid use cases in an architectural but solution and technology-neutral
manner.

The SGAM framework consists of five layers representing business objectives
and processes, functions, information exchange and models, communication
protocols and components. These five layers represent an abstract and
condensed version of the GWAC interoperability categories. Each layer covers
the smart grid plane, which is spanned by electrical domains and information
management zones. The intention of this model is to represent on which zones
of information management interactions between domains take place. It allows
the presentation of the current state of implementations in the electrical
grid, but furthermore to depict the evolution to future smart grid scenarios
by supporting the principles universality, localization, consistency,
flexibility and interoperability

InterFlex aims to get information on:

  1. Description of the Use Case 

  

  2. Diagrams of the Use Case 

  

  3. Technical data - Actors 

  

  4. Step by Step Analysis of Use Case (can be extended by detailed info on “information exchanged”) 

  

  5. Information exchanged 

  

  

Moreover, the WP3 focuses on defining an interoperable API for IT systems
involved in the flexibility transactions with cybersecurity constraints
(D3.6), Interoperability and interchangeability validation results (D3.7), and
Scalability and replicability analyses for all the use cases (D3.8).

##  3.4. Increase data re-use (through clarifying licenses)

In order to enable and promote data re-use, all data provided need to take the
following questions in a reasonable way into account and must be specified in
the Exploitation Plan of the project (D4.7, D4.8, i.e., 1  st  and 2  nd
version of the Exploitation Plan of the project results):

  * How will the data be licensed to permit the widest possible re-use? 

  

  * When will the data be made available for re-use? If an embargo is sought to give time to publish or seek patents, specify why and how long this will apply, bearing in mind that research data should be made available as soon as possible. 

  

  * Are the data produced and/or used in the project useable by third parties, in particular after the end of the project? If the re-use of some data is restricted, explain why. 

  

  * How long is it intended that the data remains re-usable? 

  

  * Are data quality assurance processes described? 

  

#  4\. ALLOCATION OF RESOURCES

Enedis as Project Coordinator of the InterFlex project is responsible for data
management of the project.

All relevant data such as KPI results, publication and deliverables must be
accessible at least 5 years after the end of the project. As such, the
Intranet and Internet platforms will be available and maintained by Enedis
during this period from 2020 until 2024. The corresponding estimated expenses
are shown hereunder:

\- Intranet licences: 96€/year/licences. 1 licence for each of the 20 partners
(TBC) - Internet Hosting and maintenance: 40€/month  
  
<table>  
<tr>  
<th>

**Cost category**

</th>  
<th>

**Year 2020**

</th>  
<th>

**Year 2021**

</th>  
<th>

**Year 2022**

</th>  
<th>

**Year 2023**

</th>  
<th>

**Year 2024**

</th>  
<th>

**Total**

</th> </tr>  
<tr>  
<td>

Intranet

</td>  
<td>

1 920 €

</td>  
<td>

1 920 €

</td>  
<td>

1 920 €

</td>  
<td>

1 920 €

</td>  
<td>

1 920 €

</td>  
<td>

**9 600 €**

</td> </tr>  
<tr>  
<td>

Internet

</td>  
<td>

480 €

</td>  
<td>

480 €

</td>  
<td>

480 €

</td>  
<td>

480 €

</td>  
<td>

480 €

</td>  
<td>

**2 400 €**

</td> </tr>  
<tr>  
<td>

**Total direct costs**

</td>  
<td>

**2 400 €**

</td>  
<td>

**2 400 €**

</td>  
<td>

**2 400 €**

</td>  
<td>

**2 400 €**

</td>  
<td>

**2 400 €**

</td>  
<td>

**12 000 €**

</td> </tr> </table>

_Table 6 : Direct data management costs excluding HR after the end of the
project_

#  5\. DATA SECURITY AND ETHICAL ASPECTS

##  5.1. Data security

Based on common works and agreements among GWP and Demo leaders, each
subcategory of data was assessed with three levels of confidentiality in order
to ensure data security.

Depending on the constraints applying to these types of data (laws, internal
rules…), it is possible to apply a level of confidentiality as followed:

\- Level 0:

  * Detailed data can never be shared 

  

  * Aggregated data or equivalent data can be shared - Level 1: 

  

  * Detailed data can be shared with some partners upon request and dedicated agreement 

  

  * No restriction on aggregated data or equivalent data - Level 2: 

  

  * No restriction whatsoever. 

  

##  5.2. Ethical aspects

Ethics requirements in the protection of personal data must be taken into
account. Indeed, within the context of Interflex demos and exploitation of
related results, partners will be collecting or processing personal data.

As such, the D1.1 Ethics POPD deliverable (protection of personal data)
specifies for each partner:

  * Certification by their competent Data Protection Authority of compliance with applicable local and European laws, 

  

  * Detailed information on the procedures that will be implemented for data collection, storage, protection, retention and destruction 

  

  * where applicable, providing templates of consent forms to be given out to customers whose personal data may collected and used 

  

#  6\. APPENDIX

List of InterFlex Common KPIs  
  
<table>  
<tr>  
<th>

**Interflex Project KPI**

</th>  
<th>

**KPI ID**

</th>  
<th>

**KPI TYPE**

</th>  
<th>

**KPI Description**

</th> </tr>  
<tr>  
<td>

Flexibility

</td>  
<td>

WP2.2_KPI_1

</td>  
<td>

Technical

</td>  
<td>

Flexible power that can be used for balancing specific grid segment.

</td> </tr>  
<tr>  
<td>

Hosting capacity

</td>  
<td>

WP2.2_KPI_2

</td>  
<td>

Technical

</td>  
<td>

Percentage increase of network hosting capacity for DER.

</td> </tr>  
<tr>  
<td>

Islanding

</td>  
<td>

WP2.2_KPI_3

</td>  
<td>

Technical

</td>  
<td>

Capacity of the energy system to switch to islanding whilst keeping the power
quality requirement.

</td> </tr>  
<tr>  
<td>

Customer recruitment

</td>  
<td>

WP2.2_KPI_4

</td>  
<td>

Social

</td>  
<td>

Measure whether demos are managing to recruit enough customer bases in order
to attain demo objectives.

</td> </tr>  
<tr>  
<td>

Active participation

</td>  
<td>

WP2.2_KPI_5

</td>  
<td>

Social

</td>  
<td>

Reflects how versatile the demos are in leveraging flexibility from different
technologies.

</td> </tr> </table>