[289] | 1 | \anrdoc{Preciser les aspects organisationnels du projet et les modalites de |
---|
| 2 | coordination (si possible individualisation dâune tache de coordination).} |
---|
| 3 | |
---|
| 4 | \begin{description} |
---|
| 5 | \item[Project management structure] |
---|
| 6 | Each task is assigned to a Task Leader. |
---|
| 7 | The Task Leaders assist the project leader in the technical organization, effort |
---|
[346] | 8 | management, and progress reporting. |
---|
[289] | 9 | A steering committee is composed by task leaders and the project leader. |
---|
| 10 | The steering committee has a monthly conference call and is in charge of conflict |
---|
| 11 | management if necessary. |
---|
| 12 | Each task leader has to report on the main high-lights, major |
---|
| 13 | opportunities and problems according to the work-plan. |
---|
[356] | 14 | The redaction of the 6-month reports is the responsibility of the steering committee. |
---|
[289] | 15 | Therefore, each Partner has the responsibility to monthly inform the task Leaders of the |
---|
[346] | 16 | current development of the \ST he is in charge of. |
---|
[289] | 17 | COACH will be organized in 8 tasks whose interactions are presented in |
---|
| 18 | Figure~\ref{dependence-task}. |
---|
| 19 | |
---|
| 20 | \item[Scientific and Technical Reports] |
---|
[383] | 21 | For every yearly review, the task leader will provide a written progress report |
---|
| 22 | for each deliverable to the coordinator for integration in the contractual reports. |
---|
[289] | 23 | |
---|
| 24 | \item[Management of knowledge, Intellectual Property Right (IPR) and Results Exploitation] |
---|
[356] | 25 | %The partners will have to work under eventual NDA constraints. |
---|
| 26 | %Prior Intellectual Property remains property of the concerned partners. |
---|
| 27 | %The exploitation of the results obtained in the project and by each partner involved in the consortium will |
---|
| 28 | %follow the rules written in the articles of the Consortium Agreement accepted and signed by |
---|
| 29 | %each partner at most 6 months after the project kick-off. |
---|
| 30 | %To manage the exploitation and dissemination plan within the project, six |
---|
| 31 | %monthly meetings will analyze the intentions from the consortium (patent, publication...). |
---|
| 32 | The partners will sign and accept the Consortium Agreement at most 6 months |
---|
| 33 | after the project kick-off. It will |
---|
| 34 | 1) eventually set NDA constraints on industrial demonstrators, |
---|
| 35 | 2) fix the intellectual properties of both prior and created intellectual properties, |
---|
| 36 | 3) define the rules of exploitation of the results obtained in the project. |
---|
| 37 | \\ |
---|
[289] | 38 | To manage the exploitation and dissemination plan within the project, six |
---|
| 39 | monthly meetings will analyze the intentions from the consortium (patent, publication...). |
---|
| 40 | |
---|
| 41 | \item[Management Tools] |
---|
| 42 | In order to permit a good management, before the kick-off meeting, |
---|
| 43 | each partner will have to identify (name, address, phone, fax and e-mail): |
---|
| 44 | \begin{itemize} |
---|
| 45 | \item the financial and administrative contact person, |
---|
| 46 | \item the scientific and technical contact person, |
---|
| 47 | \item all participants to the project. |
---|
| 48 | \end{itemize} |
---|
| 49 | A complete and detailed list will be communicated to each partner and to |
---|
| 50 | the public Authority. The partners will construct mailing lists for |
---|
| 51 | day-to-day communication. |
---|
[383] | 52 | \parlf |
---|
[289] | 53 | The first task will be the redaction of a Consortium Agreement, |
---|
| 54 | dealing mainly with all aspects of the relations |
---|
| 55 | between partners, including legal aspects, property rights and further |
---|
| 56 | exploitation of the results. This document will be submitted to the |
---|
| 57 | partner's financial and legal departments, and will define the management |
---|
| 58 | rules (decision level, reporting systems, red flag cases). |
---|
| 59 | A first draft of this document will be submitted to each partner |
---|
| 60 | during the kick-off meeting. |
---|
| 61 | |
---|
| 62 | \item[Project follow-ups] |
---|
[356] | 63 | The basic communication between single project partners will be carried out by |
---|
| 64 | means of an Information System (web site), which will be developed and |
---|
| 65 | introduced at the very beginning of the project implementation. |
---|
[289] | 66 | All scientific and administrative data related to the project will be collected and |
---|
| 67 | treated within a specific e-management plate-form accessible directly by the project web |
---|
| 68 | site by an individual login and pass-word. |
---|
| 69 | The web site will have a few levels of accessibility starting with completely free access, |
---|
| 70 | open to broad public up to internal materials available only for members of the consortium |
---|
| 71 | for the e-management area. |
---|
| 72 | This communication tools will permit to perform all the reports and to follow as well as |
---|
| 73 | possible all the tasks. |
---|
| 74 | |
---|
| 75 | \item[Project monitoring] |
---|
| 76 | For this project format and size, a 12 months review by ANR, based on a yearly progress |
---|
| 77 | report incorporating milestones reports and deliverables, seems optimum. |
---|
| 78 | The internal consortium meetings will be every six months, including a kick-off meeting at the |
---|
| 79 | start of the project, in our eyes the most important of all, as it phases the partners for the start of the project. |
---|
| 80 | \end{description} |
---|