#  Research data

Generally speaking, research data refers to data collected, processed,
observed, or generated within a project with the aim to produce original
research results. Data are processed, organized, structured and interpreted in
order to determine their true meaning and becoming in this way valuable
information.

In the framework of research activities, data can be divided into different
categories, depending on their scope, their origin as well as their
processing. For instance, very often research data are classified in:

  * Observational data 

  

  * Experimental data 

  

  * Simulation data 

  

  * Derived data 

  

Actually, observational data refers to data captured in real-time (e.g. sensor
data, survey data, sample data etc.), experimental data refers to data
obtained from laboratory equipment (e.g data resulting from validation in the
field) whereas simulation data indicates data created from numerical models.
Derived data are those data generated from existing data.

In this context, research data may include different formats:

  * Text/word documents, spreadsheets, questionnaire, transcripts 

  

  * Laboratory/Field notebooks, diaries, codebook 

  

  * Audios, videos, pictures, photographs 

  

  * Test responses 

  

  * Slides 

  

  * Artifacts, specimen, samples 

  

  * Collection of digital objects acquired and generated during the research process  Data files 

  

  * Database contents 

  

  * Protocols, procedures 

  

  * Models, algorithms, software codes, scripts, log files, simulations 

  

  * Methodologies and workflows 

  

  * Standard operating procedures and protocols  Etc. 

  

According to the key principles for research data management and in particular
to the “ _Guidelines on FAIR Data Management in Horizon 2020_ ”, research data
1  must be _findable_ , _accessible_ , _interoperable_ , _re-usable_ . The
FAIR data guiding principles are reported in the following  2  :

  1. To be **Findable** any Data Object should be uniquely and persistently identifiable 

    1. The same Data Object should be re-findable at any point in time, thus Data Objects should be **persistent** , with emphasis on their metadata 

  

    2. A Data Object should minimally contain basic machine actionable metadata that allows it to be distinguished from other Data Objects 

  

    3. Identifiers for any concept used in Data Objects should therefore be **Unique** and **Persistent**

  
  

  

  2. Data is **Accessible** in that it can be always obtained by machines and humans 

    1. Upon appropriate authorization 

  

    2. Through a well-defined protocol 

  

    3. Thus, machines and humans alike will be able to judge the actual accessibilty of each Data Object. 

  
  

  

  3. Data Objects can be **Interoperable** only if: 

    1. (Meta) data is machine-actionable 

  

    2. (Meta) data formats utilize shared vocabularies and/or ontologies 

  

    3. (Meta) data within the Data Object should thus be both syntactically parseable and semantically machine-accessible 

  
  

  

  4. For Data Objects to be **Re-usable** additional criteria are: 

    1. Data Objects should be compliant with principles 1-3 

  

    2. (Meta) data should be sufficiently well-described and rich that it can be automatically (or with minimal human effort) linked or integrated, like-with-like, with other data sources 4.3 Published Data Objects should refer to their sources with rich enough metadata and provenance to enable proper citation 

  
  

  

  

After having investigated the aforementioned aspects, it was decided that the
data management plan of E-LOBSTER will be based on some key elements  3  :

**Dataset reference and name:** An identifier has to be produced for each
dataset. In particular, the technical data related to simulations, validation
through laboratory tests, validation in the field (WP1, WP2, WP4, WP5) will be
referred by using a code composed on the date (year, month, day, hour e.g.
20181101_0845) and a name.

**Data set description:** The data that will be generated or collected during
E-LOBSTER will be described, as well as their origin (in case they are
collected). A readme.txt file will allow to have the basic information.

**Standards and metadata:** Reference to existing suitable standards of the
discipline. If these do not exist, an outline on how and what metadata will be
created has to be given.

**Data sharing** : Description of how data will be shared, including access
procedures, embargo periods (if any) will be provided. In case the dataset
cannot be shared, the reasons for this should be mentioned (e.g. IPR, personal
data, intellectual property, commercial, security-related).

**Archiving and preservation (including storage and backup):** Procedures that
will be put in place for long-term preservation of the data will be described.
Indication of how long the data should be preserved, what is its approximated
end volume.

#  Open Access

##  Measures to provide Open Access to peer-reviewed scientific publications

Fully in line with the Grant Agreement, each E-LOBSTER beneficiary will ensure
open access (free of charge online access for any user) to all peer-reviewed
scientific publications relating to its results.

In particular, it will:

  1. as soon as possible and at the latest on publication, deposit a machine-readable electronic copy of the published version or final peer-reviewed manuscript accepted for publication in a repository for scientific publications; 

  

  

Moreover, the E_LOBSTER beneficiary will aim to deposit at the same time the
research data needed to validate the results presented in the deposited
scientific publications.

  2. ensure open access to the deposited publication — via the repository — at the latest:  on publication, if an electronic version is available for free via the publisher, or  within six months of publication in any other case. 

  

  3. ensure open access — via the repository — to the bibliographic metadata that identify the deposited publication. 

  

  

The bibliographic metadata must be in a standard format and must include all
of the following: - European Union (EU)

  * Horizon 2020 

  

  * Research and Innovation Action (RIA) 

  

  * E-LOBSTER 

  

  * Grant Agreement No 774392”. 

  

  * the publication date 

  

  * the length of embargo period if applicable 

  

  * Information about the persistent identifier 

  

##  Management of the Research Data generated and/or collected during the
project

The E-LOBSTER project recognizes the value of regulating research data
management issues. Accordingly, in line with the Grant Agreement, the
beneficiaries will, to the extent possible, deposit the research data needed
to validate the results presented in the deposited publications in a clear and
transparent manner. However, they have opted, after a careful have, not to
take part to the Pilot Action on Open Research Data. The reason for this is
that data that will underlie the project’s activities may be of sensitive
nature and their protection could have a relevant importance to guarantee the
commercial perspectives in particular of the industrial partners. These data
will be put at the disposal of relevant consortium partners as well as to the
member of the stakeholder groups after having signed a devoted Non-Disclosure-
Agreement (NDA). However, they will not be disclosed (with the exception of
some cases) in order to safeguard the legitimate interests of all involved
entities.

