activity 2 – defining sea traffic management statement of...

Activity 2 – Defining Sea Traffic Management

Statement of Work Document No: MONALISA 2.0 - D2.0.2

MONALISA 2.0 — STATEMENT OF WORK 1

Document Status

Authors

NAME ORGANISATION

ANDERS W. TELL LFV

CHRISTIAN DOMFORS-AXELSSON LFV

MATS BERGELIN LFV

CAMILLA STÅLSTAD VIKTORIA SWEDISH ICT

Review

NAME ORGANISATION

Approval

NAME ORGANISATION SIGNATURE DATE

Document History

VERSION DATE STATUS INITIALS DESCRIPTION

1.0 2015-11-06 ACCEPTED C.S.

TEN-T PROJECT NO: 2012-EU-21007-S

DISCLAIMER: THIS INFORMATION REFLECTS THE VIEW OF THE AUTHOR(S) AND THE EUROPEAN COMMISSION IS NOT LIABLE FOR ANY USE THAT MAY BE MADE OF THE INFORMATION CONTAINED THEREIN.


Table of contents 1 Introduction .......................................................................................................... 5

2 Organisation and Management ........................................................................... 5

2.1 Partners and Participants ................................................................................ 6

2.2 Organisation ...................................................................................................... 6

2.3 Roles and Responsibilities ............................................................................... 6

2.3.1 Activity Leader............................................................................................ 7

2.3.2 Assistant Activity Leader ........................................................................... 7

2.3.3 Activity Coordinator ................................................................................... 7

2.3.4 Architect Leader ......................................................................................... 7

2.3.5 Architect ..................................................................................................... 7

2.3.6 Modeller ...................................................................................................... 7

2.3.7 Work Package Leader ................................................................................ 7

2.3.8 Editor .......................................................................................................... 7

2.3.9 Concept Coordinator .................................................................................. 7

2.3.10 Subject Matter Expert ............................................................................. 8

2.3.11 Partner Contribution Manager ............................................................... 8

3 Working Methodology .......................................................................................... 8

3.1 Work Packages ................................................................................................. 9

3.1.1 WP1 - Current Situation Analysis ............................................................ 10

3.1.2 WP2 - STM Performance Targets Development ..................................... 10

3.1.3 WP3 - STM Target Concept ..................................................................... 10

3.1.4 WP4 - STM Strategic Roadmap Development ........................................ 11

3.1.5 WP5 - STM Master Plan ........................................................................... 11

3.1.6 WP6 - Work Programme for MonaLisa 3.0 .............................................. 12

3.1.7 WP7 – Development of a Port CDM Demonstrator ................................ 12

3.2 Iterative work process .................................................................................... 12

4 Tasks and Deliverables ...................................................................................... 13

5 Time Plan ............................................................................................................ 19


6 Progress Monitoring .......................................................................................... 19

7 Quality Management .......................................................................................... 19

8 Information sharing ............................................................................................ 19

9 Document and Configuration Management ..................................................... 19

9.1 Work Products under configuration management ........................................ 20

9.2 Work Product lifecycle .................................................................................... 20

9.3 Version management ..................................................................................... 21

10 Communication Strategy ................................................................................... 21

11 Stakeholder Engagement ................................................................................... 21

12 Risk Management .............................................................................................. 21

13 Budget ................................................................................................................. 21

14 Appendices ......................................................................................................... 22

Annex I – Appointed Roles in Activity 2 ................................................................... 22

Annex II – Time Plan for Activity 2 ........................................................................... 24

Annex III - Budget Activity 2...................................................................................... 25


1 Introduction The purpose of this document is to define the organisation, deliverables and the time plan of MonaLisa 2.0 Activity 2; STM Definition Phase. It describes how the work will be performed in order to reach the objectives that have been established for the Activity.

