D1.1 Project Management Plan...Task T1.1 Project Control, Quality Assurance & Configuration...

Project no. 776045

Project title

Project acronym

Start date of project

Duration of project

Deliverable

Due date of deliverable

Actual submission date

Organisation name of lead

contractor for this deliverable

Dissemination level

MySustainableForest

MySustainableForest

1 November 2017

36 months

D01 D1.1

30/11/2017

15/02/2018

GMV

GMV

Public

This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 776045

Code: D01 D1.1

Version: v1

Date: 30/11/2017

Internal code: GMV 24682/17 V1/17

D1.1 PROJECT MANAGEMENT PLAN MYSUSTAINABLEFOREST

Ref. Ares(2018)1039951 - 23/02/2018

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

2 of 67

D1.1 Project Management Plan

TECHNICAL REFERENCES

Project Acronym MySustainableForest

Project Title Operational sustainable forestry with satellite-based remote sensing

Project Coordinator Julia Yagüe

GMV

[email protected]

Project Duration 1 Nov 2011 – 30 Oct 2021 (36 months)

Grant Agreement No. 776045

Deliverable Number D01 – 1.1

Dissemination Level PU

Workpackage WP 1 Coordination & Management

Task T1.1 Project Control, Quality Assurance & Configuration Management

Lead beneficiary GMV

Contributing beneficiary (ies)

RAIZ CFRI UFE FORESNA FOAL CNPF MADERA+ FORA EFI GUK


30/11/2017


23/02/2018

COPYRIGHT NOTICES

©2017 MY SUSTAINABLE FOREST CONSORTIUM PARTNERS. ALL RIGHTS RESERVED. MY SUSTAINABLE FOREST IS A HORIZON2020 PROJECT SUPPORTED BY THE EUROPEAN COMMISSION UNDER CONTRACT NO. 774652. FOR MORE INFORMATION ON THE PROJECT, ITS PARTNERS AND CONTRIBUTORS, PLEASE SEE THE MY SUSTAINABLE FOREST WEBSITE. YOU ARE PERMITTED TO COPY AND DISTRIBUTE VERBATIM COPIES OF THIS DOCUMENT, CONTAINING THIS COPYRIGHT NOTICE, BUT MODIFYING THIS DOCUMENT IS NOT ALLOWED. ALL CONTENTS ARE RESERVED BY DEFAULT AND MAY NOT BE DISCLOSED TO THIRD PARTIES WITHOUT THE WRITTEN CONSENT OF THE MY SUSTAINABLE FOREST PARTNERS, EXCEPT AS MANDATED BY THE EUROPEAN COMMISSION CONTRACT, FOR REVIEWING AND DISSEMINATION PURPOSES. ALL TRADEMARKS AND OTHER RIGHTS ON THIRD PARTY PRODUCTS MENTIONED IN THIS DOCUMENT ARE ACKNOWLEDGED AND OWNED BY THE RESPECTIVE HOLDERS. THE INFORMATION CONTAINED IN THIS DOCUMENT REPRESENTS THE VIEWS OF MY SUSTAINABLE FOREST MEMBERS AS OF THE DATE THEY ARE PUBLISHED. THE MY SUSTAINABLE FOREST CONSORTIUM DOES NOT GUARANTEE THAT ANY INFORMATION CONTAINED HEREIN IS ERROR-FREE, OR UP-TO-DATE, NOR MAKES WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, BY PUBLISHING THIS DOCUMENT.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

3 of 67


DOCUMENT STATUS SHEET

Version Date Pages Changes

v1 30/11/2017 68 First version of the document

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

4 of 67


TABLE OF CONTENTS

1. INTRODUCTION ............................................................................................................................................................................... 7

1.1. PURPOSE ............................................................................................................................................................................. 7

1.2. SCOPE .................................................................................................................................................................................. 7

2. APPLICABLE AND REFERENCE DOCUMENTS ................................................................................................................................ 8

2.1. APPLICABLE DOCUMENTS................................................................................................................................................. 8

2.2. REFERENCE DOCUMENTS ................................................................................................................................................. 8

2.3. ACRONYMS AND DEFINITIONS ......................................................................................................................................... 8

3. OBJECTIVES .................................................................................................................................................................................... 11

3.1. CONTEXT ........................................................................................................................................................................... 11

3.2. OBJECTIVES ....................................................................................................................................................................... 11

3.3. PROJECT CONCEPT ........................................................................................................................................................... 12

3.4. DEMONSTRATION SITES .................................................................................................................................................. 13

3.5. KEY PERFORMANCE INDICATORS................................................................................................................................... 14

3.6. SCHEDULE AND MILESTONES ......................................................................................................................................... 15

3.7. DELIVERABLES .................................................................................................................................................................. 19

4. PROJECT ORGANIZATION ............................................................................................................................................................. 26

4.1. CONSORTIUM................................................................................................................................................................... 26

4.2. PROJECT ORGANIZATION ................................................................................................................................................ 27 4.2.1. ORGANISATIONAL STRUCTURE AND DECISSION MAKING MECHANISMS ........................................................................................................ 28

4.3. PROJECT TEAM ................................................................................................................................................................. 30

4.4. PROJECT DIRECTORY ........................................................................................................................................................ 31

5. PROJECT BREAKDOWN STRUCTURES ......................................................................................................................................... 33

5.1. WORK BREAKDOWN STRUCTURE (WBS) ...................................................................................................................... 33

5.2. WP EFFORT SUMMARY ................................................................................................................................................... 35

5.3. WORK PACKAGE DESCRIPTIONS..................................................................................................................................... 36 5.3.1. WP 1 COORDINATION & MANAGEMENT ............................................................................................................................................................. 36 5.3.2. WP 2 SERVICE REQUIREMENTS ANALYSIS ............................................................................................................................................................ 38 5.3.3. WP3 SERVICE DEVELOPMENT AND ENGINEERING .............................................................................................................................................. 41 5.3.4. WP4 SERVICE DEMONSTRATION AND TRAINING PROGRAM PREPARATION .................................................................................................. 43 5.3.5. WP 5 INNOVATIONS AND ROADMAP ................................................................................................................................................................... 45 5.3.6. WP 6 OUTREACH, DISSEMINATION AND EXPLOITATION .................................................................................................................................... 47

6. CONFIGURATION, INFORMATION AND DOCUMENTATION MANAGEMENT ........................................................................ 50

6.1. CONFIGURATION MANAGEMENT ................................................................................................................................. 50

6.2. GENERAL ........................................................................................................................................................................... 50 6.2.1. CONFIGURATION IDENTIFICATION ........................................................................................................................................................................ 50 6.2.2. CONFIGURATION CONTROL ................................................................................................................................................................................... 50 6.2.3. DOCUMENTATION MANAGEMENT ...................................................................................................................................................................... 51

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

5 of 67


6.3. IDENTIFICATION AND MANAGEMENT .......................................................................................................................... 51 6.3.1. CONFIGURATION ITEMS MANAGEMENT ............................................................................................................................................................. 51 6.3.2. DOCUMENT IDENTIFICATION ................................................................................................................................................................................. 52 6.3.3. GMV INTERNAL CODE (GMVAD) ............................................................................................................................................................................ 53 6.3.4. DIGITAL SIGNATURE ................................................................................................................................................................................................ 53

7. MANAGEMENT, CONTROL, DIRECTION & MONITORING ........................................................................................................ 54

7.1. PROJECT CONTROL PROCEDURES .................................................................................................................................. 54 7.1.1. INDEPENDENT PROJECT CONTROL ........................................................................................................................................................................ 55 7.1.2. PROGRESS AND SCHEDULE CONTROL ................................................................................................................................................................... 55 7.1.3. METRICS CONTROL .................................................................................................................................................................................................. 56 7.1.4. PROJECT BOARD. PROJECT CONSORTIUM MONITORING. ................................................................................................................................. 56 7.1.5. PROJECT MEETINGS AND REVIEW CONTENTS ..................................................................................................................................................... 57 7.1.6. WORKPACKAGE/TASKS INTERNAL MEETINGS ..................................................................................................................................................... 60 7.1.7. INTERNAL MEETINGS AND MINUTES .................................................................................................................................................................... 60 7.1.8. ACTION ITEMS CONTROL ........................................................................................................................................................................................ 60 7.1.9. ACTION ITEM STATUS LIST ...................................................................................................................................................................................... 61

8. RISK MANAGEMENT ..................................................................................................................................................................... 62

9. QUALITY ASSURANCE ................................................................................................................................................................... 65

9.1. ORGANIZATION ................................................................................................................................................................ 65

9.2. LIFE CYCLE AND REVIEWS ................................................................................................................................................ 65

9.3. GMV INTERNAL PROCEDURES ........................................................................................................................................ 65

9.4. INSPECTIONS AND AUDITS .............................................................................................................................................. 65 9.4.1. INSPECTIONS ............................................................................................................................................................................................................ 65 9.4.2. AUDITS ...................................................................................................................................................................................................................... 66

9.5. RISK MANAGEMENT ........................................................................................................................................................ 66

9.6. STANDARDS, PRACTICES AND CONVENTIONS .............................................................................................................. 66 9.6.1. DOCUMENTATION STANDARDS ............................................................................................................................................................................ 66

9.7. PROBLEM REPORTS AND CHANGE PROCESS ................................................................................................................ 66

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

6 of 67


LIST OF TABLES AND FIGURES

Table 2-1. Applicable Documents ................................................................................................................................. 8

Table 2-2. Reference Documents .................................................................................................................................. 8

Table 2-3. Acronyms ..................................................................................................................................................... 8

Table 2-4. Definitions .................................................................................................................................................. 10

Table 3-1. KPIs of project objectives ........................................................................................................................... 14

Table 3-2. Project Milestones ..................................................................................................................................... 19

Table 3-3. Project Deliverables ................................................................................................................................... 20

Table 4-1. List of project partners and contact points ................................................................................................ 26

Table 4-2. Project Board Members ............................................................................................................................. 28

Table 4-3. Stakeholders interested in the project....................................................................................................... 29

Table 4-4. MySustainableForest Project Directory ..................................................................................................... 31

Table 5-1. WP effort summary per partner................................................................................................................. 35

Table 5-2. WP1 description ......................................................................................................................................... 36

Table 5-3. WP 2 description ........................................................................................................................................ 38





Table 6-1 Document Types Codes ............................................................................................................................... 52

Table 6-2 Company Acronym for the naming of the documents ................................................................................ 52

Table 7-1. Upcoming Project Board Meetings ............................................................................................................ 57

Table 7-2. Scheduled Project Meetings ...................................................................................................................... 58

Table 7-3. Review Contents per Project Meetings ...................................................................................................... 58

Table 8-1. Risk Index Scheme ...................................................................................................................................... 62

Table 8-2. Risk acceptance and action criteria ............................................................................................................ 62

Table 8-3. Critical Risks for Implementation ............................................................................................................... 63

Table 8-4. Summary of Project Risks ........................................................................................................................... 64

Table 9-1. GMV Internal Procedures applicable to the project. ................................................................................. 65

Figure 3-1. MySustainableForest Concept of service .................................................................................................. 12

Figure 3-2. MySustainableForest features across the forest exploitation lifecycle .................................................... 12

Figure 3-3. EO based Services Integrated into Forestry Management Workflow....................................................... 13

Figure 3-4. Transnational, interdisciplinary and cross-sector service chain ............................................................... 13

Figure 3-5. Demonstration sites .................................................................................................................................. 14

Figure 3-6. General schedule aspects ......................................................................................................................... 16



Figure 3-9. Milestones schedule ................................................................................................................................. 19

Figure 4-1. Map of project partners ............................................................................................................................ 26

Figure 4-2. Structure and hierarchy of the consortium .............................................................................................. 28

Figure 5-1. Work Breakdown Structure ...................................................................................................................... 33

Figure 6-1. Additional information to the cover page ................................................................................................ 53

Figure 7-1. Calendar overview of project meetings .................................................................................................... 57

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

7 of 67


1. INTRODUCTION

1.1. PURPOSE

This document is the Project Management Plan for the MySustainableForest Project.

Its purpose is to establish the project management techniques, conventions, procedures, and standards that will be followed throughout the project life cycle with regards to Project Management and Progress Monitoring Methodology.

MySustainableForest seeks a new form of sustainable forest management that operatively incorporates satellite-derived information into the everyday decision-making processes of foresters, whatever management perspective they prioritize at each site (productive, conservational, recreational…).

The social and economic benefit of forest resources is nowadays unquestionable and so it is the need for a sustainable and respectful use of these resources. For this reason, the Scope and Dissemination Plan aims, not only to exploit results commercially, but also to bring the project, its message and benefits to the widest possible notice among all sectors involved, be them social, industrial or managerial.

During the development of the project, special attention will be paid to the dissemination of the ground-breaking scientific work of this innovative service, which combines existing socio-economic models, with Earth Observation data and with weather information.

1.2. SCOPE

This document is structured according to:

Section 1, (present chapter) defines the purpose of the document and the project overview.

Section 2 includes the list of applicable documents and additional references to be taken into account during the project life cycle. It also contains the definitions and acronyms used in this document.

Section 3, presents the context, objectives and the key performance indicators for the control and monitor of the progress of MySustainableForest project.

Section 4 includes the management plan regarding:

Project organization;

Staff assignment and resources.

Section 5 includes the breakdown of the project presenting:

Work breakdown structure;

Work package descriptions.

Section 6 presents the configuration information of the project

Section 7 presents the cost and schedule management procedures

Section 8 includes the risks management and the detected risks.

Section 9 presents the Quality Assurance plan for the project.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

8 of 67


2. APPLICABLE AND REFERENCE DOCUMENTS

2.1. APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form part of this document to the extent specified herein. Applicable documents are those referenced in the Contract or approved by the Approval Authority.

Table 2-1. Applicable Documents

Ref. Title Code Version Date

[AD.1] Grant Agreement Nº 776045—MySustainableForest Ares(2017)5215

238 1.0 25/10/2017

[AD.2]

2.2. REFERENCE DOCUMENTS

The following documents, although not part of this document, amplify or clarify its contents. Reference documents are those not applicable and referenced within this document. They are referenced in this document in the form [RD.X]:

Table 2-2. Reference Documents

Ref. Title Code Version Date

[RD.1]

Laevers, F. Assessing the quality of childcare provision: “Involvement” as criterion. Settings in interaction. Researching Early Childhood, 3, 151-165. Göteborg: Göteborg University, 1997

1997

2.3. ACRONYMS AND DEFINITIONS

The following acronyms have been used across this document:

Table 2-3. Acronyms

Acronym Full term

AD Aplicable document

AOI Area of Interest

CFS Certificate on the financial statement

CI Configuration Item

CIDL Configuration Items Data List

CM Configuration Management

CM Configuration Management

CMMI Capability Maturity Model Integration

CN Change notice

COPA -COCEGA European farmers – European agri-cooperatives

CR Change request

DMP Data management plan

DWH European Space Agency Data Warehouse

EEA European Environmental Agency

EFFIS European Forest Fire Information System

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

9 of 67


Acronym Full term

EFH European Forestry House

EO Earth Observation

FLEGT Forest Law Enforcement, Governance and Trade.

FTP File Transfer Protocol

GIS Geographical Information System

GMV-SGC-PRO-005 Project Management Procedure

IT Information Technologies

KOM Kick-off meeting

KPI Key Performance Indicator

LIDAR Light Detection and Ranging

LSA-SAF EUMETSAT Land Surface Facility – Satellite Application Facility

MOM Minutes of Meeting

MTR Mid Term Review

OGC Open Geospatial Consortium

ORDP Open Research Data Pilot

