#  INTRODUCTION

A Data Management Plan (DMP) has been developed using FAIR data principles –
Findable, Accessible, Interoperable and Reusable. The DMP outlines what
datasets the project will generate and compile, and how these datasets will be
made accessible and stored. The DMP also describes measures that have been
taken to safeguard and protect sensitive data and emphasizes that the produced
results must be easily located and accessible.

OceanSET has chosen to use the template provided for the Data Management Plan.
At present, very little data has been collected by the project. The OceanSET
DMP is intended to be a ‘living’ document that will outline how the OceanSET
research data will be handled during and after the project, and so it will be
reviewed and updated over the course of the project whenever significant
changes arise, such as (but not limited to):

  * new data being gathered; 

  

  * generation of periodic reports; 

  

  * development of final report; 

  

  * changes in consortium policies; 

  

  * changes in consortium composition and external factors (e.g. new consortium members joining or old members leaving). 

  

In preparation for this report the OceanSET partners considered a number of
issues to be addressed. Table 1 provides a summary of the issues considered
when preparing this DMP.

SEAI will be responsible for disseminating this DMP to all project partners.
Each project partner will be responsible for managing their data, metadata,
and insuring their data meets the quality standard set out in the OceanSET
Quality Handbook.

**TABLE 1: DMP COMPONENTS**  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Issues to be addressed**

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

**1\. Data**

**summary**

</td>  
<td>

  * State the purpose of the data collection/generation 

  

  * Explain the relation to the objectives of the project 

  

  * Specify the types and formats of data generated/collected 

  

  * Specify if existing data is being re-used (if any) 

  

  * Specify the origin of the data 

  

  * State the expected size of the data (if known) 

  

  * Outline the data utility: to whom will it be useful 

  

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

  2. **FAIR Data**

  

  

2.1. Making data findable, including

provisions for metadata

</td>  
<td>

  * Outline the discoverability of data (metadata provision) 

  

  * Outline the identifiability of data and refer to standard identification mechanism. Do you make use of persistent and unique identifiers such as Digital Object Identifiers? 

  

  * Outline naming conventions used 

  

  * Outline the approach towards search keyword 

  

  * Outline the approach for clear versioning 

  

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

</td>  
<td>



</td>  
<td>

Specify standards for metadata creation (if any). If there are no standards in
your discipline describe what type of metadata will be created and how

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

2.2 Making data openly accessible

</td>  
<td>





</td>  
<td>

Specify which data will be made openly available? If some data is kept closed
provide rationale for doing so

Specify how the data will be made available

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

</td>  
<td>



</td>  
<td>

Specify what methods or software tools are needed to access the data? Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?

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

</td>  
<td>



</td>  
<td>

Specify where the data and associated metadata, documentation and code are
deposited

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

</td>  
<td>



</td>  
<td>

Specify how access will be provided in case there are any restrictions

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

2.3. Making data interoperable

</td>  
<td>





</td>  
<td>

Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.

Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow inter-disciplinary interoperability? If
not, will you provide mapping to more commonly used ontologies?

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

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

</td>  
<td>







</td>  
<td>

Specify how the data will be licenced to permit the widest reuse possible

Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data embargo is needed

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

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

</td>  
<td>



</td>  
<td>

Describe data quality assurance processes

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

</td>  
<td>



</td>  
<td>

Specify the length of time for which the data will remain re-usable

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

**3\. Allocation of resources**

</td>  
<td>



</td>  
<td>

Estimate the costs for making your data FAIR. Describe how you intend to cover
these costs

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

</td>  
<td>



</td>  
<td>

Clearly identify responsibilities for data management in your project

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

</td>  
<td>



</td>  
<td>

Describe costs and potential value of long-term preservation

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

**4\. Data security**

</td>  
<td>



</td>  
<td>

Address data recovery as well as secure storage and transfer of sensitive data

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

**5\. Ethical aspects**

</td>  
<td>



</td>  
<td>

To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former

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

**6\. Other**

</td>  
<td>



</td>  
<td>

Refer to other national/funder/sectorial/departmental procedures for data
management that you are using (if any)

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

##  Definitions

This section provides definitions for terms used in this document.

**TABLE 2: DEFINITIONS**  
  