In the following chapters, the data management plan at project level as well
as the individual partner data management plan will be presented.

#  Data management plan at project level

In this chapter, an overview of the data management plan at project level will
be presented.

In particular, in the table below for each E-LOBSTER WP, the following
information will be provided:

  * Number and name of the task 

  

  * Description of the data collected/generated at task level 

  

  * Partner owner of the data 

  

  * Format 

  

  * Confidential level. 

  

More accurate information will be presented in the next chapter, where the
data management plan at individual partner level will be illustrated.

**Table 1: Overview of E-LOBSTER Data management plan at project level**  
  
<table>  
<tr>  
<th>

**WP1 Analysis of energy losses for fully integrated power distribution and
transport networks**

</th>  
<th>

</th>  
<th>

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T1.1:

</td>  
<td>

Analysis of the energy losses within the traction chain and identification of
measures for energy losses prevention

</td>  
<td>

-Software code of the bespoke simulator for Energy losses evaluation 

-Dataset related to Metro of Madrid to be used for the analysis (MDM). -Dataset related to the outcomes of simulations on power losses with various feeding arrangement based on data of metro of Madrid 

-Different datasets related to simulations 

for the validation of the tool for the railway network

\- Modelling of the railway traction system

</td>  
<td>

MDM, UOB

</td>  
<td>

.xls, .dat, .mat,

jpeg, .txt., .pdf, .docx, .ppt

</td>  
<td>

Yes

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

T1.2

</td>  
<td>

Analysis of the energy losses within the power distribution grid and
identification of measures for energy losses prevention

</td>  
<td>

-Dataset related to parameters monitoring of the power distribution network 

-Dataset related to Metro of Madrid to be used for the analysis (MDM). 

-Modelling and simulation of the power distribution networks and components -Software code of the smart Grid simulator 

</td>  
<td>

UNEW, RINA-C,

MDM

</td>  
<td>

.xls, .dat, .mat,

jpeg, .txt., .pdf, .docx, .ppt

</td>  
<td>

Yes

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

T1.3

</td>  
<td>

Design of an advanced simulator for rail electrification systems fully
integrated with the power distribution system via a SOP and a DC bus
connection

</td>  
<td>

-Software code of the advanced simulator 

-Dataset related to simulator 

-Combination and Modelling of both power distribution networks and railway networks 

\- Control strategy of the sSOP

</td>  
<td>

MDM, UOB, UNEW, TPS

</td>  
<td>

.xls, .dat, .mat,

jpeg, .txt., .docx, .pdf, .ppt

</td>  
<td>

Yes

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

T1.4

</td>  
<td>

Impact of consumer behaviour on network losses

</td>  
<td>

\- Data about analysis of consumer behaviour and tools for reduction of energy
consumption

</td>  
<td>

FFE, RINA-C, UOB,

UNEW

</td>  
<td>

.pdf, .docx

</td>  
<td>

No

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

Page  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

-Data related to the analysis of market, socioeconomic, legal and institutional framework situations 

</th>  
<th>

</th>  
<th>

</th>  
<th>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**WP2 - Enabling technologies**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T2.1

</td>  
<td>

Electrified Transport and distribution network key elements and main
specification towards reduction of losses

</td>  
<td>

\- Data related to the analysis of the current situations in terms of energy
losses in the railway and power distribution networks,

state of the art of most suitable technologies for the losses reduction

(Handbook)

</td>  
<td>

UOB, RINA-C, TPS,

FFE,SPD,LIBAL,

RSSB

</td>  
<td>

.pdf, .docx

</td>  
<td>

No

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

T2.2

</td>  
<td>

Smart SOP (Soft Open

Point) Power Electronics Specifications and interaction with smart metering

</td>  
<td>

-Software code based on PLECS for the simulations of sSOP performance -Data related to the simulations of the sSOP 

-Specifications of the sSOP 

</td>  
<td>

TPS

</td>  
<td>

.PLECS, .pdf, .dat, .mat, .docx

</td>  
<td>

Yes

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

T2.3

</td>  
<td>

Identification, design and development of the most suitable Electrical Storage
for the mutual benefit interexchange of electricity

</td>  
<td>

-Custom made software code based on C# language for the simulations of the storage 

system performance

-Data related to the simulations of the storage system 

-Specifications of the storage system 

</td>  
<td>

LIBAL

</td>  
<td>

C#, .dat, .mat, .pdf, .docx, .txt

</td>  
<td>

Yes

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

T2.4

</td>  
<td>

Design and development of

Power Electronics prototypes

</td>  
<td>

\- Schema and design of the power electronic prototypes

</td>  
<td>

TPS, LIBAL

</td>  
<td>

.pdf, .docx, .vsd

</td>  
<td>

Yes

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**WP3 Policy, regulation and standards**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T3.1

</td>  
<td>

Identification of standard operating parameters and definitions towards future
marketability

</td>  
<td>

-Repository gathering information on existing standards and their classification 

</td>  
<td>

RSSB, FFE, MDM, RINA-C, UITP

</td>  
<td>

.pdf, .docx, .xls

</td>  
<td>

No

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

Page  
  
<table>  
<tr>  
<th>

T3.2

</th>  
<th>

Policies for the support of the marketability of ELOBSTER Solution

</th>  
<th>

-Repository gathering information on existing policies and their classification - Data related to the three stakeholder workshops with the 2 Stakeholders Groups (DSOs and Transport manager) in close collaboration with WP6 (results of questionnaires, surveys, inputs etc). 

</th>  
<th>

RINA-C, RSSB, FFE, UITP

</th>  
<th>

.pdf, .docx, .xls, .ppt, online survey

</th>  
<th>

No

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

T3.3

</td>  
<td>

E-LOBSTER Compliancy to Energy and Transport

regulation

</td>  
<td>

\- Data related to the analysis of the compliancy with current regulations

</td>  
<td>

RSSB, LIBAL, FFE

</td>  
<td>

.pdf, .docx, .xls, .ppt,

</td>  
<td>

No

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

T3.4

</td>  
<td>

Standardization procedures towards E-LOBSTER marketability

