#  Executive Summary

WASP is a research project aims to bring changes in flexible and wearable
electronics by developing new printing technology for the definition of
electronic devices and circuits on paper. The main goals of the projects are:

  1. To demonstrate electronic functionalities and emerging electronic applications enabled by nanomaterials on paper. 

  

  2. To demonstrate a sustainable technology for low-cost and flexible electronics. 

  

  3. To demonstrate a wearable paper-based technology, including sensing and communication functionalities for health care applications. 

  

  4. To demonstrate multi-scale modeling of paper based devices and complete design tool chain for printed electronis circuits and systems. 

  

  

During the development of the project, WASP will generate data from the
experimental and theoretical research activities. In this sense, and as a
project participating in the Open Research Data Pilot (ORDP) in Horizon 2020,
WASP will make its research data findable, accessible, interoperable and
reusable (FAIR).

The present document corresponds to the deliverable D1.6 “Data Management
Plan” of the WASP project and was produced as part of the WP1 “Management and
Dissemination”. It contains information about the main elements of the Data
Management policy that will be used by the Consortium with regard to the
project research data. It will include information about the production and
management of the research data along the project and the conditions and
aspects related to them. This is the first version of the DMP document. It
will be systematically reviewed and more details and description of the data
management procedures implemented by the WASP project will be included.

This deliverable will include the analysis of the most relevant aspects of the
data management policy. The document is divided into seven sections,
corresponding to the highlighted points of the Data Management Plan (DMP)
scheme: a) a general introduction describing the framework of the DMP; b) Data
Summary; c) FAIR data; d) Allocation of resources; e) Data security; f)
Ethical aspects and g) Other issues. Every section will include information
about the research data generated/collected, standards that will be used,
preservation of the data and the datasets will be shared for verification or
reuse.

#  Introduction

The deliverable D1.6 – Data Management Plan (DMP) of the WASP project provides
the strategy for managing data generated and collected during the project. It
consists on a document that will include information about how the WASP
research data obtained will be handle during and after the project, so it will
be reviewed and updated as the project evolves. The DMP include that data
handling, the types and format of the data generated and collected, the
methodologies applied and how the data will be shared and preserved.

The use of a DMP is required for all projects participating in the Open
Research Data Pilot. The document has been prepared taken into account the
template of the “Guidelines on Data Management in Horizon 2020” (
_https://ec.europa.eu/research/participants/data/ref/h2020/grants_manual/hi/oa_pilot/h2020-hi-
oadata-mgt_en.pdf_ ). The purpose of the DMP is to provide an analysis of the
main elements of data management policy. In the particular case of the WASP
project, the expected types of research datasets that will be collected or
generated along the project lie in the following categories: i)
Materials/devices modelling and circuit design; ii) Materials and device
fabrication and characterization; iii) System integration and demonstration;
iv) Process scalability, susteintability and exploitation.

From the mentioned categories, WASP project will generate several datasets,
including experimental measurements data, codes developed in different
programming languages, data coming from the atomistic simulations and
scientific articles. The data will be processed and analysed and they will be
preserved using appropriated naming rules and metadata schemes. This
information will be then organized in a DMP, considering open science
resources that are interoperable and trusted.

This document is the first version of the DMP, delivered in Month 6. It
includes an overview of the datasets to be produced by the project, and the
specific conditions related with it. The document will be updated in regular
intervals, including more details about the procedures implemented within the
WASP project.

_**Figure 1: Research data life-cycle** _

#  Data Summary  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Data collection/generation purpose, based on the project objectives.**

</td>  
<td>

The generation and collection of data has several purposes, in particular the
reproducibility of the performed results (either experimental and
theoretical), the dissemination (through articles), as well as the training of
researchers (either PhDs or post-docs), who will benefit from a detailed
description of the method/results obtained within the project.

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

**Data types and formats generated/ collected**

</td>  
<td>

In the WASP project several datasets will be generated, that can be classified
and identify schematically as follow:

**Dataset1** : Materials formulation for solution processing deposition
techniques

**Dataset2** : Development of a procedure to planarize/functionalize the paper
substrates

**Dataset3** : Sensing components

**Dataset4** : Energy generation and storage

**Dataset5** : Transponder design

**Dataset6** : Device models

