#  EXECUTIVE SUMMARY

The present document represents “D1.3 Data Management Plan” of the PASSION
Project. The project aims at the development of new photonic technologies to
support agile metro networks, enabling capacities of Tb/s per spatial channel,
100 Tb/s per link and Pb/s per node over increased transport distances. The
project breakthroughs are achieved by developing all the essential photonic
building blocks. On the transmitter side, a novel 3D stacked modular design
will be developed combining a silicon photonics (SiPh) circuit layer with
directly modulated high-bandwidth 1550nm VCSELs light sources. At the receiver
side a novel InP based coherent receiver array which handles polarization on
chip making polarization handling off chip unnecessary will be implemented.
Finally, the partners will develop a compact and cost-effective switching
concept which can support the Pb/s capacities generated by the transceiver
modules, using a combination of InP and SiPh PICs.

In order to achieve the claimed objective project partners will have to
collect and manage data related to several domains: suppliers’ data (e.g.
projects, technical details of market technologies), technological details
delivered throughout the project (e.g. tests results), partners’ personal data
(e.g. emails of partners personnel), and data collected from dissemination
activities (e.g. data collected through presentations, communication through
social media).

The purpose of this document is to provide the plan for managing the data
generated and collected during the project; the Data Management Plan (DMP).
Specifically, the DMP describes the data management life cycle for all
datasets to be collected, processed and/or generated by a research project. It
covers:

  * the handling of research data during and after the project 

  

  * which data will be collected, processed or generated 

  

  * which methodology and standards will be applied 

  

  * whether data will be shared/made open and how 

  

  * how data will be curated and preserved 

  

Following the EU’s guidelines regarding the DMP, this document is prepared for
M6 and will be updated, if necessary, during the project lifetime (in the form
of an updated deliverable).

#  INTRODUCTION

##  DMP AND AUDIENCE

This document is the PASSION Data Management Plan that the project consortium
is required to create as the project participates to the Open Research Data
pilot. The DMP describes the data management life cycle for all datasets to be
collected, processed and/or generated by a research project.

The intended audience for this document is the PASSION consortium, the
European Commission, and all stakeholders (e.g. technology suppliers, research
community, etc.) who will interact with the project in several forms and whose
data will be collected by the project partners.

##  METHODOLOGY

The methodology used by the consortium to prepare the document is as follows.

  * The objectives and the general structure of the DMP were illustrated and shared with partners. 

  

  * A template for the collection of data was defined. 

  

  * Each partner was invited to prepare an individual contribution to the DMP. 

  

  * Contributions were integrated and revised. 

  

##  STRUCTURE OF THE DMP

For each identified data set the DMP provides a description of the following
elements.

  * Data summary, describing the types of data, the origin of the data (generated internally or collected from external sources), how they fit into the project (where they are produced or collected and what contribution is provided to project objectives). 

  

  * Details on how to make data findable, including provisions for metadata. 

  

  * Details on how to access data and how data will be findable and accessible. 

  

  * Details on how to make data interoperable. 

  

  * Policies to support re-use and sharing of data. 

  

  * Resources necessary to support the collection and maintenance of data. 

  

  * Policies to guarantee a secure management of data. 

  

  * Ethical aspects and other issues. 

  

These elements correspond to the sections of the document. The elements are
provided for each partner.

#  INDIVIDUAL DMP

For each partner, details on data sets and how they will be produced, managed,
and shared in accordance with EU indications on DMP are provided in the
following sections.

##  DATA SUMMARY  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

POLIMI will collect data on:

  1. test measurement of transmitters, receivers, and node characterization of device, systems, and sub-systems 

  

  2. simulation of systems and sub-systems performance 

  

  3. simulation of device design for systems and sub-systems 

  

  

Collection of data is instrumental to achieve the following objectives of the
project:

Objective 1. Design and development of photonic technologies for the
realization of a new generation of energy-efficient and compact transmitter
(Tx)

