1\. Introduction  5

2\. Data Types  8

2.1. Data Types of the Project  8

2.2. Levels of Confidentiality and Flow of Data  9

2.3. Data Formats  10

2.4. Expected Data of the Project  11

3\. Collection, Storage and Use of Research Data and Analysed Research Data
13

4\. Storage and Use of Project Data  14

4.1. Storage of Data 14

4.2. Documenting of Data  15

5\. Data Sharing  17

5.1. Depositing Research Data  17

5.2. Open Access Publishing  17

5.3. Other Dissemination  18

6\. Opting Out Research Data  19

7\. Summary and Perspectives  20

#  Introduction

This document outlines the principles and processes for data collection,
annotation, analysis and distribution as well as storage and security of data
within the EU/JP 5G!Pagoda project. The procedures will be adopted by all
project partners throughout the project in order to ensure that all project
related data are well-managed according to contractual obligations as well as
applicable legislation both during and after the project.

5G!Pagoda is committed to openness with respect to research data and results,
as manifested by its participation in the Pilot on Open Research Data in
Horizon 2020. Therefore, as a further dissemination channel, 5G!Pagoda will
share datasets on which its results are derived as explained in this Open Data
Management Plan. Public research repositories are used to maximize the
visibility and impact of the research carried out by partners by making such
data available for reuse by 3rd parties and reproducibility of the project’s
results.

The Grant Agreement of the 5G!Pagoda project (as an Open Data Pilot
participant) obligates the project to deposit [digital research data generated
in the project] in a research data repository and take measures to make it
possible for third parties to access, mine, exploit, reproduce and disseminate
— free of charge for any user — the following:

  1. the data, including associated metadata, needed to validate the results presented in scientific publications as soon as possible; 

  

  2. other data, including associated metadata, as specified and within the deadlines laid down in the 'data management plan', i.e. this document. 

  

  

The Grant Agreement contains an option to discard the obligation to deposit a
part of research data in the case where the achievement of the action's main
objective, described in Annex 1 of the Grant Agreement, would be jeopardised.
In such case, the Open Data Management Plan must contain the reasons for not
giving access.

As the obligation to deposit research data in a databank does not change the
obligation to protect results, take care of confidentiality and security
obligations, or the obligations to protect personal data, the Open Data
Management Plan addresses these topics. This document details, how the
seemingly contradicting commitments to share and protect are implemented
within the project.

The Open Data Management Plan has, on the other hand, also served the purpose
of acting as a tool to agree on the data processing of the 5G!Pagoda project
consortium. The production of the Open Data Management Plan has helped the
consortium to identify situations, where the practices were thought to be
agreed upon and where a common understanding on practices was thought to have
been achieved, but where such in fact did not exist.

Documents related to the Open Data Management Plan are the 5G!Pagoda project
Grant Agreement, the Consortium Agreement, the Coordination Agreement, and the
Project Management, Quality and IPR Guide. Some of the deliverables also
contain information which link to the Open Data Management Plan. The
relationships are described below in Table 1.

**Table 1 Documents related to the Open Data Management Plan.**  
  
<table>  
<tr>  
<th>

Related document

</th>  
<th>

Relationship to the Open Data Management Plan

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

The Grant Agreement

</td>  
<td>

  * Article 27 details the obligation to protect results 

  

  * Article 29 details dissemination of results including open access to publications and research data 

  

  * Article 36 details confidentiality obligations 

  

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

</td>  
<td>

  * Article 39 details obligations to protect personal data, if applicable 

  

  * Annex 1, Part B, Chapter 2.4 and Chapter 2.5 detail open access publication and research data management principles. 

  

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

Consortium Agreement

</td>  
<td>

Chapter 4.1 on the General principles: “ _Each Party undertakes to notify
promptly, in accordance with the governance structure agreed in the
Coordination Agreement and directly to the Coordinator, any significant
information, fact, problem or delay likely to affect the Project, submission
of the deliverables or reports in accordance with the Grant Agreement and_

_shall promptly provide all information reasonably required by the Coordinator
to carry out its tasks._

_Each Party shall take reasonable measures to ensure the accuracy of any
information or materials it supplies to the Coordinator or the Parties.”_ This
is a general declaration of the partners to abide by the rights and
obligations set out in the Grant Agreement.

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

