Deliverable D1.1 Project Management Manualforensor-project.eu/wp-content/uploads/2015/10/FORENSOR... · 2015-10-20 · D1.1 – Project Management Manual FORENSOR Project Page 3 of

This project has received funding from Horizon 2020, European Union’s

Framework Programme for Research and Innovation, under grant agreement

No. 653355

Deliverable D1.1 Project Management Manual

Work Package 1 - Project Management

FORENSOR Project

Grant Agreement No. 653355

Call H2020-FCT-2014-2015 “Fight against Crime and terrorism”

Topic FCT-05-2014 “Law enforcement capabilities topic 1: Develop novel monitoring systems

and miniaturised sensors that improve Law Enforcement Agencies' evidence- gathering abilities”

Start date of the project: 1 September 2015

Duration of the project: 36 months

D1.1 – Project Management Manual

FORENSOR Project Page 2 of 30

Disclaimer

This document contains material, which is the copyright of certain FORENSOR contractors, and

may not be reproduced or copied without permission. All FORENSOR 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 FORENSOR consortium consists of the following partners.

No. Name Short Name Country

1 ETHNIKO KENTRO EREVNAS KAI TECHNOLOGIKIS ANAPTYXIS CERTH GR

2 JCP-CONNECT SAS JCP-C FR

3 STMICROELECTRONICS SRL STM IT

4 FONDAZIONE BRUNO KESSLER FBK IT

5 EMZA VISUAL SENSE LTD EMZA IL

6 SYNELIXIS LYSEIS PLIROFORIKIS AUTOMATISMOU & TILEPIKOINONION MONOPROSOPI EPE

SYNELIXIS GR

7 VRIJE UNIVERSITEIT BRUSSEL VUB BE

8 ALMAVIVA - THE ITALIAN INNOVATION COMPANY SPA ALMAVIVA IT

9 VISIONWARE-SISTEMAS DE INFORMACAO SA VISIONWARE PT

10 VALENCIA LOCAL POLICE PLV ES

11 POLÍCIA JUDICIÁRIA (MINISTÉRIO DA JUSTIÇA) MJ PT



Document Information

Project short name and number FORENSOR (653355)

Work package WP1

Number D1.1

Title Project Management Manual

Responsible beneficiary JCP

Involved beneficiaries JCP, CERTH, SYN

Type1 R

Dissemination level2 PU

Contractual date of delivery 30.09.2015

Last update 30.09.2015

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

v 0.1 11.09.2015 Draft JCP-C Initial version, definition of a structure

v 0.2 18.09.2015 Draft JCP-C Sections 2 and 4 created

v 0.3 23.09.2015 Draft JCP-C Section 3 and 5 created

v 0.4 25.09.2015 Draft JCP-C Sections 4 and 7 created

v 0.5 28.09.2015 Draft JCP-C Sections 4.1 added, DTW template inserted

v 0.6 28.09.2015 Draft JCP-C Consistency with D1.2 checked, comments for open points added. Formatting of the document. Review-ready version.

v 0.7 29.09.2015 Draft CERTH Review and comments for improvement

v 0.8 29.09.2015 Draft SYN Review and comments for improvement

v 0.9 30.09.2015 Draft JCP-C Implementation of comments from CERTH

v 0.10 30.09.2015 Draft JCP-C Implementation of comments from SYN

v 0.11 30.09.2015 Draft JCP-C Clean up and formatting the document. Ready for release.

v 0.12 30.09.2015 Draft JCP-C Additional comments from CERTH implemented. Section 7.3 added.

v 2.0 30.09.2015 Final JCP-C Final document for submission.



Acronyms and Abbreviations

Acronym/Abbreviation Description

AP Action Point

CA Consortium Agreement

CV Curriculum Vitae

DMS Document Management System

DoA Description of Action

Dx.y Deliverable x.y; ‘x’ is the number of the WP where the deliverable belongs and ‘y’ is the number of the deliverable.

FORENSOR FOREnsic evidence gathering autonomous seNSOR

GA General Assembly

IP(R) Intellectual Property (Rights)

KOM Kickoff Meeting

KPI Key Performance Indicator

P2P Peer-to-peer

PC Project Coordinator

PM Person-month

PMC Project Management Committee

PO Project Officer

PSC Project Steering Committee

PTM Project Technical Manager

ToC Table of Contents

WBS Work Breakdown Structure

WP Work Package

WPL Work Package Leader



Contents

1. INTRODUCTION ..................................................................................................................... 11

