À o í X í W } i D v P u v W o v - ict-terranova.eu · À o í X í W } i D v P u v W o v - ict-terranova.eu ... ñ

D1.1 – Project Management Plan

TERRANOVA Project

This project has received funding from Horizon 2020, European Union’s Framework Programme for R

Deliverable D1.1Project

Work

TERRANOVA Project

Grant Agreement No. 761794

Call: H2020-ICT-2016-2

Topic: ICT-09-2017 - Networking research beyond 5G

Start date of the project: 1 July 2017

Duration of the project: 30 months

Project Management Plan

This project has received funding from Horizon 2020, European Union’s Framework Programme for Research and Innovation, under grant agreement

No. 761794

Deliverable D1.1 Project Management Plan

Work Package 1 - Project Management

Networking research beyond 5G

July 2017

months

Page 1 of 51

This project has received funding from Horizon 2020, European Union’s nnovation, under grant agreement


TERRANOVA Project Page 2 of 51

Disclaimer This document contains material, which is the copyright of certain TERRANOVA contractors, and may not be reproduced or copied without permission. All TERRANOVA consortium partners have agreed to the full publication of this document. The commercial use of any information contained in this document may require a license from the proprietor of that information. The reproduction of this document or of parts of it requires an agreement with the proprietor of that information. The document must be referenced if used in a publication.

The TERRANOVA consortium consists of the following partners.

No. Name Short Name Country 1

(Coordinator) University of Piraeus Research Center UPRC Greece

2 Fraunhofer Gesellschaft (FhG-HHI & FhG-IAF) FhG Germany 3 Intracom Telecom ICOM Greece 4 University of Oulu UOULU Finland 5 JCP-Connect JCP-C France 6 Altice Labs ALB Portugal 7 PICAdvanced PIC Portugal



Document Information

Project short name and number TERRANOVA (653355) Work package WP1 Number D1.1 Title Project Management Plan Version v1.0 Responsible unit UPRC Involved units UPRC, JCP-C Type1 R Dissemination level2 PU Contractual date of delivery 31.07.2017 Last update 31.07.2017

1 Types. R: Document, report (excluding the periodic and final reports); DEM: Demonstrator, pilot, prototype, plan designs; DEC: Websites, patents filing, press & media actions, videos, etc.; OTHER: Software, technical diagram, etc. 2 Dissemination levels. PU: Public, fully open, e.g. web; CO: Confidential, restricted under conditions set out in Model Grant Agreement; CI: Classified, information as referred to in Commission Decision 2001/844/EC.



Document History

Version Date Status Authors, Reviewers Description v0.1 10.07.2017 Draft Kristaps Dobrajs (JCP-C) Initial version, definition of a

structure v0.2 11.07.2017 Draft Kristaps Dobrajs (JCP-C) Sections 2 -7 created v0.3 18.07.2017 Draft Angeliki Alexiou (UPRC) Editing of Sections 1-8 and

Annexes v0.4 24.07.2017 Draft Alexandros-Apostolos A.

Boulogeorgos (UPRC) Editing of Sections 1-8 and Annexes

v0.5 25.07.2017 Draft Francisco Rodrigues (PICadvanced)

PICadvanced’s contribution

v0.6 26.07.2017 Draft Dimitrios Kritharidis (ICOM)

ICOM’s contribution

v0.7 28.07.2017 Draft Kris Dobrajs (JCP-C) Editing of Sections 1-8 and Annexes

v0.8 28.07.2017 Draft Angeliki Alexiou (UPRC) Editing of Sections 1-8 and Annexes

v0.9 29.07.2017 Draft Angeliki Alexiou (UPRC) Editing of Sections 1-8 and Annexes

v1.0 31.07.2017 Final Angeliki Alexiou (UPRC) Editing of Sections 1-8 and Annexes



Acronyms and Abbreviations

Acronym/Abbreviation Description TERRANOVA Terabit/s Wireless Connectivity by TeraHertz innovative

technologies to deliver Optical Network Quality of Experience in Systems beyond 5G

CA Consortium Agreement GA Grant Agreement EC European Commission IP Intellectual Property PMC Project Management Committee WP Work Package WPL Work Package Leader



Contents

1. INTRODUCTION ..................................................................................................................... 10

2. PROJECT MANAGEMENT ....................................................................................................... 11

2.1 Project governance ........................................................................................................ 11

2.1.1 Project management structure ............................................................................. 11

2.1.2 Operational bodies ................................................................................................ 11

2.1.3 Main management roles ....................................................................................... 12

2.1.4 Advisory Board ...................................................................................................... 13

2.1.5 Contact details of all project partners ................................................................... 13

2.1.6 Conflict resolution ................................................................................................. 14

3. Information and documentation management .................................................................... 15

3.1 Document repository .................................................................................................... 15

3.2 Project Website ............................................................................................................. 15

3.3 Mailing lists .................................................................................................................... 15

3.4 Templates ...................................................................................................................... 16

3.5 Document and file numbering and versioning .............................................................. 16

3.5.1 Naming .................................................................................................................. 16

3.5.2 Versioning .............................................................................................................. 16

4. Workflow procedures ............................................................................................................ 17

4.1 Creation of Detailed Task Workplan (DTW) .................................................................. 17

4.2 Producing a deliverable ................................................................................................. 17

4.2.1 Initial table of contents ......................................................................................... 17

4.2.2 Timeline for deliverable production, deliverable review, approval and submission 17