The statement of work has been based on information contained in the Commission Decision (ANNEXES to the COMMISSION DECISION concerning the granting of Union financial aid for projects of common interest ‘MONALISA 2.0’ - 2012-EU-21007-S - in the field of the trans-European transport network (TEN-T)), as well as in the Project Handbook.

The document covers the entire work process and has been developed as a tool for the management of the Activity. It includes a detailed description of the organisation, roles and responsibilities that apply as well as methodology, deliverables, risk management and limitations in terms of time and budget.

The purpose of Activity 2, Sea Traffic Management Definition phase study, is to deliver a Master Plan for how Sea Traffic Management will be defined, developed and deployed. This Master Plan will be based upon four previous steps, a Current Situation analysis, Performance Target development, a Target Concept Description and a Strategic Roadmap development.

The definition of Sea Traffic Management that was used in the application for funding was:

“The dynamic and integrated management of sea traffic and maritime space (including sea traffic services, management of the maritime space and sea traffic flow management) — efficiently, safely, secure, environmentally and economically sustainable — through the provision of facilities and seamless services in collaboration with all parties and involving seaborne and shore-based functions.”

The exact scope and boundaries for what is meant by Sea Traffic Management within the project will be defined during the project together with activity 2 partners, but also coordinated with other activities in MONALISA 2.0.

2 Organisation and Management This section covers partners and participants, organisation and management in Activity 2. The complete project consortium is listed in the Partner Agreement for the Motorways of the Sea project “MONALISA 2.0”, and the organisation and management of the MonaLisa 2.0 project is described in the Project Handbook.


2.1 Partners and Participants Activity 2 is formed by the following partners:

Carnival Plc, United Kingdom Chalmers University of Technology, Sweden Deutsches Zentrum fuer Luft- und Raumfahrt e.V., Germany Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V., Germany Fundación Valenciaport, Spain IB SRL, Italy Italian Ministry of Infrastructure and Transport, Italy Air Navigation Services of Sweden (LFV), Sweden MARSEC-XL International Ltd, Malta Norwegian Coastal Administration, Norway Swedish Maritime Administration, Sweden Viktoria Swedish ICT AB, Sweden

2.2 Organisation The Activity 2 is managed by an Activity Management Team constituted by the Activity Leader, the Assistant Activity Leader, the Activity Coordinator and the Architect. The Activity Management Team is overall responsible for the deliverables of Activity 2. The activity Management Team reports the progress and forecast for the Activity to the Project Management Team.

The tasks in Activity 2 are divided into 7 different Work Packages. For each work package a Work Package Leader has been appointed. The Work Package leader is responsible for the deliverables connected to the tasks included in the work package.

The tasks within Work Package 3 (WP3) will be performed in 6 different concept groups. The concept groups are responsible for elaborating the concepts; Strategic Voyage Management, Dynamic Voyage Management, Flow Management, Port CDM (Port Collaborative Decision Making), SeaSWIM (Sea System Wide Information Management) and STM as a Holistic Concept, from an operational, business, institutional, informational, system and transversal point of view and for supplying the work package leaders with the information they need regarding the concepts.

To support the development of the content of the concepts, from the different perspectives, complementary expert competences are also contracted.

The architecture team supports the planning, description and modelling of the definition of the STM concept.

2.3 Roles and Responsibilities In Annex I the persons who hold the different roles in Activity 2 are presented.


2.3.1 Activity Leader

The activity leader governs, manages and leads the activity on a day-to-day basis. The activity leader runs the activity on behalf of the project manager within specified constraints and liaises throughout the project with all partners within Activity 2, Project Management Team and the Activity Management Team.

2.3.2 Assistant Activity Leader

The Assistant Activity Leader is part of the Activity Management Team and supports the Activity Leader.

2.3.3 Activity Coordinator

The Activity Coordinator is part of the Activity Management Team and supports the Activity Leader and the Assistant Activity Leader.

2.3.4 Architect Leader

The Architect Leader governs, manages and leads methodological and architecting work and governs modelling work. The Architect Leader supports Activity Management with methodology and architecting work.

