_**_Keywords_ ** _

Keywords must be provided when uploading the dataset in 4TU.Centre for
Research Data.

#  __Metadata_ _

The platforms with overviews of metadata schemas that are typically
recommended by funders (e.g, _Research Data Alliance_ , _Digital Curation
Centre_ and _Datacite_ ) do not provide schemes that are suitable for use in
this project. Therefore, to make the data interchangeable between the project
partners and future users of the data, we will develop our own schematic
overview of metadata that will be collected and described.

As stated above, the discovery metadata are governed by the Datacite metadata
schema of 4TU.Centre for research Data.

##  2.2 Making data openly accessible

Relevant data that substantiate findings in peer‐reviewed scholarly
publications produced by the ONEFLOW project will be made available open
access (and as a default, without embargo) via the data repository 4TU.Centre
for Research Data. Data in 4TU.Centre for Research Data are archived/preserved
for the long term with a minimum of 15 years.

#  __Metadata/Documentation/Provenance_ _

As part of the dataset deposited in 4TU.Centre for Research Data, a data
(provenance) guide will be deposited with data specific information
(parameters and/or variables used, column headings, codes/symbols used, etc.)
and with information on the provenance of the data. When software is needed to
reuse the data, the code will also be deposited together with the data itself.

#  __Access restrictions_ _

The project will generate research data in a wide range of levels of detail
from simulation and lab results to demonstrator validation. Most data
associated with results that may have potential for commercial or industrial
protection cannot be made available open access in general due to intellectual
property protection restrictions. Concerning the other and expected major
part, relevant data necessary for the verification of results published in
scientific journals can be made accessible on a case by case basis. The
decision concerning the publication of data will be made by the Management
Board, as the decisionmaking body of the consortium. Research data and general
documentation of public interest such as those underlying scientific
publications will be made accessible via the ONE‐FLOW website and data
repositories, such as 4TU.Centre for Research Data (see above).

_Data storage/archiving at project level_

The ONE‐FLOW Surfdrive site serves to exchange all general information and
documents like MB and GA meeting minutes, WP related documents, Grant
Agreement and Consortium Agreement, deliverables, publications, etc. This
platform shall also facilitate the exchange of research data between the
ONE‐FLOW partners. Relevant data (i.e., results to validate results in
scientific publications) will be stored on Surfdrive during the research phase
and will then be archived/published in 4TU.Centre of Research Data.

The team room for information and document exchange of the ONE‐FLOW project is
accessible for all partners, ONE‐FLOW staff members and Finance members via
the domain www.surfdrive.surf.nl. All Dutch university members have been added
after the standard log‐in procedure. All non‐Dutch university members and the
EC Officer have received the required login information including their
password per email on February 20th, 2017.

The user welcome screen features the following at a glance information: (i)
financial documents; (ii) meetings; (iii) official ONE‐FLOW documents; (iv)
presentations; and (v) work packages. The EC officers can view all documents.
The financial staff members only have access to the financial document and can
(i) read and change documents. The administrator can (i) incorporate, edit,
delete partners, (ii) incorporate, edit, delete and disable users, (iii)
incorporate, edit, delete work packages, tasks, and sub‐tasks, and (iv)
incorporate deliverables.

The work package leader in addition can create deliverable versions and
receives a reminder with increasing frequency three weeks in advance from the
date the respective deliverable is due. The reminder allows direct access to
the respective deliverable/document.

##  2.3 Making data interoperable

Since our data for dissemination will largely be made available via 4TU.Centre
for Research Data, interoperability of the data will be effectuated by the
repository’s policy. For data deposited in 4TU.Centre for Research Data we
will try to adhere as much as possible to their preferred _data/file_
_formats_ .

##  2.4 Reuse of data (user licenses)

Datasets deposited in 4TU.Centre for Research Data allow users to choose from
a menu of usage licenses (mainly Creative Commons and ODB licenses). We will
decide upon deposition of datasets which license appears most suitable. Data
will become available for re‐use immediately after publication in 4TU.Centre
for Research Data. Typically there will be no embargo period for the data.

4TU.Centre for Research Data archives data for a minimum of 15 years. Data
from the ONE‐FLOW project are provided in a format that is recommended by
4TU.Centre for Research Data for long term preservation and re‐use. 4TU.Centre
for Research Data has received a Data Seal of Approval which guarantees that
the research data deposited here will continue to be able to be found and
shared in the future.

#  3 Allocation of Resources

__3.1 Costs and value_ _

There are not additional data management costs foreseen that require
additional/separate budgeting.

Storage/archiving facilities for data during the research project are
available as in‐house facilities at the universities/institutes. Costs for
these facilities are typically borne by the departments.

Long‐term archiving/publication in 4TU.Centre for Research Data is in
principle subject to costs that would need to be budgeted, but TU/e
researchers can deposit datasets <100 GB in the repository at no cost. Since
we expect to produce a total amount of data smaller than 100 GB, no costs need
to be covered.