<table>  
<tr>  
<th>

Project partners/ consortium

</th>  
<th>

The organization constituted for the purposed of the OceanSET project
comprising of:

  * Sustainable Energy Authority of Ireland (SEAI) 

  

  * Wave Energy Scotland (WES) 

  

  * Directorate General of Energy and Geology (DGEG) 

  

  * Ocean Energy Europe (OEE) 

  

  * France Energies Marines (FEM) 

  

  * National Agency for New Technologies, Energy and Sustainable Economic  (ENEA) 

  

  * Ente Vasco de la Energía (EVE) 

  

  * The University of Edinburgh (UEDIN) 

  

  * Oceanic Platform of the Canary Islands (PLOCAN) 

  

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

Dataset

</td>  
<td>

Digital information created in the course of research, but which is not a
published research output. Research data excludes purely administrative
records. The highest priority research data is that which underpins a research
output. Research data do not include publications, articles, lectures or
presentations.

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

Data Type

</td>  
<td>

  * R: Document, report (excluding the periodic and final reports) 

  

  * DEM: Demonstrator, pilot, prototype, plan designs 

  

  * DEC: Websites, patents filing, press & media actions, videos, etc. 

  

  * OTHER: Software, technical diagram, etc. 

  

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

Dissemination

Level

</td>  
<td>

  * PU: Public, fully open, e.g. web 

  

  * CO: Confidential, restricted under conditions set out in Grant Agreement  CI: Classified, information as referred to in Commission Decision 2001/844/EC. 

  

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

Metadata

</td>  
<td>

Information about datasets stored in a repository/database template, including
size, source, author, production date etc.

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

Repository

</td>  
<td>

A digital repository is a mechanism for managing and storing digital content.

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

#  1\. Data Summary

**1a. What is the purpose of the data collection/generation and its relation
to the objectives of the project?**

The OceanSET Data Management Plan (DMP) aims to provide a strategy for
managing data generated and collected during the project and to optimise
access to and re-use of research data. Data generated during the project can
be divided into the following groups:

  * Data collected from stakeholders during the annual mapping exercise. This consists primarily of raw data collected via individual stakeholder questionnaires; 

  

  * Data generated by project partners during the analysis and monitoring exercises. This dataset consists of compiling raw data provided by stakeholders in the format of agreed metrics. 

  

The purpose of this data collection is to help achieve our 3 main objectives
of the project:

  * Facilitate the implementation of the technology development actions for Ocean energy in the SET Plan; 

  

  * Promote knowledge sharing across the European Commission, Member States, Regions and other stakeholders in the ocean energy sector; 

  

  * Investigate collaborative funding mechanisms between Member States and Regions. 

  

These objectives in turn will incentivise the engagement of stakeholders in
the annual mapping exercise. The Plan for Exploitation and Dissemination
Report (PEDR) will devise a means of feeding project results back to
stakeholders who provided information in questionnaires. This feedback loop is
seen as a key knowledge sharing mechanism and means of continued engagement
with stakeholders. The PEDR for OceanSET is available on the OceanSET website:
_www.oceanset.eu_ .

**1b. What types and formats of data will the project generate/collect and
what is the origin of the data?**

Table 3 and table 4 below set out the data sets types and format the will be
generated and collected by the OceanSET project as well as the related Work
Package (WP) number. Table 3 is the list of ‘Open Access Content’, presented
in relation to the project Deliverables.

**TABLE 3: PUBLIC OCEANSET DATA**  
  
<table>  
<tr>  
<th>

#

</th>  
<th>

**Data Type**

</th>  
<th>

**Origin**

</th>  
<th>

**WP#**

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

1

</td>  
<td>

Project Website

</td>  
<td>

FEM & Publicly available data

</td>  
<td>

WP6

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

2

</td>  
<td>

Metrics for OE Sector

</td>  
<td>

DGEG & WES

</td>  
<td>

WP5

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

3

</td>  
<td>

Report Plan for Exploitation and Dissemination of Results

</td>  
<td>

FEM

</td>  
<td>

WP6

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

4

</td>  
<td>

Report on Project data management Plan

</td>  
<td>

SEAI

</td>  
<td>

WP6

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

5

</td>  
<td>