2.3.5 Architect

The Architect performs architecting work and supports the architect leader as well as work packages with methodologies and architecting.

2.3.6 Modeller

The Modeller performs modelling work in Activity 2.

2.3.7 Work Package Leader

The Work Package Leader manages and leads Work Package activities. The Work Package Leader is overall responsible for the deliverables included in the Work Package.

2.3.8 Editor

The Editor compiles content supplied by different contributors. The editor is responsible for making the report complete, coherent, consistent and readable.

2.3.9 Concept Coordinator

The Concept Coordinator is responsible for coordinating the work in the concept group.


2.3.10 Subject Matter Expert

The Subject Matter Expert supports the concept groups and the Work Package leaders with expert competence in a specific area. The Subject Matter Expert supplies input to and feedback on the deliverables and hence is an important contributor in the review process.

2.3.11 Partner Contribution Manager

The Partner Contribution Manager is responsible for allocating adequate resources to the project.

3 Working Methodology The objective of Activity 2 is to carry out the Definition Phase for a Sea Traffic Management concept for the maritime sector.

Sea Traffic Management (STM) does not exist for maritime transport in the same way as for aviation. However, there are VTS (Vessel Traffic Services), TSS (Traffic Separation Schemes) and SRS (Ship Reporting System). The aviation domain is currently developing a new advanced Air Traffic Management system within the SESAR programme. In order to take the first step towards Sea Traffic Management, a comprehensive study in the form of a Definition phase study will be required. The methodology for this Definition phase study is very much inspired from the SESAR programme.

In the Definition phase, the framework for STM will be outlined, the target concept elaborated, analyses carried out and a plan for further development and deployment outlined. The experiences from the SESAR programme will be taken on-board in the study, a structured approach to development will be adopted and mistakes by experiences avoided. Close cooperation and adoption of experiences and results from the CISE and other relevant projects will also be incorporated in the study. CISE partners are also involved in MONALISA 2.0, which will ensure efficient collaboration.

The approach in Activity 2 is to:

• Use experience from Air Traffic Management (ATM) domain and the SESAR programme by scaling and adopting experiences and knowledge to the maritime sector, learning from traffic management principles and experiences, structures, processes, methods and concepts, adopting structures, processes and concepts;

• Use cost-benefit analysis to explore and motivate societal outcome, operational performances and performance of technical enablers;

• Use experiences and findings from Activity 1;


• Use experiences and cooperate with other relevant EU programmes;

• Involve domain experts, such as partners, stakeholders and advisors in the definition phase;

• Use an architecting and modelling approach to define and progress MONALISA 2.0 in a structured way and manage internal quality, consistency and coherency;

3.1 Work Packages The workload in Activity 2 is divided into seven different Work Packages; Current Situation Analysis, STM Performance Targets Development, STM Target Analysis, STM Strategic Roadmap Development, STM Master Plan, Work Programme for Development phase and Port CDM Demonstrator.

Figure 1 Work Packages in Activity 2 (WP7 -Port CDM Demonstrator not included)


3.1.1 WP1 - Current Situation Analysis

In Work Package 1 - Current Situation Analysis the current situation of maritime transportation is analysed. This will result in a “snapshot” description of today’s sea transport industry. The work package will also highlight needs, trends and enablers.

This work package includes analysis of current:

• legislations and regulations;

• management structures and decision mechanisms;

• safety regulations;

• existing business models,

• value chains and market;

• key stakeholders and their involvement and collaboration;

• legacy systems;

• information management and information sharing enablers;

• aspects of the human role.

3.1.2 WP2 - STM Performance Targets Development

A performance based approach will drive management decisions towards achieving the vision of the MONALISA 2.0 project. The vision of the Sea Transport Industry will cover key performance areas and their targets; identification of strategic enablers (new or improved) needed to meet the performance targets.

Principles for way forward determining how changes to conduct STM will be identified; these principles will cover e.g. environment, security, the performance partnership, future architecture STM systems (scalability, interoperability).

