Run Manager (RM) instructions

General remark: The RM is an experienced person who was strongly involved in data taking during the last months and has substantial experience as shift leader. In order to allow for optimal work efficiency as RM, the RM should not have any other on-call duties during or close in time to the period of being actively a RM. For the same reasons, the RM should not be a sub-system run coordinator.The RM is on-duty for a period of 1 week at the time. A pool of 5-10 people is selected to take rotating on-duty periods as RM.

At the start of the shift, after Monday daily meeting

  • Meet with RC/Deputy and previous RM, clarify the current list of open issues, oversee the weekly plan
  • Set up run manager phone 75870: hand-over on-call phone and/or call-forward to appropriate number

During the day:

  • Be present in the control room during critical operational periods, such as shift change, run start preparations, during operational problems, etc.
  • Check regularly the e-log
  • Follow up on issues arising, making sure the issue is sufficiently understood and followed up by an expert. The ATLAS RC/Deputy gets involved on issues that have any long-term impact or an impact on data taking during stable beam.
  • Make a list of items to be followed up on a time-scale longer than a few days, she/he can propose solutions to the ATLAS RC/Deputy.
  • Gather calibration and special run requests that involve (stable) beam time.
  • Answer the Run Coordination on-call phone and provides initial support to shift leaders.
  • The RM can take immediate actions in case of urgent problems with the ATLAS running if the run coordinator is not in the control room. The ATLAS RC/Deputy has to be involved (i.e. called) for any actions/decisions that might have an impact on the stable beam time data taking. Changes of the ATLAS daily run plan that involve stable beam time always need to be discussed with the ATLAS RC/Deputy.

Daily run meeting:

  • 5 minutes before the meeting: switch on projector, TV screen, start EVO, load daily agenda
  • Present a short report, which includes:
    • Summary of the various ATLAS activities in the past 24 hours, including incidences, problems, issues and their follow-up. Where possible, please add a link to the corresponding e-log entry.
    • List of issues from past days and the status of their follow-up

  • The ATLAS RC/Deputy (who attends the daily LHC meeting) reports the daily LHC plan during the ATLAS daily run meeting. After that, and after any input of the sub-system run coordinators, the ATLAS daily run plan is discussed and established, the RM writes down the daily run plan during the meeting, posts it (elog, yellow post-its in the ACR) and communicates/explains it to the shift leader after the meeting.

After the shift:

  • After the Monday daily meeting, hand-over to the next RM
  • It is normally expected that the RM makes a short presentation on Run Coordination matters in the ATLAS Weekly Meeting on the Tuesday after the run manager shift.
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2011-04-13 - ThiloPauly
 
    • 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