#  1\. Introduction

This document is developed as part of MARISA (MARitime Integrated Surveillance
Awareness) project, which has received funding from the European Union’s
Horizon 2020 Research and Innovation program, under the Grant Agreement number
740698.

The Project Management, Quality and Risk Plan corresponds to Deliverable 1.1
of Work Package 1 (WP1) – Project Management & Coordination. WP1 will ensure
an optimal coordination and management of MARISA Project, guaranteeing the
effective implementation of the project activities in respect of technical
progress, finance, contracts and administration. The specific objectives of
WP1 include:

  * create the effective management structure on the basis of the principles included in the Grant and Consortium Agreements, for the whole duration of the project (committees, quality plans, procedures, risk register, project management tools, etc.); 

  

  * ensure that the procedures are followed and changed if required during the project lifetime in order to ensure successful completion of tasks, deliverables and achievement of the milestones; 

  

  * oversee the progress of work packages, monitor deliverables, and resolve any risks and unforeseen issues; 

  

  * maintain contacts with the European Commission; 

  

  * chair the Executive Board, Technical Board and the Advisory Board; 

  

  * manage the innovation in MARISA ensuring the coherence between technology and exploitation dimensions. 

  

##  1.1. Purpose of the document

The D1.1 Project Management, Quality and Risk Plan provides an organized and
harmonized set of practical guidelines, procedures and support documents that
shall be used for optimizing the project implementation. It will be kept up to
date as needed throughout the project lifecycle.

This document is to be used by all partners to efficiently develop their
individual and collective activities and contribute to the global objective of
the project.

##  1.2. Reference documents

[GA] Grant Agreement-740698-MARISA.pdf

The Grant Agreement is the contract concluded between the EC (representing the
EU) and the beneficiaries under which the parties receive the rights and
obligations (e.g. the right of the Union's financial contribution and the
obligation to carry out the research and development work). The Grant
Agreement consists of the basic text and annexes, including Annex 1–
Description of the action (DoA) - part A and part B.

The DoA (Annex 1 part A) is also a key document to be taken into account given
that it compiles a specific description of the tasks that will be carried out
along the project and the expected results, deliverables and milestones to be
obtained.

This D1.1 Project Management, Quality and Risk Plan is a supporting document
to the [GA] and the DoA (Annex 1 part A) and contains extracts from both the
documents where appropriate to ensure a full definition of the management
processes and procedures to ensure that the project is delivered successfully.

[CA] Consortium Agreement

The Consortium Agreement is the internal agreement signed between the members
of the consortium establishing their rights and obligations with respect to
the implementation of the action in compliance with the grant agreement.

This D1.1 Project Management, Quality and Risk Plan is a supporting document
to the [CA] intended to provide more detailed processes and procedures to
ensure that the project is delivered successfully.

##  1.3. Applicability

The D1.1 Project Management, Quality and Risk Plan is a reference document in
the MARISA project.

From the start of the project to its end, it is applicable to all partners,
and is expected to remain stable. However, any changes will be agreed by the
Executive Board (EB) and included in a revised version.

In the unlikely event of a conflict between the D1.1 Project Management,
Quality and Risk Plan and other documents such as the Description of Work or
the Grant Agreement, they will prevail in the following order:

  1. [GA] Grant Agreement including all Annexes; 

  

  2. [CA] Consortium Agreement; 

  

  3. [D1.1] D1.1 Project Management, Quality and Risk Plan (this Document). 

  

  

The latter documents will have to be modified to remain consistent with the
former. This is especially mandatory for issues regulated by either the [GA]
or [CA] documents.

##  1.4. Definitions

In the following table, in order to clarify some concept tied to certain words
used in the document, some overall definitions have been reported.  
  
<table>  
<tr>  
<th>

</th>  
<th>

**DEFINITIONS**

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

EUCISE2020

</td>  
<td>

EUropean test bed for the maritime Common Information Sharing Environment in
the 2020 perspective. EUCISE2020 is a Security Research project of the
European Seventh Framework Program; it aims at achieving the pre-operational
Information Sharing between the maritime authorities of the European States.

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

**DEFINITIONS**

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

CISE

</td>  
<td>

CISE is the Common Information Sharing Environment for the Maritime Domain. It
will integrate existing surveillance systems and networks and give to all the
relevant authorities (EU and national authorities responsible for different
aspects of surveillance) concerned access to the information they need for
their missions at sea. The CISE will make different systems interoperable so
that data and other information can be exchanged easily through the use of
modern technologies.

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

MARISA

Toolkit

</td>  
<td>

In order to fostering faster detection of new events, better informed decision
making and achievement of a joint understanding of a situation across borders,
the MARISA toolkit it will be able to provide a suite of services to correlate
and fuse various heterogeneous and homogeneous data and information from
different sources, including Internet and social networks.

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

Data Fusion

</td>  
<td>

The process of integrating multiple data sources to produce more consistent,
accurate, and useful information than that provided by any individual data
source. Is analogous to the ongoing cognitive process used by humans to
integrate data continually from their senses to make inferences about the
external world.

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

Legacy Systems

</td>  
<td>

The previously existing Maritime Surveillance systems in the National/Regional
Coordination Centers or Coastal Stations to which MARISA Toolkit must
establish some kind of communications.

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

Maritime

Surveillance

</td>  
<td>

The set of activities aimed to understand, prevent wherever applicable and
manage in a comprehensive way all the events and actions relative to the
maritime domain which could impact the areas of maritime safety and security,
law enforcement, defense, border control, protection of the maritime
environment, fisheries control, trade and economic interest of the EU.

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

Table 1: Definitions

##  1.5. Structure of the document

The document is structured as follows:

  * Chapter 1 **Introduction** : it gives an introduction to the overall documents providing also useful information about the applicability of the present document. 

  

  * Chapter 2 **System Overview** : in this chapter an overview of the MARISA system that will be implemented as objective of the project. 

  

  * Chapter 3 **Project Organization** : this chapter presents the project management structure and the associated roles. 

  

  * Chapter 4 **Project Control and Monitoring** : in this chapter processes set up for scheduling and schedule control, management of reviews and meetings, collaboration tools, are described. 

  

  * Chapter 5 **Configuration Management** : this chapter presents the project rules for configuration management, data management. 

  

  * Chapter 6 **Quality Plan** : it presents the quality control aspects. 

  

  * Chapter 7 **Risk Management Plan** : in this chapter it is presented the risks and the opportunities management rules. 

  

#  2\. System Overview

One of the main MARISA objective is to foster faster detection of new events,
better informed decision making and achievement of a joint understanding of a
situation across borders and allowing seamless cooperation between operating
authorities and on-site / at sea / in air intervention forces.

The proposed solution is a toolkit that provides a suite of services to
correlate and fuse various heterogeneous and homogeneous data and information
from different sources, including Internet and social networks. MARISA also
aims to build on the huge opportunity that comes from using the open access to
“big data” for maritime surveillance: the availability of large to very large
amounts of data, acquired from various sources ranging from sensors,
satellites, open source, internal sources and of extracting from these amounts
through advanced correlation improves knowledge.

The MARISA toolkit provides new means for the exploitation of the bulky
information silos data, leveraging on the fusion of heterogeneous sector data
and taking benefit of a seamless semantic interoperability with the existing
legacy solutions available across Europe.

In this regard the CISE data model and the EUCISE2020 services will be
exploited, combining with the expertise of consortium members in creating
security intelligence knowledge from a wide variety of sources.

#  3\. Project Organization

##  3.1. Consortium Members  
  
<table>  
<tr>  
<th>

**No.**

</th>  
<th>

**Participant Organization Name**

</th>  
<th>

**Country**

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

**1**

</td>  
<td>

Leonardo S.p.A. (LDO)

</td>  
<td>

IT

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

**2**

</td>  
<td>

Engineering Ingegneria Informatica S.p.A. (ENG)

</td>  
<td>

IT

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

**3**

</td>  
<td>

GMV Aerospace & Defence S.A.U. (GMV)

</td>  
<td>

ES

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

**4**

</td>  
<td>

Airbus Defence and Space SAS (ADS)

</td>  
<td>

FR

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

**5**

</td>  
<td>

e-GEOS S.p.A (EG)

</td>  
<td>

IT

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

**6**

</td>  
<td>

PLATH GmbH (PLA)

</td>  
<td>

DE

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

**7**

</td>  
<td>

SATWAYS - Proionta Kai Ypiresies Tilematikis Diktyakon Kai Tilepikinoniakon
Efarmogon Etairia Periorismenis Efthinis Epe (STW)

</td>  
<td>

GR

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

**8**

</td>  
<td>

Inovaworks II Command and Control (IW)

</td>  
<td>

PT

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

**9**

</td>  
<td>

Aster S.p.A. (AST)

</td>  
<td>

IT

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

**10**

</td>  
<td>

Luciad NV (LUC)

</td>  
<td>

BE

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

**11**

</td>  
<td>

INOV Inesc Inovação (INOV)

</td>  
<td>

PT

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

**12**

</td>  
<td>

Nederlandse Organisatie voor toegepast-natuurwetenschappelijk onderzoek (TNO)

</td>  
<td>

NL

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

**13**

</td>  
<td>

Fraunhofer Gesellschaft zur Förderung der angewandten Forschung e.V. (IOSB)

</td>  
<td>

DE

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

**14**

</td>  
<td>

NATO STO – Centre for Maritime Research and Experimentation (CMRE)

</td>  
<td>

BE

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

**15**

</td>  
<td>

Toulon Var Technologies (PMM)

</td>  
<td>

FR

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

**16**

</td>  
<td>

Laurea University of Applied Sciences (LAU)

</td>  
<td>

FI

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

**17**

</td>  
<td>

Alma Mater Studiorum University of Bologna (UNIBO)

</td>  
<td>

IT

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

**18**

</td>  
<td>

Ministry of National Defence Greece (HMOD)

</td>  
<td>

GR

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

**19**

</td>  
<td>

Netherlands Coastguard (NCG)

</td>  
<td>

NL

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

**20**

</td>  
<td>

Guardia Civil (GUCI)

</td>  
<td>

ES

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

**21**

</td>  
<td>

Italian Navy (ITN)

</td>  
<td>

IT

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

**22**

</td>  
<td>

Portuguese Navy (PN)

</td>  
<td>

PT

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

Table 3: MARISA Consortium

##  3.2. Management Structure

Although MARISA is a project with a large number of partners, we have opted
for a lean and mean organization since the majority of the partners have
already worked closely together in other successful EU funded projects and
joint research activities. An overview of the proposed organisational
structure is given and shown in the Figure 1\.

Figure 1: MARISA Organization Chart

##  3.3. Project Bodies and Main Roles

###  3.3.1. Project Management and Coordination

The Project Coordinator (PC) [Francesco Cazzato, LDO], is the operative
coordinator of the project and the intermediary between the consortium and the
European Commission; PC coordinates Executive Board (EB) and Technical Board
(TB) and the Advisory Board (AB). PC is responsible for the overall
contractual, ethical, financial and administrative management of the project.
This includes also the supervision of the technical activities of the work
package leaders (WPLs). The PC is the sole contact person for the project with
the EC and will ensure the punctual delivery of reports and deliverables; the
liaison with the EndUsers/Advisory Board and with the partners; the chair of
the EB and of the TB. He promotes the participation of female researchers in
the project, approves all publications and deliverables.

The Project Manager (PM), [Valeria Fontana, LDO], with related experience in
managing research project, supports the PC and EB with the following tasks:

  * prepares the meeting agendas, organizes locations, schedules, and all activities related to helping the PC with the organization of the project; 

  

  * monitors deadlines on time and budget and issues early warnings in case certain limits are reached; 

  

  * monitors of all the deliverables and reports quality aspects; 

  

  * provide appropriate reporting and addressing questions, problems, issues to be solved inside the EB meetings; 

  

  * manage the risk plan. 

  

