CAP Checklist Date: 12/09/06 CAP#: 1019 _ |X| Has the interaction with the load been checked? Yes, there should be NO load running and there should be NO maneuver load on-board the spacecraft. _ |X| Has comm been identified and duration estimated accurately? Yes: opportunity at 2006:343:19:10:00 - 2006:343:19:55:00 _ |X| If SCS slots are used, is there SCS slot contention? No. _ |X| Does the CAP perform SCS slot cleanup? It depends if the CAP is interrupted or if it runs to completion: * If this CAP is interrupted by a science resumption load, that load will terminate, clear and disable SCS 131. * If this CAP runs to completion, the OC/CC will need to disable and clear SCS 131 at the first COMM opportunity. _ |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. If it occurs after Step 5 but before Step 8 (the primary step in the CAP), it could produce an unnecessary SIM translation when the radiation rates get high near perigee. Comm loss before Step 5 and after Step 8 has no effect. _ |X| Does CAP require radmon to be enabled or disabled to be compatible with current load? CAP expects RADMON to be disabled at COMM start; will be enabled by this CAP if executed. _ |X| What is the worst case scenario for the CAP execution? If the wrong CTI_RTS is chosen, with too long a delay time, ACIS CCDs could be clocking in the belts until the commands in this SCS terminate the science run or perhaps until one of the SCS107 triggers is reached if RADMON is still enabled. Otherwise, the worst case scenario is that the science resumption load is built incorrectly such that it does not contain the commands to terminate and clear SCS 131. The first set of ACIS commands in the load could then cause the back-end processor to crash. If SCS 131 is still active and a new science run is started in the load, ACIS CTI commanding may interfere with the science run in that load (could prematurely end a science run). - what science can be lost? Can't execute CTI measurement or science runs after a BEP crash are lost until the BEP is rebooted. - 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_CTI_16HR_131.CLD 2. O_SCSCTRL (V3.4) 3. O_PROT_SCSCTRL (V3.2) 4. O_SETOBSID (V3.2) 5. C_SET_FORMAT (V3.3) _ |X| Are all products certified and do SOP and scripts have version 3.0 or higher? _ | | 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? Yes, to 62818 _ |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 2006:343:19:10 - 2006:343:19:55, 14:10-14:55 local time _ | | 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