Difference between revisions of "ShiftLeader"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
** any major events, including accesses | ** any major events, including accesses | ||
| − | *Post Snapshots of important information at least twice a shift. | + | *Post Snapshots of important information at <B> least </B> twice a shift. |
** Include- Hall A tools, BPM strip-charts, and BCM strip-charts. | ** Include- Hall A tools, BPM strip-charts, and BCM strip-charts. | ||
** Include any snap shots of the details after a change. | ** Include any snap shots of the details after a change. | ||
| + | ** Please feel free to post these Snapshots more often. | ||
Revision as of 12:10, 17 July 2017
In the process of editing and updating this page. Please contact any of the Tritium Students for suggestions, ideas, help, or etc.
Shift Leader Responsibilities
- Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the HALOG
- Keep track of beam time accounting
- Learn how to keep track of the BTA with the BTA how-to.
- Consult the daily run plans and communicate with run coordinator whenever problems happen that cannot be solved by shift workers.
- Maintain data taking quality and an efficient use of beam time.
- Follow the directives in the COO
- Log the following in a shift summary in the HALOG:
- run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers
- any major events, including accesses
- Post Snapshots of important information at least twice a shift.
- Include- Hall A tools, BPM strip-charts, and BCM strip-charts.
- Include any snap shots of the details after a change.
- Please feel free to post these Snapshots more often.