The Financial Officer (FO), [Alessandro Ambrosetti, LDO], supports the PC and
EB with the following tasks:

  * distributes the payments received from the Commission to the Partners, according to the rules defined in the [GA] and [CA]; 

  

  * receives the Partners’ reports on the person efforts and expenditures related to each six-month period; 

  

  * support to the Project coordinator for any amendment may occur to the [GA] and [CA]; 

  

  * produces and monitors the Annual Financial Statements. 

  

###  3.3.2. Executive Board

Executive Board (EB): is the decision making body and has the highest level of
authority in the project. The EB is chaired by the Project Coordinator. The EB
can authorize the PC to defer to the Commission for specific decisions in case
a specific question cannot be resolved internally. Decisions within the EB
will be taken ideally by consensus, but if necessary, by a two-thirds majority
vote. In general, the EB meets in person at least once every six months. In
addition to face-to-face meetings, the EB may hold teleconference meetings to
discuss project progress and to make decisions and take action where
appropriate. Specific tasks of the EB are:

  * Being responsible for all the aspects of the project, including to review progress against the defined deliverables and timetables and propose corrective actions whenever necessary; 

  

  * Deciding upon the eventual reallocation of the projects’ budget by WPs and reviewing and proposing to the contractors budget transfers to include in the project plan. 

  

  * Making proposals to the partners for the review and/or amendment of the terms of the [GA] and/or the [CA]. 

  

  * Deciding upon major changes in work, particularly termination, creation, or reallocation of activities. 

  

  * Deciding to suspend all or part of the project or to terminate all or part of the partners, or to request the Commission to terminate the participation of one or more partners. 

  

  * Deciding upon the entering into the [GA] and the [CA] of new partners. 

  

  * Agreeing procedures and policies in accordance with the Commission contractual rules, for the knowledge and Intellectual Property Rights (IPR) management. 

  

###  3.3.3. Technical Board

The Technical Board (TB) is the technical body which has technical authority
in the project; it is chaired by the Project Coordinator (PC) and it is
composed by the Innovation Manager (IM) and WP Leaders (WPLs). The TB supports
the PC and the Executive Board (EB) in the following tasks:

  * guarantees that the engineering tasks are carried out on schedule and in accordance with the tasks and functions determined by the [GA]; 

  

  * understand the plan and scope of the project by developing the technical breakdown structure, schedule and workflow diagrams, resource requirements, and constraints; 

  

  * define interfaces as for instance understanding potential incompatibilities across project components; 

  

  * control the configuration, help in milestone review and assessment; 

  

  * understand biases, assumptions and other technical details that affect the results; 

  

  * place any data regarding the user’s expectations, requirements, design, etc. under version control. 

  

###  3.3.4. User Community

The MARISA development methodology relies on the User Community that will
include “end user practitioners”, partners, associates, maritime surveillance
experts to explore and exploit the human capital in Member States and their
institutions identifying operational needs, operational scenarios, existing
gaps, acceptability issues and societal impacts that the proposed solutions
may entail. The design of MARISA therefore integrates the users’ experience
and design-development related R&D, trust building and cocreativity in a
collective-authentic manner.

The User Community will also provide guidance to the partners and enable
interactions in the consortium for the implementation of the data fusion
technologies. The current composition of the MARISA User

Community comprehends all the partners including the “end users practitioners”
that have joined MARISA as full partners: Italian Navy, Guardia Civil,
Netherlands Coast guard, Hellenic MoD and Portuguese Navy.

Moreover, the User Community also includes the associated partners that have
already expressed interest and support to the objectives of the project.
However the consortium is always open to accept other members during the
execution of the project.

###  3.3.5. Advisory Board

The MARISA Consortium has also foreseen an Advisory Board (AB). This
additional body meets three times throughout the project (M10, M20 and M30)
and consists of selected European and International organisations not directly
involved in the project as full partners. The AB supports and advises project
partners with experience and know-how throughout the project duration. Their
valuable feedback to the strategic and technical process of the project brings
many benefits for the MARISA project. Members of the AB will provide an
external view. The AB will advise on strategic directions of the project in
terms of detailed technical goals and impact, standardisation, ethical and
societal issues. To achieve high quality results within the MARISA project, a
strong cooperation with the AB members will actively be pursued and
facilitated by frequent interaction.

The current composition of the Advisory Board is reported in Table 4:  
  
<table>  
<tr>  
<th>

**Nation**

</th>  
<th>

**Org. Name/Dep.**

</th>  
<th>

**Member of the Advisory Board**

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

**FI**

</td>  
<td>

Finnish Border Guard

</td>  
<td>

_Commander Ari Laaksonen_

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

**IT**

</td>  
<td>

Italian Ministry of Interior - Dipartimento della Pubblica Sicurezza –
Direzione Centrale dell’Immigrazione e della Polizia delle Frontiere

</td>  
<td>

_Dott.ssa Rosa Maria Preteroti_

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

**SP**

</td>  
<td>

Qi Europe - Security and Defence

</td>  
<td>

_Javier Warleta Alcina_

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

**MA-USA**

</td>  
<td>

Massachusetts Institute of Technology

</td>  
<td>

_Pierre F.J. Lermusiaux_

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

**IT**

</td>  
<td>

Italian Space Agency - Maritime Surveillance Projects

</td>  
<td>

_Dott.ssa Carolina Matarazzi_

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

**NO**

</td>  
<td>

Peace Research Institute Oslo

</td>  
<td>

_Maria Gabrielsen Jumbert_

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

**FR**

</td>  
<td>

État-Major de la Marine - ICT systems in

CEPN

</td>  
<td>

_Captain of Frigate Benoit Stephan_

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

**IT**

</td>  
<td>

Leonardo S.p.A

</td>  
<td>

_Andrea Biraghi_

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

Table 4: MARISA Advisory Board

###  3.3.6. Security Board

Security Advisory Board (SAB) will review all potential EU classified
information, throughout the project life, coordinated by the MARISA Project
Security Officer and report at the Executive Board meetings.

The Security Advisory Board consists of representatives from the Consortium as
reported in the Table 5:  
  
<table>  
<tr>  
<th>

**Nation**

</th>  
<th>

**Org. Name**

</th>  
<th>

**Project Security Officer**

</th>  
<th>

**E-Mail**

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

**IT**

</td>  
<td>

LDO

</td>  
<td>

_Francesco Moliterni_

</td>  
<td>

francesco.moliterni@leonardocompany.com

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

**Nation**

</td>  
<td>

**Org. Name**

</td>  
<td>

**Member of the AB**

</td>  
<td>

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

**IT**

</td>  
<td>

ENG

</td>  
<td>

_Fabio Barba_

</td>  
<td>

fabio.barba@eng.it

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

**ES**

</td>  
<td>

GMV

</td>  
<td>

_Oscar Pablo Tejedor Zorita_

</td>  
<td>

otejedor@gmv.com

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

**FR**

</td>  
<td>

ADS

</td>  
<td>

_Philippe Chrobocinski_

</td>  
<td>

philippe.chrobocinski@airbus.com

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

**GR**

</td>  
<td>

STW

</td>  
<td>

_Antonis Kostaridis_

</td>  
<td>

a.kostaridis@satways.net

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

**BE**

</td>  
<td>

CMRE

</td>  
<td>

_Amleto Gabellone_

</td>  
<td>

amleto.gabellone@cmre.nato.int

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

**ES**

</td>  
<td>

GUCI

</td>  
<td>

_Luis Antonio Santiago Marín_

</td>  
<td>

luissantiago@guardiacivil.es

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

**ES**

</td>  
<td>

GUCI

</td>  
<td>

_Carlos Díaz Martín_

</td>  
<td>

carlosdiazm@guardiacivil.es

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

Table 5: MARISA Security Advisory Board

All the SAB representatives have wide experience in handling security issues.
As detailed in the summary CVs (reported in [GA]), many of them have acted as
Project Security Officer in a number of H2020 projects or are responsible of
Security Management in the respective companies.

###  3.3.7. Other Project Roles

The **Innovation Manager** (IM), [Véronique Pevtschin, ENG] ensures the
coordination of all activities connected to technology alignment to user
needs, technology transfer, management of innovation, including IPR, detection
of market opportunities and channels. IM supports the PC and the EB in
aligning innovation to user needs, in fostering the exploitation of innovation
and in connecting with other suppliers to promote the openness of the
approach. In 4.4, it is reported a more detailed explanation about how the
Innovation Management will be carried out in MARISA.

The **Ethics Manager** (EM), [Sari Sarlio-Siintola, LAU], with an extensive
expertise for the ethics work, a) identifies and analyses ethical and societal
framework; b) monitors the ethical concerns in the project, b) ensures that
the project will comply with the Research Ethics taking all relevant
international ethical aspects into consideration, prior to the execution of
the operational trials, c) translates and implements the ethical requirements
to the various deliverables in the project, d) provides advice on assessments
on ethics in the ethical and societal reports, e) facilitates collaboration
with all the project actors.

The **Communication Manager** (CM), [Eric den Breejen, TNO] ensures the
quality and execution of the communication (and dissemination) plan of the
project. CM supports the PC and EB with the following tasks: a) preparation of
the communication and dissemination plan for activities in relation to the
general media in conjunction with the innovation manager for the specifics of
industrial dissemination; b) Monitoring of media and other means of
dissemination for the duration of the project; c) definition and review of
dissemination material.

The **User Community Leader** (UCL), [Rauno Pirinen, LAU] with vast experience
in applying user-driven methodology in the definition of user needs, design
and validation of information systems, leads and animates the User Community.

#  4\. Project Control and Monitoring

##  4.1. Work Breakdown Structure

The project’s organisation regarding the overall work spread and allocation is
based on a systematic approach: everything produced throughout and by the
project corresponds with a Work Package task. The work division will therefore
be articulated on a two level basis:

  * Level 1: Work Packages that gather group of single tasks, all with the same assigned objective. Each Work Package carries out its tasks, has autonomous control over internal issues and delivers research and development results in accordance with the Project Work Programme and within the allocated budget. 

  

  * Level 2: Single Tasks, embedded within the Work Packages, which are linked to a sole and defined action, like the production of a Deliverable. 

  

  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**TITLE**

</th>  
<th>

**BRIEF DESCRIPTION**

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

**WP1**

</td>  
<td>

**Project Management & Coordination **

</td>  
<td>

Overall management and coordination on the project in respect of technical
progress, finance, contracts and administration.

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

T1.1

</td>  
<td>

Project Coordination

</td>  
<td>

Coordination of the overall administration and finances of the project.

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

T1.2

</td>  
<td>

Project Management, Quality Control and Risk Management

</td>  
<td>

Day-to-day planning and work supporting the Project Coordination during the
entire lifecycle of the project.

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

T1.3

</td>  
<td>

Innovation Management

</td>  
<td>

Innovation management of MARISA reflects the strategy of MARISA deliver
technology aligned to market needs, European strategies and operational
contexts.

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

T1.4

</td>  
<td>

Ethics Management

</td>  
<td>

Guidance and steering on legal, ethical and societal issues of the proposed
MARISA solution.

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

**WP2**

</td>  
<td>

**User Needs and Operational Scenarios**

</td>  
<td>

Animation of the MARISA User Community to foster pro-active involvement of
stakeholders following a user-centric approach in the MARISA design and
validation.

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

T2.1

</td>  
<td>

User community animation

</td>  
<td>

Animation of the MARISA User Community focused on the goal of “innovation”,
delivering the benefits of data fusion to maritime surveillance through the
MARISA toolkit of services.

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

T2.2

</td>  
<td>

Addressing user needs through MARISA services

</td>  
<td>

This task will build on results of previous R&D and cooperative projects and
the input of the users’ community to elaborate the relevant requirements of
data fusion functionalities, the organisation of these functionalities into
actionable services.

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

T2.3

</td>  
<td>

Adoption model for MARISA

</td>  
<td>

The adoption path will be applied to drive the incremental alignment of the
innovative services to the user needs and evaluate the implementations with
respect to the needs.

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

T2.4

</td>  
<td>

Interaction with Existing/Legacy

Systems and the CISE environment

</td>  
<td>

