data, which can be made publically accessible, in order to protect the
industrial interests.

The Art.29.3 suggests that participants will have to provide information, via
the repository, about tools and instruments needed for the validation of
project outcomes, without to infringe industrial interests and Consortium
Agreement. Following these indications about data protection, this article
will be applied to only those tools and instruments that do not interfere with
the confidentiality and protection of industrial interest aspects.

_Will you re-use any existing data and how?_

No. OCEAN data are non-previously existing data and these will be generated
within the Project development by the partners.

_What is the origin of the data?_

The origin of the data derives from the experimentation made in the frame of
the project. According to Consortium Agreement and project politics to
preserve confidentiality, the Steering Committee has decided that can be
shared data which have been before specifically approved by the Exploitation
and Innovation Committee (EIC) of the Consortium, and after publication in
Open Access journals or after embargo period in other journal, when they do
not infringe journal politics or Consortium interests. The rules indicated in
the Consortium Agreement for dissemination (in particular section 8.4 –
Dissemination of the Results) should be respected. Project aspects which have
been instead specifically indicates as public, such as some deliverables, are
instead out of these restrictions and will be made available on the
repository.

For the first version of the project DMP, the analysis is based on the
following series of datasets (DSx) and related subsets (DSx/y), indicated
below.  
  
<table>  
<tr>  
<th>

_Ref_

</th>  
<th>

_Title_

</th>  
<th>

_Partner (*)_

</th>  
<th>

_Data Type_

</th>  
<th>

_WP or Task_

</th>  
<th>

_~Size & _

</th>  
<th>

_Access level_

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

DS0

</td>  
<td>

General Aspects on OCEAN

Project

</td>  
<td>

ERIC

</td>  
<td>

Public info for the project, open presentations at conferences and other
events, public

accessible Deliverables

</td>  
<td>

WP8

</td>  
<td>

500

MB

</td>  
<td>

Public

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

DS1

</td>  
<td>

CO  2  reduction Demo Cell

</td>  
<td>

AVT

</td>  
<td>

Design data for Demo cell and related components

</td>  
<td>

WP1

</td>  
<td>

1,5 GB

(total)

</td>  
<td>

Confidential

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

DS1/1

</td>  
<td>

Process design specifications and

design of Demo

cell

</td>  
<td>

AVT

</td>  
<td>

Design specifications and concept for the Demo Cell

</td>  
<td>

WP1

(T1.1.

T1.4))

</td>  
<td>

300

MB

</td>  
<td>

Confidential

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

DS1/2

</th>  
<th>

Catalysts for CO  2  reduction in

Demo Cell

</th>  
<th>

AVT

</th>  
<th>

Catalyst characteristics and performances

</th>  
<th>

WP1

(T1.2)

</th>  
<th>

300

MB

</th>  
<th>

Confidential

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

DS1/3

</td>  
<td>

Gas diffusion electrode

</td>  
<td>

GSKL

</td>  
<td>

Procedures for preparation of GDE

</td>  
<td>

WP1

(T1.3)

</td>  
<td>

100

MB

</td>  
<td>

Confidential

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

DS1/4

</td>  
<td>

Testing and validation of

Demo Cell

</td>  
<td>

RWE

</td>  
<td>

Data about process stability, efficiency and product quality

</td>  
<td>

WP1

(T1.6,

T1.7)

</td>  
<td>

800

MB

</td>  
<td>

Confidential

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

DS2

</td>  
<td>

Paired electrosynthesis

</td>  
<td>

GENS

</td>  
<td>

Anode and cathode characteristics, and direct heating technology

</td>  
<td>

WP2

</td>  
<td>

0,8 GB

(total)

</td>  
<td>

Confidential

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

DS2/1

</td>  
<td>

Anode catalyst development and scale-up

</td>  
<td>

AVT

</td>  
<td>

Anode catalyst characteristics and performances, scaleup procedures

</td>  
<td>

WP2

(T2.1,

T2.2)

</td>  
<td>

300

MB

</td>  
<td>

Confidential

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

DS2/2

</td>  
<td>

Direct electrode heating

</td>  
<td>

GENS

</td>  
<td>

Design data, and scale-up of direct electrode heating technology, prototype
features and performances

</td>  
<td>

WP2

(T2.3,

T2.4,

T2.5,

T2.6)

</td>  
<td>

500

MB

</td>  
<td>

Confidential

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

DS3

</td>  
<td>

Process for formate to oxalate

</td>  
<td>

HYS

</td>  
<td>

Design data and characteristics for a process for formate to oxalate
conversion

</td>  
<td>

WP3

</td>  
<td>

1,4 GB

