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