This work package includes analysis and elaboration of:

• performance framework including e.g. performance targets, key performances areas;

• vision and goals for STM.

3.1.3 WP3 - STM Target Concept

Based on the findings in the current situation analysis, target concept(s) for Sea Traffic Management will be developed; driven by the performance targets achieving the MONALISA 2.0 vision and goals. On-going concept developments will also be taken into consideration for further elaboration of the STM target concept(s).

This work package includes definition of target:


• legislations and regulations;

• management structures and decision mechanisms;

• safety regulations;

• business models, value chains and market;

• key stakeholders and their involvement and collaboration;

• STM systems;

• information management and information sharing enablers;

• aspects of the human role; and

• aspects impacting STM in a transversal manner;

3.1.4 WP4 - STM Strategic Roadmap Development

The STM Strategic Roadmap Development will analyse the STM Current Situation, Performance Targets and STM Target Concepts in order to describe and establish a shared vision of the overall transition sequence to implement the STM Target Concept that was defined to deliver the STM performance targets.

This work package identifies the operational improvements and enablers to be deployed as well as the development activities needed to support them. The main target with the strategy vision is to describe and demonstrate the feasibility of the transition sequence to realise the STM Target Concept.

A STM Strategic Roadmap will be developed providing a frame for the development of a detailed and concrete STM Master Plan.

3.1.5 WP5 - STM Master Plan

This work package aims at developing the STM Master plan for implementing Sea Traffic Management in Europe, by further elaborating and detailing the STM Strategic Roadmap, hence providing a link to the STM Work Programme. The STM Master Plan supports a timely and consistent implementation of the STM Target Concept at European level, and an evolutionary path, in which performance closely matches the targets, optimizes the benefits and secures the financial viability of its implementation and deployment by stakeholders.

The STM Master Plan encompass the lifecycle between feasibility up to and including deployment and are supported by an analysis of the associated benefits, funding and financing aspects as well as the related risks. Both the time component of the roadmap, Master Plan and the associated benefits are critical for the success of the future phases of the STM programme. An economic scheme is established which addresses the relationship between the required investments for all stakeholders and the commitment to achieve cost-effectiveness and quality of performance targets.


3.1.6 WP6 - Work Programme for MonaLisa 3.0

This work package aims at developing the Work programme that defines project items necessary to support the development of the STM Target Concept by the execution of the Strategic STM Roadmap and more specifically the STM Master Plan. This includes development/deployment of existing systems, development of systems, which are almost mature, applied research to refine the concept and develop technical solutions and longer term research for the more advanced concepts and technologies.

The objective of the Work programme document is to produce a “project definition” which provides the confidence, before making any major commitment to the programme, that the development phase can be launched.

3.1.7 WP7 – Development of a Port CDM Demonstrator

Work package 7 – Development of a Port CDM Demonstrator was not part of the original project specification but added during the project process after having been identified as an essential part of a STM system.

The Port CDM (Collaborative Decision Making) concept aims at increasing the ability to determine the accuracy of port approaches by and for involved actors. The overall goal is to provide approaching vessels with accurate estimations of when it is desired that they arrive to the traffic area and consequently arrive at, and later on departure from, berth.

Port CDM is defined by a number of information sharing services. In this work package the first version of these services are developed and demonstrated in two ports. The services are based on information from the numerous systems that different actors use to plan and coordinate their efforts in port approaches.

3.2 Iterative work process The work in activity 2 will be carried out in three main iterations and hence deliverables will be reported in three main releases. Internally in the activity each of the iterations will in turn be divided into shorter iterations, assuring that the deliverables are continuously updated and improved during the entire process.

The work packages have to some degree a sequential dependency, i.e. in general a higher work package number is dependent on input from a lower one. Focus during the first iteration will hence be on the deliverables connected to WP0-2 while iteration 2 will focus more on deliverables in WP3 and iteration 3 on deliverables in WP4-7.


