CAP Checklist                Date: 30 May 2003               CAP#: 851

 _
|x| Has the interaction with the load been checked?
    Yes, MAY3103 SCS107 replan load should be running.
 _
|x| Has comm been identified and duration estimated accurately?  
    Yes: 2003:150:22:00 - 2003:151:00:30
 _
|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 expects RADMON to be enabled by the load.
 _
|x| What is the worst case scenario for the CAP execution?
    - what science can be lost?  Can't execute CTI measurement or
				 can't perform SCS slot clean-up.

    - 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_CTI01_138.CLD
    2. O_SCSCRTL	(V3.4)
    3. O_SETOBSID	(V3.2)
    4. C_SET_FORMAT	(V3.3)
 _
|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, to 62847

 _
|x| If a Flight Software Patch, has the checkbook checksum been compared
    with the value in the CAP? N/A

 _
|x| Who will be on-console and is the CAP being run at a reasonable time?
    Yes, OC/CC, ACIS
    05/30/03: 6:00 PM EDT
 _
|_| 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.6, 13 Dec 2001, RJB