modules for the metro network enabling up to Tb/s capacity per PIC Objective
2. Design and development of photonic technologies for the realization of a
new generation of compact, flexible receiver (Rx) modules for the metro
network, able to sustain the PASSION sliceable- bandwidth/bitrate approach.

Objective 4. Design and development of scalable and modular S-BVT

architectures, allowing to adaptively generate multiple flows of Tb/s capacity
and enabling up to 100 Tb/s aggregated capacity per link

Objective 5. Development of scalable and modular metro network architectures
for subsystem sharing and functional reuse to support flexible agile
spectrum/spatial switching addressing capacities of Pb/s per node.

In particular, data will be used in the following WPs: 2, 3, 5.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data are useful for the technology partners
(VTT, TUE, VERT, CTTC, EFP, NICT), for technology suppliers (SMO, TID), for
dissemination partners (EPIC).

Data format will comprise Excel files (.xls), Matlab files (.mat, .dat), txt.

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request to POLIMI and be approved (if necessary after consultation with the other PASSION partners). 

  

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

2\. CTTC

</td>  
<td>

CTTC will collect data on:

  1. Measurements and experimental analysis of transmitters, receivers, systems, and sub-systems, related to the PASSION S-BVT architectures supported by the developed photonic technologies and devices 

  

  2. Simulation of systems and sub-systems for suitable transceiver architecture design and performance evaluation 

  

  3. Overall setup time attained in the targeted project demonstrations when automatically programming an end-to-end optical connection involving transmitters, receivers and optical switch nodes developed according to the devised PASSION solutions. 

  

  4. Devised data model (YANG) and related encoding (JSON or.XML) for configuring and retrieving status of the PASSION network elements and devices. 

  

  5. Collection of different performance metrics (i.e., connection blocking, average SBVT utilization, average optical spectrum usage, control setup time, etc.) when dynamically provisioning optical flows aligned with the defined PASSION use cases 

  

  

The collection of this data is crucial to cope with the following PASSION
objectives:

Objective 4. Design and development of scalable and modular S-BVT

architectures, allowing to adaptively generate multiple flows of Tb/s capacity
and

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

</th>  
<th>

enabling up to 100 Tb/s aggregated capacity per link

Objective 5. Development of scalable and modular metro network architectures
for subsystem sharing and functional reuse to support flexible agile
spectrum/spatial switching addressing capacities of Pb/s per node.

In particular, the generated data will be used within WP2 and WP5.

Data are generated by project activities; specific existing data (such as
systems and sub-systems specifications) on CTTC laboratory facilities and

ADRENALINE Testbed® are envisioned to be shared (re-used) if needed by the
project.

In the context of the project, data are useful for the rest of the PASSION
partners including technology partners, technology suppliers and dissemination
partners.

Data format will comprise Excel files (.xls), Word Documents (.doc), .txt, as
well as specific files for the used data model (.yang) and the protocol
encoding (.xml or .json)

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request to CTTC either directly or through the coordinator POLIMI and be approved (if necessary after consultation with the other PASSION partners). 

  

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

3\. TUE

</td>  
<td>

TUE will collect data on:

  1. simulation of device design for systems and sub-systems 

  

  2. devices fabrication 

  

  3. test measurement of transmitters, receivers, and node characterization of device, systems, and sub-systems 

  

  

Collection of data is instrumental to achieve the following objectives of the
project:

Objective 1. Design and development of photonic technologies for the
realization of a new generation of energy-efficient and compact transmitter
(Tx) modules for the metro network enabling up to Tb/s capacity per PIC
Objective 2. Design and development of photonic technologies for the
realization of a new generation of compact, flexible receiver (Rx) modules for
the metro network, able to sustain the PASSION sliceable- bandwidth/bitrate
approach.

Objective 3: Development of energy-efficient and small-footprint switching
technologies for a node featuring functional aggregation/disaggregation,
together with switching in the space and wavelength domain in order to handle
1-Pb/s capacity.

Objective 4. Design and development of scalable and modular S-BVT

