#  Executive summary

The overall objective of WP7 in SYLFEED is to “ _continuously monitor and
provide means for the SYLFEED partners to share their knowledge within the
consortium and to integrate the research activities as well as to exploit the
developments, and/or communicate and disseminate the results to the scientific
and industrial community and to the wider audience. The global objective is to
prepare and encourage the use and wide acceptance of project outputs_ ”, as
per the Description of Action (DoA). Additionally, internal communication is
an integral part of the success of SYLFEED, as described in WP8, specifically
Task 8.3.

Deliverable 7.6, contributes towards these goals and to the success of SYLFEED
by creating a "Data Management Plan (DMP)", as per the Horizon 2020 Open
Research Data Pilot. The current deliverable contains two SYLFEED DataSets
(SDS) detailing the content of datasets used within SYLFEED, how it will be
preserved, and steps taken to make data publically available after the project
end. Additional SDS will be created as the project progresses.

This deliverable is set up by MATIS with the help of ARBIOM and both partners
will update and add to the DMP.

#  Deliverable report

SYLFEED Data Management Plan (DMP) under the H2020 Open Research Data Pilot.

#  Introduction

Over the course of a research project, considerable amounts of data are
gathered and generated. Often, these data are not preserved or made available
for reuse later on, causing time and effort to be spent in other projects
gathering similar data. The goal of the Horizon 2020 Open Research Data Pilot
is to remedy this issue, by ensuring that research data generated through a
project is made available for reuse after the project ends.

#  H2020 Open Research Data Pilot

The H2020 Open Research Data Pilot is based on the principle of making data
**FAIR** :

  * **Findable**

  

  * **Accessible**

  

  * **Interoperable**

  

  * **Reusable**

  

#  SYLFEED Data Management Plan

As a way of managing the data used during a project lifetime, a Data
Management Plan (DMP) must be created. The DMP-forms includes details on:

  * the handling of research data during and after the end of the project 

  

  * what data will be collected, processed and/or generated 

  

  * which methodology and standards will be applied 

  

  * whether data will be shared/made open access 

  

  * how data will be curated and preserved (including after the end of the project) 

  

  * ethical issues related to the data 

  

  * estimated costs associated with data archiving/sharing 

  

The creation of the DMP is included in deliverable 7.6 (D7.6). As per the DoA,
D7.6 will fulfill three requirements as a participant in the H2020 Open
Research Data Pilot:

  * "Firstly, the collected research data should be deposited in data repository (the SYLFEED project will use the Zenodo repository), 

  

  * Secondly, the project will have to take measures to enable third parties to access, mine, exploit, reproduce and disseminate this research data, 

  

  * Finally, a Data Management Plan (DMP) has to be developed detailing what kind of data the project is expected to generate, whether and how it will be exploited or made accessible for verification and reuse, and how it will be curated and preserved". 

  

Two types of data will be generated during the project:

  * _Raw data:_ This data will be stored on partners secured server and is not intended to be shared with the consortium. Partners ensure that the server capacity is adequate to store the data of SYLFEED project. 

  

  * _Consolidated data:_ This data will be shared within the consortium. It will be stored on Aymingsphere, the internal project website, further described below. In addition, consolidated data will be at least stored on the data’s owner secured server. 

  

The project data identified at this stage of the project, and that will be
generated during the project life have been compiled in a table ; this table
is confidential and is made available to the project partners on the project
collaborative platform Aymingsphere. This table will be regularly updated
during the project in order to include all new data that could be identified
at a later stage.

Data is classified by Work Package, and additional information regarding the
database where the data will be stored, and the author is mentioned.

#  The SYLFEED DataBase and DataSets

Currently the SYLFEED DataBase (SDB) includes several SYLFEED DataSets (SDS).
These can be found in the appendix at the end of this document. However,
during the later stages of the project and as the project progresses, relevant
SDS will be uploaded to the SDB. At or near the project end, datasets will be
uploaded from the SDB to OpenAire  ( _openaire.eu/_ )  or other relevant and
appropriate locations as agreed upon by the SYLFEED consortium.

A part of the SDB are two webpages; SYLFEED public page (  _www.sylfeed.eu_ )
and AYMINGSPHERE, the internal page for consortium communication.  
  
<table>  
<tr>  
<th>

**Name of database**

</th>  
<th>

SYLFEED website (WP7)

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

Data summary

</td>  
<td>