2. PROJECT MANAGEMENT ....................................................................................................... 12

2.1 Project governance ........................................................................................................ 12

2.1.1 Project management structure ............................................................................. 12

2.1.2 Operational bodies ................................................................................................ 12

2.1.3 Main management roles ....................................................................................... 13

2.1.4 Conflict resolution ................................................................................................. 15

3. Information and documentation management .................................................................... 16

3.1 Document repository .................................................................................................... 16

3.2 Mailing lists .................................................................................................................... 16

3.3 Templates ...................................................................................................................... 16

3.4 Document and file numbering and versioning .............................................................. 16

3.4.1 Naming .................................................................................................................. 16

3.4.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 ................................................................................................................................ 19

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 ............................................................................................................................ 20

6.1 Internal reporting .......................................................................................................... 20

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

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



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

6.2.3 Yearly reports ........................................................................................................ 20

7. IPR protection and DISSEMINATION ..................................................................................... 21

7.1 Main principles of IPR protection .................................................................................. 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

7.3 Main dissemination principles....................................................................................... 21

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

ANNEX I – FORENSOR ROLE ALLOCATION ..................................................................................... 23

ANNEX II – DetaIled Task Workplan (DTW) template ................................................................... 24



List of Figures

Figure 1 – FORENSOR project management structure .................................................................. 12

Figure 2 – Conflict resolution principle in FORENSOR ................................................................... 15



List of Tables

Table 1: Deliverables review and approval procedure. ................................................................. 17



Executive Summary

This document presents the Project Management Manual – the guideline to Consortium

Partners in administrative, organizational and procedural questions in FORENSOR. It reminds the

project management structure, hierarchy, main decision bodies and Partner contacts, and

describes the steps of decision making and conflict resolution in the project. It describes rules

and tools for management of information and documentation and gives necessary template.

On procedural side it describes basic guideline for implementation of tasks and deliverables,

gives reference scheduling and guidelines for that and indicate how to behave in case of

identification of risks and problems.

Approach to organization of physical and remote meetings is also given, along with the

reporting guidelines.

Finally, main principles of IPR management and security clearance are described.



1. INTRODUCTION The present document is intended to serve as a manual for project Partners in all everyday

routines and activities related to the management of the FORENSOR project 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 information on project operational organization

and procedures, information and document management, conflict resolutions, financial matters,

reporting, etc. For this reason, the document is intended to be a living document, updated when

any related rule, procedure, etc. has been changed.

Section 2 of document reminds general hierarchy of project management and describes

operational bodies and roles. Section 3 describes general principles of management of

information and documentation and provides necessary templates. Section 4 provides

description of workflows agreed in the project implementation, particularly for the planning of

ongoing and future tasks. Section 5 informs about organization of meetings, while section 6

describes necessary reporting tasks. Finally, section 7 describes general principles of IPR

management. Two annexes show allocation of FORENSOR roles and provide template for

planning of tasks.



2. PROJECT MANAGEMENT

2.1 Project governance

2.1.1 Project management structure

FORENSOR project has a multi-level management structure (Figure 1), where work is performed

by 4 main bodies, which are:

General Assembly;

Project Steering Committee;

Project Management Committee;

Workpackage Groups.

FORENSOR General Assembly

All Partners

WP9 Dissemination and ExploitationTechnical Group

External Advisory Board (EAB)

Security Advisory BoardProject Security Officer

Project Management CommitteeCoordinator, WP Leaders

- IPR Manager- Quality Manager

-Risks Manager- Business Development Manager

- Ethical Manager

Steering Committee

All Partners (Technical)

Pro

ject

Off

ice

Org

an

iza

tio

na

l an

d a

dm

inis

tra

tive

su

pp

ort

WP2Technical

Group

WP3Technical

Group

WP4Technical

Group

WP5Technical

Group

WP6Technical

Group

WP7Technical

Group

WP8Technical

Group

Figure 1 – FORENSOR project management structure

2.1.2 Operational bodies

Clear hierarchy is introduced for fulfilling the project goals:

The General Assembly, being ultimate decision body of the project, approves 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.

The Project Steering Committee (PSC) establishes the main lines of the project; it is

chaired by the Project Coordinator. All PSC members and their contact details are

mentioned in Annex I.



The Project Management Committee is the executive body of the project (under the

guidance of the Project Steering Committee); it is chaired by the Project Technical

Leader. PMC is composed of the Coordinator, WP1 leader, the seven technical (WP2-

WP8) WP Leaders, Quality Manager, IPR Manager, Risks Manager, Business

