ATLAS Organisation - Description of appointments

Organization.png



You will find here a brief overview of the ATLAS organisation. More details exist on the role of the Spokesperson, the Executive Board and the Collaboration Board in the ATLAS Organisation document. The Spokesperson electoral process is described in this document. Details are also provided in the original MoU.

ATLAS Management

Spokesperson

  • The Spokesperson is the highest level executive of ATLAS, and as such has the overall responsibility of the execution and day-to-day organisation of ATLAS. The Spokesperson represents the ATLAS executive branch at the Collaboration Board and speaks on behalf of the Collaboration to the LHC Committee, to the CERN Management, and to the outside world.
  • The Spokesperson is elected by the Collaboration Board, after a nomination of candidates by, and in due consultation with, the Collaboration. ATLAS normally has one Spokesperson. However, the Collaboration Board can also decide, with a 2/3 majority, to elect two Spokespersons. The term of office is 2 years, renewable once with a 2/3 majority. The appointment is made in consultation with the CERN Management.
  • Current Spokesperson.

Deputy Spokesperson

  • The Spokesperson may nominate one or two Deputies, who are elected by the Collaboration Board for the duration of the term of office of the Spokesperson. The responsibilities of the Deputy Spokesperson(s) are defined by the Spokesperson.
  • Current Deputy Spokesperson(s).

Technical Coordinator

  • The Technical Coordinator monitors the overall technical aspects of the detector, the experimental area, and common project issues, and typically deals with safety, ATLAS infrastructure at CERN, surface and experimental areas, services, installation, machine interface, and test beams.
  • The Technical Coordinator is CERN staff. The appointment is proposed by the Spokesperson, endorsed by the Collaboartion Board, and is made in in agreement with the CERN Management.
  • Current Technical Coordinator.

Resource Coordinator

  • The Resource Coordinator monitors and manages the financial and human resources of the collaboration and will typically deal with budget planning, human resources planning, Memoranda of Understanding, and the Common Fund.
  • The Resource Coordinator is CERN staff. The appointment is proposed by the Spokesperson, endorsed by the Collaboartion Board, and made in in agreement with the CERN Management.
  • Current Resource Coordinator.

Upgrade Coordinator

  • The Upgrade Coordinator ensures that the upgrade programme is well-defined, well-matched to the physics goals, and proceeding well. The Upgrade Coordinator is responsible for reporting on upgrade activities to the Executive Board, and for ensuring that Upgrade Project Leaders are informed of Executive-Board matters that impact on the Upgrade Projects. The Spokesperson and the Upgrade Coordinator work closely together in preparing upgrade-related interactions with the CERN LHCC and related review committees.
  • The Upgrade Coordinator is elected/endorsed by the Collaboration Board from candidate(s) proposed by the Spokesperson. In the selection, the Spokesperson will be assisted by a search committee, and will call for nominations and feedback from the Collaboration. The term of office is for two years, renewable. The Upgrade Coordinator may be part of the ATLAS Management team, depending on the phase of the upgrade programme; it is currently is the case.
  • Details about the ATLAS Upgrade organisation structure.
  • Current Upgrade Coordinator.

ATLAS Executive Board

  • The Executive Board directs the execution of the ATLAS project, in line with the policies set by the Collaboration Board.The Executive Board brings together the Activity Coordinators/Project Leaders responsible for the ATLAS operation and physics exploitation, and additional members at large, with a view to the overall performance of the experiment. The Executive Board is chaired by the Spokesperson and the Technical Coordinator serves as deputy chairperson. The members of the Executive Board are elected for a period of office of two years, renewable with a 2/3 majority. See also EB twiki.

ATLAS Collaboration Board

  • The Collaboration Board is the policy and decision-making body of the ATLAS Collaboration. More details here.
  • The Deputy Chair of the Collaboration Board is elected by the Collaboration Board. After the first year of office, the Deputy become the Chair. After the end of the Chair's term of office (two years not renewable), the Chair serves for another year as Deputy. See CB twiki.
  • The Chair may nominate an advisory group (current composition here), the members of which will be elected by the Collaboration Board upon proposal of the Chair for the duration of the Chair's term.