This task focuses on identifying the legacy systems which MARISA will interact
with, during the project trials but also beyond, to address their capabilities
to exchange data and required agreements.

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

T2.5

</td>  
<td>

Innovative use of additional data sources

</td>  
<td>

This task focus on designing a MARISA toolkit that can easily integrate new
data sources and support new services beyond the MARISA project community and
duration.

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

**#**

</th>  
<th>

**TITLE**

</th>  
<th>

**BRIEF DESCRIPTION**

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

T2.6

</td>  
<td>

Legal and Ethical Context Analysis

</td>  
<td>

This task starts at the very beginning of the project by identifying and
analysing legal and ethical regulation framework in which MARISA operates
linked to the MARISA functionalities for data fusion.

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

T2.7

</td>  
<td>

Operational Scenarios & Trials Definition

</td>  
<td>

In this task, the implementation and trial results will be traced back to
initial requirements, according to the two-phase approach of the work plan.

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

**WP3**

</td>  
<td>

**MARISA Toolkit Design**

</td>  
<td>

Delivery of the high level architecture of the MARISA Toolkit and the
associated services based on requirements and scenarios previously defined.

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

T3.1

</td>  
<td>

Overall Toolkit Design

</td>  
<td>

Definition of the MARISA Toolkit main building blocks and interfaces among
them; identification of services producers and consumers and main system
components (internal and external, including legacy systems).

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

T3.2

</td>  
<td>

Data Fusion Module and resulting services

</td>  
<td>

Definition of the data fusion module architecture including the identification
of the resulting services which shall be classified.

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

T3.3

</td>  
<td>

External and internal Interfaces and gateways design

</td>  
<td>

Based on the services behaviour, the required capabilities and the flow of
information previously defined, the external and internal interfaces shall be
identified.

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

T3.4

</td>  
<td>

Data models definition

</td>  
<td>

Elaboration of a common data model for data exchange.

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

T3.5

</td>  
<td>

User interactions (HCI)

</td>  
<td>

Development of human-computer-interface modules.

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

**WP4**

</td>  
<td>

**Data analysis and fusion**

</td>  
<td>

Identification of all the Data Fusion computing capabilities of Marisa Toolkit
providing methods and algorithms to extract value added information from the
available external data sources.

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

T4.1

</td>  
<td>

Data Fusion Level 1 products

</td>  
<td>

This task addresses the aspect of “Observation of elements in the environment”
to provide a more accurate awareness of objects in the maritime environment.

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

T4.2

</td>  
<td>

Data Fusion Level 2 products

</td>  
<td>

This task addresses the aspect of “Comprehension of the current situation” to
provide useful information among the relationships of level 1 objects in the
maritime environment.

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

T4.3

</td>  
<td>

Data Fusion Level 3 products

</td>  
<td>

This task addresses the aspect of “Projection of future states”, to predict
the evolution of a maritime situation, in support of rapid decision making and
action.

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

**WP5**

</td>  
<td>

**Supporting capabilities and infrastructure**

</td>  
<td>

Definition and development of the supporting infrastructure for the MARISA
toolkit.

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

T5.1

</td>  
<td>

Big Data Infrastructure set-up

</td>  
<td>

Definition, implementation and set-up of a scalable Big Data management and
analysis infrastructure with the aim to support and integrate the analysis,
fusion, and analytics modules.

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

T5.2

</td>  
<td>

Interfaces to external data sources (include gateways)

</td>  
<td>

Implementation of the adapter modules and gateways for the integration of the
required external data sources and legacy Systems.

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

T5.3

</td>  
<td>

User interactions

</td>  
<td>

Implementation of the front-end components of the toolkit.

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

T5.4

</td>  
<td>

Data fusion distribution services

</td>  
<td>

A set of system-to-system interfaces will be made available to be used by the
end user operational systems or other external systems.

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

T5.5

</td>  
<td>

Information and Assurance services

</td>  
<td>

Implementation of the identity and access management services providing MARISA
toolkit the capability to identify (authentication) and grant and access
privileges (authorization) to all users, systems and devices connecting to
MARISA.

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

**WP6**

</td>  
<td>

**MARISA Toolkit integration and validation**

</td>  
<td>

Integration of the various components of the system and test and validation of
the configurations to provide WP7 with qualified systems to support the
trials.

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

**#**

</th>  
<th>

**TITLE**

</th>  
<th>

**BRIEF DESCRIPTION**

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

T6.1

</td>  
<td>

General principles of test architecture and data integration

</td>  
<td>

Definition of the generic principles of the test architecture based on
specifications provided by users or developers of the tools and components
that will be used.

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

T6.2

</td>  
<td>

Definition and implementation of integration platforms

</td>  
<td>

Definition and implementation of integration platforms (at PMM premises), able
to test all components in different configurations and interfaces to local
legacy systems.

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

T6.3

</td>  
<td>

Definition of system configurations for each trial

</td>  
<td>

The outcome of the task will be the definition files of each campaign
configuration, the definition of the data sets needed for each campaign and
the test files that shall be used to validate each configuration.

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

T6.4

</td>  
<td>

Factory integration of campaign configurations

</td>  
<td>

The task will integrate all components developed in WP4 and WP5 into the whole
chain, physically in a first step and functionally in a second step. The
system configurations will be qualified through the test files and validated
on the basis of the specifications prepared in WP2 and WP3.

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

T6.5

</td>  
<td>

Validation of campaign configurations with simulation/emulation tools

</td>  
<td>

Factory scenarios will be defined to test and validate the MARISA toolkit in
the different trial configurations, with the aim to provide validated
configurations for the trials execution.

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

**WP7**

</td>  
<td>

**Verification in Operational Trials**

</td>  
<td>

Definition of the overall approach to be applied to the operational trials,
execution of the operational trials, collection and analysis of trial results.

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

T7.1

</td>  
<td>

Operational Trials Approach

</td>  
<td>

This task will define the approach and plans to operational trials to be
conducted in Phase 1 and Phase 2 considering the preparatory work performed by
the User Community in WP2.

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

T7.2

</td>  
<td>

Iberian Trial

</td>  
<td>

This task includes activities for the detailed organization, logistics,
setting-up and execution of the Iberian Trial.

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

T7.3

</td>  
<td>

Northern Sea Trial

</td>  
<td>

This task includes activities for the detailed organization, logistics,
setting-up and execution of the North Sea Trial.

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

T7.4

</td>  
<td>

Ionian Trial

</td>  
<td>

This task includes activities for the detailed organization, logistics,
setting-up and execution of the Ionian Sea trial.

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

T7.5

</td>  
<td>

Aegean Trial

</td>  
<td>

This task include activities for the detailed organization, logistics,
setting-up and execution of the Aegean Sea Trial.

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

T7.6

</td>  
<td>

Strait of Bonifacio Trial

</td>  
<td>

This task include activities for the detailed organization, logistics,
setting-up and execution of the Strait of Bonifacio Trial.

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

T7.7

</td>  
<td>

Verification Results Consolidation

</td>  
<td>

This task will a) assess the results of each trial against the objective, b)
verify the KPIs defined in Section 1.2, c) provide recommendations and define
a roadmap for the subsequent project phases.

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

**WP8**

</td>  
<td>

**Dissemination and Exploitation**

</td>  
<td>

Dissemination, exploitation and standardization activities of the MARISA
project.

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

T8.1

</td>  
<td>

Communication and Dissemination Strategy and Plan

</td>  
<td>

This task defines the complete communication and dissemination strategy for
the MARISA project ensuring that the appropriate MARISA results are conveyed
to the right audience in the right time.

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

T8.2

</td>  
<td>

MARISA Web Site and dissemination materials

</td>  
<td>

The MARISA web site will be set-up and maintained. Official MARISA project
leaflets, brochures, posters, videos and workshops material will be prepared
in this task.

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

T8.3

</td>  
<td>

MARISA Workshops

Coordination

</td>  
<td>

This task will be dedicated to the preparation, organisation, management and
coordination of 3 workshops to present and promote the MARISA results to the
MARISA Consortium partners, end-users, user community and other relevant
stakeholders.

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

T8.4

</td>  
<td>

MARISA Training toolkit support

</td>  
<td>

This task delivers the training material in a format adapted to users to
support them through trials in phase 1 and in phase 2.

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

**#**

</td>  
<td>

**TITLE**

</td>  
<td>

**BRIEF DESCRIPTION**

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

T8.5

</td>  
<td>

IPR Management and Exploitation plan

</td>  
<td>

This task focuses on creating and refining business models, supported by
adoption paths and including proposed IPR models, oriented both to existing
partners and external organisations interested in delivering new data fusion
services through the MARISA toolkit.

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

T8.6

</td>  
<td>

Standardization

</td>  
<td>

This task will address standardizations of MARISA approach, methods and
results.

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

**WP9**

</td>  
<td>

**Ethics Requirements**

</td>  
<td>

This work package sets out the 'ethics requirements' that the project must
comply with.

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

Table 6: MARISA WBS

The **Work Package Leaders** (WPL) direct the day-to-day technical planning
and execution of work and escalate issues to the EB as required. The WPLs are
responsible for monitoring progress in their respective work package and for
coordinating the activities and compiling the responses. They collaborate with
partners on the tasks of each work package in order to assure the quality of
work and the present the results in reports according to the project
description.

Specific activities of the Work Package Leader are:

  * planning of the Work Package’s activities; 

  

  * coordination of the Task Leaders within the Work Package; 

  

  * liaison with the Project Coordinator (technical follow-up and information on IPR issues in connection with the Work Package); 

  

  * deadline management, and implementation of the Project Work Programme at the Work Package level, in particular the Work Package Leader has to inform the Coordinator and the other Work Package Leaders whenever a timeline might not be achieved so that the necessary contingency plans can be implemented; 

  

  * quality control and performance assessment of the Tasks associated to the Work Package; 

  

  * in case of conflict between contributors, the Work Package Leader tries to find a solution (corrective action) and if needed will inform the Coordinator and the EB; 

  

  * responsible for security issues of the deliverables in their WP. 

  

The Work Package Leader is responsible for the respect of the stipulated
deadlines, and if necessary the execution of the relevant part of the
contingency plan.

The **Task Leaders** (TLs) are responsible of all aspects of the Task’s
execution. A Task consists of a clearly identified simple objective (develop a
specified tool or provide a deliverable).

Specific activities of the Task Leaders are:

  * contribute to the elaboration of the Work Package’s planning; 

  

  * coordination and management of the Task team and the Contributors; 

  

  * liaison with the Work Package Leader (technical follow-up and information on IPR issues in connection with the Work Package); 

  

  * deliver milestones and deliverables in accordance with the Project Work Programme; 

  

  * inform the Work Package Leader on all relevant events and activities related to the Task; 

  

  * propose and implement corrective actions in case of malfunctions; 

  

  * provide cost statements, information and data (financial and other) necessary for the mid-term and final review. 

  

The Task Leader is responsible for the respect of the stipulated deadlines,
and if necessary the execution of the relevant part of the contingency plan.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**TITLE**

</th>  
<th>

**LEADER**

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

**WP1**

</td>  
<td>

**Project Management & Coordination **

</td>  
<td>

**LDO**

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

T1.1

</td>  
<td>

Project Coordination

</td>  
<td>

LDO

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

T1.2

</td>  
<td>

Project Management, Quality Control and Risk Management

</td>  
<td>

LDO

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

T1.3

</td>  
<td>

Innovation Management

</td>  
<td>

ENG

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

T1.4

</td>  
<td>

Ethics Management

</td>  
<td>

LAU

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

**WP2**

</td>  
<td>

**User Needs and Operational Scenarios**

</td>  
<td>

**LAU**

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

T2.1

</td>  
<td>

User community animation

</td>  
<td>

LAU

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

T2.2

</td>  
<td>

Addressing user needs through MARISA services

</td>  
<td>

LDO

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

T2.3

</td>  
<td>

Adoption model for MARISA

</td>  
<td>

ENG

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

T2.4

</td>  
<td>

