1. FORCAST Line Operation #1 Pasquale Temi NASA-Ames

2. “Observatory Level” Line-ops FORCAST Line-ops #1 is the first activity that involve an integrated test and a characterization plan at the Observatory Level It is indeed our first chance to test on ground the Observatory as an integrated system FORCAST Line-ops #1 will contain Observatory elements that have not been formally verified. This Line ops represents an opportunity to perform planned tests that would establish the readiness of the various Observatory elements to proceed. For MCCS, it will represent the first time that significant new functionality has been integrated with aircraft and Telescope Assembly (TA) hardware and software. For the Science Instrument, it will also represent the first time that FORCAST software is integrated with MCCS software while controlling the SI hardware mounted on the TA

3. “Observatory Level” Line-ops Objectives Determine to what extent the combined TA-MCCS-FORCAST integrated Observatory is ready for conducting the Short Science flight series #1. Enable the Science Instrument development team and Mission Operation team to assess the current capabilities of the Observatory for executing the science operations, in preparation for Short Science flight Series #1 System evaluation will be performed to ensure that system functions in the expected manner when placed in the intended environment.

4. Segment 2 – Tracking dates TA ActivationFCF 2009 2010 Science Flight Platform Flight TA Flight Ground Testing Data Analysis Contingency Flight ISF FRR #3 AFSRB

5. Assumptions and Approach Line Op Definition: – FORCAST Line Op #1 is an Observatory-level evaluation for SS1 and a risk-reduction activity FORCAST Line Op #1 is not formal V&V “for credit” Subsystems are not in formal SS1 configuration Observatory Configuration and Line Op Entrance Criteria: – MCCS (incl. EB4), TA, FORCAST are “SS1-like” – Detailed entrance criteria and configuration prerequisites are given in the Plan and in forthcoming Test Procedures – Assume subsystem verifications, respective ICD verifications, and PCA results are already available before onset of Line Op Requirements – Tests are against Observatory-level requirements of ES Level B and of SE01-013 (down-selected for ES)

6. Acceptance and Approvals: – Plans, Procedures, and Test Results will be placed under CM and all accepted by SOFIA Program Chief Engineer – Detailed test procedures, available before TRR – Any PRs will be submitted to Program Chief Engineer; Corrective Action/Deviation/Waiver will be in accordance with Program process Coordination: – Pasquale Temi is lead and POC – On-aircraft tests will be coordinated between Science, Platform Engineering, and Aircraft Ops, in accordance with June 23, 2009 memo, “Coordinating Test Activities Onboard the SOFIA Aircraft” – Ongoing weekly planning meetings with TA, MCCS, FORCAST and Ops representatives – Final coordination is through Program Integration IPT Assumptions and Approach

7. Observatory Level Line-ops Structure SOFIA Observatory Integration Test Plan for Line-ops #1 Cavity Door System Telescope Assembly Science Instrument FORCAST MCCS Line Operations #1 test is conducted at the Observatory level, with the Platform Systems configuration very close to the Short Science #1 configuration, and with FORCAST integrated with the TA and MCCS subsystems. Short Science Configuration. Power distribution available at SI rack, rack patch panel and TA patch panel SW at Engineering Build 4; all other subsystems at Short Science Configuration Cavity door and TA aperture fully operational under MCCS control Short Science #1 Configuration Fully operational TA, balanced with FORCAST installed; Inertial stabilization Mode Available; Tracker available on all three images; SMA fully functional Requires Support from: TA operators, FORCAST operators, MCCS operators, Mission Ops support, Aircraft Ops support

8. Test Plan - Structure Approach 1)List of requirements needed for ES (from Level B and -013) 2)Identify the appropriate (series of) test associated to each requirement 3)Identify SI flight scenarios 4)Identify Mission Ops. flight scenarios 5)Write test Plan & Test Procedures 6)Prioritize the list Observatory check out and ICD functional check will asses if each subsystem is ready for integration prior to line operations Test Plan fields: Configuration/Environment: Prerequisites: Test Description: Exit Criteria: Personnel Requirement: Estimated duration: Requirements:

9. Prerequisites MCCS 1.MCCS at Engineering Build 4 2.MCCS (EB4)-FORCAST SIL Test Completed 3.Surrogate Data Acquisition System operational 4.Platform and Experimenters Networks configured 5.NTP and IRIG-B operational 6.TO and MD Workstations operational 7.MADS audio data stored and available for transfer 8.MCCS TAIPS data stored and available for transfer 9.MCCS Workstation and PIS data stored and available for transfer 10.MCCS Housekeeping stored and available for transfer 11.Science Transfer System available for connection to Experimenter Network 12.Science Data Cache and Network available for data migration activities Cavity door and TA aperture fully operational under MCCS control