architectures, allowing to adaptively generate multiple flows of Tb/s capacity
and enabling up to 100 Tb/s aggregated capacity per link

Objective 5. Development of scalable and modular metro network architectures
for subsystem sharing and functional reuse to support flexible agile
spectrum/spatial switching addressing capacities of Pb/s per node.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data are useful for the technology partners

(POLIMI, VTT, VERT, CTTC, EFP, NICT), for technology suppliers (SMO, TID), for
dissemination partners (EPIC).

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

</th>  
<th>

Data format will comprise Excel files (.xls), Matlab files (.mat, .dat), txt.
GDS files (.gds) and photos (.jpg)

Access to data will be granted to:

\- all partners of the PASSION project

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

4\. VTT

</td>  
<td>

VTT will collect data on:

  1. Optical, Electrical, Thermomechanical Simulations of Silicon Photonic chips, fiber-coupled packaged transmitter modules with VCSEL and node switching sub-assemblies. 

  

  2. Test measurement of the above at room temperature and operating temperatures 

  

  

Collection of data is instrumental to achieve the following objectives of the
project:

Objective 1. Design and development of photonic technologies for the
realization of a new generation of energy-efficient and compact transmitter
(Tx) modules for the metro network enabling up to Tb/s capacity per PIC

Objective 2. Highly dense Packaging Design and manufacturing technologies for
VCSEL-based, energy-efficient,Tb/s capacity transmitter (Tx) modules

In particular, data will be mainly used in the following WPs: 3, 4\.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data are useful for the technology partners
(TUE, VERT, VLC, OPSYS, POLIMI), for technology suppliers (SMO, TID), for
dissemination partners (EPIC).

Data format will comprise Excel files (csv.xls), Matlab files (.mat, .dat),
txt.

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request to POLIMI and be approved (if necessary after consultation with the other PASSION partners). 

  

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

5\. VERT

</td>  
<td>

Vertilas will collect data on:

  1. Test data of VERTILAS VCSELs 

  

  2. Test data of VERTILAS VCSELs with laser drivers 

  

  3. Data on optical coupling of VCSELs and PICs 

  

  4. Data on assembly and integration of VCSELs and PICs This data is required to achieve the following objectives: 

  

  

Objective 1. Verify the VCSEL design and laser prodiuctio parameters Objective
2: Characterise the VCSELs for project partners for system design concept,
module integration and performance evaluation.

Objective 3: Set requirements and operation parameters to operate VCSELs with
other components and achieve optimized performance

Objective 4: Provide data to partners to derive system requirements from

VCSELs functionality and performance

Objective 5. Define and support component integration techniques

Data generated by VERTILAS is useful for project partners, e.g. POLIMI; VTT,
TUE, CCTC and others. For dissemination, data can be provided to EPIC.

Data formats used will be mainly excel files, graphs and text (word,
powerpoint). Data will be made accessible to project partners for the system
design and component integration.

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

6\. VLC

</td>  
<td>

VLC will collect data on:

  1. Simulation data for the design and layout of photonic integrated circuits. 

  

  2. Characterization of photonic integrated circuits and building blocks. Collection of data is instrumental to achieve the following objectives of the project: 

  

  

Objective 1. Improving the performance of the target PICs through iterative
design based on characterization data.

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

</th>  
<th>

Objective 2. Performance evaluation towards achieving the target goals.
Objective 3. Validating the fabrication platforms.

In particular, data will be used in the following WPs: 3, 4, and partially 5.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data might be useful for the technology
partners (VTT, TUE, POLIMI, VERT, OPSYS, SMO, EFP, ETRI).

Data format will comprise Excel files (.xls), Matlab files (.mat, .dat), .txt.
GDS design files will not be shared.

Access to data will be granted to:

  * all requesting partners of the PASSION project 

  

  * external organisations that will submit an access request to POLIMI and be approved (if necessary after consultation with the other PASSION partners). 

  

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

7\. OPSYS

</td>  
<td>

OPSYS will collect data on:

1\. Characterization data different types of switches and WSS. Data on
performance of node different parts and at the end the sub-systems and system
level performance including different transmission scenarios. 2. Data on
Techno-economic analysis of the proposed solutions

3\. Data on recommended device packaging design reliable for the sub-systems
integration

Collection of data is instrumental to achieve the following objectives of the
project:

Objective 1. Design and development of photonic technologies for the
realization of a new generation of energy-efficient and compact transmitter
(Tx) modules for the metro network enabling up to Tb/s capacity per PIC
Objective 3: Development of energy-efficient and small-footprint switching
technologies for a node featuring functional aggregation/disaggregation,
together with switching in the space and wavelength domain to handle 1-Pb/s
capacity. In particular:

  * Design of the optical switching node with added flexibility through implementation of different levels of aggregation, as in spectrum and in space, to improve effective and agile usage of the traffic pipes. 

  

  * Design of compact and low number of electrodes WSSs and low insertion loss high connectivity WDM and multicast switches (MCSs). 

  

Objective 4. Design and development of scalable and modular S-BVT
architectures, allowing to adaptively generate multiple flows of Tb/s capacity
and enabling up to 100 Tb/s aggregated capacity per link

Objective 5. Development of scalable and modular metro network architectures
for subsystem sharing and functional reuse to support flexible agile
spectrum/spatial switching addressing capacities of Pb/s per node.

In particular, data will be used in the following WPs: 2, 3, 4, 5\.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data are useful for the technology partners
(TUE, ETRI, VLC, EFP, VTT), for technology suppliers (SMO, TID, VERTILAS), for
dissemination partners (EPIC).

Data format will comprise Excel files (.xls), Matlab files (.mat, .dat), txt.

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request to POLIMI and be approved (if necessary after consultation with the other PASSION partners). 

  

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

8\. EFP

</td>  
<td>

EFP will collect data on:

  * Chip level DC qualification (i.e. quantify DC figures of merit of components) 

  

  * Chip level RF qualification (i.e. quantify electro-optical response of components) 

  

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

</th>  
<th>

  * Wafer level qualification (i.e. photoluminescence measurements) 

  

  * Prototype DC&RF qualification (i.e. verify prototype design satisfy requirements) 

  

Collection of these data is key to achieve:

Objective 2. Design and development of photonic technologies for the
realization of a new generation of compact, flexible receiver (Rx) modules for
the metro network, able to sustain the PASSION sliceable- bandwidth/bitrate
approach.

Yet, as all project objectives are correlated, feedback from the above is
relevant to the achievement of the other project objectives. No re-use of
previously generated data is foreseen.

Data in custom trext files, and in the case of the wafer level qualification,
additional PL reports generated by software from equipment vendor.

Only relevant plots, and/or values of relevant figures of merit will be shared
to project partners when necessary and/or requested.

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

9\. SMO

</td>  
<td>

SMO will collect data on:

  1. measurement of the telecommunication nodes and related sub-system, which will be developed and/or integrated during the Project development. 

  

  2. simulation results that will be produced during the project execution will be part of the collected data. 

  

  

Data collection will be manly used to:

1\. characterise the behaviour of the developed systems and sub-systems,
according to the Project objectives. In particular:

  * transmitter (Tx) and receiver (Rx) modules for the metro network enabling up to Tb/s capacity per PIC; 

  

  * optical nodes and switching capacity; 

  

  * scalable and modular metro network architectures; 

  

  * demonstration results and statistics 

  

Data format will include the most common file format (e.g. Excel files _.xls_
, Matlab files _.mat_ , _.dat_ , Word files _.doc_ , _.docx_ , PowerPoint
files _.ppt_ , _.pptx_ , Text files _.txt_ , etc.)

Access to data will be granted to: all partners of the PASSION project
external organisations that will submit an access request to POLIMI as
coordinator. PASSION partners will approve access grant.

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

10\. TID

</td>  
<td>

Telefonica is collecting and sharing information about real network topologies
and their physical characteristics for network design and techno-economic
analysis. Telefonica is not providing any information about customers data.

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

