LCG Project Structure  
 
 
 
 
   

 

 

 

Collaboration Board (CB)

  • The Collaboration Board (CB) provides the main technical direction for LCG. The CB is composed of a representative of each Institution or federation of Institutions that is a member of the Collaboration, the LCG Project Leader and the Spokespersons of each LHC Experiment, with voting rights; and the CERN Chief Scientific Officer (CSO), and CERN/IT and CERN/PH Department Heads, as ex-officio members without voting rights, as well as a Scientific Secretary. The CB elects the Chairperson of the CB from among its Members. The CB meets annually and at other times as required.

Overview Board (OB)

  • A standing committee of the CB, the Overview Board (OB), has the role of overseeing the functioning of the Collaboration. It also acts as a clearing-house for conflicts that may arise within the Collaboration. The OB is chaired by the CERN CSO. Its other members include one person appointed by the agency/agencies that funds/fund each of the Tier-1 centres, the Spokespersons of the LHC Experiments, the LCG Project Leader, the CERN/IT and CERN/PH Department Heads, and a Scientific Secretary. It meets about four times per year.

    Both the CB and the OB may co-opt additional non-voting members as they deem necessary. The non-voting members complement the regular members by advising on, for example, matters concerning the environment in which the Collaboration operates or specialist aspects within their areas of expertise.

Management Board (MB)

  • The work of the Collaboration is organized and managed as the LHC Computing Grid Project. The Management Board (MB) supervises the work of the Project. It is chaired by the LCG Project Leader and reports to the OB. The MB organizes the work of the Project as a set of formal activities. It maintains the overall programme of work and all other planning data necessary to ensure the smooth execution of the work of the Project. It provides quarterly progress and status reports to the OB. The MB endeavours to work by consensus but, if this is not achieved, the LCG Project Leader shall make decisions taking into account the advice of the Board. The MB membership includes the LCG Project Leader, the Technical Heads of the Tier-0 and Tier-1 centres, the leaders of the major activities managed by the Board, the Computing Co-ordinator of each LHC Experiment, the Chair of the Grid Deployment Board (GDB), a Scientific Secretary and other members as decided from time to time by the Board.

Grid Deployment Board (GDB)

  • The Grid Deployment Board (GDB) is the forum within the Project where the computing managements of the experiments and the regional computing centres discuss and take, or prepare, the decisions necessary for planning, deploying, and operating the LHC Computing Grid. Its membership includes: as voting members - one person from each country with a regional computing centre providing resources to an LHC experiment (usually a senior manager from the largest such centre in the country), a representative of each of the experiments; as non-voting members - the Computing Co-ordinators of the experiments, the LCG Project Leader, and leaders of formal activities and projects of the Collaboration. The Chair of the GDB is elected by the voting members of the board for a two-year term. The GDB may co-opt additional non-voting members as it deems necessary. The GDB reports to the LCG Management Board.

Architects Forum (AF)

  • An Architects Forum (AF) consisting of the Applications Area Manager (chair), the software architects of the four LHC experiments, the leaders of the various AA software projects and other invited members provides for the formal participation of the experiments in the planning, decision-making and architectural and technical direction of applications area activities. Architects represent the interests of their experiment and contribute their expertise. The AF meets every two weeks and makes decisions about the difficult issues that cannot be resolved in open forums such as the Applications Area meeting. The Applications Area Meeting takes pace fortnightly and provides a forum for information exchange between the project and the LHC experiments.

The activities of the project are organised as a number of sub-projects or Areas

Applications Area

  • Provide the tools and infrastructure for physics application software development
  • Organise sub-projects to implement the common solutions identified by the SC2

Applications Area Meetings
Discussion and consultation
Open membership

Fabric Area

  • Responsible for organizing the LHC computing services at CERN
  • Responsible for the architecture of the T0 and CAF installations
  • Responsible for Data Challenges to verify the scalability and performance of the architecture
  • Sharing technical information with systems administration experts at other regional centers
  • Regular re-evaluation of evolving technologies in areas such as fabric management, storage and computation
  • Regular re-assessment of the cost of the LHC computing facility

Grid Deployment Area

  • Organise and operate the pilot global grid service for LHC
  • Coordinate with regional centre managers and with the production managers from the experiments
  • Build and certify a distribution package for installation at regional centres
  • Operate the grid infrastructure (information services, registration services, call centre, operations centre, user consultancy and support)


    The Grid Deployment Area has several standing committees to coordinate different aspects of its work.
Security Group
Proposals for security strategy, policy and planning
Membership: security experts, chair David Kelsey/RAL
 
 
LCG Operations Team
Day-to-day operational decisions
Membership: one person from each site

The manager of the grid deployment area also serves as the Operations Manager of the EGEE project, ensuring a very close integration of the services deployed by these projects.

Distributed Analysis & Grid Support (formerly ARDA)

This area is responsible for working with teams within the experiments, helping them to interface to grid services and coordinating between the experiments, the middleware developers and regional centres involved in distributed analysis prototyping.