CAP Checklist                Date: 25 January 2002               CAP#: 774

 _
|x| Has the interaction with the load been checked? 
    Yes.
 _
|x| Has comm been identified and duration estimated accurately?  Yes
 _
|x| If SCS slots are used, is there SCS slot contention?  No
 _
|x| Does the CAP perform SCS slot cleanup?  Yes
 _
|x| Does the CAP set the correct format at completion?  N/A, FMT 2
    is used throughout.
 _
|x| What happens if comm is lost during the CAP execution?
    It depends on which point in the CAP. It could mean loss of
    science or inability to perform SCS cleanup at this COMM.
 _
|x| Does CAP require radmon to be enabled or disabled to be compatible
    with current load?  CAP assumes RADMON is disabled.
 _
|x| What is the worst case scenario for the CAP execution?
    - what science can be lost? Can't restart any science run.
				
    - does action generate significant momentum?  No
    - can safe mode be triggered during the CAP?  No
 _
|x| List (or attach list) of products that are required (loads,
    scripts, SOPs). Include version number for scripts and SOPs.
    1. 1A_WS003_165.CLD 
    2. 1A_WS000_203.CLD
    3. 1A_RS000_207.CLD
    4. 1A_RH000_151.CLD
    5. I_1_SET_RAD_FLAG.ssc  (V3.1)
 _
|x| Are all products certified and do SOP and scripts have version 3.0
    or higher?  Yes
 _
|x| Has OC verified that all required products are available on console?  Yes
 _
|x| Does the CAP require an OBSID change?  Yes: 62854
 _
|x| Who will be on-console and is the CAP being run at a reasonable time?
    OC/CC, ACIS, yes (9:05-11:15 local)
 _
|_| Has CAP been reviewed by FD, FOM, SOT lead and OC or their designee?


Comments:

None


To be attached to the signed CAP.

Rev 1.5, 12 Apr 2001, RJB