#  1\. INTRODUCTION

This document describes the initial **Data Management Plan** (DMP), as
Deliverable 8.4 on Month 6, customized for the VIPRISCAR project, funded by
the BBI-JU (The Bio-Based Industries Joint Undertaking) under the Grant
Agreement (GA) No. 790440.

The purpose of this DMP is to ensure the data generated and collected in the
VIPRISCAR project will follow the **FAIR** data management policy, meaning
making data findable, accessible, interoperable, and reusable. According to
the guidelines provided by EU Horizon 2020 programmes (European Comission,
2018), following information will be included in this DMP:

Methods to handle the research data during and after the end of project

Descriptions of the datasets that will be collected, processed, and/or
generated, such as data type, format, volume, source, etc.

Methodologies and standards that will be adopted for the data management

Level of accessibility/confidentiality of the data

Methods to curate and preserve the data during and after the end of the
project

Nevertheless, some important remarks are to be noticed. The encouragement to
conduct the DMP is to serve as a tool to assist the project having good data
management practice. In addition, according to article 29.3 in the GA, the
VIPRISCAR project is not applicable for open access to research data, meaning
the research data collected and/or generated in the VIPRISCAR project does not
have to be submitted to open access. Hence, the rules to apply in this case
would be in accordance with the IPR strategy and exploitation plan. Research
data dissemination shall not hinder the ability of the partners to file for a
patent. More details will be provided in the first version of exploitation
plan as deliverable D8.7 due month 6.

#  2\. DATA SUMMARY

##  2.1 Purpose of Data Generation and Collection

The purpose of data generation and collection in the VIPRISCAR project is to
achieve the objectives of the project: Improve the manufacturing process of
isosorbide bis(methyl carbonate) (IBMC) from the current technology readiness
level (TRL) 3 to 5 and provide proofof-principle of the major target IBMC
applications of coating, adhesive, and medical catheters.

##  2.2 Data Generation and Collection

The majority of the datasets will be generated from work package (WP) 2 to WP7
from the experiments throughout the project lifetime. Descriptions of the
datasets are categorized into both qualitative and quantitative aspects (as
shown in Table 1). There are total 21 datasets being identified at current
stage. The information has been collected via questionnaires distributed to
each partner and may be updated in future versions of the DMP (D8.5, due M24;
D8.6, due M36).

####  TABLE 1 DATASET INFORMATION TEMPLATE  
  
<table>  
<tr>  
<th>

**Work Package**

</th>  
<th>

Which WP and deliverable are this dataset related to

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

**Dataset Name**

</td>  
<td>

The name of the dataset should be easily to search and find

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

**Dataset Description**

</td>  
<td>

Brief description of the dataset

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

**Responsible partners**

</td>  
<td>

The lead partners responsible for the dataset generation/collection

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

**Purpose**

</td>  
<td>

The purpose of the data collection/generation and its relation to the
objectives of the project

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

**Type**

</td>  
<td>

Types of data could be report, paper, interview, expert or organization
contact details, video, audio, presentation, or note

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

**Format**

</td>  
<td>

Data formats could be XLSX, DOC, PDF, PPT, JPEG, OPJ, TIFF

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

**Volume**

</td>  
<td>

The size of the dataset (units: GB/MB) and the number of files

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

**Source**

</td>  
<td>

The origin of the data

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

**IPR Owner**

</td>  
<td>

Which project participant(s) own the intellectual property right (IPR)

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

**Re-use existing Data**

</td>  
<td>

Identification if any existing data being reused and how they are used

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

**Beneficiary**

</td>  
<td>

To whom the data may be useful

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

**DOI (if known)**

</td>  
<td>

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

**Keywords**

</td>  
<td>

The keywords associated with the dataset to make it easier to search and find

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

**Version number**

</td>  
<td>

To keep track of changes to the dataset

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

####  TABLE 2 DATASETS INFORMATION FOR WP1  
  
<table>  
<tr>  
<th>

**Work Package 1**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP1-9, all deliverables

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

**Dataset Name**

</td>  
<td>

Deliverables from work package one to nine

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

**Dataset**

**Description**

</td>  
<td>

The dataset includes all the deliverable reports from work package one to nine
required in the GA

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

**Responsible partners**

</td>  
<td>

TECNALIA and all the lead partners for each deliverable

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

**Purpose**

</td>  
<td>

To ensure the project implementation and document the results in proper manner

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

**Type**

</td>  
<td>

Reports

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: Approx. 40-50

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

**Source**

</td>  
<td>

Partners contribution

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

**IPR Owner**

</td>  
<td>

Involved partners who write the report

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

VIPRISCAR consortium and public if the deliverables are openly accessible

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

**Keywords**

</td>  
<td>

Deliverable

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Deposit location**

</td>  
<td>

Openly accessible data will be deposited on the project website. Confidential
report will be deposited in the project intranet.

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

**TABLE 3 DATASETS INFORMATION FOR WP2**  
  
<table>  
<tr>  
<th>

**Work Package 2**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 2 , Deliverable D2.1 and D2.2

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

**Dataset Name**

</td>  
<td>

WP2_IBMC process development and validation at lab scale

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about conditions of reactions carried
about in TECNALIA to IBMC process development. A complete characterization of
products will be also reported.

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To bring B4P and Exergy enough data for upscaling and techno-economic analyses
of the IBMC process, respectively

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

**Type**

</td>  
<td>

Conditions of reaction

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: To be defined

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

**Source**

</td>  
<td>

Lab experimentation in TECNALIA

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

**IPR Owner**

</td>  
<td>

TECNALIA

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

**Re-use existing Data**

</td>  
<td>

Yes ☒ No ☐

They are data obtained before VIPRISCAR application and used for filing the
patents granted through 2018. The will be used as starting point for reaction
improvement in WP2.

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

**Beneficiary**

</td>  
<td>

B4P, Exergy

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

**Keywords**

</td>  
<td>

IBMC

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 2 , Deliverable D2.3 Process simulation and preliminary up scaling report

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

**Dataset Name**

</td>  
<td>

Heat and mass balance; process flow diagram; equipment list

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

**Dataset**

**Description**

</td>  
<td>

  1. Heat and mass balance: a document (excel) contains all stream information, including flowrate, temperature, pressure, composition, and physical properties 

  

  2. Process flow diagram: a diagram shows all the unit operations in the integrated plant, and the main pipe connections; 

  

  3. Equipment list: list of equipment used in the process and the essential equipment information 

  

  

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

**Responsible partners**

</td>  
<td>

EXERGY

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

**Purpose**

</td>  
<td>

To complete the deliverable in WP2

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

**Type**

</td>  
<td>

Quantitative data, diagram, list

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: at least 4

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

**Source**

</td>  
<td>

Simulation software, information from partners

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

**IPR Owner**

</td>  
<td>

EXERGY

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All technical consortiums

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

**Keywords**

</td>  
<td>

Simulation

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**TABLE 4 DATASETS INFORMATION FOR WP3**  
  
<table>  
<tr>  
<th>

**Work Package 3**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 3 , Deliverable D3.3 Plant up-scaling simulation to industrial scale

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

**Dataset Name**

</td>  
<td>

Heat and mass balance; process flow diagram; equipment list; equipment sizing

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

**Dataset**

**Description**

</td>  
<td>

  1. Heat and mass balance: a document (excel) contains all stream information, including flowrate, temperature, pressure, composition, and physical properties. 

  

  2. Process flow diagram: a diagram shows all the unit operations in the integrated plant, and the main pipe connections. 

  

  3. Equipment list: list of equipment used in the process and the essential equipment information. 

  

  4. Equipment sizing: sizing calculations of the scaled-up equipment 

  

  

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

**Responsible partners**

</td>  
<td>

EXERGY

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

**Purpose**

</td>  
<td>

To complete the deliverable in WP2

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

**Type**

</td>  
<td>

Quantitative data, diagram, list

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: at least 5

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

**Source**

</td>  
<td>

Simulation software, manual calculations, information from partners

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

**IPR Owner**

</td>  
<td>

EXERGY

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All technical consortiums

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

**Keywords**

</td>  
<td>

Simulation

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**TABLE 5 DATASETS INFORMATION FOR WP4**  
  
<table>  
<tr>  
<th>

**Work Package 4**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 4 , Deliverable D4.1, D4.2, D4.3

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

**Dataset Name**

</td>  
<td>

Vipriscar_WP4

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

**Dataset**

**Description**

</td>  
<td>

The dataset is constituted of a hard copy series of notebooks with progressive
number, that reference files containing relevant data. It contains synthetic
protocols, formulations and testing conditions/test results.

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

**Responsible partners**

</td>  
<td>

AEP

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

**Purpose**

</td>  
<td>

The dataset will be used for internal purposes. It will contain design and
synthesis data of new materials from IBMC to be used in coatings and
process/performance data of the obtained coatings.

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

**Type**

</td>  
<td>

Description of lab procedures for synthesis and testing, test results,
chemical structures and properties of the materials

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

Other ☒ Hard copy laboratory notebook(s)

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

**Volume**

</td>  
<td>

Expected Size: 100 GB☐ MB☒ Number of files: 10-20

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

**Source**

</td>  
<td>

The data is generated internally, through design and lab testing

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

**IPR Owner**

</td>  
<td>

AEP POLYMERS

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

**Re-use existing Data**

</td>  
<td>

Yes ☒ No ☐

We will use QC and analytic data provided by TECNALIA regarding the received
IMBC samples (From TECNALIA) as a basis for our processes.

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

**Beneficiary**

</td>  
<td>

AEP, GAIKER, TECNALIA, JOWAT, LEITAT

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

**Keywords**

</td>  
<td>

WP4, coatings, PUD, NIPU

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 4 , Deliverable D4.1

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

**Dataset Name**

</td>  
<td>

IBMC hydroxyl-polycarbonates and waterborne polyurethane dispersions

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

**Dataset**

**Description**

</td>  
<td>

Procedures for synthesizing IBMC derived hydroxyl-oligocarbonates and
properties of obtained products. Procedures for producing PUDs and properties
of obtained dispersions.

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

**Responsible partners**

</td>  
<td>

GAIKER

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

**Purpose**

</td>  
<td>

To define the fabrication procedure to obtain IBMC derived prepolymers and to
develop PUDs with IBMC for further preparation of coatings.

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

**Type**

</td>  
<td>

Report with associated characterization results.

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☐ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐ Other ☐ Click or tap here to
enter text.

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

**Volume**

</td>  
<td>

Expected Size: 10 GB☐ MB☒ Number of files: < 10

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

**Source**

</td>  
<td>

Experimental work

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

**IPR Owner**

</td>  
<td>

GAIKER

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

**Re-use existing Data**

</td>  
<td>

Yes ☒No ☐

As a reference for define experimental conditions and characterization
methods, and as comparative data to define chemical structures and properties.

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

**Beneficiary**

</td>  
<td>

Chemical industry; Manufacturers of coatings/paints/adhesives/sealants;
Scientific researchers

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

**Keywords**

</td>  
<td>

Isosorbide bis(Methyl Carbonate), bio-based molecule, polycarbonate diol, bio-
based PUDs, bio-based polyurethane

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

**Version number**

</td>  
<td>

Yes ☒No ☐

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

**Work Package**

</td>  
<td>

WP 4 , Deliverable D4.2

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

**Dataset Name**

</td>  
<td>

IBMC based coatings

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

**Dataset**

**Description**

</td>  
<td>

Procedures for producing IBMC based coatings, characterization of properties
and comparison to reference examples.

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

**Responsible partners**

</td>  
<td>

AEP POLYMERS

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

**Purpose**

</td>  
<td>

To develop coatings from IBMC based PUDs

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

**Type**

</td>  
<td>

Report with associated characterization results.

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☐ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐ Other ☐ Click or tap here to
enter text.

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

**Volume**

</td>  
<td>

Expected Size: 10 GB☐ MB☒ Number of files: < 10

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

**Source**

</td>  
<td>

Experimental work

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

**IPR Owner**

</td>  
<td>

GAIKER

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

**Re-use existing Data**

</td>  
<td>

Yes ☒ No ☐

As a reference for define experimental conditions and characterization
methods, and as comparative data to define chemical structures and properties.

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

**Beneficiary**

</td>  
<td>

Manufacturers of coatings/paints/adhesives/sealants; Scientific researchers

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

**Keywords**

</td>  
<td>

Isosorbide bis(Methyl Carbonate), bio-based PUDs, bio-based polyurethane, bio-
coating

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

**Version number**

</td>  
<td>

Yes ☒No ☐

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

**TABLE 6 DATASETS INFORMATION FOR WP5**  
  
<table>  
<tr>  
<th>

**Work Package 5**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 5 , Deliverable D5.1

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

**Dataset Name**

</td>  
<td>

WP5.1 _Adhesives application proof of principle

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about the selection of the raw
materials and the definition of adhesives applications

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To collect enough data to develop NIPUs (adhesives) from IBMC

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

**Type**

</td>  
<td>

Materials and applications specifications

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: To be defined

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

**Source**

</td>  
<td>

Literature review

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

**IPR Owner**

</td>  
<td>

TECNALIA

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

TECNALIA, JOWAT

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

**Keywords**

</td>  
<td>

NIPUs, adhesives

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 5 , Deliverable D5.3-D5.6

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

**Dataset Name**

</td>  
<td>

WP5.2 NIPUs-based adhesives

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about conditions of reactions carried
about in TECNALIA to NIPUs-based adhesive process development. A complete
characterization of products will be also reported.

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To collect proper conditions to developed NIPUs-based adhesives

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

**Type**

</td>  
<td>

Conditions of reaction and characterization

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: To be defined

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

**Source**

</td>  
<td>

Lab experimentation in TECNALIA

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

**IPR Owner**

</td>  
<td>

TECNALIA

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

JOWAT

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

**Keywords**

</td>  
<td>

NIPUs-based adhesives

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**TABLE 7 DATASETS INFORMATION FOR WP6**  
  
<table>  
<tr>  
<th>

**Work Package 6**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 6 , Deliverable D6.1

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

**Dataset Name**

</td>  
<td>

WP6- Synthesis of thermoplastic IBMC-based NIPUs

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about experiments related to
synthesis, biofunctionalization and characterization of IBMC based NIPUs.

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

**Responsible partners**

</td>  
<td>

TECNALIA, CIKAUTXO

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

**Purpose**

</td>  
<td>

To bring to CIKAUTXO a bio functionalized IBMC-based NIPU to process it into a
catheter

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

**Type**

</td>  
<td>

Experiments conditions and results

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: To be defined

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

**Source**

</td>  
<td>

Lab experimentation in TECNALIA

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

**IPR Owner**

</td>  
<td>

TECNALIA

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

CIKAUTXO

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

**Keywords**

</td>  
<td>

Synthesis, biofunctionalization, toxicity, IBMC, antimicrobial, antithrombotic

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 6 , Deliverable D6.3

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

**Dataset Name**

</td>  
<td>

WP6_Biocompatibility and bio functionality of the final prototype

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about the results of biocompatibility
and bio functionality evaluations of the final catheter prototype.

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To demonstrate the usefulness in catheter production of IBMC-based NIPUs

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

**Type**

</td>  
<td>

Results of experiments

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: To Be Defined

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

**Source**

</td>  
<td>

Lab experimentation carried out by TECNALIA

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

**IPR Owner**

</td>  
<td>

TECNALIA

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

CIKAUTXO

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

**Keywords**

</td>  
<td>

Biocompatibility bio functionality biocidal antithrombotic

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**TABLE 8 DATASETS INFORMATION FOR WP7**  
  
<table>  
<tr>  
<th>

**Work Package 7**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 7 , Deliverable D7.7

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

**Dataset Name**

</td>  
<td>

WP7_ Health and safety study

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

**Dataset**

**Description**

</td>  
<td>

The dataset will contain data collection about the results of a toxicity study
on IBMC and most promising final product. Results of the bibliographic search
on Regulatory issues and standards related to Environment and health and
safety issues concerning the IBMC production will also be included.

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

**Responsible partners**

</td>  
<td>

TECNALIA, VERTECH

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

**Purpose**

</td>  
<td>

To identify and evaluate health and safety issues related to VIPRISCAR project
technologies and products to prevent, correct and control potential risks, if
necessary.

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

**Type**

</td>  
<td>

Results of experiments and results of bibliographic data

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: TBD

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

**Source**

</td>  
<td>

Lab experimentation carried out by TECNALIA and bibliographic research carried
out by Vertech with the support of TECNALIA. Other partners´ contributions.

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

**IPR Owner**

</td>  
<td>

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

**Re-use existing Data**

</td>  
<td>

Yes ☒ No ☐

Bibliographic data to know the state of the art in all the mentioned issues

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

**Beneficiary**

</td>  
<td>

To all the consortium

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

**Keywords**

</td>  
<td>

Toxicity, REACH, health, safety, regulation, standard, IBMC

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 7 , Deliverable D7.2

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

**Dataset Name**

</td>  
<td>

LCC data collection

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

**Dataset**

**Description**

</th>  
<th>