10. Prerequisites - TA & SI TA Prerequisites: 1.Short Science #1 Configuration 2.Fully operational TA, balanced with FORCAST installed; 3.Conical reflective secondary mirror button installed 4.Inertial stabilization Mode Available; 5.Tracker available on all three imagers; 6.SMA fully functional (will have already been verified to move reliably and repeatably through their whole range. Chopping performance will have already been thoroughly tested in the hangar using the LabView oscilloscope equipment). SI Prerequisites: 1.FORCAST fully operation in Short Science Configuration mounted on the instrument flange 2.Power distribution available at SI rack, rack patch panel and TA patch panel 3.Access to the backend of SI instrument 4.Install and remove FORCAST calibration Box

11. “Observatory Level” Line-ops – TA Tests 5.2 TA Tests 5.2.1 Basic Controllability and Housekeeping Evaluation 5.2.2 TA Gyro Alignment and Quasi-static Flexible Body Compensation Check 5.2.3 Off-Axis Pointing Accuracy Check 5.2.4 TA Gyro Drift Check 5.2.5 Coarse Drive Coupled Mode Evaluation

12. MCCS Centric Test Cases TestAuthorsDurNotes Scen 0 – 1 st PointingA. Meyer3Night, door open, on tarmac Initialization of Sky to TA coord (ERF to IRF) Scen 1 – Setup SI Boresight R. Grashuis2Night, door open, on tarmac Alignment of SI Ref Frame to TA (SIRF to IRF) Scen 3 – Unchopped Nods R. Grashuis1Night, door open, on tarmac Nodding between defined beams (for SS1, simple moves via goto) Scen 4 – ROF Update A.Meyer3Night, door open, on tarmac Prediction of time remaining and rewind of the Line of Sight to maximize time where Rotation of Field remains frozen during observations Scen 5 – Chopper Setup S. Adams4Night, door open, on tarmac 2-pt chop @ various freq., throws, offsets, angles Scen 6 – Chop & NodS. Adams3Night, door open, on tarmac Nodding and chopping Coordinated MotionW. Miller?6Night, door open, on tarmac Tracking aperture position relative to TA position Prerequisites - TA & SI  Tests with dependencies on night operations

13. MCCS Centric Test Cases Prerequisites - TA & SI  Tests with no dependencies on night operations  Some tests are not MCCS per se; however, they deal with transfer and ingestion of MCCS of data into the DCS TestAuthorsDurNotes AdministrativeE. Moore/J. Rasmussen 2No constraint (hangar/tarmac, door open/closed, day/night) MCCS login, print, receive images, print, etc. Data TransferN. Callis3No constraint (hangar/tarmac, door open/closed, day/night) Transfer of SI, MCCS, data to Transfer System Data IngestionR. Shuping2No constraint (hangar/tarmac, door open/closed, day/night) Archival from Transfer System into DCS Export from DCS

14. MCCS Test Case Sequencing Test Case Sequencing 14 Administrative Scenario 0 Scenario 1 Scenario 5 Scenario 4 Coordinated Motion Data Transfer Data Ingestion Scenario 3 Scenario 3 may be optional - it involves nodding, which for SS1/EB4, should only be TA positioning using standard ta_pos.goto, which is tested in Scenario 0, although not in application of nodding concepts No constraint on night, door, or tarmac On sky at night, door open

15. “Observatory Level” Line-ops – SI Tests 5.3 SI Tests 5.3.1 FOR-HO-1: INF Pressure Test 5.3.2 FOR-HO-2: Grounding Scheme Checkout 5.3.3 FOR-HO-3: SMA Interface 5.3.4 FOR-LO-1: Alignment of FORCAST to TA 5.3.5 FOR-LO-2: SMA Focus 5.3.6 FOR-LO-2a:Occulting Masks Test 5.3.7 FOR-LO-3: Ground Bore Sight Determination 5.3.8 FOR-LO-4: TA Emissivity 5.3.9 FOR-LO-5: Chop and Nod Settle Times; Image Quality 5.3.10 FOR-LO-6: Optimum Chop Frequency 5.3.11 FOR-LO-7: Plate Scale 5.3.12 FOR-LO-8: Asymmetric Chop 5.3.13 FOR-LO-9: Pointing Stability 5.3.14 FOR-LO-10: Header Population for Acquired Data 5.3.15 FOR-LO-11: Data Reduction Pipeline Verification for C2N and C2ND Modes

