CAP Checklist Date: __05/05/03__ CAP#: 847 _ |x| Has the interaction with the load been checked? Yes _ |x| Has comm been identified and duration estimated accurately? Yes _ |x| If SCS slots are used, is there SCS slot contention? No _ |x| Does the CAP perform SCS slot cleanup? No, if needed CAP will activate SCS107 _ |x| Does the CAP set the correct format at completion? N/A FMT2 used throughout _ |x| What happens if comm is lost during the CAP execution? If comm is lost, we will not be able to make the proper verifications for obsid 3505 _ |x| Does CAP require radmon to be enabled or disabled to be compatible with current load? CAP assumes RADMON is enabled _ |x| What is the worst case scenario for the CAP execution? - what science can be lost? Observation of Sco X-1 (OBSID 3505) lost - does action generate significant momentum? No - can safe mode be triggered during the CAP? Yes _ |x| List (or attach list) of products that are required (loads, scripts, SOPs). Include version number for scripts and SOPs. 1. (normal Sun mode) 2. 3. _ |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 _ |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? CXC/MIT ACIS teams will be on-console, real-time COMM scheduled for 4pm Thursday May 8, 2003 _ | | Has CAP been reviewed by FD, FOM, SOT lead and OC or their designee? Comments: To be attached to the signed CAP. Rev 1.6, 13 Dec 2001, RJB