Report on Knowledge sharing workshops

</td>  
<td>

DGEG

</td>  
<td>

WP5

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

6

</td>  
<td>

Publication and Promotion of Annual Reports

</td>  
<td>

SEAI & Secondary data

</td>  
<td>

WP6

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

7

</td>  
<td>

Report on Dissemination Workshops

</td>  
<td>

Secondary data

</td>  
<td>

WP6

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

8

</td>  
<td>

Financial requirements for SET PLAN

</td>  
<td>

WES & Secondary data

</td>  
<td>

WP3

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

9

</td>  
<td>

Public/private financing ratio for each action, or bundle of actions, in the
SETPlan IP

</td>  
<td>

Secondary data

</td>  
<td>

WP3

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

Table 4 is the list of ‘Closed Content’, presented in relation to the project
Deliverables.

**TABLE 4: PRIVATE OCEANSET DATA**  
  
<table>  
<tr>  
<th>

#

</th>  
<th>

**Data Type**

</th>  
<th>

**Origin**

</th>  
<th>

**WP#**

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

1

</td>  
<td>

POPD - Requirement No. 3

</td>  
<td>

SEAI

</td>  
<td>

WP1

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

2

</td>  
<td>

Project Management handbook

</td>  
<td>

SEAI

</td>  
<td>

WP7

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

3

</td>  
<td>

Quality Handbook

</td>  
<td>

SEAI

</td>  
<td>

WP7

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

4

</td>  
<td>

H - Requirement No. 1

</td>  
<td>

SEAI

</td>  
<td>

WP1

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

5

</td>  
<td>

Refined Technology Strategy

</td>  
<td>

WES

</td>  
<td>

WP4

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

6

</td>  
<td>

Agreed PCP operating mechanism

</td>  
<td>

WES Primary Data

</td>  
<td>

WP4

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

7

</td>  
<td>

Annual mapping and analysis progress report

</td>  
<td>

SEAI

</td>  
<td>

WP2

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

8

</td>  
<td>

Annual Funding Gap analysis and recommendation report

</td>  
<td>

WES

</td>  
<td>

WP3

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

9

</td>  
<td>

Annual Monitoring and Review Report

</td>  
<td>

DGEG

</td>  
<td>

WP5

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

10

</td>  
<td>

Annual Report on Dissemination and Communication activities

</td>  
<td>

FEM & Secondary

Data

</td>  
<td>

WP6

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

11

</td>  
<td>

Call Documentation for PCP

</td>  
<td>

WES

</td>  
<td>

WP4

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

12

</td>  
<td>

Design of Insurance and Guarantee Fund

</td>  
<td>

Primary Data

</td>  
<td>

WP3

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

**1c. Will you re-use any existing data and how?**

While it is envisaged that most data collected will be open access and widely
disseminated, some results of the project may need to be protected due to IP
rights. Regarding the exploitation of results, there currently is no plan to
exploit the information other than in the sense of maximizing communication
and dissemination actions to the benefit of the project goals. In the
Consortium Agreement there is an option to exploit jointly owned data between
partners via request to the partners under fair and reasonable use. However,
currently there is no active plan to ‘exploit’ the data.

Even if these databases are deemed valuable, the objective of the project is
not to derive direct business opportunities for the partners involved, but
rather to inform ocean energy stakeholders, funders and policy makers of the
availability of project results. This will remain central in any agreements
around data collection and dissemination.

**1d. To whom might it be useful ('data utility')?**

The data generated in the project will be very beneficial to a variety of
stakeholders including: policy makers, public funders, device developers,
utilities, private investors and supply chain companies. The data collected
will be relevant to key areas of OE project development including; technology
development, consenting and project finance. Information gathered will help
identify challenges in these areas and serve as an input for policy design at
national and European level in these areas. Finally, the data will inform the
wider public about the developments and potential of the ocean energy sector.

#  2\. FAIR data

The OceanSET DMP (D6.2) applies the Findable, Accessible, Interoperable,
Reusable (FAIR) approach for the project’s results.

##  Making data findable, including provisions for metadata

