CAP Checklist                Date: 12/14/04               CAP#: 949

 _
|x| Has the interaction with the load been checked?
    Yes, these two ACIS FP temperature commands do not interfere with
    any commands in the load.
 _
|x| Has comm been identified and duration estimated accurately?  
    Yes: opportunity at 2004:349:17:05 - 2004:349:18:05
    Yes: opportunity at 2004:350:20:40 - 2004:350:22:40

 _
|x| If SCS slots are used, is there SCS slot contention?  No.
 _
|x| Does the CAP perform SCS slot cleanup?  
    Yes, the CAP performs immediate SCS cleanup.
 _
|x| Does the CAP set the correct format at completion?  N/A, FMT 1
    is used throughout.
 _
|x| What happens if comm is lost during the CAP execution?
    It depends on which point in the CAP. If before step 2, the 126~C
    command will never be sent.  If after step 2 but before step 3, 
    ACIS will not see the TLM verifier. If after step 3 but before
    step 4, the SCS slot will not be cleared and will need to be
    cleared at the next COM.  A similar logic follows for steps 5-8 in
    which the FP temperature is reset to the operational point.
    There are two COM opportunities after the 2004:350:2040 pass to
    reset the ACIS FP temperature to the operational point before the
    next ACIS science observation.  
  
 _
|x| Does CAP require radmon to be enabled or disabled to be compatible
    with current load?  CAP expects RADMON to be enabled. 

 _
|x| What is the worst case scenario for the CAP execution? The worst
case scenario is that the ACIS FP temperature cannot be reset to the
operational point at the 2004:350:2040 pass.

    - what science can be lost?  CTI measurements done at
      incorrect FP temperature.
    - 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_WS033_249.CLD
    2. 1A_WS032_249.CLD
    3. O_SCSCTRL	(V3.4)
    4. O_PROT_SCSCTRL	(V3.2)

 _
|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, will be done as part of this CAP review
 _
|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?
    Yes, OC/CC, ACIS
    12/15/04: 12:05pm-1:05 pm EST
    12/16/04:  3:40pm-5:40 pm EST
 _
|x| 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