All partners will have to fill the data collection template with the CAPEX
(investment for the machinery, external processes, infrastructure), OPEX
(specific cost of waste material, process energy, maintenance, labor force,
insurances, taxes etc.) and the incomes of the system (the specific cost of
the main product and by-products of the process).

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

**Responsible partners**

</td>  
<td>

All partners

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

**Purpose**

</td>  
<td>

The data collection will determine cost-effectiveness of the proposed
technologies compared to currently used techniques.

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

**Type**

</td>  
<td>

Quantitative data

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☐ PDF ☐ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: <100 GB☐ MB☒ Number of files: <15

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

**Source**

</td>  
<td>

The data comes from the different demosites. The partners will fill the data
collection table and send it back to Vertech Group.

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

**IPR Owner**

</td>  
<td>

Technology owners.

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All involved partners.

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

**Keywords**

</td>  
<td>

LCC, economic feasibility, economic validation

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 7 , Deliverable 7.3

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

**Dataset Name**

</td>  
<td>

LCA data collection

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

**Dataset**

**Description**

</td>  
<td>

Input and output of all partners processes

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

**Responsible partners**

</td>  
<td>

All partners will have to generate the information and Vertech will collect
it.

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

**Purpose**

</td>  
<td>

The data will be used to comprehensively characterize environmental impacts
through the whole life cycle thanks to an LCA.

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

**Type**

</td>  
<td>

Quantitative data

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☐ PDF ☐ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

Other ☒ CSV

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

**Volume**

</td>  
<td>

Expected Size: <100 GB☐ MB☒ Number of files: <15

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

**Source**

</td>  
<td>

The data comes from the different demosites. The partners will fill the data
collection table and send it back to Vertech Group.

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

**IPR Owner**

</td>  
<td>

Technology owners.

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All involved partners.

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

**Keywords**

</td>  
<td>

LCA, environmental impacts, sustainability analysis.

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 7 , Deliverable D7.1 Technical evaluation of VIPRISCAR concepts

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

**Dataset Name**

</td>  
<td>

Heat and mass balance

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

**Dataset**

**Description**

</td>  
<td>

This document (excel) contains all stream information, including flowrate,
temperature, pressure, composition, and physical properties

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

**Responsible partners**

</td>  
<td>

EXERGY

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

**Purpose**

</td>  
<td>

To complete the deliverable in WP7

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

**Type**

</td>  
<td>

Quantitative data

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: at least 5

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

**Source**

</td>  
<td>

Simulation software, manual calculations, information from partners

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

**IPR Owner**

</td>  
<td>

EXERGY

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All technical consortiums

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

**Keywords**

</td>  
<td>

Simulation

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**TABLE 9 DATASETS INFORMATION FOR WP8**  
  
<table>  
<tr>  
<th>

**Work Package 8**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 8 , Deliverable D8.11-D8.14

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

**Dataset Name**

</td>  
<td>

Dissemination and communication plan

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

**Dataset**

**Description**

</td>  
<td>

The plan will contain data related to dissemination and communication issues

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To manage the issues related to dissemination and communication

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

**Type**

</td>  
<td>

Dissemination material

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: at least 10

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

**Source**

</td>  
<td>

Partners contribution

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

**IPR Owner**

</td>  
<td>

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All audience

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

**Keywords**

</td>  
<td>

Publications, dissemination, communication

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Deposit location**

</td>  
<td>

Through the VIPRISCAR website

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

**Work Package**

</td>  
<td>

WP 8 , Deliverable D8.15

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

**Dataset Name**

</td>  
<td>

Website

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

**Dataset**

**Description**

</td>  
<td>

Content of the website

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To disseminate the VIPRISCAR project

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

**Type**

</td>  
<td>

Dissemination material

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

**Format**

</td>  
<td>

XLSX ☒ DOC ☒ PDF ☒ PPT ☒ JPEG ☒ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒

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

**Source**

</td>  
<td>

Partners contribution

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

**IPR Owner**

</td>  
<td>

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

All audience

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

**Keywords**

</td>  
<td>

Website, dissemination

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 8 , Deliverable 8.4

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

**Dataset Name**

</td>  
<td>

WP8_D8.4_Data Management Plan Questionnaires From the Consortium

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

**Dataset**

**Description**

</td>  
<td>

This dataset includes all the questionnaires answered by each partner in the
consortium about the datasets that will be generated within the project
lifetime and how they will be managed during and after the end of project

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

**Responsible partners**

</th>  
<th>

All partners are responsible to fill out the questionnaire that is designed,
distributed, and collected by Vertech

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

**Purpose**

</td>  
<td>

To conduct the Data management plan tailor-made for VIPRISCAR project

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

**Type**

</td>  
<td>

Questionnaires

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☒ PDF ☐ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: >10 GB☐ MB☒ Number of files: Approx. 30

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

**Source**

</td>  
<td>

Project partners

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

**IPR Owner**

</td>  
<td>

Partners who fill out the questionnaire

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

Whole consortium and related stakeholders

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

**Keywords**

</td>  
<td>

Data management plan, FAIR, findability, accessibility, interoperability,
reusability, data security

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 8 , Deliverable 8.7

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

**Dataset Name**

</td>  
<td>

WP8_D8.7_Exploitation Plan Questionnaires From the Consortium

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

**Dataset**

**Description**

</td>  
<td>

This dataset includes all the questionnaires answered by each partner in the
consortium for the information about the KERs, IPR strategy and protection,
market analysis, and exploitation

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

**Responsible partners**

</td>  
<td>

All partners are responsible to fill out the questionnaire that is designed,
distributed, and collected by Vertech

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

**Purpose**

</td>  
<td>

To conduct the Exploitation plan tailor-made for VIPRISCAR project

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

**Type**

</td>  
<td>

Questionnaires

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☒ PDF ☐ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: >10 GB☐ MB☒ Number of files: Approx. 30

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

**Source**

</td>  
<td>