Coordination Agreement

</td>  
<td>

  * Chapter 4.1 on the General principles: _“Each Party undertakes to take part in the efficient implementation of the Coordinated Project, and to cooperate, perform and fulfil, promptly and on time, all of its obligations in the said project and under this Coordination Agreement as may be reasonably required from it and in a manner of good faith._

  

_Each Party undertakes to notify promptly, in accordance with the governance
structure of the Coordinated Project, and as required for the coordination
under this Coordination Agreement, any significant information, fact, problem
or delay likely to affect the project(s) or the coordination.”_ This is a
general declaration of the partners to abide by the rights and obligations set
out in the Coordinated Project, Project Plan, part of the Grant Agreement.

  * Chapter 8.4 on Publication defines publication principles. 

  

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

Project Management, Quality and IPR Guide

</td>  
<td>

The Project Management, Quality and IPR Guide defines the quality criteria for
all work conducted in the 5G!Pagoda project.

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

Yearly report on standardization, dissemination and exploitation achievements

</td>  
<td>

Contributions to standardization will enable 5G!Pagoda to achieve broader
recognition of its results by a wide industry community, stimulate higher
levels of interoperability and contribute to establishing economies of scale
for 5G!Pagoda applications. Moreover, close coordination between research
projects and standardization organizations, particularly through running and
validated testbeds, is an important mechanism for exploitation of results and
for inspiring and initiating innovation.

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

Report on innovation achieved and forthcoming industrial exploitation

</td>  
<td>

This public report summarises the innovations achieved in the project and the
activities and plans to exploit these innovations and other project results.

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

5G!Pagoda does not intend collecting any data that may expose private
information (i.e., user contextrelated data). If during the course of the
project, this becomes a necessity, the 5G!Pagoda consortium is committed to
respect privacy and comply with the EU respective directives and national law:
any data deemed private will not be made publicly available, and if it has to
be made public, it will be appropriately anonymized. The project may generate
quantitative models of various aspects of the 5G!Pagoda system (e.g.,
performance of specific network function, performance of a service over a
specific network slice, network or application level traces, dependence of
end-user experience on specific system and environment parameters, etc.),
which will be made available via open-access publications, technical reports,
and the project’s public deliverables. The partners will evaluate the
applicability of standards with respect to various aspects of data
publication, indexing, storage, preservation, privacy, etc., and will report
on them in this Open Data Management Plan (i.e. deliverable D1.2).

Where applicable, each contributor to a publication as an outcome of 5G!Pagoda
will acquire a persistent identifier from the ORCID registry and each
published data set or other research data object will be assigned a persistent
identifier from DataCite, which builds on OIDs. The consortium will strive to
publish data on repositories indexed by the Registry of Research Data
Repositories, which provides an XML schema and an API for querying research
data. The selected repositories should support the Open Archives Initiative
Protocol for Metadata Harvesting (OAI-PMH) standard for repository
interoperability and cross-archive search. The consortium will ensure that
appropriate metadata are provided for the published data, including the
acknowledgement to the funding of EU, H2020, and the Japanese Ministry of
Internal Affairs and Communications, the name of the project, the grant number
and the name of the action.

The ODMP may be re-evaluated during the project. On each updated version, the
necessary corrective actions will be included, to ensure that research data
remain discoverable, accessible, assessable and intelligible, interoperable
and (re)usable beyond their original purpose. The European Commission as well
as the Japanese Ministry of Internal Affairs and Communications will be
accordingly notified.

#  Data Types

##  Data Types of the Project

In the 5g!Pagoda project there are four basic types of data (Figure 1):
research data, analysed research data, project data and reports and
communication data.

**Research data** covers the data collected on the project subject matter and
it refers to information, in particular facts or numbers, collected to be
examined and considered as a basis for reasoning, discussion, or calculation.

In a research context, examples of data include statistics, results of
experiments, measurements, observations resulting from fieldwork, survey
results, interview recordings and images. The focus is on research data that
is available in digital form.

Users can normally access, mine, exploit, reproduce and disseminate openly
accessible research data free of charge. /H2020 Online Manual/

Based on discussion with the consortium members, it has become apparent that
it is difficult at this stage to identify the kind of data to be collected on
the project. However, once such data become identified, this Open Data
Management will be accordingly updated.

