charge of carrying out the technical work described in Section
\ref{Workpackages}.</dd>
</dl>
+
+ <h2>Decision Process</h2>
+ <p>Decisions will normally be taken by seeking consensus. However,
+ after a reasonable amount of time has been allowed to illustrate
+ and defend of conflicting positions, in order to avoid deadlock
+ in project operational progress, the approval of two-third majority
+ of the partners will be sufficient. If the decision being taken
+ is unacceptable
+ to partners found in the minority positions, the resolution of the
+ conflict will be elevated to each partner's higher executive level.
+ If no resolution is possible, than the standard ``red flag'' procedure
+ will be used, as a last resort. Either the PCC or the Project Manager
+ can initiate the conflict resolution procedure.</p>
+
+ <h2>Information Flow</h2>
+ <p>Information flow within the Project will be ensured by exchange of
+ internal technical papers, notification of relevant new publications
+ technologies or standards, and reports from external meetings.
+ All technical documentation generated by the project should be
+ exchangeable in electronic format, according to a set of guidelines
+ to be agreed at project start-up. The project Manager will enforce
+ adherence to these guidelines. Only strictly formal correspondence
+ will be exchanged by ordinary mail and telefax. Urgent correspondence
+ over e-mail will be sent with a request for explicit acknowledgement.</p>
+ <p>The Coordinating Partner will be responsible to prepare and maintain
+ a Web page of the project and a CVS repository (also available via Web).
+ The CVS repository is meant to keep the trace of the overall
+ progress of the Project, and it will be used by the PCC to monitor
+ the state of advancement of the work. Each partner periodically
+ submit reports to the prime contractor, listing all technical
+ contributions, publications, meeting attendance and other information
+ which may help in understanding the provided effort and cost figures.</p>
+ <p>The Project will establish a high quality Web site for internal and
+ external communications. It will be operational as from one month of
+ the commencement date and will be maintained during the project duration.
+ The ``members only'' area will include e.g. all private deliverables,
+ progress and management reports, and cost statements. The open area will
+ include
+ the project presentation as defined in Appendix 2 of the ``Guidelines
+ for Contract Preparation'' document, all public deliverables, and any
+ relevant information suggested by the Project Exploitation Board.</p>
+
+ <h2>Quality Procedures</h2>
+ <p>For all deliverables, the following review procedure
+ will be adopted: release by the Work-Package Leader, two-week review
+ period for comments by the PCC, two-week amendment period to incorporate
+ PCC recommendations, one-week balloting period for approval by the
+ PCC.</p>
+
+ <h2>Confidentiality and IPR handling</h2>
+ <p>Matters related to Confidentiality and IPR handling will be defined
+ in the ``Consortium Agreement''. As regards literature papers
+ originated from work in the Project, there will be two
+ categories of papers:</p>
+ <ol>
+ <li>Project Endorsed Publications, requiring notification and approval by
+ the PCC.</li>
+ <li>Project-related publications, only requiring notification to
+ the PCC. They must contain an acknowledgement of support by the
+ project Consortium and, if required by the PCC, a disclaimer that
+ the views are not necessarily those of the Consortium.</li>
+ </ol>
+ <p>Concerning possible contributions to Standards, they will be
+ directly submitted by project members.</p>
</body>
</html>
projects / helm.git / commitdiff