OS Open source

OTH Other items (WRT the project’s documentation nomenclature)

PDPA Payload Data Processing and Applications Business Unit at GMV

PoC Point of contact

PR Progress Report

RD Reference document

REA EC Research Executive Agency

REDD UN Programme on Reducing Emissions from Deforestation and Forest Degradation in Developing Countries

RS Remote sensing

RTD Research Technology and Development

SB Stakeholders Board

SFM Sustainable Forest Management

SODRA Forest-owner association in Sweden

SWOT Strengths, Weaknesses, Opportunities, and Threats Analysis Method

SyGMa H2020’s Grant Management System

TBC To be confirmed

TBD To be defined

ToR Terms of reference

TRL Technology rediness level

VHR Very High Resolution

WBS Work Breakdown Structure

WKS Workshop

WP Work Package

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

10 of 67


Acronym Full term

WPD Work Package Description

Table 2-4. Definitions

Concept/Term Definition

List of configuration items

Catalogue of configuration items in a reference line or delivery (Configuration Item Data List, CIDL).

Configuration Product Description provided from the amount, nature, and interconnections of its parts, allowing thus to know exactly and completely how the product has been conceived, designed, and created.

Configuration Management/Control

Configuration management item consisting in the assessment, coordination, approval, or disapproval and implementation of changes in configuration items after having established formally their configuration identification.

Configuration Status Accounting

Registering and reporting the data needed to manage effectively a configuration.

Life cycle of a Product All phases in the life of a product from needs identification through disposal.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

11 of 67


3. OBJECTIVES

3.1. CONTEXT

European forests are structured among private and public ownership almost in a 50/50 relationship. Therefore, the mobilization of both public and private forestry is key for the utilization of sustainable supply of wood resources through sustainable forest management.

Some challenges forest stakeholder’s operations face are:

Lack of information from private forest owners;

Lack of updated and sufficiently accurate data from forest inventories suitable for sustainable forest management at local/regional levels, which implies that spatial analysis is still done mainly manually in many situations; and

Growing importance of climate change related impacts especially coupled to the long term timing of forestry and its investment horizon

Satellite images facilitate addressing these challenges. Satellite Earth Observation (EO) provides information on different forest and tree stand parameters. EO data is exploited and managed at various spatial and temporal resolutions. These technologies support the definition of forestry operations and long term planning.

3.2. OBJECTIVES

MySustainableForest seeks the integration of EO into the forestry realm, demonstrating the advantages of ingesting EO based information into the daily decision making, protocols and operations of silvicultural stakeholders.

MySustainableForest tackles technological, commercial, societal and political objectives:

1. To provide services for sustainable forest management at commercial stage integrating advanced EO processing with meteorological information, in-situ data and customized forestry models to conduct sustainable forestry in the context of the forest industry needs (refer to WP2 and WP3). It will find the right combination of different data sources to fulfil End-Users needs while fostering a collaborative open space for further transnational collaborative research, experimentation and future co-development within the forestry community.

2. To achieve services integration into End-Users working environment, ICT infrastructures and operational workflows (refer to WP2 and WP3) considering any needed End-User customization.

3. To demonstrate services value for End-Users in terms of the associated cost/benefit, quality service and business case of the EO downstream application in all EU forestry regions (refer to WP4, WP5, WP6).

4. To raise recommendations for policy makers in order to design instruments which will support EU forest owners to manage their forest based on efficient sources of information for an optimal and responsible woodland exploitation (refer to WP6).

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

12 of 67


3.3. PROJECT CONCEPT

Figure 3-1. MySustainableForest Concept of service

Forest management services will be developed upon GMV’s eoforest technological platform and upon the scientific models from MADERA+, FORA and EFI (Figure 3-1). Synergies are sought across satellite-derived information, Web-based Information and Communication Technologies (ICT).

Concerning data types, services shall combine satellite data, meteorological information (ground stations or EUMETSAT LSA-SAF) in situ forest data (volume, biomass and carbon, wood quality) and socio-economic models.

Algorithms for calibration and validations of the services will require in-situ data (i.e. LIDAR) and the knowledge of local forest stakeholders.

Figure 3-1 shows the concept of operations proposed in this project. Technologies benefit activities along the entire forest life and exploitation cycle (Figure 3-2).

Figure 3-2. MySustainableForest features across the forest exploitation lifecycle

To support the forestry operations workflow, MySustainableForest will integrate, in an automatic manner, space information and in-situ data into the end-users IT infrastructure.

Accessible End-User ICT Infrastructure

Server based GIS and geospatial data handling

Web based auxiliary

data access and products delivery,

Open standard interfaces

Advanced image processing and fusion.- Basic level- Medium level- Advanced level

METEOGROWTH AND WOOD QUALITY MODELS

EO EO based service

INSPIRE compliant Open PlatformSpace based input datasets

SOCIO-ECONOMIC DATA/MODELS

Detailed Operational

Planning

Field Campaigns

Surveying

Digital Inventory

Stands Assessment

Land Cover Dynamics

Protected Areas

Ecosystems Information

Preventive Actions

Support to

Certification Audits

Wood Quality Map

Stands Characterization

Strategic Planning face to climate change

Operating Silviculture Plans

Optimized and priorizedharvesting operations according to full area information

Optimizingresources, fires and pests prevention, environmental protection

Exhaustive and frequent of key measurementsand assessments

Sustainable long-term management,reliable yield forecast

Reliable reportingregarding environmental issues

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

13 of 67


Figure 3-3. EO based Services Integrated into Forestry Management Workflow

MySustainableForest bridges satellite based products into forest management and markets, as pictured in Figure 3-4 below.

Figure 3-4. Transnational, interdisciplinary and cross-sector service chain

3.4. DEMONSTRATION SITES

The project shall implement the EO based management services in six AOI’s across Europe’s bioclimatic regions (Figure 3-5), featuring the services for the most representative forest types: temperate natural forests (oaks) and plantations (Pinus spp.) in Spain, Mediterranean and Temperate Continental (heterogeneous stands and lowland pedunculated oak forests) in Croatia, Mediterranean (Eucalyptus spp.) plantations in Portugal, Oceanic for France and Temperate Continental for Czech Rep and Lithuania.

Other external data or

models (field data, etc.)

eoforest

SERVICE

SERVER

1 On-demand

or systematic

service

request

through

eoforest web

site

SERVICE INTERFACE

2 Check request parameters and activate the intelligent search / activate the QC/QA processing

4 Space data acquisition, including regular updates Space Data

Provider

5 Datasets reception & quality validation

7. Service product delivery (open interfaces) ready for space analysis

CUSTOMIZABLE

PROCESSING WORKFLOWJob

Order

3 If something is missing, alert user and recover whatever is needed

End-User

Operational

Infrastructure

6 Processing requested product (i.e. indicator as fusion of multitemporal resolution imagery, models and other data sources, analisis for objects extraction, etc.)

2

1

3

4 5

6

7

Biomass AssessmentStress indicators

Disturbances assessment

Vulnerability trendsWood Quality

indicators

Public&privateowners, NGOs

Industrial Expertise

Advanced algorithms and

models

Pre-processing

Industrial customers

Added-value productsDownstream Services

Applied research

Bridging the gap from space data to forestry market End-UsersData

Providers

Scientific marketing, Stakeholders early engagement, Citizens awareness, Policy recommendations

End-User needs, validation and training

Sentinels

Meteo

3rd PartyMissions

LIDAR

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

14 of 67


Figure 3-5. Demonstration sites

3.5. KEY PERFORMANCE INDICATORS

The following key performance indicators (KPIs) have been defined to assess how project objectives are attained:

Table 3-1. KPIs of project objectives

Business Area Key Performance Indicator (KPI) Target Range

Technological (Objectives 1 and 3)

T1. EO based products/services´ TRL 7-9

T2. Robust service (to cope with service failures) 95-98%

T3. Number of publications 15-30

Market (Objectives 1, 3 and 4)

M1. Active involvement of stakeholders (moderate, high and extremely high in Leuven scale [Laevers1997])

50-75 End-Users

15-25 of other stakeholders

M2. Number of public stakeholders testimonials 3-6

M3. Number of published patents or utility models 1-2

M4. Number of reference customers 3-6

M5. EO products/services portfolio as increase in size (new products) or enhancement (on existing products)

3-9

M6. Participants´ market share 1-10%

M7. Participants´ market penetration 1-3%

M8. Reached audience by communication and dissemination activities

25-50 per workshop,

50-200 views of project videos,

25-200 views of articles/posts,

25-6000 people of TV/radio interview

Forest Owners Association of Lithuania :

Private, non-profit

Forest owners for wood

Forestry Research

Remote sensing skills

Croatian Forest Research Institute :

Public, non-profit

Government s ownership for recreation

Forestry Research


University Forest Enterprise –

Mendel University :

Public, non-profit

Uni. owner for research & training

Forestry Research

Centre National de la Propriété Forestière:

Public, non-profit

Forest owners advice and training

Forestry Research/Innovation service


Navarra Forest Owners Association:

Private, non-profit

Forest owners for wood & recreation

Forestry ResearchSouth-East Europe

South-West Europe

Central-East Europe

Central-West Europe

North Europe

RAIZ/NAVIGATOR:

Private paper industry, for profit

Forest owner for pulp&paper

Forestry Research


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

15 of 67


Business Area Key Performance Indicator (KPI) Target Range

M9. Registered active users in the platform 50-100

M10. Policy recommendations to enable market adoption 1-3

Operational (Objective 2)

O1. Women participation in the project 35-40%

O2. Smooth and smart integration into End-Users workflow and working environment

100%

Financial (Objective 3) F1. Time for breakeven 2 years after project termination

F2. Jobs creation increase in participating SMEs 10-20%

F3. Average annual savings in End-Users´ due to forestry operations optimizations (i.e. staff)

5-10%

3.6. SCHEDULE AND MILESTONES

The following figures depict in a visual manner the project schedule

Figure 3-6 recalls some general aspects of the project schedule:

Year, month and month number (1-36 months)

Reporting periods 1 and 2

Logic flow periods

1. Early Service Readiness/ Service Preparation

2. Enhanced Service Readiness/ Service demonstration &Training

3. Advanced Service Readiness/ Ramp-up & Initial operations

4. Routine Operations

Interim progress reports (2)

Progress reports (2)

Milestones (7)

Reviews (4)

Project Workshops (4)

Practical training (3)

Figure 3-7 recalls the schedule of Work Packages during the 36 month of the project’s duration

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

16 of 67


Figure 3-6. General schedule aspects

Financing 75% 25%

Reporting periods

Year

Month Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Logic flow periods

Progress Reports Interim progress report 1 Progres Report 1 Interim progress report 2 Progres Report 2

Milestones Kom AR S1 MTR S2 S3 FR

Reviews RV1 RV2 RV3 RV4

WP6 Workshops

Practical Training

REPORTING PERIOD 1 REPORTING PERIOD 2

Use case in-depth definition

Algorithms prototyping

Workflow integration

Early Service Pre-Commercial Launch –Boreal, Mediterranean &

Atlantic Forests-

Pre-operational demonstration trials

Enhanced Service Pre-Commercial Launch

–Boreal, Mediterranean & Atlantic ForestsPilot usages

Market replication other

regions

Advanced Service Commercial

Launch –include testimonials

from pilot usages in European

2017 2018 2019 2020

Early Service Readiness/ Service PreparationEnhanced Service Readiness/ Service

demonstration &Training

Advanced Service Readiness/ Ramp-

up & Initial operationsRoutine Operations

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

17 of 67



Year


Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

WORK PACKAGES Coordinator

WP1 Coordination & ManagementGMV

WP2 Service Requirements AnalysisFORESNA

2A PRT Case Specification GMV, RAIZ, GUK

2B HRZ Case Specification GMV, CFRI, GUK

2C CZE Case Specification GMV, UFE, GUK

2D ESP Case Specification GMV, FORESNA, GUK

2E LTU Case Specification GMV, FOAL, GUK

2F FRA Case Specification GMV, CNPF, GUK

T2.4 High Level Design GMV

WP 3 Service Development and Engineering GMV

WP 4 Service Demonstration and Training Program Preparation RAIZ

4A PRT Case Demo RAIZ

4B HRZ Case Demo CFRI

4C CZE Case Demo UFE

4D ESP Case Demo FORESNA

4E LTU Case Demo FOAL

4F FRA Case Demo CNPF

WP5 Innovation and Roadmap CFRI

WP6 Outreach, Dissemination and ExploitationEFI

2017 2018 2019 2020

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

18 of 67



Financing 75% 25%

Reporting periods

Year


Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Logic flow periods

Progress Reports Interim progress report 1 Progres Report 1 Interim progress report 2 Progres Report 2



WP6 Workshops

Practical Training

WORK PACKAGES Coordinator


WP2 Service Requirements AnalysisFORESNA

2A PRT Case Specification GMV, RAIZ, GUK

2B HRZ Case Specification GMV, CFRI, GUK

2C CZE Case Specification GMV, UFE, GUK

2D ESP Case Specification GMV, FORESNA, GUK

2E LTU Case Specification GMV, FOAL, GUK

2F FRA Case Specification GMV, CNPF, GUK

T2.4 High Level Design GMV

WP 3 Service Development and Engineering GMV

WP 4 Service Demonstration and Training Program Preparation RAIZ

4A PRT Case Demo RAIZ

4B HRZ Case Demo CFRI

4C CZE Case Demo UFE

4D ESP Case Demo FORESNA

4E LTU Case Demo FOAL

4F FRA Case Demo CNPF

WP5 Innovation and Roadmap CFRI

WP6 Outreach, Dissemination and ExploitationEFI






Atlantic Forests-





regions




2017 2018 2019 2020





Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

19 of 67


The complete list of project milestones follows:

Table 3-2. Project Milestones

M No. Title Lead Month Description WP

M1 KOM: Kick-off Meeting GMV 1 GA is signed by all partners. 1

M2 AR: Analysis Review

GMV 6 End-Users requirements are

complete and verifiable. 1, 2

M3

S1: Early Service Readiness

GMV

13 The technological integration for the early service into End-Users workflows is complete and tested. End-Users have been trained and are ready for the service pre-operational trials.

1, 3, 4 .

M4

MTR: Mid Term Review

GMV

18 End-Users feedback is satisfactory on the early service and industrial partners confirm their business opportunity window. Project objectives and KPIs are in line with the expected final targets.

1, 2, 3, 4, 6 ...

M5

S2: Enhanced Service Readiness

GMV

22 The enhanced service chain is tested and ready for its demonstration within End-Users´ operational environment.

1, 3, 4, 5 ...

M6 S3: Advanced Service Readiness

GMV 30 The advanced service chain is

demonstrated by End-Users under real operational conditions.

1, 2, 3, 4, 5 ...

M7 FR: Final Review

GMV 36 Consortium partners validate the

business model. Project objectives and KPIs are reached.

1, 2, 3, 4, 5, 6.

Figure 3-9. Milestones schedule

3.7. DELIVERABLES

The following documentation shall be provided as described in the table below. For each deliverable the dissemination level is specified using the following codes: PU = Public, PP = Restricted to other programme participants, RE = Restricted to a group specified by the consortium, and CO = Confidential, only for members of the consortium. All dissemination levels include the Commission Services and the REA. The nature of each deliverable is specified according to the following codes: R= Report, P = Prototype, D = Demonstrator, O = Other, ORDP = Open Research Data Pilot, E = Ethics.

All documentation will be delivered electronically in PDF format (and in original format if required) to the EC through the H2020’s Grant Management System (SyGMa).

Year


Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Logic flow

periods






Atlantic Forests-





regions




2017 2018 2019 2020





Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