4 Tasks and Deliverables The tasks and deliverables of Activity 2 are based on what is stated in the Commission Decision and in the MonaLisa 2.0 Strategic Action Plan and are listed in detail in the table below. Main deliverables are highlighted by grey background colour.

Sub Act

Task ID

Task Description Deliverable ID

Deliverable Name

WP0

T-2.0.1 Develop Request for Work

D2.0.1 Request for work

Outline MONALISA 2 Activity 2 Business Case

T-2.0.2 Develop Statement of Work

D2.0.2 Statement of work

Project Management Plan

Communication Strategy

Stakeholder Engagement Strategy

Quality Management Strategy

Risk Management Strategy

MONALISA 2 Activity 2 Business Case

D2.0.2-7 Communication Material

T-2.0.3 Develop Working and Development Approaches and Methodology

MONALISA 2 Activity 2 Working Methodology

T-2.0.4 Develop overall Activity 2 working and development method

MONALISA 2 Activity 2 Working and Development Method

T-2.0.5 Develop Current situation and Target concept working and development method

Current and Target Working and Development Method


T-2.0.6 Develop Performance Target approach and method

Performance Framework Approach and Method

T-2.0.7 Develop STM Strategic Roadmap Approach and Method

D2.4.1 STM Strategic Roadmap Approach and Method

T-2.0.8 Develop STM Master Plan Approach and Method

STM Master Plan Approach and Method

T-2.0.9 Develop STM Work Programme Approach and Method

STM Work Programme Approach and Method

T-2.0.10

Develop and maintain Architecture Framework

D2.0.3 STM Architecture Framework

T-2.0.11

Develop and maintain Common Reference Project Information Model

Common Reference Project Information Model

T-2.0.12

Develop and maintain Architecture Description

D2.0.4 STM Architecture Description

T-2.0.14

Manage iterations

WP1

T-2.1.1 Develop STM Current Analysis Deliverable

D2.1.1 STM - The current situation

->WP0 T-2.0.5


T-2.1.2 Analyse and Describe Current STM Institutional View

Current Institutional Description

T-2.1.3 Analyse and Describe Current STM Business View

Current Situation Business Case and Cost Benefit Considerations


T-2.1.4 Analyse and Describe Current Current Business Description

Current Business Description

T-2.1.5 Analyse and Describe Current STM Operational View

Current Operational Description

T-2.1.6 Analyse and Describe Current STM Systems Technical & Technology View

Current Systems Technical & Technology Description

T-2.1.7 Analyse and Describe Current Information Systems and Information Technology View

Current Information Systems and Information Technology Description

T-2.1.8 Analyse and Describe the Role of the Human

Current Human Aspects Description

T-2.1.9 Analyse and Describe Transversal Aspects

Current Transversal Aspects Description (safety, environment, security etc.)

->WP0 T-2.0.10

STM Architecture Framework

T-2.1.10

Update Architecture Description

STM Architecture Description::Current Situation

WP2

T-2.2.1 Develop Performance Target

D2.2.1 STM -Performance Framework

->WP0 T-2.0.6

Performance Target Approach and Method

T-2.2.2 Develop the Vision and Goals of the future Sea Traffic Management

Vision and Goals Description

T-2.2.3 Develop Strategic Enablers

Strategic Enablers Description


T-2.2.4 Describe strategic principles for the way forward

Strategic Principles for the way forward Description

T-2.2.5 Develop Performance Assessment Case

Performance Assessment Case

->WP0 T-2.0.10

Updated STM Architecture Framework

T-2.2.6 Update Architecture Description

STM Architecture Description::Performance Target

WP3

T-2.3.1 Develop STM Target Deliverable

D2.3.1 STM - The Target Concept

->WP0 T-2.0.5


T-2.3.2 Analyse, Describe and Develop Target STM Institutional View

D2.3.1-1 Target Institutional Description