4.3 Reporting an issue, a risk or a problem ......................................................................... 18

5. Meetings ................................................................................................................................ 18

5.1 Physical meetings .......................................................................................................... 19

5.1.1 Internal meetings .................................................................................................. 19

5.1.2 External meetings .................................................................................................. 19

5.2 Phone conferences (internal) ........................................................................................ 19

6. REPORTING ............................................................................................................................ 19



6.1 Internal reporting .......................................................................................................... 19

6.2 External reporting .......................................................................................................... 20

6.2.1 Periodic reporting .................................................................................................. 20

6.2.2 Final report ............................................................................................................ 20

7. IPR protection ........................................................................................................................ 21

7.1 Main IPR protection principles ...................................................................................... 21

7.1.1 Access Rights to Background and Foreground IP .................................................. 21

7.1.2 IP Ownership ......................................................................................................... 21

7.2 Dissemination of project results and security clearance .............................................. 21

8. REFERENCES .......................................................................................................................... 22

ANNEX I – General Assembly Members ........................................................................................ 23

ANNEX II – PROJECT Management committee MEMBERS ............................................................ 23

ANNEX III – WP LEADERS ............................................................................................................... 23

ANNEX V – TERRANOVA technical contacts .................................................................................. 24

ANNEX VI – PRESENTATION AND DELIVERABLE TEMPLATES ......................................................... 25

ANNEX VII – DetaIled Task Workplan (DTW) template ................................................................. 37

1. Introduction ........................................................................................................................... 39

2. Partners MM allocation ......................................................................................................... 40

3. Task No: objectives and description ...................................................................................... 41

4. Identification of sub-tasks ..................................................................................................... 41

5. Risks and/or issues ................................................................................................................ 41

6. Request for contribution ....................................................................................................... 41

7. Contribution to deliverable(s) ............................................................................................... 41

8. Deliverable X.Y Table of Contents ......................................................................................... 42

ANNEX VIII – QUARTERLY REPORT template ................................................................................. 43

1. Summary of Main Achievements and Key Outcomes ........................................................... 49

1.1 Technical Progress and Achievements .......................................................................... 49

1.1.1 WPx ........................................................................................................................ 49

1.2 Project Status ................................................................................................................ 49

1.2.1 WP1 Project Management and Coordination ....................................................... 49

Task 1.1: Project Organisation and Management [M1 – M30] ............................................. 49

Task 1.2: Project Technical and Innovation Management [M1 – M30] ................................ 49

Task 1.3: Project Office and Quality management [M1 – M30] ............................................ 49



1.3 Deliverable and Milestone Status ................................................................................. 50

1.3.1 Deliverables ........................................................................................................... 50

1.3.2 Milestones ............................................................................................................. 50

1.4 Project meetings, dates and venues ............................................................................. 51



Executive Summary

This deliverable presents the core management hand book for the TERRANOVA project. The project management consists of organisational, administrative, legal and financial tasks, both within the consortium and between the EC and the consortium members. This work is substantially supported by the use of the TERRANOVA website, mailing lists as well as by using a repository for creating and sharing documents, providing relevant templates and distributing guidelines and central project information. This deliverable will be focusing on describing internal work processes, summarizing reporting strategies and requirements as well as outlining organisational structures related to the project governance and technical coordination.

The content of this deliverable may be regularly updated when required.

Project administration for TERRANOVA covers the following tasks:

Management of the consortium, Communication within the consortium as well as with the Commission, Provision of guidelines on quality assurance and report writing, including the provision

of various templates, Organization of regular conference calls for all partners and provision of minutes, etc., Monitoring of resource expenditure and Submission of reports and deliverables

Legal and financial tasks in the TERRANOVA project cover the following:

Management of contractual issues and timely distribution of corresponding documents and relevant information to partners (e.g. regarding Grant Agreement and Consortium Agreement),

Communication between consortium partners and the EC on project- and funding-related issues and

Management of budget and distribution of payments to partners, etc.

In order to address the above aspects this deliverable is organised around 6 main project management functions and the associated procedures: Project management structure and roles, Information and Documentation Management, Workflow procedures, Meetings, Reporting, and IPR Protection.



1. INTRODUCTION The present document is intended to serve as a manual for project partners in all everyday routines and activities related management of TERRANOVA and also to administrative and financial matters of the project. The purpose of this document is to be a central place for the consortium Partners to get the information on project operational organization and procedures, information and document management, conflict resolutions, financial matters, reporting, etc. For this reason, this document is meant to be living document, updated when any related rule, procedure, etc. has been changed.

The organization of this document is as follows. In Section 2, the project management structure, the main management roles, and the conflict resolution strategy are demonstrated. In Section 3, the information and documentation management tools are defined. In more detail, in Section 3.1, the documentation repository is presented, while in Section 3.2, the mailing lists are given. Section 3.3 focuses on illustrating the project presentation and deliverable templates, whereas, in Section 3.4, document naming and versioning are demonstrated. Specific workflow procedures, such as the creation of detailed task workplans, the deliverables producing process, issues, risks and/or problems reporting procedures are defined. In Section 5, the types and frequency of meetings are given, while, in Section 6, internal and external reporting procedures and documents are described. Finally, Section 7 presents the main principles of IPR protection, as well as the dissemination of project results and security clearance plan.


TERRANOVA Project

2. PROJECT MANAGEMENT2.1 Project governance