20 of 67


Table 3-3. Project Deliverables

Nº Rel No. Title Description Lead WP No Nature Level Due date

D1 D1.1 Project Plan Plan to detail as needed the organisation, WBS, schedule and deliverables including any interim version, for each development phase or milestone. It will include also procedures for configuration management, for verification and for assuring the quality of the Project results including deliverables contents or guidelines

GMV WP1 Report PU 30 November 2017

D2 D6.19 Background Intellectual Property

Gather and document the background IP existing within the Consortium at the beginning of the project.

GMV WP6 Report CO 30 November 2017

D3 D2.1 End-User Use Cases

End-User Use Cases will update, complete and refine the information provided at proposal time by End-Users on their specific needs, including their priority on each identified use case.

FORESNA

WP2 Report PU 31 January 2018

D4 D6.1 Outreach and Dissemination Plan (v1)

Outreach and Dissemination Plan will present the communication and dissemination objectives, players, target audiences, messages and implementation measures along the Project duration.

EFI WP6 Report PU 31 January 2018

D5 D6.4 Communication Materials (v1)

Communication Materials will embrace the related materials produced up to the delivery date. These relates to policy briefings, brochure, web site and contents, newsletters, articles, videos, etc. as planned.

EFI WP6 Websites, patents filling, etc.

PU 31 January 2018

D6 D1.11 Data Management Plan (v1)

The Data Management Plan (DMP) addresses the relevant aspects of making data FAIR – findable, accessible, interoperable and re-usable, including what data the project will generate, whether and how it will be made accessible for verification and re-use, and how it will be curated and preserved. Through this DMP, it can be defined certain datasets to remain closed according to the principle "as open as possible, as closed asnecessary.

GMV WP1 ORDP: Open Research Data Pilot

PU 28 February 2018

D7 D6.10 Stakeholders Workshop-1 Report

Stakeholders Workshop-1 Report will summarize workshop execution and results.

GMV WP6 Report PU 28 February 2018




PU 30 April 2018

D9 D2.2 Service Requirements and Validation of Use Cases

Service Requirements and Validation of Use Cases includes:

- the technical requirements and constraints for each service to be provided to each End-User following the End-User Use Cases,

- the procedures for testing the services to be provided for verifying that they fulfill the End-Users needs specified in the End-User Use Cases.

GMV WP2 Report CO 31 May 2018

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

21 of 67



D10 D2.3 Architectural Design

The Architectural Design will specify the top-level components of the service demonstrating that it covers all Service Requirements.


D11 D3.1 Integration and Validation Plan

The Integration and Validation Plan will define the procedures for testing the integration of the different service components and for verifying that it complies with the Service Requirements

GMV WP3 Report PU 31 May 2018

D12 D1.2 DWH use for 2018

Explanation of the use of DWH data during 2018.

GMV WP1 Report CO 31 July 2018

D13 D1.3 DWH request for 2019

Additional VHR satellite data requested to the DWH for use in 2019.

GMV WP1 Report CO 31 July 2018

D14 D1.7 Interim Progress Report-1

This report will detail technical and financial progress of each participating partner in the period [M1, M9]. It will be used to monitor the proper implementation of the work and ensure the early intervention of the coordinator in case of need. The overall figures of efforts and budget spent by partners will not be fully binding but reported for information purposes.

GMV WP1 Report CO 31 August 2018

D15 D4.1 Service Getting Started Guide

Service Getting Started Guide will describe what the service does and how to use it in a concise, easy to understand by End-Users and comprehensive manner.

GMV WP4 Report PU 30 September 2018


The Data Management Plan (DMP) addresses the relevant aspects of making data FAIR – findable, accessible, interoperable and re-usable, including what data the project will generate, whether and how it will be made accessible for verification and re-use, and how it will be curated and preserved. Through this DMP, it can be defined certain datasets to remain closed according to the principle "as open as possible, as closed as

necessary.

GMV WP1 Report PU 31 October 2018

D17 D3.2 Remote Sensing Algorithms and Models Trade-off

Remote Sensing Algorithms and Models Trade-off will document any needed trade-off considered for new or refined remote sensing algorithms and models in order to fulfil the End-Users needs.

CFRI WP3 Report PU 31 October 2018

D18 D3.3 Integration and Validation Report (v1)

This Integration and Validation Report will report the results of the execution of the planned Integration and Validation tests on the Early Service.

GMV WP3 Report CO 31 October 2018



EFI WP6 Report PU 31 October 2018




PU 31 October 2018

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

22 of 67





GMV WP6 Report PU 31 January 2019

D22 D4.2 End-User Trials Assessment Report (v1)

This End-User Trials Assessment Report will compile the critical evaluations from End-Users partners about the EO derived products (in Early Service) provided to each End-User. It will cover at least End-Users´ operational and financial criteria in line with Project objectives (i.e. O2. Smooth and smart integration into End-Users workflow and working environment, F3. Average annual savings in End-Users´ due to forestry operations optimization).

RAIZ WP4 Report PU 31 March 2019

D23 D6.14 Compilation of Publications Abstracts (v1)

Compilation of Publications Abstracts will provide the complete set of abstracts related to Project derived publications.

CFRI WP6 Websites, patents filling, etc.

PU 31 March 2019

D24 D1.8 Progress Report-1

This report will detail both technical and financial progress of each participating partner in the period [M1, M17]. It will be used to monitor the proper implementation of the work and ensure the intervention of the coordinator in case of need. The overall figures of efforts and budget spent by partners will be fully binding.

It will consist of technical and financial structured forms and questionnaires which will be fulfilled online, and a descriptive document where the work carried out in the reporting period is explained together with any justification about deviations against the Project plan.

GMV WP1 Report CO 30 April 2019




PU 30 April 2019

D26 D6.16 Business and Exploitation Plan (v1)

The purpose of this document is to assess the economic viability and future sustainability of the associated business. Its contents and structure will integrate those of a standard business plan. It will embrace the market analysis including the assessment of the barriers for market uptake as well as the sustainability of the service after the end of the Project. In particular, it will pay attention to the impact of no longer having access to free data provided by the EU. Commercialisation will be led by GMV. The draft contract for Service Level Agreement will be found in Annex.

This first version of the document will be built on the basis of the gained experience with End-Users usage of the Early Service.


D27 D5.1 Product Roadmap (v1)

Product Roadmap will serve for planning the services evolution. It brings important support to the innovation manager, letting define the firm’s technological evolution in advance and always focussing on market demands.

CFRI WP5 Report CO 30 June 2019

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

23 of 67




Use of DWH satellite data during 2019. GMV WP1 Report CO 31 July 2019

D29 D1.5 DWH request for 2020

Request of DWH data for 2020. GMV WP1 Report CO 31 July 2019


The Data Management Plan (DMP) addresses the relevant aspects of making data FAIR – findable, accessible, interoperable and re-usable, including what data the project will generate, whether and how it will be made accessible for verification and re-use, and how it will be curated and preserved. Through this DMP, it can be defined certain datasets to remain closed according to the principle "as open as possible, as closed as necessary.



This Integration and Validation Report will report the results of the execution of the planned Integration and Validation tests on the Enhanced Service.






This End-User Trials Assessment Report will compile the critical evaluations from End-Users partners about the EO derived products (in Enhanced Service) provided to each End-User. It will cover at least End-Users´ operational and financial criteria in line with Project objectives (i.e. O2. Smooth and smart integration into End-Users workflow and working environment, F3. Average annual savings in End-Users´ due to forestry operations optimization).

RAIZ WP4 Report PU 31 December 2019


This is the second version of the document. It will be built on the basis of the gained experience with End-Users usage of the Enhanced Service.

GMV WP6 Report CO 31 January 2020

D35 D1.9 Interim Progress Report-2

This report will detail technical and financial progress of each participating partner in the period [M18, M27]. It will be used to monitor the proper implementation of the work and ensure the early intervention of the coordinator in case of need. The overall figures of efforts and budget spent by partners will not be fully binding but reported for information purposes.

GMV WP1 Report CO 29 February 2020





Description of the use of DWH data made during 2020.



This Integration and Validation Report will report the results of the execution of the planned Integration and Validation tests on the Advanced Service.


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

24 of 67






PU 30 April 2020


This End-User Trials Assessment Report will compile the critical evaluations from End-Users partners about the EO derived products (in Advanced Service) provided to each End-User. It will cover at least End-Users´ operational and financial criteria in line with Project objectives (i.e. O2. Smooth and smart integration into End-Users workflow and working environment, F3. Average annual savings in End-Users´ due to forestry operations optimization).

RAIZ WP4 Report PU 31 August 2020

D41 D5.2 Product Roadmap (v2)

Product Roadmap will serve for planning the services evolution. It brings important support to the innovation manager, letting define the firm’s technological evolution in advance and always focussing on market demands

CFRI WP5 Report CO 30 September 2020


Compilation of Publications Abstracts will provide the complete set of abstracts related to Project derived publications.


PU 30 September 2020


This is the third version of the document. It will be built on the basis of the gained experience with End-Users usage of the Advanced Service.

GMV WP6 Report CO 30 September 2020

D44 D6.20 Foreground Intellectual Property

This report will document the foreground IP developed along the project by the different partners.


D45 D1.10 Progress Report-2

This report will detail both technical and financial progress of each participating partner in the period [M18, M36]. It will be used to monitor the proper implementation of the work and ensure the intervention of the coordinator in case of need. The overall figures of efforts and budget spent by partners will be fully binding.

It will consist of technical and financial structured forms and questionnaires which will be fulfilled online, and a descriptive document where the work carried out in the reporting period is explained together with any justification about deviations against the Project plan.



The Data Management Plan (DMP) addresses the relevant aspects of making data FAIR – findable, accessible, interoperable and re-usable, including what data the project will generate, whether and how it will be made accessible for verification and re-use, and how it will be curated and preserved. Through this DMP, it can be defined certain datasets to remain closed according to the principle "as open as possible, as closed as necessary.


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

25 of 67



D47 D5.3 Needs under global change and opportunities with new EO sensors for SFM

Needs under global change and opportunities with new EO sensors for SFM will describe forestry stakeholder new needs for Sustainable Forest Management under the climate change challenge, considering the outcome of the Project and the opportunities raised by the Copernicus evolution program.





PU 31 October 2020


Stakeholders Workshop-4 Report will summarize workshop execution and results


Specific focus is set on ORDP deliverable: D6_D1.11_Data Management Plan (v1). The following sources shall be used as a reference for the purpose

EC standard DMP template https://dmponline.dcc.ac.uk/

What is the Open Research Data Pilot? - https://www.openaire.eu/what-is-the-open-research-data-pilot

How to create a DMP Plan - https://www.openaire.eu/opendatapilot-dmp

Open Research Data Pilot in Horizon 2020, How can OpenAIRE help? - https://www.openaire.eu/edocman?id=798&task=document.viewdoc

How to select a repository? - https://www.openaire.eu/opendatapilot-repository

https://dmponline.dcc.ac.uk/

https://www.openaire.eu/what-is-the-open-research-data-pilot

https://www.openaire.eu/opendatapilot-dmp

https://www.openaire.eu/edocman?id=798&task=document.viewdoc

https://www.openaire.eu/opendatapilot-repository

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

26 of 67


4. PROJECT ORGANIZATION

4.1. CONSORTIUM

MySustainableForest Project is composed of 11 European partners. The institutions in partnership represent two key factors to the project objectives:

Fair representation of SME’s, academia and research, forest owners associations and large industrial and technological corporation

Fair representation of the various forest types across Europe through the chosen AOI sites: Portugal, Spain, France, Croatia, the Czech Republic and Lithuania.

Figure 4-1maps the location of each and every consortium member while Table 4-1 lists the personel involves per institution and the contact address.

Figure 4-1. Map of project partners

Table 4-1. List of project partners and contact points

Nº Short Name Legal Name Name & Surname e-mail

1 GMV GMV AEROSPACE AND DEFENCE SA

1. Julia Yagüe (PM) 2. Antonio Tabasco 3. Almudena Sánchez 4. Ana Sebastián Lopez 5. Valerio Platania

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

2 RAIZ RAIZ - INSTITUTO DE INVESTIGACAO DA FLORESTA E PAPEL

6. Luis Fontes 7. Margarida Mendes Silva 8. Sergio Fabres 9. Nuno Manuel Goncalves

Borralho 10. André Duarte 11. Celeste Ramalho

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

mailto:[email protected]











Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

27 of 67


Nº Short Name Legal Name Name & Surname e-mail

3 CFRI HRVATSKI SUMARSKI INSTITUT

12. Ivan Pilas 13. Ivan Balenovic 14. Dijana Vuletić 15. Luka Jurjević

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

4 UFE MENDELOVA UNIVERZITA V BRNE

16. Lumír Dobrovolný [email protected]

5 FORESNA ASOCIACION FORESTAL DE NAVARRA

17. Juan Miguel Villaroel 18. Eduardo Montero 19. Teresa Marticorena

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

6 FOAL LIETUVOS MISKO SAVININKU ASOCIACIJA- FOREST OWNERS ASSOCIATION OF LITHUANIA

20. Algis Gaižutis 21. Živilė Navardauskė 22. Gintautas Mozgeris 23. Vytautas Bardauskas

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

7 CNPF CENTRE NATIONAL DE LA PROPRIETE FORESTIERE

24. Clotilde Fontaine 25. Michel Chartier 26. Raoul Daubresse


8 MADERA+ MADERA PLUS CALIDAD FORESTAL SL

27. Esther Merlo 28. Gloria Bustingorri 29. Miguel Piñeiro


9 FORA FORA FOREST TECHNOLOGIES SLL

30. Iñigo Lizarralde 31. Paco Rodríguez

[email protected] [email protected]

10 EFI EUROPEAN FOREST INSTITUTE

32. Inazio Martinez de Arano 33. Albert Garduño 34. María Zapata


11 GUK GMV INNOVATING SOLUTIONS LTD

Ana Sebastián [email protected]

4.2. PROJECT ORGANIZATION

The project consortium is a balanced mix of Universities, RTD, technology providers (mainly R&D driven SMEs), and R&D actors (RTD’s and universities) who will provide scientific knowledge, technical skills and facilities for implementing the work plan, innovation support, regional policy support, market awareness, and a solid socio-economic basis to ensure the correct targets are aimed.

The structure for the consortium is hierarchized according to Figure 4-2. :

























Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

28 of 67


Figure 4-2. Structure and hierarchy of the consortium

The project management will follow the rules dictated by the contract between the European Commission and the consortium. A Consortium Agreement (CA) has been signed among the partners. It defines the internal management rules of the consortium: responsibility / commitment of each participant, roles of the boards and co-ordinator, and the confidentiality, access rights to the ownership and exploitation of the results conditions.

4.2.1. ORGANISATIONAL STRUCTURE AND DECISSION MAKING MECHANISMS

GMV will act as coordinator. GMV holds ISO 9001 and CMMI level 5 certifications and is familiar with EC standards and administrative procedures. The project hierarchical structure shown in Figure 4-2 complies with EC rules and relies on the following roles, needed for developing this close-to-market project.

The Project Coordinator (Managerial and technical) is the highest-level authority in the project including solving difficulties, major problems, disputes or conflicts that could eventually occur, and is formally empowered to take binding decisions. Julia Yagüe (PhD) shall be the project coordinator, holding the responsibility of management activities, PoC between the project and the EC project officer. GMV will lead project life cycle milestones, including reviews with REA and technical meetings. The PC shall prepare the progress review meetings and MoMs. Formerly assigned PC Ana Sebastian (PhD), a senior Forest

Engineer (PhD) and GIS and remote sensing master, shall participate from GMV-UK 1.

