In project are involved following participants:
Poznan Supercomputing and Networking Center (PSNC), Poland
Max Planck Institut feur Gravitationsphysik (AEI), Golm, Germany
Konrad Zuse Zentrum fuer Informationstechnik (ZIB), Berlin, Germany
Masarykova univerzita v Brne (Masaryk University, MU), Brno, Czech Republic
Computer and Automation Research Institute, Hungarian Academy of Sciences (SZTAKI), Budapest, Hungary
Vrije Universiteit (VU), Amsterdam, The Netherlands
Universita' Degli Studi di Lecce (High Performance Computing Center, ISUFI), Lecce, Italy
University of Wales (CARDIFF), Cardiff, Wales, UK
Sun Microsystems Gridware GmbH (GRIDWARE)
Compaq Computer EMEA BV (COMPAQ)
National Technical University of Athens (NTUA), Athens, Greece


Introduction
The work in the GridLab project is split into twelve technical development work packages, one work package for information dissemination and exploitation, and one, WP14 for overall project management. The role of WP14 is to ensure the project's professional management, including careful orchestration and monitoring of work across groups, major project decisions, liaisons with external projects and with the international advisory board, and many more.

The main goal of this WP is daily management of the project, periodic reports to the EU, overall administration and conflict resolution. Within this WP a central repository for tools and source code will be established, which later constitutes the reference for all developers and users. PSNC will provide a dedicated Project Manager and Project Administrative and Financial Coordinator partly funded by the project. This effort will be complemented by an equivalent effort of IT and administrative staff. To help the project manager and the project boards in their task, a project office will be set up to ensure daily monitoring and support of the logistics of the project. Daily communication between all participants will be via electronic mail, keeping time lost travelling and travel expenses to a minimum. The project office will ensure that digests of the email communication between partners are transferred to the Web site providing easily accessible information on the current activities of all partners. The project office will assist in setting common styles for deliverables, web pages and presentations.

Tasks of WP14 Workpackage

1.	Daily management of the project, periodic reports to the EU, overall administration and conflict resolution.
2.	Development of a central repository for tools and source code, which later constitutes the reference for all developers and users.
3.	Controlling: resources, costs, deadlines.
4.	Review the planning of operation, pre- and post-processing of meetings.
5.	Operation, technical: management of development, communication with other partners, quality control: check conformance with specification and standards.
6.	Assessement and Evaluation.

List of deliverables

D14.1 (Report)	Quality Assurance Plan, (Month 3).
D14.2 (Report)	Methodology for quality assurance, (Month 6).
D14.3 (Report)	Quality Assurance Plan, (Month 3).
D14.4-D14.15 (Report)	Commences month 3: Quarterly reports.
D14.16-D14.18 (Report)	Commences month 12: Yearly reports.

Project Management

The GridLab management structure is designed to deal with problems arising in large international collaborative teams. Also, since the project aim and motivation is to provide stable, lasting and usable software and services for scientific user communities, it is essential that the results of the RTD provide industrial quality production services. Such a strategy is essential for future commercial exploitation.




Management Structure

   Project Manager
The project will be managed by the PSNC (WP14), with Dr Jarek Nabrzyski as overall Project Manager. The Project Manager will:

(i)	assemble the initial steering committee, representing the different institutions and workpackages,
(ii)	act as the chairperson of the steering committee,
(iii)	provide day-to-day management, administration and coordination of the project,
(iv)	interface with the CEC,
(v)	coordinate deliverables.

   International Advisory Board
For a project with the proposed scope of GridLab, it is crucial to be fully coordinated and integrated with other large scale Grid projects around the world. We have assembled an independent advisory board comprising of world renowned Grid and HPC experts from around the world to provide guidance and refine directions for the GridLab project. The Advisory Board will attend yearly project meetings, and provide assessments and recommendations to the Steering Committee. The board will include:

(i)	Daniel Reed: Director of the National Center for Supercomputing Applications (NCSA) and the National Computational Science Alliance. In this role Reed is very familiar with the needs of HPC applications, which are a major focus of GridLab. Reed is also involved in the US-funded GrADS project, that share a number of goals with GridLab.
(ii)	Paul Avery: Co-lead of the GriPhyN project, which is one of the largest Grid projects worldwide. Avery will provide valuable advice and will be able to provide research connections between the GriPhyN and GridLab projects.
(iii)	Lennart Johnsson: Director of the Texas Learning and Computation Center, University of Houston and Cullen Professor of Computer Science.
(iv)	Domenico Laforenza: Head of the Advanced Computing Department at the CNUCE, Institute of the Italian National Research Council.
(v)	Thierry Priol: Research Director at Institut National de Recherche en Informatique et en Automatique (INRIA)

   Steering Committee
The executive responsibility for the project will lie with the Steering Committee, who will make major decisions. This committee, initially appointed by the Project Manager who will also chair the committee, will include representatives of each institution and workpackage involved in the GridLab project. To be effective, these representatives should have authority for decision making on behalf of their company or institution. The steering committee will reach decisions by consensus, with conflicts resolved by the Project Manager unless overruled by a two-thirds majority. The Steering Committee will convene twice per year, and by video/phone conferencing every two months, managing contractual matters, overall project strategy, commercialization strategy, and principles for resource allocation. In addition, they will formulate a decision making process for the project, which will ensure smooth running without adversely affecting the working practices of individual research groups.

   Technical Board
The Technical Board, which reports to the Steering Committee, is responsible for the day-to-day coordination and direction of the project, ensuring integrated and interoperable software, implementing quality control, reviewing technical progress, reports and deliverables, maintaining contacts with other projects, and resolving conflicts. The composition of the Technical Board will be decided by the Steering Committee, but will include a Quality Assurance Manager, Testbed Manager and representatives of all workpackages and project leads. The board will meet at least four times a year, in addition to monthly video/phone conferences.

   Dissemination Board
The Dissemination Board coordinates the outreach of the project, concentrating on the distribution and possible commercialization of the resulting software, for example documenting quality and coding requirements. The board will be comprised of representatives from each industrial partner of the project and will meet at least twice a year, reporting directly to the Steering Committee.

   Workpackage Managers
Each workpackage will be assigned a Workpackage Manager by the lead institute. These managers will coordinate with the Technical Board on progress and potential problems and conflicts, and will be responsible for ensuring that the correct information flow and coordination with associated workpackages is maintained.


Information, Planning and Meetings

Bimonthly Progress Reports, detailing status, problems, conflicts and plans, will be produced by all partners and forwarded to the Project Manager. The Project Manager will prepare a Planning Report each six months, in coordination with the Technical Board and Steering Committee. Planning Reports will contain a project wide review and assessment of the monthly reports. At appropriate points, planning reports are forwarded to the CEC and its nominated reviewers. In addition, the Project Manager will maintain regular contacts with Team Leaders and Work Package Managers to ensure that the project work develops as defined in the schedule. The Project Manager will organize general meetings, to be held in Europe, twice a year, which will be open to all members of the project and their associated collaborators.
Bimonthly reports are the internal reports for the Stering Committee meetings, which will take place every two months. The aim of these reports is to keep the Stering Committee informed about the current status of the project. These reports are not related to the quarterly reports for the Commision.
Back to top