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