11\. EPIC

</td>  
<td>

EPIC will collect data on:

1\. End-user companies interested in the technology developed by PASSION 2.
Companies interested in providing the components to the PASSION supply chain
for the next generation of metro network based on PASSION technology

  3. Companies interested in the standards developed or adopted by PASSION 

  

  4. European Projects competing/complementing PASSION 

  

  

Collection of data is instrumental to achieve the following objectives of the
project:

  * Objective 1: provide recommendations on migration and roadmap for industrialization; 

  

  * Objective 2: coordinate and perform project results dissemination, giving appropriate visibility of PASSION to the relevant European, national and international forums; 

  

  * Objective 3: promote the technical results of PASSION to the European and global research community (e. g. setting up a project web site, dissemination 

  

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

</th>  
<th>

events);

  * Objective 4: coordination of dissemination activities (e.g. participation in conferences, contribution to scientific journals, organization of workshops and events, etc.); 

  

  * Objective 5: exchange with other projects active in neighbouring fields with similar focus (within and possibly outside EU HORIZON2020); 

  

  * Objective 6: generate a software tool for metro network design useful for the operators willing to exploit PASSION technologies, devices and architectures; - Objective 7: participate to international standardization bodies 

  

Data are generated by attending the events, organizing the workshops and also
through the website and social media; no re-use of previously generated data
is foreseen in this context.

In the context of the project, data are useful for the technology partners
(VTT, TUE, VERT, CTTC, EFP, NICT), for technology suppliers (SMO, TID), for
dissemination partners (EPIC).

Data format will comprise Excel files (.xls) and txt.

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request and be approved (if necessary after consultation with the other PASSION partners). 

  

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

12\. NICT

</td>  
<td>

NICT will collect data on:

1\. test measurement of transmitters, receivers, and node characterization of
device, systems, and sub-systems

Collection of data is instrumental to achieve the following objectives of the
project:

Objective 1. Design and development of photonic technologies for the
realization of a new generation of energy-efficient and compact transmitter
(Tx)

modules for the metro network enabling up to Tb/s capacity per PIC Objective
2. Design and development of photonic technologies for the realization of a
new generation of compact, flexible receiver (Rx) modules for the metro
network, able to sustain the PASSION sliceable- bandwidth/bitrate approach.

Objective 4. Design and development of scalable and modular S-BVT

architectures, allowing to adaptively generate multiple flows of Tb/s capacity
and enabling up to 100 Tb/s aggregated capacity per link

Objective 5. Development of scalable and modular metro network architectures
for subsystem sharing and functional reuse to support flexible agile
spectrum/spatial switching addressing capacities of Pb/s per node.

In particular, data will be used in WP 5.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

In the context of the project, data are useful for the technology partners
(VTT, TUE, VERT, CTTC, EFP, NICT), for technology suppliers (SMO, TID), for
dissemination partners (EPIC).

Data format will comprise Excel files (.xls), Matlab files (.mat, .dat), txt.

Access to data will be granted to:

  * all partners of the PASSION project 

  

  * external organisations that will submit an access request to NICT and be approved (if necessary after consultation with the other PASSION partners). 

  

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

13\. ETRI

</td>  
<td>

ETRI will collect data on:

  1. Mask design of the photonic space switch (polymer based optical matrix switch). 

  

  2. Simulation results of switching characteristics (e.g. BPM simulation) 3. Device (Chip) Characterization results: 

     * optical insertion loss, polarization dependent loss, extinction ratio, electrical switching power 

  

     * waveguide cross-section analysis, SEM & EDAX 

  

  

  

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

</td>  
<td>

Objective of the data collection:

\- Development of energy-efficient and small-footprint switching technologies
for a node featuring functional aggregation/disaggregation, together with
switching in the space domain.

Data will be used in the following WPs: 4, 5.

Data are generated by project activities; no re-use of previously generated
data is foreseen in this context.

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

##  MAKING DATA FINDABLE  
  
<table>  
<tr>  
<th>

