d1.1 management plan - mosesmoses-project.eu/.../uploads/2017/08/moses-d1.1-management_pla… ·...

Managing crOp water Saving with Enterprise Services

Project funded by the European Union’s Horizon 2020 research and innovation programme WATER-1a-2014: First application and market replication

Grant agreement H2020-642258

D1.1 Management plan

WP 1 – Management Nature: Report

Dissemination level: Public

Moses Project (H2020-642258)

Document Title: D1.1 Management plan Release: 1, 15/02/2016

Page: 2 of 20

Authors table

Name (Company/Entity) Date

Written by: A. Amodio (Esri) 15/02/2016

Contributors: …………...

Reviewed/ Authorized by:

A. Amodio (Esri) 17/02/2016

Revision Table

Issue date Release

17/02/2016 1

Detailed Revision Table

Release # Page(s) Change(s) with respect to the previous release

NA NA NA

The document is available to authorized users on the SyGMA (System for Grant MAnagement), managed by EC; the tool is available at the following link: https://ec.europa.eu/research/participants/grants-app/reporting/DLV-642258 Public documentation is also available at the following link: http://www.moses-project.eu/download/

https://ec.europa.eu/research/participants/grants-app/reporting/DLV-642258

http://www.moses-project.eu/download/



Page: 3 of 20

Table of Contents 1 Introduction .................................................................................................................................. 5

1.1 Moses project ........................................................................................................................ 5

1.2 Purpose of the document ...................................................................................................... 5

1.3 Definitions, acronyms and abbreviations.............................................................................. 6

1.4 Applicable and reference documents ................................................................................... 6

2 Project plan ................................................................................................................................... 7

2.1 Activities breakdown and development logic ....................................................................... 7

2.2 Deployment plan ................................................................................................................. 12

2.3 Project schedule .................................................................................................................. 12

2.4 Milestones ........................................................................................................................... 15

2.5 Deliverable ........................................................................................................................... 16

3 Team and contact information ................................................................................................... 17

4 Documentation review workflow ............................................................................................... 18

5 Collaboration and management tools ........................................................................................ 19

5.1 Introduction ......................................................................................................................... 19

5.2 Collaborative tools .............................................................................................................. 19

5.2.1 Google Drive ................................................................................................................. 19

5.2.2 Dropbox ........................................................................................................................ 19

5.2.3 Microsoft Onedrive ...................................................................................................... 19

5.3 Management and development tools ................................................................................. 20

5.3.1 Trello ............................................................................................................................ 20

5.3.2 Atlassian Jira ................................................................................................................. 20

5.4 Moses website ..................................................................................................................... 20

5.5 Participant portal ................................................................................................................. 20



Page: 4 of 20

Table of Figures Figure 1: Moses concept and work plan .............................................................................................. 7

Figure 2: Moses Work Breakdown Structure ....................................................................................... 9

Figure 4: Overall Gantt chart of MOSES project. ............................................................................... 12

Figure 5: Schedule of lines of activities WP2 Engineering ................................................................. 13

Figure 6: Schedule of line of activities WP3 Services and DSS Platform ........................................... 13

Figure 7: Schedule of line of activities WP4 First Application and WP5 Scaling-Up and Replication 14



Page: 5 of 20

1 Introduction

1.1 Moses project

The background of the project, its concepts and the technologies that will be exploited are stated into the document in [AD1], “Moses Project Grant Agreement and Annexes”, Horizon 2020 Grant Agreement No. 642258. The main objective of MOSES is “to put in place and demonstrate at the real scale of application an information platform devoted to water procurement and management agencies to facilitate planning of irrigation water resources”. To achieve these goals, the MOSES project combines in an innovative and integrated platform a wide range of data and technological resources: EO data, probabilistic seasonal forecasting and numerical weather prediction, crop water requirement and irrigation modelling and online GIS Decision Support System. The project has been proposed by the Moses Consortium, which is composed by the following entities:

1. Esri Italia Spa (Esri), Italy 2. Agenzia Regionale per la Prevenzione, l'Ambiente e l'Energia dell'Emilia-Romagna (Arpae),