It is envisaged that the report that will contain the bulk of data collected
by OceanSET will be the annual reports. OceanSET will publish 3 annual reports
which will be the primary method of disseminating the data collected. The
annual reports will present data as meta or grouped data; individual sources
of data will not be identifiable. The annual report will include references to
the original data source. Keywords will be provided which will clearly
identify the type of data contained in the report.

All OceanSET’s documents will be identifiable based on a common naming
convention. Version control will be clearly identified and will follow the
version control set out in the OceanSET Project Management Handbook, which is
available to the OceanSET consortium.

To ensure document and data control, each document and data set shall be
uniquely identifiable. Each deliverable and data set must be associated unique
document name to ensure version control. The deliverable and data identifier
must be used in the deliverable filename.

The data identifier for the deliverable must be: ** <Deliverable
identifier><Up-to-three-words-from the data name>_<followed by the version
number>_<Partner & (authors initials)>_<date dd-mmyyyy>.doc **

Example: Deliverable7.4_OceanSET Annual
Report_v0.1_SEAI(JF)_01-01-2019.docMaking data openly accessible

OceanSET will focus on assessing the progress of the ocean energy sector and
will monitor the National and EU funded projects in delivering successful
supports. Relevant data will be collected annually and will be used to inform
Member States (MS) and the European Commission (EC) on progress of the sector.
It will also be used to review what works and what doesn’t and to assess how
to maximise the benefit of the funding streams provided across the MS, Regions
and the EU.

The metadata will be disseminated through the Annual Report. These reports
will be published in full as appropriate in the following locations:

  * The OceanSET project website  _www.oceanset.eu_

  

  * The Community Research and Development Information Service (CORDIS) which is the European Commission's primary source of results from the projects funded by the EU's framework programmes for research and innovation including Horizon 2020. 

  

  * A research data repository, compatible and compliant with OpenAIRE guidance. The repository will host scientific publications and all datasets associated with such publications. 

  

The Confidential project data sets and reports will be hosted on:

  * The OceanSET Consortium private file sharing folder, this allows secure data share across partners. This area provides a space for information exchange and an archive for all the documentation produced along the Project lifespan. 

  

  * Individual partner’s institutional online repositories will host and preserve data until the end of the project. 

  

Table 3 outlines the data that will be made public, with Table 4 indicating
the private data generated within OceanSET.

In accordance with Article 27 of the grant agreement (Appendix A), the project
partners are obliged to protect the results where these can be expected to be
commercially or industrially exploited.

##  Making data interoperable

Data will be collected and shared in a standardised way using a standard
format for that data type. As required, reference will be made to any software
required to run it. Given the scope of this project it is anticipated that
publicly available software will be used to store data. Barriers to access
through interoperability issues are not anticipated.

The metadata format will follow the convention of the hosting research data
repository. A draft metadata format is set out below and this is subject to
review in the next DMP update.

General Information

  * Title of the dataset/output 

  

  * Dataset Identifier (using the naming convention outlined in Section 2.1) 

  

  * Responsible Partner 

  

  * Work Package 

  

  * Author Information 

  

  * Date of data collection/production 

  

  * Geographic location of data collection/ production 

  

  * The title of project and Funding sources that supported the collection of the data i.e. European Union’s Horizon 2020 research and innovation programme under grant agreement No 840651. 

  

Sharing/Access Information

  * Licenses/access restrictions placed on the data 

  

  * Link to data repository 

  

  * Links to other publicly accessible locations of the data, see list in Section 2.2  Links to publications that cite or use the data  Was data derived from another source? 

  

Dataset/Output Overview

  * What is the status of the documented data? – “complete”, “in progress”, or “planned” 

  

  * Date of production 

  

  * Date of submission/publication  Are there plans to update the data? 

  

  * Keywords that describe the content 

  

  * Version number 

  

  * Format - Post Script (PDF), Excel (XLSX, CSV), Word (DOC), Power Point (PPT), image (JPEG, PNG, GIF, TIFF). 

  

  * Size - MBs 

  

Methodological Information

  * Used materials 

  

  * Description of methods used for experimental design and data collection 

  

  * Methods for processing the data 

  

  * Instruments and software used in data collection and processing-specific information needed to interpret the data 

  

  * Standards and calibration information, if appropriate 

  

  * Environmental/experimental conditions 

  

  * Describe any quality-assurance procedures performed on the data  Dataset benefits/utility 

  

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