**Analysed research data** means the reports composed of the research data.
Analysed data also refers to qualitative and quantitative data analyses
conducted on the data. Reviews of earlier published data and records will be
utilised to some degree. This data will be considered as analysed research
data for the purposes of this document. Project related workshops and
stakeholder engagement events are public events and the workshop notes of
project partners will be treated in the same way as analysed research data
(i.e. the notes will be shared within the consortium).

**Figure 1 Data types.**

**Project data** includes administrative and financial project data, including
contracts, partner information and periodic reports, as well as accumulated
data on project meetings, teleconferences and other internal materials. This
data is confidential to the project consortium and to the European Commission.

Project data includes mainly MS Office documents, in English, which ensures
ease of access and efficiency for project management and reporting. Most of
the project data is stored in the password protected OwnCloud repository,
administrated by Aalto University.

**Reports and other communication data** includes deliverables, presentations
and for example articles. This data type also refers to the contents of the
5G!Pagoda project website.

Each data type is treated differently with regard to the level of
confidentiality (see Chapter 2.2). Some of the data falls under the EU, Japan,
and national laws on data protection and for this reason the project is
obliged to seek necessary authorisations and to fulfil notification
requirements.

The project will assume the principle of using commonly used data formats for
the sake of compatibility, efficiency and access. The preferred means of data
types is MS Office compatible formats, where applicable.

##  Levels of Confidentiality and Flow of Data

Overall, there are three basic levels of confidentiality, namely Public,
Confidential to consortium (including Commission Services), and Confidential
to the Partner.

**Figure 2 Data types displayed in three levels of confidentiality.**

Figure 2 displays how the previously mentioned data types are positioned in
the level of confidentiality context. Figure 3 displays the data in more
granularity.

**Figure 3 Data distributed into the three levels of confidentiality in more
detail.**

##  Data Formats

Recommended file formats are presented in the following table. See best
practices for file formats from  _Stanford University Library_ .

**Table 2 Recommended file formats.**  
  
<table>  
<tr>  
<th>

**Text format**

</th>  
<th>

**File extension**

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

Acrobat PDF/A

</td>  
<td>

.pdf

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

Comma-Separated Values

</td>  
<td>

.csv

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

Open Office Formats

</td>  
<td>

.odt, .ods, .odp

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

Plain Text (US-ASCII, UTF-8)

</td>  
<td>

.txt

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

XML

</td>  
<td>

.xml

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

**Image / Graphic formats**

</td>  
<td>

**File extension**

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

JPEG

</td>  
<td>

.jpg

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

JPEG2000

</td>  
<td>

.jp2

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

PNG

</td>  
<td>

.png

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

SVG 1.1 (no java binding)

</td>  
<td>

.svg

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

TIFF

</td>  
<td>

.tif, .tiff

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

**Audio formats**

</td>  
<td>

**File extension**

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

AIFF

</td>  
<td>

.aif, .aiff

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

WAVE

</td>  
<td>

.wav

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

**Motion formats**

</td>  
<td>

**File extension**

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

AVI (uncompressed)

</td>  
<td>

.avi

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

Motion JPEG2000

</td>  
<td>

.mj2, .mjp2

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

##  Expected Data of the Project

Table 3 presents the data expected to be created during the project.

D1.2 – Open Data Management Plan  
  
<table>  
<tr>  
<th>

**5G!Pagoda**

</th>  
<th>

**Version 1.0**

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

**Page 12 of 20**

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

**Table 3 Expected data of the project.**  
  
<table>  
<tr>  
<th>

</th>  
<th>

**Publications**

</th>  
<th>

**Reports & Deliverables **

</th>  
<th>

**Software**

</th>  
<th>

**Open Research Data**

</th>  
<th>

**Opted Out Research Data**

</th>  
<th>

**Contribution to Open Sources**

</th>  
<th>

**Contribution to Standars**

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

**Partner**

</td>  
<td>

Gold

</td>  
<td>

Green

</td>  
<td>

Consortium

</td>  
<td>

Public

</td>  
<td>

Consortium

</td>  
<td>

Public

</td>  
<td>

Yes 1)

</td>  
<td>

No

</td>  
<td>

May be

</td>  
<td>

Yes 2)

</td>  
<td>

No

</td>  
<td>

May be

</td>  
<td>

Yes 3)