Italy 3. Agencia Estatal de Meteorologia (AEMET), Spain 4. Institutul National de Hidrologie Si Gospodarire a Apelor (INHGA), Romania 5. Administratia Nationala de Meteorologie R.A. (ANM), Romania 6. Alma Mater Studiorum - Universita Di Bologna (UNIBO), Italy 7. Asociacion Feragua de Comunidades de Regantes de Andalucia (FER), Spain 8. Serco Belgium Sa (SERCO), Belgium 9. Technische Universiteit Delft (DUT), Netherlands 10. Universidad de Castilla - La Mancha (UCLM), Spain 11. Universite Chouaib Doukkali (UCD), Morocco 12. Agromet Srl (AM), Italy 13. Consorzio di Bonifica di Secondo Grado per il Canale Emiliano Romagnolo (CER), Italy 14. Aliara Agrícola Sl (ALI), Spain 15. Aryavarta Space Organization (ASO), India 16. Consorzio di Bonifica della Romagna (CBR), Italy1

The project started on the 1st of July 2015, while the Kick-Off meeting took place in Rome on the 14th and 15th of July 2015.

1.2 Purpose of the document

The purpose of this document is to present the Moses management plan, including team organization and contact information.

1 Partner proposed with the Amendment AMD-642258-1, starting from the 1st of January 2016



Page: 6 of 20

The objective of the Management Plan is to describe the approach to the project management, to the organization of the demonstration and scientific activities to be performed during the project lifecycle. This plan then describes the execution, management and control of the project, in particular referring to the demonstration and scientific activities. The document will be re-issued any time it is required, evolving during the lifespan of the project. A plan for MOSES system assessment and development will be worked out in view of MOSES adoption at water irrigation management level.

1.3 Definitions, acronyms and abbreviations

The following table lists acronyms and abbreviations used in this document.

AD Applicable Document

DA Demonstration Area

DSS Decision Support System

EASME European Agency for Small and Medium Enterprises

EO Earth Observation

GIS Geographical Information System

NA Not Applicable

RD Reference Document

SYGMA System for Grant MAnagement

WBS Work Breakdown Structure

WP Work Package

Table 1: List of acronyms and abbreviations

1.4 Applicable and reference documents

The following documents are applicable: [AD1] “Moses Project Grant Agreement and Annexes”, Horizon 2020 Grant Agreement No. 642258 [AD2] “AMENDMENT to Moses Project Grant Agreement and Annexes”, Horizon 2020 Reference

No. AMD-642258-1 The following documents are used as references: [RD1] Moses Consortium Agreement, version 2, 2015-05-18



Page: 7 of 20

2 Project plan

2.1 Activities breakdown and development logic The definition of the activities to be performed within the lifecycle of the Moses project derives directly

from the approach described in Figure 1.

COMMUNICATION, DISSEMINATION

AND IMPACTS

MOSES ENGINEERING

MOSES SERVICES & DSS PLAFORM

MANAGEMENT

Early Season

Crop Mapping

In-Season Water

Demand Monitoring

Irrigation Forecasting

DUT

ESRI

UNIBO

ARPA-ER

ARPA-ER

DUT

Seasonal

Probabilistic

Forecasting

ANM

ESRI

SCALING-UP AND REPLICATION

SERCO

FIRST APPLICATION ARPA-ER

Figure 1: Moses concept and work plan



Page: 8 of 20

The project will loosely follow an agile2 development approach where engineering, implementation,

integration and operation phases are cyclically performed.

The first year of the project is devoted to the engineering and implementation of the first version of MOSES

platform; in the following six months, a full cycle is completed with the first application of MOSES services

over the Italian DA. Meanwhile, the other DAs prepare their local activities by following the setup of Italian

DA and receiving dedicated training.

The second half of the project is dedicated to the scaling-up and replication of MOSES services to the Spanish,

Romanian and Moroccan DAs, which implies a second iteration of the development lifecycle. At the same

time, the Italian DA is ready to enter in the full pre-operation phase.

During the last six months, the final (Release Candidate) version of the MOSES platform is released and it is

considered ready to enter in operation.

Management and Dissemination activities are performed for the whole project duration, assuring continuity

in the supervision of project, coordination of partners and diffusion of the results to the scientific and

commercial community.

The Work Breakdown Structure derives then directly from the presented approach, and is shown in Figure 2.

2 Agile Software Development is a set of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.



Page: 9 of 20

Figure 2: Moses Work Breakdown Structure

2.1.1.1 WP1 - Management