The Project Board (PB) shall handle the most important decisions on the project: amendments to the contractual documents, adaptations of work plan, allocated budget, risks assessment, partial and final results confidentiality, harmonisation among dissemination issues, multilingual issues, ethical issues, gender aspects, assessment of the scientific quality of the results, assessment of the commercial potential of the results, etc.

Members of the PB shall be one representative per consortium member, as listed in Table 4-2.

The complete list of the Project’s Board competences can be consulted in section 7.1.4 below

Table 4-2. Project Board Members

Nº Short Name Legal Name Board Member

1 GMV GMV AEROSPACE AND DEFENCE SA Julia Yagüe (PM)

2 RAIZ RAIZ - INSTITUTO DE INVESTIGACAO DA FLORESTA E PAPEL Luis Fontes

3 CFRI HRVATSKI SUMARSKI INSTITUT Ivan Pilas

4 UFE MENDELOVA UNIVERZITA V BRNE Lumír Dobrovolný

5 FORESNA ASOCIACION FORESTAL DE NAVARRA Eduardo Montero

6 FOAL FOREST OWNERS ASSOCIATION OF LITHUANIA Algis Gaižutis

1Ana Sebastian works at the Remote Sensing Applications Divisions of GMV since 2008, leading the development of EO-based forest services.

Ana prepared the project’s proposal. Since September 2017 Ana moved to the UK office, entity added as a Beneficiary to the project. GMV’s

office in Madrid shall coordinate the project and the IT- activities; GMV-UK shall gear the communication between forest stakeholders’ needs

and GMV IT staff. These coordination ensures that the end-users’ needs are conveyed into RS and IT requirements. Moreover, Her knowledge

of forest markets shall contribute to the analysis of Service gaps, proposals for future innovations and engaging with End-Users.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

29 of 67


Nº Short Name Legal Name Board Member

7 CNPF CENTRE NATIONAL DE LA PROPRIETE FORESTIERE Clotilde Fontaine

8 MADERA+ MADERA PLUS CALIDAD FORESTAL SL Esther Merlo

9 FORA FORA FOREST TECHNOLOGIES SLL Iñigo Lizarralde

10 EFI EUROPEAN FOREST INSTITUTE Inazio Martinez de Arano

11 GUK GMV INNOVATING SOLUTIONS LTD Ana Sebastián

Decisions in the PB will be taken by majority vote, by default.

The PB decides jointly for business: financial, commercial and technical issues in any decision to be taken. The PB will track cash-flows, end-Users or potential customers´ feedback and technological advances, concerning effort, cost, impact and value for the associated development to shape the strategic and technological service roadmap.

The PB shall meet monthly for progress internal review meeting. Web-conferences, phone and email exchanges among members will be the regular communication channels. The Board agenda will be focus on specific issues depending on the project phase. The project coordinator will ensure the implementation of the decisions taken. Any major decision regarding the GA will be submitted to EC for approval. A procedure is agreed for conflict resolution; refer to the specific section below for details.

The Stakeholders Board gathers potential business partners, who rely on project success to obtain competitive advantages in their operations.

The consortium is complemented with the Stakeholders Board including members of the EU associations and EU regional organizations (i.e. COPA-COGECA, and others to be incorporated along the project).The purpose of this Board is to extend the market up-take perspective beyond partners´ current networking and to raise recommendations to policy makers which might improves the economical context for both public and small forestry owners. An additional level of validation activities, such as operational trials, will be executed by the potential End-Users, being either public or private entities, members of the Stakeholders Board now or joining it along the project development

Several forestry organizations such as national and regional associations as well as public national and regional authorities and private small forest owners have already confirmed their interest on their active participation in the project, refer to Letters of Interest (LOIs) in Technical Annex after Sections 4-5 of proposal. This is a project consultative body to get feedback and advice on market needs and commercial issues. Members of this board will receive under confidentiality basis early information on project results and are invited to remotely provide comments / suggestions timely about the project intermediate/finals results. This will foster a broad access to all major forestry stakeholders in EU. Please, refer to table below for details on potential members and LOIs in Technical Annex after Section 4-5 for confirmations.

Table 4-3. Stakeholders interested in the project

Organization Organisation type Regional interest

Interest / Level of involvement

SODRA Private for profit Sweden Observer as owner of a large private exploitation

Croatian Forest Private for profit Croatia Observer as owner of a large public exploitation

ENCE Private for profit Spain Observer as owner of a large public exploitation

PROMAGAL Federation Spain Observer as small forestry owner / Business model for members

ASEFOGA Association Spain Observer as small forestry owner / Business model for members

COSE Association Spain Observer as national association embracing regional associations

UNAC Association Portugal Business model for members

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

30 of 67


Organization Organisation type Regional interest

Interest / Level of involvement

The Navigator Company

Private for profit Portugal Observer as owner of a large private exploitation

Croatian Oak Cluster Association Croatia Business model for members

COPA-COGECA Association Europe Policy recommendations to EC

CEPF Association Europe Policy recommendations to EC

Österreichische Bundesforste AG

Private for profit Austria Observer as large forest management company

Regione Toscana authority

Regional authority Italy Reporting, and supporting rural development

Bavarian State Ministry of Food, Agriculture and Forestry

Regional authority Germany Climate change regional adaptation

Schenker Forst und Landwirtschaft

Regional authority Austria Observer as small forestry owner

JCyL Regional authority Spain Promotion of regional rural development

The Stakeholders Board is open along the project’s duration for the engagement of new end-users, on a voluntary basis.

4.3. PROJECT TEAM

GMV sets up a dedicated project team for the purpose of MySustainableForest project, led by Julia Yagüe as Project Coordinator. Julia is a Project Manager at GMV Payload Data Processing and Applications Business Unit (PDPA). She shall be supported by Ana Sebastian, from GMV (PDPA Unit), based in the UK, and by Almudena Sánchez.

As project coordinator, Julia Yagüe shall be the focal point of contact at GMV for all project related matters, both technical and managerial.

Under the overall responsibility of the appointed Project Coordinator, GMV shall establish a project organization. All the members of the project team shall be under his direct authority and he shall be responsible for all matters related to the project and will report to him.

The staff assigned to the project always report functionally to the appointed Project Manager for all matters concerning this project. In this respect, the Project Manager is clearly given full authority over the project team members for their period of assignment to the project. In the case of part-time assignments, the Project Manager and the line responsible for each person allocated to the contract are clearly indicated, at the time of project staffing, the proportion of the team member working time available to the project, and the former has full authority within the scope of this working time; the relevant line responsible cannot revoke any such part-time assignment to a project without the prior consent and agreement of the Project Manager.

GMV's project team will be organized functionally in the following roles, which will support the Project Manager for the implementation of the project:

A Contract Officer, Mr. Juan Carlos Carmona, who shall take care of all the contractual and legal aspects of the project, including grant agreement signature, preparation, etc. He shall be GMV’s counterpart to the EC Contracts Manager nominated for the contract. He shall advise the Project Coordinator on all the relevant contractual and legal issues. Also, he will support Project Coordinator on issues related to intellectual property rights.

A Project Controller, Antonio Tabasco, Division Manager, who is experienced in the management, control and supervision of large projects. The Project Controller shall be responsible within the proposed project organisation for:

Managing the WBS, schedule and cost control aspects of the project.

Providing schedule and cost inputs for the risk management.

Controlling the resources planned for the project management.

Those activities are also going to be performed by the project coordinator, but the project controller is going to be an independent check of the project evolution.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

31 of 67


Those activities are within the usual functions carried-out internally at GMV by the unit heads for ensuring the fulfillment of the project objectives within the agreed schedule and cost. Because of the high commitment of GMV to the proposed schedule applicable to the development, the figure of the project controller should be understood as an addition measure to avoid any schedule or cost deviation from the nominal one while ensuring the high quality of the work performed. No cost is charged for this.

A Quality Assurance Manager, Ms. María Inocencia García Martín, from the GMV’s QA Department, who shall support the QA tasks relevant to the project, especially to ensure internal standard procedures for this size of research project are followed.

A Project Administration Officer, Ms. Marta Jordá, will assist the Project Coordinator for administrative activities dealing with financial details on a monthly basis such as those related with justifications.

The above GMV’s team is complemented by the following staff from the consortium members:

RAIZ Project Manager and responsible of assigned tasks, Mr. Luis Fontes

CFRI Project Manager and responsible of assigned tasks, Mr. Ivan Pilas

UFE Project Manager and responsible of assigned tasks, Mr. Lumír Dobrovolný

FORESNA Project Manager and responsible of assigned tasks, Mr. Eduardo Moreno

FOAL Project Manager and responsible of assigned tasks, Mr. Algis Gaižutis

CNPF Project Manager and responsible of assigned tasks, Mrs. Clotilde Fontaine

MADERA+ Project Manager and responsible of assigned tasks, Mrs. Esther Merlo

FORA Project Manager and responsible of assigned tasks, Mr. Iñigo Lizarralde

EFI Project Manager and responsible of assigned tasks, Mr. Inazio Martinez de Arano

GUK Project Manager and responsible of assigned tasks, Mrs. Ana Sebastian

The above key personnel are fully acquainted with all the managerial and technical aspects relevant to the project to ensure the successful achievement of the objectives within the proposed schedule. Remarkably, the proposed team is composed of engineers with a high level of experience and motivation in the area.

4.4. PROJECT DIRECTORY

The table below contains the structure of the project’s directory for MySustainableForest project:

Table 4-4. MySustainableForest Project Directory

Key personnel Project Assignment Company E-mail address

Juan Carlos Carmona GMV Contract Officer GMV [email protected]

Antonio Tabasco GMV Project Controller GMV [email protected]

Julia Yagüe GMV Project Coordinator GMV [email protected]

Ana Sebastián GMV Deputy Project Coordinator (UK Based) GMV UK asebastiá[email protected]

Almudena Sánchez Primary Coordinator Contact GMV [email protected]

María Inocencia García Martín GMV Quality Assurance Manager GMV [email protected]

Marta Jordá GMV Project Administration Officer GMV [email protected]

Luis Fontes RAIZ Project Manager RAIZ [email protected]

Ivan Pilas CFRI Project Manager CFRI [email protected]

Lumír Dobrovolný UFE Project Manager UFE [email protected]

Eduardo Moreno

FORESNA Project Manager FORESNA [email protected]:[email protected]

Algis Gaižutis FOAL Project Manager FOAL [email protected]




mailto:asebastiá[email protected]










Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

32 of 67


Key personnel Project Assignment Company E-mail address

Clotilde Fontaine CNPF Project Manager CNPF [email protected]

Esther Merlo MADERA+ Project Manager MADERA+ [email protected]

Iñigo Lizarralde FORA Project Manager FORA [email protected]

Inazio Martinez de Arano EFI Project Manager EFI [email protected]





Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

33 of 67


5. PROJECT BREAKDOWN STRUCTURES

5.1. WORK BREAKDOWN STRUCTURE (WBS)

Figure 5-1 below shows the work breakdown structure for the implementation of MySustainavleForest project. Six major WPs have been identified:

WP 1 Coordination & Management

WP 2 Service Requirements Analysis

WP3 Service Development and Engineering

WP4 Service Demonstration and Training Program Preparation

WP 5 Innovations and Roadmap

WP 6 Outreach, Dissemination and Exploitation

Figure 5-1. Work Breakdown Structure

Major WPs are subdivided into tasks as follows:

WP1 Coordination & Management

T1.1 Project Control, Quality Assurance & Configuration Management T1.2 Technical Coordination

WP2 Service Requirements Analysis

WP2A PRT Case Specification

T2A.1 Detailed User Needs T2A.2 External Datasets Field Data and Data Quality T2A.3 Operational Environment Specification and Workflow Interfaces T2A.4 Service Requirements

WP2B HRZ Case Specification

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

34 of 67


T2B.1 Detailed User Needs, Functional and Performance Specification T2B.2 External Datasets, Field Data and Data Quality T2B.3 Operational Environment Specification and Workflow Interfaces T2B.4 Service Requirements

WP2C CZE Case Specification

T2C.1 Detailed User Needs T2C.2 External Datasets Field Data and Data Quality T2C.3 Operational Environment Specification and Workflow Interfaces T2C.4 Service Requirements

WP2D ESP Case Specification

T2D.1 Detailed User Needs T2D.2 External Datasets Field Data and Data Quality T2D.3 Operational Environment Specification and Workflow Interfaces T2D.4 Service Requirements

WP2E LTU Case Specification

T2E.1 Detailed User Needs T2E.2 External Datasets Field Data and Data Quality T2E.3 Operational Environment Specification and Workflow Interfaces T2E.4 Service Requirements

WP2F FRA Case Specification

T2F.1 Detailed User Needs T2F.2 External Datasets Field Data and Data Quality T2F.3 Operational Environment Specification and Workflow Interfaces T2F.4 Service Requirements

T2.4 High Level Design

WP 3 Service Development and Engineering

T3.1 Standards and Interoperability T3.2 Support to Field Data Survey T3.3 Platform and Processing Chain Preparatory Activities T3.4 Remote Sensing Algorithms, Models Tailoring and Data Fusion T3.5 Workflow Integration Engineering T3.6 Service Chain Testing

WP 4 Service Demonstration and Training Program Preparation

WP4A PRT Case Demo

T4A.1 Pre-Operational Service Planning & Support T4A.2 Regulatory Issues T4A.3 End-Users Pre-Operational Trials & Critical Assessment

WP4B HRZ Case Demo

T4B.1 Pre-Operational Service Planning & Support T4B.2 Regulatory Issues T4B.3 End-Users Pre-Operational Trials & Critical Assessment

WP4C CZE Case Demo

T4C.1 Pre-Operational Service Planning & Support T4C.2 Regulatory Issues T4C.3 End-Users Pre-Operational Trials & Critical Assessment

WP4D ESP Case Demo

T4D.1 Pre-Operational Service Planning & Support T4D.2 Regulatory Issues T4D.3 End-Users Pre-Operational Trials & Critical Assessment

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

35 of 67


WP4E LTU Case Demo

T4E.1 Pre-Operational Service Planning & Support T4E.2 Regulatory Issues T4E.3 End-Users Pre-Operational Trials & Critical Assessment

WP4F FRA Case Demo

T4F.1 Pre-Operational Service Planning & Support T4F.2 Regulatory Issues T4F.3 End-Users Pre-Operational Trials & Critical Assessment

T4.5 Business Model Validation

WP5 Innovation and Roadmap

T5.1 Fully Operational Service Concept &Usability Gap Analysis T5.2 Technology Trade-offs & Service Improvements T5.3 Future Service Roadmap and Transition Phase Definition

WP6 Outreach, Dissemination and Exploitation

T6.1 Communication T6.2 End-Users Engagement and Stakeholders Board Coordination T6.3 IPRs Management

5.2. WP EFFORT SUMMARY

Table 5-1. WP effort summary per partner

Partner 1 2 3 4 5 6 7 8 9 10 11

GMV RAIZ CFRI UFE FORESNA FOAL CNPF MADERA+ FORA EFI GUK TOTAL mm

WP 1 Coordination & Management 20 3 3 1 3 1 1 1 1 3 0 37

WP 2 Service Requirements Analysis 8 7 5 5 10 6 3 8 4 1 2 59

WP3 Service Development and Engineering

17 10 11 2 7 6 2 35 14 6,5 2 112,5

WP4 Service Demonstration and Training Program Preparation

18 14 4 4 4 8 4 9 3 4 0 72

WP 5 Innovations and Roadmap 11 2 17 3 3 5 1 7 4 2 1 56

WP 6 Outreach, Dissemination and Exploitation