1\.

POLIMI

</th>  
<th>

•

</th>  
<th>

Data will be stored in a shared folder called PASSION DATA

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0)

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

</td>  
<td>

•

</td>  
<td>

Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT]

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

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

</td>  
<td>

•

</td>  
<td>

Access to data will be guaranteed for the duration of the project and for 6
months after the end of the project

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

2\.

CTTC

</td>  
<td>

•

</td>  
<td>

Data will be stored in a shared folder called PASSION DATA

(ttps://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0)

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

</td>  
<td>

•

</td>  
<td>

Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT]

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (e.g. SIM for simulation, TST for test, DES for design, …) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

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

</td>  
<td>

•

</td>  
<td>

Access to data will be guaranteed for the duration of the project and for 6
months after the end of the project

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Data will be stored in a shared folder

( _https://www.dropbox.com/sh/njorvbpkal6hptw/AADdsrhZ-lUmztQm7e2laUgKa?dl=0_
)

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

</td>  
<td>

•

</td>  
<td>

Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT]

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

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

</td>  
<td>

•

</td>  
<td>

Access to data will be guaranteed for the duration of the project and for 6
months after the end of the project

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Data will be stored in a shared folder called PASSION DATA

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0)

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

</td>  
<td>

•

</td>  
<td>

Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT]

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

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

</td>  
<td>

•

</td>  
<td>

Access to data will be guaranteed for the duration of the project and for 6
months after the end

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

</th>  
<th>

of the project

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

5\.

VERT

</td>  
<td>

  * Technical information and VCSEL parameters for project partners will be stored on the shared folder (Repository URL will be provided once ready) 

  

  * Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT] 

  

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

Access to data will be guaranteed for the duration of the project and for 6
months after the end of the project

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

6\. VLC

</td>  
<td>

  * Data will be stored in a shared folder called PASSION DATA 

  

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0 )

  * Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT] 

  

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

  * Access to data will be guaranteed for the duration of the project and for 6 months after the end of the project 

  

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

7\.

OPSY

S

</td>  
<td>

  * Data will be stored in a shared folder called PASSION DATA 

  

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0 )

  * Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT] 

  

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

  * Access to data will be guaranteed for the duration of the project and for 6 months after the end of the project 

  

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

8\. EFP

</td>  
<td>

  * Data stored in in-house database 

  

  * Since only relevant plots and/or values of relevant figures of merit will be provided when necessary and/or requested, the internally used naming conventions are irrelevant to share 

  

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

9\. SMO

</td>  
<td>

  * All the relevant data collected will be send to the Project Coordinator. PoliMI will store and manage the data in a shared folder called PASSION DATA 

  

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0)

  * Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT] 

  

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

  * Access to data will be guaranteed for the duration of the project and for 6 months after the end of the project 

  

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

10\. TID

</td>  
<td>

• Reference Network topologies and fibre characteristics are reported in D21.

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

11\. EPIC

</td>  
<td>

  * Data will be stored in a shared folder called PASSION DATA 

  

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0 )

  * Naming convention will be: [Name of the company]_[Website of the company]_[Name of the contact]_ [Details of the company] 

  

  * Access to data will be guaranteed for the duration of the project and for 6 months after the end of the project 

  

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

12\. NICT

</td>  
<td>

  * Data will be stored in a shared folder (Dropbox URL) 

  

  * Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT] 

  

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

  * Access to data will be guaranteed for the duration of the project and for 6 months after the end of the project 

  

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

Data will be stored in a shared folder called PASSION DATA