The management structure for the MOSES project foresees different coordination figures, which will be

active for the whole project duration:

the project coordinator;

the scientific coordinator;

the demo service coordinator.

Such organization reflects into the WP1 subtasks distribution.

The coordination team will implement all along project lifecycle the routines for the project management,

the relationship with European Commission and the coordination of scientific activities. This should

guarantee the success of the system implementation and the demonstration activities.

MOSES

Management

Project management

ScientificGroup

Demo coordination

MOSES Engineering

Requirements

Design

Service definition

LCA analysis

MOSES Services and DSS Platform

Early-seasoncrop mapping

Seasonalprobabilisticforecasting

Irrigationforecasting

In-season water demand

monitoring

DSS implementation

MOSES platform integration and

test

First Application

Setup and training

First application

Service assessment

Scaling-up and Replication

Italy pre-operation

Spainreplication

Romania replication

Morocco replication

Communication, Dissemination and Impacts

Communication

Market and business plan

MOSES impact analysis

MOSES exploitation

platform



Page: 10 of 20

The project manager will also deal with contractual aspects, related in particular to the financial and

administrative issues of the project. He will be responsible for the accomplishment of project plan and

contractual obligations.

Furthermore, the Management Support Team, consisting of the project coordinator and the work

packages leaders, will assist and facilitate the work of the coordinator for executing the decisions of

the General Assembly3 as well as the day-to-day management of the Project.

2.1.1.2 WP2 - Engineering

The collection of the user requirements, according to the specific needs of the different MOSES

demonstration areas, is the starting point of the project. This phase will lead to the architectural and service

definition, where some critical elements such as Design Definition File and service definition will be of

particular importance for pushing MOSES services towards the real market.

The system will include the following elements (see Figure 1):

- Early-season crop mapping

- Seasonal probabilistic forecasting

- Irrigation forecasting

- In-season water demand monitoring

- DSS platform

The design of the MOSES system will be the main deliverable of WP2.

2.1.1.3 WP3 – Services and DSS platform

The MOSES platform will be implemented starting from the design documents, which are output of the WP2

activities. Each subtask of the WP3 is devoted to the implementation/customization of the high-level

functionalities of the system. An agile approach will be used for the platform engineering, implementation,

integration and testing, leading to the release of several versions of MOSES platform. As a consequence of

this approach, the WP3 activities will not be strictly time-limited, but will be distributed during the project

lifecycle.

2.1.1.4 WP4 - First application

The first application of MOSES services will be performed for the Italian DA.

WP4 activities start with its setup, the procurement of the necessary EO data and the training activities for

the other DAs. Once the first version of the MOSES platform will be released from WP3, the first application

demonstration activities will be performed.

Finally, at the end of demonstration activities, a service assessment has been planned for improving the

service effectiveness for the demo replication in the Spanish, Romanian and Moroccan DAs.

3 The General Assembly is the ultimate decision-making body of the consortium, and consists of one representative of each Party.



Page: 11 of 20

2.1.1.5 WP5 - Scaling-up and replication

WP5 activities deal with a second iteration of MOSES services for the Italian DA, and the replication of MOSES

services for the Spanish, Romanian and Moroccan DAs; in fact, the activities for all the DAs are performed in

parallel. The MOSES products, generated over the DAs, will be compared with local ground truth in order to

validate and calibrate the models used.

2.1.1.6 WP6 - Communication, Dissemination and Impacts

Particular attention will be given to the results dissemination within the scientific and commercial

communities. Dissemination activities foreseen are the participation to scientific conferences and

workshops, the setup of the project web site maintained along the project life, and the organization of two

workshops. MOSES impacts and business opportunities will be considered and analysed in a specific activity.

The workshops will be organized after the first and the second campaigns.



Page: 12 of 20

2.2 Deployment plan [Example: The project involves deploying an application to state health partners. This section would discuss the approach for rolling out the application

to the end users, including conducting environment assessments, developing memorandums of understandings, hardware/software installation, data

conversion.]

2.3 Project schedule The following drawing contains the Gantt chart for the project. The project officially started on July 1, 2015, while the Kick-Off meeting took place in Rome on July 14 and 15,

2015. The chart will be updated into this document to reflect the changes occurred.

Figure 3: Overall Gantt chart of MOSES project.



Page: 13 of 20