10 4 6 2 2 2 2 9 4 14 2 57

TOTAL 84 40 46 17 29 28 13 69 30 31 7 393,5

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

36 of 67


5.3. WORK PACKAGE DESCRIPTIONS

5.3.1. WP 1 COORDINATION & MANAGEMENT

Table 5-2. WP1 description

WP No. WP1 Start Date or Starting Event KoM (M1-M36)

WP title WP 1 Coordination & Management

Participant No. 1 2 3 4 5 6 7 8 9 10 11 Total

Short name of participant

WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 20 3 3 1 3 1 1 1 1 3 0 37

Objectives

1. To coordinate and manage the entire project activities including technical, programmatic, quality and security issues, as well as contractual and ethical aspects (i.e. data privacy protection).

2. To keep control of the project ensuring that its objectives will be met within budget, calendar and scope.

Description of work

Task 1.1 Project Control, Quality Assurance & Configuration Management (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). The Project Control, Quality Assurance and Configuration Management describes the strategy, resource and calendar in management, quality and configuration of the project to control project finance, contractual issues and programmatic, to ensure the achievement of required quality and to ensure configuration procedures are established and properly used. Data policy for input datasets and implementation of project data management and preservation policy will be established. Also, it will ensure that applicable data privacy procedures are effectively implemented for handling and protection. All this information will be condensed in the Project Plan.

Project progress will be monitored, plans updated if needed and status reported including deliverables, actions, risks, associated contingencies plans, KPIs achievement as well as completed communication/exploitation activities. Direct and frequent relation with EC project officer will be kept.

Task 1.2 Technical Coordination (GMV, RAIZ, CFRI, FORESNA, EFI). This is to coordinate project technical aspects such as data formats and operational environments to facilitate the integration into End-Users workflows. It will include reaching agreements about technological issues or standard interfaces, protocols and processing chain tradeoffs. Interoperability issues will be tackled with respect of each End-User needs.

Deliverables

Nº Rel No Title Lead WP No Nature Level Due date

D01 D1.1 Project Plan GMV WP1 Report PU 30 November 2017

D12 D1.2 DWH use for 2018 GMV WP1 Report CO 31 July 2018

D13 D1.3 DWH request for 2019 GMV WP1 Report CO 31 July 2018

D28 D1.4 DWH use for 2019 GMV WP1 Report CO 31 July 2019

D29 D1.5 DWH request for 2020 GMV WP1 Report CO 31 July 2019

D37 D1.6 DWH use for 2020 GMV WP1 Report CO 30 April 2020

D14 D1.7 Interim Progress Report-1 GMV WP1 Report CO 31 August 2018

D24 D1.8 Progress Report-1 GMV WP1 Report CO 30 April 2019

D35 D1.9 Interim Progress Report-2 GMV WP1 Report CO 29 February 2020

D45 D1.10 Progress Report-2 GMV WP1 Report CO 31 October 2020

D06 D1.11 Data Management Plan (v1) GMV WP1 ORDP: PU 28 February 2018

D16 D1.12 Data Management Plan (v2) GMV WP1 Report PU 31 October 2018

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

37 of 67




Full description of deliverables in section 3.7

Milestones

Full description of milestones in section 3.6

WP1 calendar is pictured below

Reporting periods

Year


Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36


T1.1 Project Control, Quality Assurance & Configuration Management

T1.2 Technical Coordination

WP Deliverables


2017 2018 2019 2020

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

38 of 67


5.3.2. WP 2 SERVICE REQUIREMENTS ANALYSIS

Table 5-3. WP 2 description


WP title WP 2 Service requirements analysis



WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 8 7 5 5 10 6 3 8 4 1 2 59

Objectives

1. To refine End-User requirements confirming what is needed by customers from the service in a verifiable manner. 2. To define the validation of the case studies from End-Users perspectives to incorporate the project results into their

operations. 3. To derive technical specifications to support the service for the End-Users.

Description of work

Please note that all WP2X have always equivalent tasks´ definition; each one is focussed on a particular demo site and End-User. WP2A PRT Case Specification (GMV, RAIZ, GUK) Task 2A.1 Detailed User Needs, Functional and Performance Specification (GMV, RAIZ, GUK). This task is to processand organize the information about End-Users´ needs in terms of what and how the service needs to provide, including aspects related to frequency, accuracy, format and metadata. It shall define the indicators that the service needs to implement. The specification of indicators shall be verifiable. The specification of performances such as accuracy shall be quantified and agreed as feasible considering all available auxiliary in-situ data. Needs on interfaces with each End-User existing working environment shall be described in such a way that facilitates its prompt verification. All essential requirements will be clearly marked. The identified use cases and their focuses are associated to partners according to their priorities: NAVIGATOR-VC-010 which focusses on timber production including forest growth rate and wood quality NAVIGATOR -VC-020 which focusses on focusses on water resources, soil quality and biodiversity, End-User will compile use cases detailed information in a complete and harmonized manner. GMV will support the process from its wide expertise in remote sensing capabilities for feasibility issues. Task 2A.2 External Datasets, Field Data and Data Quality (RAIZ). Field procedures will be determined by end-users according to their expertise and own standard procedures. Sampling areas will be defined (e.g. plot area, sample size) and variables will be collected at tree, plot or landscape levels. Some of the variables relevant to the project are e.g. diameter at breast height, tree height and leaf area index (growth models and inventory); visual characterization of the vegetation vertical structure e.g. species, height class and percentage of cover (land cover characterization), visual classification of crown damage (defoliation and discoloration), above ground biomass and water quality. The quality of the selected auxiliary in-situ data for each demonstration site and models will be assessed and their quality control index will be determined. This task will include the preparation of appropriate datasets for calibration and testing, for End-Users training pedagogical exercises, and for non-operational trials or pre-operational uses. Task 2A.3 Operational Environment Specification and Workflow Interfaces (GMV, RAIZ, GUK). A description of the operational environment where the software will operate shall be prepared by End-User. In a service development, each subsystem might have interfaces to other external systems. This includes characterizing information sources in terms of existing format, protocols, quality and identification of harmonization needs. These external interfaces shall be specified in a verifiable manner. Expected changes in the operational environment shall be specified so that the service can be designed considering its adaptability and portability to next future conditions including potential statutory requirements or applicable standards. The operational environment description shall be complete regarding the use cases to be implemented during validation activities. Any limitation or constraint such as existing hardware, operating systems or communications

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

39 of 67


standards/protocols/band rate which are imposed by the End-Users´ operational environment to the service shall be specified in a verifiable manner. Task 2A.4 Service Requirements (GMV, RAIZ, MADERA+, FORA, EFI, GUK). This task is for GMV, with support from End-User, to derive the functional, security and performance detailed specification for the required service including the EO derived products specification associated to End-Users priorities and detailed use case. MADERA+, FORA and EFI will support service requirements definition from their respective expertise (wood quality, trees growth and socioeconomic) as needed. WP2B HRZ Case Specification (GMV, CFRI, GUK)

Task 2B.1 Detailed User Needs, Functional and Performance Specification (GMV, CFRI, GUK).

CFRI-VC-010 which focusses on timber production, CFRI-VC-020 and which focusses on stress indicators, Task 2B.2 External Datasets, Field Data and Data Quality (CFRI). Task 2B.3 Operational Environment Specification and Workflow Interfaces (GMV, CFRI, GUK). Task 2B.4 Service Requirements (GMV, CFRI, MADERA+, FORA, EFI, GUK). WP2C CZE Case Specification (GMV, UFE, GUK) Task 2C.1 Detailed User Needs, Functional and Performance Specification (GMV, UFE, GUK). UFE-VC-010 which focusses on forest inventory, UFE-VC-020 which focusses on drought trend, Task 2C.2 External Datasets, Field Data and Data Quality (UFE). Task 2C.3 Operational Environment Specification and Workflow Interfaces (GMV, UFE, GUK). Task 2C.4 Service Requirements (GMV, UFE, MADERA+, FORA, EFI, GUK). WP2D ESP Case Specification (GMV, FORESNA, GUK) Task 2D.1 Detailed User Needs, Functional and Performance Specification (GMV, FORESNA, GUK). FORESNA-VC-010 which focusses on biomass quantification including wood quality, FORESNA -VC-020 which focusses on disturbances/damages evolution and evaluation, Task 2D.2 External Datasets, Field Data and Data Quality (FORESNA). Task 2D.3 Operational Environment Specification and Workflow Interfaces (GMV, FORESNA, GUK). Task 2D.4 Service Requirements (GMV, FORESNA, MADERA+, FORA, EFI, GUK). WP2E LTU Case Specification (GMV, FOAL, GUK) Task 2E.1 Detailed User Needs, Functional and Performance Specification (GMV, FOAL, GUK). FOAL-VC-010 which focusses on timber production including wood quality, FOAL -VC-020 which focusses on habitat fragmentation. Task 2E.2 External Datasets, Field Data and Data Quality (FOAL). Task 2E.3 Operational Environment Specification and Workflow Interfaces (GMV, FOAL, GUK). Task 2E.4 Service Requirements (GMV, FOAL, MADERA+, FORA, EFI, GUK). WP2F FRA Case Specification (GMV, CNPF, GUK) Task 2F.1 Detailed User Needs, Functional and Performance Specification (GMV, CNPF, GUK). CNPF-VC-010 which focusses on timber production CNPF-VC-020 which focusses on damages evolution and evaluation Task 2F.2 External Datasets, Field Data and Data Quality (CNPF, GUK). Task 2F.3 Operational Environment Specification and Workflow Interfaces (GMV, CNPF, GUK). Task 2F.4 Service Requirements (GMV, CNPF, MADERA+, FORA, EFI, GUK). Task 2.4 High Level Design (GMV). This task is to derive the high level technical architecture from the detailed service specification to ensure that the service fulfills the End-Users and is able to deal with any required customization or configuration option and to cope with any threat in the processing chain. Also, any tailoring, limitation or constraint which is imposed by the End-Users operational environment to the service shall be considered.

Deliverables

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

40 of 67



D03 D2.1 End-User Use Cases FORESNA WP2 Report PU 31 January 2018

D09 D2.2 Service Requirements and Validation of Use Cases


D10 D2.3 Architectural Design GMV WP2 Report CO 31 May 2018


Milestones


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

41 of 67


5.3.3. WP3 SERVICE DEVELOPMENT AND ENGINEERING



WP title WP 3 Service development and engineering



WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 17 10 11 2 7 6 2 35 14 6,5 2 112,5

Objectives

1. To define new remote sensing algorithms or refine existing ones. 2. To integrate all prototyped components and needed technological infrastructure to build the platform –

technological infrastructure- which will allow to provide a fully automated service. 3. To check that each component meet its specification. 4. To prepare reference datasets for testing and training purposes. 5. To verify that the integrated system/service works as requested in End-Users requirements.

Description of work Task 3.1 Standards and Interoperability (GMV, RAIZ, CFRI). This task is to consider any applicable standard to ensure that internal interfaces are working properly to ensure smooth service integration into each End-User operational environment and workflow; and also external interfaces are stable and fulfil the End-Users requirements towards applicable regulations from external authorities or entities. Task 3.2 Support to Field Data Survey (MADERA+). This task will include the preparation of appropriate datasets for calibration and testing in Spain, France, Croatia, Czech Rep. and Lithuania to support End-Users, in line with their requests, especially on non-destructive acquisition of wood quality truth data. Task 3.3 Platform and Processing Chain Preparatory Activities (GMV, CFRI, MADERA+, FORA, EFI, GUK). GMV existing space based data acquisition means will be tailored for the service requirements. A semi- or fully-automated processing chain service will be built into eoforest. Its IT infrastructure will be open and facilitate an area for future research and collaboration free of charge. Recorded data from the on-field campaigns will be used to calibrate the remote sensing algorithms. Also, eoforest will be made as configurable as possible to ease accommodation of End-Users criteria and parameters (i.e. resolution, frequency of updates, accuracy parameters, etc.). Task 3.4 Remote Sensing Algorithms, Models Tailoring and Data Fusion (GMV, CFRI, MADERA+, FORA, EFI, GUK). GMV remote sensing algorithms, FORA´s LIDAR processing, advanced scientific models from FORA, MADERA+ and EFI on forest growth, wood quality and socio-economic aspects respectively, and data fusion will be tailored to solve the End-Users challenges, each one focused in different scenarios (Mediterranean Oceanic, Temperate Hyperoceanic and Temperate Continental). An adaptation and integration of the specific forestry genre/species models will be needed, including the integration with socio-economic data and models and with tailored SWOT methodologies [Marino2013] for specific use cases (i.e. fire disturbance, wood quality). RAIZ specific growth and economical models, calibrated to its forest conditions, will be use to its own case studies. Experimentation will be run and early estimates on products accuracy will be obtained. Task 3.5 Workflow Integration Engineering (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). This task is to ensure a technological integration of all the needed working environment components to fulfil the defined High Level Design. Three cycles integration strategy will be followed: only essential EO derived products will be prioritized for the early version. A replication of each End-User working environment would be needed to test integration and service robustness without impacting in End-Users operations. This may include building dummies (i.e. data flows simulation) to simulate external entities interfaces of the operational environment to isolate and solve problems. EO derived products will be OGC compliant provided by GMV for integration into the End-Users workflows according to each End-User´ ICT infrastructure. Task 3.6 Service Chain Testing (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). This is to test the complete service processing chain with respect to operational End-Users requirements according to End-Users validation use cases and procedures. This implies to prepare and coordinate the overall service infrastructure testing activities under realistic conditions with real data for relevant operational scenarios.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

42 of 67


Deliverables


D11 D3.1 Integration and Validation Plan GMV WP3 Report PU 31 May 2018










Milestones


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

43 of 67


5.3.4. WP4 SERVICE DEMONSTRATION AND TRAINING PROGRAM PREPARATION



WP title WP 4 Service Demonstration and Training Program Preparation



WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 18 14 4 4 4 8 4 9 3 4 0 72

Objectives

1. To show that the set of integrated technologies fulfil the End-Users requirements and support their operational process in an efficient and effective way.

2. To develop a training program for End-Users in order to facilitate MySustainableForest service usage. 3. To demonstrate the Business Model

Description of work All WP4X have always equivalent tasks´ definition; each one is focussed on a particular demo site and End-User. WP4A PRT Case Demo (GMV, RAIZ) Task 4.1 Pre-Operational Service Planning & Support (GMV, RAIZ). This task is for End-User to plan and prepare all needed logistics and practical arrangements to conduct the validation use cases into their operational environment. It will ensure that any needed action for providing or configuring the service is properly performed and accurately documented in the service´s guide. Task 4.2 Regulatory Issues (RAIZ). This task is to analyse the potential of the service products to reduce effort in fulfilling regulatory requirements such as mandatory local, regional or national reporting, certification regulation or EU Timber Regulation (EUTR). Task 4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, RAIZ). End-User will run the service in a preoperational mode fully integrated into their workflows as trial for the project duration to conduct the validation use cases within its operational environments –. Such pre-operational trials will be assessed by End-User with the final aim of deriving an independent critical evaluation of the EO derived products. The pre-operational usage will start with the early version and then will evolve into pilot usages with both the enhanced and advanced versions of the service. WP4B HRZ Case Demo (GMV, CFRI) Task 4.1 Pre-Operational Service Planning & Support (GMV, CFRI). Task 4.2 Regulatory Issues (CFRI). Task 4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, CFRI). WP4C CZE Case Demo (GMV, UFE) Task 4.1 Pre-Operational Service Planning & Support (GMV, UFE). Task 4.2 Regulatory Issues (UFE). Task 4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, UFE). WP4D ESP Case Demo (GMV, FORESNA) T4.1 Pre-Operational Service Planning & Support (GMV, FORESNA). T4.2 Regulatory Issues (FORESNA). T4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, FORESNA). WP4E LTU Case Demo (GMV, FOAL) Task 4.1 Pre-Operational Service Planning & Support (GMV, FOAL). Task 4.2 Regulatory Issues (FOAL). Task 4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, FOAL). WP4FRA Case Demo (GMV, CNPF) Task 4.1 Pre-Operational Service Planning & Support (GMV, CNPF). Task 4.2 Regulatory Issues (CNPF). Task 4.3 End-Users Pre-Operational Trials & Critical Assessment (GMV, CNPF).

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