Development Manager and Security Officer (see section 2.1.3)

The WP technical groups ensure day-to-day WP work; each group is chaired by the

respective WP Leader. List of WP leaders and their contact details can be found in Annex

I.

2.1.3 Main management roles

Particular persons are responsible for administrative, financial, technical, business-related,

ethical, IPR, quality and risk management aspects. Sub-chapters below are describing people

responsible for those aspects – Consortium Partners are expected to communicate to those

people in case of issues in mentioned aspects.

2.1.3.1 Project Coordinator

The Project Coordinator is Dr. Petros Daras (CERTH). His major tasks are:

Financial coordination of the project and distribution of EC’s payments to partners,

Chairing the General Assembly,

Chairing the PSC,

Confirmation and approval of periodic reports for the Commission,

Representative of consortium to events.

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

2.1.3.2 Project Technical Manager

Project Technical Manager is Dr. Petros Daras (CERTH). Project Technical Manager has the

following responsibilities:

Supervision of the overall technical progress of the project,

Chair of External Advisory Board,

Technical relationship and coordination with other relevant R&D projects,

Consolidation of the technical reports,

Follow-up and coordination of all technical work-packages,

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

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



2.1.3.4 Business Development Manager (BDM)

The obligation of BDM is to coordinate the work related to business aspects and market

proximity. Business Development Manager will ensure proper outputs during product/process

conceptualizations at project milestones, follow up on market analysis and development of

business models/monetization schemes, and report to GA. FORENSOR BDM is Stefania Di Serio

(Almaviva).

2.1.3.5 Project Security Officer and Security Advisory Board

FORENSOR Security Officer is Mr. Lazaros Gymnopoulos (CERTH). His major task is to follow the

information and knowledge generated from FORENSOR project and to warn the Project

Coordinator and the Steering Committee on appearance of sensitive information that might be

subject to limitations in dissemination. This assumes review of the deliverables, publications,

and other dissemination material, ensuring that no sensitive information will be disclosed.

Security Officer chairs the Security Advisory Board, which members are:

Prof. Paul De Hert (VUB)

Mr Ángel Albendín (PLV)

Carlos Farinha (PJP)

João Carreira (PJP)

The major roles of the Security Advisory Board will be to contribute to the definition of the data

management plan (D1.4) and to the monitoring of FORENSOR security challenges. Moreover,

they will have to review the deliverables, publications, and other dissemination material,

ensuring that no sensitive information will be disclosed. The Security Advisory Board will take

particular care in assessing the sensitivity of the following deliverables before any publication:

D1.4; D3.1; D6.2; D6.5; D7.5; D8.3; D8.4.

2.1.3.6 Ethical Manager

FORENSOR has included expert on fundamental rights, legal and ethical aspects into its

Consortium and will pay full attention to all and any arising legal, ethical and societal aspects

regarding development, installation and use of FORENSOR sensors by LEA. The Ethical Manager

is Dariusz Kloza (VUB).

2.1.3.7 IPR Manager

FORENSOR IPR Manager is Dr Giulio Ulrini (STM). IPR Manager assesses all IPR relevant

information that was brought in the project or was developed within the project. IPR Manager

gives recommendations to the GA on the handling of the assessed IPR issues. In his tasks, the

IPR Manager may request the assistance of experts with IPR background recruited from the

consortium partners.

2.1.3.8 Quality manager and Risk Manager

Quality manager is Dr Nicholas Vretos (CERTH) and project risk manager is Roman Kaurson (JCP-

C). Those two roles are extensively described in Deliverable D1.2 [2], where main principles of

quality management are described.



2.1.4 Conflict resolution

Hierarchy described in 2.1.2 should be followed for resolutions of potential problems:

When a conflict occurs in a WP technical group, WP leader seeks for the consensus to solve the problem. If the problem cannot be solved it is escalated to the Project Management Committee: the WPL prepares a description of the problem and its possible solutions.

If consensus cannot be reached within the PMC, the Technical Project Manager escalates it to the Steering Committee, using the same process as described above.

If the problem cannot be solved by consensus, the steering committee escalates it to GA and a vote occurs, requiring a simple majority. Extraordinary GA meetings can be organized.

Figure 2 – Conflict resolution principle in FORENSOR



3. INFORMATION AND DOCUMENTATION MANAGEMENT

3.1 Document repository At the time of writing this deliverable (September 2015) fully secured document repository,

solely dedicated to FORENSOR, is being set up by the Partner PLV. All necessary documentation