</td>  
<td>

No

</td>  
<td>

May be

</td>  
<td>

Yes 4)

</td>  
<td>

No

</td>  
<td>

May be

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

AALTO

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

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

UT

</td>  
<td>

Δ

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

FGIMT2020,5GMF

</td>  
<td>

</td>  
<td>

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

Ericsson

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

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

Orange

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

3GPP, ETSI NFV, ITU-T

</td>  
<td>

</td>  
<td>

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

FOKUS

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

EI

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

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

MI

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

ITU-T

</td>  
<td>

</td>  
<td>

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

DG

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

KDDI

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

3GPP, 5GMF

</td>  
<td>

</td>  
<td>

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

HITACHI

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

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

NESIC

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

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

WU

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

X

</td>  
<td>

ITU-TFG IMT2020, SG13

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

If you answered yes to the following items, please give detailed
comments/explanations below!

</td>  
<td>

</td>  
<td>

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

Yes 1)

</td>  
<td>

Describe the data, give also format and expected amount (MB, GB)

</td>  
<td>

</td>  
<td>

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

Yes 2)

</td>  
<td>

If you are opting out data (keep it confidential), describe the data and give
reasons for opting out

</td>  
<td>

</td>  
<td>

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

Yes 3)

</td>  
<td>

If you are contributing to open sources, describe the contributing data and
the open source instance

</td>  
<td>

</td>  
<td>

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

Yes 4)

</td>  
<td>

If you are contributing to standards preparation, describe the instance to
contribute to

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Detailed comments**

</td>  
<td>

</td>  
<td>

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

**Partner**

</td>  
<td>

**Comment**

</td>  
<td>

</td>  
<td>

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

AALTO

</td>  
<td>

4) Aalto may contribute to ITU-T IMT 2020 Network Softwarization Working Group
along with The University of Tokyo

</td>  
<td>

</td>  
<td>

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

UT

</td>  
<td>

4) UT will contribute to ITU-T IMT-2020 and 5GMF Network Architecture WG

</td>  
<td>

</td>  
<td>

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

Ericsson

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Orange

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

FOKUS

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

EI

</td>  
<td>

3) EURECOM is interested to contribute the code around Open Air Interface
(OAI) to the OAI Software Alliance

</td>  
<td>

</td>  
<td>

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

MI

</td>  
<td>

4) MI will contribute to ITU-T SG20

</td>  
<td>

</td>  
<td>

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

DG

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

KDDI

</td>  
<td>

4) KDDI will contribute to 3GPP SA2 WG and 5GMF Technology Promotion Group

</td>  
<td>

</td>  
<td>

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

HITACHI

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

NESIC

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WU

</td>  
<td>

4) Waseda will contribute to ITU-T FG IMT-2020 and may be to SG13

</td>  
<td>

</td>  
<td>

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

#  Collection, Storage and Use of Research Data and Analysed Research Data

The research data will be collected following jointly agreed guidelines and
principles in order to guarantee the achievement of sound research data and to
make the reusability of the research data possible. Possible data flows are
presented in Figure 4.

**Figure 4 Open access to scientific publication and research data in the
wider context of dissemination**

**and exploitation (Source: H2020 Programme, Guidelines on Open Access to
Scientific Publications and Research Data in Horizon 2020, Version 3.1, 25
August 2016).**

#  Storage and Use of Project Data

##  Storage of Data

The data accumulated in the 5G!Pagoda project will be analysed and stored
according to the principles detailed in this plan. Overall the detailed
research data will be stored by the organisations which has collected it, and
the project data will be stored by Aalto University. Both the central
repository and the databases of the individual organisations will be secured
using the latest security protocols, and access to data will be granted only
for persons nominated by the project partners.