Project partners

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

**IPR Owner**

</td>  
<td>

Partners who fill out the questionnaire

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

Partners involved for each commercial KERs

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

**Keywords**

</td>  
<td>

Exploitable results, exploitation route, intellectual property

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

**Work Package**

</td>  
<td>

WP 8 , Deliverable D8.5

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

**Dataset Name**

</td>  
<td>

VIPRISCAR Articles

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

**Dataset**

**Description**

</td>  
<td>

Articles in technical journals.

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To increase the visibility of the project and disseminate outstanding results
related to IBMC based PUDs and coatings

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

**Type**

</td>  
<td>

Technical paper.

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☐ PDF ☒PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: 5 GB☐ MB☒ Number of files: 2

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

**Source**

</td>  
<td>

Experimental work and reporting

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

**IPR Owner**

</td>  
<td>

GAIKER

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

**Re-use existing Data**

</td>  
<td>

Yes ☒ No ☐

As a reference for define experimental conditions and characterization
methods, and as comparative data to define chemical structures and properties.

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

**Beneficiary**

</td>  
<td>

Chemical industry; Manufacturers of coatings/paints/adhesives/sealants;
Scientific researchers

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

**Keywords**

</td>  
<td>

Isosorbide bis(Methyl Carbonate), bio-based PUDs, bio-based polyurethanes,
biocoatings

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

**Version number**

</td>  
<td>

Yes ☐ No ☒

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

**TABLE 10 DATASETS INFORMATION FOR WP9**  
  
<table>  
<tr>  
<th>

**Work Package 9**

</th>  
<th>

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

**Work Package**

</td>  
<td>

WP 9 , Deliverable D9.1 and D9.2

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

**Dataset Name**

</td>  
<td>

Ethics requirements

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

**Dataset**

**Description**

</td>  
<td>

The dataset will collect the ethics requirements that the project must comply

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

**Responsible partners**

</td>  
<td>

TECNALIA

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

**Purpose**

</td>  
<td>

To comply with the ethics requirements

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

**Type**

</td>  
<td>

authorization of compliance with ethical requirements

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

**Format**

</td>  
<td>

XLSX ☐ DOC ☒ PDF ☒ PPT ☐ JPEG ☐ OPJ ☐ TIFF ☐

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

**Volume**

</td>  
<td>

Expected Size: GB☐ MB☒ Number of files: 2

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

**Source**

</td>  
<td>

Partners contribution

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

**IPR Owner**

</td>  
<td>

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

**Re-use existing Data**

</td>  
<td>

Yes ☐ No ☒

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

**Beneficiary**

</td>  
<td>

BBI-JU

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

**Keywords**

</td>  
<td>

Ethics

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

**Version number**

</td>  
<td>

Yes ☒ No ☐

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

#  3\. FAIR DATA

The VIPRISCAR project will dedicate to make the datasets collected or
generated in the project comply to European Commission’s FAIR data policy –
“Findable, Accessible, Interoperable, Reusable”.

##  3.1 Findability

For published articles, a Digital Object Identifier (DOI) as a unique and
permanent code to identify will be assigned by the corresponding journal. In
other case, the identification mechanism will depend on the repository that
the VIPRISCAR project adopts if any.

Common naming conventions have been set out in D1.1 Quality Assurance Plan
prepared by project participant TECNALIA for all files stored on the project
archive.

Naming conventions:

VIPRISCAR_<DX.Y/WPX/TX.Y>_<Title>_ <Version>_<Date>.filetype

Where:

<DX.Y> Deliverable number, e.g. “D2.3” for Deliverable 2.3.

<WPX> Work Package identifier, e.g. for example “WP1” or ”WP2”.

<TX.Y> Task number, e.g. “T3.1” for Task 3.1.

<Title> Short description of document.

<Version> Version identifier, e.g. ‘v1’.

<Date> Date in “yyyymmdd” format.

Example:

VIPIRSCAR_D1.1_Quality Assurance Plan (I)_v1_20180208.docx.

Search keywords of each dataset are provided by the project participants who
generate the datasets to optimize the possibilities for reuse and are noted in
the dataset information table as shown in section 2.2 above.

Other different standards to identify the datasets used by each partner are
listed below if any:

####  TABLE 11 STANDARDS OF DATASET IDENTIFICATION BY EACH PARTNER  
  
<table>  
<tr>  
<th>

**Partner Name**

</th>  
<th>

**Standards**

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

JOWAT

</td>  
<td>

Analysis-ID, Date, person, batch number

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

##  3.2 Accessibility

According to Article 29.1 in the GA, each beneficiary must disseminate the
project results as soon as possible by disclosing them to the public through
appropriate means, unless the legitimate interests would be infringed.
Currently, the VIPRISCAR project considers using Microsoft’s SharePoint as an
intranet/repository to deposit project related data and documentation. Key
features include easiness to manage/share/collaborate the file anywhere, wide-
range of preview function for more than 270 common file types, support for
team communication and engagement, and automation of repetitive tasks
(Microsoft, 2018).
2016)

For scientific publications, each partner must take measures to ensure open
access, meaning providing online access for any user without additional
charge, to all peer-reviewed scientific publication relating to its results in
accordance with the Article 29.2 in the GA. Two main publishing approaches to
consider are Green and Gold open access (Newcastle University, 2018)(Springer,
2018).

**Green open access:** Also referred as self-archiving. Authors deposit the
manuscripts into their institutional repository or a subject repository with
immediate or delayed open access, making the publications freely accessible
for all users. The deposited version of the publication (usually will be the
final version for publication), terms and condition (e.g. embargo period) for
the open access depend on the funder or publisher.

**Gold open access:** Final version of the manuscripts are freely accessible
for all users via publisher website permanently right after the publication
without any embargo period.

Authors owns the copyright without most of the permission restrictions
compared to green open access.