Interaction with Existing/Legacy Systems and the CISE environment

</td>  
<td>

GMV

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

T2.5

</td>  
<td>

Innovative use of additional data sources

</td>  
<td>

IOSB

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

T2.6

</td>  
<td>

Legal and Ethical Context Analysis

</td>  
<td>

LAU

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

T2.7

</td>  
<td>

Operational Scenarios & Trials Definition

</td>  
<td>

AST

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

**WP3**

</td>  
<td>

**MARISA Toolkit Design**

</td>  
<td>

**GMV**

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

T3.1

</td>  
<td>

Overall Toolkit Design

</td>  
<td>

GMV

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

T3.2

</td>  
<td>

Data Fusion Module and resulting services

</td>  
<td>

LDO

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

T3.3

</td>  
<td>

External and internal Interfaces and gateways design

</td>  
<td>

STW

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

T3.4

</td>  
<td>

Data models definition

</td>  
<td>

ENG

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

T3.5

</td>  
<td>

User interactions (HCI)

</td>  
<td>

LUC

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

**WP4**

</td>  
<td>

**Data analysis and fusion**

</td>  
<td>

**LDO**

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

T4.1

</td>  
<td>

Data Fusion Level 1 products

</td>  
<td>

LDO

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

T4.2

</td>  
<td>

Data Fusion Level 2 products

</td>  
<td>

IOSB

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

T4.3

</td>  
<td>

Data Fusion Level 3 products

</td>  
<td>

TNO

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

**WP5**

</td>  
<td>

**Supporting capabilities and infrastructure**

</td>  
<td>

**ENG**

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

T5.1

</td>  
<td>

Big Data Infrastructure set-up

</td>  
<td>

ENG

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

T5.2

</td>  
<td>

Interfaces to external data sources (include gateways)

</td>  
<td>

GMV

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

**#**

</td>  
<td>

**TITLE**

</td>  
<td>

**LEADER**

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

T5.3

</td>  
<td>

User interactions

</td>  
<td>

LUC

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

T5.4

</td>  
<td>

Data fusion distribution services

</td>  
<td>

LDO

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

T5.5

</td>  
<td>

Information and Assurance services

</td>  
<td>

ADS

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

**WP6**

</td>  
<td>

**MARISA Toolkit integration and validation**

</td>  
<td>

**ADS**

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

T6.1

</td>  
<td>

General principles of test architecture and data integration

</td>  
<td>

ADS

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

T6.2

</td>  
<td>

Definition and implementation of integration platforms

</td>  
<td>

PMM

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

T6.3

</td>  
<td>

Definition of system configurations for each trial

</td>  
<td>

ADS

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

T6.4

</td>  
<td>

Factory integration of campaign configurations

</td>  
<td>

ADS

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

T6.5

</td>  
<td>

Validation of campaign configurations with simulation/emulation tools

</td>  
<td>

ADS

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

**WP7**

</td>  
<td>

**Verification in Operational Trials**

</td>  
<td>

**STW**

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

T7.1

</td>  
<td>

Operational Trials Approach

</td>  
<td>

STW

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

T7.2

</td>  
<td>

Iberian Trial

</td>  
<td>

GMV

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

T7.3

</td>  
<td>

Northern Sea Trial

</td>  
<td>

TNO

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

T7.4

</td>  
<td>

Ionian Trial

</td>  
<td>

LDO

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

T7.5

</td>  
<td>

Aegean Trial

</td>  
<td>

STW

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

T7.6

</td>  
<td>

Strait of Bonifacio Trial

</td>  
<td>

ADS

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

T7.7

</td>  
<td>

Verification Results Consolidation

</td>  
<td>

STW

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

**WP8**

</td>  
<td>

**Dissemination and Exploitation**

</td>  
<td>

**TNO**

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

T8.1

</td>  
<td>

Communication and Dissemination Strategy and Plan

</td>  
<td>

TNO

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

T8.2

</td>  
<td>

MARISA Web Site and dissemination materials

</td>  
<td>

AST

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

T8.3

</td>  
<td>

MARISA Workshops Coordination

</td>  
<td>

TNO

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

T8.4

</td>  
<td>

MARISA Training toolkit support

</td>  
<td>

AST

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

T8.5

</td>  
<td>

IPR Management and Exploitation plan

</td>  
<td>

ENG

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

T8.6

</td>  
<td>

Standardization

</td>  
<td>

LDO

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

**WP9**

</td>  
<td>

**Ethics Requirements**

</td>  
<td>

**LDO**

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

Table 7: MARISA WPs and Tasks Responsibilities

##  4.2. Development Methodology

The MARISA overall development methodology is depicted in Figure 2. The
following principles have been followed.

**Strong involvement of the user community** to capture the relevant
operational needs and validate the results. The MARISA development methodology
relies on the User Community that will include “end user practitioners”,
partners, associates, maritime surveillance experts to explore and exploit the
human capital in Member States and their institutions identifying operational
needs, operational scenarios, existing gaps, acceptability issues and societal
impacts that the proposed solutions may entail.

**Compliance with European Maritime Security Strategy and CISE Data Model** to
maximize interoperability with other MSA community of interest already
existing and operating. The MARISA toolkit will be designed to streamline the
integration with the current and future MSA operational systems, to allow
different configurations and levels of exploitation, to ensure full
compatibility with the CISE data model and with the overall European policy
that facilitates the interagency interoperability and cooperation and allows
each Member State to decide how, when and whether additional data sources are
of relevance to its operations.

**Attention to reuse capabilities and results coming from other European
programs** , but ready to introduce state-of-the-art technologies when
appropriate. Great attention will be devoted to the previous European and
national projects since it is the MARISA Consortium intention to build on
results of these projects. Since all the MARISA participants have been
involved in EU funded R&D and cooperative projects, their deep knowledge of
those projects will allow to move from the current achievements and introduce
improvements and further innovation.

**Protection of Data Fusion Products based on the “need-to-share” approach** ,
to guarantee access and distribution of data fusion results among relevant
stakeholders. MARISA on the one hand will process a great amount of raw data
of different types, on the other hand will produce a relevant number of data
fusion products.

**Adoption of the Agile Software Development Methodology** supported by a
continuous integration environment to assure an evolutionary development of
MARISA services, ease the collaboration and ownership among geographically
distributed partners.

**Validation of MARISA in specific operational trials** . A large part of the
effort will be dedicated to verify and validate the MARISA toolkit in a
variety of operational trials. Indeed, MARISA will be a trial based project.
Trials will be real life exercises, not a guided tour on pre-packed demos.
Each specific trial is characterized by a geographic area, where MARISA
services will be tested, by the Use Cases and hence the system functionalities
will be verified in that trial by the project partners and practitioners
involved in that trial, with its own assets and/or output data coming from
their own systems and needed for the trial execution.

**Two Phase Approach** . The project is organized in two main phases, each
phase will include a complete MARISA life cycle iteration from statement and
finalization of user needs, MARISA toolkit design, development, integration
and setting-up, to trial sessions to validate MARISA through selected
scenarios. This two-phases approach allows to initially construct the concepts
and methods of the MARISA toolkit, deliver and operationally validate a subset
of MARISA initial services. Successively, based on the feedback of the first
phase, MARISA concepts and methods will be revised and enhanced, additional
services will be included and the complete MARISA toolkit validated again in
operational scenarios.

Figure 2: MARISA Development Methodology

##  4.3. Work Logic

MARISA is structured in 9 work packages, over a duration of 30-months. The
work logic is shown in Figure

3\.

Figure 3: MARISA Work Logic

MARISA end users practitioners are involved from the start in WP2,
contributing to the analysis of the context and the definition of the trials.
Users also play a key role in refining the operational scenarios that drive
the trials definition and in feeding the detailed analysis to be done of how
the legacy systems are exercised during the trials. Users also play a key role
in refining the operational scenarios that drive the trials definition and in
feeding the detailed analysis to be done of how the legacy systems are
exercised during the trials.

This involvement is consolidated into user needs, which are then prioritised
to create the functional, interface operational and security requirements as
input to the MARISA Toolkit Design phase performed in WP3. The MARISA software
development, integration and test activities performed in (WP4, WP5 and WP6)
will exploit Agile software development processes supported by a continuous
integration environment that eases the management of multiple contributions
provided by the project partners in a geographically distributed productive
scenario. A relevant integration and validation environment will be provided
in WP6 to minimize the risk of toolkit deployment. Operational scenarios will
be tested in advance in WP6 using simulated and real data. The MARISA Toolkit
will be operationally validated in WP7 according to selected scenarios. The
validation will also include an assessment of the metrics and KPIs.

##  4.4. Innovation Management

The Figure 4 shows the approach to Innovation Management in the MARISA
project.

Figure 4: MARISA Innovation Management

The **User Needs analysis** will focus on the organization of “brainstorming
meetings”, identification and analysis of the assets through the use of value
proposition canvas methodology (who is the customer/s, brainstorming on
customer’s needs). Output will be value proposition canvas, preliminary input
to business models, input to WP3, WP8

The **Competitors and market analysis** will involve the Innovation Team as
well as WP8 Leader in order to come out with a competitor-feature matrix and
an analysis (or re-analysis) of main competitors (value proposition, featured
offered, etc.).

The **Technical improvements** analysis will be carried out together with the
technical partners and it will deal with active participation and animation of
the technical meeting, planning of technical improvements providing also
roadmaps for the MARISA solution as well as provision of new version of the
assets.

**Check point meetings** will represent moments in the project lifecycle,
involving team of technical and nontechnical people with a set of
heterogeneous skills, in which to have demo of improved asset, discussion on
results of previous activities and refined value proposition and unique
selling point (updates, refinement).

The **Innovation Manager** (IM), [Véronique Pevtschin, ENG] ensures the
coordination of all Innovation Management activities.

Main foreseen tasks of the Innovation Manager are:

  * Links and refines user needs to monitor and ensure alignment of technology innovation to user needs. 

  

  * Prepares the exploitation plan taking into account the inputs from the AB and the EB. 

  

  * Manages the execution of the overall exploitation plan of the project and supports the partners in setting up their individual business plans, in order to exploit the results. 

  

  * Manages the knowledge produced during the project lifecycle and assesses the opportunity for applying for patents or declaring copyrights, through maintaining all innovations descriptions, screening and ownership. 

  

  * Supports the individual partners’ legal departments in their drafting of the legal and contractual agreements with respect to the IPR of the project either internally or externally (the IM does not provide the legal consultancy, as this knowledge is part of the internal legal departments, but acts as a support to fully explain the features of the MARISA approach and their requirements on issues such as data exchange, interconnection of solutions with different IPRs and owners etc). 

  

MARISA Tasks and Deliverables affected by the Innovation Management activities
are reported in the Figure 5.

Figure 5: Innovation Managements in the Project Tasks and Deliverables

##  4.5. Schedule and Milestones

The Figure 6 shows the master schedule of the different work packages. The
whole project duration is 30 months. The project is organized in two main
phases each phase ending with trial sessions that validate MARISA through
selected operational scenarios.

  * Phase-1 focuses on the initial construction of the concepts and methods needed for the MARISA Toolkit and delivers and validate a subset of services. 

  

  * Phase-2 evolves the concepts and methods based on the feedback gained from the first phase, delivers and validate the complete MARISA toolkit. 

  

Phase-1 will be completed in 20 months (M1-M20), subsequent Phase-2 will be
completed in 10 months (M21-M30).

Figure 6: MARISA Gantt Chart

The following table includes the Project Milestones, with a short description
of their scope and verification means.  
  
<table>  
<tr>  
<th>

**ID**

</th>  
<th>

**Milestone name**

</th>  
<th>

**Related work package(s)**

</th>  
<th>

**Estimated date**

</th>  
<th>

**Means of verification**

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

**MS1**

</td>  
<td>

Project Start

</td>  
<td>

All

</td>  
<td>

M01

</td>  
<td>

1\. Kick-Off meeting.

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

**ID**

</th>  
<th>

**Milestone name**

</th>  
<th>

