#  INTRODUCTION

##  Motivation

The DTOceanPlus project participates in the Pilot on Open Research Data
launched by the European Commission (EC) along with the H2020 programme. This
pilot is part of the Open Access to Scientific Publications and Research Data
programme in H2020. The goal of the programme is to foster access to research
data generated in H2020 projects. The use of a Data Management Plan (DMP) is
required for all projects participating in the Open Research Data Pilot.

Open access is defined as the practice of providing on-line access to
scientific information that is free of charge to the reader and that is
reusable. In the context of research and innovation, scientific information
can refer to peer-reviewed scientific research articles or research data.

Research data refers to information, facts or numbers collected to be examined
and considered, and as a basis for reasoning, discussion, or calculation. In a
research context, examples of data include statistics, results of experiments,
measurements, observations resulting from fieldwork, survey results, interview
recordings and images. The focus is on research data that is available in
digital form.

As a user progresses through the stages of creating a design in DTOceanPlus,
they will require access to reference data to support decision-making.
Moreover, a database of long-standing reference data will collect all the
relevant information produced by the research and demonstration activities in
the project. Essentially, it will contain a catalogue of components, vessels,
ports and equipment, as well as the associated features for assessments of
designs such as performance, cost, reliability, environmental or social impact
ratings. Actually, user consultation responses [1] highlighted the need for
transparent access to this kind of data.

Additionally, the underlying data needed to validate the results presented in
scientific publications will be considered insofar possible for open access
publication [1] .

Nevertheless, data sharing in the open domain can be restricted as a
legitimate reason to protect results that can reasonably be expected to be
commercially or industrially exploited. In this sense, the Commission applies
the principle of 'as open as possible, as closed as necessary' and allow
partial opt out due to IPR concerns, privacy/data protection concerns or for
other legitimate reasons. Strategies to limit such restrictions could include
anonymising or aggregating data, agreeing on a limited embargo period or
publishing selected datasets.

##  Purpose of the Data Management Plan

The purpose of the DMP is to provide an analysis of the main elements of the
data management policy that will be used by the Consortium with regard to the
project research data.

The DMP covers the complete research data life cycle. It describes the types
of research data that will be generated or collected during the project, the
standards that will be used, how the research data will be preserved and what
parts of the datasets will be shared for verification or reuse. It also
reflects the current state of the Consortium agreements on data management and
must be consistent with exploitation and IPR requirements.

**FIGURE 1.1: RESEARCH DATA LIFE CYCLE (ADAPTED FROM UK DATA ARCHIVE [2] )**

The DMP is not a fixed document, but will evolve during the lifespan of the
project, particularly whenever significant changes arise such as dataset
updates or changes in Consortium policies.

This document is the final version of the DMP. It is an update from the
version submitted in October 2018 (D9.10). It has been produced following the
EC guidelines for project participating in this pilot and additional
consideration described in ANNEX I: KEY PRINCIPLES FOR OPEN ACCESS TO RESEARCH
DATA.

##  Research data types in DTOceanPlus

The data types that will be produced during the project are based on the
Description of the Action (DoA) and their results.

According to such consideration, Table 1.1 reports a list of categories of
research data that DTOceanPlus will produce. These research data types have
been defined, including data structures, sampling and processing requirements,
as well as relevant standards. This list may be adapted with the addition or
removal of datasets in the final version of the DMP to take into consideration
the project developments and scientific publications. A detailed description
of each dataset is given in the following sections of this document.

**TABLE 1.1: DTOCEANPLUS TYPES OF DATA**  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Dataset category**

</th>  
<th>

**Lead partner**

</th>  
<th>

**Related WP(s)**

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

**3**

</td>  
<td>

Logistics and Marine Operations

</td>  
<td>

WavEC

</td>  
<td>

WP5

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

**1**

</td>  
<td>

SK, ET and ED Components

</td>  
<td>

TECNALIA

</td>  
<td>

WP5

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

**2**

</td>  
<td>

Environmental and Social Acceptance

</td>  
<td>

FEM

</td>  
<td>

WP6

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