OcenanSET is focused on gathering existing data and monitoring. The metadata
will be available for re-use through the OceanSET website where the annual
reports will be stored and will be published on CORDIS. Data sets uploaded in
OceanSET repository will be accessible to the public by contacting OceanSET
via the website to request access to the datasets. Potential users are
expected to adhere with the Terms of Use of the repository. OceanSET will
ensure that all data requests will be subject to scrutiny under GDPR and that
no data which can identify individual sources or technology will be released.

#  3\. Allocation of resources

  3. **What are the costs for making data FAIR in your project?**

  

  

The activities related to making the data/outputs open access are anticipated
to be covered within the allocated budget for each work package. Further
investigation of potential cost related to a repository need to be done. The
repository will ensure that data is stored safely and securely and in full
compliance with European Union data protection laws and in accordance with
Article 27 (Appendix A).

**3.b 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).**

The costs related to open access to research data are eligible as part of the
OceanSET Horizon 2020 grant. The costs of making scientific publications,
hosting a project website and the partners and open access data repositories
are contained within the OceanSET budget as eligible costs.

**3c. Who will be responsible for data management in your project?**

SEAI has been appointed as the Quality and Data Manager (QDM), in
collaboration with consortium partners, to manage the data generated during
the project. The QDM will identify an appropriate data repository to store and
safeguard the datasets but ensure that data is readily accessible. Data
generated during the project can be divided into the following groups:

  * Data collected from stakeholders during the annual mapping exercise. This consists primarily of raw data collected via individual stakeholder questionnaires. 

  

  * Data generated by project partners during the analysis and monitoring exercises. This dataset consists of compiling raw data provided by stakeholders in the format of agreed metrics. 

  

France Energies Marine (FEM) have been appointed as Communication and
Dissemination Manager (CDM), in collaboration with consortium partners, they
will oversee the identification of which datasets will be disseminated and the
most appropriate means of disseminating this data. This has been conducted and
the defined strategy is presented in the Plan for Exploitation and
Dissemination Report (PEDR) in Deliverable 6.1.

**3d. 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)?**

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 Consortium’s General Assembly (GA) at the SET Plan’s
Implementation Working Group meeting. OceanSET aims to align with the long-
term preservation of data of the SET Plan.

#  4\. Data security

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

For the duration of the project, datasets will be stored on the responsible
partner’s storage system. Every partner is responsible to ensure that the data
are stored safely and securely and in full compliance with European Union data
protection laws and in accordance with Article 27 (Appendix

A).

SEAI as lead partner will have the responsibility to store the bulk of the
data collated from questionnaires. While a bespoke repository has not yet been
designed, a system is planned that will be aligned with requirements under
Article 27.

SEAI’s IT data handling and security policy is available below in Appendix B.

It is the policy of the SEAI to:

  * Implement human, organisational, and technological security controls to preserve the confidentiality, availability and integrity of its information. 

  

  * Comply with all laws and regulations governing information security. 

  

  * Develop and maintain appropriate policies, procedures and guidelines to achieve a high standard of information security, reflecting industry best practice. 

  

  * Actively assess and manage risks to SEAI information. 

  

  * Continuously review and improve SEAI information security controls. 

  

  * Respond to any breach of security to minimise damage to information systems. 

  

After the completion of the project, all the responsibilities concerning data
recovery and secure storage will go to the repository storing the dataset.

**4b. Is the data safely stored in certified repositories for long term
preservation and curation?**

The data will be stored long term in a certified repository that is in line
with the requirements of the SET PLAN. This will be discussed at the SET PLAN
OceanSET Implementation Work Group.

#  5\. Ethical aspects

**5 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).**

The General Data Protection Regulation will be respected for all relevant
personal data collected. When the project involves access by the partners to
personal data, the partners shall be regarded as responsible for treatment of
said data and shall comply with rules. The ethics requirements of the OceanSET
project are further described in the Work Package 1 which includes Deliverable
1.1: H - Requirement No. 1 and D1.2: POPD - Requirement No. 3.

OceanSET have developed a procedure to insure any personal data we receive is
given by consent. Participants who sign up to OceanSET will sign up via our
3-step sign-up process.

