From 112b6b32680a9c357ae247d01b71a67258188437 Mon Sep 17 00:00:00 2001 From: Claudio Sacerdoti Coen Date: Tue, 19 Mar 2002 17:35:23 +0000 Subject: [PATCH] * Some documents were not valid * Project Leaders added to every package * New data in project-management --- helm/mowgli/home/html/Makefile | 5 +- helm/mowgli/home/xml/news.xml | 2 +- .../home/xml/proposal/project-management.xml | 280 +++++++++++------- .../home/xml/work-packages/work-package.dtd | 2 + 4 files changed, 184 insertions(+), 105 deletions(-) diff --git a/helm/mowgli/home/html/Makefile b/helm/mowgli/home/html/Makefile index 6dcdd8b86..9edc5d52b 100644 --- a/helm/mowgli/home/html/Makefile +++ b/helm/mowgli/home/html/Makefile @@ -174,8 +174,9 @@ software/index.html: $(XMLROOT)/software/index.xml \ $(XSLTP) --param path_to_top "'..'" --param use_frames "'$(FRAMES)'" -o $@ $(XHTMLCONTENT) $< proposal/project-management.html: $(XMLROOT)/proposal/project-management.xml \ - $(XHTMLCONTENT) - sed $(RMDOCTYPE) $< | $(XSLTP) --param path_to_top "'..'" --param use_frames "'$(FRAMES)'" -o $@ $(XHTMLCONTENT) - + $(XHTMLCONTENT) \ + $(XSLROOT)/management.xsl + $(XSLTP) $(XSLROOT)/management.xsl $< | $(XSLTP) --param path_to_top "'..'" --param use_frames "'$(FRAMES)'" -o $@ $(XHTMLCONTENT) - proposal/project-summary.html: $(XMLROOT)/proposal/project-summary.xml \ $(XHTMLCONTENT) diff --git a/helm/mowgli/home/xml/news.xml b/helm/mowgli/home/xml/news.xml index 6fb68c5e6..85704fe8d 100644 --- a/helm/mowgli/home/xml/news.xml +++ b/helm/mowgli/home/xml/news.xml @@ -21,7 +21,7 @@ 20020311 - Paul Libbrecht + Paul Libbrecht contributes a much improved PDF file for the MOWGLI proposal in the member area. diff --git a/helm/mowgli/home/xml/proposal/project-management.xml b/helm/mowgli/home/xml/proposal/project-management.xml index 8912bc90d..f7a423bc9 100644 --- a/helm/mowgli/home/xml/proposal/project-management.xml +++ b/helm/mowgli/home/xml/proposal/project-management.xml @@ -1,29 +1,82 @@ - + + + + + + - - - Project Management - - + + - - - - - - -
- Previous Page - - Index - - Next Page -
+ + -
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +]> + + + + + + + + + +
+ Previous Page + + Index + + Next Page +
+
+
+

Project Management

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

@@ -39,69 +92,93 @@
  • Project Exploitation Board
  • Work-package Teams.
  • -
    -
    Project Manager
    -
    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.
    - -
    Exploitation Manager
    -
    S/he will be responsible for coordinating - exploitation activities undertaken by the Project Exploitation Board - (PEB) in close cooperation with the Project Coordination Committee - (PCC).
    - -
    Work-package Leaders
    -
    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
    -
    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).
    - -
    Project Coordination Committee
    -
    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. In view of minimising management overhead - and project costs, partners providing the Project Manager, - and the Work-packages Leaders are required to appoint the same - person as their official representative in the Project - Coordination Committee.
    - -
    Project Exploitation Board
    -
    The PEB will be chaired by the - Project Exploitation Manager, and composed by the Exploitation - Managers of each partner. It will monitor the state of the art in - the domains of content-based information technologies, W3C activities, - Web publishing, and digital libraries. It will be responsible for - planning the dissemination and exploitation strategies for the - consortium, to be approved by the PCC.
    - -
    Work-package Teams
    -
    They are constituted of the technical contributors. - Each team will be chaired by a Work-package Leader, and it will be in - charge of carrying out the technical work described in Section - \ref{Workpackages}.
    -
    - +
    +
    + + + 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 will normally be taken by seeking consensus. However, +

    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 will be sufficient. If the decision being taken + 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. @@ -110,44 +187,44 @@ can initiate the conflict resolution procedure.

    Information Flow

    -

    Information flow within the Project will be ensured by exchange of +

    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 - to be agreed at project start-up. The project Manager will enforce + agreed at project start-up. The project Manager enforces 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.

    -

    The Coordinating Partner will be responsible to prepare and maintain + 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 will be used by the PCC to monitor + 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 will establish a high quality Web site for internal and - external communications. It will be operational as from one month of +

    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 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 + 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 - will be adopted: release by the Work-Package Leader, two-week review + 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 will be defined +

    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 will be two + originated from work in the Project, there are two categories of papers:

    1. Project Endorsed Publications, requiring notification and approval by @@ -157,12 +234,12 @@ project Consortium and, if required by the PCC, a disclaimer that the views are not necessarily those of the Consortium.
    -

    Concerning possible contributions to Standards, they will be +

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

    - -
    - - + + +
    +
    Previous Page @@ -175,6 +252,5 @@
    - - - + +
    diff --git a/helm/mowgli/home/xml/work-packages/work-package.dtd b/helm/mowgli/home/xml/work-packages/work-package.dtd index 723468da5..215bd5218 100644 --- a/helm/mowgli/home/xml/work-packages/work-package.dtd +++ b/helm/mowgli/home/xml/work-packages/work-package.dtd @@ -12,6 +12,8 @@ +