Specific datasets may be associated to scientific publications (i.e.
underlying data), public project reports and other raw data or curated data
not directly attributable to a publication. Datasets can be both collected,
unprocessed data as well as analysed, generated data. The policy for open
access are summarised in Figure 1.2.

**FIGURE 1.2: RESEARCH DATA OPTIONS AND TIMING**

Research data directly linked to the proprietary technologies or projects used
for the validation of the design tools will not be released in the open domain
as they can compromise the commercialisation prospects of industrial partners.
The rest of research data will be deposited in an open access repository.

When the research data is linked to a scientific publication, the provisions
described in ANNEX II: SCIENTIFIC PUBLICATIONS will be followed. Research data
needed to validate the results presented in the publication should be
deposited at the same time for “Gold” Open Access  1  or before the end of the
embargo period for “Green” Open Access  2  . Underlying research data will
consist of selected parts of the general datasets generated, and for which the
decision of making that part public has been made.

Other datasets will be related to any public report or be useful for the
research community. They will be selected parts of the general datasets
generated or full datasets and be published as soon as they become available.

##  Roles and responsibilities

Each DTOceanPlus partner must respect the policies set out in this DMP.
Datasets must be created, managed and stored appropriately and in line with
applicable legislation.

The Project Coordinator has a particular responsibility to ensure that data
shared are easily available, but also that backups are performed, and that
proprietary data are secured.

EDP CNET, as WP7 leader, will ensure dataset integrity and compatibility for
its use during the validation of the design tools by different partners.

Registration of datasets and metadata is the responsibility of the partner
that generates the data in the WP. Metadata constitutes an underlying
definition or description of the datasets, which facilitates finding and
working with particular instances of data.

Backing up data for sharing through open access repositories is the
responsibility of the partner possessing the data.

Quality control of these data is the responsibility of the relevant WP Leader
(particularly WP4-5-6-7), supported by the Project Coordinator.

If datasets are updated, the partner that possesses the data has the
responsibility to manage the different versions and to make sure that the
latest version is available in the case of publicly available data.

Last but not least, all Consortium members must consult the concerned
partner(s) before publishing data that can be associated with an exploitable
result, in the open domain.

#  DATA COLLECTION, STORAGE AND BACK-UP

One of the main outputs of this DMP is to identify research datasets that are
needed in ocean energy designs. They must be generic enough (not specific,
such as site and machine characterisation) to be reusable in multiple
projects. For that purpose, a database of long-standing reference data will
collect all the relevant information produced by the research and
demonstration activities in the project. Essentially, it will contain a
catalogue of components, vessels, ports and equipment, as well as the
associated features for assessments of designs such as performance, cost,
reliability, environmental or social impact ratings. Three main categories for
open datasets have been identified:

  * Logistics and marine operations: data on vessels, equipment, ports and operations. 

  

  * Components: PTO (Power Take-Off), mooring, electrical cabling. 

  

  * Environmental and social acceptance: stressors and materials. 

  

Logistics and marine operations datasets will provide information on the
supporting systems to an ocean energy system throughout its lifecycle. The
environmental and social acceptance will gather key context data to enable
decision-making. Finally, the components datasets define the properties and
give data on main assessments (performance, reliability, cost). In this way,
they might gather pieces of information used in SLC (System Lifetime Cost),
RAMS (Reliability, Availability, Maintainability and Survivability) and SPEY
(System Performance and Energy Yield) modules.

It is important to point out that DTOceanPlus project will produce datasets
that are not univocally related to any commercial supplier, usually creating
catalogues from different sources of information. By combining them, it will
be creating something that is not bound to a specific provider. Particularly,
the DTOceanPlus project will produce reference data resulting from:

  * Supplier datasheets. 

  

  * Literature review. 

  

  * Model fitting. 

  

  * Fundamental relationships. 

  

  * Default values. 

  

The DMP must guarantee the integrity of data during the project. To avoid any
undesirable information loss, regular back-ups or replication in different
locations should be implemented.

The following sections describe the different categories for open datasets
that will be produced in the course of the project.

##  Logistics and Marine Operations Data

The suitable design of offshore Logistics and Marine Operations (LMO) is
paramount to establish the global design of a particular project. Apart from
the physical components and systems, a full characterisation of a wide range
of vessels, equipment and port data is required. As a consequence, the
following reference data have been identified:

  * Activities 

  

  * Operation Types 

  

  * Terminals 

  

  * Vessels 

  

  * Equipment (i.e. Pilling, Protection, Burial, Drivers, ROV) 

  

Among the various features to be captured, there are the following ones:

  * Physical description: dock space, loading capacity, storage area, cranes, vessel size & speed, bollard / winch pull, operating limits, crew, drivers, ROV, duration and location of the operations, relations between vessels and equipment … 

  

  * Quantitative rating: use costs, average fuel consumption, noise level, … A short description of the LMO dataset is given below. 

  

**TABLE 2.1: LOGISTICS AND MARINE OPERATIONS DATA**  
  
<table>  
<tr>  
<th>

**Reference/Name**

</th>  
<th>

• DS_Logisitics_Marine_Operations

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

**Description**

</td>  
<td>

• Activities, operation types, terminals, vessels and equipment. Dataset being
characterised by the physical description and quantitative ratings.

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

**Source**

</td>  
<td>

• Supplier datasheets, literature review and model fitting

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

**Type**

</td>  
<td>

• Derived

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

**Format**

</td>  
<td>

• CSV, MS Excel, SQL, JSON

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

**Software**

</td>  
<td>

• N/A

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

**Estimated size**

</td>  
<td>

• <1 GB

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

**Storage**

</td>  
<td>

• Catalogue / Database

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

**Back-up**

</td>  
<td>

• Regular back-ups on local and/or cloud-hosted servers

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

##  Components Data

The physical characterisation of low-level data components provides key
information to drive the design decisions of ocean energy subsystems, devices
and full array projects. Availability of a large family of components will
significantly facilitate design optimisation. Default values will be provided
insofar they are necessary for completing and ocean energy design but
difficult to determine.

Usually components will comprise balance of plant (e.g. mooring lines and
shackles, power cables, connectors and switchgear) and off-the-shelf
components (e.g. generator and motors, gearboxes, hydraulic cylinders,
turbines, accumulators).

The following sub-sections describe the components data associated to station
keeping, energy transformed and delivery systems.

###  Station Keeping component data

The physical characterisation of Station Keeping (SK) components provides key
information to drive the design decisions of ocean energy mooring systems. The
available data comprises the following components:

  * Buoys 

  

  * Shackles 

  

  * Swivels 

  

  * Anchors 

  

  * Chains 

  

  * Wire ropes 

  

  * Synthetic ropes 

  

Among the various component features, the material, mass, sizing and main
physical properties of components, as well as feasible combinations between
anchors and soil types will be captured.

A short description of the station keeping dataset is given below.

**TABLE 2.2: STATION KEEPING COMPONENT DATA**  
  
<table>  
<tr>  
<th>

**Reference/Name**

</th>  
<th>

• DS_Station_Keeping

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

**Description**

</td>  
<td>

• SK components (i.e. Buoys, Shackles, Swivels, Anchors, Chains, Wire ropes
and Synthetic ropes), physical features and feasible combinations between
anchors and soil types

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

**Source**

</td>  
<td>

• Supplier datasheets and literature review

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

**Type**

</td>  
<td>

• Derived

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

**Format**

</td>  
<td>

• CSV, MS Excel, SQL, JSON

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

**Software**

</td>  
<td>

• N/A

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

**Estimated size**

</td>  
<td>

• < 1 GB

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

**Storage**

</td>  
<td>

• Catalogue / Database

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

**Back-up**

</td>  
<td>

• Regular back-ups on local and/or cloud-hosted servers

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

###  Energy Transformation component data

To drive the design decisions of ocean Energy Transformation (ET) system for a
device or for a full array project, the available dataset comprises at least
the following components:

  * Turbine 

  

  * Power generator 

  

  * Power converter 

  

Among the various component features, the material, mass, sizing and main
physical properties of ET components; performance and energy yield
characteristics (e.g. efficiency curve, etc.); reliability, availability,
maintainability and survivability data (e.g. failure rate, design limits,
etc.); and lifetime costs (e.g. cost of manufacture, assembly, replace,
repair, etc.) will be captured.