Research data of VIPRISCAR project, as mentioned in previous section, is not
bound to be submitted to open access. As one of the results of the VIPRISCAR
project, research data will be owned by the project participants who generate
it, according to article 26 in the GA. The project coordinator together with
the responsible partners will determine how the data collected and/or
generated in the project will be made openly available. Relevant information
to provide in future versions of the DMP (D8.5, due M24; D8.6, due M36) may
include but not limit to following information: The channels to deposit the
data (e.g. repository, website, scientific journals), methods or software
required to access the data if any, restriction on use if any, embargo period
if any, the procedures to provide access, etc. Certain datasets may not be
shared or would be share under restrictions considering ethical,
confidentiality (in Article 36), security-related (in Article 37), privacy-
related (in Article 39), IPR and commercial/industrial exploitation potential
(in Article 27). In this case, reasons for data accessibility constrains will
be explained.

Below is the list of the datasets that have been identified as confidential in
order to protect the IP of the results and ensure the success of the
exploitation after the end of the projects. **TABLE 12 CONFIDENTIAL DATASETS**  
  
<table>  
<tr>  
<th>

**WP**

</th>  
<th>

**Datasets**

</th>  
<th>

**Accessibility within the**

**Consortium**

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

WP1-9

</td>  
<td>

All deliverable reports except D1.1-D1.4 Quality

Assurance Plan, D1.5-D1.8 Project Management Plan, D7.8-D7.10 European and
local legal and non-legal limitations, barriers and standards for VIPRISCAR
products, D8.4-D8.6 Data Management Plan, D8.11D8.14 Dissemination and
communication plan, D8.15 Project Website

</td>  
<td>

Confidential, only for members of the consortium (including the

Commission Services)

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

WP2-9

</td>  
<td>

All data generated within the project

</td>  
<td>

Accessible to the partners within the project

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

WP4

</td>  
<td>

VIPRISCAR_WP4

</td>  
<td>

The consortium will be given access to select portions of the dataset, mainly
concerning test results.

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

Important remark for any partner intending to disseminate its results, it is
obligatory to provide notice with sufficient information on the dissemination
contents to other partners at least **45** days in advance to the
dissemination. Other partners, if not agree, may object within **30** days
after receiving the notification and should provide proper justification to
explain the reason why its legitimate interests would be significantly
infringed. In this case, appropriate steps to solve the conflicts should take
place; otherwise, the dissemination would not be able to further proceed.

##  3.3 Interoperability

The VIPRISCAR project aims to collect and document the data in a standardized
way to ensure the datasets would be easy to understand, reuse and interoperate
among different parties who are interested in utilizing them. Standard
technical terminology will also be used to facilitate inter-disciplinary
interoperability.

##  3.4 Reusability

Data reusability means the easiness to re-use the data for further researches
or other purposes. In VIPRISCAR project, the datasets have high reusability in
that normally no special methods or software is required to re-use the data.
The time of reusability for those research data which will be made available
to re-use is not yet defined.

The procedures to ensure the highest data quality and validity include
internal reviews as well as peer reviews if the articles or documents would be
published through scientific journals. Other specific procedures adopted by
partners are listed below:

####  TABLE 13 SPECIFIC QUALITY CONTROL PROCEDURES ADOPTED BY PARTNERS  
  
<table>  
<tr>  
<th>

**Partner Name**

</th>  
<th>

**Standards**

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

JOWAT

</td>  
<td>

Good Laboratory Practices

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

AEP

</td>  
<td>

International standards (ASTM, ISO, UL94 and others) and written internal
procedures and testing methods

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

Additionally, quality control of data at different stages from data
collection, data entry or digitalization, and data checking is crucial in the
VIPRISCAR project in that many research experiments would be conducted
throughout the lifetime of the project. Following measures referred to the
Good Practice Note of Research Data Management (CGIAR, 2017) are offered as
references for the consortium partners to follow in order to ensure data
quality.

Stage 1: Data collection

Calibrate the instruments to ensure the measurement accuracy

Take multiple measurements, observations, or samples to ensure the data
reliability

Double confirm the truth of the record with adequate experts in the relevant
domains

Unify standardized methods and standard operating procedures Stage 2: Data
entry or Digitalization:

Set out validation rules in data entry software

Use controlled vocabularies, anthologies, code lists and choice lists to
minimize the occurrence probability of human mistakes

Follow the naming conventions for the variables including names, dates,
versions to avoid confusion

Stage 3: Data checking

Double check the coding accuracy and out-of-range values

Check data completeness, appropriate naming conventions used

Choose random samples to verify the consistency with original data

Conduct statistical analysis to detect if any errors or abnormal values exist

#  4\. DATA SECURITY

Currently, the VIPRISCAR project considers using Microsoft’s SharePoint as the
intranet/repository to manage, share, and collaborate for the data and
documents related to the project. Three levels of configurations to balance
between the security protection and the ease of collaboration are recommended
based on the confidentiality level of the data and documents from baseline,
sensitive, to highly confidential (as shown in Figure 2) (Microsoft, 2018).
More details will be provided in the future versions of DMP if SharePoint is
chosen.

Meanwhile, most of the consortium partners have their own provisions in place
for data security within organizations (as listed in the Table 14 below).

###  TABLE 14 DATA SECURITY PROVISIONS WITHIN PARTNER'S ORGANIZATION  
  
<table>  
<tr>  
<th>

**Partner Name**

</th>  
<th>

**Data Security Provisions**

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

TECNALIA

</td>  
<td>

Access controls: Every worker in TECNALIA has his/her own password-protected
user account to access the systems. The password must satisfy complexity
requirements and shall be changed every 90 days. The access to networks
folders and programs where information is stored/managed depends on user
permissions which are decided by factors such as division, role in the
company, role in the project, etc. The permissions are managed by
administrators only and must be asked by authorized persons through authorized
channels.

