**Executive Summary**

This document describes the data the project will generate and how it will be
produced and analyzed. It also aims to detail how the data related to the
PortForward project will be disseminated and afterwards shared and preserved.

#  1 Introduction

This document introduces the second version of the project Data Management
Plan (DMP).

PortForward participates in the Open Research Data Pilot (ORD pilot), through
which the European Commission aims to improve and maximize access and reuse of
research data generated by Horizon 2020 projects. The ORD pilot considers the
need to balance openness and protection of scientific information,
commercialization and Intellectual Property Rights (IPR), privacy concerns,
security as well as data management and preservation questions.

The DMP describes the data management life cycle for the data to be collected,
processed and/or generated by the project. The PortForward DMP provides an
analysis of the main elements of the data management policy that will be used
by the consortium regarding all the datasets that will be generated by the
project. It ensures that the research data will be findable, accessible,
interoperable and re-usable (FAIR).

It also lists the different datasets that will be used, collected and
generated by the project, the main exploitation perspectives of these
datasets, and the major management principles the project will implement to
handle these.

The DMP is not a fixed but rather a living document that will evolve through
the lifespan of the project. This first version of the DMP includes an
overview of the datasets to be produced by the project and the specific
conditions that are attached to them. The DMP will cover the complete data
life cycle.

#  2 Data summary

All PortForward partners have identified the datasets that will be produced
during the different phases of the project. The following table provides a
summary of these datasets, including the associated WP and the name of the
partner responsible for each one.

**Table 1 Overview of PortForward datasets**  
  
<table>  
<tr>  
<th>

**Dataset No.**

</th>  
<th>

**Dataset Name**

</th>  
<th>

**Lead**

</th>  
<th>

**Associated**

**WP**

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

**1**

</td>  
<td>

User expectations and goals

</td>  
<td>

ACCIONA

</td>  
<td>

WP1

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

**2**

</td>  
<td>

Use case restrictions

</td>  
<td>

Vigo

</td>  
<td>

WP1

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

**3**

</td>  
<td>

Technical specifications

</td>  
<td>

IFF/ LEITAT

</td>  
<td>

WP1

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

**4**

</td>  
<td>

KPI catalogue

</td>  
<td>

MARTE

</td>  
<td>

WP1

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

**5**

</td>  
<td>

System architecture incl. existing port systems

</td>  
<td>

LEITAT

</td>  
<td>

WP2

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

**6**

</td>  
<td>

People and assets tracking data

</td>  
<td>

LEITAT

</td>  
<td>

WP4

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

**7**

</td>  
<td>

AR Remote assistance data

</td>  
<td>

UBIMAX

</td>  
<td>

WP4

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

**8**

</td>  
<td>

AR pilot assistance data

</td>  
<td>

UBIMAX

</td>  
<td>

WP4

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

**9**

</td>  
<td>

Stowage optimization data

</td>  
<td>

ACCIONA

</td>  
<td>

WP4

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

**Dataset No.**

</td>  
<td>

**Dataset Name**

</td>  
<td>

**Lead**

</td>  
<td>

**Associated**

**WP**

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

**10**

</td>  
<td>

Mafis working hours optimization

</td>  
<td>

ACCIONA

</td>  
<td>

WP4

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

**11**

</td>  
<td>

Sustainability assessment data

</td>  
<td>

LEITAT

</td>  
<td>

WP5

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

**12**

</td>  
<td>

Yard operations data

</td>  
<td>

BRUNEL

</td>  
<td>

WP5

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

**13**

</td>  
<td>

Digital twin (3D model, process and sensor data)

</td>  
<td>

IFF

</td>  
<td>

WP6

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

**14**

</td>  
<td>

Decision support system

</td>  
<td>

IFF

</td>  
<td>

WP6

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

**15**

</td>  
<td>

Stakeholder survey data

</td>  
<td>

MARTE

</td>  
<td>

WP7

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

**16**

</td>  
<td>

Use case implementation and evaluation data

</td>  
<td>

MARTE/ KRISTIANSAND

</td>  
<td>

WP7

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

**17**

</td>  
<td>

Standardization

</td>  
<td>

IFF

</td>  
<td>

WP8

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

**18**

</td>  
<td>

Technology scouting and technology watch data

</td>  
<td>

CORE

</td>  
<td>

WP8, WP9

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

**19**

</td>  
<td>

Market, competition and customer data

</td>  
<td>

MARTE

</td>  
<td>

WP8

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

**20**

</td>  
<td>

Business model canvas elements

</td>  
<td>

CORE

</td>  
<td>

WP8

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

**21**

</td>  
<td>