</td>  
<td>

  * Data related to existing standards 

  

  * Data related to gap to be covered 

  

</td>  
<td>

FFE, RSSB

</td>  
<td>

.pdf, .docx, .xls, .ppt,

</td>  
<td>

No

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

T3.5

</td>  
<td>

Final proposals to unlock policies, standards and regulatory bottlenecks

</td>  
<td>

-Proposals for future standards 

</td>  
<td>

RSSB, LIBAL, RINA-C

</td>  
<td>

.pdf, .docx, .ppt,

</td>  
<td>

No

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

T3.5

</td>  
<td>

Best practices for the cyber security of transports and distribution network
smart management systems

</td>  
<td>

\- Guidelines and check list for cybersecurity of transports and distribution
network smart management systems

</td>  
<td>

RINA-C, RSSB, FFE, MDM)

</td>  
<td>

.pdf, .docx, .xls, .ppt,

</td>  
<td>

Yes

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

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

**WP4 S** ystem integration **– Measures and technologies for collaborative
rail and electricity networks for losses reduction and mutual benefit
interaction**

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T4.1

</td>  
<td>

Identification of correlations and all possible shared degrees-offreedom
between Railway Energy Network

and Distribution Electricity

Network

</td>  
<td>

-Data related to the analysis of the global electric framework including constraints and degrees-of-freedom of both the railway electric grid (i.e. train scheduling, overtension related to the start/stop of trains etc.) and the distribution network electric grid (i.e. quality of the power, frequency level, traditional daily supply scheduling etc… - ). 

</td>  
<td>

UOB, RINA-C,

UNEW, UOB,

MDM, RSSB, FFE

</td>  
<td>

.pdf, .docx, .xls, .ppt,

</td>  
<td>

No

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

T4.2

</th>  
<th>

Reference Architecture for Operational R+G (Railwayto-grid) Management

System

</th>  
<th>

  * Data and characterization of the different interfaces 

  

  * Data related to Functional analysis - Schemas of Physical System Architecture and Interface Architecture 

  

  * Data related to behavioral Architecture, concerning the system usability, applications and use cases 

  

</th>  
<th>

UNEW, RINAC, UOB, MDM, TPS

</th>  
<th>

.pdf, .docx, .xls, .ppt,

</th>  
<th>

Yes

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

T4.3

</td>  
<td>

Operational R+G

Management System

</td>  
<td>

  * Source code for the R+G Management system 

  

-Data related to the testing of the R+G 

Management system

-Design of the R+G Management system 

  * Algorithm related to the R+G 

  

Management system

-Data related to Testing of R+G 

Management system

</td>  
<td>

RINA-C, UNEW,

UOB, MDM, TPS,

LIBAL

</td>  
<td>

.pdf, .docx, .xls, .ppt, .dat, .mat Format of the source code for the R+G to
be still defined after the analysis of interfaces

</td>  
<td>

Yes

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

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

**WP5 - Demonstration and Validation of the E-LOBSTER**

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T5.1

</td>  
<td>

E-LOBSTER R+G

Management real-time simulation and validation in Hardware-in-the Loop

</td>  
<td>

\- Dataset referred to the real-time testing in the in the Smart Grid UNEW
Laboratory with physical/emulation platform

</td>  
<td>

UNEW, MDM,

TPS, UOB, FFE,

LIBAL

</td>  
<td>

.xls, .dat, .mat, jpeg, .txt., .docx, .pdf

</td>  
<td>

Yes

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

T5.2

</td>  
<td>

E-LOBSTER R+G

Management and power electronics laboratory validation and testing at

the Smart Grid Laboratory

</td>  
<td>

-Dataset referred to the laboratory Validation in the Smart Grid UNEW Laboratory of the R+G Management and power electronics devices 

</td>  
<td>

UNEW, MDM,

TPS, UOB, FFE,

LIBAL

</td>  
<td>

.xls, .dat, .mat, jpeg, .txt., .docx, .pdf

</td>  
<td>

Yes

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

T5.3

</td>  
<td>

Demonstration and field testing of the R+G

Management

</td>  
<td>

-Dataset referred to the Validation in the 

field in the Metro of Madrid of the R+G Management System and power

</td>  
<td>

MDM, RINA-C, FFE, TPS, LIBAL

</td>  
<td>

.xls, .dat, .mat,

jpeg, .txt., .docx, .pdf, .ppt

</td>  
<td>

Yes, with the except of Guidelines

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

</td>  
<td>

</td>  
<td>

electronics devices as well as the overall ELOBSTER concept

-Guidelines and Best practices and measures for the installation of the selected technologies at pilot site 

</td>  
<td>

</td>  
<td>

</td>  
<td>

that are not confidential

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

T5.4

</td>  
<td>

Step by Step Monitoring

Process from TRL4 to TRL 6

</td>  
<td>

\- Data related to the monitoring of KPI

</td>  
<td>

UOB, UNEW, FFE, MDM, RINA-C

</td>  
<td>

.xls, docx, .pdf

</td>  
<td>

Yes

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**WP6 Dissemination and Route for Replication**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Task**

</td>  
<td>

**Description**

</td>  
<td>

**Data**

</td>  
<td>

**Owner(s)**

</td>  
<td>

**Format**

</td>  
<td>

**Confidential**

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

T6.1

</td>  
<td>

Scale up of the E-LOBSTER concept and preliminary replication design

</td>  
<td>

  * Data for replicability studies 

  

  * Data related to cost benefit analysis for assessing replicability 

  

</td>  
<td>

RINA-C, FFE, TPS,

LIBAL, MDM

</td>  
<td>

.xls, docx, .pdf

</td>  
<td>

No

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

T6.2

</td>  
<td>

Business Model and

Roadmap Towards TRL 9

</td>  
<td>

\- Data related to potential Business models and roadmaps

</td>  
<td>

All partners

</td>  
<td>

.xls, docx, .pdf, .ppt

</td>  
<td>

Yes

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

T6.3

</td>  
<td>

Dissemination Activities

</td>  
<td>

\- Dissemination materials in different forms