Backup: TECNALIA has two-level backup. The first level is the system “previous
versions” service that allows a user to recover a copy of the work (5 copies a
day, two weeks period) by his/her own. Moreover, every day TECNALIA makes full
backup of the working information. There are daily, weekly, monthly and yearly
copies. The recover from this backup requires a formal procedure.

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

</th>  
<th>

Transfer of data: To transfer the information we can use platforms that
require security protocols, such as OneDrive, SharePoint, or the “consigna” of
TECNALIA, and we can use information protection tools such as Veracrypt and
others.

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

JOWAT

</td>  
<td>

National regulations

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

CIKAUTXO

</td>  
<td>

To be determined

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

B4P

</td>  
<td>

Regular server back-up of all data

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

AEP

</td>  
<td>

The data is stored in a firewalled and password-accessible server and in
online password protected server(s).

Daily back-up on a stand-alone mirrored hard-drive.

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

VERTECH

</td>  
<td>

Using internal company server

Documents are automatically saved on the OneDrive. Historical copies could be
access on the server

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

EXERGY

</td>  
<td>

Hardware (computers) purchased for performance, reliability and security. All
of them are equipped with windows defender and are automatedly updated and
password protected.

Password protected cloud-based central document storage is utilized for
project documents, plus 2-step authentication protection for administrators.

Automatic file retention and regular electronic backups.

Email retention that are protected by password.

Guidance on safeguards provided for employees in the handbook which all
employees are required to review.

Holding of and processing of all personal data in line with General Data
Protection Regulation (GDPR) requirements.

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

GAIKER

</td>  
<td>

On-Premise: from the earlier stages of the project until it is considered a
closed project, information access is granted only to the staff working
directly on it; there is just a live copy of information, and several others
in backup data; the backup data is encrypted and protected with random
passwords of more than 50 positions. The passwords are kept in security boxes,
with physical access controls in place.

Offsite copies: The access is restricted to the IT staff of the company, and
the information is encrypted, so if someone else accesses by accident or
intentionally to the information, it would be useless.

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

LEITAT

</td>  
<td>

Using internal server

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

#  5\. ETHICAL ASPECTS

The VIPRISCAR project partners are to comply with article 34 concerning ethics
and research integrity principles in the GA.

Ethical principles (including the highest standards of research integrity)
Applicable international, EU, and national law

In the VIPRISCAR project, no ethical or legal issues that can have an impact
on data sharing have been identified at current stage.

Important remark to be noticed that the EU GDPR regulation has been officially
enforced on 25 May 2018, aiming to protect and empower all EU citizens
personal data privacy as well as reshape the way organizations across the
region manage data and proceed towards data privacy.

The GDPR is organized around seven key principles (European Commission, 2016):

  * Lawfulness, fairness and transparency 

  

  * Purpose limitation 

  

  * Data minimization 

  

  * Accuracy 

  

  * Storage limitation 

  

  * Integrity and confidentiality (security) 

  

  * Accountability 

  

**Personal data** is information that relates to an identified or identifiable
individual (name, number, location, IP address…). Information which has had
identifiers removed or replaced in order to pseudonymize the data is still
personal data for the purposes of GDPR.

Hence, if any dataset that will be collected and/or generated in the VIPRISCAR
project may involve data privacy issue, responsible partner should take notice
of the following key changes in GDPR (GDPR.ORG, 2018)(European Commission,
2018) and ensure to be compliant with the regulations. Noteworthily, only the
relevant changes have been listed below. The consortium shall comply with but
not limit to those GDPR regulations if applicable.

**Conditions for consent** : The request for consent must be provided in an
intelligible and easily accessible form, along with the explanation of the
purpose for data processing attached to that consent. The language used is
required to be clear and plain instead of illegible terms or conditions full
of legalese.

**Increased territorial scope:** GRDP is applicable if at least one of the
following conditions is met.

The personal data processing concerns data subjects in the EU

Personal data controller or processor is located in the EU, regardless of the
exact location of processing taking place **Data subject rights:**

Breach notification: In case of any data breach that may “result in a risk for
the rights and freedoms of individual”, the breach notification must be
provided within 72 hours after becoming aware of a data breach.

Right to access: Data subjects are empowered to request confirmation with the
data controller that if personal data concerning them is being process, where
and for what purpose and shall receive an electronic copy of personal data
without additional cost.

Right to be forgotten: Data subjects have the right to demand the data
controller to erase their personal data, cease further dissemination, and half
third-parties processing it upon condition that the data is no longer
applicable for the original purpose for processing or the data subjects
withdraw their consents.

**Privacy by design** : Data controller shall include data protection into
consideration from the very beginning of designing of systems. Appropriate
measures shall be taken to protect the rights of data subjects, for instance
only data which is considered necessary for completion of the tasks should be
held and processed and only relevant personnel would be granted the access
rights for data processing.

Recommendations on the right to be informed:

Inform individuals about the collection and use of their personal data.

Provide individuals with information including: The purposes for processing
their personal data, the retention periods for that personal data, and who it
will be shared with. It is called the ‘privacy information’.

Provide privacy information to individuals at the time their personal data are
collected from them.

When you obtain personal data from a source other than the individual, you
need to provide the individual with privacy information in less than a month.
If you use data to communicate with the individual, you should provide privacy
information at the latest when the first communication takes place

When you collect personal data from the individual it relates to, you must
provide them with privacy information at the time you obtain their data. you
must tell people who you are giving their information to and give them an easy
solution to opt out.

The information you provide to people must be concise, transparent,
intelligible, easily accessible, and it must use clear and plain language.

It is often most effective to provide privacy information to people using a
combination of different techniques including layering, dashboards, and just-
in-time notices.

User testing is a good way to get feedback on how effective the delivery of
your privacy information is.