(total)

</td>  
<td>

Confidential

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

DS3/1

</td>  
<td>

Process design and input data in batch conditions

</td>  
<td>

HYS/AVT

</td>  
<td>

Process design specifications and engineering, batch process tests

</td>  
<td>

WP3

(T3.1,

T3.2,

T3.3)

</td>  
<td>

600

MB

</td>  
<td>

Confidential

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

DS3/2

</td>  
<td>

Prototype design and manufacture, performances

</td>  
<td>

HYS/AVT

</td>  
<td>

Prototype manufacture data and testing, including with real feeds

</td>  
<td>

WP3

(T3.4,

T3.5,

T3.6)

</td>  
<td>

800

MB

</td>  
<td>

Confidential

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

DS4

</td>  
<td>

Electrochemical acidification

</td>  
<td>

AVT

</td>  
<td>

Multifunctional electrochemical salt splitting system data

</td>  
<td>

WP4

</td>  
<td>

2,0 GB

(total)

</td>  
<td>

Confidential

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

DS4/1

</td>  
<td>

Process design for acidification with membranes

</td>  
<td>

IIT

</td>  
<td>

Design data of bipolar membrane based modules and related specs

</td>  
<td>

WP4

(T4.1,

T4.2)

</td>  
<td>

400

MB

</td>  
<td>

Confidential

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

DS4/2

</td>  
<td>

Coupling with oxidative or reductive electrosynthesis

</td>  
<td>

IIT

</td>  
<td>

Data on electrocatalysts/ electrodes for the oxidative or reductive
electrosynthesis

</td>  
<td>

WP4

(T4.3,

T4.4)

</td>  
<td>

500

MB

</td>  
<td>

Confidential

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

DS4/3

</td>  
<td>

Unit design and control

</td>  
<td>

IIT

</td>  
<td>

Data on ESS system for controlling the process

</td>  
<td>

WP4

(T4.5)

</td>  
<td>

500

MB

</td>  
<td>

Confidential

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

DS4/4

</td>  
<td>

Prototype design and performances

</td>  
<td>

AVT

</td>  
<td>

Data on prototype design, manufacture and testing, including with real feeds

</td>  
<td>

WP4

(T4.6,

T4.7,

T4.8)

</td>  
<td>

600

MB

</td>  
<td>

Confidential

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

DS5

</td>  
<td>

Conversion of formate and oxalate to highvalue products

</td>  
<td>

ERIC

</td>  
<td>

Data on catalysts and reaction conditions for the conversion of formate and
oxalate to high-value products

</td>  
<td>

WP5

</td>  
<td>

2.4 GB

(total)

</td>  
<td>

Confidential

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

DS5/1

</td>  
<td>

Electrochemical hydrogenation of

oxalate

</td>  
<td>

ERIC

</td>  
<td>

Data on electrocatalysts and performances in the electrochemical hydrogenation
of oxalate, including with real feeds

</td>  
<td>

WP5

(T5.1, T5.2.

T5.3)

</td>  
<td>

800

MB

</td>  
<td>

Confidential

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

DS5/2

</td>  
<td>

Catalytic hydrogenation and

hydroformulation

</td>  
<td>

UVA

</td>  
<td>

Data on catalysts and performances in the hydrogenation and hydroformulation,
including with real feeds

</td>  
<td>

WP5

(T5.4. T5.5,

T5.6)

</td>  
<td>

800

MB

</td>  
<td>

Confidential

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

DS5/3

</td>  
<td>

Polymerization to new polyesters

</td>  
<td>

UVA

</td>  
<td>

Data on the assessment of polymer targets and polymerization processes for
glycolic acid polyesters and oxalate diester, including tests at larger scale

</td>  
<td>

WP5

(T5.7. T5.8,

T5.9)

</td>  
<td>

800

MB

</td>  
<td>

Confidential

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

DS6

</td>  
<td>

Process assessment

</td>  
<td>

IIT

</td>  
<td>

Data on process assessment, based on LCA analysis

</td>  
<td>

WP6

</td>  
<td>

1,2 GB

(total)

</td>  
<td>

Confidential

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

DS6/1

</td>  
<td>

Life cycle analysis

</td>  
<td>

IIT

</td>  
<td>

Data on life cycle analysis (LCA) modelling for the estimation of the
environmental footprint

</td>  
<td>

WP6

(6.1)

</td>  
<td>

700

MB

</td>  
<td>

Confidential

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

DS6/2

</td>  
<td>

Process assessment

</td>  
<td>

IIT

</td>  
<td>

Data on process assessment and quantification of environmental impact

</td>  
<td>

WP6