At each dataset will be assigned a specific name/number. Inside these
datasets, the formats for the data generated/collected will correspond to:

  1. Raw data in ASCII format (.txt, .xls, .xlsx) 

  

  2. Open-source codes developed in different programming languages (Fortran, C and python) 

  

  3. Text based documents related with the description of the methodologies implemented in the project and publication in scientific journals, in (.doc, .tex, .pdf). 

  

  4. Illustrations, graphics and presentations (.png, .jpg, .tiff, .eps, .ppt, .pptx, .pdf). 

  

  

Further information about changes or inclusion of additional datasets during
the progress of the project will be included in the subsequent versions of the
DMP.

If specialized software is used then information about free readers will be
provided.

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

**Origin of the data**

</td>  
<td>

Based on the nature of the data generated, the origin of the data is related
with two principal sources: from the simulations activity, coming especially
from ab initio and atomistic simulations and the data obtained from the
experimental measurements of the devices. Moreover, another origin is the
development of open-source codes, that allow a complete transparency of the
obtained results.

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

**Size of the data**

</td>  
<td>

The size of the files varies depending on the data generated. From the
simulation activity we will get raw data in ASCII format of the order of
tens/hundreds of Gigabyte coming especially from ab initio and atomistic
simulations. From the experimental measurements, the amount of data will be
reduced, expecting a collection of data

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

</th>  
<th>

of the order of hundreds of Megabytes at most. With respect to the documents
size, it is expected files of the order of Megabytes.

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

**Re-use of existing data**

</td>  
<td>