In this section, the project governance of the TERRANOVA project is presented. In particular, in subsection 2.1.1, the project management structure is presented, while in subsection 2.1.2, the operation bodies and their responsibilities are described. Addimain management roles are defined, whereas, in subsection 2.1.5, contact details of all the project partners are provided. Finally, the conflict resolution strategy that will be followed in the project is presented

2.1.1 Project management structure

In order to achieve its objectives, structure. The general overview of the project governance is represented in Figure 1. detail, the work is mainly performed by

General Assembly; Project Management Commit Work Package Groups, Project Office.

The project management is further complemented by an External Advisory Board, described in subsection 2.1.4.

Figure

2.1.2 Operational bodies

Clear hierarchy is introduced for fulfilling the project goals: The General Assembly

project budget and general annual objectives; it is chaired by the Project Coordinator.All GA members and their contact details are mentioned in Annex I.


PROJECT MANAGEMENT

In this section, the project governance of the TERRANOVA project is presented. In particular, in subsection 2.1.1, the project management structure is presented, while in subsection 2.1.2, the operation bodies and their responsibilities are described. Additionally, in subsection 2.1.3, the main management roles are defined, in subsection 2.1.4 the Advisory Board is presented,

, contact details of all the project partners are provided. Finally, the t will be followed in the project is presented in subsection 2.1.6

Project management structure

In order to achieve its objectives, the TERRANOVA project has a multi-level management The general overview of the project governance is represented in Figure 1.

performed by four (4) bodies, namely:

Project Management Committee; and

ent is further complemented by an External Advisory Board, described in

Figure 1 – TERRANOVA project management structure

Operational bodies

Clear hierarchy is introduced for fulfilling the project goals: (GA), as the ultimate decision body of the project,

project budget and general annual objectives; it is chaired by the Project Coordinator.their contact details are mentioned in Annex I.

Page 11 of 51

In this section, the project governance of the TERRANOVA project is presented. In particular, in subsection 2.1.1, the project management structure is presented, while in subsection 2.1.2, the

tionally, in subsection 2.1.3, the in subsection 2.1.4 the Advisory Board is presented,

, contact details of all the project partners are provided. Finally, the in subsection 2.1.6.

level management The general overview of the project governance is represented in Figure 1. In more

ent is further complemented by an External Advisory Board, described in

ultimate decision body of the project, approves the project budget and general annual objectives; it is chaired by the Project Coordinator.



The Project Management Committee is composed of the Coordinator, the Technical Project Manager, the seven (WP1-WP7) work package Leaders (WPLs). In its tasks, it is supported by the Project Office. The Project Coordinator chairs the Project Management Committee. (see section 2.1.3)

The work package (WP) technical groups ensure day-to-day WP work; each group is chaired by the respective WP Leader. The list of WP leaders and their contact details can be found in Annex III.

2.1.3 Main management roles

Particular individuals are responsible for administrative, financial, technical, business-related, ethical, IPR, quality and risk management aspects. Table 2.1.3.1 summarizes the main management roles and the responsible individual. The sub-sections below indicate the individuals responsible for these aspects. Consortium Partners are expected to contact the responsible individual in case of issues in the mentioned aspects.

Table 2.1.3.1: Main management roles and responsible individuals Management role Responsible person

Project Coordinator Prof. Angeliki Alexiou (UPRC) Project Technical Manager Dr. Colja Schubert (FhG) Project Office Mr. Kristaps Dobrajs (JCP-C) Innovation Manager Dr. Thomas Merkle (FhG) Quality and Risk Manager Dr. Jean-Charles Point (JCP-C)

2.1.3.1 Project Coordinator

The Project Coordinator is Prof. Angeliki Alexiou. Her major tasks are: Financial coordination of the project and distribution of EC’s payments to partners; Chairing the GA; Chairing the PMC; Confirmation and approval of periodic reports for the European Commission (EC); Representative of consortium towards the EC and all external events.

All questions of administrative, organizational or financial matter should be addressed to the Project Coordinator and the Project Office (see 2.1.3.3).

2.1.3.2 Project Technical Manager

Project Technical Manager is Dr. Colja Schubert. The Project Technical Manager has the following responsibilities:

Chairing the External Advisory Board; Technical relationship and coordination with other relevant R&D projects; Supervision of the overall technical progress of the project; Consolidation of the technical reports; Follow-up and coordination of all technical work-packages.

The Project Technical Manager should be normally involved in ongoing technical discussions and should be informed on deviations from plan or any project technical risks.



2.1.3.3 Project Office

The Project Office acts as daily project management instrument and support to the Project Coordinator, in administrative, reporting, organizational and managerial activities (excl. financial). The Project Office representative is Jean-Charles Point (JCP-C).

2.1.3.4 Innovation Manager

TERRANOVA Innovation Manager is Dr. Thomas Merkle (FhG). The Innovation Manager assesses all IPR relevant information that is brought into the project or is developed within the project. The Innovation Manager gives recommendations to the GA on the handling of the assessed IPR issues. To fulfil his tasks, the Innovation Manager may request the assistance of experts with IPR background recruited from the consortium partners.

2.1.3.5 Quality and Risk Manager

Quality and Risk Manager is Jean-Charles Point (JCP-C). These two roles are extensively described in Deliverable D1.2, where the main principles of quality and risk management are described.

2.1.4 Advisory Board