ATLAS Projects

  • A System Project Leader is responsible to the ATLAS Collaboration for ensuring that the operation of the corresponding System is carried out in a way that ensures the required performance and long-term reliability. Project Leaders manage the operation and maintenance of their system. More details about the role of Project Leaders.
  • The Project-Leader election starts by forming a search committee of the Institute Board that calls for nominations from the community. This committee presents a short list of Project-Leader candidates to the Institute Board, after consulting with the (sub)system community and the ATLAS Management. The appointment is for two years with the possible extension according to the ATLAS organisation rules.
  • Inner Detector (ID) Project Leader.
  • LAr Calorimeter Project Leader.
  • Tile Calorimeter Project Leader.
  • Muon Instrumentation Project Leader.
  • Forward Detectors Project Leader.
  • Trigger/DAQ Project Leader.
  • ITk Project Leader.

ATLAS Activities

  • Details of the activity areas.
  • The shortlists of candidate Coordinators of the Trigger, Computing, Data Preparation, and Physics Coordination areas are proposed by the Spokesperson. The Spokesperson is assisted by a search committee, and makes a call for nominations and feedback from the Collaboration. The Coordinators are elected by the Collaboration Board. The mandate of the Coordinators is for two years, renewable. In the case of the Physics Coordinator, two consecutive mandates are not allowed.
  • Trigger Coordination
    • This area of responsibility covers all trigger (LVL1 and HLT) performance issues. More details here.
    • Current Coordinator.
  • Computing Coordination
    • This area of responsibility covers operation of the offline computing, development and maintenance of the core Software, and overall technical coordination and integration of the core and non-core Software. More details here.
    • Current Coordinator.
  • Data Preparation Coordination
    • This area of responsibility covers data analysis after the data arrive at the Tier0, and of the corresponding aspects for the simulated events: offline data quality and data treatment; reconstruction, calibration and alignment at the (sub)-detector level; and first combined reconstruction of physics objects by bringing together the information of various sub-detectors, and use of these objects to align and calibrate the various sub-detectors. More details here.
    • Current Coordinator.
  • Physics Coordination
    • This area of responsibility covers the more refined reconstruction of physics objects, and the development of reconstruction algorithms optimised for different physics channels. It also covers global performance issues, such as the determination of the absolute energy scales of the experiment. Another aspect under the responsibility of Physics Coordination is the extraction of physics analysis results. More details here.
    • Current Coordinator.
  • Run Coordination
    • The Run Coordinator is formally delegated from the Technical Coordinator to perform some of the technical responsibilities related to daily operation during data taking.
    • The shortlist of candidate Run Coordinators is proposed by the Spokesperson and the Technical Coordinator. They are assisted by a search committee, and make a call for nominations and feedback from the Collaboration. The Run Coordinator is endorsed by the Collaboration Board. A given Run Coordinator is not expected to be in charge for more than one or two (at most) run periods (i.e. yearly machine operation time).
    • Current Coordinator.
  • Publication Committee
    • The Publication Committee Chair is responsible for ensuring that the ATLAS publications are of high scientific and formal standard, overseeing the preparation of ATLAS publications, participating in the release of proceedings, identifying suitable journals for ATLAS publications and ensuring that the ATLAS guidelines and publication policy are followed. More details here. See also the Publication Policy.
    • The Publication Committee consists of 10 members, each member serving for two years, and in addition a Chair and a Deputy Chair.The Deputy Chair is elected every two years by the Collaboration Board following a normal ATLAS election procedure; the shortlist of candidate Deputy Publication Committee Chairs is proposed by the Collaboration Board Chair. The CB chair is assisted by a search committee, and makes a call for nominations and feedback from the Collaboration. In the second year of the mandate, the Deputy becomes Chair of the Committee.
    • Current Chair.

LHC Resources Review Boards (RRB)

  • The RRB comprises the representatives of each experiment's Funding Agencies and the Managements of CERN and of each experimental Collaboration. It is chaired by the CERN Director for Research and Computing. More info here.

-- ManuellaVincter - 2020-03-09

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng Organization.png r1 manage 70.8 K 2020-03-09 - 08:32 ManuellaVincter  
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2020-03-12 - ManuellaVincter
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback