CAP Checklist                Date: 8 March 2002_______       CAP#: 785____

 _
|x| Has the interaction with the load been checked?
    Yes: ACIS CTI commanding has been removed.
 _
|x| Has comm been identified and duration estimated accurately?
    Yes: 2002:073:12:45 - 2002:073:15: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 at which point in the CAP. It could mean loss of
    science, or inability to reset ACIS DAC levels, or inability to
    execute ACIS-S CTI measurement and perform SCS cleanup at this COMM.
 _
|x| Does CAP require radmon to be enabled or disabled to be compatible
    with current load?  There is no requirement on RADMON, however we 
    expect RADMON to be disabled at the time of CAP execution.
 _
|x| What is the worst case scenario for the CAP execution?
    - what science can be lost?  Can't execute charge injection test, or
				 can't reset DAC values at this COMM, or
				 can't perform ACIS-S 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_WS007_164.CLD
     2.	1A_WS041_252.CLD
     3.	1A_XB000_250.CLD
     4.	1A_XB001_251.CLD
     5.	1A_WB01F_131.CLD
     6.	1A_WB020_132.CLD
     7.	1A_WB021_133.CLD
     8.	1A_WB022_134.CLD
     9.	1A_WB023_135.CLD
    10.	1A_WB024_136.CLD
    11.	1A_WB025_137.CLD
    12.	1A_WB026_138.CLD
    13.	1A_WS046_140.CLD
    14.	1A_WT065_141.CLD
    15.	1A_WS047_142.CLD
    16.	1A_XT000_190.CLD
    17.	1A_RS000_207.CLD
    18.	1A_AA000_191.CLD
    19.	1A_RYFS0_211.CLD
    20.	1A_RZFS0_217.CLD
    21.	1A_CTI02_139.CLD
    22. O_SCSCRTL	(V3.4)
    23. O_SETOBSID	(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: Operations has verified that all of the .CLD files are available.
 _
|x| Does the CAP require an OBSID change?  Yes, to 62852 for CTI
					   measurement.  
 _
|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
    03/14/02: 7:30 AM EST
 _
|x| Has CAP been reviewed by FD, FOM, SOT lead and OC or their designee?
    Yes: CAP review held 8 March 2002 at 9:30 AM EST.

Comments:

None


To be attached to the signed CAP.

Rev 1.6, 13 Dec 2001, RJB