1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns="http://www.w3.org/1999/xhtml">
6 <title>Project Management</title>
7 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
8 <link rel="stylesheet" href="../style/mowgli.css" type="text/css"/>
11 <h1>Project Management</h1>
12 <p>The Project management will be assured by the following relevant
15 <li>Project Manager</li>
16 <li>Exploitation manager</li>
17 <li>Work-package Leaders</li>
18 <li>Technical Contributors</li>
20 <p>and by the following Project Bodies:</p>
22 <li>Project Coordination Committee (PCC)</li>
23 <li>Project Exploitation Board</li>
24 <li>Work-package Teams.</li>
27 <dt>Project Manager</dt>
28 <dd>The mandate of the Project Manager is
29 to represent the Project, report to the Commission, monitor
30 overall performance of the project, ensure accomplishment
31 of the technical objectives, promote project visibility,
32 promote dissemination of project results in the relevant international
33 forums, promote acceptance of project results, administer
34 project resources and monitor project spending.</dd>
36 <dt>Exploitation Manager</dt>
37 <dd>S/he will be responsible for coordinating
38 exploitation activities undertaken by the Project Exploitation Board
39 (PEB) in close cooperation with the Project Coordination Committee
42 <dt>Work-package Leaders</dt>
43 <dd>They are responsible for the performance of
44 Work-packages, and they must be committed to the Work-package for at
45 least five man months per year.</dd>
47 <dt>Technical Contributors</dt>
48 <dd>Technical Contributors are specialised
49 staff provided by the partners. They could be either people active on
50 a stable basis into a Work-package, or people who contribute from time
51 to time on specific tasks related to the work-plan (external
54 <dt>Project Coordination Committee</dt>
55 <dd>The PCC is chaired by the Project
56 Manager and constituted by one representative from each Partner, and
57 is the main decision body of the Consortium. It is in charge
58 of all formal decisions regarding technical direction of the work,
59 proper interrelation between Work-packages,
60 relations with IST Office, policies for promotion of results,
61 administrative arrangements. In view of minimising management overhead
62 and project costs, partners providing the Project Manager,
63 and the Work-packages Leaders are required to appoint the same
64 person as their official representative in the Project
65 Coordination Committee.</dd>
67 <dt>Project Exploitation Board</dt>
68 <dd>The PEB will be chaired by the
69 Project Exploitation Manager, and composed by the Exploitation
70 Managers of each partner. It will monitor the state of the art in
71 the domains of content-based information technologies, W3C activities,
72 Web publishing, and digital libraries. It will be responsible for
73 planning the dissemination and exploitation strategies for the
74 consortium, to be approved by the PCC.</dd>
76 <dt>Work-package Teams</dt>
77 <dd>They are constituted of the technical contributors.
78 Each team will be chaired by a Work-package Leader, and it will be in
79 charge of carrying out the technical work described in Section
80 \ref{Workpackages}.</dd>
83 <h2>Decision Process</h2>
84 <p>Decisions will normally be taken by seeking consensus. However,
85 after a reasonable amount of time has been allowed to illustrate
86 and defend of conflicting positions, in order to avoid deadlock
87 in project operational progress, the approval of two-third majority
88 of the partners will be sufficient. If the decision being taken
90 to partners found in the minority positions, the resolution of the
91 conflict will be elevated to each partner's higher executive level.
92 If no resolution is possible, than the standard ``red flag'' procedure
93 will be used, as a last resort. Either the PCC or the Project Manager
94 can initiate the conflict resolution procedure.</p>
96 <h2>Information Flow</h2>
97 <p>Information flow within the Project will be ensured by exchange of
98 internal technical papers, notification of relevant new publications
99 technologies or standards, and reports from external meetings.
100 All technical documentation generated by the project should be
101 exchangeable in electronic format, according to a set of guidelines
102 to be agreed at project start-up. The project Manager will enforce
103 adherence to these guidelines. Only strictly formal correspondence
104 will be exchanged by ordinary mail and telefax. Urgent correspondence
105 over e-mail will be sent with a request for explicit acknowledgement.</p>
106 <p>The Coordinating Partner will be responsible to prepare and maintain
107 a Web page of the project and a CVS repository (also available via Web).
108 The CVS repository is meant to keep the trace of the overall
109 progress of the Project, and it will be used by the PCC to monitor
110 the state of advancement of the work. Each partner periodically
111 submit reports to the prime contractor, listing all technical
112 contributions, publications, meeting attendance and other information
113 which may help in understanding the provided effort and cost figures.</p>
114 <p>The Project will establish a high quality Web site for internal and
115 external communications. It will be operational as from one month of
116 the commencement date and will be maintained during the project duration.
117 The ``members only'' area will include e.g. all private deliverables,
118 progress and management reports, and cost statements. The open area will
120 the project presentation as defined in Appendix 2 of the ``Guidelines
121 for Contract Preparation'' document, all public deliverables, and any
122 relevant information suggested by the Project Exploitation Board.</p>
124 <h2>Quality Procedures</h2>
125 <p>For all deliverables, the following review procedure
126 will be adopted: release by the Work-Package Leader, two-week review
127 period for comments by the PCC, two-week amendment period to incorporate
128 PCC recommendations, one-week balloting period for approval by the
131 <h2>Confidentiality and IPR handling</h2>
132 <p>Matters related to Confidentiality and IPR handling will be defined
133 in the ``Consortium Agreement''. As regards literature papers
134 originated from work in the Project, there will be two
135 categories of papers:</p>
137 <li>Project Endorsed Publications, requiring notification and approval by
139 <li>Project-related publications, only requiring notification to
140 the PCC. They must contain an acknowledgement of support by the
141 project Consortium and, if required by the PCC, a disclaimer that
142 the views are not necessarily those of the Consortium.</li>
144 <p>Concerning possible contributions to Standards, they will be
145 directly submitted by project members.</p>