All project administrative data will be stored at a dedicated database for the
5G!Pagoda project. The project uses the OwnCloud repository (https://
_https://5g-pagoda.aalto.fi/owncloud/_ )  , which is a secure, password
protected document repository and archive system. Access to the database is
managed by the coordinator and provided for project consortium and other
parties as deemed necessary by the project team. The project data is stored on
Aalto University servers, not in the cloud, for added security. The project
data management structure and categories are as follows.

Workpackages

WP1

WP2

WP3

WP4

WP5

WP6

Templates

Standards-Activities

Project Meetings

Physical Meetings

ConfCalls

Market Analysis

Deliverables

WP1

WP2

WP3

WP4

WP5

WP6

Admin Relevant

Original DoA

Grant Agreement

Consortium Agreement

Coordination Agreement

The 5G!Pagoda Project Management, Quality and IPR Guide details the project
internal management structure and processes, as well as quality and reporting
practices. Related to project data management, best practices for data
generation and sharing have been applied. This includes set rules for version
control, whereby the partners are encouraged to use unified methods for naming
the documents by the Task or Deliverable name, with a corresponding version
number. The documents are stored in the database and preferably shared within
the consortium via a link to the database rather than e-mail attachments. All
deliverables have a unified look and feel with a unified template which helps
the reviewers in their project evaluation.

The project coordinator assumes the responsibility for timely documentation
and sharing of project management related documents and materials. Each Work
Package (WP) leader monitors the timely documentation of WP related
requirements within the consortium. Each task leader ensures the timely
production of the deliverable for which he/she is responsible. With the
strongly inter-related and intertwined Tasks in the different Work Packages,
the same previously described principles regarding e.g. confidentiality levels
and data types will be applied.

##  Documenting of Data

The stored data needs to be provided with metadata that complies with an
international metadata standard. To facilitate this, the following questions
should be answered already during the research work:

  * Who are the creators and what are their affiliations 

  

  * Where the data is located and is there a persistent identifier 

  

  * What is the license chosen to allow reuse 

  

  * How, when and by whom the data has been collected/ created 

  

  * How the data has been prepared for analysis 

  

  * What kind of data manipulations have taken place 

  

  * How and what methods have been used to analyse the data 

  

  * What instruments and devices have been used 

  

  * Which scientific publications are based on this data 

  

  * What is the software used to process and analyse the data 

  

Available metadata standards are listed e.g. in these sites:

  * _General Metadata standards_ listed by the Digital Curation Center (DCC) UK 

  

  * _Discipline-specific metadata standards_ listed by the Digital Curation Center (DCC) UK 

  

  * _Metadata standards by topic_ listed by the Research Data Alliance (RDA) 

  

It is imperative to get a persistent identifier for data so that it is
findable and citable. The most common identifier is Digital Object Identifier
(DOI). Appropriate data repositories provide persistent identifiers for data
sets.

The 5G!Pagoda project intends to use  _DataSite_ digital identifier for
research data. For more details about DOI, the interested reader may refer to
th  e _International DOI Foundation (IDF_ )  .

To license a dataset requires either 1) that all creators agree to release the
data they have created using the same license; or 2) the ownership of datasets
is transferred to one legal entity. One straightforward and effective way of
doing this is to attach  _Creative Commons_ _Licences_ ( _CC BY_ o  r  _CC0_ )
to the data deposited. Th  e _EUDAT B2SHARE_ t  ool includes a built-in
license wizard that facilitates the selection of an adequate license for
research data.

Table 4 presents the planned Open Access Data of the project. For repositories
see Chapter 5.

**Table 4 Curation of stored open data.**  
  
<table>  
<tr>  
<th>

**Partner**

</th>  
<th>

**Data type**

</th>  
<th>

**Repository**

</th>  
<th>

**Metadata standard**

</th>  
<th>

**License standard**

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

All partners

</td>  
<td>

PU deliverables

</td>  
<td>

Participant Portal

</td>  
<td>

</td>  
<td>

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

AALTO

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

UT

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

Ericsson

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

Orange

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

Orange

</td>  
<td>

Software

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

EI

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

EI

</td>  
<td>

Software

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

MI

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

DG

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

WU

</td>  
<td>

Publications

</td>  
<td>

TBD

</td>  
<td>

TBD

</td>  
<td>

TBD

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

#  Data Sharing

All parties have signed the Coordination Agreement and the European Partners
have signed/accessed to the project Grant Agreement and Consortium Agreement,
which all together detail the parties’ rights and obligations, including – but
not limited to – obligations regarding data security and the protection of
privacy. These obligations and the underlying legislation will guide all of
the data sharing actions of the project consortium.

The 5G!Pagoda project has committed to participate in the Pilot on Open
Research Data in Horizon 2020, which is an expression of the larger Open
Access initiative of the European Commission  1  . Participation in the pilot
is manifested on two levels: a) depositing research data in an open access
research database or repository and b) choosing to provide open access to
scientific publications which are derived from the project research. At the
same time, the consortium is dedicated to protect the privacy of the
informants and companies.