T-2.3.3 Analyse, Describe and Develop Target STM Business View

D2.3.1-2 Target Concept Business Case and Cost Benefit Analysis

T-2.3.4 Analyse, Describe and Develop Target Business Description

D2.3.1-3 Target Business Description

T-2.3.5 Analyse, Describe and Develop Target STM Operational View

D2.3.1-4 Target Operational Description

T-2.3.6 Analyse, Describe and Develop Target STM Systems Technical & Technology View

D2.3.1-5 Target Systems Technical & Technology Description

T-2.3.7 Analyse, Describe and Develop Target Information Systems and Information Technology View

D2.3.1-6 Target Information Systems and Information Technology Description


T-2.3.8 Analyse, Describe and Develop the Role of the Human in STM

D2.3.1-7 Target Human Aspects Description

T-2.3.9 Analyse, Describe and Develop Target Transversal Aspects

D2.3.1-8 Target Transversal Aspects Description (safety, environment, security etc)

T-2.3.10

Develop Performance Assessment Case

D2.3.1-9 Target Concept Performance Assessment Case

T-2.3.11

Analyse and Describe Target Concept Validation Results

Target Concept Validation Results Description

T-2.3.12

Develop Formal Safety Assessment Case

D2.3.1-11 Formal Safety Assessment Case

->WP0 T-2.0.10


T-2.3.13

Update Architecture Description

STM Architecture Description::Target Concept

WP4

T-2.4.1 Develop STM Strategic Roadmap

Included in D2.5.1

->WP0 T-2.0.7

STM Strategic Roadmap Approach and Method

T-2.4.2 Develop Sequence Transition Strategy Description

Sequence Transition Strategy Description

T-2.4.3 Develop Stakeholder Business Case Description (per Improvement Package)

Stakeholder Business Case Description (per Improvement Package)

->WP0 T-2.0.10



->WP0 T-2.0.11



STM Architecture Description::Strategic Roadmap

WP5

T-2.5.1 Develop STM Master Plan

D2.5.1 STM Master Plan

->WP0 T-2.0.8

STM Master Plan Approach and Method

T-2.5.2 Develop Detailed Stakeholder Business Case description

Detailed Stakeholder Business Case description

T-2.5.3 Develop Risk management plan

Risk management plan

T-2.5.4 Develop Outline Stakeholder deployment roadmap

Outline Stakeholder deployment roadmap

T-2.5.5 Develop Financing and funding

Financing and funding

T-2.5.6 Develop Electronic STM Master Plan

D2.5.2 Electronic STM Master Plan

->WP0 T-2.0.10


->WP0 T-2.0.11



STM Architecture Description::STM Master Plan

WP6

T-2.6.1 Develop STM Work Programme

(Included in D2.5.1)

->WP0 T-2.0.9

STM Work Programme Approach and Method


->WP0 T-2.0.10



STM Architecture Description::STM Work Programme

5 Time Plan The time plan for Activity 2 is presented in Annex II.

6 Progress Monitoring The progress of Activity 2 is monitored internally through regular Work Package Leader coordination meetings and Concept coordinator meetings.

The progress of Activity 2 is also monitored on a Project Management level through regular PMT meetings and quarterly technical reports.

7 Quality Management To ensure satisfactory quality of the deliverables each release will be preceded by an internal review process during which the deliverable will be reviewed and approved by all partners involved in Activity 2. The review process is described in detail in document “ML2 Act2_Review process.pptx”1. Each review will be documented according to the “ML2 Act2_Review Form template.xlsx”2.

8 Information sharing Activity 2 uses Projectplace for document handling, according to Monalisa 2.0 project directions.

9 Document and Configuration Management The following requirements apply for all documents created in Activity 2:

− Project, activity and version should be part of the filename to be clearly identifiable outside Projectplace, it’s foreseen that document will also be mailed between parties.

1 https://service.projectplace.com/pp/pp.cgi/r1041919192 2 https://service.projectplace.com/pp/pp.cgi/r1041644236