**Step 1:** Interested parties in the OceanSET project can become participants
of the project in two ways:

  * Participants can visit our website  _www.oceanset.eu_ and if they are interested in getting involved, sign up to our mailing list/database; 

  

  * Project partners inform their relevant business contacts who may be interested about the project and encourage them to sign up via the website or by return email **.**

  

**Step 2** : Once an interested party signs up to our mailing list/database,
he or she will receive an email asking to confirm the requested subscription
by clicking the “Yes, subscribe me to the list”. This email also provides a
point of contact should the interested party have any questions about what
they are joining.

**Step 3** : If the interested party confirms the subscription, he or she will
be prompted to confirm that the respondant is human by clicking the “I’m not a
Robot”

The sign-up form and emails from project partners inform participants about
the OceanSET project and identify the point of contact. The website also
includes a Privacy Policy adjacent to the sign-up on the website which
includes;

  * Types of Collected Data, 

  

  * The purpose for which the data will be processed,  The persons to whom the data may be disclosed. 

  

If any changes occur to our privacy policy, we will notify participants of
these changes by posting the new Privacy Policy on the website. The OceanSET
Privacy Policy is available on the OceanSET website  _www.oceanset.eu_ .

Data collected and produced as part of the project will be done in accordance
with the ethical principles, notably to avoid fabrication, falsification,
plagiarism or other research misconduct. It is not the intent of the OceanSET
questionnaires or interviews to collect personal data.

Participants confirm consent by completing the survey/interview. Participants
will be informed that the business information provided may be put in the
public domain in anonymised, aggregated

format. Questionnaires provided by OceanSET will include a copy of the
OceanSET Privacy Policy as well as contact details of the appointed Data
Protection Officer (DPO).

#  6\. Other issues

**6a. Do you make use of other national/funder/sectorial/departmental
procedures for data management? If yes, which ones?**

The lead partner is subject to the Data protection Act; Freedom of Information
Act and General Data Protection Regulation. All data must be collected, stored
and disseminated in accordance with these Acts.

#  Appendix A: OceanSET Grant Agreement Extract

###  ARTICLE 27 — PROTECTION OF RESULTS — VISIBILITY OF EU FUNDING 27.1
Obligation to protect the results

Each beneficiary must examine the possibility of protecting its results and
must adequately protect them — for an appropriate period and with appropriate
territorial coverage — if: (a) the results can reasonably be expected to be
commercially or industrially exploited and

(b) protecting them is possible, reasonable and justified (given the
circumstances). When deciding on protection, the beneficiary must consider its
own legitimate interests and the legitimate interests (especially commercial)
of the other beneficiaries.

###  27.2 _Unspecified Granting Authority_ ownership, to protect the results

If a beneficiary intends not to protect its results, to stop protecting them
or not seek an extension of protection, _the Unspecified Granting Authority_
may — under certain conditions (see Article 26.4) — assume ownership to ensure
their (continued) protection.

###  27.3 Information on EU funding

Applications for protection of results (including patent applications) filed
by or on behalf of a beneficiary must — unless the _Commission_ requests or
agrees otherwise or unless it is impossible — include the following:

“The project leading to this application has received funding from the
_European Union’s Horizon 2020 research and innovation programme_ under grant
agreement No 840651”.

###  27.4 Consequences of non-compliance

If a beneficiary breaches any of its obligations under this Article, the grant
may be reduced (see Article 43).

Such a breach may also lead to any of the other measures described in Chapter
6.

**ARTICLE 29 — DISSEMINATION OF RESULTS — OPEN ACCESS — VISIBILITY OF EU
FUNDING**

###  29.1 Obligation to disseminate results

Unless it goes against their legitimate interests, each beneficiary must — as
soon as possible — ‘ **disseminate** ’ its results by disclosing them to the
public by appropriate means (other than those resulting from protecting or
exploiting the results), including in scientific publications (in any medium).
This does not change the obligation to protect results in Article 27, the
confidentiality obligations in Article 36, the security obligations in Article
37 or the obligations to protect personal data in Article 39, all of which
still apply.

A beneficiary that intends to disseminate its results must give advance notice
to the other beneficiaries