##  Depositing Research Data

Following the principles of the European Commission Open Data pilot, the
applicable research data gathered in the project will be made available to
other researchers through open access database or repositories, in order to
increase the potential exploitation of the project work.

To make research data openly accessible, the following matters shall be
considered:

  * Specify which data will be made openly available? If some data is kept closed, provide rationale for doing so 

  

  * Specify how the data will be made available 

  

  * Specify what methods or software tools are needed to access the data? Is documentation about the software needed to access the data included? Is it possible to include the relevant software (e.g. in open source code)? 

  

  * Specify where the data and associated metadata, documentation and code are deposited 

  

  * Specify how access will be provided in case there are any restrictions 

  

  * Assess the interoperability of your data. Specify what data and metadata vocabularies, standards or methodologies you will follow to facilitate interoperability. 

  

There are online research data archives, which may be subject-based/thematic,
institutional or centralised. Useful listings of repositories include the
Registry of  _Research Data Repositories_ a  nd  _Databib_ .  The Open Access
Infrastructure for Research in Europe (OpenAIRE) provides additional
information and support on linking publications to underlying research data.
Some repositories like  _Zenodo_ (an OpenAIRE and CERN collaboration), allows
researchers to deposit both publications and data, while providing tools to
link them. Zenodo and some other repositories as well as many academic
publishers also facilitate linking publications and underlying data through
persistent identifiers and data citations.

##  Open Access Publishing

All peer-reviewed scientific publications relating to results are published so
that open access (free of charge, online access for any user) is ensured.
Publications will either immediately be made accessible online by the
publisher (Gold Open Access), or publications are available through an open
access repository after an embargo period, which according to the Grant
Agreement can be six months at maximum (Green Open Access). Possible Gold Open
Access journals include IEEE Access Magazine. For all other articles, the
researchers aim at publishing them in a Green Open Access repository. The
coordinator, Aalto University, has a Green Open Access repository the
5G!Pagoda consortium can use, at  _https://aaltodoc.aalto.fi/?locale-
attribute=en_ .

A repository for scientific publications is an online archive. Institutional,
subject-based and centralised repositories are all acceptable choices.

The  _Open Access Infrastructure for Research in Europe_ _(OpenAIRE)_ i  s the
recommended entry point for researchers to determine what repository to
choose. It also offers support services for researchers, such as the National
Open Access Desks. Other useful listings of repositories are:

  * _Registry_ _of Open Access Repositories (ROAR)_

  

  * _Directory_ _of Open Access Repositories_ _(OpenDOAR)_

  

A machine-readable electronic copy of the published version or final peer-
reviewed manuscript accepted for publication will be available in a repository
for scientific publications. Electronic copies of publications will have
bibliographic metadata in a standard format and will include "European Union
(EU)" and "Horizon 2020", the name of the action, acronym and grant number;
publication date, and length of embargo period if applicable, and identifier.

_ORCID_ identifier is used to identify the authors of publications in the
5G!Pagoda project.

##  Other Dissemination

In addition to the above, the project will release yearly a public report on
standardization, dissemination and exploitation achievements (deliverables
D6.2, D6.3, and D6.4). At the end of the project, a report on innovation
achieved and forthcoming industrial exploitation will be also released (D6.5).

#  Opting Out Research Data

The 5G!Pagoda project can opt out at any stage and so free itself
retroactively from the obligations associated with the conditions – if:

  * participation is incompatible with the obligation to protect results that can reasonably be expected to be commercially or industrially exploited 

  

  * participation is incompatible with the need for confidentiality in connection with security issues 

  

  * participation is incompatible with rules on protecting personal data 

  

  * participation would mean that the project's main aim might not be achieved 

  

  * the project will not generate / collect any research data or 

  

  * there are other legitimate reasons 

  

Alternatively, the 5G!Pagoda project can also choose to keep selected datasets
or even all data closed for any of the reasons above, via this Data Management
Plan.

At this phase of the project no research data is identified and thus opting
out is not relevant.

#  Summary and Perspectives

The Open data management plan will be updated during the project lifetime if
new practices for data management are introduced.