source: anr-2010/section-4.2.tex @ 277

Last change on this file since 277 was 133, checked in by coach, 15 years ago

Paul: Consortium agreement

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