44 of 67


Task 4.4 End-Users Training Preparation (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). This activity is to develop a training program for End-Users of the service. Training material will be structured in basic contents (i.e. sustainable forestry, forestry ecosystem services, forestry vulnerability to climate change, remote sensing principles, Copernicus, etc.) to be prepared by EFI and specific material (i.e. examples of services use cases) under GMV responsibility. Teaching strategies will combine lectures and practical sessions. It is foreseen to inject the basic contents of End-Users capacity building course to the Stakeholders awareness communication with a feedback process which will be designed with a methodical approach to elicit, analyse, prioritize and document the End-Users’ requirements. Thus, activities to be executed, in collaboration especially with project partners involved on the pilot demonstrations, will include: preparing training material, delivering training and compiling stakeholders feedback. Three cycles for training the strategy will be followed in line with the workflow engineering integration plan (early, enhanced and advanced service). Training elements will include materials for use both online and in a classroom non-operational setting. The latest includes technical on-site support when delivered as part of a given Stakeholders workshop. Training material will be improved according to attendees´ suggestions and enriched with up-to date scientific knowledge on the chosen methodological and technological approaches, including relevant aspects of ecosystem functioning and the socio-economic system. End-Users training feedback will be collected for an assessment of the service in meeting their particular requirements and next future expectations. Task 4.5 Business Model Validation (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). GMV will tune the service products, according to the trials critical assessment. GMV, partners developing models- MADERA+, FORA, EFI- and End-Users will re-assess the associated business models considering both the End-Users training feedback and their cost/benefit valuation. Current hypothesis for financial projections (i.e. service recurrent costs, pricing, etc.) needs to be confirmed or modified accordingly. This task will also build the structure for the Service Level Agreements and feed the elaboration of the Business Plan.

Deliverables


D11 D3.1 Integration and Validation Plan GMV WP3 Report PU 31 May 2018










Milestones


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

45 of 67


5.3.5. WP 5 INNOVATIONS AND ROADMAP



WP title WP 5 Innovations and roadmap



WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 11 2 17 3 3 5 1 7 4 2 1 56

Objectives

1. To define a technological roadmap to ensure a smooth development of a fully operational service, which will be kept at the scientific cut-of-the-edge level in next future for competitive reasons.

Description of work

T5.1 Fully Operational Service Concept &Usability Gap Analysis (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, GUK). This task is to drive project results looking into long term added value for End Users and considering their feedback (based on training, demonstration trials and pre-commercial activities) on pending or new needed features, with special interest on enhanced performances or complementary features (e.g. data fusion, etc.). A proposal on prioritized features, derived from such usability gap, for further service concept will be prepared. T5.2 Technology Trade-offs & Service Improvements (GMV, CFRI, MADERA+, FORA, EFI, GUK). This task is toassess service usage and potential improvements with respect to technological trends, new available satellite datasets (i.e. Sentinel-3 for land surface temperature), etc. A proposal on prioritized features, derived from such technological advances, for further service improvements will be prepared. T5.3 Future Service Roadmap and Transition Phase Definition (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI, GUK). Considering the usability gap analysis and the service improvements analysis, this task is to identify future and required capabilities of the service in terms of requested needs for a successful international service and time to market. Services in the pipeline already identified are identification of allergenic species and planning for optimal reforestation face to climate change. It will be assessed the applicability of the proposed service into different markets segments (i.e. small forestry owners, large public owners) so that a transition phase towards exploiting the project results into adjacent markets niches (i.e. biomass energy) can be defined and planned. This will be achieved in coordination with project workshops and associated targeted surveys. A plan to prepare the platform for users registration and open contents management will be prepared. Emerging information needs and potential market opportunities will be fed into these activities in order to take into account global megatrends (development of the bio-economy, increased urbanization, rural abandonment), relevant policy processes (i.e. EU FLEGT, REDD+, EU Sustainability criteria, Bonn Challenge, etc.), Copernicus core services evolution, existing information platforms (i.e. JRC EFFIS, EEA, Bioeconomy Observatory ), and societal developments (i.e. internet of things, citizens science).

Deliverables


D27 D5.1 Product Roadmap (v1) CFRI WP5 Report CO 30 June 2019

D41 D5.2 Product Roadmap (v2) CFRI WP5 Report CO 30 September 2020

D47 D5.3 Needs under global change and opportunities with new EO sensors for SFM



Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

46 of 67


Milestones


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

47 of 67


5.3.6. WP 6 OUTREACH, DISSEMINATION AND EXPLOITATION



WP title WP 4 Service Demonstration and Training Program Preparation



WP leader

Participant

GM

V

RA

IZ

CFR

I

UFE

FOR

ESN

A

FOA

L

CN

PF

MA

DER

A+

FOR

A

EFI

GU

K

Person/months 10 4 6 2 2 2 2 9 4 14 2 57

Objectives

1. To define and implement the most effective possible communication and exploitation plan making the best usage of the project assets.

2. To ensure that the communication plan is implemented in coordination with End-Users, industrial partners and other stakeholders such as forestry companies and even EC.

3. To maximize the relevance and applicability of scientific marketing through open dissemination of findings and results to academic and scientific world.

4. To establish mechanisms for End-Users engagement along project duration and after its termination.

Description of work Task 6.1 Communication (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). A strategy for communication during the project timeframe will and implemented with the involvement of stakeholders and coordinated with project partners. It will be based be the concepts and approaches described above (see page 33 & table 15) and will go beyond communicating project activities to address awareness raising on the great opportunities that available remote sensing and ICT technologies are opening for improved forest management. This will be based in research results, real life forestry stakeholders problems linked with success cases and testimonials. The communication strategy will include precise communication objectives, the definition of target groups (including stakeholders and potential End-Users) and the definition of adequate communication channels, styles of engagement and communication actions. It will be supported by strong project branding, a website, social media channels and a dissemination package (brochures, factsheets, motion infographics, press releases and scientific articles, a bi-annual newsletter, among others). Relationships with EU and wider society, social networks and media agencies as well as with European sciencedivulgation organizations will be established. The impact of the communications actions will be evaluated annually for impact (i.e. audience, events´ attendees, visibility in social-media, genre, etc.) and the strategy will be adapted throughout the project, as needed to achieve an effective outreach of results, during and after the project. Task 6.2 End-Users Engagement and Stakeholders Board Coordinationº (GMV, RAIZ, CFRI, UFE, FORESNA, FOAL, CNPF, MADERA+, FORA, EFI). End-Users engagement will be conducted through the execution of the planned Stakeholders´ workshops with different aims according to the project progress and the status of the service. These workshops will seek: 1/ to raise awareness about the potential of both remote sensing and ICT technologies to support the needs of broader range of different End-Users for responsible forest exploitation; 2/ to attract interest about the potential benefits of the resulting project solutions illustrating them by End-Users on their demonstration trials; 3/ to create the willing to adopt the forest management support services co-developed with End-Users. A link will be established with DG AGRI -Environment, Forestry and Climate Change Unit- to involve and create synergies with ongoing (i.e. on biomass) and next future (i.e. sustainable forestry) relevant Focus Groups. Stakeholders Board will be kept open at any moment for engaged End-Users to join on a voluntary basis. This task will also facilitate the coordination with the Stakeholders Board regarding End-Users Requirements, managing their expectations as well as guide the consortium on market issues as needed. Task 6.3 IPRs Management (GMV, MADERA+, FORA, EFI). The agreement on IPRs for future product exploitation will be managed as soon as preliminary results are available to ensure that patents to keep the freedom to operate are properly registered. The Innovation, Dissemination and Exploitation Manager will liaise with incumbents to prepare any material needed for the Project Board to decide about IPR issues on foreground, and specially on the contractual agreements for its fair exploitation. Task 6.4 Commercial Exploitation (GMV, MADERA+, FORA, GUK). A plan for worldwide commercial exploitation will be prepared and pre-commercial activities executed from project kick-off in line with its potential exportation and market replication. A push strategy will be implemented during the project: service demonstrations and structured surveys on End-

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

48 of 67


Users’ needs will be performed through active attendance to international congresses and trade-shows. Business model and financial projections might be adjusted along project life time on the light of the intermediate project results with particular attention to the request of IP protection in the geographical areas of major potential market interest. Sustainable revenues for all consortium partners will be pursued in the medium and long term either from project results exploitation or from the benefits of its usage. Business will be ready to be launched and comercial exploitation planned and ready to be executed.

Deliverables



EFI WP6 Report PU 31 January 2018





D05 D6.04 Communication Materials (v1) EFI WP6 Websites, patents filling, etc.

PU 31 January 2018


PU 30 April 2018


PU 31 October 2018


PU 30 April 2019


PU 30 April 2020


PU 31 October 2020




GMV WP6 Report PU 31 January 2019







PU 31 March 2019



PU 30 September 2020




GMV WP6 Report CO 31 January 2020

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

49 of 67




D02 D6.19 Background Intellectual Property

GMV WP6 Report CO 30 November 2017

D44 D6.20 Foreground Intellectual Property



Milestones


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

50 of 67


6. CONFIGURATION, INFORMATION AND DOCUMENTATION MANAGEMENT

The Configuration Management section defines all the activities concerning configuration, information and documentation management, understanding by CM the process of:

Identifying and defining the configuration items corresponding to the project.

Controlling its storage.

Controlling the release and change of these items through the project life cycle.

Recording and reporting the status of configuration items.

Verifying the completeness and correctness of configuration items.

6.1. CONFIGURATION MANAGEMENT

6.2. GENERAL

Under the scope of the Configuration Management Area, the following major activities are addressed:

Configuration Identification: comprising determination of product structure, selection of configuration items, documenting the configuration item’s physical and functional characteristics including interfaces and subsequent changes, and allocating identification characters or numbers to the configuration items and their documents.

Configuration Control: comprising the control of changes (evaluation, co-ordination, approval or disapproval and implementation) to a configuration item after formal establishment of its configuration documents.

Configuration Status Accounting: recording and reporting of the established configuration documents, the status of proposed changes and the status of the implementation of approved changes.

Verification of Configuration: verifying that configuration documents are in agreement with configured items.

6.2.1. CONFIGURATION IDENTIFICATION

A Configuration Item (CI) may be any kind of software, a document or a set of CIs, that is separately controlled by the Configuration Manager. There shall be a unique identifier assigned to each configuration item.

6.2.2. CONFIGURATION CONTROL

The deliverables configuration items shall be subject to configuration control. This section describes how the configuration control is achieved on this project.

The configuration control will be performed in the following way in order to implement changes to the configuration and identify the records to be used for tracking and documenting the sequence of steps for each change.

The following process will be used in the configuration control:

board functions, responsibilities, authorities;

processing changes;

change requests;

change proposal;

change evaluation;

change approval;

change implementation;

processing planned configuration departures (deviations);

Processing unplanned configuration departures (product non-conformances, waivers).

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

51 of 67


6.2.3. DOCUMENTATION MANAGEMENT

6.2.3.1. REDMINE tool for configuration management

Configuration Management Tool used in the context of project management: Redmine tool is used for documentation.

