CAP Checklist Date: 09 JAN 2004 CAP#: 903 _ |x| Has the interaction with the load been checked? Yes, the JAN1004 SCS107 replan load should be running. _ |x| Has comm been identified and duration estimated accurately? Yes: first opportunity at 2004:010:20:00 - 2004:010:21:00 _ |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 on which point in the CAP. It could mean loss of science or inability to perform SCS cleanup at this COMM. _ |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? - what science can be lost? Can't execute 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_CTI01_138.CLD 2. O_SCSCRTL (V3.4) 3. O_SETOBSID (V3.2) 4. C_SET_FORMAT (V3.3) _ |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? - Yes, as part of this CAP review _ |x| Does the CAP require an OBSID change? Yes, to 62842 _ |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 01/10/04: 3:00 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