− Document should be uploaded to correct folder on Projectplace when ready for sharing, version management should be engaged

− Document should be locked/unlocked on Projectplace to indicate ongoing work

9.1 Work Products under configuration management A Work Product is an artefact of interest to the project. Work product are documents, reports, sections in documents, models, diagrams, data sets, catalogues, etc. that are created, modified, or referred to during the project.

A Deliverable is a work product that is recognized in methodology, and/or in task definitions as an output.

A Main Deliverable is a top level Deliverable identified and recognized as a formal output of the project. Main deliverables should be approved by all Activity 2 partners.

A Supplement is a work product that underpins the deliverables.

9.2 Work Product lifecycle Lifecycle states of Work Products (Main deliverables and deliverables):

− Identified: A need for the work product has been identified.

− Started: The work product has been created and some content may exist, but parts may be missing and information incomplete. Preconditions (specification, requirements, methodological, architectural, working arrangement and others) for working with the work product have not all been met.

− Frozen development: All work on adding new features is suspended, shifting the effort towards fixing issues, integration, consolidation with adjacent work streams and improving quality. Note: The addition of new features may have a disruptive effect on other parts of the activity, due both to the introduction of new, untested parts or resources and to interactions with other features; thus, a feature freeze helps improve the activity's deliverables.

− Completed: The development of the work product has been completed according to its specification and requirements.

− Review: The work product is undergoing review, or validation.

− Accepted: The work product has passed the necessary reviewing, or validation mechanism required to consider it of acceptable quality.

− Approved: The work product has been formally approved.


− Delivered: The work product has been formally delivered, with delivery specific material developed, material has been archived, lessons learned has been captured, and metrics are made available.

The following diagram illustrates the primary flow between states.

9.3 Version management Version management starts on 0.1. Versions are stepped on second level in lifecycle states Started, Frozen, Completed and Review, 0.1, 0.2 … 0.9, 0.10, 0.11 etc.

When document changes state to Accepted, the first level is increased, e.g. 1.0, 2.0 etc. The version shall be visible in the filename and the document header. The lifecycle state shall be visible in the document header.

10 Communication Strategy According to the Project Handbook MonaLisa 2.0 the “Communication Plan MONALISA 2.0” constitutes the basis for all communication means in the project.

11 Stakeholder Engagement Stakeholders are handled on Project Management level. To ensure that important stakeholders are involved in the entire development process different advisory groups are used. Advisory Groups are defined in the Project Handbook.

12 Risk Management Identified project risks will be documented in the “ML2-Act2_Risk List.xls” document. A person responsible for monitoring the risk will be appointed and the document will also be followed up regularly during Activity Management meetings.

13 Budget The budget for activity 2 is presented in Annex III.


14 Appendices

Annex I – Appointed Roles in Activity 2 Activity Leader – Mikael Hägg, Chalmers University of Technology

Assistant Activity Leader – Mikael Lind, Viktoria Swedish ICT

Activity Coordinator – Camilla Stålstad, Viktoria Swedish ICT

Architect Leader - Mikael Olofsson, LFV

Architect – Sandra Haraldson, Viktoria Swedish ICT, Beata Myhrer, LFV

Modeller – Sandra Haraldson. Viktoria Swedish ICT, Beata Myhrer, LFV, Mikael Olofsson, LFV

Work Package Leaders:

WP1 – Caterina Cerrini, IB SRL

WP2 – José Andres Gimenez, Valencia Port Foundation

WP3 – Mikael Lind, Viktoria Swedish ICT

WP4 – Per-Erik Holmberg, Viktoria Swedish ICT

WP5 – Björn Andreasson, Swedish Maritime Administration

WP6 – Björn Andreasson, Swedish Maritime Administration

WP7 – Mikael Lind, Viktoria Swedish ICT

Editors:

WP3 – Anders Dalén, Viktoria Swedish ICT