In addition to the project partners and the various management responsibilities explained in the previous sections, the TERRANOVA project management is complemented by an External Advisory Board. The Advisory Board is chaired by the Project Technical Manager and consists of another (minimum) 3 influential experts from industry, with proven track record in transferring advanced technologies from research labs to the market. The Advisory Board members supervise the technical directions and provide feedback on the relevance and focus of the work as well as on ways to maximise the potential impact. The Advisory Board consists of

Dr. Pekka Kyosti, Keysight Technologies, Dr Theodore Sizer, Bell Labs, Nokia and Dr. Shilpa Talwar, Intel Labs.

The composition of the Advisory Board might be changed by the decision of Project Management Committee – in this case, all partners can propose substitute/additional candidates.

2.1.5 Contact details of all project partners

All contact details of Partners active in the daily implementation of the project are given in ANNEX IV (administrative contacts) and ANNEX V (technical contacts).


TERRANOVA Project

2.1.6 Conflict resolution

As a general rule, decision making processes have been thought to minimize the possible inception of conflicts and, in case of any of themTherefore, as demonstrated in Figure 2, 2.1.2 should be followed for resolutions of potential problems: When a conflict occurs in a WP technical group, consensus

If the problem cannot be solvedproblem as well as possible solutions and submits it to Committee (PMC).

If consensus cannot be reached within the PMC, the Technical Project Manager escalates it to GA and a vote occurs, requiring a simple majority.organized if necessary on this purpose

Figure


Conflict resolution

As a general rule, decision making processes have been thought to minimize the possible in case of any of them, they will be solved, first of all, amicably.

s demonstrated in Figure 2, the hierarchy that has been described inshould be followed for resolutions of potential problems:

When a conflict occurs in a WP technical group, consensus is sought to solve the problem. If the problem cannot be solved, the WPL prepares a report with the description of the problem as well as possible solutions and submits it to the Project Management

If consensus cannot be reached within the PMC, the Technical Project Manager escalates it e occurs, requiring a simple majority. Extraordinary GA meetings can be

if necessary on this purpose.

Figure 2 – Conflict resolution principle in TERRANOVA

Page 14 of 51

As a general rule, decision making processes have been thought to minimize the possible they will be solved, first of all, amicably.

described in subsection

to solve the problem. the WPL prepares a report with the description of the

Project Management

If consensus cannot be reached within the PMC, the Technical Project Manager escalates it Extraordinary GA meetings can be


TERRANOVA Project

3. INFORMATION AND DOCU3.1 Document repository

At the time of writing this deliverable (July 2017), a fully secured document repository, solely dedicated to TERRANOVA, is being set up by the Partners. All necessary documentation is currently stored in the “Zoho Projects” cloud platform, untisolution is launched, to be described in detail in D1.2 Quality Assurance Manual (M06).

Figure

3.2 Project Website The TERRANOVA website is currently it will be maintained during the project time life and 2 years after

It will present the concepts, vision, objectives and expected outcomes as well as public documents, deriving from the project work; it will be regularly updated, offering links to other relevant sites and links to partnersthe project will establish presence in a number of welltwitter, Facebook).

All partners are asked to contribute content continuously throughout the project’s lifespan, and specifically, a call for content is launched every two months. The technical management of the website is under the responsibility of Partner with full involvement from all partners providing content.

3.3 Mailing lists Two mailing list are organized for handling administrative and technical questions arising in the project. Those mailing lists are:

Administrative mailing list: General mailing list: TERRANOVA WPs mailing lists:


INFORMATION AND DOCUMENTATION MANAGEMENTrepository

At the time of writing this deliverable (July 2017), a fully secured document repository, solely dedicated to TERRANOVA, is being set up by the Partners. All necessary documentation is currently stored in the “Zoho Projects” cloud platform, until the fully customized and functional solution is launched, to be described in detail in D1.2 Quality Assurance Manual (M06).

Figure 3 – Zoho Projects document repository