Some database will be used, for instance 2D Materials database (
_https://cmr.fysik.dtu.dk/c2db/c2db.html_ ) to get information about
computational simulations parameters to be used to model the devices.
Moreover, the DFT pseudopotentials included in Quantum

Espresso package ( _https://www.quantum-_

_espresso.org/pseudopotentials_ ) will be used in order to describe the
interaction among the atoms in the atomistic simulations.

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

**Data utility**

</td>  
<td>

A repository of the generated data and implemented methodologies will be
fundamental for the training of new researchers in the field and also to those
joining the research group, so to reduce the learning curve and to allow a
faster integration within the WASP project activity. The data obtained from
experimental measurements and simulations can be used by theoretical groups as
input for theoretical modelling or as a reference for future comparison and
for the reproducibility of published results. The data will be also important
for the private sector, for commercial applications and for other research
groups working in the field.

The data will be suitable for use by other research groups working on the
following topics: nanomaterials, flexible electronics, sensors, multi-scale
modelling.

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

#  FAIR Data

3.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Data discoverable with metadata, identifiable and locatable by means of a
standard identification mechanism (e.g.**

**DOI)**

</td>  
<td>

WASP has chosen ZENODO platform ( _http://zenodo.org_ ) as repository data
archive. It is based on facilities and management FAIR data principles, on GIT
version control system and the Digital Object Identifier (DOI) system. ZENODO
is part of OpenAIRE collaboration and allows researchers to locate data and
publications, and assigning a persistent identifier and data citations in
order to link to them. The guidelines provided by ZENODO will be used by WASP
to ensure the right format of data uploaded to comply with FAIR principles.

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

**Naming conventions**

</td>  
<td>

The research data, documents and other product obtained in the WASP project
will be identified, collected and structured by using a name convention,
consisting of project and dataset name and an identification number related
with the dataset. Partners will be informed about the specific information and
metadata parameters that will support FAIR data management.

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

**Re-use through keywords provided**

</td>  
<td>

Keywords will be provided and updated with the project advancement.

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

**Version numbers used**

</td>  
<td>

Individual file names will contain version numbers that will be incremented at
each version.

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

**Metadata**

</td>  
<td>

Metadata is a descriptive information that help other researchers to find the
data in an online repository. Detailed metadata will give to the other
researchers the information to determine whether the dataset is important and
useful for its own research. The metadata created for all of the project’s
datasets will fulfil the respository’s (Zenodo) requirement for a minimum set
of metadata.

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

3.2 Making data openly accesible  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Data openly available and data shared under restrictions.**

</td>  
<td>

The generated data from the research activity (simulations and experimental
measurements, codes, etc) will be included in repositories chosen for the
project (ZENODO platform) and it will be made openly available unless there is
a specific reason not to publish it. With respect the multi-scale simulations,
it will be availabile the website of open-source code NanoTCAD ViDES (an open-
source simulation framework), which is representing a benchmark for two-
dimensional materials based devices _http://vides.nanotcad.com_ , exploiting
ViDES as simulations tool, as well as the specific website of the WASP project

( _https://www.wasp-project.eu_ ).

The beneficiaries must give each other access (under reasonable conditions) to
background needed for exploiting their own results.

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

**Accessibility of the data (e.g.**

**deposition in a repository)**

</td>  
<td>

About the datasets, they will be transferred to the ZENODO, repository,
through open access to data files and metadata and use and reuse of data
permitted. Additional data storage will be ensured by individual partner
institution’s data repositories. Data will also included in HPC resources of
University of Pisa, and made publicly available, in order to allow
availability, well beyond the timespan of the project.

For what concerns the published articles, and in particular regarding those
published in journals which do not offer the possibility to the reader to
download freely, we will upload in public repositories as Arxiv.org the final
version of the draft of the article, as well as in the publication section of
the WASP website, where we will also attach the tarball of the raw data
included in the published figures.

Within the timespan of the project, we will consider the possibility of
including the generated codes in repositories (as for example github or
sourceforge).

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

**Methods or software to access the data**

</td>  
<td>

The data deposited on ZENODO will be accessible to the public without
restrictions. The access to the data will be through standard available
softwares. In the case specific software tools will be developed, a text
document including the information about such software and how to use it will
be provided.

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

**Relevant software (open source code)**

</td>  
<td>

Most of the softwares needed inside the project are available. In the
particular case of specific software developed in the project, the source will
be deposited in the repository. In particular, the link to the open source
softwares used to carry out the modelling and simulations (Quantum Espresso
and related codes therein for atomistic simulations and NanoTCAD Vides for
nanoscale devices simulation) will be included.

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

**Data, metadata, documentation and code repositories**

</td>  
<td>

WASP project has chosen ZENODO platform ( _http://zenodo.org_ ) as repository
data archive. It is based on facilities and management FAIR data principles.
ZENODO is part of OpenAIRE collaboration. The guidelines provided by ZENODO
will be used by WASP to ensure the right format of data is uploaded to comply
with FAIR principles.

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

**Access under restriction on use**

</td>  
<td>

There are no restrictions on the use of the published data, but users will be
required to acknowledge the Consortium and the source of the data in any
resulting publications.

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

**Data access committee**

</td>  
<td>

There won’t be need of data access committee.

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

**Conditions for access**

</td>  
<td>

Zenodo provides well described conditions for access.

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

**Identity of the users accesing the data**

</td>  
<td>

Zenodo does not need any especial permissions or registration in order to
access to the repository files. In order to upload the data, users are
required to register.

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

3.3 Making data interoperable  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Interoperability of the data produced, data exchange and re-use between
researchers, institutions, organisations, countries, etc.**

</td>  
<td>

The generated and shared data will consist on simple raw data (ASCII files in
multicolumn structures). These data can be opened by any user with a simple
text editor. It is possible also to release the data directly embedded in the
file exploited to generate the figures of the articles. The programs used to
get and visualise data are open source (for example, Xmgrace or Python).

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

**Data, metadata, vocabularies, standards or methodologies for
interoperability**

</td>  
<td>

Vocabularies will be used in metadata fields in order to support consistent,
accurate and quick indexing and retrieval of relevant data. Keywords will be
used for indexing and subject headings of the data and metadata. Vocabularies
and keywords will be the standards used by OpenAIRE and will be updated along
the project execution, in order to increase the interopaerability of the
project’s data and metadata.

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

**Inter-disciplinary interoperability by standard vocabularies for data
types**

</td>  
<td>

Standard vocabularies will be used for all datasets in order to ensure inter-
disciplinary interoperability and re-use. All datasets will use the same
standard vocabularies for data and metadata capture/creation.

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

**Mappings to ontologies if unavoidable uncommon or specific ontologies or
vocabularies**

</td>  
<td>

The compability of our project specific ontologies and vocabularies will be
guaranteed through appropriate mapping to more commonly used onrtologies.

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

3.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**License for the re-use**

</td>  
<td>

The data will be openly available under CC0 Creative Commons license. All open
content is openly accessible through open

APIs. Metadata is exported via OAI-PMH and can be harvested.

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

**Availability of the data for the re-use. Application of eventual embargo.**

</td>  
<td>

Data will be fully available in the repositories (both data and codes), except
in those cases we believe that a disclosure could be detrimental for the
competitive advantage gained with respect to other groups or if we decide to
secure the intellectual property with patents. If needed, datasets could be
deposited under embargo status and the repository will restrict access to the
data until the end of the embargo period, becoming available automatically and
the end of such period.

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

**Third parties use of the data produced. Restrictions on the re-use of
data.**

</td>  
<td>

The data produced and/or used along the project will be deposited on a public
repository (in our case ZENODO) and the access to it will be unlimited by
third parties.

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

**Duration of the re-usable data**

</td>  
<td>

There won’t be a limiting time for the re-usability from a thirdparty of the
data/info.

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

**Description of the data quality assurance**

</td>  
<td>

Repetion and comparation of the measurements, adherence to standards for data
recording, the use of specific vocabularies and terminology, characterisation
of the measurement set-ups and validation of the data collected will assure
the data quality.

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

Allocation of resources  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Costs of data FAIR**

</td>  
<td>

The repository services offered by ZENODO are free of charge and enable peers
to share and preserve research data in several sizes and formats: datasets,
images, presentations, publications and softwares.

  * Data archiving at ZENODO: free of charge, including the DOI assigned to each dataset. 

  

  * Copyright licensing with Creative Commons: free of charge • Cost of the name domain: 12 EUR/yr 

  

The eventual costs have been kept to a minimum by making only relevant data
FAIR.

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

**How will these be covered?**

</td>  
<td>

Costs related to open access to research data are eligible as part of the
Horizon 2020 grant (if compliant with the Grant Agreement conditions).
Resources for long term preservation, associated costs and potential value, as
well as how data will be kept beyond the project and how long, will be
discussed by the whole consortium during General Assembly (GA) meetings.

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

**Data management responsible**

</td>  
<td>

The PI and the project manager will lead the coordination of the updates to
the data management plan. Project manager will be responsible for organising
data backup and storage, data archiving and for depositing the data within the
repository (ZENODO).

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

**Resourses for long term preservation, costs, value, availability of the
data.**

</td>  
<td>

The value of the preservation will be determined during the progress of the
project. The associated costs for dataset preparation for archiving will be
covered by the project itself. Long-term preservation will be provided and
associated costs covered by a selected disciplinary repository.

There are no costs associated with the long-term preservation of the data.

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

Data security  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Data security provisions, data security, data storage and transfer of
sensitive data.**

</td>  
<td>

In order to ensure the security of the data, some actions will be taken, for
instance: store data in at least two separate locations, lable files in
systematic and structured way in order to keep the coherence of the final
dataset. Deposition in the Zenodo public repository will provide additional
security as it has multiple replicas in a distributed file system which is
backed up on a nightly basis.

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

**Storage of the data**

</td>  
<td>

The data will be safely stored in the ZENODO open access repository. CERN is
working towards ISO certification of the organisational end technical
infrastructure which ZENODO relies on for long-term preservation. Every
partner will be responsible of the data produced and will ensure that the data
will be stored safely and securely and in agreement with the EU data
protection laws. At the end of the project the repository chosen to store the
dataset will have the responsibility of the data recovery and secure storage.

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

Ethical aspects  
  
<table>  
<tr>  
<th>

</th>  
<th>

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

**Ethical or legal issues on data sharing**

</td>  
<td>

WASP partners involved in the project will follow the EU and national
standards regarding ethics and data management. They must comply with the
ethical principles and confidentiality (according with the Article 34 of the
Grant Agreement). WASP partners must retain any data, documents or other
material as confidential during the implementation for the project.

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

**Consent for data sharing and long term preservation.**

</td>  
<td>

Research data which contains personal data will just be disseminated for the
purpose for which it was specified by the consortium. Moreover, the data
generated and shared have to be documented and approved by the consortium to
guarantee highest standards of data protection.

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

Other issues  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

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

**Use of**

**departmental management**

</td>  
<td>

**national/funder/sectorial/ procedures for data**

</td>  
<td>

Data management will be compliant with the research data policy of H2020
Horizon and European laws.

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