(video, lefleat, website etc.)

</td>  
<td>

All

</td>  
<td>

.mp4, .jpeg, .pdf, .docx

</td>  
<td>

No

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

T6.4

</td>  
<td>

Stakeholders engagement for future marketability of

E-LOBSTER concept

</td>  
<td>

\- Data related to the three stakeholder workshops with the 2 Stakeholders
Groups (DSOs and Transport manager in close collaboration with WP3 (results of
questionnaires, surveys, inputs etc).

</td>  
<td>

RINA-C, RSSB, FFE, UITP

</td>  
<td>

.pdf, .docx, .xls, .ppt, online survey

</td>  
<td>

No

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

T6.5

</td>  
<td>

Exploitation and IPR management

</td>  
<td>

  * Guidelines for IPR strategy 

  

  * Market data with respect to the different exploitable results - Plans for exploitation 

  

</td>  
<td>

All partners

</td>  
<td>

.docx, .pdf

</td>  
<td>

Yes

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

#  Individual partner data management plan

In this chapter, the E-LOBSTER individual partner data management plan is
presented. In particular, each partner was requested to fill the table
illustrated in Figure 1, according to the following instructions:

  * **NAME:** name data/metadata/dataset; 

  

  * **DESCRIPTION:** brief description of data/metadata/dataset; 

  

  * **CREATED:** each partner should indicate if data/metadata/dataset was (or will be) created during the project (Yes/No); 

  

  * **GATHERED:** each partner should indicate if data/metadata/dataset was (or will be) collected from other sources (Yes/No); 

  

  * **TYPE:** each partner should indicate the type of data/metadata/dataset selecting some of the following options (more than option is possible): Document, Video, Images, Source code/Software, Algorithm, Raw Data, Dissemination material, etc; 

  

  * **FORMAT:** each partner should indicate the file extension of data/metadata/dataset (.pdf, .xls, .mat, specific customized format etc ) and if a description of the data is available for its use 

  

  * **SIZE:** each partner should indicate the file extension the file dimension of data/metadata/dataset (order of magnitude: KB, MB or GB); 

  

  * **OWNER** : the lead beneficiary of the specific data/metadata/dataset (or “external” if the owner is not part of E-LOBSTER consortium) has to be indicated; 

  

  * **DISSEMINATION LEVEL:** each partner should indicate the dissemination level of the specific data/metadata/dataset collected or created during the project, by selecting one of the followings: Confidential, Public, Consortium, etc; 

  

  * **REPOSITORY DURING THE PROJECT (FOR PRIVATE/PUBLIC ACCESS):** each partner should indicate the location of data/metadata/dataset collected or created during the project, by selecting among E-LOBSTER file repository (Nextcloud), open access repositories, partner repository (private cloud/ drop box/ internal area), etc; 

  

  * **BACK-UP FREQUENCY** : it refers to the frequency of updating data/metadata/dataset collected or created during the project (daily, monthly, yearly etc.) 

  

  * **REPOSITORY AFTER THE PROJECT:** the location of data/metadata/dataset collected or created during the project after its conclusion, by selecting among E-LOBSTER file repository (Nextcloud), open access repositories, partner repository (private cloud/ drop box/ internal area), etc; 

  

  * **PRESERVATION AFTER THE END OF THE PROJECT (IN YEARS** ): if data/metadata/dataset collected or created during the project will be maintained, each partner must define for how many years they will be available. 

  

**Figure 1: Template for individual partner data management plan**

E-LOBSTER – D7.2 Data Management Plan Page 13 of 28

##  RINA-C DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE**

**END OF THE**

**PROJECT (IN**

**YEARS)**

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

Dataset - Monitoring data on

power

distribution network

</td>  
<td>

This dataset includes monitoring data related to parameters of the power

distribution network received from the local DSO

</td>  
<td>

No

</td>  
<td>

YES

</td>  
<td>

RINA-C/ local DSO

</td>  
<td>

Raw data

</td>  
<td>

.dat, .xls

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

5 years

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

Dataset – Impact on consumers

</td>  
<td>

Data including analysis of market, socioeconomic, legal and

institutional framework situations and trends

</td>  
<td>

NO

</td>  
<td>

YES

</td>  
<td>

RINA-C /FFE

</td>  
<td>

Data,

Documents

and figures

</td>  
<td>

.xls

.pdf

.jpeg

</td>  
<td>

MB

</td>  
<td>

Public

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

5 years

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

Data on energy losses in the railway and power

distribution networks

</td>  
<td>

Data related to the analysis of the current situations in terms of energy
losses in the railway and power

distribution networks (state of the art)

</td>  
<td>

NO

</td>  
<td>

YES

</td>  
<td>

RINA-C

</td>  
<td>

Data,

Documents

and figures

</td>  
<td>

.xls

.pdf

.jpeg

</td>  
<td>

MB

</td>  
<td>

Public

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

5 years

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

R+ G

Management

System

</td>  
<td>

Dataset including all the simulations carried out for the validation of the
railway simulator tool

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

RINA-C

</td>  
<td>

Source code/ Software

</td>  
<td>

to be defined after the definition of the different interfaces

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

RINA private internal repository

</td>  
<td>

daily

</td>  
<td>

RINA private internal repository

</td>  
<td>

Permanent

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

</th>  
<th>

(WP1)

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

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

Dataset – Validation of

R+G Data

Management

System

</td>  
<td>

Dataset related to testing of

the R+G Data

Management

System

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

RINA-C

</td>  
<td>

Raw data and Documents

</td>  
<td>

to be defined

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal RINA-C repository

</td>  
<td>

5 years

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

First

stakeholder workshop - Transport

Manager

Stakeholder

Group (SG)

</td>  
<td>

Data related to the First stakeholder workshop:

questionnaires, surveys, video, audio, documentation, dissemination material,
minutes of workshop.

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

RINA- C,

UITP, RSSB

</td>  
<td>

Documents, video, audio, data, pictures

</td>  
<td>

.pdf

</td>  
<td>

GB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER repository (Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Second stakeholder workshop - DSO

Stakeholder

Group (SG)

</td>  
<td>

Data related to the second stakeholder workshop:

questionnaires, surveys, video, audio, documentation, dissemination material,
minutes of workshop.

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

RINA- C,

UITP, RSSB

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

GB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Joint

Stakeholder

Workshop – TM and DSO

Stakeholder

Group (SG)

</td>  
<td>

Data related to the Final stakeholder workshop:

questionnaires, surveys, video, audio, documentation, dissemination material,
minutes of workshop.

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

RINA- C,

UITP, RSSB

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

GB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Dataset Standards

</td>  
<td>

Data related to the analysis of current standards

</td>  
<td>

No

</td>  
<td>

Yes

</td>  
<td>

Consortium

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Dataset – Cost Benefit

Analysis

</td>  
<td>

Data related to the Cost

Benefit Analysis for the replication of the E-LOBSTER concept

</td>  
<td>

Yes

</td>  
<td>

YES

</td>  
<td>

RINA-C

</td>  
<td>

Document, data

</td>  
<td>

.pdf, .xls

</td>  
<td>

MB

</td>  
<td>

Public

(document)

Confidential

(raw data)

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

##  TPS DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE PROJECT**

**(IN YEARS)**

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

Simulators

</td>  
<td>

Simulator for testing sSOP

</td>  
<td>

Yes

</td>  
<td>

NO

</td>  
<td>

TPS

</td>  
<td>

Source code/Software

</td>  
<td>

.PLECS

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

weekly

</td>  
<td>

Partner repository

</td>  
<td>

Permanent

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

Dataset on testing

</td>  
<td>

Outcomes of the testing activities through simulator

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

TPS

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat .pdf

.xlsx

</td>  
<td>

MB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository

(raw data),

Project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data),

Project

Repository

Nextcloud

(documents)

</td>  
<td>

At least 5 years

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

sSOP Design

</td>  
<td>

schema and design of sSOP

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

TPS

</td>  
<td>

Documents

and figures

</td>  
<td>

.jpg

.pdf

.vsd

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

weekly

</td>  
<td>

Partner repository

</td>  
<td>

Permanent

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

Dataset validation in UNEW Laboratory

</td>  
<td>

Outcomes of the validation activities

during the test in UNEW Smart Grid

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

TPS

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat .pdf

.doc

</td>  
<td>

MB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository

(raw data),

Project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data),