website is currently being designed and implemented [www.ict-it will be maintained during the project time life and 2 years after the end of the project

It will present the concepts, vision, objectives and expected outcomes as well as public from the project work; it will be regularly updated, offering links to other

relevant sites and links to partners’ websites. Web 2.0 will be widely used for dissemination and the project will establish presence in a number of well-known social networking sites (LinkedIn,

All partners are asked to contribute content continuously throughout the project’s lifespan, and specifically, a call for content is launched every two months. The technical management of the

sibility of Partner 5 (JCP-Connect SAS) and is a collaborative process, with full involvement from all partners providing content.

Two mailing list are organized for handling administrative and technical questions arising in the e mailing lists are:

Administrative mailing list: [email protected]; [email protected];

Page 15 of 51

MENTATION MANAGEMENT

At the time of writing this deliverable (July 2017), a fully secured document repository, solely dedicated to TERRANOVA, is being set up by the Partners. All necessary documentation is

fully customized and functional solution is launched, to be described in detail in D1.2 Quality Assurance Manual (M06).

-terranova.eu]; the end of the project.

It will present the concepts, vision, objectives and expected outcomes as well as public from the project work; it will be regularly updated, offering links to other

websites. Web 2.0 will be widely used for dissemination and sites (LinkedIn,

All partners are asked to contribute content continuously throughout the project’s lifespan, and specifically, a call for content is launched every two months. The technical management of the

Connect SAS) and is a collaborative process,

Two mailing list are organized for handling administrative and technical questions arising in the



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

Subscribers belonging to each list can be found in Annex IV and Annex V.

3.4 Templates Templates for project presentation and project deliverables are given in ANNEX VI.

3.5 Document and file numbering and versioning Most documents in a collaborative project are written with contributions from several partners. In order to minimize the effort for handling such documents, it is important for all participants to follow agreed standards for formats and tools to be used in document editing and exchange.

3.5.1 Naming

Document naming principle is as follows: TERRANOVA_[document identity]_WPn_dd[month]yyyy_vx.y.ext

E.g.: TERRANOVA_D1.1_WP1_02September2015_v0.1.pdf TERRANOVA_D1.1_WP1_28September2015_v0.15.pdf TERRANOVA_D1.1_WP1_30September2015_v1.0.pdf

Or (when WPs name does not exist): TERRANOVA_prelim.system.reqs_WP3_02September2015_v0.1.pdf

3.5.2 Versioning

When a document is issued for the first time, it should be defined as a draft (version 0.x). Usually, the approval process requires that a document is circulated for comments among the interested partners. Upon receiving the comments by the specified deadline, the author will make the proper modifications; therefore, changing the version sub-number, without affecting the main number. Normally, the first official release of a document will be called V1.0 and this number will be assigned by the Quality Manager when he/she has approved the document. The main version number (the first figure before the “.”) is increased by one unit only if a different version of the document is delivered to the Commission, or if major modifications have significantly altered the contents of the document. The editor must not forget to update the version number in all its occurrences in the document (File Properties and cover pages). Clearly, every care should be taken to avoid distributing different documents with the same version number. To sum up, two types of versions will be created, namely

v0.x, 1.x, 2.x, etc., which will be the working version; and v1.0, 2.0, 3.0, which will be the released version (e.g. locked for internal use or for

submission to EC).



THE GOLDEN RULE TO RESPECT: NEVER DISTRIBUTE TWO DIFFERENT DOCUMENTS (EVEN ONLY SLIGHTLY DIFFERENT) WITH THE SAME FILE REFERENCE.

4. WORKFLOW PROCEDURES 4.1 Creation of Detailed Task Workplan (DTW)

Every starting task begins with producing a Detailed Task Workplan (DTW), which is an internal document that intends to decrease the risk of different understanding of the task by the involved partners. DTW template should contain at least the following chapters:

Partners MM allocation; Objectives and description of task; Identification of sub-tasks; Risks and/or issues; Requests for contribution; Contribution of this task to the deliverable(s) it feeds; Table of Contents (at least initial) of this deliverable.

The Task Leader is responsible for producing DTW and its distribution among the TERRANOVA consortium. The template of DTW can be found in Annex VII.

4.2 Producing a deliverable

4.2.1 Initial table of contents

It is important to define at least the initial table of contents for a deliverable as early as possible. Table of contents for the deliverable should be also included in the DTW described in Section 4.1.

4.2.2 Timeline for deliverable production, deliverable review, approval and submission

Step

When#

(time before the submission deadline)

Who What

#1 42 days

(6 weeks) Document Editor

Submits Table of Contents (ToC), sections contents in bullet form with brief explanation, and writing allocation (who is writing each section) for the deliverable (to WPL, PTM, PMC).



Detailed timeline of deliverable production, along with series of deadlines will be described in the section “Deliverables Review and Approval Procedure” of Deliverable D1.2.

4.3 Reporting an issue, a risk or a problem Once discovered an issue, a risk or a technical problem, every Partner should immediately inform the Project Coordinator, the Project Technical Manager and the Risk Manager (as described in Section 2.1.3) in written form. The report should contain at least following points:

Description of the problem; Description of the proposed solutions; Estimated impact:

o Impact on technical performance; o Impact on project schedule; o Impact on project budget; o Impact on work of other partners.

For all non-technical issues, the Project Coordinator and the Project Office shall be informed.

5. MEETINGS Two types of meetings will be conducted during the TERRANOVA project, namely physical (F2F) meetings and phone conferences.

#2 39 days WPL, PTM, PMC Provide comments/ feedback.

#3 21 days

(3 weeks) Document Editor

Submits final draft of the deliverable (to the Quality Manager and PMC).

#4 20 days Quality Manager Sends final draft of the deliverable to the Internal Reviewers.

#5 14 days

(2 weeks) Internal Reviewers Provide comments/ feedback.

#6 7 days

(1 week) Document Editor

Submits final version of the deliverable (to the Project Coordinator).

#7 1 day Project Coordinator Approves and uploads the deliverable to the EC services.



5.1 Physical meetings Both internal and external meetings will be held during the timeline of the project. For planning of travels and accommodation, the usual contractual conditions and principles of economy shall be applied.

5.1.1 Internal meetings

The partners agree to meet 2 to 3 days every 3-4 months in joint consortium meetings (plenary meetings) or special technical workshops (e.g., use cases, integration, test, or solving special issues), whereas more frequent meetings can be organized at the beginning of the project, when a degree of uncertainty in technical questions and end-users exists. P2P meetings between partners working on a particular topic are possible as well (the meeting logistics and outcomes will be communicated to the general mailing list).

During the plenary meetings, WP Technical Groups should also organize meetings. Moreover, during the plenary meeting, meetings of the various (management) bodies might take place.

5.1.2 External meetings

Several types of external meetings could be organized as well, e.g.: Project dissemination events; and Meeting with External Advisory Board.

Furthermore, Project periodic meetings shall be organized in the end of each (reporting) period and after the project end.

5.2 Phone conferences (internal) Phone conferences can be organized at any time. Partners shall send their requests for organization of phone conference to the Project Office.

GA meetings are usually organized via conference call. GA meetings shall be organized at least once per year, or more often, as required.

6. REPORTING 6.1 Internal reporting

It is of internal use and should help detect potential issues sufficiently early.

Every partner introduces, by the end of the quarter, the PM resources spent and a short description of the work accomplished, using the template distributed by the Project Office. It should describe the technical and management project work done and effective time spent on the project.

It also contains a short table, in which the partners should mention any potential risks that could come up during the project work. The table should be updated each time a new risk arises or an old risk has been resolved.

It is due at least 2 weeks after the end of each quarter.

A template for Quarterly Report is provided in Annex VIII.



6.2 External reporting

6.2.1 Periodic reporting

6.2.1.1 Technical reporting

The technical part of the periodic report shall be submitted after the end of each one of the 2 reporting periods (M1-M18 and M19-M30), within 60 days after the formal end of each period. The WPLs are responsible for producing periodic reports, with the contributions of the task leaders where necessary. The report is organized and compiled by the Project Office using the appropriate EC template; the coordinator shall edit, review, sign and submit the periodic report to the EC.

6.2.1.2 Financial reporting

Financial reporting is the sole responsibility of each Partner and shall be done during 60 days after the formal end of each reporting period. Financial reporting in the end of each reporting period shall be done in the Participant Portal3 of EC.

6.2.2 Final report

In addition to the periodic report, the consortium shall submit a final report to the Commission within 60 days after the end of the project. The final report shall comprise:

a final publishable summary report covering results, conclusions and socio-economic impact of the project;

a report covering the wider societal implications of the project, including gender equality actions, ethical issues, efforts to involve other actors and spread awareness as well as the plan for the use and dissemination of foreground.

3 http://ec.europa.eu/research/participants/portal/



7. IPR PROTECTION The Data Management Plan deliverable (D1.2), due M06, will incorporate all rules and guidelines concerning the management of IPR, both background and foreground. The main principles of IPR Protection are described in the following sections and should be established at the very beginning of the project.

7.1 Main IPR protection principles

7.1.1 Access Rights to Background and Foreground IP

In order to ensure smooth execution of the project, the project partners agree to grant royalty-free access to Background and Foreground IP for the execution of the project. Therefore, all project partners have determined in the CA any Background IP they are willing to submit to the project, before the project has started.

7.1.2 IP Ownership

Foreground IP shall be owned by the project partner carrying out the work leading to such IP. If any Foreground IP is created jointly by at least two project partners and it is not possible to distinguish between the contributions of each of the project partners, such work will be jointly owned by the contributing project partners. The same shall apply if, in the course of carrying out work in the project, an invention is made having two or more parties contributing to it, and it is not possible to separate the individual contributions. Any such joint inventions and all related patent applications and patents shall be jointly owned by the contributing parties. Further details concerning the exposure to jointly owned Foreground IP, joint inventions and joint patent applications are addressed in the CA.

7.2 Dissemination of project results and security clearance TERRANOVA consortium endeavours to offer open access to its scientific results reported in the publications.



8. REFERENCES [1] GRANT AGREEMENT — 761794 — TERRANOVA project H2020-ICT-2016-2017/H2020-ICT-2016-2

[2] TERRANOVA 761794 ANNEX 1 Description of Work, v0.9, May 2017

[3] TERRANOVA Consortium Agreement, version 0.6, 20-7-2017



ANNEX I – GENERAL ASSEMBLY MEMBERS No. Partner

Short Name General Assembly Member

1 UPRC Angeliki Alexiou 2 FhG Thomas Merkle 3 ICOM Dimitrios Kritharidis 4 UOULU Markku Juntti 5 JCP-C Jean-Charles Point 6 ALB José Salgado 7 PIC Francisco Rodrigues

ANNEX II – PROJECT MANAGEMENT COMMITTEE MEMBERS PMC role PMC member

Project Coordinator Angeliki Alexiou (UPRC) Technical Manager Colja Schubert

Innovation Manager Thomas Merkle (FhG) Quality and Risk Manager Jean-Charles Point (JPC-C)

WP2 Leader José Salgado (ALB) WP3 Leader Markku Juntti (UOULU) WP4 Leader Angeliki Alexiou (UPRC) WP5 Leader Thomas Merkle (FhG) WP6 Leader Colja Schubert (FhG) WP7 Leader Kristaps Dobrajs (JPC-C)

ANNEX III – WP LEADERS WP No. WP Leader Partner

Short Name 1 Angeliki Alexiou UPRC 2 José Salgado ALB 3 Markku Juntti UOULU 4 Angeliki Alexiou UPRC 5 Thomas Merkle FhG (IAF) 6 Colja Schubert FhG (HHI) 7 Kristaps Dobrajs JCP-C



ANNEX IV – TERRANOVA ADMINISTRATIVE CONTACTS

UPRC : Angeliki Alexiou [email protected]

FhG: Colja Schubert [email protected]

ICOM : Dimitrios Kritharidis [email protected]

UOULU : Markku Juntti [email protected]

JCP-C : Jean-Charles Point [email protected]

ALB : José Salgado [email protected]

PIC : Francisco Rodrigues [email protected]

ANNEX V – TERRANOVA TECHNICAL CONTACTS UPRC : Angeliki Alexiou [email protected]

FhG: Colja Schubert [email protected]

ICOM : Dimitrios Kritharidis [email protected]

UOULU : Markku Juntti [email protected]

JCP-C: Kristaps Dobrajs [email protected]

ALB : José Salgado [email protected]

PIC : Francisco Rodrigues [email protected]



ANNEX VI – PRESENTATION AND DELIVERABLE TEMPLATES

© The TERRANOVA consortium 2017-2019

Co-funded by the Horizon 2020 Framework Programme of the

European Union

Title LayoutSubtitle


Title and Content Layout with List• Add your first bullet point here

• Add your second bullet point here

• Add your third bullet point here


Title and Content Layout with Chart

0

1

2

3

4

5

6

Category 1 Category 2 Category 3 Category 4

Series 1

Series 2

Series 3




Two Content Layout with Table

• First bullet point here

• Second bullet point here

• Third bullet point here

Group 1 Group 2

Class 1 82 95

Class 2 76 88

Class 3 84 90


Two Content Layout with SmartArt

• First bullet point here

• Second bullet point here

• Third bullet point here

Group A

Task 1

Task 2

Task 3

Task 4


TERRANOVA Project


Deliverable D<Title of the deliverable>

Work Package

TERRANOVA Project


Topic ICT-09-2017 “Networking research beyond 5G”





No. 761794

Deliverable DX.Y

<Title of the deliverable> Work Package X: <Title of work package>

“Networking research beyond 5G”

1 July 2017

30 months

Page 27 of 51






Participant No Participant organisation name Participant short name Country

1 (Coordinator) University of Piraeus Research Center UPRC Greece

2 Fraunhofer Gesellschaft (FhG-HHI & FhG-IAF) FhG Germany

3 Intracom Telecom ICOM Greece

4 University of Oulu UOULU Finland

5 JCP-Connect JCP-C France

6 Altice Labs ALB Portugal

7 PICAdvanced PIC Portugal




Project short name and number TERRANOVA (761794) Work package WPX Number DX.Y Title <Title of the deliverable> Responsible beneficiary … Involved beneficiaries … Type4 … Dissemination level5 … Contractual date of delivery DD.MM.YYYY Last update v x.yz DD.MM.YYYY

4 4Types.4 4R:4 Document, report (excluding the periodic and final reports); 4DEM:4 Demonstrator, pilot, prototype, plan designs; 4DEC:4 Websites, patents filing,

press & media actions, videos, etc.; 4OTHER:4 Software, technical diagram, etc. 5 5Dissemination levels.5 5PU:5 Public, fully open, e.g. web; 5CO5:5 Confidential, restricted under conditions set out in Model Grant Agreement; 5CI:5 Classified,

information as referred to in Commission Decision 2001/844/EC.



Document History

Version Date Status Authors, Reviewers Description v 0.01 DD.MM.YYYY Template JCP-C Project deliverable template. v 0.02 DD.MM.YYYY Draft … Table of contents and document

structure. … … … … …

v 0.24 DD.MM.YYYY Draft … Internal review comments and feedback.

… … … … … v 1.00 DD.MM.YYYY Final … Final document for submission.

<Please remove the note below, in the final document>

Note: Versioning rules

We will be using 3 obligatory digits for deliverable versioning in the following format: “v X.YZ”. “X” indicates document release (i.e. submission to the EC) while “YZ” indicate document version within a certain release. All versions prior to the first release (submission) are indicated with X being 0.

For example, the initial version of a document (e.g. this template filled with the specific information of a specific deliverable) should be indicated as ‘v 0.01’. Later versions could be indicated, for example, as ‘v 0.05’, ‘v 0.19’, ‘v 0.47’, etc. up to ‘v 0.99’. First release (submission to the EC) of the document should be indicated as v 1.00. In case further versions of the document are needed then those could be indicated, for example, as ‘v 1.03’, ‘v 1.32’, ‘v 1.66’, etc. up to ‘v 1.99. Second release (submission to the EC) of the document should be indicated as v 2.00, and so on.








Contents

1 Heading 1 ............................................................................................................................... 32

1.1 Heading 2 ....................................................................................................................... 32

1.1.1 Heading 3 ............................................................................................................... 32



List of Figures

No table of figures entries found.



List of Tables

No table of figures entries found.



Executive Summary

<Executive Summary here>



Heading 1

Heading 2

Heading 3


TERRANOVA Project

ANNEX VII – DETAILED TASK

Task No

Detailed Task Workplan

‘TERRANOVA_ DTW_te


LED TASK WORKPLAN (DTW) TEMPLATE

Task No - Task name

Detailed Task Workplan (DTW)

_ DTW_template_WP1_18September2017_v0.1.doc

Version: 0.1

Last Update: DD.MM.YYYY

Distribution Level: Confidential

Page 37 of 51

ATE

_v0.1.docx’



Revision History

No. Version Edition Author(s) Date 1 0 1 Kristaps Dobrajs, JCP-C 11/07/2017

Comments: Initial release of the template

2 0 2 Comments:

3 0 3 Comments:

4 0 4 Comments:

5 0 5 Comments:

6 0 6 Comments:

7 0 7 Comments:

8 0 8 Comments:

9 0 9 Comments:

10 0 10 Comments:

11 0 11 Comments:

12 Comments:

13 Comments:

14 Comments:

15 Comments:

Table of Contents

1. Introduction ........................................................................................................................... 39

2. Partners MM allocation ......................................................................................................... 40

3. Task No: objectives and description ...................................................................................... 41

4. Identification of sub-tasks ..................................................................................................... 41

5. Risks and/or issues ................................................................................................................ 41

6. Request for contribution ....................................................................................................... 41

7. Contribution to deliverable(s) ............................................................................................... 41

8. Deliverable X.Y Table of Contents ......................................................................................... 42



1. INTRODUCTION The main goal of this detailed task workplan (DTW) is to serve as a central

document that defines the workload, responsibilities and targets of the TERRANOVA partners participating in Task no – Task name. The current version is a working document required to be reviewed by the corresponding partners as they are outlined in section 2.

Following its review and consultation by the corresponding partners, to take place during upcoming TERRANOVA meetings, telcos and in the form of email correspondence, it will be considered as a document on which all partners have agreed upon.

NOTE: To that effect please provide your comments, corrections and clarifications and return your review to the task leader in question.



2. PARTNERS MM ALLOCATION

The list of involved partners and their PM allocation is as follows:

Partner Short name PM allocation in Task no



3. TASK NO: OBJECTIVES AND DESCRIPTION Describe task and its objectives

4. IDENTIFICATION OF SUB-TASKS Subtasks might not have been identified in details during the time of proposal creation. Describe sub-tasks (a sub-sub-tasks is needed) here. Include timeplan for those subtasks.

5. RISKS AND/OR ISSUES Describe here know risks and/or issues, potential technological limitations (e.g. VGA resolution of sensor, max computational power, etc.)

6. REQUEST FOR CONTRIBUTION Describe in the table below, which contributions are necessary in order to fulfill considered task.

Partner Contribution Description

7. CONTRIBUTION TO DELIVERABLE(S) Please describe which deliverable(s) task is feeding.



8. DELIVERABLE X.Y TABLE OF CONTENTS

Provide deliverable (which is fed by the considered task) Table of Contents (ToC), to the best of Your knowledge.


TERRANOVA Project

ANNEX VIII – QUARTERLY REPORT TEM


Quarterly Management ReportWork Package 1

TERRANOVA Project


Call: H2020-ICT-2016-2

Topic: ICT-09-2017 - Networking research beyond 5G




QUARTERLY REPORT TEMPLATE


No. 761794

Quarterly Management ReportWork Package 1 - Project Management

Networking research beyond 5G

July 2017

months

Page 43 of 51


Quarterly Management Report





No. Name Short Name Country 1

(Coordinator) University of Piraeus Research Center UPRC Greece

2 Fraunhofer Gesellschaft (FhG-HHI & FhG-IAF) FhG Germany 3 Intracom Telecom ICOM Greece 4 University of Oulu UOULU Finland 5 JCP-Connect JCP-C France 6 Altice Labs ALB Portugal 7 PICAdvanced PIC Portugal




Project short name and number TERRANOVA (761794) Work package WP1

Title Quartlery Management Report

Version v0.1

Responsible unit JCP-C

Involved units UPRC, JCP-C

Type6 R

Dissemination level7 CO Last update DD.MM.YYYY

6 Types. R: Document, report (excluding the periodic and final reports); DEM: Demonstrator, pilot, prototype, plan designs; DEC: Websites, patents filing, press & media actions, videos, etc.; OTHER: Software, technical diagram, etc. 7 Dissemination levels. PU: Public, fully open, e.g. web; CO: Confidential, restricted under conditions set out in Model Grant Agreement; CI: Classified, information as referred to in Commission Decision 2001/844/EC.



Document History

Version Date Status Authors, Reviewers Description v0.1 27.07.2015 Draft Kristaps Dobrajs (JCP-C) Initial version, definition of a

structure

v0.4 v0.5 v0.6






CA Consortium Agreement GA Grant Agreement EC European Commission



Executive Summary

The Quarterly Management Report (QMR) is intended to provide a quick overview of the activities performed by the consortium and the related expenses based on the past three months’ activities.

It will not only highlight the on-going activities but also the possible issues and or deviations and describe the remedial actions that were defined.



1. SUMMARY OF MAIN ACHIEVEMENTS AND KEY OUTCOMES 1.1 Technical Progress and Achievements

1.1.1 WPx

1.1.1.1 Task x.1:

Summary of Progress towards the Objectives

Significant Results

Deviations, Impacts and Corrective Actions

1.2 Project Status

1.2.1 WP1 Project Management and Coordination

Task 1.1: Project Organisation and Management [M1 – M30]

Task 1.2: Project Technical and Innovation Management [M1 – M30]

Task 1.3: Project Office and Quality management [M1 – M30]



1.3 Deliverable and Milestone Status

1.3.1 Deliverables

Del. no. Deliverable name Version WP

no. Lead participant Nature Dissemination

level

Due delivery date from Annex I (proj month)

Actual / Forecast delivery date Dd/mm/yyyy

Status Contractual Yes/No

Comments

Dx.y

1.3.2 Milestones

Milestone

no.

Milestone name

Work Package N°

Lead Beneficiary

Delivery date from Annex I dd/mm/yyyy

Achieved Yes/No

Actual / Forecast achievement date dd/mm/yyyy

Comments

MSx



1.4 Project meetings, dates and venues

The follow meetings have taken place during the period

Meetings attended (including WP and consortium meetings, Conferences and Workshops)

Date Meeting Venue Hosting Company Meeting Type / Group Nr of Person(s) Comments

- - - End of Document - --

Documents

À o í X í W } i D v P u v W o v - ict-terranova.eu · À o í X í W } i D v P u v W o v - ict-terranova.eu ... ñ