is currently stored in the Dropbox-like cloud platform, until fully customized and functional

solution is launched.

3.2 Mailing lists Two mailing lists are organized for handling administrative and technical questions arising in the

project. Those mailing lists are:

Administrative mailing list: [email protected];

Technical mailing list: [email protected].

3.3 Templates Templates for project presentation and project deliverables are given in the Deliverable D1.2.

Template for Detailed Task Workplan (see 4.1) can be found in Annex II.

3.4 Document and file numbering and versioning

3.4.1 Naming

Document naming principle is as follows:

FORENSOR_[document identity]_WPn_dd[month]yyyy_vx.y.ext

E.g.:

FORENSOR_D1.1_WP1_02September2015_v0.1.pdf



or (when Work Breakdown Structure (WBS) name does not exist):

FORENSOR_prelim.system.reqs_WP3_02September2015_v0.1.pdf

3.4.2 Versioning:

v0.x, 1.x, 2.x, etc. is working version;

v1.0, 2.0, 3.0 is 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.

mailto:[email protected]

mailto:[email protected]



4. WORKFLOW PROCEDURES

4.1 Creation of Detailed Task Workplan (DTW) Every starting task begins with producing a Detailed Task Workplan (DTW) – internal document,

intended to decrease a risk of different understanding of task by involved partner. DTW

template should contain at least 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.

Task leader is responsible for producing DTW and distribution of it among Partners. The

template of DTW can be found in Annex II.

4.2 Producing a deliverable 4.2.1 Initial table of contents

It is important to define at least initial table of contents for deliverable as early as possible.

Table of contents for deliverable should be included in the DTW described above.

4.2.2 Timeline for deliverable production, deliverable review, approval and

submission Detailed timeline of deliverable production, along with series of deadlines is described in the

section “Deliverables Review and Approval Procedure” of Deliverable D1.2. Here the typical

schedule with respective deadlines is reminded.

Table 1: Deliverables review and approval procedure.

Step When3 Who What

#1 42 (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.

#2 39 WPL, PTM, PSC, PMC

Provide comments/ feedback.

#3 21 (3

weeks) Document

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

#4 20 Quality

Manager Sends final draft of the deliverable to the Internal Reviewers.

#5 14 (2

weeks) Internal

Reviewers Provide comments/ feedback.

#6 7 (1

week) Document

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

3 This column shows the days before the contractual delivery date.



#7 1 Project

Coordinator Approves and uploads the deliverable to the EC services.

4.3 Reporting an issue, a risk or a problem Once discovered and issue, a risk or a problem of technical nature, every Partner should

immediately inform the Project Technical Manager the Project Coordinator, and the Risk

Manager (see 2.1.3) in written form. The report should contain at least following points:

Description of the problem;

Description of the proposed solution;

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, Coordinator and Project Office shall be informed.



5. MEETINGS

5.1 Physical meetings Both internal and external meetings are possible during timeline of the project. For planning of

travels and accommodation, 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 in the beginning of the project, when

a degree of uncertainty in technical questions and end-users (LEAs) exists. P2P meeting between

partners working on particular topic are possible as well (subject of Coordinator approval).

Whenever the project coordinator considers that there is a crisis situation that cannot be solved

with off-line (email communications) or Phone calls, he may call for an extraordinary meeting.

During plenary meetings, meetings of the various bodies might take place but at minimum WP

Technical Groups meetings should take place.

5.1.2 External meetings

Several types of external meetings could be organized as well, e.g.:

Project dissemination events;

Meeting with External Advisory Board.

Furthermore, Project periodic meetings shall be organized in the end of each period and after

project end. Normally, at least WP Leaders shall attend review meetings, however general rule is

that during review meeting Consortium shall be able to answer all questions related to work

performed during considered period. Thus, Coordinator may call for specific Partner to attend

the review meeting.

5.2 Phone conferences (internal) Phone conferences can be organized any time. Partners shall send their requests for

organization of phone conference to Project Office.

GA meetings are usually organized via phone. A GA meeting shall be organized at least once a

year, or upon request.



6. REPORTING

6.1 Internal reporting It is of internal use and should help to detect early issues.

Every partner introduces by the end of the quarter the PM resources spent and a short description of work achieved, using 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 solved.

It is due at least 2 weeks after the beginning of the next quarter.

6.2 External reporting

6.2.1 Periodic reporting 6.2.1.1 Technical reporting

