X-Git-Url: http://matita.cs.unibo.it/gitweb/?a=blobdiff_plain;f=helm%2Fmowgli%2Fhome%2Fxml%2Fproposal%2Fproject-management.xml;fp=helm%2Fmowgli%2Fhome%2Fxml%2Fproposal%2Fproject-management.xml;h=0000000000000000000000000000000000000000;hb=1696761e4b8576e8ed81caa905fd108717019226;hp=86b9face89f541f95343b6e13e53eaf02f889457;hpb=5325734bc2e4927ed7ec146e35a6f0f2b49f50c1;p=helm.git diff --git a/helm/mowgli/home/xml/proposal/project-management.xml b/helm/mowgli/home/xml/proposal/project-management.xml deleted file mode 100644 index 86b9face8..000000000 --- a/helm/mowgli/home/xml/proposal/project-management.xml +++ /dev/null @@ -1,256 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -]> - - - - - - - - - -
- Previous Page - - Index - - Next Page -
-
- - -

Project Management

-

The Project management will be assured by the following relevant - roles:

-
    -
  1. Project Manager
    2. -
  2. Exploitation manager
    3. -
  3. Work-package Leaders
    4. -
  4. Technical Contributors
    5. -
-

and by the following Project Bodies:

-
    -
  1. Project Coordination Committee (PCC)
    2. -
  2. Project Exploitation Board
    3. -
  3. Work-package Teams.
    4. -
- -
- - - The mandate of the Project Manager is to represent the Project, report to - the Commission, monitor overall performance of the project, ensure - accomplishment of the technical objectives, promote project visibility, - promote dissemination of project results in the relevant international - forums, promote acceptance of project results, administer - project resources and monitor project spending. - - - - - He is responsible for coordinating exploitation activities undertaken - by the Project Exploitation Board (PEB) in close cooperation with the - Project Coordination Committee (PCC). - - - - - They are responsible for the performance of - Work-packages, and they must be committed to the Work-package for at - least five man months per year. - - - - - Technical Contributors are specialised - staff provided by the partners. They could be either people active on - a stable basis into a Work-package, or people who contribute from time - to time on specific tasks related to the work-plan (external - contributors). - - - - - - - - - - - - The PCC is chaired by the Project - Manager and constituted by one representative from each Partner, and - is the main decision body of the Consortium. It is in charge - of all formal decisions regarding technical direction of the work, - proper interrelation between Work-packages, - relations with IST Office, policies for promotion of results, - administrative arrangements. - - - - - - - - - - - - The PEB is chaired by the - Project Exploitation Manager, and composed by the Exploitation - Managers of each partner. It monitors the state of the art in - the domains of content-based information technologies, W3C activities, - Web publishing, and digital libraries. It is responsible for - planning the dissemination and exploitation strategies for the - consortium, to be approved by the PCC. - - - - - They are constituted of the technical contributors. - Each team is chaired by a Work-package Leader, and it is in - charge of carrying out the technical work described in - each Work-Package. - - -
- -

Decision Process

-

Decisions is normally 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 is 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.

- -

Information Flow

-

Information flow within the Project is 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 - agreed at project start-up. The project Manager enforces - adherence to these guidelines. Only strictly formal correspondence - is exchanged by ordinary mail and telefax. Urgent correspondence - over e-mail is sent with a request for explicit acknowledgement.

-

The Coordinating Partner is 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 is 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.

-

The Project has established a high quality Web site for internal and - external communications. It has been operational as from one month of - the commencement date and will be maintained during the project duration. - The ``members only'' area includes e.g. all private deliverables, - progress and management reports, and cost statements. The open area - includes 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.

- -

Quality Procedures

-

For all deliverables, the following review procedure - is 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.

- -

Confidentiality and IPR handling

-

Matters related to Confidentiality and IPR handling have been defined - in the ``Consortium Agreement''. As regards literature papers - originated from work in the Project, there are two - categories of papers:

-
    -
  1. Project Endorsed Publications, requiring notification and approval by - the PCC.
    2. -
  2. 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.
    3. -
-

Concerning possible contributions to Standards, they are - directly submitted by project members.

- - -
- - - - - - -
- Previous Page - - Index - - Next Page -
- -