Figure 4: Schedule of lines of activities WP2 Engineering

Figure 5: Schedule of line of activities WP3 Services and DSS Platform



Page: 14 of 20

Figure 6: Schedule of line of activities WP4 First Application and WP5 Scaling-Up and Replication



Page: 15 of 20

2.4 Milestones

[Example of schedule management approach: Establish a baseline within the first two weeks

of the project and monitor progress against the baseline on a weekly basis. The Project

Manager will be responsible for ensuring the project schedule is updated with the latest

information and never more than three business days out of date. For variances on executive

milestones greater than 10%, the project may choose to use guidance specified by CPIC. See

the CDC UP Project Schedule document for more guidance on project schedules and for

Project Schedule templates.]

The reviews/milestones listed into the document in [AD1] are reported the following table:

Milestone number Milestone name Delivery date

MS1 Kick-Off 1

MS2 Preliminary Design Review 7

MS3 First Application Readiness Review 12

MS4 Intermediate Review 19

MS5 Pre-operation Readiness Review 24

MS6 Pre-operation Assessment 31

MS7 Final Review 36

Table 2: Milestone list



Page: 16 of 20

2.5 Deliverable

In the following table there is the list of deliverable.

Del. # Deliverable Title Delivery date (mo. after T0)

D1.1 Management Plan PDR (M7) eventually reviewed

before any milestones

D1.2 Data Management Plan PDR (M7)

D2.1 Requirements Document PDR (M7)

D2.2 Design Definition File PDR (M7); PRR (M24); PA (M31)

D2.3 Life-Cycle Analysis Document PRR (M24); FR (M36)

D2.4 Service Definition Document PDR (M7)

D3.1 Crop mapping package FARR (12); PRR (24); PA (31)

D3.2 Seasonal probabilistic forecasting package FARR (M12); PRR (M24); PA (M31)

D3.3 Irrigation forecasting package FARR (M12); PRR (M24); PA (M31)

D3.4 In-season water demand monitoring package FARR (M12); PRR (M24); PA (M31)

D3.5 MOSES DSS package FARR (M12); PRR (M24); PA (M31)

D4.1 MOSES First Setup Report FARR (M12)

D4.2 Training Activities Report IR (M19)

D4.3 Service Assessment Report IR (M19)

D5.1 Demo IT Preoperation Package Report IR (M19); PA (M31)

D5.2 Demo RO Replication Report PA (M31)

D5.3 Demo ES Replication Report PA (M31)

D5.4 Demo MO Replication Report PA (M31)

D6.1 Communication and Dissemination Plan PDR (M7); IR (M19)

D6.2 Communication and Dissemination Report & Material IR (M19); FR (M36)

D6.3 Impact analysis and Business Plan IR (M19); FR (M36)

D6.4 Integrated MOSES Exploitation Platform IR (M19); FR (M36)



Page: 17 of 20

3 Team and contact information In the following tables the technical and administrative point of contact for the project.

For administrative/financial matters

Name : Mr. Angelo Amodio (project coordinator) Phone : +39 06 40696210 Fax: +39 06 40696333 E-mail : [email protected]

For technical matters and general project information

[email protected] [email protected] [email protected] [email protected]

mailto:[email protected]







Page: 18 of 20

4 Documentation review workflow A specific review workflow will be followed by the project team before any delivery. The workflow is composed by two distinct phases which balance the review effort over the project sub-teams that are involved in the deliverable creation: a first deliverable drafting phase circumscribes the technical review effort to only the deliverable direct contributors and a second final review phase brings the deliverable draft to the attention of both the EC-EASME and the rest of the technical project team before of the final deliverable issue via upload on the SyGMA (System for Grant MAnagement). Here is the detailed description of the documentation review phase:

1. DELIVERABLE DRAFTING PHASE - the deliverable lead beneficiary acts as interface between the technical sub-teams that contribute to the deliverable: this means that the lead beneficiary takes care of organizing all of the activities (e.g. collecting and harmonizing contributions, setting up partial reviews with document contributors) that are needed to complete a full-featured draft of the deliverable. The output draft is then sent by main author to the coordinator. Depending on the deliverable, the coordinator may involve GSA and reviewers in this early stage, in order to speed up the revision process.