(6.2)

</td>  
<td>

500

MB

</td>  
<td>

Confidential

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

(*) responsible of Task or WP (  & ) up to this size, depends on which
specific data are planned to be sgared as indicated in the text.

The Consortium has reckoned that the commercial interests of the industrial
partners must be preserved and the protection of the competitiveness of the
European industry in this sector shall been ensured. Priority objective shall
be to avoid disadvantage on the market and the preservation of commercial
interest over Open dissemination. At this stage of the project, where results
are still under development, the Consortium has agreed to undertake a
conservative approach, thus classifying several datasets as Confidential
(either at Consortium or Beneficiary level). Access level of datasets will be
further discussed and revised along the project implementation, based on more
concrete exploitation analysis. For this reason, at the current stage access
level for data produced in the project are indicated as Confidential, but this
will be not excludes that specific subset of data, which upon approval of EIC,
are decided to be disseminated, will be put in a repository that will be
organized according to the structure indicated in the Table above, after the
eventual embargo period which may derive from the publication in some
journals. The dataset D0, referring to general aspects on OCEAN Project, i.e.
public info for the project, open presentations at conferences and other
events, public accessible Deliverables, etc., instead to not follow above
restrictions.

_What type of data are produced?_

With the increasing share of renewable electricity in the overall energy
production, there is a renewed interest in electrochemistry in industry as a
clean and carbon-neutral energy source to drive chemical reactions. Despite
electrochemistry and electrosynthesis being known for decades, application of
electrochemical synthesis in industry so far is limited. Therefore, both the
demonstration of electrochemical processes to proof the industrial and
economic feasibility, as well as the development of new advanced
electrochemical methodologies is needed to overcome current challenges and
create new applications for electrochemistry. The overall objectives of the
OCEAN project are to

  1. provide a proof of the economic and industrial feasibility of the electrochemical technology to convert carbon dioxide 

  

  2. develop and demonstrate innovative electrochemical technologies to overcome current challenges in electrochemistry 

  

  3. Integration of the electrochemical technologies into industrial operations 

  

  

As part of these objectives, OCEAN project thus aims to proof the industrial
and economic feasibility of the developed technologies, develop innovative
electrochemical methodologies and integrate into industrial operations, as
defined in the Description of the Work of the project. Therefore, most of the
data realized cannot be made publically available, without infringe the
industrial interests on the project, both in terms of known-how and
data/technologies which can be patented. Furthermore, a key element in the
project is an electrochemical process acquired by Avantium with relative IPs,
and which details are shared among the Consortium partners for the purpose of
the projects, but that cannot be diffused publically.

Based on these considerations, the purpose of the data collection/generation
and its relation to the objectives of the project have thus to be reconsidered
with respect to the Open access to research data politics, which thus should
be limited to only those data which, after internal approval by the
Exploitation and Innovation Committee (EIC) of the OCEAN project (the body
dedicated to analysis of these aspects), could be diffused