You must regularly review, and where necessary, update your privacy
information. You must bring any new uses of an individual’s personal data to
their attention before you start the processing.

The checklist (as shown in Table 15) suggests the information to provide when
collecting personal data either from individuals directly or from other
sources (ico., 2018).

###  TABLE 15 CHECKLIST OF INFORMATION TO PROVIDE WHEN COLLECTING PERSONAL
DATA  
  
<table>  
<tr>  
<th>

**What information do we need to provide?**

</th>  
<th>

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

The name and contact details of your organization

</td>  
<td>

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

The name and contact details of your representative

</td>  
<td>

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

The contact details of your data protection officer

</td>  
<td>

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

The purposes of the processing

</td>  
<td>

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

The lawful basis for the processing

</td>  
<td>

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

The legitimate interests for the processing

</td>  
<td>

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

The categories of personal data obtained

</td>  
<td>

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

The recipients or categories of recipients of the personal data

</td>  
<td>

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

The details of transfers of the personal data to any third countries or
international organizations

</td>  
<td>

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

The retention periods for the personal data

</td>  
<td>

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

The rights available to individuals in respect of the processing

</td>  
<td>

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

The right to withdraw consent

</td>  
<td>

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

The right to lodge a complaint with a supervisory authority

</td>  
<td>

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

The source of the personal data

</td>  
<td>

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

The details of whether individuals are under a statutory or contractual
obligation to provide the personal data

</td>  
<td>

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

The details of the existence of automated decision-making, including profiling

</td>  
<td>

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

#  6\. OTHER ISSUES

At current stage, most of the consortium partners including GAIKER, TECNALIA,
AEP, LEITAT, VERTECH have reported no obligation to comply with additional
specific national, funder, sectorial, departmental, or institutional data
management policies.

Certain partners have informed using other procedures for data management:

B4P: Funder regulation

JOWAT: Data management software

More information may be updated in the future versions of the DMP (D8.5, due
M24; D8.6, due M36) regarding the details of the specific policies followed by
those partners as well as other possible issues related to data management if
identified.

#  7\. ALLOCATION OF RESOURCES

According to the guidelines provided by EU Commission (European Comission,
2018), costs related to open access to research data in Horizon 2020 programme
are eligible for reimbursement during the project lifetime if the requirements
in article 6 and article 6 D.3 as well as other articles relevant for the cost
category chosen are met.

The planned budget dedicated to data management which is already foreseen in
the GA as well as additional information provided by each partner have been
gathered together in Table 16 below. This information might be completed or
evolve in the future versions of the DMP (D8.5, due M24; D8.6, due M36)
depending on the results of questionnaires collected from the consortium
partners.

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

**Partner Name**

</th>  
<th>

**Descriptions**

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

TECNALIA

</td>  
<td>

Open access articles (10k€)

Web page: web domain, picture, video, plugin… (2k€)

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

EXERGY

</td>  
<td>

Cost related to open access and IPR (5k€)

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

LEITAT

</td>  
<td>

Publication in Open Access (5k€)

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

As for long-term preservation of the datasets, different internal policies of
each partners are noted in Table 17 and will be updated in future versions of
the DMP (D8.5, due M24; D8.6, due M36) based on the information provided by
the consortium partners.

###  TABLE 17 DATA LONG-TERM PRESERVATION POLICIES  
  
<table>  
<tr>  
<th>

**Partner Name**

</th>  
<th>

**Planned Resources**

</th>  
<th>

**Decision Maker for Data Preservation**

</th>  
<th>

**Preservation Timeframe**

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

TECNALIA

</td>  
<td>

Yes

</td>  
<td>

Project Manager of VIPRISCAR

</td>  
<td>

10 years

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

JOWAT

</td>  
<td>

Yes

</td>  
<td>

Jowat

</td>  
<td>

According to national regulation

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

CIKAUTXO

</td>  
<td>

To be

Determined

</td>  
<td>

To be Determined

</td>  
<td>

To be Determined

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

B4P

</td>  
<td>

Yes

</td>  
<td>

Board of B4plastics

</td>  
<td>

At lest 3 years after project termination

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

AEP

</td>  
<td>

Yes

</td>  
<td>

Project Manager

</td>  
<td>

Indefinitely

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

VERTECH

</td>  
<td>

No

</td>  
<td>

</td>  
<td>

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

EXERGY

</td>  
<td>

Yes

</td>  
<td>

Project Manager and Head of department

</td>  
<td>

To be confirmed

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

GAIKER

</td>  
<td>

Yes

</td>  
<td>

**Internal policies.** Project information will be preserved in several
repositories. 1) On-Premise storage systems, as repositories for the
information. 2) On-Premise copy of data, as a first backup copy of info.

</td>  
<td>

**Internal policies.** Virtually forever. At least 2 copies of information
will be preserved forever, as the company exists.

**External repositories:**

Depending on the repository,

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

</td>  
<td>

</td>  
<td>

  3. Offsite copy of data (cloud providers, in Dublin and Frankfurt) as an external backup copy of data. 

  

  4. External searchable scientific information repositories. 

  

  

</td>  
<td>

for example, if zenodo is used, it will maintain the information as CERN
Laboratory exists (at the moment 20+ years guaranteed).

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

LEITAT

</td>  
<td>

No

</td>  
<td>

Principle investigator of VIPRISCAR project

</td>  
<td>

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

#  8\. EVOLUTION OF THE DATA MANAGEMENT PLAN THROUGHOUT THE PROJECT

This initial DMP will continuously evolve within the lifetime of the project
and future versions will be provided in Deliverable 8.5 (due M24) and
Deliverable 8.6 (due M36). New questionnaires will be circulated to the
consortium partners in order to update all the identification of new datasets,
changes of the already identified datasets or data management policy within
the consortium (e.g. new innovation potential, decision to file for a patent)
if necessary.