**Related work package(s)**

</th>  
<th>

**Estimated date**

</th>  
<th>

</th>  
<th>

**Means of verification**

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

**MS2**

</td>  
<td>

Initial

Definition of User community needs, Operational

trial

scenarios and strategy

</td>  
<td>

WP2, WP6, WP7, WP8

</td>  
<td>

M05

</td>  
<td>

1\. 2.

3\.

4\.

</td>  
<td>

User Community established.

Initial User needs and operational trial scenarios strategy and definition
achieved (initial version of D2.2 to D2.7 submitted).

Availability of project management, risks, quality plans (D1.1).

Establishment of communication and dissemination strategy (D8.1).

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

**MS3**

</td>  
<td>

MARISA

Toolkit

Initial

Design

</td>  
<td>

WP3, WP6

</td>  
<td>

M10

</td>  
<td>

1\.

2\.

</td>  
<td>

Initial definition of MARISA toolkit design achieved (initial version of D3.1
to D3.5 submitted).

Definition of integration test platform and integration plans achieved (D6.1,
D6.2, D6.4 submitted).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

3\.

</td>  
<td>

Detailed plans for operational scenarios achieved (D7.1).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

4\.

</td>  
<td>

Web Site established and populated with dissemination material (D8.2, D8.3).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

5\.

</td>  
<td>

Initial Project Report produced (D1.2 submitted).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

6\.

</td>  
<td>

Initial Societal Ethical Report available (D1.5).

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

**MS4**

</td>  
<td>

MARISA

Toolkit completed for Phase-1 Operational

Trials

</td>  
<td>

WP4, WP5, WP6, WP7

</td>  
<td>

M15

</td>  
<td>

1\.

2\.

</td>  
<td>

MARISA Toolkit completed for Phase 1 (Initial version of D4.1 to D4.3 and D5.1
to D5.5 produced) and in factory validated for Phase-1 Operational Trials
(initial version of D6.3, D6.5, D6.6 submitted).

Training Kit available (initial version of D8.5).

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

**MS5**

</td>  
<td>

Mid-Term Review

</td>  
<td>

WP1, WP2, WP7, WP8

</td>  
<td>

M20

</td>  
<td>

1\.

</td>  
<td>

Phase-1 Operational Trials completed and results available (initial version of
D7.2 submitted).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

2\.

</td>  
<td>

Analysis of MARISA Phase-1 achievements and assessment from the User Community
available (Initial version of D2.1 produced).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

3\.

</td>  
<td>

Updated Web Site and dissemination material available (D8.2, D8.3 final).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

4\.

</td>  
<td>

First workshop achieved (D8.4), Exploitation plan achieved (D8.6).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

5\.

</td>  
<td>

First standardization report available (D8.8).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

6\.

</td>  
<td>

Final user and operational needs for Phase-2 achieved. (Final version of D2.2
to 2.7 submitted).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

7\.

</td>  
<td>

Intermediate Project and Societal Ethical Reports Available (D1.3, D1.6).

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

**ID**

</td>  
<td>

**Milestone name**

</td>  
<td>

**Related work package(s)**

</td>  
<td>

**Estimated date**

</td>  
<td>

</td>  
<td>

**Means of verification**

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

**MS6**

</td>  
<td>

MARISA

Toolkit Completed for Phase-2 Operational

Trials

</td>  
<td>

WP4, WP5, WP6, WP7

</td>  
<td>

M26

</td>  
<td>

1\.

2\.

</td>  
<td>

Final MARISA toolkit implementation achieved (final version of D3.1 to D3.5,
D4.1 to D4.3, D5.1 to D5.4, D6.3 to D6.6 submitted).

Detailed plans for phase-2 operational scenarios achieved (final D7.1
produced).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

3\.

</td>  
<td>

Final version of Training Kit available (final D8.5 produced)

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

**MS7**

</td>  
<td>

MARISA

Project

Completion

</td>  
<td>

WP1, WP2, WP7, WP8

</td>  
<td>

M30

</td>  
<td>

1\.

2\.

</td>  
<td>

Phase-2 Operational Trials completed and results available (final version of
D7.2).

Assessments of MARISA Phase-2 achievements available (final version of D2.1
produced).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

3\.

</td>  
<td>

Exploitation Uptake actions established

(D8.7).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

4\.

</td>  
<td>

Standardization reports available (final D8.8).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

5\.

</td>  
<td>

Final Project and Societal Ethical Reports available (D1.3, D1.7).

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

6\.

</td>  
<td>

All action deliverables completed and submitted.

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

Table 8: MARISA Milestones

###  4.5.1. Activity Network

Figure 7 shows inter WP dependencies among the nine work packages. WP2
provides the user requirements to WP3 and WP7 for the design of the MARISA
toolkit and operational trials. WP7 provides feedback to WP3-6 after the first
project phase is finished, which will be used to fine-tune the outcome of the
corresponding WPs during the second phase of the project.

Figure 7: MARISA Pert-like diagram showing deliverables and inter-WP links

###  4.5.2. Project Review Plan

The MARISA Project is split into two reporting periods:

  * P1: Month 1 – Month 18 (M1 – M18); 

  

  * P2: Month 19 – Month 30 (M19 – M30); 

  

At the end of each period a Project Review Meeting will be held with the
participation of the EC Project Officer and independent reviewers appointed by
the EC.  
  
<table>  
<tr>  
<th>

**Review number**

</th>  
<th>

**Tentative timing**

</th>  
<th>

**Planned Venue of Review**

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

RV1

</td>  
<td>

18

</td>  
<td>

Rome

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

RV2

</td>  
<td>

30

</td>  
<td>

Rome

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

Table 9: Project Reviews

###  4.5.3. List of Deliverables

The following table provides the list of the deliverables throughout the
project lifecycle.  
  
<table>  
<tr>  
<th>

**Del.**

**Num.**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**WP**

</th>  
<th>

**Lead**

</th>  
<th>

**Type**

</th>  
<th>

**Dissem. level**

</th>  
<th>

**Deliv. date**

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

**D1.1**

</td>  
<td>

Project Management, Quality and Risk Plan

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D1.2**

</td>  
<td>

MARISA Project Initial Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D1.3**

</td>  
<td>

MARISA Project Intermediate Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D1.4**

</td>  
<td>

MARISA Project Final Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M30

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

**D1.5**

</td>  
<td>

MARISA Societal Ethical Initial Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D1.6**

</td>  
<td>

MARISA Societal Ethical Intermediate Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D1.7**

</td>  
<td>

MARISA Societal Ethical Final Report

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M30

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

**D1.8**

</td>  
<td>

MARISA Data Management Plan

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

ORDP

</td>  
<td>

CO

</td>  
<td>

M6

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

**D1.9**

</td>  
<td>

MARISA Data Management Plan (final)

</td>  
<td>

WP1

</td>  
<td>

LDO

</td>  
<td>

ORDP

</td>  
<td>

CO

</td>  
<td>

M24

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

**D2.1**

</td>  
<td>

MARISA User Community Report

</td>  
<td>

WP2

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D2.2**

</td>  
<td>

MARISA User Requirements

</td>  
<td>

WP2

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D2.3**

</td>  
<td>

MARISA Adoption Models

</td>  
<td>

WP2

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D2.4**

</td>  
<td>

MARISA Interaction with existing/legacy systems

</td>  
<td>

WP2

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M5

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

**D2.5**

</td>  
<td>

MARISA Usage of Additional Data Sources

</td>  
<td>

WP2

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M5

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

**D2.6**

</td>  
<td>

Legal, ethical and societal aspects of

MARISA

</td>  
<td>

WP2

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D2.7**

</td>  
<td>

MARISA Operational Scenarios and Trials

</td>  
<td>

WP2

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D2.8**

</td>  
<td>

MARISA User Community Report (final)

</td>  
<td>

WP2

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M30

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

**D2.9**

</td>  
<td>

MARISA User Requirements (final)

</td>  
<td>

WP2

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D2.10**

</td>  
<td>

MARISA Adoption Models (final)

</td>  
<td>

WP2

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D2.11**

</td>  
<td>

MARISA Interaction with existing/legacy systems (final)

</td>  
<td>

WP2

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M20

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

**D2.12**

</td>  
<td>

MARISA Usage of Additional Data

Sources (final)

</td>  
<td>

WP2

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M20

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

**D2.13**

</td>  
<td>

Legal, ethical and societal aspects of

MARISA (final)

</td>  
<td>

WP2

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D2.14**

</td>  
<td>

MARISA Operational Scenarios and Trials

(final)

</td>  
<td>

WP2

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D3.1**

</td>  
<td>

MARISA Toolkit Design

</td>  
<td>

WP3

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D3.2**

</td>  
<td>

MARISA Services Description Document

</td>  
<td>

WP3

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D3.3**

</td>  
<td>

MARISA Interfaces description Document

</td>  
<td>

WP3

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M10

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

**D3.4**

</td>  
<td>

MARISA data model description

</td>  
<td>

WP3

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D3.5**

</td>  
<td>

MARISA Human machine best practices and design document

</td>  
<td>

WP3

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D3.6**

</td>  
<td>

MARISA Toolkit Design (final)

</td>  
<td>

WP3

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M22

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

**D3.7**

</td>  
<td>

MARISA Services Description Document

(final)

</td>  
<td>

WP3

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M22

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

**D3.8**

</td>  
<td>

MARISA Interfaces description Document

(final)

</td>  
<td>

WP3

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M22

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

**Del.**

**Num.**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**WP**

</th>  
<th>

**Lead**

</th>  
<th>

**Type**

</th>  
<th>

**Dissem. level**

</th>  
<th>

**Deliv. date**

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

**D3.9**

</td>  
<td>

MARISA data model description (final)

</td>  
<td>

WP3

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M22

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

**D3.10**

</td>  
<td>

MARISA Human machine best practices and design document (final)

</td>  
<td>

WP3

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M22

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

**D4.1**

</td>  
<td>

MARISA Level 1 Data Fusion Services Description

</td>  
<td>

WP4

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D4.2**

</td>  
<td>

MARISA Level 2 Data Fusion Services Description

</td>  
<td>

WP4

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D4.3**

</td>  
<td>

MARISA Level 3 Data Fusion Services Description

</td>  
<td>

WP4

</td>  
<td>

TNO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D4.4**

</td>  
<td>

MARISA Level 1 Data Fusion Services

Description (final)

</td>  
<td>

WP4

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D4.5**

</td>  
<td>

MARISA Level 2 Data Fusion Services

Description (final)

</td>  
<td>

WP4

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D4.6**

</td>  
<td>

MARISA Level 3 Data Fusion Services

Description (final)

</td>  
<td>

WP4

</td>  
<td>

TNO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D5.1**

</td>  
<td>

MARISA Big data Infrastructure

</td>  
<td>

WP5

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D5.2**

</td>  
<td>

MARISA Interfaces to External data sources

</td>  
<td>

WP5

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M12

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

**D5.3**

</td>  
<td>

MARISA User Interfaces

</td>  
<td>

WP5

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D5.4**

</td>  
<td>

MARISA Data Fusion Distribution Services

</td>  
<td>

WP5

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M12

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

**D5.5**

</td>  
<td>

MARISA Access Control Services

</td>  
<td>

WP5

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M12

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

**D5.6**

</td>  
<td>

MARISA Big data Infrastructure (final)

</td>  
<td>

WP5

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D5.7**

</td>  
<td>

MARISA Interfaces to External data sources (final)

</td>  
<td>

WP5

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M24

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

**D5.8**

</td>  
<td>

MARISA User Interfaces (final)

</td>  
<td>

WP5

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D5.9**

</td>  
<td>

MARISA Data Fusion Distribution

Services (final)

</td>  
<td>

WP5

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M24

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

**D5.10**

</td>  
<td>

MARISA Access Control Services (final)

</td>  
<td>

WP5

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M24

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

**D6.1**

</td>  
<td>

General principles of MARISA test architecture and data integration

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D6.2**

</td>  
<td>

Definition of MARISA integration platforms

