Collider shot setup for Run 2 observations and suggestions

This note is intended to provoke discussion on Collider Run II shot setup. We hope this is a start of activities that will converge on a functional description of what is needed for shot setups in Collider Run II. We will draw on observations of the present shot setup to raise questions and make suggestions for the next Collider run. It is assumed that the reader has some familiarity with the Collider operational issues. Shot setup is defined to be the time between the end of a store and the time the Main Control Room declares colliding beams. This is the time between Tevatron clock events SCE and SCB. This definition does not consider the time experiments use to turn on their detectors. This analysis was suggested by David Finley. The operational scenarios for Run II will require higher levels of reliability and speed for shot setup. See Appendix I and II. For example, we estimate that a loss of 3 pb-1/week (with 8 hour stores) will occur if shot setups take 90 minutes instead of 30 minutes. In other words: If you do 12 shots for one week and accept an added delay of one minute in each shot, you will loose more than 60 nb-1 for that week alone (based on a normal shot setup of 30 minutes). These demands should lead us to be much more pedantic about all the factors that affect shot setups. Shot setup will be viewed as a distinct process that is composed of several inter- dependent 'components': procedures, hardware, controls, and sociology. These components don't directly align with the different Accelerator Division departments, but are topical groupings of the needed accelerator functions. Defining these components, and categorizing our suggestions within them, are part of the goal of this document. Of course, some suggestions span several of these components