(https://www.dropbox.com/sh/gr43zcj8vmqaeox/AAAV1NftJ85mNngZRmNGXWXDa?dl=0 )

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

</td>  
<td>

•

</td>  
<td>

Raw measurement data will be stored in the local server of ETRI

(Measurement data will be shared to the project cloud shared folder if
requested)

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

</td>  
<td>

•

</td>  
<td>

Naming convention will be: [WP#]_[CODE]_ [CONTENT DATA]_[V].[EXT]

  * [WP#] indicated the number of WP that generated the data. Optional 

  

  * [CODE] indicates the type of data (SIM for simulation, TST for test, DES for design) 

  

  * [V] indicates the version of the file 

  

  * [EXT] is the extension of the file 

  

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

</td>  
<td>

•

</td>  
<td>

Access to data will be guaranteed for the duration of the project and for 6
months after the end of the project

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

##  MAKING DATA OPENLY ACCESSIBLE  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

2\. CCTC

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.).

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files.

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

Only relevant plots and/or values of relevant figures of merit will be
provided to project partners when necessary and/or requested. This will be
done by e-mail or on project’s shared folder (access granted by the
coordinator, who is the repository owner)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications of common use (e.g. Microsoft
Office, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

</td>  
<td>

•

</td>  
<td>

The project will not provide the tool and the licenses that may be needed to
read the stored data.

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

10\. TID

</td>  
<td>

•

</td>  
<td>

Reference networks and cost models will be included in public deliverables

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

Data will be available to all project partners through access to the shared
folder. Access to folder will be granted by the repository owner (coordinator)

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

</td>  
<td>

•

</td>  
<td>

Data can be accessed through applications that depends on the format of data
(e.g. MW Office or other office software, Matlab, etc.)

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

</td>  
<td>

•

</td>  
<td>

No metadata will be associated to the files

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

##  MAKING DATA INTEROPERABLE  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

2\. CCTC

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present.

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

</td>  
<td>

•

</td>  
<td>

PDAflow foundation standards will be used to compile any PDK or design
library, making them interoperable with the main photonic design frameworks.

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

Not applicable

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

10\. TID

</td>  
<td>

•

</td>  
<td>

No issues on interoperability are expected

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

No specific issues of interoperability are present

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

</td>  
<td>

•

</td>  
<td>

Since data will be “flat” and consist of one single entity with attributes,
structure of data will not be described and the schema of the table will be
representative of the structure

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

</td>  
<td>

•

</td>  
<td>

Mapping with ontologies will not be provided

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

##  INCREASE DATA REUSE  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

Use of data will be freely available to all partners following the access
rights regulated by the PASSION CA

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

</td>  
<td>

•

</td>  
<td>

After the end of the project partner will agree on the kind of access to data
and on the limitations (including embargo periods)

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

</td>  
<td>

•

</td>  
<td>

Quality of data will be guaranteed through repetition of tests

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

2\. CTTC

</td>  
<td>

•

</td>  
<td>

Use of data will be freely available to all partners following the access
rights regulated by the PASSION CA

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

</td>  
<td>

•

</td>  
<td>

After the end of the project, partners will agree on the kind of access to
data and on the limitations (including embargo periods)

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

</td>  
<td>

•

</td>  
<td>

Quality of data will be guaranteed through repetition of tests

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Use of data will be freely available to all partners following the access
rights regulated by the PASSION CA

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

</td>  
<td>

•

</td>  
<td>

After the end of the project partner will agree on the kind of access to data
and on the limitations (including embargo periods)

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

</td>  
<td>

•

</td>  
<td>

Quality of data will be guaranteed through repetition of tests

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Use of data will be freely available to all partners following the access
rights regulated by the PASSION CA

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

</td>  
<td>

•

</td>  
<td>

After the end of the project, partner will agree on the kind of access to data
and on the limitations (including embargo periods)

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

</td>  
<td>

•

</td>  
<td>

Quality of data will be guaranteed through repetition of tests if specifically

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

</td>  
<td>

authorized by the project coordinator

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

5\. VERT

</td>  
<td>

  * Licensing of VERTILAS data is not planned 

  

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

6\. VLC

</td>  
<td>

  * Use of data will be freely available to all partners for R&D purposes, following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

7\. OPSYS

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

8\. EFP

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project, partners will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

9\. SMO

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

10\. TID

</td>  
<td>

• Reference Networks and cost models included in public deliverables can be
freely reused

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

11\. EPIC

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

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

12\. NICT

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

Quality of data will be guaranteed through repetition of tests

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

13\. ETRI

</td>  
<td>

  * Use of data will be freely available to all partners following the access rights regulated by the PASSION CA 

  

  * After the end of the project partner will agree on the kind of access to data and on the limitations (including embargo periods) 

  

  * Quality of data will be guaranteed through repetition of tests 

  

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

##  ALLOCATION OF RESOURCES  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

2\. CTTC

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository

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

</td>  
<td>

</td>  
<td>

owner

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Data will be kept in Dropbox, no extra cost

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

10\. TID

</td>  
<td>

•

</td>  
<td>

Costs are included in the technical WP effort

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner
(coordinator)

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

Costs of maintaining the repository of the data are covered by the hosting
institution and will not be charged on the project

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

</td>  
<td>

•

</td>  
<td>

Responsible for the maintenance of the infrastructure is the repository owner

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

##  DATA SECURITY  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, Coordinator will access to data through
dedicated app that will guarantee replication of data at local level

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

2\. CTTC

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, CTTC will access to data through dedicated app
that will guarantee replication of data at local level

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, TUE will access to data through dedicated app
that will guarantee replication of data at local level

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, VTT will access to data through dedicated

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

</td>  
<td>

</td>  
<td>

app that will guarantee replication of data at local level

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, VERT will access to data through dedicated app
that will guarantee replication of data at local level

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, VLC will access to data through dedicated app
that will guarantee replication of data at local level

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

Data are stored in in-house database and partially shared through the cloud
repository

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

Data is stored in an in-house database and local storage with back-up online

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, SMO will access to data through dedicated app
that will guarantee replication of data at local level

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

10\. TID

</td>  
<td>

•

</td>  
<td>

Project information is stored in cloud back ups.

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

Address data recovery as well as secure storage and transfer of sensitive data

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

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, EPIC will access to data through dedicated app
that will guarantee replication of data at local level

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

Since data are stored in a shared cloud repository, cloud will guarantee
backups of data. Furthermore, NICT will access to data through dedicated app
that will guarantee replication of data at local level

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

Since data related to PASSION project are stored in a shared cloud repository,
cloud will guarantee backups of data. Furthermore, ETRI network blocks the
unauthorized access from outside and only limited information (e.g. e-mail,
electronic approval system) is accessible through VPN connection. The
unauthorized USB memory cannot be used at the computers in the ETRI networks.

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

##  ETHICS  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

2\. CTTC

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

No ethical issues are associated to the process of collecting data, to their
content and maintenance

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

10\. TID

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

Sensitive data are collected. Contacts must agree to share their contact
information.

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

No sensitive data are collected. No personal data are collected. No ethical
issues is associated to the process of collecting data, to their content and
maintenance

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

##  OTHER  
  
<table>  
<tr>  
<th>

1\. POLIMI

</th>  
<th>

•

</th>  
<th>

Not relevant

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

2\. CTTC

</td>  
<td>

•

</td>  
<td>

Not relevant

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

3\. TUE

</td>  
<td>

•

</td>  
<td>

Not relevant

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

4\. VTT

</td>  
<td>

•

</td>  
<td>

Not relevant

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

5\. VERT

</td>  
<td>

•

</td>  
<td>

Not relevant

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

6\. VLC

</td>  
<td>

•

</td>  
<td>

Not relevant

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

7\. OPSYS

</td>  
<td>

•

</td>  
<td>

Not relevant

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

8\. EFP

</td>  
<td>

•

</td>  
<td>

Not relevant

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

9\. SMO

</td>  
<td>

•

</td>  
<td>

Not relevant

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

10\. TID

</td>  
<td>

•

</td>  
<td>

Not relevant

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

11\. EPIC

</td>  
<td>

•

</td>  
<td>

Not relevant

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

12\. NICT

</td>  
<td>

•

</td>  
<td>

Not relevant

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

13\. ETRI

</td>  
<td>

•

</td>  
<td>

Not relevant

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