Project

Repository

Nextcloud

</td>  
<td>

At least 5 years

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

</td>  
<td>

Laboratory

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

(documents)

</td>  
<td>

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

Dataset validation in Metro of Madrid

</td>  
<td>

Outcomes of the validation activities in the field in Metro of Madrid

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

TPS

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository

(raw data),

Project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data),

Project

Repository

Nextcloud

(documents)

</td>  
<td>

At least 5 years

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

##  RSSB DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/**

**PUBLIC ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE**

**PROJECT (IN**

**YEARS)**

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

First

stakeholder workshop

(Transport

Manager SG)

</td>  
<td>

Data related to the First stakeholder workshop: questionnaire s, surveys,

documents

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

Consortium

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER

file repository

(Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Second stakeholder workshop (DSO

SG)

</td>  
<td>

Data related to the Second stakeholder workshop: questionnaire s, surveys,

documentats

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

Consortium

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER

file repository

(Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Joint

Stakeholder Workshop with both SG

</td>  
<td>

Data related to the Second stakeholder workshop: questionnaire s, surveys,

documentats

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

Consortium

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER

file repository

(Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

Dataset Standards

</td>  
<td>

Data related to the analysis of current standards

</td>  
<td>

No

</td>  
<td>

Yes

</td>  
<td>

Consortium

</td>  
<td>

Document

</td>  
<td>

.pdf

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER file repository (Nextcloud), Internal partner repository

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER

file repository

(Nextcloud), Internal partner repository

</td>  
<td>

5 years

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

##  UOB DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

NAME

</th>  
<th>

DESCRIPTION

</th>  
<th>

CREATED

</th>  
<th>

GATHERED

</th>  
<th>

OWNER

</th>  
<th>

TYPE

</th>  
<th>

FORMAT

</th>  
<th>

SIZE

</th>  
<th>

DISSEMINATION LEVEL

</th>  
<th>

REPOSITORY

DURING THE

PROJECT (FOR

PRIVATE/PUBLIC

ACCESS)

</th>  
<th>

BACK-UP

FREQUENCY

</th>  
<th>

REPOSITORY AFTER THE PROJECT

</th>  
<th>

PRESERVATION

AFTER THE END OF

THE PROJECT (IN

YEARS)

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

Single and multi-train simulators

</td>  
<td>

Bespoke simulator for Energy losses evaluation

(WP1)

</td>  
<td>

Yes

</td>  
<td>

NO

</td>  
<td>

UOB

</td>  
<td>

Source code/ Software

</td>  
<td>

.mat

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

monthly

</td>  
<td>

Partner repository

</td>  
<td>

Permanent

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

Madrid

Metro Line 2 – train, route and power network data

</td>  
<td>

These data is used for the simulation to study the energy losses (WP1, WP5)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

Madrid

Metro

Line 2

</td>  
<td>

Raw data Documen

ts and figures

</td>  
<td>

.xls .pdf

</td>  
<td>

1160

KB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository Nextcloud project repository

</td>  
<td>

monthly

</td>  
<td>

Partner repository Nextcloud project repository

</td>  
<td>

At least 5 years

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

Energy losses evaluation data

</td>  
<td>

These are the simulation data based on Madrid Metro Line 2. The data describe
the power losses with various feeding arrangement

(WP1)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB

</td>  
<td>

Raw data Documen

ts and figures

</td>  
<td>

.dat

.mat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data

confidential,

Summing up of results public

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/prese ntation summing

up the simulations)

</td>  
<td>

monthly

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/present ation summing up the simulations)

</td>  
<td>

At least 5 years

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

Dataset for Single and multi-train simulator tool assessm.

</td>  
<td>

Dataset including all the simulations carried out for the validation of the
railway simulator tool

(WP1)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB

</td>  
<td>

Raw data Documen

ts and figures

</td>  
<td>

.dat

.mat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential,

Summing up of results public

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/prese ntation summing

up the simulations)