IPR catalogue

</td>  
<td>

CORE

</td>  
<td>

WP9

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

**22**

</td>  
<td>

IoT device/network communication and localization data

</td>  
<td>

IMEC

</td>  
<td>

WP3, WP4

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

In order to collect all relevant information for each dataset, the following
table was provided to the consortium partners. One table was generated for
each dataset. The topics addressed in the table include all relevant
information, such as dataset responsible partner, use of metadata, definition
of data formats, provisions for making the data FAIR, security and ethical
aspects. All the tables with the detailed information on each dataset are
provided in the annex of this deliverable.

**Table 2 Form for collection of information on each dataset**  
  
<table>  
<tr>  
<th>

DATASET NAME

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

Data Identification

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

Dataset description

</td>  
<td>

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

Source

</td>  
<td>

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

Partners activities and responsibilities

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

Partner owner of the data; copyright holder (if applicable)

</td>  
<td>

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

DATASET NAME

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

Partner in charge of data collection

</td>  
<td>

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

Partner in charge of data analysis

</td>  
<td>

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

Partner in charge of data storage

</td>  
<td>

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

Related WP(s) and task(s)

</td>  
<td>

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

Standards

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

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

Standards, format, estimated volume of data

</td>  
<td>

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

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

Data access policy / Dissemination level: confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

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

Embargo periods (if any)

</td>  
<td>

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

Legal framework(s) regulating or affecting in any way this dataset. How is
this addressed?

</td>  
<td>

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

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

Archiving and preservation (including storage and backup)

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

Data storage (including backup): Where? For how long?

</td>  
<td>

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

#  3 FAIR data

PortForward aims at generating FAIR data, i.e. data that is findable,
accessible, interoperable and reusable.

###  3.1 Making data findable, including provisions for metadata

In order to make data findable, metadata will be used. All partners have
agreed in providing relevant metadata and keywords, so that their data will be
easily discoverable. Clear version numbers will be included (automated process
through the project repository) and standard naming conventions will be
defined.

###  3.2 Making data openly accessible

The consortium partners already identified which data will be made openly
available and which cannot be shared (or need to be shared under restriction),
including the reason why access is restricted in the latter case.

In the next DMP versions, more details will be provided regarding the
accessibility of the data. Details on the repository, the methods and tools
necessary to access the data will be included in future versions of the DMP.
The consortium aims at using the project website (or other easily accessible
repositories) as repository for open accessible (public) data, ensuring easy
access to anyone interested.

###  3.3 Making data interoperable

Provisions are also taken to make data interoperable, making it easier to
exchange and re-use them across research institutions, organisations, etc.
This could be more difficult for project-specific technical datasets, but the
project strives in making all open data interoperable. Interoperability for
technical data is also addressed in WP2, T2.3 “Interoperability & data
modelling”. The goal of this task is to define a generic model of data
curation.

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

Information regarding the reusability of the data will be provided for each
dataset separately. The consortium partners provided relevant information on
embargo periods and the intended period that their data will remain reusable.

#  4 Allocation of resources

Costs for making the project data FAIR are eligible as part of the Horizon
2020 grant. At this current stage, no such costs are foreseeable. In the
future DMP versions this chapter will be updated and include costs for long-
term preservation of data (after the project end).

#  5 Data security

During the implementation of the PortForward project, the consortium members
will collect data in various forms, e.g. pen and paper, photos, videos,
electronic documents. For the purpose of the project documentation, each
partner will store this data individually. For this, the respective
organizational rules and regulations of each partner with respect to data
storage and security apply.

For the cooperation between partners in the consortium, the coordinator
Fraunhofer Gesellschaft established a dedicated document management platform,
based on OpenText Content Server. Data relevant to multiple partners will be
stored and retained on this infrastructure. The content server infrastructure
underlies the data protection responsibilities of the Fraunhofer Gesellschaft.

Storing of personal data will only occur with explicit prior informed consent
of subjects, based on the informed consent procedures as laid out in D11.1.

#  6 Ethical aspects

Regarding the ethical and legal issues impacting data sharing, certain
provisions have already been implemented in the project ethics work package
(WP11). D11.1 provides information on the stakeholder involvement, selection
and recruitment as well as the informed consent procedure. In D11.2,
information on the compliance of the consortium towards the collection of
personal data and their handling over the life cycle of the project is
provided.

#  7 Next steps

The PortForward partners in a yearly basis will update the DMP. The next
versions of the DMP will be delivered on December 2020 (D9.7) and December
2021 (D9.8). All deliverables are considered public and will be uploaded on
the project’s website after being officially approved.