DTOceanPlus will require quantitative ratings of various performance
parameters at component level to derive aggregated figures for subsystems,
devices and ultimately the whole array. Benchmarks and thresholds for
Structured Innovation and Stage Gate Design Tools may be also considered
within this category.

A short description of the ET dataset is given in Table 2.3.

**TABLE 2.3: ENERGY TRANSFORMATION COMPONENT DATA**  
  
<table>  
<tr>  
<th>

**Reference/Name**

</th>  
<th>

• DS_Energy_Transformation

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

**Description**

</td>  
<td>

• ET components (i.e. Turbine, Generator, Power converter), physical features,
performance and energy yield, reliability, availability, maintainability and
survivability and lifetime costs.

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

**Source**

</td>  
<td>

• Supplier datasheets and literature review

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

**Type**

</td>  
<td>

• Derived

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

**Format**

</td>  
<td>

• CSV, MS Excel, SQL, JSON

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

**Software**

</td>  
<td>

• N/A

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

**Estimated size**

</td>  
<td>

• < 1 GB

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

**Storage**

</td>  
<td>

• Catalogue / Database

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

**Back-up**

</td>  
<td>

• Regular back-ups on local and/or cloud-hosted servers

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

###  Energy Delivery component data

The available data related to the Energy Delivery (ED) system will comprise
the following components:

  * Switchgear 

  

  * Collection point 

  

  * Transformer 

  

  * Dry mate connector 

  

  * Wet mate connector 

  

  * Dynamic cable 

  

  * Static cable 

  

As in the case of the Energy Transformation dataset, among the various
component features, the material, mass, sizing and main physical properties of
ED components; performance and energy yield characteristics; reliability,
availability, maintainability and survivability data; and lifetime costs will
be captured.

A short description of the ED dataset is given below.

**TABLE 2.4: ENERGY DELIVERY COMPONENT DATA**  
  
<table>  
<tr>  
<th>

**Reference/Name**

</th>  
<th>

• DS_Energy_Delivery

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

**Description**

</td>  
<td>

• ED components (i.e. Switchgear, Collection point, Transformer, Dry/Wet mate
connectors, Dynamic cable and Static cable), physical features, performance
and energy yield, reliability, availability, maintainability, survivability
and lifetime.

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

**Source**

</td>  
<td>

• Supplier datasheets and literature review

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

**Type**

</td>  
<td>

• Derived

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

**Format**

</td>  
<td>

• CSV, MS Excel, SQL, JSON

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

**Software**

</td>  
<td>

• N/A

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

**Estimated size**

</td>  
<td>

• < 1 GB

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

**Storage**

</td>  
<td>

• Catalogue/Database

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

**Back-up**

</td>  
<td>

• Regular back-ups on local and/or cloud-hosted servers

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

##  Environment & Social Acceptance Assessment Data

Reference data may be required to assess ocean energy projects in their
context and take global design decisions. One of the assessments in
DTOceanPlus is the Environmental and Social Acceptance (ESA). For this reason,
the available dataset comprises the following categories:

  * Endangered species 

  

  * Materials 

  

  * Job Creation 

  

Among the various component features, there will be captured characteristics
related to environmental and social acceptance such as stressors and CO2
emissions.

A short description of the ESA dataset is given below.

**TABLE 2.5: ENVIRONMENTAL & SOCIAL ACCEPTANCE DATA **  
  
<table>  
<tr>  
<th>

**Reference/Name**

</th>  
<th>

• DS_Environmental_SocialAcceptance

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

**Description**

</td>  
<td>

• Characteristics related to environmental and social acceptance of materials
and endangered species.

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

**Source**

</td>  
<td>

• Supplier datasheets and literature review

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

**Type**

</td>  
<td>

• Derived

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

**Format**

</td>  
<td>

• CSV, MS Excel, SQL, JSON

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

**Software**

</td>  
<td>

• N/A

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

**Estimated size**

</td>  
<td>

• <1 GB

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

**Storage**

</td>  
<td>

• Catalogue / Database

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

**Back-up**