Concept Coordinators:

Strategic Voyage Management – Sten Terje Falnes, Norwegian Coastal Administration

Tor-Inge Miljeteig, Norwegian Coastal Administration

Dynamic Voyage Management – Ulf Svedberg, Swedish Maritime Administration

Björn Andreasson, Swedish Maritime Administration

Flow Management – Mikael Hägg, Chalmers University of Technology

Gabriel Ferrús, Valencia Port Foundation

Port CDM – Mikael Lind, Viktoria Swedish ICT


Sandra Haraldson, Viktoria Swedish ICT

SeaSWIM – Geir Fagerhus, Marsec XL

Krystyna Wojnarowicz, Marsec XL

STM as a Holistic Concept – Mikael Hägg, Chalmers University of Technology

Mikael Lind, Viktoria Swedish ICT

Subject Matter Experts:

Operational – Peder Alber, LFV (ATM Subject Matter Expert)

Åke Wall, LFV (ATM Subject Matter Expert)

Legal – Lars-Göran Malmberg, Göteborgs Universitet

Business - Heather A. Smith, Queen's School of Business

Niels Björn - Andersen, Copenhagen Business School

Institutional – Anders Brödje, Swedish Maritime Administration

Partner Contribution Managers:

Carnival Plc - Mike Collier Chalmers University of Technology – Mikael Hägg Deutsches Zentrum fuer Luft- und Raumfahrt e.V - Matteo Berioli Fraunhofer – Ole John Fundación Valenciaport- José Andres Gimenez IB SRL- Caterina Cerrini Italian Ministry of Infrastructure and Transport – Mario Dogliani Air Navigation Services of Sweden (LFV) – Mats Bergelin MARSEC-XL International Ltd - Geir Fagerhus Norwegian Coastal Administration - Sten Terje Falnes Swedish Maritime Administration – Magnus Sundström Viktoria Swedish ICT AB – Mikael Lind


Annex II – Time Plan for Activity 2 Milestones for Activity 2

Month Milestone Result

2014 -02

M04 Release1 of main milestone deliverables from iteration 1, with special focus on Current Situation Analysis

2014-12 M05 Release 2 of main milestone deliverables from iteration 2, with special focus on STM Performance Target and STM Target Concept

2015-12 M06 Release 3 of main milestone deliverables from iteration 3, with special focus on STM Strategic Roadmap, STM Master Plan and STM Work Programme.


Annex III - Budget Activity 2


39 partners from 10 countries

taking maritime transport into the digital age

By designing and demonstrating innovative use of ICT solutions

MONALISA 2.0 will provide the route to improved

SAFETY - ENVIRONMENT - EFFICIENCY

Swedish Maritime Administration ◦ LFV ◦ SSPA ◦ Viktoria Swedish ICT ◦ Transas ◦ Carmenta ◦ Chalmers University of Technology ◦ World Maritime University ◦ The Swedish Meteorological and Hydrological Institute ◦ Danish Maritime Authority ◦ Danish

Meteorological Institute ◦ GateHouse ◦ Navicon ◦ Novia University of Applied Sciences ◦ DLR ◦ Fraunhofer ◦ Jeppesen ◦ Rheinmetall ◦ Carnival Corp. ◦ Italian Ministry of Transport

◦ RINA Services ◦ D’Appolonia ◦ Port of Livorno ◦ IB SRL ◦ Martec SPA ◦ Ergoproject ◦ University of Genua ◦ VEMARS ◦ SASEMAR ◦ Ferri Industries ◦ Valencia Port Authority ◦

Valencia Port Foundation ◦ CIMNE ◦ Corporacion Maritima ◦ Technical University of Madrid ◦ University of Catalonia ◦ Technical University of Athens ◦ MARSEC-XL ◦ Norwegian Coastal

Administration

www.monalisaproject.eu


http://www.monalisaproject.eu/

activity 2 – defining sea traffic management statement of...

Documents