2. DELIVERABLE FINAL REVIEW PHASE - the coordinator publishes the draft deliverable to the internal document management systems, which means that the item becomes visible to all the project sub-teams as well as to the EASME and reviewers. Since the date of publication, the project sub-teams have typically one calendar week (but it depends on the nature of the deliverable itself) to ask for explanations and propose modifications to the draft deliverable: the requests/proposals will be shared and quickly discussed (e.g. via teleconference, mail exchange, etc…) among the whole project technical team and modifications to the deliverable will eventually be made directly by the coordinator; this process would take no more than one week. After the deadline, the review is closed, the deliverable state is changed from draft to issued and further requests/proposals are evaluated by GSA and coordinator, which shall agree on the need to reissue the document.



Page: 19 of 20

5 Collaboration and management tools

5.1 Introduction

5.2 Collaborative tools

5.2.1 Google Drive

Google Drive is a file storage and synchronization service created by Google. It allows users to store files in the cloud, share files, and edit documents, spreadsheets, and presentations with collaborators. Google Drive encompasses Google Docs, Sheets, and Slides, an office suite that permits collaborative editing of documents, spreadsheets, presentations, drawings, forms, and more. A dedicated webspace for the project has been setup by the Google account [email protected], and shared directly to the partners. The Gdrive webspace is used for the sharing of documentation, pictures, maps and as tool for sharing the creation and online editing of documents. Googe Docs and Google Spreadsheet (the online editing tools of Gdrive) allow the multiuser editing, but not always maintain the formatting of previously uploaded Word or Excel files. These tools are then used to create and edit online documents, and not to edit Microsoft Word or Excel files.

5.2.2 Dropbox

Dropbox is a file hosting service that offers cloud storage, file synchronization, personal cloud, and client software. Dropbox allows users to create a special folder on their computers, which Dropbox then synchronizes so that it appears to be the same folder (with the same contents) regardless of which device is used to view it. Files placed in this folder are also accessible via the Dropbox website and mobile apps. Dropbox is used mainly to distribute large documents to partners and to external users.

5.2.3 Microsoft Onedrive

OneDrive (previously SkyDrive, Windows Live SkyDrive and Windows Live Folders) is a file hosting service that allows users to sync files and later access them from a web browser or mobile device. Users can share files publicly or with their contacts; publicly shared files do not require a Microsoft account to access. It is part of the suite of online services formerly known as Windows Live. Onedrive and in particular its tools Word Online and Excel Online, are used as an alternative to Gdrive when more than a user has to edit simultaneously a document, and when formatting of original Word and Excel documents has to be preserved.




Page: 20 of 20

5.3 Management and development tools

5.3.1 Trello

Trello is a web-based project management application with a freemium business model; a basic service is provided free of charge. Trello uses the kanban4 paradigm for managing projects, originally popularized by Toyota in the 1980s for supply chain management. Projects are represented by boards, which contain lists (corresponding to task lists in other management approach). Lists contain cards (corresponding to tasks in other management approach). Cards are supposed to progress from one list to the next (via drag-and-drop), for instance mirroring the flow of a feature from idea to implementation. Users can be assigned to cards. Users and boards can be grouped into organizations. Cards accept comments, attachments, votes, due dates and checklists. Users may organize projects through the utilization of boards, lists and cards, which form a bespoke data hierarchy that facilitates effective management of projects, jobs and tasks. Trello will be also used as digital forum

5.3.2 Atlassian Jira

Jira is a proprietary issue tracking product, developed by Atlassian. It provides bug tracking, issue tracking, and project management functions. Jira will be used within Esri Italia and other organizations that will participate to the development to the Moses platform.

5.4 Moses website

The Moses website, available at http://www.moses-project.eu/, has dedicated sections, public and user-restricted, to the download of deliverable, publications, presentations.

5.5 Participant portal

The participant portal, managed by the European Commission, has a section for the Moses project, available at the link: https://ec.europa.eu/research/participants/grants-app/reporting/DLV-642258 In the section, the deliverable of the project may be downloaded.

4 Kanban is a scheduling system for lean and just-in-time (JIT) production; it is a system to control the logistical chain from a production point of view, and is an inventory control system.

http://www.moses-project.eu/

https://ec.europa.eu/research/participants/grants-app/reporting/DLV-642258

d1.1 management plan - mosesmoses-project.eu/.../uploads/2017/08/moses-d1.1-management_pla… ·...

Documents