</td>  
<td>

WP6

</td>  
<td>

PMM

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D6.3**

</td>  
<td>

Definition of MARISA Trial Configurations

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R/O

</td>  
<td>

CO

</td>  
<td>

M15

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

**D6.4**

</td>  
<td>

MARISA Toolkit Integration and validation Test Plan

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M10

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

**D6.5**

</td>  
<td>

MARISA Toolkit Integration and validation test report

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M15

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

**D6.6**

</td>  
<td>

MARISA Toolkit

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

DEM

</td>  
<td>

PU

</td>  
<td>

M15

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

**D6.7**

</td>  
<td>

Definition of MARISA Trial Configurations (final)

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R/O

</td>  
<td>

CO

</td>  
<td>

M26

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

**D6.8**

</td>  
<td>

MARISA Toolkit Integration and validation Test Plan (final)

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M22

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

**D6.9**

</td>  
<td>

MARISA Toolkit Integration and validation test report (final)

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M26

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

**Del.**

**Num.**

</td>  
<td>

**Deliverable name**

</td>  
<td>

**WP**

</td>  
<td>

**Lead**

</td>  
<td>

**Type**

</td>  
<td>

**Dissem. level**

</td>  
<td>

**Deliv. date**

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

**D6.10**

</td>  
<td>

MARISA Toolkit (final)

</td>  
<td>

WP6

</td>  
<td>

ADS

</td>  
<td>

DEM

</td>  
<td>

PU

</td>  
<td>

M26

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

**D7.1**

</td>  
<td>

MARISA Validation in operational trial approach and plan

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D7.2**

</td>  
<td>

MARISA Validation in operational trial approach and plan - Appendix

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

RE

</td>  
<td>

M10

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

**D7.3**

</td>  
<td>

MARISA Operational trials results Report and Lesson Learnt

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M20

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

**D7.4**

</td>  
<td>

MARISA Operational trials results Report and Lesson Learnt - Appendix

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

RE

</td>  
<td>

M20

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

**D7.5**

</td>  
<td>

MARISA Validation in operational trial approach and plan (final)

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D7.6**

</td>  
<td>

MARISA Validation in operational trial approach and plan (final) - Appendix

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

RE

</td>  
<td>

M20

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

**D7.7**

</td>  
<td>

MARISA Operational trials results Report and Lesson Learnt (final)

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M30

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

**D7.8**

</td>  
<td>

MARISA Operational trials results Report and Lesson Learnt (final) – Appendix

</td>  
<td>

WP7

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

RE

</td>  
<td>

M30

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

**D8.1**

</td>  
<td>

MARISA Communication and Dissemination Strategy and Plan

</td>  
<td>

WP8

</td>  
<td>

TNO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M5

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

**D8.2**

</td>  
<td>

MARISA Dissemination Material

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M10

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

**D8.3**

</td>  
<td>

MARISA WEB Site

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

DEC

</td>  
<td>

PU

</td>  
<td>

M10

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

**D8.4**

</td>  
<td>

MARISA Workshop Organization and

Results

</td>  
<td>

WP8

</td>  
<td>

TNO

</td>  
<td>

R/O

</td>  
<td>

PU

</td>  
<td>

M20

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

**D8.5**

</td>  
<td>

MARISA Training Kit

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

O

</td>  
<td>

PU

</td>  
<td>

M15

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

**D8.6**

</td>  
<td>

MARISA Exploitation Plan

</td>  
<td>

WP8

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D8.7**

</td>  
<td>

MARISA Exploitation and Uptake mechanisms

</td>  
<td>

WP8

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

M30

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

**D8.8**

</td>  
<td>

MARISA Services Standardization Report

</td>  
<td>

WP8

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D8.9**

</td>  
<td>

MARISA Dissemination Material (final)

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M20

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

**D8.10**

</td>  
<td>

MARISA WEB Site (intermediate)

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

DEC

</td>  
<td>

PU

</td>  
<td>

M20

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

**D8.11**

</td>  
<td>

MARISA Workshop Organization and

Results (final)

</td>  
<td>

WP8

</td>  
<td>

TNO

</td>  
<td>

R/O

</td>  
<td>

PU

</td>  
<td>

M30

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

**D8.12**

</td>  
<td>

MARISA Training Kit (final)

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

O

</td>  
<td>

PU

</td>  
<td>

M26

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

**D8.13**

</td>  
<td>

MARISA Services Standardization Report

(final)

</td>  
<td>

WP8

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

M30

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

**D8.14**

</td>  
<td>

MARISA WEB Site (final)

</td>  
<td>

WP8

</td>  
<td>

AST

</td>  
<td>

DEC

</td>  
<td>

PU

</td>  
<td>

M30

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

**D9.1**

</td>  
<td>

H – Requirement No.4

</td>  
<td>

WP9

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

CO

</td>  
<td>

M9

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

**D9.2**

</td>  
<td>

POPD – Requirement No.6

</td>  
<td>

WP9

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

CO

</td>  
<td>

M9

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

**D9.3**

</td>  
<td>

POPD – Requirement No.8

</td>  
<td>

WP9

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

CO

</td>  
<td>

M9

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

**D9.4**

</td>  
<td>

POPD – Requirement No.9

</td>  
<td>

_WP9_

</td>  
<td>

_LDO_

</td>  
<td>

ETH

</td>  
<td>

CO

</td>  
<td>

M9

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

Table 10: MARISA Deliverables List

##  4.6. Collaboration among partners

Due to the nature of the project, an efficient and effective communication and
knowledge-flow among the partners is very important. A deliverable describing
the complete communication and dissemination strategy for the MARISA project
is going to be delivered in M5. Regarding collaboration among partners, the
following arrangements will be made to ensure optimum sharing of knowledge
within the consortium.

###  4.6.1. Collaboration Tools

####  _4.6.1.1. Web Site_

A fully accessible project portal will be developed, with users’ customized
view and public as well as consortium-internal areas. The project web site
will support the communication among the project members, as well as
maintenance of a common repository of the documentation.

####  _4.6.1.2. Slack_

Slack is a cloud-based set of team collaboration tools and services. Slack
teams allow communities, groups, or teams to join through a specific URL or
invitation sent by a team admin or owner.

A Slack Environment has been already opened in the context of WP2 activities,
with a specific focus on the

MARISA User Requirements gathering phase, in order to support “dynamics”
between participants (EndUsers and Practitioners). At this purpose, it has
been created one slack channel per Trial involving End-users and providers,
encouraging discussions as well as exchanging of documentation among
participants.

###  4.6.2. Project Meetings

  * **Internal project meetings** will serve as the main forum for interactions between all groups and for reviews preparation. Project internal meetings will be more telephone conferences instead of physical meetings. 

  

  * **Telephone conferences** will be held at least every months and physical meetings will be held at least every 3 months. WP internal/cross WP meetings will be held when requested via telephone or physical if needed. Video conference may be used, although some partners may not have the facility, and may not be suitable if more than two partners need to be involved. 

  

  * **Integration meetings** are also foreseen at the end of integration activities to assess the readiness of the MARISA Toolkit to operational trials. 

  

  * We plan three **Advisory Board meetings** to take place together with the achievement of main project milestones: MS3 (M10) toolkit design, MS5 (M20) Mid-Term Review, MS7 (M30) Final Review. 

  

  * **Innovation meetings** are planned every 3 months in the first year of the project (4 in total). 

  

  * **Technical Board meetings** are planned about every 6 month. 

  

  * **Executive Board meetings** are planned at least every 6 months or on request. 

  

#####  4.6.2.1. Meetings Plan

The following figure provides an overall view of the project meetings plan.
This plan does not include the Formal Project reviews, that have been
described in the related paragraph 4.5.2.

Figure 8: Project Meetings Master Schedule

##  4.7. Involvement of end-users external to the Consortium

Community mechanisms will be created (as part of the MARISA Web Site
implemented in WP8) to foster interactions, leading to knowledge co-created
through social interactions, competence sharing and collective service
development. The User Community will be set-up involving user partners as well
as external end users invited to join the initiative. In this context, MARISA
aims to be as inclusive as possible, building also on the links of individual
consortium partners of the MARISA consortium to past and on-going initiatives
in the domain (CLOSEYE, EUCISE2020, SeaBILLA, PERSEUS, CoopP etc.) to speed up
the process.

The User Community includes partners, practitioners involved as full partners,
all the associated partners (the organizations that have already expressed
interest and are supporting the objectives of the project maritime domain
experts, external end users). However the consortium is always open to accept
other members during the execution of the project. It addresses user needs,
operational requirements, potential ethical and societal issues. It is
coordinated and animated by the User Community Leader.

#  5\. Configuration Management

Configuration Management deals with the overall project consistency,
identification and tracking of changes related to all project results
including the deliverables, documents, testing procedures and any other
related activity.

##  5.1. Document Configuration Management

Document configuration management will be ensured through the tracking of the
versions and history of changes of the various project documents
(deliverables, meeting minutes, reviewed documents, etc.).

Document history will be tracked in each deliverable in a separate table
describing the different versions of the document and the reasons of
change/updates on it. Each deliverable main author will be responsible for
updating this.

##  5.2. Software Configuration Management

The software components monitoring, will be done using a software version
configuration tool (CVS, SVN etc.), which will be installed on a central
Server. This will ensure that all necessary components of the MARISA Toolkit
will be available for the distributed development teams.

##  5.3. E-Mail Conventions

E-mail will be an important means to exchange information in the MARISA
project.

All E-mail subject headings must start with the text “[MARISA]”. Additional
tags can be added to specify relevant work packages, tasks, and deliverables
where appropriate, and if deemed useful. The tags should never contain spaces
within the square brackets.

Some examples of email subject headings are:

  * [MARISA] [WP8] Title 

  

  * [MARISA] [WP1] [Task1.2] [D1.4] Title…….. document 

  

  * [MARISA] [WP2] Title 

  

  * [MARISA] [WP4] [Task4.3] Title 

  

#  6\. Quality Management

##  6.1. Quality Assurance Process

Quality control is responsibility of everybody involved in the each project
activity.

The quality control task performed by the Coordinator at project level will
not substitute for internal quality control used in the various partner
organisations for their internal work. All partner organisations should ensure
that their existing internal quality control procedures are applied to MARISA
project tasks.

However, as part of their role, the Project Coordinator, the Project Manager,
the Innovation Manager and the Technical Board will act as Project Quality
Assurance Team.

Objectives of the Project Quality Assurance Team are:

  * to ensure appropriate application of the procedures in MARISA; 

  

  * to control the main outputs (mainly documents) of the Project/Work Packages & organising reviews. 

  

With reference to **Project Deliverables** : each project deliverable is
assigned to one leading responsible partner. This partner takes the
responsibility that the deliverable is of high quality and timely delivered.
The responsible partner assures that the content of a deliverable is
consistent with the team-workings of the deliverable and that the particular
objectives related to the goals of the project are met. Any issues related to
deliverables, endangering the success of the work package or the project, have
to be reported by the WP leader immediately to the Project Management and
discussed within the Coordination team.

###  6.1.1. Reviews for Documentation/Deliverables

A Reviews Process involving each partner and selected reviewers is adopted in
the Consortium to ensure the quality of deliverables and of any other external
publication with regard to the technical content, the objectives of the
project and to adhere to formal requirements established in the Grant and
Consortium Agreements. Review process ensures that publications and
deliverables comply with IPR of the partners. For external publications as
well as for project deliverables, the review process will involve all
Consortium partners and requires the approval of the Project Quality Assurance
Team.

Project documentation will be reviewed against the following criteria
regarding form as well as content of the document:

  * Format of the document according to the document templates. 

  

  * Identification and correction of typing mistakes, etc. 

  

  * Check of consistency: 

    * with the overall scope of the document (e.g. it contains the right information, avoiding unnecessary information, etc.); 

  

    * with previous relevant documentation (e.g. technical specifications vs requirements definition, no redundancy with other documents, etc.). 

  

  

  * Technical aspects of the documentation will be reviewed also by the Project Quality Assurance Team in order to ensure that the document meets the technical goals of the project, and that all technical information is advancing the current state of the art and the recent technological research level. 

  