</td>  
<td>

• Regular back-ups on local and/or cloud-hosted servers

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

#  DATA STANDARDS AND METADATA

The following standards should be used for data documentation:

  * DNV-RP-J301 [3] : Subsea Power Cables in Shallow Water Renewable Energy Applications. 

  

  * DNVGL-OS-E301 [4] : it contains criteria, technical requirements and guidelines on design and construction of position mooring systems. The objective of this standard is to give a uniform level of safety for mooring systems, consisting of chain, steel wire ropes and fibre rope. 

  

  * IEC TS 62600-10 [5] : technical specification for assessment of mooring system for Marine Energy Converters (MECs). 

  

  * IEC TS 62600-30 [6] : technical specification on electrical power quality requirements for wave, tidal and other water current energy converters. 

  

  * IEC TS 62600-100 [7] : technical specification on power performance assessment of electricity producing wave energy converters. 

  

  * IEC TS 62600-200 [8] : Electricity producing tidal energy converters - Power performance assessment. 

  

  * ISO 14224:2006 [9] : collection and exchange of reliability and maintenance data for equipment. 

  

Metadata records will accompany the data files in order to describe,
contextualise and facilitate external users to understand and reuse the data.

DTOceanPlus will adopt the DataCite Metadata Schema [10] , a domain agnostic
metadata schema, as the basis for harvesting and importing metadata about
datasets from data archives. The core mission of DataCite is to build and
maintain a sustainable framework that makes it possible to cite data through
the use of persistent identifiers.

The following metadata should be created to identify datasets:

  * Identifier: A unique string that identifies the dataset. 

  

  * Author/Creator: The main researchers involved in producing the data in priority order. 

  

  * Title: A name or title by which a data is known. 

  

  * Publisher: The name of the entity that holds, archives, publishes prints, distributes, releases, issues, or produces the data. 

  

  * Publication Year: The year when the data was or will be made publicly available. 

  

  * Subject: Subject, keyword, classification code, or key phrase describing the resource. 

  

  * Contributor: Name of the funding entity (i.e. "European Union" & "Horizon 2020"). 

  

  * Size: Unstructured size information about the dataset (in GBs). 

  

  * Format: Technical format of the dataset (e.g. csv, txt, xml, etc.). 

  

  * Version: The version number of the dataset. 

  

  * Access rights: Provide a rights management statement for the dataset. Include embargo information if applicable. 

  

  * Geo-location: Spatial region or named place where the data was gathered. 

  

#  DATA SHARING AND REUSE

During the life cycle of the DTOceanPlus project, datasets will be stored and
systematically organised in a relational database tailored to comply with the
requirements of WP7. The database schema and the queryable fields, will be
also publicly available to the database users as a way to better understand
the database itself.

In addition to the project database, relevant datasets will be also stored in
ZENODO [11] , which is the open access repository of the Open Access
Infrastructure for Research in Europe, OpenAIRE [12] .

All collected datasets will be disseminated without an embargo period unless
linked to a green open access publication. Data objects will be deposited in
ZENODO under:

  * Open access to data files and metadata and data files provided over standard protocols such as HTTP and OAI-PMH. 

  

  * Use and reuse of data permitted. 🞂 Privacy of its users protected. 

  

By default, data access policy will be unrestricted unless otherwise
specified. The generic Creative Commons CC-BY licenses will be used. This
license allows:

  * Sharing - copy and redistribute the material in any medium or format. 

  

  * Adapting - remix, transform, and build upon the material for any purpose, even commercially. 

  

#  DATA ARCHIVING AND PRESERVATION

The DTOceanPlus project database will be designed to remain operational for 5
years after the project end. By the end of the project, the final dataset will
be transferred to the ZENODO repository, which ensures sustainable archiving
of the final research data.

Items deposited in ZENODO will be retained for the lifetime of the repository,
which is currently the lifetime of the host laboratory CERN and has an
experimental programme defined for the at least next 20 years. Data files and
metadata are backed up on a nightly basis, as well as replicated in multiple
copies in the online system. All data files are stored along with a MD5
checksum of the file content. Regular checks of files against their checksums
are made.