Sylfeed project website is functional since end of November 2017. It
highlights graphical elements such as logo, spiral, footer, and a common set
of colors. The objective of the website is to present SYLFEED project,
objectives, work packages, and inform interested parties about the latest news
of the project. All data displayed on the SYLFEED website is open to the
public. The website will be available throughout the lifetime of the project
at the current domain, www.sylfeed.eu, and the content of the website will be
available after the end of the project under the website of the coordinator,
ARBIOM, through web page redirect from current address.

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

Making data findable,

including provisions for metadata

</td>  
<td>

The data is available on the project website and is open source. All data can
be found through regular websearch and through a regular keyword search. Each
website post or page is labelled with relevant metadata for easier access.

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

Making data openly accessible

</td>  
<td>

All website data is open source, hosted within the WordPress Content
Management system (CMS)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and address by the consortium as a whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backed-up on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

N/A

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

**Name of database**

</th>  
<th>

Website for internal matters (AYMINGSPHERE / SharePoint; WP8)

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

Data summary

</td>  
<td>

AYMINGSPHERE ensures that partners have access to adequate resources,
monitoring and planning procedures for an efficient management of the whole
technological work carried out in the framework of the SYLFEED project.
Partners can exchange and share documents, participate in discussion forums…

The structure is organized as follows:

  * Project records: includes Communication documents, quality documents, management documents, meetings documents, 

  

  * Certified documents 

  

  * Steering tools: action list, roadmap, issues, decisions, risks 

  

  * Financial follow-up with subsections per partner - Work packages with a separate folder per WP. 

  

  * Useful links 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data on the AYMINGSPHERE website is for internal communication only and is not
available for the public, unless otherwised determined by the SYLFEED
consortium.

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

Making data openly accessible

</td>  
<td>

Data is not available for the public, unless otherwised determined by the
SYLFEED consortium.

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable by the consortium only, unless otherwised
determined by the SYLFEED consortium.

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

Allocation of resources

</td>  
<td>

N/A

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

Data Security

</td>  
<td>

Data is stored on a SharePoint Content Management System. Data reside on a
secure server and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

N/A

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

#  Conclusion

The Appendix describes the content of the different datasets, the ways in
which data will be stored and how/if it will be made available at the project
end. Due to the project being at an early stage, and because different work
packages are at a different time schedule, not all forms share the same level
of detail or same level of dissemination.

The DMP is intended to be a "living" document and will evolve as the project
progresses. Periodic revisions of the DMP are planned as described in the DoA.

Extra revisions might be scheduled should it be needed. The table on page 2 in
this document "Document history" provides a summary of revisions carried out
over the lifetime of this Data Management Plan. It provides a version number,
the date of the latest revision, the editor, and a comment describing the
change made.

#  Appendix: DataSets  
  
<table>  
<tr>  
<th>

**DataSet reference and name**

</th>  
<th>

Demo plant equipment specifications & data sheet (WP1)

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

DataSet summary

</td>  
<td>

  * Brochures 

  

  * Booklets 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Demo plant drawings (WP1)

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

DataSet summary

</td>  
<td>

  * Drawings 

  

  * Electronic documents 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Demo plant SOP (WP1)

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

DataSet summary

</td>  
<td>

  * Brochures 

  

  * Booklets 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Demo plant operational outputs (T, P, flow rate, conc, …) (WP1)

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

DataSet summary

</td>  
<td>

 Matrix of data

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Demo plant sourcing

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

DataSet summary

</td>  
<td>

  * Report 

  

  * LOIs 

  

  * Contract and other commercial documents 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential

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

Making data openly accessible

</td>  
<td>

Data is confidential

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and NSG.

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

**DataSet reference and name**

</th>  
<th>

Demo plant construction, commissioning and operation

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

DataSet summary

</td>  
<td>

 Reports

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and NSG.

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

**DataSet reference and name**

</th>  
<th>

Bioprocess data (WP2)

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

DataSet summary

</td>  
<td>

  * R&D Bioprocess Data, 

  

  * Reports on SCP production at small scale 

  

  * Reports on SCP production at small scale  Reports on optimisation of SCP production at small 

  

  * Reports on optimisation of SCP production at small 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and SPP.

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

**DataSet reference and name**

</th>  
<th>

Fish feed nutritional analysis (WP3)

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

DataSet summary

</td>  
<td>

  * Intermediary reports (3) on nutritional analysis, undesirable components and methods for optimization 

  

  * Final report on nutritional analysis, undesirable components and methods for optimization 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Matís
and Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Feed formulation (WP3)

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

DataSet summary

