source: anr/section-4.2.tex @ 67

Last change on this file since 67 was 38, checked in by coach, 15 years ago
File size: 3.8 KB
Line 
1\begin{description}
2\item[Project management structure]
3First of all, a good management requires that each task is assigned to a Task Leader.
4The Task Leaders assist the project leader in the technical organization, effort
5management, of the co-operation and the reporting of the progress. Each month the Task
6Leaders have to send to the project leader short update report with the
7main high-lights, major opportunities and problems according to the work-plan.
8Therefore, each Partner has the responsibility to monthly inform the task Leaders of the
9current development of the \ST he has in charge.
10COACH will be organized in \mustbecompleted{FIXME: 8} tasks whose interactions are presented in
11Figure~\ref{dependence-task}.
12
13\item[Scientific and Technical Reports]
14For every yearly review, a written progress report for each deliverable has to be
15provided by the task leader to the coordinator for integration in the contractual reports.
16
17\item[Management of knowledge, Intellectual Property Right (IPR) and Results Exploitation]
18The partners will have to work under the eventual NDA constraints.
19Prior Intellectual Property remains property of the concerned partners.
20The exploitation of the results obtained in the project and by each partner involved in the consortium will
21follow the rules written the articles of the Consortium Agreement accepted and signed by
22each partner at most 6 months after the project kick-off.
23To manage the exploitation and dissemination plan within the project, six
24monthly meetings will analyze the intentions from the consortium (patent, publication...).
25
26\item[Management Tools]
27In order to permit a good management, before the kick-off meeting, the different partners
28will have to identify namely (and with their address, phone, fax and e-mail):
29\begin{itemize}
30  \item The financial and administrative person authorized and the legal person authorized
31or at least the scientific and technical.
32  \item A complete and detailed list will be communicated to each partner and to public
33  Authority.
34  \item Mailing lists used by the partners for the day to day communication.
35\end{itemize}
36Following the requests and the information received by the partner's representatives and
37their financial and legal department, a Consortium Agreement will be written and will
38deal mainly with all aspects of the relationships between partners, including legal
39aspects, property rights and further exploitation of the results.
40Moreover, the management rules of the project will also be defined clearly in this major
41document (decision level, reporting systems, red flag cases).  A first draft of this
42document will be submitted to each partner during the kick-off meeting.
43
44\item[Project follow-ups]
45The 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.
46All scientific and administrative data related to the project will be collected and
47treated within a specific e-management plate-form accessible directly by the project web
48site by an individual login and pass-word.
49The web site will have a few levels of accessibility starting with completely free access,
50open to broad public up to internal materials available only for members of the consortium
51for the e-management area.
52This communication tools will permit to perform all the reports and to follow as well as
53possible all the tasks.
54
55\item[Project monitoring]
56For this project format and size, a 12 months review by ANR, based on a yearly progress
57report incorporating milestones reports and deliverables, seems optimum.
58The internal consortium meetings will be six monthly, including a kick-off meeting at the
59start of the project, in our eyes the most important of all, as it phases the partners for
60the start of the project on.
61\end{description}
Note: See TracBrowser for help on using the repository browser.