Different type of data will be generated within the project, depending on WPs.

  * In WP1 (CO  2  reduction Demo Cell) data generated will regard process design specifications (T1.1), characteristics of catalysts (T1.2), procedures for scale-up of gas diffusion electrode (T1.3), engineering and design of the Demo Cell (T1.4), manufacturing and assembling of the Demo Cell (T1.5), data on the testing, validation and demonstration of the Demo Cell (T1.5, T1.6). Data format are in the form of word or excel reports, and PFD and P&ID data. 

  

  * In WP2 (Paired electrosynthesis) data generated regard anode catalyst development and scale-up (T2.1, T2.2), process design specifications (T2.3), scale-up of direct electrode heating (T2.4), prototype manufacture, testing and demonstration (T2-4-2.8). 

  

  * In WP3 (Formate to oxalate) data generated regard process design specifications (T3.1), optimize batch process conditions (T3.2), engineer and design continuous process (T3.3), manufacturing and testing (T3.4-3.6). 

  

  * In WP4 (Electrochemical acidification) data generated regard conception of bipolar membrane based modules and related specs (T4.1), development of TRL5 module (T4.2), coupling with oxidative electrosynthesis (T4.3) and with reductive electrosynthesis (T4.4), unit design and control, manufacturing and testing (T4.5-T4.8). 

  

  * In WP5 (High-value products from formate and oxalate) data generated regard electrochemical hydrogenation of oxalate (screening, optimization, tests with real feed (T5.1-T5.3), catalytic hydrogenation and hydroformulation (screening, optimization, tests with real feed (T5.4-T5.6), polymerization (developing new polyesters, optimization, tests at large scale) (T5.7-T5.9). 

  

  * In WP6 (Life-Cycle Analysis) data generated regard life cycle analysis (T6.1), process assessment and quantification of environmental impact (T6.2). 

  

  * In WP7 (Business case and exploitation strategy) data generated regard market Analysis (T7.1), Business Case (T7.2). 

  

As emerges from this survey of data generated within the project

  1. none of these tasks will generate data using standard procedures which can be put in a standardized database, open within the Consortium or externally; all the raw data need to 

  

  

be processed and elaborated, because in the absence of the proper procedure of
data elaboration and specific expertise, they can generate misinterpretation,
which can be the bases also of patents infringements and other IPR issues. For
this reason, the Consortium has decided to make available in database only
data published in papers and related support information, but after specific
analysis that they cannot determine IPR issues. The data will be in an
exchangeable format such as word, excel, PFD, P&ID or other
graphical/vectorial data.

  2. all these data should be maintained confidential by Consortium, and specifically saved by beneficiaries who generated them, and shared only between the Consortium for the purpose of the project, if not decided otherwise by EIC. 

  

  

It should be also noted that the datasets indicated above are not
characterized by single or limited type of results, which can be stored in a
searchable database, or which may be used without specific or sometime
proprietary elaboration methodologies. The datasets do not have intrinsically
the characteristics of dataset interoperability, management and re-use. The
recommendations by OpenAIRE cannot be applied, as well as they do not
compliant with UK Data Archive.

The repository for the dataset will be made available through links in the
public part of the project web site.

_What is the expected size of the data?_

As indicated above, the total size of the data is up to about 9-10 GB, but
depends on the specific data which will be shared in the databases as
explained in the text. Better estimations will be made in a later stage of the
project.

_To whom might it be useful ('data utility')?_

At this stage of the project, as indicated above, data utility will be
strictly limited either at Consortium or Beneficiary level. The datasets are
functional to reach the objectives of the WPs and Tasks indicated, and the
overall project objectives. As indicated, specific subset of data in the
databases will be make public available, after EIC decision to allow
publication of specific data, and after eventual embargo period relative to
journals politics. The data will be relative to those published and related
supporting information, which should be specifically approved by EIC and
follow Consortium Agreement politics about dissemination of the results, as
well as the Dissemination Plan.

Within the constrains indicated above, data utility will be for all those
(researchers and other) that like to obtain further indications on the
published results by the project, as well as to find in a single place all the
published data. The dataset will allow third parties to be able to access,
mine, exploit, reproduce and disseminate the data, if they do not infringe
copyrights related to publications in journals. The access to data will help
to validate the results presented in scientific publications.

#  2 FAIR data

##  2\. 1. Making data findable, including provisions for metadata

_Are the data produced and/or used in the project discoverable with metadata,
identifiable and locatable by means of a standard identification mechanism
(e.g. persistent and unique identifiers such as Digital Object Identifiers)?_

The data will be available through links reported in the OCEAN web site, which
will refer to repositories open accessible. The data will refer to specific
publications and supporting info, and thus will be identified by the DOI of
the related publications, which will be used also as metadata.

_What naming conventions do you follow?_

As indicated above, we will use DOI of publication as naming convention.

_Will search keywords be provided that optimize possibilities for re-use?_

Search keywords will be a secondary level of DOI to allow a better
identification of the available data.

_Do you provide clear version numbers?_

The version number will refer to DOI of related publication.

_What metadata will be created? In case metadata standards do not exist in
your discipline, please outline what type of metadata will be created and
how._

The metadata will be related to DOI of publication and second level searchable
keywords.

###  2.2. Making data openly accessible

_Which data produced and/or used in the project will be made openly available
as the default? If certain datasets cannot be shared (or need to be shared
under restrictions), explain why, clearly separating legal and contractual
reasons from voluntary restrictions._

The data openly available as the default are those corresponding to D0 dataset
indicate in the Table above. For the other datasets, as indicated, only the
subset of data which have been specifically indicate by EIC as publishable,
will be make available, for confidentiality motivations.

_Note that in multi-beneficiary projects it is also possible for specific
beneficiaries to keep their data closed if relevant provisions are made in the
consortium agreement and are in line with the reasons for opting out._

Depending on the type of data, they can be keep for specific beneficiaries, in
agreement with consortium agreement indications.

_How will the data be made accessible (e.g. by deposition in a repository)?_

Data indicated as openly accessible will in repository for each dataset, which
link will be indicated in the public accessible part of the OCEAN web site.

_What methods or software tools are needed to access the data?_

The data will be in an exchangeable format such as word, excel, PFD, P&ID or
other graphical/vectorial data.

_Is documentation about the software needed to access the data included?_

The software needed will be common software identified by their extension.

_Is it possible to include the relevant software (e.g. in open source code)?_

No, because they will be not in open source code, but commercial software.

_Where will the data and associated metadata, documentation and code be
deposited? Preference should be given to certified repositories which support
open access where possible._

We prefer to use repositories by beneficiaries, to have a better control.

_Have you explored appropriate arrangements with the identified repository?_

It is in progress.

_If there are restrictions on use, how will access be provided?_

Access will be granted upon specific request, with personal data and
indications of the use.

_Is there a need for a data access committee?_

Access will be decided by EIC.

_Are there well described conditions for access (i.e. a machine readable
license)?_

Ye, conditions for access will be described.

_How will the identity of the person accessing the data be ascertained?_

It will be asked to have specific demonstration of who will access to the data
and motivations.

###  2.3. Making data interoperable

_Are the data produced in the project interoperable, that is allowing data
exchange and re-use between researchers, institutions, organisations,
countries, etc. (i.e. adhering to standards for formats, as much as possible
compliant with available (open) software applications, and in particular
facilitating re-combinations with different datasets from different origins)?_

The data, within restrictions indicate above, will allow project
interoperable, data exchange and re-use between researchers, institutions,
organisations, countries, etc. For their characteristics, however, there is no
available (open) software applications, and recombinations with different
datasets from different origins will be not possible.

_What data and metadata vocabularies, standards or methodologies will you
follow to make your data interoperable?_

We will use DOI and keywords, and use of commercially widely available
software, for data interoperability.

_Will you be using standard vocabularies for all data types present in your
data set, to allow inter-disciplinary interoperability?_

Yes, as indicated above. However, a variety of type of data, with different
characteristics, will be produced, which do not fit requirements for standard
vocabularies for all data types present in datasets

_In case it is unavoidable that you use uncommon or generate project specific
ontologies or vocabularies, will you provide mappings to more commonly used
ontologies?_

Yes, we will provide the necessary indications.

###  2.4. Increase data re-use (through clarifying licences)

_How will the data be licensed to permit the widest re-use possible?_

Data open will be only those specifically defined by EIC, and they will not
need specific license, expect for possible restrictions by copyrights
associated to journal politics.

_When will the data be made available for re-use? If an embargo is sought to
give time to publish or seek patents, specify why and how long this will
apply, bearing in mind that research data should be made available as soon as
possible._

Embargo politic will depend on the specific journals in which publication is
made. The scientific quality of the journal, the readership and type of
audience will be the elements for decision on where to published, rather than
open access. Most of the open access journal have an unacceptable low
scientific level; they are just made for business.

_Are the data produced and/or used in the project useable by third parties, in
particular after the end of the project? If the re-use of some data is
restricted, explain why._

Decisions on how to maintain repository after the end of the project is
postponed at a later stage of the project.

_How long is it intended that the data remains re-usable?_

It is planned for now that the data remain accessible for the time of the
project, because do not exist resources for maintenance after this period.
However, decisions on how to maintain repository after the end of the project
is postponed at a later stage of the project.

_Are data quality assurance processes described?_

Data quality assurance is guaranteed by making available data of publications
in peer reviewed journals.

##  3\. Allocation of resources

_What are the costs for making data FAIR in your project?_

No (costs).

_How will these be covered? Note that costs related to open access to research
data are eligible as part of the Horizon 2020 grant (if compliant with the
Grant Agreement conditions)._

Are not indicated costs for FAIR in the Grant Agreement and should be thus
identified a way on how to cover the costs.

_Who will be responsible for data management in your project?_

The project and scientific coordinators.

_Are the resources for long term preservation discussed (costs and potential
value, who decides and how what data will be kept and for how long)?_

No, they are not identified, and decision is postponed at a later stage of the
project.

##  4\. Data security

_What provisions are in place for data security (including data recovery as
well as secure storage and transfer of sensitive data)?_

It will be followed standard procedures for data security.

_Is the data safely stored in certified repositories for long term
preservation and curation?_

No, because they are no resources for now for certified repository. It will be
look if they can be identified.

##  5\. Ethical aspects

_Are there any ethical or legal issues that can have an impact on data
sharing? These can also be discussed in the context of the ethics review. If
relevant, include references to ethics deliverables and ethics chapter in the
Description of the Action (DoA)._

No

_Is informed consent for data sharing and long term preservation included in
questionnaires dealing with personal data?_

Yes. It will follow the GDPR rules of the EU.

##  6\. Other issues

_Do you make use of other national/funder/sectorial/departmental procedures
for data management? If yes, which ones?_

No.