</td>  
<td>

 Report on feed formulation of commercial diets for carnivorous fish
(Atlantic salmon) and omnivorous fish (Tilapia)

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Matís
and Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Small & large scale feed production (WP3)

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

DataSet summary

</td>  
<td>

  * Report on production methods and quality parameters for small scale feed production 

  

  * Report on production methods and quality parameters fo large scale feed production 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Matís
and Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Small & large scale trials (WP3)

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

DataSet summary

</td>  
<td>

 Report on Small scale feeding trials describing test setup, fish’s growth
rate or deformations  Report on large scale feeding trials describing test
setup, fish’s growth rate or deformations

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Matís
and Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Feed formulation from C5 and lignin streams (WP4)

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

DataSet summary

</td>  
<td>

  * Intermediary report on lignin incorporation in fish feed formulation 

  

  * Final report on lignin incorporation in fish feed formulation 

  

  * Intermediary report on C5 fermentation into SCP and for C5 use in fish feed formulation 

  

  * Final report on C5 fermentation into SCP and for C5 use in fish feed formulation 

  

  * Intermediary report on lignin incorporation in fish feed formulation 

  

  * Final report on lignin incorporation in fish feed formulation 

  

  * Intermediary report on C5 fermentation into SCP and for C5 use in fish feed formulation 

  

  * Final report on C5 fermentation into SCP and for C5 use in fish feed formulation 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Matís
and Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Cost of ownership of SCP (WP5)

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

DataSet summary

</td>  
<td>

 Techno economic evaluation of the cost of goods and cost of operations.
calculations, market data

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Business cases (WP5)

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

DataSet summary

</td>  
<td>

  * Presentations 

  

  * Report 

  

  * Market analysis  Projections 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Report on LCA on production of proteins from lignocellulose based on ARBIOM’s
process (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

List of protein sources to be compared (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

Report on existing LCA for other protein sources (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

Report on LCA of other protein sources (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

Report on LCA for all protein sources (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

LCA data sets (WP6)

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

DataSet summary

</td>  
<td>

 Report

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is open access and is findable through research data repository.

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

Making data openly accessible

</td>  
<td>

Data is open access.

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom
and Ostfold.

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

**DataSet reference and name**

</th>  
<th>

Communiction/dissemination tools (WP7)

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

DataSet summary

</td>  
<td>

  * Brochures 

  

  * Posters 

  

  * Infographics including animations 

  

  * Videos 

  

  * Newsletters 

  

  * Press releases 

  

  * Social media accounts 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

The data is available on the project website and is open source. All data can
be found through regular websearch and through a regular keyword search. Each
website post or page is labelled with relevant metadata for easier access.

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

Making data openly accessible

</td>  
<td>

All website data is open source, hosted within the WordPress Content
Management system (CMS))

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

N/A

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

**DataSet reference and name**

</th>  
<th>

Registration of SCP (Single Cell Protein) (WP7)

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

DataSet summary

</td>  
<td>

 Document submitted to the EU to use our SCP as fish feed ingredient/
Authorisation from the

EU/FDA to use our product for feed applications

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Exploitation data (WP7)

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

DataSet summary

</td>  
<td>

  * Project business cases 

  

  * SCP based product competitive advantages  SYLFEED demonstration impact analysis  Update of business plans and identification of steps 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Meeting minutes & reports (WP8)

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

DataSet summary

</td>  
<td>

  * Minutes from all SYLFEED meetings 

  

  * Internal progress reports 

  

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Published data will be re-usable. Confidential data will be assessed on a case
by case basis upon official request, and addressed by the consortium as a
whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will stored on a secure server at Arbiom.

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

**DataSet reference and name**

</th>  
<th>

Quality & Risk Management Plan (WP8)

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

DataSet summary

</td>  
<td>

 reports

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

Making data findable,

including provisions for metadata

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data openly accessible

</td>  
<td>

Data is confidential, only for members of the consortium (including the
Commission Services)

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

Making data interoperable

</td>  
<td>

N/A

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

Increase data re-use

(through clarifying licences)

</td>  
<td>

Confidential data will be assessed on a case by case basis upon official
request, and addressed by the consortium as a whole.

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

Allocation of resources

</td>  
<td>

N/A

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

Data security

</td>  
<td>

Data reside on a secure server (SSL) and is backedup on a regularly basis.

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

Ethical aspects

</td>  
<td>

N/A

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

Other

</td>  
<td>

Upon completion of the project, data will be stored on a secure server at
Arbiom.

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