Redmine (https://www.easyredmine.com/ ) significantly improves the management of large projects. It represents a single focal point to perform different configuration management activities for all involved entities.

Main characteristics are summarised as follows:

Friendly web interface allowing an easy, intuitive, quick and remote access through Intranet.

Different user permissions allowing specific functionalities, privileges and level of information to different users.

Management of the status for each configuration item (SPR, Request, Action, etc.).

Homogeneous and coherent environment to dynamically manage the following configuration items:

Documentation.

Document Change Request.

Software Problem Reports and Software Modification Reports.

List of Actions.

General risks and Risks at Milestones.

Questions and Comments, via a Mail Box utility.

Reviews of documents

6.2.3.2. Delivery methods for documentation

For the exchange of documents, Redmine web access, GMV FTP site and emails notification will be used. GMV shall always be responsible for the submission of the documentation deliveries to the EC through the H2020’s Grant Management System (SyGMa).

6.3. IDENTIFICATION AND MANAGEMENT

A Configuration Item (CI) is defined as an aggregation of software that is designated for configuration management and is treated as a single entity in the CM process. Configuration Items include the plans, specifications, design documentation, testing materials, software tools, executable code, code libraries, data files, source code files and documentation for installation, maintenance, operations and use.

One of the first steps in the CM activity is to establish the rules to uniquely identify the different configuration items to be built or acquired during the project.

Each Configuration Item will have a unique identification code (that includes a short name identification of the Configuration Item) that will be maintained during the whole life cycle.

The following configuration items shall be subject to configuration control: Documents (both internally generated by GMV and external in the scope of the project).

Code related items.

The following sections describe the identification rules for the different types of CI. Identification rules are also provided for project communications (faxes, letters, e-mails) and other records relevant to the project.

6.3.1. CONFIGURATION ITEMS MANAGEMENT

This section describes the management of the different configuration items.

The reference line in a project is made up by:

External Documents: All documents that have not been generated by GMV or by any member of the project consortium is considered as external document.

Internal documents: Documents prepared by the members of the project consortium. They will be reviewed internally

https://www.easyredmine.com/

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

52 of 67


and finally sent to the EC by using SyGMa tool.

6.3.2. DOCUMENT IDENTIFICATION

The following rules apply to documents:

Document External Code: Project Document Identifier, as per Table 3-3. Project Deliverables,

Document Internal Code (GMVAD): for the published product documents, which is necessary for archival in GMV’s library.

Document Version/Revision number (if required).

Document files naming conventions.

The configuration identifier (CI) for project documentation will have the following form:

NN_RR_[Title] for contract deliverables; where NN_RR defines the sequential deliverable number and the relative (to the WP) deliverable number. Sample

D01_D1.1_Project_Management_Plan{this document

Descriptor_Title_CompanyAcronym_yyyymmdd. Samples:

MOM_Conferencall_FORESNA_MADERA+_FORA_GMV_20180219

TND_AOIs_data_description_All_20180315

OTH_French_AOI_description_WEB_CNPF_20180401

Table 6-1 Document Types Codes

Document Type Descriptor

Deliverable number (according to the Grant Agreement see [AD.1]).

Numbered from D01 to D49, check Table 3-3. Project Deliverables Dnn_rr

Change Notice/Change Request CN/CR

Minutes of Meeting(s)_ MOM

Technical document TND

Other Items (used for surveys results, etc) OTH

Table 6-2 Company Acronym for the naming of the documents

Acronym Company

GMV GMV AEROSPACE AND DEFENCE SA

RAIZ RAIZ - INSTITUTO DE INVESTIGACAO DA FLORESTA E PAPEL

CFRI HRVATSKI SUMARSKI INSTITUT

UFE MENDELOVA UNIVERZITA V BRNE

FORESNA ASOCIACION FORESTAL DE NAVARRA

FOAL FOREST OWNERS ASSOCIATION OF LITHUANIA

CNPF CENTRE NATIONAL DE LA PROPRIETE FORESTIERE

MADERA+ MADERA PLUS CALIDAD FORESTAL SL

FORA FORA FOREST TECHNOLOGIES SLL

EFI EUROPEAN FOREST INSTITUTE

GUK GMV INNOVATING SOLUTIONS LTD

The document identification code must appear in the cover page of the document, together with these data: company name, project name, title, issue and revision, issue date and the appropriate signatures.

Additional information for the deliverable documents is related with the: dissemination level, Workpackage it belongs, task where it’s implemented, lead beneficiary name, contributing beneficiary (ies) (if there are), due date of deliverable and actual submission date. This additional information will appear following to cover page in the similar format:

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

53 of 67


Project Acronym

Project Title

Project Coordinator

Project Duration

Grant Agreement

Deliverable Number

Dissemination Level

Workpackage

Task

Lead beneficiary

Contributing beneficiary (ies)



Figure 6-1. Additional information to the cover page

In addition, all the pages of the document shall include – in its header – the document identification code, issue, issue date and page number.

6.3.3. GMV INTERNAL CODE (GMVAD)

All the documents that are project deliverables created/reviewed by GMV will contain a Document Internal Code or GMVAD.

Document internal code has the form GMVAD 2nnnn/yy Vx/aa. The internal code is only used for internal control purposes at GMV. The GMV library responsible provides this code where:

nnnn 4 digits sequential number provided by the GMV library.

yy last two digits of the published date.

x the number of times that have been published.

aa last two digits of the year of the update date.

Example of the evolution of one document:

First version: GMVAD 24682/17 V1/17

New version: GMVAD 24682/17 V2/18

6.3.4. DIGITAL SIGNATURE

Digital signature applies to technical documents, and any other document requiring a signature. The digital certificate is personal, and it contains the signer's public and private keys. All GMV's employees have an assigned digital certificate.

GMV issues certificates used for signing at a corporate level, and also for deliverables.

Not all the members of consortium have available the digital signature, so other methods (such as scanned signatures with acknowledge of approval) will be procured for the signature of the documents.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

54 of 67


7. MANAGEMENT, CONTROL, DIRECTION & MONITORING

7.1. PROJECT CONTROL PROCEDURES

Project Control is implemented according to the GMV Quality System (Project Management Procedure, GMV-SGC-PRO-005) Project Management Practices. Project Management Practices may be adapted as needed by specific Project Management Requirements. Projects are controlled using the following techniques:

Independent Project Control

Progress and Schedule Control

Metrics Control

Project Consortium Monitoring

Actions Items Control

Risk Management

The GMV Project Manager is responsible for making readily available to the customer up to date information on Project Status through Periodic Reports. In the case of this project, the Progress Reports (PR) shall be sent to EC through three periodic reports (as defined in [AD.1]).

The preparation and delivery of Progress Reports do not prevent anyhow the possibility of immediate communication of any problem or abnormal circumstances detected during the course of the project. The immediate communication of problems aside the Periodic Report communication channel shall be restricted only to those aspects potentially affecting the achievement of the project technical objectives within schedule and to the expected performances.

The Project Reporting for MySustainableForest is established for PR1 (M18, April 2019) and PR2 (M36, October 2020).

From the end of each progress period there are 60 days to provide the report to the EC.

Then, the EC has 90 days to approve/reject claimed costs and transfer the corresponding payment to the Coordinator.

Coordinator is in charge of submitting this Report although all beneficiaries needs to contribute their parts.

More in detail, the Periodical Reports are composed by:

Periodical technical report, which must provide a summary for publication containing:

an explanation of the work carried out by the beneficiaries;

an overview of the progress towards the objectives of the action, including milestones and deliverables identified in Annex 1. Exploitation and dissemination activities. Communication activities.

a summary for publication by the Agency;

the answers to the ‘questionnaire’, covering issues related to the action implementation and the economic and societal impact…

Periodical financial report containing:

Individual financial statement, detailing eligible costs (even if they exceed the amounts). Certification that information is full, reliable, costs are eligible, all receipts have been declared

Periodic summary financial statement, created automatically by the electronic exchange system, consolidating the individual financial statements for all reporting periods and including the request for payment of the balance

The Final Report (delivered at the end of the project) must contain:

Final technical report, which must provide a summary for publication containing:

an overview of the results and their exploitation and dissemination;

the conclusions on the action, and

the socio-economic impact of the action;

Final financial report containing:

final summary financial statement, created automatically by the electronic exchange system, consolidating the

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

55 of 67


individual financial statements for all reporting periods and including the request for payment of the balance and

certificate on the financial statements (CFS) for each beneficiary and for each linked third party that requests a total contribution of EUR 325 000 or more. Each CFS is composed of two separate documents:

The Terms of Reference (‘the ToR’) to be signed by the beneficiary and the Auditor;

The Auditor’s Independent Report of Factual Findings to be issued which includes the agreed-upon procedures to be performed by the Auditor, and the standard factual findings to be confirmed by the Auditor.

7.1.1. INDEPENDENT PROJECT CONTROL

Additionally, according to the GMV rules, the progress of each project, its schedule and all other project management metrics are internally reported in a monthly basis. This type of report serves as input for a Project Independent Control that analyses Project Metrics for all the projects under development at GMV. This Project Independent Control, after the reports being conveniently processed, is able to alert on project problems from a Company global perspective.

Project Independent Control is performed using statistical Project Management Models that continuously are evolving. The result of this process provides the means to detect abnormal situations that may be undetected at Project level by the Project Manager.

7.1.2. PROGRESS AND SCHEDULE CONTROL

The Project Manager is responsible for the preparation and maintenance of the Project Schedule, as derived from the WBS and the associated WP descriptions. The Project Manager shall perform the following activities:

Follow-up of the progress of all activities under development

Continuous update of the Project Schedule and Costs according to the Progress

Generate print-outs of the schedule Gantt Chart

Effective schedule control is based on the agreed schedule. This schedule is the only reference for all related planning data. The applicable schedule is the only official information as far as dates are concerned. In order to avoid potential incompatibilities, all remaining sources of information (e.g. WPD) shall be referred only to dates relative to milestones and not to absolute dates.

Schedule control is based on a ´pro-active´ process anticipating potential deviations with a close coordination with the Risk Management procedures. In the case that the Project Manager or the Project Controller detects any problem from his assessment of the schedule and actual status of the work, it shall performed a thorough analysis of the situation, identifying the causes for such a problem, assessing possible recovery means and reporting immediately on the problem and the results of the assessment performed, including any and all information relevant to the recommended recovery actions.

Following EC approval (in writing by duly authorised representative) of the recommended course of actions, the Project Manager will immediately implement the necessary actions.

In accordance with the principle of management-by-exception, if the Project Manager / Project Controller do not detect any significant deviation in the status with respect to the plans, the work shall proceed as planned with information on project status in the progress reports.

The schedule control system shall ensure the:

Realistic representation of the project in its totality, with no omissions

Effective communication of the latest approved bar charts or other schedule information to the staff at all levels ultimately responsible for the execution of the work

Adherence to the requirements of these plans and schedules, to actively control the execution of work

Immediate reporting of actual or foreseeable deviations from the agreed plan to EC

Effective processing of reported deviations including the definition and implementation of the corrective action

Gantt charts will serve as the schedule reporting documents that take into account all essential tasks, processes and events required to accomplish the contract objectives and accurately reflect the results of the subcontractors. Milestone trend analyses will be performed as well and a record maintained of the predicted achievement date for each milestone.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

56 of 67


In the case that the Project Manager detects any problem or deviation of the planned Schedule and Cost, it shall be performed a thorough analysis of the situation. As result of this analysis, the Project Manager shall be able to identify the causes and implement the needed recovery actions.

Progress and Schedule Control Metrics are GMV internally reported through the Project Independent Control process.

7.1.3. METRICS CONTROL

Along with progress and schedule control, the GMV Quality System defines several other internal metrics for project control. Those metrics are adapted and used or not according to project needs. Metrics are periodically controlled by the Project Manager, typically in a monthly basis. In the case that the Project Manager detects any deviation in those metrics, the needed recovery actions shall take place.

Internal Project Metrics issues to control are:

Productivity

Actions Status

Non-Conformities (NC) status

Stability Requirements

Project Control Metrics are internally reported for the Project Independent Control procedure.

7.1.4. PROJECT BOARD. PROJECT CONSORTIUM MONITORING.

MySustainableForest project progress monitoring shall be made through Project Board during their monthly progress internal reviews meetings.

Project Board will be responsible of the most important decisions on the project such as:

Potential amendments to the contractual documents,

Possible adaptations of work plan and allocated budgets,

Risks assessment

Decisions concerning IPR issues on the foreground knowledge developed during the project’s life cycle , and especially on the contractual agreements for its fair exploitation

Partial and final results confidentiality harmonisation among dissemination issues, multilingualism issues, ethical issues, gender aspects,

Assessment of the scientific quality of the results,

Assessment of the commercial potential of the results

The main features of the Project Board are:

One representative per partner

Decisions will be taken by Project Board by majority vote

The Board agenda will be focused on specific issues depending on the project phase.

The project coordinator will ensure the implementation of the decisions taken. Any major decision regarding the GA will be submitted to EC for approval.

Monitoring shall provide an up-to-date explanation of any technical, contractual and schedule problems, and shall therefore contain the following information (if necessary):

Management: Concise descriptions of all important problem areas, their criticality and anticipated impact (e.g. delays in the schedule or non-conformance with the Contract requirements), the Contractor’s current work and the expected results, as well as the continuing problem- solving activities.

Schedule Report (if necessary): Overall project charts showing the duration and progress of main phase interface events and milestones.

Technical: The status of technical problem issues, design, implementation, interface and testing shall be summarized. All technical issues that may have an impact on schedule, cost or the documentation baseline shall be raised.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

57 of 67


Action Items List: A listing of action items from all previous meetings shall be included showing the status. It shall distinguish between current open actions and actions closed since the last issue of the Progress Report (with closure details).

Invoicing and Payment Status: To monitor actual payment status versus planned, and update the payment forecast for Contractors at all levels.

Statement of Critical Issues affecting the project and proposed solutions.

These information could be provided either as part of the Progress Report or in a separate report to be issued at the same time of the Progress Report.

Project Board meetings shall be held monthly by teleconference, tentatively during the first week. The OS gotomeeting tool shall be used for the teleconferences. The following table shows the scheduled project board meetings for MySustainableForest:

Table 7-1. Upcoming Project Board Meetings

Id Objective Project Month Date Tentative Date

PBM1 Review of Items to be covered during Workshop 1 5 Mar-18 06/03

PBM2 Future tasks. Deliveries and WP progress (TBC) 6 Apr-18 10/04

PBM3 Future tasks. Deliveries and WP progress (TBC) 7 May-18 04/05

PBM4 Future tasks. Deliveries and WP progress (TBC) 8 Jun-18 05/06

PBM5 Future tasks. Deliveries and WP progress (TBC) 9 Jul-18 03/07

PBM6 Future tasks. Deliveries and WP progress (TBC) 10 Aug-18 01/08

PBM7 Future tasks. Deliveries and WP progress (TBC) 11 Sept-18 04/09

PBM8 Future tasks. Deliveries and WP progress (TBC) 12 Oct-18 02/10

PBM9 Future tasks. Deliveries and WP progress (TBC) 13 Nov-18 06/11

PBM10 Future tasks. Deliveries and WP progress (TBC) 14 Dec-18 04/12

7.1.5. PROJECT MEETINGS AND REVIEW CONTENTS

Project meetings are partially coincident with Milestones and Reviews. Moreover, there are other meetings on account of the stakeholder’s workshops and practical training on the services.

Figure 7-1. Calendar overview of project meetings

Below, Table 7-2. Scheduled Project Meetings shows the tentative plan for project meetings.

Meetings locations follow a spatial sequence across all AOIs tested during the project. This is done so for a double reason: first to validate on site the specific forest services and requirements and, second, to allow and foster having encounters with local end-users and federated stakeholders.

Year


Month Nº 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Logic flow periods



WP6 Workshops

Practical Training





Atlantic Forests-





regions




2017 2018 2019 2020





Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

58 of 67


Table 7-2. Scheduled Project Meetings

Id Objective Place Month Tentative Date Host

KOM Start of the Project Madrid 1 21/11/2017 GMV

WKS 1 Stakeholders Workshop 1 Brussels 5 13/03/2018 GMV at EFH

AR Analysis Review Pamplona (TBD) 6 17-18/04/2018 FORESNA

RV1 1st interim review Ourense (TBD) 9 03-04/07/2018 MADERA+

S1 Early Service Readiness Jastrebarsko, Croacia (TBD) 13 27-28/11/2018 GMV / CFRI

WKS 2 Stakeholders Workshop 2 Jastrebarsko, Croacia (TBD) 14 27-28/11/2018 CFRI

TR1 Training 1 Jastrebarsko, Croacia (TBD) 14 27-28/11/2018 CFRI

MTR Mid Term Review Křtiny, Czech Republic (TBC) 18 21-22/04/2019 UFE

RV2 1st review report Křtiny, Czech Republic (TBC) 18 21-22/04/2019 UFE

S2 Enhanced Service Readiness Orléans/Aquitaine, France (TBD) 22 30-31/07/2019 CNPF

WKS 3 Stakeholders Workshop 3 Aveiro Eixo, Portugal (TBD) 27 28-29/01/2020 RAIZ

RV3 2nd interim review Aveiro Eixo, Portugal (TBD) 27 28-29/01/2020 RAIZ

TR2 Training 2 Aveiro Eixo, Portugal (TBD) 27 28-29/01/2020 RAIZ

S3 Advanced Service Readiness Barcelona, (TBD) 30 21-22/04/2020 EFI

WKS 4 Stakeholders Workshop 3 Vilnius, Lithuania (TBD) 34 03-04/09/2020 FOAl

TR3 Training 3 Vilnius, Lithuania (TBD) 34 03-04/09/2020 FOAL

RV4 Final review report Madrid, Oxford (TBD) 36 13-14/10/2020 GMV/GUK

The following Table 7-3 shows deliverable version to be provided for review at each milestone; see Gantt Chart for planned dates:

Table 7-3. Review Contents per Project Meetings

Deliverable (number)

Deliverable name WP

number Lead participant Type Dissemination level Delivery date

Kick-off Meeting (KOM): Grant Agreement

Analysis Review (AR)

D1.1 Project Plan 1 GMV R PU M1

D6.19 Background Intellectual Property

6 GMV R CO M1

D2.1 End-User Use Cases 2 FORESNA R PU M3

D6.1 Outreach and Dissemination Plan (v1)

6 EFI R PU M3

D6.4 Communication Materials (v1) 6 EFI DEC PU M3

D1.11 Data Management Plan (v1) 1 GMV R PU M4

D6.10 Stakeholders Workshop-1 Report

6 GMV R PU M4

Early Service Readiness (S1)


D2.2 Service Requirements and Validation of Use Cases

2 GMV R CO M7

D2.3 Architectural Design 2 GMV R CO M7

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

59 of 67



Deliverable name WP


D3.1 Integration and Validation Plan 3 GMV R PU M7

D1.2 DWH use for 2018 1 GMV R CO M9

D1.3 DWH request for 2019 1 GMV R CO M9

D1.7 Interim Progress Report-1 1 GMV R PU M10

D4.1 Service Getting Started Guide 4 GMV R PU M11


D3.2 Remote Sensing Algorithms and Models Trade-off

3 CFRI R PU M12

D3.3 Integration and Validation Report (v1)

3 GMV R CO M12


6 EFI R PU M12


Mid Term Review (MTR)


6 GMV R PU M15

D4.2 End-User Trials Assessment Report (v1)

4 RAIZ R PU M17

D6.14 Compilation of Publications Abstracts (v1)

6 CFRI DEC PU M17

D1.8 Progress Report-1 1 GMV R PU M18

Enhanced Service Readiness (S2)


D6.16 Business and Exploitation Plan (v1)

6 GMV R CO M18

D5.1 Product Roadmap (v1) 5 CFRI R CO M20


D1.5 DWH request for 2020 1 GMV R CO M21

Advanced Service Readiness (S3)



3 GMV R CO M24


6 EFI R PU M24


4 RAIZ R PU M26


6 GMV R CO M27

D1.9 Interim Progress Report-2 1 GMV R PU M28


6 GMV R PU M28


Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

60 of 67



Deliverable name WP



3 GMV R CO M30


Final Review (FR)


4 RAIZ R PU M34

D5.2 Product Roadmap (v2) 5 CFRI R CO M35

D6.15 Compilation of Publications Abstracts (v2)

6 CFRI DEC PU M35


6 GMV R CO M35

D6.20 Foreground Intellectual Property

6 GMV R CO M35

D1.10 Progress Report-2 1 GMV R PU M36


D5.3 Needs under global change and opportunities with new EO sensors for SFM

5 EFI R PU M36



6 GMV R PU M36

7.1.6. WORKPACKAGE/TASKS INTERNAL MEETINGS

The WP and Tasks Internal meetings are typically maintained every two weeks. WP leaders are requested to circulate and upload the MoM and progress actions to be taken onto the communication tool REDMINE.

Project Internal Meetings agenda mainly include the Project State, the Progress of Activities under development, Actions Status, Problems detected during the period and their associated mitigation Actions.

7.1.7. INTERNAL MEETINGS AND MINUTES

Internally to each WP and Task activity, the Project Manager shall schedule a set of regular meetings (usually twice per month) with the whole project team to make a close monitoring of the project progress as well as individual meetings with any project team member as needed. Such internal reviews will take place in order to:

Review general system status.

Review development progress and configuration.

Summarise key points and provide actions to solve them (if applicable).

Current actions status summary.

Presentation of the different work performed by each member and review of next planned activities.

The frequency of these reviews could be increased depending on the criticality of the project phase and the status of the project. The same practice is requested to subcontractors.

7.1.8. ACTION ITEMS CONTROL

The Project Manager for each WP shall be responsible for the follow-up of the action items recorded at the progress and review meetings. Although the implementation of the action items and the resolution of the technical issues are under the direct responsibility of the agreed responsible, the project manager shall be responsible for following up the status of any

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

61 of 67


open Action Item. Should an Action Item or technical issue remains open after the expected due date, the Project Manager shall recall such event to the responsible.

Concerning the rules for the Actions assignment and management, the guidelines listed below are proposed, as they have been previously adopted by GMV in projects of similar criticality demonstrating the required efficiency:

The Actions are originated during meetings. Only a participant in a meeting may be nominated as responsible

The Actions shall be mutually agreed between the Originator and the Responsible of the Action

The Actions shall be recorded in the Minutes of the Meeting – MoM. The Action Items List shall be prepared at the end of the Minutes of Meeting - MoM, compiling all the Actions Issues raised during the Meeting together with those risen in previous meetings

The Actions raised placed by each company in the Minutes of Meeting - MoM, shall be accepted for both companies only at the signature of the document by the corresponding company representatives.

On the other hand, for the Closure of an Action:

The closure of an Action will depend on the answer provided by the Action Responsible. The provided answer shall be evaluated in order to ensure its adequacy for closing out the Action Item. When an action is answered, the status shall be moved from Open to Responded.

The final decision about the closure of one Action shall be taken during meetings in which the Actions Status will be reviewed

The closing of an Action shall be mutually agreed between the Originator and the Responsible. The status shall be moved in this case from Responded to Closed.

7.1.9. ACTION ITEM STATUS LIST

The Project Manager shall be responsible for the follow-up of the action items recorded at progress and review meetings, teleconferences, or any other discussion.

Although the implementation of the Action Items and the resolution of the Technical Issues are under the direct responsibility of the agreed actionee, the Project Manager shall be responsible for following-up the status of any open Action Item. In case an Action Item remains open after the expected due date, the Project Manager shall recall such event to the actionee.

The information about action items will include at least the following:

Action Item identifier

A brief description

Initiation date

Reference to the minutes of meeting at which the action item was initiated

Due date

The actionee (company + person’s name)

The initiator (company + person’s name)

Status (“O” = Open, “R” = Responded, “C” = Closed)

Closing reference

Closing date

Critical Item Flag (Y/N)

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

62 of 67


8. RISK MANAGEMENT

Risk management process is actively executed by Project Coordinator in collaboration with inputs and feeding from all partners and every project area along the whole MySustainableForest project duration.

Project risks status is reported regularly within project management reporting. The results of risk assessment and reduction and the residual risks are communicated to the project team for information and follow-up in the Project Board. Risk management assists managers, experts and engineers by including risk aspects in management and engineering practices and judgements throughout the project life cycle. The entire spectrum of risks will be assessed. Undesired events are assessed for their severity and likelihood of occurrence.

The assessments of the alternatives for reducing the risks are iterated, and the resulting measurements of performance and risk trend are used to optimize the tradable resources. The implementation of the risk management process consists of a number of continuous “risk management cycles” over the project duration. Within the risk management process, available risk information is produced and structured, facilitating risk communication and management decision making. Risks are scored according to the index derived from the combination of its likelihood and severity:

Table 8-1. Risk Index Scheme

Risk Index

Severity

low

medium high

1 2 3 4 5

Low Moderate Significant Damaging Catastrophic

Like

liho

od

high 5 Very likely Unacceptable

4 Likely

medium 3 Possible Severe

low 2 Unlikely

1 Remote Controlled

According to this scheme, the obtained risk index falls under three possible risk categories (Unacceptable, Severe, Controlled), which give the qualitative results of the risk. Risks are scored according to their risk index and commensurate actions are defined to handle them in an effective manner up until risk is considered acceptable and not further action is required:

Table 8-2. Risk acceptance and action criteria

Risk Index Reduction Action(s) Required

Meaning

Unacceptable YES Most concerning Controls are insufficient or ineffective Unrecoverable damage to reputation, finances or business continuity Action required immediately

Severe YES Controls in place but may be ineffective Mitigation / contingency plans should overcome worst results Some action required immediately / further action at a later date Status of risk should be managed continuously

Controlled NO Comfortable with the risk Controls are sufficient and already in place Consequences can be managed or are relatively unimportant Status of risk should be reviewed periodically

Project risks will be scored including a colour code (red, orange and green) according to their index (function of its severity and probability).

Actions effectiveness will be monitored on a monthly basis at Project Board and consequently risks are re-assessed, new ones might be opened, new actions might be launched up until their full mitigation or associated risk index is decreased up until acceptance and associated actions closure in accordance with the established procedure.

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

63 of 67


Table 8-3. Critical Risks for Implementation

Risk Id. and Description WP Impact* Likelihood 1..5 Severity 1..5 Index 0..25

R-01. Proposed technological innovation not matching the End-Users demands or expectations

WP2, WP4 S, P 1 4 4

Proposed Risk Mitigation Details (Actionee, Action):

GMV to monitor monthly the service performance from early stages of the project, to manage End-User expectations proactively, to promote customers loyalty, to assess service value offer regarding End-Users requirements and to observe market evolution and technological state-of-the-art in a continuous manner including the project stakeholders´ workshops.

R-02. Performance results from validation results does not allows operational savings that justify service fee

WP3, WP4 C, P 2 5 10


GMV to urgently review the business plan including costs structures for optimization and re-analyse the technological trade-offs looking for performance improvements while tapping the synergies and potential of consortium partners.

R-03. Market hypothesis for market up-take or business parameters not confirmed

WP6 C, S 2 5 10


GMV to urgently to review the marketing strategy including the parameters of the cooperation model with partners, the business plan including commercial investments on market development, to conduct further stakeholders survey to focus better the service value on the market and to optimize the operational costs including data from customs and change rates.

R-04. Market entry takes longer than expected

WP1, WP6 C, S 1 3 3


GMV to organize the planned workshops carefully to build the needed credibility, engagement and trust among stakeholders. Partners End-Users will play the role of ambassadors in their forestry local, regional and national communities.

R-05. Market structure change due to mergers and/or acquisitions provoking losing or delaying of commercial opportunities

WP6 C, S 3 4 12


GMV to re-assess the market competitive forces and to review completely the business plan in order to adequate accordingly the associated strategy including the needed strategic alliances in the different regions of the world, and to develop further the cooperation arrangements with current stakeholders.

R-06. Competitors surpass eoforest performance

WP4, WP5 C, P 2 4 8


eoforest technology patent process is planned. GMV leads and keeps the coordinated R&D investment with consortium partners according to market demands and paying attention to the competitors offering. Continuous market surveillance is ongoing.

R-07. Defaulting partner Any C, S 2 2 4


GMV to monitor quarterly the financial health of their partners, support them to use good financial practices, help them to find appropriate financial support and ultimately decide about whether acquire the potential defaulting partner specific knowledge or otherwise to replace it by an alternative partner. Most risky partners are SMEs and their financial self-assessment provides healthy indicators (refer to ch.4).

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

64 of 67


Actions effectiveness will be monitored on a monthly basis at Project Board and consequently risks are re-assessed, new ones might be opened, new actions might be launched up until their full mitigation or associated risk index is decreased up until acceptance and associated actions closure in accordance with the established procedure.

Table 8-4. Summary of Project Risks

Risk Index

Severity

1 2 3 4 5

Low Moderate Significant Damaging Catastrophic

Like

liho

od

5 Very likely

4 Likely

3 Possible

2 Unlikely R-07 R-05 R-02, R-04

1 Remote R-06 R-04 R-01 R-03

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

65 of 67


9. QUALITY ASSURANCE

9.1. ORGANIZATION

Mª Inocencia García is assigned to the project as Quality Assurance (QA) Manager. She is absolutely independent from the implementation team. She reports directly to the Head of the GMV´s Quality Department (that it is independent of the operational direction in charge of the Project), having the authority, responsibility and necessary independence to propose, maintain and apply this Quality Assurance Programme. Moreover she reports to the Project Manager on QA activities.

Every change affecting the QA organization of the project will be notified to the customer prior to implementation.

9.2. LIFE CYCLE AND REVIEWS

Reviews serve to provide a qualitative assessment of product correctness. The term Review is understood to be synonym with contractual, project or formal review.

Formal reviews (or Project Reviews) will be joint meetings that include the Customer and GMV. QA activities for meeting preparation include planning, review agenda preparation, data package revision, and approval of review final disposition (accepted, provisionally accepted with pending actions, or rejected).

The QA Manager may participate in formal reviews to verify that appropriate actions have been implemented to satisfy all quality issues

and concerns. GMV shall maintain records of all review meetings.

To assist with eliminating the cause of discrepancies or non-conformances, Action Items can be generated with the minutes of the review meeting. Corrective actions shall be performed and depending on the magnitude of these corrective actions, the work scheduled for the next phase, following the formal review, can be allowed to start in parallel or postponed until after the corrective actions are implemented.

9.3. GMV INTERNAL PROCEDURES

The following table contains the list of GMV internal procedures that applies to the project with the modifications described in this document. They are available at GMV premises for checking and inspection by customer.

Table 9-1. GMV Internal Procedures applicable to the project.

Reference Title Code Version

[GM.1] Project Quality Assurance Procedure GMV-SGC-PRO-020 19/11/2015

[GM.2] Proposal Management and Contract Review Procedure

GMV-SGC-PRO-052 07/12/2015

[GM.3] Project Management Procedure GMV-SGC-PRO-005 02/02/2017

[GM.4] Verification and Validation Procedure GMV-SGC-PRO-053 03/02/2017

[GM.5] Configuration Management Procedure GMV-SGC-PRO-022 23/08/2016

[GM.6] Purchasing Procedure GMV-SGC-PRO-050 19/11/2015

[GM.7] Problem Management Procedure GMV-SGC-PRO-025 19/11/2015

[GM.8] Requirements Specification Procedure GMV-SGC-PRO-055 24/08/2016

[GM.9] Design and Production Procedure GMV-SGC-PRO-056 19/11/2015

[GM.10] Subcontractors Management Procedure GMV-SGC-PRO-011 19/11/2015

9.4. INSPECTIONS AND AUDITS

9.4.1. INSPECTIONS

The Customer may conduct inspections at GMV. Any such inspections will not, in any way, replace GMV’s inspections, or relieve GMV of the responsibility for ensuring the quality of the deliverable items.

Additionally, internal verification activities shall take place as needed (e.g. internal reviews, verification of COTS on reception, etc.).

Code:

Date:

Version:

Page:

D01 D1.1

30/11/2017

v1

66 of 67


All facilities and documentation used by GMV for the program shall be open to inspection and evaluation by the Customer and their consultants subject to GMV’s confidentiality restrictions at all reasonable times.

9.4.2. AUDITS

GMV shall perform internal audits at established regular intervals to ensure appropriate implementation of the requirements of the Product Assurance Program. Results of such audits shall be documented. Action items resulting from the audit shall be tracked until issues are satisfactorily resolved.

If applicable, GMV shall perform audits of any subcontractors and/or suppliers it uses to ensure that the required quality standards and contractual requirements are appropriately implemented.

9.5. RISK MANAGEMENT

An initial Risk identification is performed during proposal preparation and updated throughout the project. In identifying and classifying a risk, consideration given to the following factors:

Previous experience of project staff in the development of similar projects,

Maturity of the technologies to be used in the project

Typical deviations detected in terms of costs, schedule and execution in similar projects

The Project Manager is responsible for the risk management process. The QA Manager is involved in the risk management process when new risks are identified. The QA Manager verifies that the risk management process is performed as specified.

9.6. STANDARDS, PRACTICES AND CONVENTIONS

9.6.1. DOCUMENTATION STANDARDS

All documents produced by GMV shall use GMV’s templates. Documents shall be reviewed internally based on checklists. If necessary, GMV’s templates may be tailored to follow the customer’s document template. GMV’s procedures explain how to automatically generate document templates, how to proceed with internal reviews of the documents, and how to publish a document.

The Project Manager (PM) will designate the review team for each document published. The review team is comprise of, at least, the PM and corresponding QA Manager. The QA Manager review is based on document samples and limited to consistency with document inputs, adhesion to applicable standards and document completeness according to document objectives.

Corrections and updates to documentation will proceed as follows: The author will receive and compile all the comments from the review team and incorporate the corrections. In case of conflicts among comments or between the reviewer and the author, both the corresponding QA manager and the Project Manager will be informed to take an action and resolve the issue. When corrections have been incorporated, the document shall be approved by the corresponding QA Manager and authorized by the Project Manager before publishing. Any change to a document shall require the approval of the corresponding approval authority.

9.7. PROBLEM REPORTS AND CHANGE PROCESS

The objective of tracking and corrective action is to record process non-compliance with expected plans and standards, to record deficiencies of outputs.

According to the internal procedures the following types of discrepancies may be used:

Review Item Discrepancies (RIDs), to document issues on a contractual document

Non Conformance Reports (NCRs), related to issues in processes and usually identified during an audit.

Request for Deviation or Waiver, to document a formal request to deviate from a requirement or to obtain a waiver of a requirement.

This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 776045

www.mysustainableforest.com

END OF DOCUMENT

D1.1 Project Management Plan...Task T1.1 Project Control, Quality Assurance & Configuration...

Documents

Transcript of D1.1 Project Management Plan...Task T1.1 Project Control, Quality Assurance & Configuration...