Project governance and introduction of management...

1 E. PICCIOTTTI THE ADRIARADNET PROJECT KICK-OFF MEETING

Project governance and

introduction of management team

THE ADRIARadNet PROJECT

University of L’Aquila

E. Picciotti ,V. Colaiuda, F. Marzano


ADRIARadNet Work Plan

The overall project objective will be carried out through 7 WP,

each WP is subdivided into one or more actions:

WP0: Project preparation (DONE!!!)

WP1: Project management and coordination

WP2: Communication and dissemination

WP3: User-oriented requirements and guidelines for Adriatic

hydrometeorological decision support systems

WP4: Integrated system for Adriatic hydro-meteorological radar-

based monitoring and model-based forecasting

WP5: Design and implementation of Adriatic web-based

information network and data-sharing platform

WP6: Demonstration and assessment campaign in Italian central

Adriatic area

WP7: Demonstration and assessment campaign in Balkan southern

Adriatic area


WP Action Amount Start date End date Duration

1 1.1 170.000 OCT 2012 SEP 2014 24 Months

WP Action Amount Start date End date Duration

1 1.2 160.000 OCT 2012 SEP 2014 24 Months

Managements activities are performed during

the entire lifecycle of the project

WP1 Has two action


Deliverables for Management WP1

The foreseen meeting as write in AF::

- kick-off meeting in L'Aquila at month 1;

- first interim meeting in Tirana at month 6;

- progress meeting in Ancona at month 12;

- second interim meeting in Dubrovnik at month 18;

- final meeting in L'Aquila at month 24.

Deliverables: :

All meeting requires to write a report (minutes) that

to be submitted to IPA


• Efficient and effective management of the project to ensure all deliverables are met within the proposed timescale.

• To ensure that the necessary resources are made available to carry out the aims and objectives of the project.

• To coordinate communications internally within the Consortium, between the Consortium and IPA Managing Authority

Management and Coordination Objectives


General Assembly (Steering Committe)

Project Coordinator

WP1 Leader

WP3 Leader

WP4 Leader

WP5 Leader

WP6 Leader

WP2 Leader

All Partners

WP7 Leader

Management Team

LB FB7 FB6 LB FB1 FB2 FB3

Project Governance structure

To reach the objective the management governance

has been structured as shown below

Financial Team


The General Assembly shall consist of one representative of each Partner, the following decisions shall be taken by the General Assembly:

• Any technical change in the Application Form

• Any financial change in the Application Form

• Proposal to the European Commission for suspension of all or part of the Project

• Proposal to the European Commission for termination of the project and the Partnership agreement

The General Assembly shall not deliberate and decide validly, unless the majority (5/8) of its members are present or represented (quorum)

General Assembly role

General Assembly is the decision making boby of the Consortium

and assists the the Coordinator for technical and management issues


• Leadership of the consortium

• Oversee collaboration between partners

• Interaction with the IPA

• Oversee “Advertisement” of the project

• Resolve any kind of issues

• To solve the possible conflicts within the partners

• Verification of time schedule of the work

• Intermediary between IPA and the Partners

• Check real use of partner funds against plans

Project Coordinator role


• Design of Web-site, logo and brochures

• Internal and External communication

• Write all project and meeting report

• Provide all reports to IPA Managing Authority

• The day to day contact for any question of the

partners and support in reporting activities

• Responsible for the handling of funds received

by the IPA

Management team role


• Financial and administrative management

• Overseeing of all IPA regulations regarding

use of funds and administrative framework

• Has overview of the planned use of each

partner funds

• The day to day contact for any question of

the partners and support in financial activities

Financial Team role


Current Project Governance people

• Frank Marzano (CETEMPS, Project Coordinator)

• Valentina Colaiuda (CETEMPS, Management Team)

• Errico Picciotti (CETEMPS, Management Team)

• Roberto Olivieri (BEEP, Financial Team)

• Marcella Rezzolla (BEEP, Financial Team)

• Paolo Sala (BEEP, Financial Team)









by the IPA

Focus on Reports


REPORTING REQUIREMENTS

During the course of our project we must

submit to IPA:

1. Progress Report

2. Progress Project Report

3. Deliverables


1.Progress Report

WHEN: Each Final Beneficiaries can report their

expenditures whenever they want

The Progress Report is composed of:

• Activity Report that provides information on the activities

implemented in the related period of reporting,

• Financial Report which provides information on project’s

expenditure per budget lines and WP.

WHO: Each Final Beneficiaries, LB and FBn

HOW: both in electronic (by MIS) and paper format (to

FLCO)


Step for Reimbursement procedure


2.Progress Project Report

WHEN: on a six-monthly basis: by 30th April and by 31st

October

The Project Progress Report is composed of:

• Progress report detailing project activities as a whole,

achievement of outputs, results and deliverables produced

• Financial reporting regarding validated expenditures (DVE)

and the submitted applications for reimbursement (AR)

• Relevant enclosures as communication and publicity

documents, deliverables and so on…

WHO: Only Lead Beneficiaries, LB

HOW: both in electronic (by e-mail) and paper format (to

IPA-JTS premises)


3.Deliverables

• Each significant element of the project should

conclude with a deliverable which is the concrete output

and evidence of the work.

•A Deliverable may be a report, or an action such as the

construction of a prototype, the installation of a

demonstrator, the organisation of a conference with the

production of related proceedings, the publication of a

book, the completion of a specification, etc.

WHEN: Within the Project Progress Report (every six months)

WHO Only LB also those carried out by FBn

HOW: Each FBn send his deliverable to LB, then LB send

the deliverables in paper format to IPA-JTS premises









by the IPA

Focus on Web site and logo


About Project Website and logo......


Design of Web-site http://cetemps.aquila.infn.it/adriaradnet/


Partner Contact Section

partner to contact


Web-site reserved area

Reserved area


Web site: Reserved Area

In the reserved area you can find all relevant

documentations about ADRIARadNet:

1. Grand Agreement

2. General Conditions

3. Partnership Agreement

4. Funding Allocation Letter (FAL)

5. Application Form (AF)

6. Programme Management and Control Manual

7. Guideline for MIS and Procurement

8. Brochures and other dissemination material

9. Template for reporting and project change

10. Any deliverables submitted to IPA

11. Meeting Reports and related presentation


Official Logo

radar antenna

.

drop

.

adriatic map

.


Brochure

Have been carried out in close collaboration with

ABRUZZO REGION in 4 different languages


Thanks for your Attention

For more detail Please check the

Programme Management and Control Manual

Project governance and introduction of management...

Documents

Transcript of Project governance and introduction of management...