16. “Observatory Level” Line-ops – Operational Tests  5.4 Operational Tests (Simulated Flight Operational Scenarios: FORCAST operational scenarios integrated with OPS SIM #8 flight simulations) 5.4.1 FOR-LO-13: Flight Scenario for Determining Frame 5.4.2 FOR-LO-14: Flight Scenario for Focus Determination 5.4.3 FOR-LO-15: Flight Scenario of Standard Star 5.4.4 FOR-LO-16: Flight Scenario for Science Object (standard chop and nod off source) 5.4.5 FOR-LO-17: Flight Scenario for Science Object (scan mode) - Waived - MCCS functionality not available until GREAT line ops 5.4.6 FOR-LO-18: Flight Scenario for Science Object (quick step and stare mode)  Flight Plan with three legs will be generated, incorporating FORCAST scenarios Briefed at pre-flight briefing Implemented on day one as part of the SIM #8 simulated flight

17. Test Sequence Test #Test DescriptionGroupLocationDurationParallel# days# nightsPrerequisites DAY 1 - TA Hangar tests 1 5.2.1Basic controllability and HK evalTAHangar4 Needs MCCS h&s/w & TA configured 5.2.5CD coupled mode evalTAHangar2 Needs TA 5.2.1 Total Hours 6 DAY 2 - SI & MCCS Hangar tests 1 5.1.1Admin test caseMCCSHangar2 Needs MCCS h&s/w & TA configured 5.1.9data transferMCCSHangar3yes 5.3.1INF pressure testHO-1Hangar-3yes Needs FORCAST installed 5.3.2Grounding scheme checkHO-2Hangar4 Needs FORCAST installed 5.3.3SMA interfaceHO-3Hangar1 Needs SMA checkout complete Total Hours 7 NIGHT 1 - CDDS & SI tests 1 5.3.4Alignment of FORCAST to TA (pupil)LO-1Line2 Needs FORCAST hangar tests complete 5.3.6Occulting Masks TestLO-2aLine2 Needs pupil imaging 5.1.10MCCS-TA-CDDS coordinated motionMCCSLine6 Needs pupil imaging Total Hours 10 NIGHT 2 - TA & SI tests 1 5.2.2TA Gyro alignment and QS FBC checkTALine1 Needs TA 5.2.1 5.2.3off axis pointing accuracy checkTALine1 Needs TA 5.2.1 5.2.4TA gyro drift checkTALine1 Needs TA 5.2.1 5.3.5SMA FOCUS (unchopped)LO-2Line2 Needs FOR-LO-1 5.3.7Ground Boresight determinationLO-3Line4 Needs FOR-LO-2 Total Hours 9 NIGHT 3 - MCCS tests 1 5.1.2scenario 0 - First PointingMCCSLine3 Needs TA, CDDS, basic SI complete 5.1.3scenario 1- Set up SI BoresightMCCSLine2 Needs scenario 0 5.1.4scenario 3 - Unchopped noddingMCCSLine1 Needs scenario 1 Total Hours 6 NIGHT 4 - MCCS tests 1 5.1.5scenario 4 - ROF updateMCCSLine3 Needs scenario 1 5.1.6scenario 5 - Chopper SetupMCCSLine4 Needs scenario 1 Total Hours 7

18. Time line NIGHT 5 - SI tests 1 5.3.9chop & nod settle times, IQLO-5Line4 Needs Scenario 3 & 5 5.3.10optimum chop frequencyLO-6Line2 Needs Scenario 5 5.3.12asymmetric chopL0-8Line2 Needs Scenario 5 8 DAY 6 - Ops Sim 1 5.4.7pre-flightOpsHangar4yes day shift on day of flight sim Total Hours 4 NIGHT 6 - Ops Sim 1 5.4.8flight simulation - night 1OpsLine6 Needs TA, CDDS, MCCS and some SI complete In-Flight Frame ratesLO-13flight 1 yes In flight Focus (chopped)LO-14flight 1 yes In flight std star obsLO-15flight 1 yes In flight science object obsLO-16flgiht 1 yes In flight quick step obsLO-18flight 1 yes Total Hours 6 DAY 7 - Ops Sim & MCCS tests 1 5.4.10post flightOpsHangar1yes day shift on day after flight sim 5.1.8data ingestionMCCSHangar2yes 5.1.9data transferMCCSHangar3yes Total Hours 6 NIGHT 7 - SI tests 1 5.3.11plate scaleLO-7Line2 Needs FOR-LO-3, 5 & 6 5.3.13pointing stabilityLO-9Line2 Needs FOR-LO-2 5.3.8TA emissivityLO-4Line4 Needs CDDS complete 5.3.14header populationL0-10Line yes 5.3.15data reduction pipeline verificationLO-11Line yes Total Hours 8 Test #Test DescriptionGroupLocationDurationParallel# days# nightsPrerequisites

19. Time line DAY 8 - Ops Sim 1 5.4.7pre-flightOpsHangar4yes day shift on day of flight sim Total Hours 4 NIGHT 8 - Ops Sim 1 5.4.9flight simulation - night 2OpsLine6 In-Flight Frame ratesLO-13flight 2 yes In flight Focus (chopped)LO-14flight 2 yes In flight std star obsLO-15flight 2 yes In flight science object obsLO-16flight 2 yes In flight quick step obsLO-18flight 2 yes Total Hours 6 DAY 9 - Ops Sim & MCCS tests 1 5.4.10post flightOpsHangar1yes day shift on day after flight sim 5.1.8data ingestionMCCSHangar2yes Total Hours 3 NIGHT 9 - SI/Aircraft test 1 5.3.16emi/emc ground testingLO-12Line8 need more info on test duration Total Hours 8 Totals 69 Contingency nights 5 Test #Test DescriptionGroupLocationDurationParallel# days# nightsPrerequisites

20. Time line AugSeptOctNovDecJanFebMar Test Plan Draft Status Meeting Test Plan Final Test Procedures TRR Line-ops #1 Quick Look Results Final Analysis report