source: anr/section-project-management.tex @ 320

Last change on this file since 320 was 289, checked in by coach, 14 years ago

Changed to adapt the document to the ANR 2011 call.

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