The procedures and timeline for the review project documentation are described
hereafter.

  * The partner responsible for preparing the deliverable, drafts a Table of Contents (ToC), assigns tasks to all involved partners and sets the respective deadlines (considering also time needed for quality review). 

  

  * Involved partners provide their feedback within the deadlines and the responsible partner prepares the first draft of the document. 

  

  * This draft is sent to the entire consortium for comments and improvements/additions. The feedback period for project partners should last at least five working days. Feedback is sent directly to the responsible partner who revises the document and prepares the semi-final version. 

  

  * The Quality Control Process begins based on the semi-final version of the deliverable. **This version has to be ready no later than 20 working days before the final deadline.** At least two Internal Reviewers have been assigned in advance (refer to the reviewers table). 

  

  * The Internal Reviewers send their comments (by five working days) to the Project Quality Assurance Team who consolidates and checks the reports and sends them to the partner responsible. 

  

  * This partner responsible for preparing the deliverable then improves the document based on received comments. In case the comments/suggestions cannot be realised, the reasons for this must be documented. If necessary (i.e. if there are too many comments on the first round), another round of comments from the Internal Reviewers takes place. 

  

  * The partner responsible addresses them appropriately and prepares the final version of the document, which is sent to the Project Coordinator (at least five days before the final deadline). 

  

  * The Project Coordinator then submits the document to the EC. 

  

Figure 9: MARISA Deliverable Preparation and Quality Review Process - Flow

Figure 10: MARISA Deliverable Preparation and Quality Review Process \-
Timeline

##  6.2. Deliverables Item List and Internal Reviewers  
  
<table>  
<tr>  
<th>

**Del.**

**Num.**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**Lead**

</th>  
<th>

**Type**

</th>  
<th>

**Int.**

**Rev/er**

**#1**

</th>  
<th>

**Int.**

**Rev/er**

**#2**

</th>  
<th>

**Delivery date**

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

**D1.1**

</td>  
<td>

Project Management, Quality and Risk Plan

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

ENG

</td>  
<td>

GMV

</td>  
<td>

M5

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

**Del.**

**Num.**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**Lead**

</th>  
<th>

**Type**

</th>  
<th>

**Int.**

**Rev/er**

**#1**

</th>  
<th>

**Int.**

**Rev/er**

**#2**

</th>  
<th>

**Delivery date**

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

**D1.2**

</td>  
<td>

MARISA Project Initial Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

STW

</td>  
<td>

ENG

</td>  
<td>

M10

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

**D1.3**

</td>  
<td>

MARISA Project Intermediate Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

GMV

</td>  
<td>

ADS

</td>  
<td>

M20

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

**D1.4**

</td>  
<td>

MARISA Project Final Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

ADS

</td>  
<td>

STW

</td>  
<td>

M30

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

**D1.5**

</td>  
<td>

MARISA Societal Ethical Initial Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

LAU

</td>  
<td>

ENG

</td>  
<td>

M10

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

**D1.6**

</td>  
<td>

MARISA Societal Ethical Intermediate Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

LAU

</td>  
<td>

ENG

</td>  
<td>

M20

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

**D1.7**

</td>  
<td>

MARISA Societal Ethical Final Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

LAU

</td>  
<td>

ENG

</td>  
<td>

M30

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

**D1.8, D1.9**

</td>  
<td>

MARISA Data Management Plan

(initial, final)

</td>  
<td>

LDO

</td>  
<td>

ORDP

</td>  
<td>

ENG

</td>  
<td>

GMV

</td>  
<td>

M6, M24

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

**D2.1, D2.8**

</td>  
<td>

MARISA User Community Report

(initial, final)

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

ADS

</td>  
<td>

INOV

</td>  
<td>

M20, M30

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

**D2.2, D2.9**

</td>  
<td>

MARISA User Requirements (initial, final)

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

CMRE

</td>  
<td>

IW

</td>  
<td>

M5, M20

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

**D2.3, D2.10**

</td>  
<td>

MARISA Adoption Models (initial, final)

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

LUC

</td>  
<td>

TNO

</td>  
<td>

M5, M20

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

**D2.4, D2.11**

</td>  
<td>

MARISA Interaction with

existing/legacy systems (initial, final)

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

EG

</td>  
<td>

ADS

</td>  
<td>

M5, M20

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

**D2.5, D2.12**

</td>  
<td>

MARISA Usage of Additional Data

Sources (initial, final)

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

TNO

</td>  
<td>

STW

</td>  
<td>

M5, M20

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

**D2.6, D2.13**

</td>  
<td>

Legal, ethical and societal aspects of MARISA (initial, final)

</td>  
<td>

LAU

</td>  
<td>

R

</td>  
<td>

IW

</td>  
<td>

PLA

</td>  
<td>

M5, M20

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

**D2.7, D2.14**

</td>  
<td>

MARISA Operational Scenarios and

Trials (initial, final)

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

STW

</td>  
<td>

PMM

</td>  
<td>

M5, M20

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

**D3.1, D3.6**

</td>  
<td>

MARISA Toolkit Design (initial, final)

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

TNO

</td>  
<td>

INOV

</td>  
<td>

M10, M22

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

**D3.2, D3.7**

</td>  
<td>

MARISA Services Description

Document (initial, final)

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

ADS

</td>  
<td>

TNO

</td>  
<td>

M10, M22

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

**D3.3, D3.8**

</td>  
<td>

MARISA Interfaces description Document (initial, final)

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

IOSB

</td>  
<td>

LAU

</td>  
<td>

M10, M22

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

**D3.4, D3.9**

</td>  
<td>

MARISA data model description

(initial, final)

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

IW

</td>  
<td>

ADS

</td>  
<td>

M10, M22

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

**D3.5, D3.10**

</td>  
<td>

MARISA Human machine best

practices and design document (initial, final)

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

LAU

</td>  
<td>

IW

</td>  
<td>

M10, M22

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

**D4.1, D4.4**

</td>  
<td>

MARISA Level 1 Data Fusion Services

Description (initial, final)

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

AST

</td>  
<td>

EG

</td>  
<td>

M12, M24

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

**D4.2, D4.5**

</td>  
<td>

MARISA Level 2 Data Fusion Services

Description (initial, final)

</td>  
<td>

IOSB

</td>  
<td>

R

</td>  
<td>

ENG

</td>  
<td>

UNIBO

</td>  
<td>

M12, M24

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

**D4.3, D4.6**

</td>  
<td>

MARISA Level 3 Data Fusion Services

Description (initial, final)

</td>  
<td>

TNO

</td>  
<td>

R

</td>  
<td>

ADS

</td>  
<td>

CMRE

</td>  
<td>

M12, M24

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

**D5.1, D5.6**

</td>  
<td>

MARISA Big data Infrastructure

(initial, final)

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

STW

</td>  
<td>

EG

</td>  
<td>

M12, M24

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

**D5.2, D5.7**

</td>  
<td>

MARISA Interfaces to External data sources (initial, final)

</td>  
<td>

GMV

</td>  
<td>

R

</td>  
<td>

TNO

</td>  
<td>

INOV

</td>  
<td>

M12, M24

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

**Del.**

**Num.**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**Lead**

</th>  
<th>

**Type**

</th>  
<th>

**Int.**

**Rev/er**

**#1**

</th>  
<th>

**Int.**

**Rev/er**

**#2**

</th>  
<th>

**Delivery date**

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

**D5.3, D5.8**

</td>  
<td>

MARISA User Interfaces (initial, final)

</td>  
<td>

LUC

</td>  
<td>

R

</td>  
<td>

IOSB

</td>  
<td>

LAU

</td>  
<td>

M12, M24

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

**D5.4, D5.9**

</td>  
<td>

MARISA Data Fusion Distribution

Services (initial, final)

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

PMM

</td>  
<td>

STW

</td>  
<td>

M12, M24

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

**D5.5, D5.10**

</td>  
<td>

MARISA Access Control Services

(initial, final)

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

EG

</td>  
<td>

TNO

</td>  
<td>

M12, M24

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

**D6.1**

</td>  
<td>

General principles of MARISA test architecture and data integration

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

LDO

</td>  
<td>

GMV

</td>  
<td>

M10

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

**D6.2**

</td>  
<td>

Definition of MARISA integration platforms

</td>  
<td>

PMM

</td>  
<td>

R

</td>  
<td>

ENG

</td>  
<td>

STW

</td>  
<td>

M10

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

**D6.3, D6.7**

</td>  
<td>

Definition of Trial Configurations (initial, final)

</td>  
<td>

ADS

</td>  
<td>

R/O

</td>  
<td>

IOSB

</td>  
<td>

IW

</td>  
<td>

M15, M26

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

**D6.4, D6.8**

</td>  
<td>

MARISA Toolkit Integration and

validation Test Plan ( initial, final)

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

GMV

</td>  
<td>

ENG

</td>  
<td>

M10, M22

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

**D6.5, D6.9**

</td>  
<td>

MARISA Toolkit Integration and

validation test report (initial, final)

</td>  
<td>

ADS

</td>  
<td>

R

</td>  
<td>

STW

</td>  
<td>

LDO

</td>  
<td>

M15, M26

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

**D6.6, D6.10**

</td>  
<td>

MARISA Toolkit

</td>  
<td>

ADS

</td>  
<td>

DEM

</td>  
<td>

IW

</td>  
<td>

LUC

</td>  
<td>

M15, M26

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

**D7.1, D7.5**

</td>  
<td>

MARISA Validation in operational trial approach and plan (initial, final)

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

LDO

</td>  
<td>

GMV

</td>  
<td>

M10, M20

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

**D7.2, D7.6**

</td>  
<td>

MARISA Validation in operational trial approach and plan – Appendix (initial,
final)

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

LDO

</td>  
<td>

GMV

</td>  
<td>

M10, M20

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

**D7.3, D7.7**

</td>  
<td>

MARISA Operational trials results

Report and Lesson Learnt (initial, final)

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

ENG

</td>  
<td>

ADS

</td>  
<td>

M20, M30

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

**D7.4, D7.8**

</td>  
<td>

MARISA Operational trials results

Report and Lesson Learnt – Appendix

(initial, final)

</td>  
<td>

STW

</td>  
<td>

R

</td>  
<td>

ENG

</td>  
<td>

ADS

</td>  
<td>

M20, M30

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

**D8.1**

</td>  
<td>

MARISA Communication and Dissemination Strategy and Plan

</td>  
<td>

TNO

</td>  
<td>

R

</td>  
<td>

GMV

</td>  
<td>

PLA

</td>  
<td>

M5

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

**D8.2, D8.9**

</td>  
<td>

MARISA Dissemination Material

(initial, final)

</td>  
<td>

AST

</td>  
<td>

R

</td>  
<td>

EG

</td>  
<td>

INOV

</td>  
<td>

M10, M20

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

**D8.3,**

**D8.10,**

**D8.14**

</td>  
<td>

MARISA WEB Site (initial, intermediate, final)

</td>  
<td>

AST

</td>  
<td>

DEC

</td>  
<td>

LUC

</td>  
<td>

UNIBO

</td>  
<td>

M10,

M20,

M30

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

**D8.4, D8.11**

</td>  
<td>

MARISA Workshop Organization and

Results

</td>  
<td>

TNO

</td>  
<td>

R/O

</td>  
<td>

CMRE

</td>  
<td>

EG

</td>  
<td>

M20, M30

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

**D8.5, D8.12**

</td>  
<td>

MARISA Training Kit (initial, final)

</td>  
<td>

AST

</td>  
<td>

O

</td>  
<td>

INOV

</td>  
<td>

LAU

</td>  
<td>

M15, M26

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

**D8.6**

</td>  
<td>

MARISA Exploitation Plan

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

STW

</td>  
<td>

GMV

</td>  
<td>

M20

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

**D8.7**

</td>  
<td>

MARISA Exploitation and Uptake mechanisms

</td>  
<td>