It is impossible to predict the future value of the data that will be
deposited, for example because there are no datasets yet (to our knowledge)
that allow us to benchmark the potential value against existing datasets.
“Immaterial benefits” of publishing the data in a data repository are
addressed under Section 1 (Data Utility).

__3.2 Responsibilities_ _

Lead for this task is TU/e (Van Hest, formerly Hessel), and co‐lead with TU
Graz (Gruber‐Woelfler) and MIC (Tekautz). Yet, all partners are involved in
providing support and input to complete the DMP.

The ownership of data is regulated by the Consortium Agreement. The data owner
will primarily store its data on its own servers following its internal data
management procedures. Most partners have a dedicated Data Protection Officer
(DPO) and some partners have a Research Data Management team (RDM team).

#  4 Data Security

At all institutions data security is governed by the ICT departments. Data
security policies are typically at the institutional level (occasionally
supported by departmental support policies/practices).

#  5\. Ethical aspects

ONE‐FLOW does not handle personal data except for actors appearing in shoots
and pictures, in which case the partners follow the standard procedure of
getting authorization from the actors to show and distribute the videos and
images to the public.

#  6 Other (i.e, national/funder/sectorial/departmental for data management)

As of yet, there are to our knowledge no national policies on research data
management. However, the TU/e’s leading principles for data management are
outlined in the national _Code of Scientific_ _Conduct_ and the university’s
own _TU/e Code of Scientific Conduct_ . We have used these principles as a
supporting guide for organizing our RDM.

#  Appendix 1: Detailed overview of data types and formats

The most common data types to be generated, collected and used in ONE‐FLOW are
listed below per work package. The data range from typical data used in
reaction chemistry, supramolecular chemistry/functional materials, reactor
engineering and process/sustainability modelling and design. Information
related to each type of data and its concrete expressions is given. Most
relevant is here the file format, the total file size expected, and the
expected data‐access status after the project.

##  A1.1 Work Package 1 ‐ Data Inventory

Work Package 1 deals with supramolecular chemistry/functional materials. Four
partners (color‐coded) filled in (see Table 4). The total data size will
likely approach about 15 GB. The partners, however, have different data needs
announced ranging from MBs to GBs. The sharing of data has been classified in
four categories: open access, open‐embargo, limited share and share only
(explanation of the terms in the legend of Table A1). A discussion on the next
GA and possible by a telecon will aim at unifying the decision path to sharing
data.

**Table A1** _Overview of expected data types and further information,
including the sharing policy, in WP 1._ _Clarification of the terms in the
last column: Open = data can be made public open access without embargo;
Open‐embargo = data can be made public open access after an embargo period;
Share only = data cannot be made public and are only shared between (some)
project members; access to data is controlled; Limited Share = data cannot be
made public and cannot be shared between all project members; access to data
is restricted._

##  A 1.2 2

Work 2 deals with reaction chemistry for cascades and their transfer into
micro‐flow. Four partners (color‐coded) filled in (see Table 5). The total
data size will likely be in the order of 10‐15 GB. The partners, however, have
different needs announced from MB to GB. That might be unified by unifying the
data considered. The sharing of data is majorly open access and frequently
open‐embargo; here and there chosen is also limited share and share only. A
discussion on the next GA and possible by a telecon can aim at unifying the
decision path to sharing data.

**Table A2** _Overview of expected data types and further information,
including the sharing policy, in WP 2._ **A1.3 3**

Work 3 deals with process engineering to achieve fully compatible process
ingredients, thereby eliminating the need for compartmentation and separation.
Three partners (color‐coded) filled in (see Table 6). The total data size will
likely be in the order of 10‐15 GB. The partners, however, have different
needs announced from MB to GB. That might be unified by unifying the data
considered. The sharing of data switches between open access and limited share
/ share only. A discussion on the next GA and possible by a telecon can aim at
unifying the decision path to sharing data.

**Table A3** _Overview of expected data types and further information,
including the sharing policy, in WP 3._ **A1.4 4**

Work 4 deals with the digitalization of the new factory approach. Four
partners (color‐coded) filled in (see Table 7). The total data size will
likely be in the order of 10‐15 GB. The partners, however, have different
needs announced from KB to GB. That might be unified by unifying the data
considered. The sharing of data is from open access to open‐embargo to limited
share and share only. A discussion on the next GA and possible by a telecon
can aim at unifying the decision path to sharing data.

**Table A4** _Overview of expected data types and further information,
including the sharing policy, in WP 4._

##  A1.5 5

Work Package 5 deals with reactor engineering and process/sustainability
modelling and design Three partners (color‐coded) filled in (see Table 8). The
total data size will likely be in the order of 1‐2 GB. The partners have
similar needs announced. The sharing of data is for a large part share only,
which relates to the fact that here a platform technology is developed by a
SME, aiming at commercialization. The academic partners have chosen open
access. A discussion on the next GA and possible by a telecon can aim at
unifying the decision path to sharing data.

**Table A5** _Overview of expected data types and further information,
including the sharing policy, in WP 5._