</td>  
<td>

monthly

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/present ation summing up the simulations)

</td>  
<td>

At least 5 years

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

Dataset for the integrated simulator tool assessm.

</td>  
<td>

Dataset including all the simulations carried out for the testing of the
integrated tool (WP1)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB, UNEW

</td>  
<td>

Raw data Documen

ts and figures

</td>  
<td>

.dat

.mat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential,

Summing up of results public

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/prese ntation summing

up the simulations)

</td>  
<td>

monthly

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/present ation summing up the simulations)

</td>  
<td>

At least 5 years

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

Dataset of laboratory validation

</td>  
<td>

Data related to the validation of the simulator in the UNEW Smart Grid

Laboratory

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB, UNEW

</td>  
<td>

Raw data Documen

ts and figures

</td>  
<td>

.dat

.mat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data

confidential,

Summing up of results public

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/prese ntation summing

up the simulations)

</td>  
<td>

monthly

</td>  
<td>

Partner repository (raw data). Nextcloud project repository

(document/present ation summing up the simulations)

</td>  
<td>

At least 5 years

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

##  LIBAL DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY AFTER THE PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE PROJECT**

**(IN YEARS)**

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

Simulators CELATORS

</td>  
<td>

Custom made simulator for testing the electric storage systems

</td>  
<td>

Yes

</td>  
<td>

NO

</td>  
<td>

LIBAL

</td>  
<td>

Source code/Software

</td>  
<td>

C, C#, .txt

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

weekly

</td>  
<td>

Partner repository

</td>  
<td>

Permanent

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

LIBAL Cloud

</td>  
<td>

MS Azure Cloud data collection software

</td>  
<td>

YES

</td>  
<td>

NO

</td>  
<td>

LIBAL

</td>  
<td>

Source code/Software

</td>  
<td>

N/A

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

Continuously

</td>  
<td>

LIBAL

</td>  
<td>

Permanent

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

Dataset on testing

</td>  
<td>

Outcomes of the testing

activities through simulator

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

LIBAL

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat

.pdf

</td>  
<td>

MB

</td>  
<td>

confidential

</td>  
<td>

Partner repository

(raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

At least 5 years

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

Electric

Storage

System

Design

</td>  
<td>

Schema and design of Electric

Storage

Systems

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

LIBAL

</td>  
<td>

Documents

and figures

</td>  
<td>

.jpg

.pdf

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

</td>  
<td>

weekly

</td>  
<td>

Partner repository

</td>  
<td>

Permanent

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

Dataset validation in UNEW Laboratory

</td>  
<td>

Outcomes of the validation activities during the test in UNEW Smart Grid

Laboratory

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

LIBAL

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat

.pdf

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

Partner repository

(raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

At least 5 years

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

Dataset validation in Metro of Madrid

</td>  
<td>

Outcomes of the validation activities in the field in Metro of Madrid

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

LIBAL

</td>  
<td>

Raw data and documents

</td>  
<td>

.dat

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository

(raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

weekly

</td>  
<td>

Partner repository (raw data), project Repository

Nextcloud

(documents)

</td>  
<td>

At least 5 years

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

##  MDM DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE PROJECT**

**(IN YEARS)**

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

MDM Data

files from substation equipment

</td>  
<td>

Recording data available from the different substation equipment to be used
for simulations

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

MDM

</td>  
<td>

Document, raw data

</td>  
<td>

.xls

</td>  
<td>

100

MB

</td>  
<td>

Consortium

</td>  
<td>

Internal partner repository, Project repository

(Nextcloud)

</td>  
<td>

weekly

</td>  
<td>

Internal partner repository, Project repository (Nextcloud)

</td>  
<td>

5

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

MDM

Measurement data from the substation equipment

</td>  
<td>

Real measurement from the substation equipment to be used for simulations

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

MDM

</td>  
<td>

Document, raw data

</td>  
<td>

.xls

</td>  
<td>

10 MB

</td>  
<td>

Consortium

</td>  
<td>

Internal partner repository, Project repository

(Nextcloud)

</td>  
<td>

weekly

</td>  
<td>

Internal partner repository, Project repository (Nextcloud)

</td>  
<td>

5

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

MDM

Installations

</td>  
<td>

Photographs of different installations in

MDM

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

MDM

</td>  
<td>

Images

</td>  
<td>

.jpg

</td>  
<td>

100

MB

</td>  
<td>

Consortium

</td>  
<td>

Internal partner repository, Project repository

(Nextcloud)

</td>  
<td>

weekly

</td>  
<td>

Internal partner repository, Project repository (Nextcloud)

</td>  
<td>

5

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

##  UNEW DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT (FOR**

**PRIVATE/**

**PUBLIC ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE PROJECT**

**(IN YEARS)**

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

Energy losses evaluation data on

</td>  
<td>

These are the simulation data based on

Madrid Metro

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UNEW

</td>  
<td>

Raw data

Documents

and figures

</td>  
<td>

.dat

.mat

.xls

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential,

Summing up of results public

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository

</td>  
<td>

daily

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository

</td>  
<td>

At least 5 years

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

Madrid Metro 12

</td>  
<td>

Line 12. The data describe the load flow study results as part of the
simulation study in T1.2

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

(document/presen tation summing up the simulations)

</td>  
<td>

</td>  
<td>

(document/prese ntation summing

up the simulations)

</td>  
<td>

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

Madrid

Metro

Line 12

</td>  
<td>

This data is used for the simulation to study the energy losses (WP1, WP5)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

MDM

</td>  
<td>

Raw data

Documents

and figures

</td>  
<td>

.xls .pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential

</td>  
<td>

Partner repository Nextcloud project repository

</td>  
<td>

monthly

</td>  
<td>

Partner repository Nextcloud project repository

</td>  
<td>

At least 5 years

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

Dataset

</td>  
<td>

WP5_demnsta

rtion

</td>  
<td>

Yes

</td>  
<td>

Yes

</td>  
<td>

UNEW

</td>  
<td>

Experim.

</td>  
<td>

.xls

.pdf

.mat

</td>  
<td>

kB

</td>  
<td>

confidential

</td>  
<td>

Private cloud

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Smart Grid Simulator

</td>  
<td>

Simulator for Energy losses evaluation (WP1)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UNEW

</td>  
<td>

Source code/Softw are

</td>  
<td>

.m

.mat

</td>  
<td>

MB

</td>  
<td>

Confidential

</td>  
<td>

UNEW internal repository

</td>  
<td>

monthly

</td>  
<td>

UNEW internal repository

</td>  
<td>

Permanent

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

Dataset for the integrated simulator

tool

assessmen

t

</td>  
<td>

Dataset including all the simulations carried out for the testing of the
integrated tool (WP1)

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB, UNEW

</td>  
<td>

Raw data

Documents

and figures

</td>  
<td>

.dat

.mat

.xls

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential,

Summing up of results public

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository

(document/presen tation summing up the simulations)

</td>  
<td>

daily

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository

(document/prese ntation summing

up the simulations)

</td>  
<td>

At least 5 years

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

Dataset of laboratory validation

</td>  
<td>

Data related to the validation of the simulator in the UNEW Smart Grid

Laboratory

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

UOB, UNEW

</td>  
<td>

Raw data

Documents

and figures

</td>  
<td>

.dat

.mat

.xls

.pdf

</td>  
<td>

MB

</td>  
<td>

Raw data confidential,

Summing up of results public

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository (document/presen
tation summing up the simulations)

</td>  
<td>

daily

</td>  
<td>

UNEW repository (raw data). Nextcloud project repository (document/prese
ntation summing

up the simulations)

</td>  
<td>

At least 5 years

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

##  FFE DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT**

**(FOR**

**PRIVATE/**

**PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE PROJECT**

**(IN YEARS)**

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

Data of consumer consumption.

</td>  
<td>

Analysis of consumer behavior. Information on

consumptions and tools for reduction of energy consumption.

</td>  
<td>

No

</td>  
<td>

Y (from previous projects)

</td>  
<td>

FFE

</td>  
<td>

report

</td>  
<td>

.doc

</td>  
<td>

MB

</td>  
<td>

Public-use

</td>  
<td>

Nextcloud and partner Private-cloud

</td>  
<td>

daily

</td>  
<td>

Partner repositoryPrivate cloud

</td>  
<td>

10 years

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

Current operating standards

</td>  
<td>

The document

will describe the actual standards and analyse the specific national
regulations. It will be done also a revision of the applicable standards.

</td>  
<td>

N0

</td>  
<td>

Y (From state of art)

</td>  
<td>

FFE

</td>  
<td>

report

</td>  
<td>

.doc (most probable

) or xlsl

</td>  
<td>

MB

</td>  
<td>

Public Use

</td>  
<td>

Nextcloud and partner Private-cloud

</td>  
<td>

daily

</td>  
<td>

Partner repositoryPrivate cloud

</td>  
<td>

10 years

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

Workshop feedbacks

</td>  
<td>

The document

will delineate the results of Stakeholders’ group workshops.

It will be described the most relevant factors and it will be collected the
evidence coming from this

workshops and

this activities

</td>  
<td>

Yes

</td>  
<td>

No

</td>  
<td>

FFE

</td>  
<td>

Docum

ent (report)

</td>  
<td>

.doc

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

Nextcloud and partner Private-cloud

</td>  
<td>

daily

</td>  
<td>

Partner repositoryPrivate cloud

</td>  
<td>

10 years

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

</td>  
<td>

groups.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

##  UITP DATA MANAGEMENT PLAN  
  
<table>  
<tr>  
<th>

**NAME**

</th>  
<th>

**DESCRIPTION**

</th>  
<th>

**CREATED**

</th>  
<th>

**GATHERED**

</th>  
<th>

**OWNER**

</th>  
<th>

**TYPE**

</th>  
<th>

**FORMAT**

</th>  
<th>

**SIZE**

</th>  
<th>

**DISSEMINATION LEVEL**

</th>  
<th>

**REPOSITORY DURING THE**

**PROJECT**

**(FOR**

**PRIVATE/**

**PUBLIC**

**ACCESS)**

</th>  
<th>

**BACK-UP FREQUENCY**

</th>  
<th>

**REPOSITORY**

**AFTER THE**

**PROJECT**

</th>  
<th>

**PRESERVATION**

**AFTER THE END**

**OF THE**

**PROJECT (IN**

**YEARS)**

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

Preliminary

Stakeholder

Workshop: E-

LOBSTER

Stakeholder

Workshops

No.1

Stakeholder

Workshop on

Electric PT – M13 – M36: Preliminary time Oct – Nov 2019

</td>  
<td>

A preliminary workshop on

Electric PT

Stakeholder

Group – Feedback from the

workshop

received in the forms of questionnaire surveys, meeting notes, documents

</td>  
<td>

Yes

</td>  
<td>

Yes

</td>  
<td>

External

</td>  
<td>

Text or word documents, spreadsheets

questionnaire

, transcripts, meeting minutes ; audiotapes, videotapes ; database contents ;
publications, reports, dissemination materials

</td>  
<td>

PDF

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER

file repository (Nextcloud)

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud)

</td>  
<td>

Maintained – 5 years

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

Preliminary

Stakeholder

Workshop: E-

LOBSTER

Stakeholder

Workshops

No.2

Stakeholder

Workshop

Electric

Distribution

</td>  
<td>

A preliminary workshop on

Electric

Distribution Network Operators and Tech

Providers

Stakeholder

Group – Feedback

</td>  
<td>

Yes

</td>  
<td>

Yes

</td>  
<td>

External

</td>  
<td>

Text or word documents, spreadsheets questionnaire transcripts, meeting
minutes ; audiotapes, videotapes ; database contents ;

</td>  
<td>

PDF – descripti on available

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER

file repository (Nextcloud)

</td>  
<td>

weekly

</td>  
<td>

E-LOBSTER file repository (Nextcloud)

</td>  
<td>

Maintained – 5 years

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

Network Operators and Tech

Providers) – M13 – M36: Preliminary time March – April 2020

</td>  
<td>

from the

workshop

received in the forms of

questionnaire s, surveys, meeting

notes, documents

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

publications, reports, dissemination materials

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Joint

Stakeholder

Workshop: E-

LOBSTER

Stakeholder

Workshops

No.3

Stakeholder

Workshop

Electric PT and Electric Distribution

Network Operators and Tech Providers ) – (M13 – M36): Preliminary time Feb –
April 2021

</td>  
<td>

A joint

workshop on

Electric PT and Electric Distribution

Network Operators and Tech

Providers

Stakeholder

Groups – Feedback from the

workshop

received in the forms of

questionnaire s, surveys, meeting

notes, documentats

</td>  
<td>

Yes

</td>  
<td>

Yes

</td>  
<td>

External

</td>  
<td>

Text or word documents, spreadsheets

;

questionnaire s, transcripts, meeting minutes ; audiotapes, videotapes ;
database contents ; publications, reports, dissemination materials

</td>  
<td>

PDF – descripti on available

</td>  
<td>

MB

</td>  
<td>

Consortium

</td>  
<td>

E-LOBSTER

file repository (Nextcloud)

</td>  
<td>

Yearly (After the workshop organised and conducted)

</td>  
<td>

E-LOBSTER file repository (Nextcloud)

</td>  
<td>

Maintained – 5 years

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

#  Research Data Repositories

Although E-LOBSTER decided do not participate to the Pilot Action on Open
Research Data in order do not hamper the commercial interests of the
industrial partners, at this stage of the project, the ELOBSTER consortium
investigated about potential research data Repositories to be used for the
sharing of no confidential data (e.g. papers).

Among the different possibilities, ZENODO (  _http://www.zenodo.org/_ )  which
is the cost free open access repository of OpenAIRE (the Open Access
Infrastructure for Research in Europe,  _https://www.openaire.eu/_ )  has been
considered. OpenAIRE is an EC-funded initiative which aims to support the Open
Access policy of the European Commission via a technical infrastructure.
Actually, OpenAIRE has grown through a series of project phases funded by the
European Commission  4  : from the DRIVER projects to link Europe’s repository
infrastructure, to the first OpenAIRE project aimed to assist the EC in
implementing its initial pilot for Open Access (OA) to publications, and,
through several further phases which have extended and consolidated the
OpenAIRE mission to implement Open Science policies. OpenAIRE currently
operates an interoperable and validated network of more than 520 repositories
and OA journals (integrating more than 9 million OA publications and 1,000
datasets)

It has identified over 100,000 FP7 publications from about half the 26,000 FP7
projects, and offers literature-data integration services.

In particular, it is OpenAIRE platform, the technical infrastructure that is
key for interconnecting the large-scale collections of research outputs across
Europe. It creates workflows and services on top of this valuable repository
content, which enable an interoperable network of repositories (via the
adoption of common guidelines), and easy upload into an all-purpose repository
(via ZENODO)  5  . Recently, the 29  th  of October 2018, OpenAIRE became a
fully fledged organisation, with the formation of its legal entity, **OpenAIRE
A.M.K.Ε.** , a non-profit partnership, to ensure a permanent presence and
structure for a European-wide national policy and open scholarly communication
infrastructure.

So far the objective of the OpenAIRE portal was to make as much European
funded research output as possible available to all. Institutional
repositories are typically linked to it. Furthermore, dedicated pages per
project are visible on the OpenAIRE portal, making research output
(publications, datasets or simple project information) accessible through the
portal thanks to the bibliographic metadata linked to each publication.

Concerning ZENODO, the OpenAIRE project, as explained above, is in the
vanguard of the open access and open data movements in Europe and was
commissioned by the EC to support its Open Data policy by providing a catch-
all repository for EC funded research. CERN (an OpenAIRE partner and pioneer
in open source, open access and open data) provided this capability and ZENODO
was launched in May 2013. In support of its research programme CERN has
developed tools for Big Data management and extended Digital Library
capabilities for Open Data. Through ZENODO these Big Science tools could be
effectively shared in the research sector  6  .

**Figure 2: Home page of Zenodo**

In addition to ZENODO, among the other repositories to be considered there is
also re3data.org.

re3data.org  7  is a global registry of research data repositories that covers
research data repositories from different academic disciplines. It presents
repositories for the permanent storage and access of data sets to researchers,
funding bodies, publishers and scholarly institutions. re3data.org promotes a
culture of sharing, increased access and better visibility of research data.
The registry went live in autumn 2012 and is funded by the German Research
Foundation (DFG). Project partners in re3data.org are the Berlin School of
Library and Information Science at the Humboldt-Universität zu Berlin, the
Library and Information Services department (LIS) of the GFZ German Research
Centre for Geosciences, the KIT Library at the Karlsruhe Institute of
Technology (KIT) and the Libraries of the Purdue University. The German
partners are actively involved in the German Initiative for Network
Information (DINI) and current research data management activities.

**Figure 3: Home page of re3data.org**

#  Conclusions

This deliverable represents the E-LOBSTER Data Management Plan at month 6. The
scope of this Data Management Plan is to describe the data management life
cycle for the data to be collected, processed and/or created in the framework
of the E-LOBSTER project.

In particular, this document specifies how the E-LOBSTER research data will be
handled in the framework of the project as well as after its completion.

More in detail, the report indicated:

  * what data will be collected, processed and/or created and from whom 

  

  * which data will be shared and which one will be maintained confidential 

  

  * how and where the data will be stored during the project 

  

  * which backup strategy will be applied for safely maintaining the data 

  

  * how the data will be preserved after the end of the project 

  

In particular, in the report both the data management plans at project and at
individual partner level have been presented.

The present Data Management Plan has to be considered as a living document,
and any future update or change in the E-LOBSTER data management policy will
be included in the periodic reports or will be specified in the deliverables
related to the specific tasks. In particular, the Data Management Plan will be
refined according to the IPR strategy that will be defined for the E-LOBSTER
exploitable results.