ENG

</td>  
<td>

R

</td>  
<td>

PLA

</td>  
<td>

CMRE

</td>  
<td>

M30

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

**D8.8, D8.13**

</td>  
<td>

MARISA Services Standardization Report

</td>  
<td>

LDO

</td>  
<td>

R

</td>  
<td>

UNIBO

</td>  
<td>

STW

</td>  
<td>

M20, M30

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

**D9.1**

</td>  
<td>

H – Requirement No.4

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

LAU

</td>  
<td>

N/A

</td>  
<td>

M9

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

**Del.**

**Num.**

</td>  
<td>

**Deliverable name**

</td>  
<td>

**Lead**

</td>  
<td>

**Type**

</td>  
<td>

**Int.**

**Rev/er**

**#1**

</td>  
<td>

**Int.**

**Rev/er**

**#2**

</td>  
<td>

**Delivery date**

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

**D9.2**

</td>  
<td>

POPD – Requirement No.6

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

LAU

</td>  
<td>

N/A

</td>  
<td>

M9

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

**D9.3**

</td>  
<td>

POPD – Requirement No.8

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

LAU

</td>  
<td>

N/A

</td>  
<td>

M9

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

**D9.4**

</td>  
<td>

POPD – Requirement No.9

</td>  
<td>

LDO

</td>  
<td>

ETH

</td>  
<td>

LAU

</td>  
<td>

N/A

</td>  
<td>

M9

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

Table 11: Deliverables Item Reviewers

#  7\. Risk Management

##  7.1. Risk Management Process

The Risk Management Process has started during the proposal preparation and
has been assessed at Project Kick-Off.

The following steps are foreseen:

  * initial brainstorming and preliminary risk identification; 

  

  * preparation of the Project Risk Register. Every entry of the Risk register provides the evaluation 

  

(High, Medium, Low), of the likeliness of the risk (“L.” column), and the
impact of the consequences (“C.” column);

  * for each Risk Item in the Risk register, a mitigation action will be identified; 

  

  * every three months an assessment of the Risk register will be performed, which will result in the update of the Risk register; 

  

  * every six months the Risk Analysis will be performed during the Executive Board; 

  

  * if, during the Risk register assessment (i.e. every three months), a given Risk Item will present a high like hood or a high consequence, and if the mitigation action did not produce any results, a specific meeting will be called to discuss the risk item and update the mitigation action as needed. 

  

Several risks have been already identified. The following table presents the
current risk identification for various work packages. For each item, it is
included the Description of the Risk, the Mitigation Action, The Like hood and
Consequence.  
  
<table>  
<tr>  
<th>

**Task/WP**

</th>  
<th>

**Description of risk**

</th>  
<th>

**Mitigation action**

</th>  
<th>

**L**

</th>  
<th>

**C**

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

**WP1,**

**Management**

</td>  
<td>

General project management risk: insufficient resources and personnel
committed to the project. Partner being in difficulties (company
reorganization), partner withdrawal

</td>  
<td>

Raise the issue urgently with higher level management in partner organization,
ask EB to proposed solutions, in case of withdrawal replace partner.

</td>  
<td>

**L**

</td>  
<td>

**H**

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

**WP2, WP3 Requirement definition and standards**

</td>  
<td>

If the requirements are not precise, there is risk that the implementation of
the components suffers a general slack that would compromise effectiveness of
the toolkit.

</td>  
<td>

This risk is mitigated by the SE approach adopted for the MARISA design and
development, that makes use of a Model Based Systems Engineering and of a
“Architectural Framework” as well by the adoption of the Agile development
with the practitioners

involved as full partners

</td>  
<td>

**M**

</td>  
<td>

**M**

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

**WP3,**

**Interfaces**

</td>  
<td>

Interaction with operational border surveillance systems could pose two
difficulties: a) security restrictions can prevent a seamless integration with
the network envisaged in MARISA, b) daily operations

(planned or unplanned) of existing civil and military systems could delay the
tests envisaged in MARISA

</td>  
<td>

Mitigation action is twofold: a) early engagement with the final users
responsible of the current border surveillance operational systems to assess
the security restrictions. It is highlighted that these practitioners are
already involved in MARISA as full partners, b) flexible contingence plan: in
case one of these systems (for operational reasons) becomes unavailable during
a certain period of the demonstration an alternative time slot is envisaged

</td>  
<td>

**H**

</td>  
<td>

**M**

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

**Task/WP**

</th>  
<th>

**Description of risk**

</th>  
<th>

**Mitigation action**

</th>  
<th>

**L**

</th>  
<th>

**C**

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

**WP3, WP4 and WP5, Technical solution**

</td>  
<td>

There is technical risk in the design phase of MARISA solution that shall be
only detected at verification/validation time.

</td>  
<td>

Trade-off studies planned during the development phase (e.g. prototypes, mock-
ups, simulations) These help in mitigating the risk by analyzing early the
potential technical problems. Moreover the iterative approach will further
mitigate this risk.

</td>  
<td>

**M**

</td>  
<td>

**M**

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

**WP5, risk in software development**

</td>  
<td>

Delay in testing and validation of the software

</td>  
<td>

MARISA relies on software components that are already existing and largely
tested, integrated with new software development. Then, the complexity of the
software to be developed is reduced. Delays will affect individual components
and not the system as a whole.

</td>  
<td>

**L**

</td>  
<td>

**H**

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

**WP6,**

**integration**

</td>  
<td>

The major risk at the integration phase is clearly that a number of components
do not match the agreed specification, functionalities or simply interfaces.

</td>  
<td>

Thanks to SE methods, the complexity of the development would be kept at
manageable level. The possibility to test in advance the MARISA toolkit in
synthetic environment reduces the risk to have troubles during the physical
trials.

</td>  
<td>

**M**

</td>  
<td>

**M**

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

**WP6,**

**integration**

</td>  
<td>

Delays for components provided by WP4 and 5

</td>  
<td>

The integration is made in an incremental way, starting by an initial version
to test the interfaces. Any time a version of the components is stabilized, it
is tested in the integration platform to avoid bottlenecks and identify the
problems early.

</td>  
<td>

**M**

</td>  
<td>

**L**

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

**WP6,**

**integration**

</td>  
<td>

Components not stabilized or not mature for integration

</td>  
<td>

All development WP will test and qualify the components prior to delivery to
WP6.

</td>  
<td>

**L**

</td>  
<td>

**M**

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

**WP7, WP2**

</td>  
<td>

Risk in the availability of real sensible data set to sustain the trials
impact

</td>  
<td>

Joint definition of trials during WP2, reduces the risk for misalignment
between trials objectives and practitioners data availability

</td>  
<td>

**M**

</td>  
<td>

**M**

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

**WP7, WP2**

</td>  
<td>

Demonstrated solution not fully in line with end user constraints

</td>  
<td>

End users involvement in all project phases. High number of end users with
dedicated budget ensures high average level of consultation in due time. WP7
will be performed in two phases, 1) with the toolkit providing a subset of
services, 2) with the toolkit in its final configuration. The feedback of the
first phase will be analyzed and incorporated in the final MARISA toolkit.

</td>  
<td>

**L**

</td>  
<td>

**H**

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

**WP7**

</td>  
<td>

System failure during trials

</td>  
<td>

The components will be tested in laboratories and in a controlled environment
by technical partners to ensure a minimal operation of the system at the start
of each trial phase. More, the trials performance in 2 phases permits possible
malfunctions to be identified at early stage.

</td>  
<td>

**M**

</td>  
<td>

**M**

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

**Task/WP**

</td>  
<td>

**Description of risk**

</td>  
<td>

**Mitigation action**

</td>  
<td>

**L**

</td>  
<td>

**C**

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

**WP8, dissemination**

</td>  
<td>

Delay in dissemination and exploitation of the results due to a disagreement
about IPR

</td>  
<td>

MARISA has nominated an Innovation

Manager in the management structure in order to advise about all IP issues and
propose fair solution

</td>  
<td>

**M**

</td>  
<td>

**M**

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

Table 12: Risk Identification

##  7.2. Risk Areas

The following Risk Areas will be taken into account as reference during the
Risk Analysis.  
  
<table>  
<tr>  
<th>

**Risk Areas**

</th>  
<th>

**Low**

</th>  
<th>

**Medium**

</th>  
<th>

**High**

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

**1**

</th>  
<th>

**2**

</th>  
<th>

**3**

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

_**Technology** _

</td>  
<td>

Developed & used in other projects in maritime or other sectors

</td>  
<td>

Technology qualified not in use.

</td>  
<td>

Only investigation work, new technology

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

_**Standards** _

</td>  
<td>

Developed & used in other projects in maritime or other sectors

</td>  
<td>

Experience in use of applicable Standards not consolidated

</td>  
<td>

Only investigation work, no application, new Standard

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

_**Requirements** _

</td>  
<td>

Well defined, no modification risks or user uncertainty. Some minor areas
needs requirements

definition

</td>  
<td>

For some critical areas the requirements are not

complete and aligned

</td>  
<td>

Critical requirements imprecise or unreachable

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

_**External Interface Definition** _

</td>  
<td>

Well-established External Interfaces definition, with only minor areas to be

defined

</td>  
<td>

The External Interfaces definition is not fully consolidated, with many areas
to be defined

</td>  
<td>

The External Interfaces definition needs to be largely established

during the project

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

_**Complexity of Integration and** _

_**validation** _

</td>  
<td>

Early definition and baseline of Requirements and

External Interface.

Low coupling between S/W component.

Availability of Integration/ validation Platform

</td>  
<td>

Requirements and External Interface baseline with some areas to be defined.
Medium coupling between S/W component.

Availability of Integration/ validation Platform

</td>  
<td>

No Requirements and External ICD baseline.

High coupling between S/W component.

Insufficient availability of

Integration/Validation Platform

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

_**Parallel development** _

</td>  
<td>

Build approach with no parallel development between builds and adequate time
allocated to

development

</td>  
<td>

Build approach with low parallel development between builds and

adequate time allocated

</td>  
<td>

Build approach with high parallel development between build with no margin on
schedule (all activities are on critical path)

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

**Risk Areas**

</td>  
<td>

**Low**

</td>  
<td>

**Medium**

</td>  
<td>

**High**

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

**1**

</td>  
<td>

**2**

</td>  
<td>

**3**

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

_**People Motivation & Commitment ** _

</td>  
<td>

All resources required for project are motivated an committed for the project
success

</td>  
<td>

Limited Motivation and commitment

</td>  
<td>

Team completely non motivated and committed

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

_**Schedule** _

_**Constraints** _

</td>  
<td>

Schedule with critical path, no particular schedule

shifting forecast

</td>  
<td>

Schedule under control with precise critical areas, some criticality may
create schedule impacts

</td>  
<td>

Schedule very critical and/or unfeasible based S/W size and

complexity

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

_**Supplier** _

</td>  
<td>

Supplier already successfully involved in previous project

</td>  
<td>

Supplier not involved in previous project

</td>  
<td>

Supplier not involved in previous project or that in previous project had
major criticality in schedule and/or in performances

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

_**Project Staffing** _

</td>  
<td>

Project understaffed in number or in expertise

</td>  
<td>

Project staffing very insufficient in expertise or in number

</td>  
<td>

Project staffing very insufficient both in number and in expertise

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

_**SW/HW** _

_**Availability** _

</td>  
<td>

Insufficient number of SW licenses or work station

</td>  
<td>

Medium sharing of SW

licenses or work station

</td>  
<td>

Total lack of SW licenses or work station

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

_**Communication** _

</td>  
<td>

Low lack of communication inside the project team

</td>  
<td>

Medium lack of communication inside the project team

</td>  
<td>

Total lack of communication inside the project team

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

Table 13: Risk Areas

#  8\. Data Management

The MARISA Data Management Plan will describe the data management life cycle
for the data to be collected, processed and/or generated by the MARISA
project.

Information about 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 and how data will be curated and preserved (including after the
end of the project) will be described in the D1.8 Data Management Plan due in
M6.