29.12.2012 Views

proposal part b - The Bernstein Project

proposal part b - The Bernstein Project

proposal part b - The Bernstein Project

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CIP-ICT PSP Call 4 44<br />

Pilot B<br />

[Imperialle]<br />

Work package number : 6<br />

Start date or starting<br />

event:<br />

Work package title: Monitoring and testing<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 13<br />

Participant short name OEAW BAM TUG IVCR SMK ICPAL WRM BL HERTZ UTBV BAL ISM ACV<br />

Person-months per <strong>part</strong>icipant: 5.0 0.0 8.0 7.0 10.0 3.0 4.0 2.0 1.0 8.0 2.0 2.0 1.0<br />

Objectives (ii)<br />

<strong>The</strong> primary role of the work-package is to periodically monitor the work’s progress according to the<br />

schedule. Periodic monitoring checks the quality of outputs and ensures through feed-back the best results.<br />

A mechanism will be put in place to evaluate the impact of the project on the targeted application areas<br />

during and after its lifetime.<br />

Description of work (iii)<br />

T6.1 Monitoring (SMK,OEAW)<br />

Monitor the progression of the work, notice <strong>part</strong>ners in time on delays, provide monitoring notes to the<br />

<strong>part</strong>ners, coordinator and the Commission. <strong>The</strong> monitoring will be conducted by the coordinator’s office,<br />

which has the best overview of the state of the project. A general assessment is formed by day-to-day<br />

contact with the <strong>part</strong>ners, while formal assessments, consisting in short notices about the work progress of<br />

each <strong>part</strong>ner, will have a frequency of 6 months.<br />

T6.2 Validation (SMK, IVCR, TUG, UTBV)<br />

Implement a project-wide validation mechanism, generate quality assessment reports on the developed<br />

outputs and provide feed-back to the developers. <strong>The</strong> validation mechanism is based on the cycles of<br />

evaluation and feed-back at work-package and project level, involving both project members and external<br />

users.<br />

T6.3 Evaluation (SMK, OEAW)<br />

Continual feed-back from external users on their assessment of the developed outputs is to be maintained<br />

by using the network put in place in the “WP7 Dissemination” workpackage. A final analysis and report on<br />

the observed impact will be presented at the end of the project. A list of evaluation criteria conceived in this<br />

work-package will ensure that other assessments of the project’s impact can be conducted after the<br />

project’s lifetime.<br />

Deliverables (iv)<br />

D6.1 (included in D8.2) / m12 – Assessment & evaluation report #1: Note on the progress of the work in<br />

relation to the schedule and report on reliability measures and improvements to consider.<br />

D6.2 (included in D8.5) / m24 – Assessment & evaluation report #2<br />

D6.3 (included in D8.7) / m30 – Assessment & evaluation report #3<br />

m1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!