STScI Ground System Development Status: WFC3 Wayne Baggett

WFC3 Ground System Development Status Development is on schedule: Phases 1 and 2 are complete (Macro definitions, Initial aperture definitions, Full-frame UVIS ACCUM, darks and bias) Phase 3 in progress (Full-frame IR MULTIACCUM, darks are done, Lamp operations in work) Phase 4 is in detailed planning Proposals with these completed modes can be entered into the system and processed through to command loads (with some caveats)!

WFC3 STScI Phase Development Plan

STScI Front-End Testing Process Each Subsystem (RPS2, TRANS, Commanding) does own Code and Unit Test Component testing conducted by independent test team “End to end” testing conducted by the Flight System Engineering Team (Commanding) via “Certification Proposal” Takes Certification Proposal through RPS2 TRANS SPSS Commanding

STScI Front-End Testing Process (cont.) System Testing (aka “SMS Testing”) done on Ops benches using the Certification Proposal: Tests newly-implemented capabilities and regression tests old capabilities; done at the end of each phase Process proposal through front end systems Generate command load(s) in PASS Load and execute command loads on Ops bench Collect telemetry and science data from execution Process science data through OPUS when possible

Prerequisites for System Testing What’s needed for System Testing to occur: STScI ground system development of capability completed FSW development of capability completed (C&UT) FSW timing measurements done, analyzed, and incorporated into ground system SW/Ops bench available

This requires at least one year between the FSW/Ops bench To mitigate risk to our development schedule, STScI requires System Testing to be performed at least three times prior to SMGT (assumed to be 1 May 2003): Early development of basic capabilities gets more testing Both ground system and FSW are continually improved Ample opportunity to react to problems before SMGT This requires at least one year between the FSW/Ops bench availability and SMGT!

Why System Testing can’t be done now: No recons in Commanding – get transitions done by January 2002 FSW incomplete and slipping – IR detector support not available until 3 May 2002 Ops bench is incomplete Note: SM3B may impact STScI’s availability for about two months

The Ball FSW slip of 17 October 2001 has put less than one year between the availability of FSW for System Testing and SMGT. Limits bench test opportunities and increases risk to the STScI ground system development Mitigated by the inclusion of a new task in Phase 5 to allow for rework – if needed this task will displace another task, impacting the capabilities available for SMGT and launch We need earlier FSW/Ops bench availability, or schedule relief

Constraining dates (based on Ball schedule, 17 Oct 2001): 21 Jan 2002 – Bench with Mechanism simulator available 25 Feb 2002 – Mech Part 1 (Sofa, Shutter, Correctors) C&UT 26 Feb 2002 – Mech Part 3 (Lamps) C&UT 12 Apr 2002 – UVIS Detector C&UT 29 Apr 2002 – Mech Part 2 (CSM, FSM) C&UT 30 Apr 2002 – Service Functions C&UT 3 May 2002 – IR Detector C&UT 1 May 2003 – SMGT