CAP Checklist                Date: __07/17/03__           CAP#: 847

 _
|x| Has the interaction with the load been checked? Yes, commanding
 to stop the loads may be needed.

 _
|x| Has comm been identified and duration estimated accurately?  Yes 
    2003:201:20:30 - 2003:201:22:00; 2003:202:02:30 - 2003:202:05:30

 _
|x| If SCS slots are used, is there SCS slot contention? No

 _
|x| Does the CAP perform SCS slot cleanup? No, if needed CAP will
activate SCS107

 _
|x| Does the CAP set the correct format at completion? N/A FMT2 used 
    throughout

 _
|x| What happens if comm is lost during the CAP execution?
    If comm is lost, we will not be able to make the proper 
    verifications for obsid 3505

 _
|x| Does CAP require radmon to be enabled or disabled to be compatible
    with current load? CAP assumes RADMON is enabled

 _
|x| What is the worst case scenario for the CAP execution?
   loss of science time due to load termination
    - what science can be lost?  If SCS107 or normal Sun mode are
activated, all science will be lost until loads are resumed. 
    - 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. O_PROT_SCSCTRL (V3.2)

 _
|x| Are all products certified and do SOP and scripts have version 3.1
    or higher? Yes

 _
|x| Has OC verified that all required products are available on console? Yes

 _
|x| Does the CAP require an OBSID change? No
 
 _
|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?
    CXC/MIT ACIS teams will be on-console
    07/21/03: 12:30 AM EDT
 _
| | Has CAP been reviewed by FD, FOM, SOT lead and OC or their designee?


Comments:




To be attached to the signed CAP.

Rev 1.6, 13 Dec 2001, RJB