Technical part of periodic report shall be submitted in the end of each period – during 60 days after formal end of each period. WP Leaders are responsible for producing periodic report, with the contributions of Task Leaders where necessary. The report is organized and compiled by Project Office using EC template; the Coordinator shall 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 period. Financial reporting in the end of each period shall be done via NEF functionality of the Participant Portal4 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 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.

6.2.3 Yearly reports

In addition to the contractual periodic and final reports, the Coordinator will submit to the Commission supplementary yearly reports.

The yearly Report should be limited to 3 sections:

The key results achieved by the project during the past year. WPL is responsible for writing that section;

The activity performed by partners (responsibility of each Partner) – internal report precedes that;

Report on the spending of resources (financial expenditures and manpower spending).

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

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



7. IPR PROTECTION AND DISSEMINATION The Data Management Plan (D1.4) due M3 will incorporate all rules and guidelines concerning

the management of IPR, both background and foreground. Below are few main principles, which

should be stated in the early beginning of the project.

7.1 Main principles of IPR protection

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 CA [1] any Background IP they are willing to submit to the project within the CA 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. 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 on 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 FORENSOR consortium endeavours to offer open access to its scientific results reported in

publications. However, due to FORENSOR nature as security project, no information will be

published before a Security Clearance is granted by the Project Coordinator, project security

specialists and PO.

7.3 Main dissemination principles Apart from security clearance, following rules should be applied:

When the expenses related to dissemination (e.g. travelling to conference to present a

paper) are claimed during FORENSOR cost claims, the project has to be officially

mentioned and this has to be proven by official documentation/contribution;

The conference/presentation/contribution documentation has to be uploaded on the

FORENSOR repository;

When the event takes place outside the EC, permission from the Project Officer has to

be granted.



8. REFERENCES [1] FORENSOR project Consortium Agreement (CA)

[2] FORENSOR Deliverable D1.2 - Project Quality Assurance Manual



ANNEX I – FORENSOR ROLE ALLOCATION

Partner/Role

Project Management Committee (PMC) General Assembly

(GA)

Steering Committee

(SC)

Security Advisory

Board

Data Controller

Financial Contacts Coordinator

Technical Manager

Security Officer IPR

Manager Quality

Manager Risk

Manager

Business Developmen

t Manager

Ethical Manager

Work Package Leaders

Chair Technical manager Coordinator Coordinator Security Officer

CERTH Petros Daras Petros Daras

Lazaros Gymnopoulos

Nicholas Vretos

Nicholas Vretos (WP5)

Petros Daras Nicholas Vretos

Petros Daras

JCP-C Roman Kaurson

Roman Kaurson (WP1)

Michele Wilmet, Roman Kaurson

Jean-Charles Point

Michele Wilmet

STM Giulio Urlini

Giulio Urlini

(WP7) Giulio Urlini Giulio Urlini Giulio Urlini

FBK Massimo Gottardi (WP4)

Massimo Gottardi

Massimo Gottardi

Financial department

contact is available to Coordinator

EMZA Zeev

Smilansky (WP4)

Eitan Ramati Zeev

Smilansky Eitan Ramati

SYNELIXIS Theodore Zahariadis

(WP6)

Theodore Zahariadis

Theodore Zahariadis

Theodore Zahariadis

VUB Dariusz Kloza

Paul Quinn (WP2)

Paul Quinn Paul Quinn Paul De

Hert Paul De

Hert Kim Coppens

ALMAVIVA Stefania Di

Serio

Paolo Piu (WP8)

Alessandra Raffone

Alessandra Raffone

Federica Staccoli Michela Grispini

VISIONWARE - Bruno Castro Filipe

Custódio Carmen Santos

PLV José L. Diego (WP9)

José L. Diego José L. Diego

Ángel Albendín

Susana Sola

MJ - João Carreira Nuno Matos

Carlos Farinha,

João Carreira

Berta Santos

ANNEX II – DETAILED TASK WORKPLAN (DTW) TEMPLATE

FORENSOR

Task X.Y - Task name

Detailed Task Workplan (DTW)

[Insert file name here]

Version: 0.1

Last Update: 30/9/2015 3:59:00 PM

Distribution Level: Confidential



Revision History

No. Version Edition Author(s) Date

1 0 1 Roman Kaurson, JCP-C 18/09/2015

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

Insert table of contents here



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 FORENSOR 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 FORENSOR 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 time plan 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.

Documents

Deliverable D1.1 Project Management Manualforensor-project.eu/wp-content/uploads/2015/10/FORENSOR... · 2015-10-20 · D1.1 – Project Management Manual FORENSOR Project Page 3 of