###  29.2 Open access to scientific publications

Each beneficiary must ensure open access (free of charge online access for any
user) to all peer-reviewed scientific publications relating to its results. In
particular, it must:

(a) as soon as possible and at the latest on publication, deposit a machine-
readable electronic copy of the published version or final peer-reviewed
manuscript accepted for publication in a repository for scientific
publications;

Moreover, the beneficiary must aim to deposit at the same time the research
data needed to validate the results presented in the deposited scientific
publications. (b) ensure open access to the deposited publication — via the
repository — at the latest:

  1. on publication, if an electronic version is available for free via the publisher, or 

  

  2. within six months of publication (twelve months for publications in the social sciences and humanities) in any other case. 

  

  

(c) ensure open access — via the repository — to the bibliographic metadata
that identify the deposited publication.

The bibliographic metadata must be in a standard format and must include all
of the following: of — unless agreed otherwise — at least 45 days, together
with sufficient information on the results it will disseminate.

Any other beneficiary may object within — unless agreed otherwise — 30 days of
receiving notification, if it can show that its legitimate interests in
relation to the results or background would be significantly harmed. In such
cases, the dissemination may not take place unless appropriate steps are taken
to safeguard these legitimate interests.

If a beneficiary intends not to protect its results, it may — under certain
conditions (see Article 26.4.1) — need to formally notify the _Commission_
before dissemination takes place.

  * the terms _“European Union (EU)” and “Horizon 2020”_ ; 

  

  * the name of the action, acronym and grant number; 

  

  * the publication date, and length of embargo period if applicable, and - a persistent identifier. 

  

###  29.3 Open access to research data

_Regarding the digital research data generated in the action (‘**data** ’),
the beneficiaries must: (a) deposit in a research data repository and take
measures to make it possible for third parties tocaccess, mine, exploit,
reproduce and disseminate — free of charge for any user — the following: _

  1. _the data, including associated metadata, needed to validate the results presented in scientific publications, as soon as possible;_

  

  2. _not applicable;_

  

  3. _other data, including associated metadata, as specified and within the deadlines laid down in the ‘data management plan’ (see Annex 1); (b) provide information — via the repository — about tools and instruments at the disposal of the beneficiaries and necessary for validating the results (and — where possible — provide the tools and instruments themselves)._

  

  

_This does not change the obligation to protect results in Article 27, the
confidentiality obligations in Article 36, the security obligations in Article
37 or the obligations to protect personal data in Article 39, all of which
still apply._

_As an exception, the beneficiaries do not have to ensure open access to
specific parts of their research data under Point (a)(i) and (iii), if the
achievement of the action's main objective (as described in Annex 1) would be
jeopardised by making those specific parts of the research data openly
accessible. In this case, the data management plan must contain the reasons
for not giving access._

**29.4 Information on EU funding — Obligation and right to use the EU emblem**
Unless the _Commission_ requests or agrees otherwise or unless it is
impossible, any dissemination of results (in any form, including electronic)
must: (a) display the EU emblem and (b) include the following text:

“This project has received funding from the _European Union’s Horizon 2020
research and innovation programme_ under grant agreement No 840651”.

When displayed together with another logo, the EU emblem must have appropriate
prominence. For the purposes of their obligations under this Article, the
beneficiaries may use the EU emblem without first obtaining approval from the
_Commission_ .

This does not however give them the right to exclusive use.

Moreover, they may not appropriate the EU emblem or any similar trademark or
logo, either by registration or by any other means.

###  29.5 Disclaimer excluding _Commission_ responsibility

Any dissemination of results must indicate that it reflects only the author's
view and that the _Commission_ is not responsible for any use that may be made
of the information it contains.

###  29.6 Consequences of non-compliance

If a beneficiary breaches any of its obligations under this Article, the grant
may be reduced (see Article 43). Such a breach may also lead to any of the
other measures described in Chapter 6.

#  Appendix B: SEAI Information Security & Handling Policy

SEAI Information

Security Policy.pdf

SEAI Information

Classification Handling

**CONTACT DETAILS**

Ms. Patricia Comiskey Project Coordinator, SEAI

This project has received funding from the European Union’s Horizon 2020
research and innovation programme under grant agreement N°840651