CAP Checklist Date: 03 Nov 2003 CAP#: 894 _ |x| Has the interaction with the load been checked? Yes, No load running, SCS 107 ran. _ |x| Has comm been identified and duration estimated accurately? Yes: first opportunity at 2003:307:19:45 next opportunity at 2003:308:03:45 _ | | If SCS slots are used, is there SCS slot contention? No _ | | Does the CAP perform SCS slot cleanup? _ |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? Depends on which point in the CAP, worst case is right before the re-boot command so that the ACIS Flight SW is not running. If we lose if before re-starting DEA HKP, we have no DEA HKP data until the next pass (we currently have none). _ |x | Does CAP require radmon to be enabled or disabled to be compatible with current load? CAP expect RADMON to be disabled as SCS 107 has executed. _ |x| What is the worst case scenario for the CAP execution? - what science can be lost? No science lost, but if warm reboot fails to bring up proper version of the flight SW, we will need to reload latest ACIS patch to the spacecraft. - 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. SOP 61070 v3.1 2. SOP 61010 v3.1 _ |x| Are all products certified and do SOP and scripts have version 3.0 or higher? Yes _ | | Has OC verified that all required products are available on console? - _ |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 _ | | 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