GRC SPACE OPERATIONS PROJECT OFFICE Space Communications Office SCAN Testbed Project Monthly Status Review D. Malarik, Project Manager M. Zernic, Deputy Project Manager R. Reinhart, Project Principal Investigator L. Aponte-Richter, Resource Analyst July 12,

GRC Project Manager: MSC/Diane Malarik Chief Engineer: DT/Josh Freeh Safety & Mission Assurance Lead: Q/R. Plastow NASA Customer: SCaN Program/John Rush Key Contractor(s): GESS/ASRC; SpaceDOC/ZIN Project Mission Statement: Develop, deploy and operate a communications, navigation, and networking testbed on ISS to advance the TRL of Software Defined Radios (SDR) and the Space Telecommunications Radio Standard (STRS) in support of future NASA missions. GRC Scope: The SCaN Testbed project is defined as the design, build, launch, and operations of the SCAN Testbed, as well as the development, integration and on-orbit execution of experiments and other users. Project closeout will occur no earlier than 2018, or upon Program direction, with SCAN Testbed decommissioning, disposal, and final documentation. GRC will lead a multi-partner team (GSFC, JPL, JSC, General Dynamics and Harris) to deliver the testbed for launch on JAXA’s HTV3 in July 2012 and operate for a minimum of 3 years. Project Life Cycle Schedule Insertion into HTV-3 Unpressurized Section Flight System in TVAC SCaN Testbed Operations & Experiments Project 2 MilestonesSRRIVRPDRCDRPh III Safety SARORRLaunchOpsOn-Orbit Expts ReturnFinal Report Actual/ Baseline 5/200810/20089/20094/201008/201110/20116/20127/2012Inc. 32=>01/2013N/A

3 SCAN TESTBED PAYLOAD OPS AND EXPERIMENTS Overall Status

Accomplishments (1 of 3) Operational Readiness Review (ORR) (6/5) ORR Board Findings (6/13) –Document comment spreadsheets –Overall Findings Presentation Four Request for Actions ORR Board recommends proceeding to Phase E, pending the completion of 2 Contingent Actions –All deficiencies, issues and concerns traced to FTE and/or budget shortfalls Project Response (EMB on 6/28; to be presented at CMC on 7/16) – Document authors have dispositioned all comments, in conjunction with the initiator of the comment. Docs to be updated to next revision, as appropriate – RFAs assigned to SCaN Testbed Project personnel for disposition; 2 of 4 closed with concurrence of initiator (as of 7/11/12) – Project has completed both Review Board recommendations identified as Contingent Actions 4 Venus Transit 6/5/12 Photo taken by Steve Hall CriteriaRating of Criteria Elements ORR Entrance ORR Success KDP-E Success

Accomplishments (2 of 3) Last remaining Safety Hazard Report Verifications were approved; all Certification of Flight Readiness items completed and closed! –HTV3 CoFR Schedule completed July 6 Goddard Space Flight Center network services successfully completed the SCaN Testbed Mission Operations Readiness Review (MORR), Jun 21 SCaN Testbed Presentation at ISS Utilization Conference –June 26-28, 2012 in Denver, Colorado attended by Jim Stegeman –SCaN Testbed highlighted in Gerstenmaier's keynote address; talked about the potential to revolutionize SDR technology for NASA by using this new "facility" onboard ISS. –Presented in Spacecraft Systems Technology Session 5

Conceptual Drawing of SCANOT Payload SCaN Noon Time Talk (6/20): “CoNNeCT – A Totally Unique Experience,” detailing the project history, challenges, and Lessons Learned (Diane Malarik) Accomplishments (3 of 3) 6 Conceptual Design Jul 2007 MCR/SRR May 2008 PDR/CDR Sep 2009 / Apr 2010 Final Design Aug 2010 “Waterboarding has nothing over on this project”

7 NASA and JPL Experiments Status Initial Set for On-Orbit Execution (Waveform/Experiment Development ≤ FY12) # 1 S-band SDR Technology (TRL Advancement, TDRSS launch waveforms) – Completed JPL Flight Data Analysis Book – Continue GIU SDR characterization – Complete draft commissioning plan #2 Ka-band SDR Technology (TRL Advancement, TDRSS launch waveforms) – Continue Flight Data Analysis Book development – Continue GIU SDR characterization – Complete draft commissioning plan #3 IPv4 routing/networking – Conducted review of current objectives and approach as applies to future potential network experiments #4 GPS L1, L2, L5 – Development suspended until FY13 due to funds depletion – Waveforms not yet delivered to GRC

8 SBIR 2011 Phase I Experiment Formulation/Concept Development in FY12 #7, Radio Navigation Waveform (Codeless GPS), Emergent – No new highlights to report #8, Agile Cognitive (Signal detection) – Space Micro – No new highlights to report #9, Scintillation Hardened GPS (Solar Flare Study) – Comm Largo – No new highlights to report

9 Pursuit of SCaN Testbed Utilization SBIR Experiment Calls – 2011 Phase II – Proposals expected Fall On-orbit tests not expected until ~late 2013 (depends on Phase II proposal and selection) – 2012 Phase I Solicitation Planned for Fall 2012 University/Commercial Experiment Calls – Call to be released in July 2012 for Commercial/Academic/OGA Determined with GRC Legal, Procurement, and ITAR representatives (7/11): Cooperative Agreement Notice with Universities Space Act Agreements with all other entities – First users expected late 2013/early 2014 (depends on funding & development time) Potential multi-Agency interest in spectrum efficient, adaptive techniques Planned outreach/participation in – International Communications Satellite Systems Conference (ICSSC) and Ka-Band Conference (September th in Ottawa, Ontario) Group travel via ground transportation under investigation – Wireless Innovation (SDR) Forum (January 2013 in Washington, DC) Keynote address STRS Tutorial Technical papers/presentations (2)

SCAN Testbed Top Project Risks Approach M – Mitigate W – Watch A – Accept R – Research C – Closed Criticality  Decreasing (Improving)  Increasing (Worsening)  Unchanged N New L x C Trend LIKELIHOODLIKELIHOOD CONSEQUENCES LxC Trend RankApproachRisk Title  1M Underfunded Operations and Experiments Phase  2M Experimenter Software Interface C 3M Loss of Experienced Software Personnel  4M,WELC HRDL Repair High Med Low STATUS AS OF: 7/10/12 10

Issues and Concerns Restoration of SCaN PAA to minimally implementable resource profile that was negotiated as an April 5 th PPBE re-submit –Ref. Malarik conversation w/Rush that sustains uncertainty Experiment Call mechanism/release delay –Impact upon non-SCaN proposers to plan/seek resources for FY13 ISS priorities and crew time allocation may impact installation, checkout, and commissioning schedule –HRDL repair now scheduled for 8/1 ( ✓ currently alleviates previous concern) –JEM RMS cooling pump repair may delay SCaN Testbed installation onto ELC-3 (perhaps by 1 week) 11

12 SCaN Testbed Master Schedule Overview

SCaN Testbed Daily Schedule July, 2012 Note Calendar includes (GMT date) BLUE TEXT: ON-ORBIT ACTIVITIES BLACK TEXT: GIU ACTIVITIES

SCaN Testbed Daily Schedule August, 2012 Note calendar includes (GMT date) BLUE TEXT: ON-ORBIT ACTIVITIES BLACK TEXT: GIU ACTIVITIES

15 Upcoming Events Experiment Call Release, July 2012 Special CMC Briefing: ORR Findings and KDP-E, Jul 16 GIU Dry Run of Checkout & Commissioning Week #2, Jul 9-10 ISS-POIC Simulation #2, Jul 12 HTV3 Launch, Jul 20 at 10:18 PM ET – Featured event at 100 th Bomb Group; All subsequent activities subject to change per ISS scheduling process: –“Just-in-Time” with POIC, Jul 23 –HTV berth, Jul 27 –HRDL cable repair, Aug 1 –EP MP extraction and dock to JEM EF, Aug 3 –SCaN Testbed Installation on ELC-3, Aug 4 –SCaN Testbed Operational Power Activation; begin C&C, Aug 6

Back-up 16

RankRisk IDRisk StatementApproach & PlanComments 11 SCAN-135Underfunded Operations and Experiments Phase Given the: limited funding available for Phase E of the SCaN Testbed Project, There is a possibility that: Level 1 requirements may not be met. Context: Per PPBE-14, the SCaN Testbed budget is limited during FY , and is zeroed out in FY16 and beyond. The ability to fund new experiments and complete the Software Development as identified in the SW Requirements Specification, is significantly constrained. This may result in the deferral of many experiments' completion until late 2014 and 2015, deferral or elimination of Priority 2 and Priority 3 SW requirements, and deferral or delay of the SW Code Optimization tasks that were planned to increase the CPU margin available to experimenters. If the SCaN Testbed is decommissioned in 2015, it is possible some Level 1 requirements may not be met. Mitigate 1.Release NASA Research Announcement (NRA) to attract experiments that do not require SCaN Program funding, by 6/30/12. 2.Assess Level 1 impacts given current software funding and experiment funding. Present as part of the ORR briefing packages, by 6/5/12. 3.Prioritize remaining software development to maximize capability using Level 1 impact assessment, by 6/30/12. 4.Develop PPBE-15 request to SCaN Program to support more robust utilization of SCaN Testbed, by 3/31/13. 5.Seek non-SCaN Program funding via pursuit of other NASA sponsors, such as OCT, for internal experiment development, by 6/30/13. STATUS: PPBE-14 budget cycle activities and decisions during March-April 2012 have established a minimum set of requirements for viable implementation in FY13. Significant work has been invested in the planning and formulation of a NRA (formerly known as Announcement of Opportunity) to be released in June 2012 to attract non-SCaN Program sponsored use of the SCaN Testbed. ORR and KDP-E briefing packages addressed software status and included PI assessment. ORR held on June 5, 2012, and KDP-E to occur on July 12, Software development has been prioritized. Quantity of new scripts have been determined for mission ops; JIRAs have been identified to be incuded in the post-ship software build. RISK FOCUS Risk Score: 4 L x 5 C Timeframe: Near Term Risk Category: Technical Owner: Diane Malarik SCAN Testbed Risks Underfunded Operations and Experiments Phase HIGH 17 STATUS AS OF: 7/10/12

RankRisk IDRisk StatementApproach & PlanComments 22 SCAN-123Experimenter Software Interface Given the: software interface between avionics software and experimenter software on the avionics is in development, There is a possibility that: experiment software will be difficult to integrate with the PAS. Context: Experimenters are expected to provide software applications to run on the avionics. The first planned software is the baseline IPv4 networking experiment. Mitigate 1.Reduce initial functionality by only implementing the portions needed for baseline networking. (completed 9/30/11) 2.Implement software capability for initial networking experiment. (completed 9/30/11) 3.Defer testing/verification of baseline networking from Flight System, pre-ship to GIU, post-ship. (completed 4/27/12) 4.Decompose requirements that describe standard experimenter software interface capabilities, by 6/30/12. 5.Implement software interface capabilities in post- ship version of PAS software on-orbit with experimenter interfaces, by 12/31/12. STATUS: After the Flight System has shipped, testing on GIU has been completed and has verified required kernel capabilities are sufficient. Determined further requirements decomposition is necessary to appropriately implement experimenter interface capabilities. A design review was conducted in early June 2012, with follow-on reviews conducted as needed. S/W Team has determined a set of APIs for functional implementation that are approx. 80% developed using the Software Development System unit. JPL PI/SMEs currently assessing this proposed solution as potential users of such an interface. Technical Interchange Meeting (TIM) proposed to be scheduled to: Assess current approach Assess impact upon the initial networking experiment Determine/assign forward work, if any RISK FOCUS Risk Score: 3 L x 4 C Timeframe: Near-term Risk Category: Cost, Schedule Owner: Steve Hall SCAN Testbed Risks Experimenter Software Interface MED 18 STATUS AS OF: 7/10/12

RankRisk IDRisk StatementApproach & PlanComments 33 SCAN-136Loss of Experienced Software Personnel Given the: loss of several SW engineers that have left GRC, There is a possibility that: on-orbit troubleshooting will be inefficient. Context: Several SW engineers have left the project, and several have left GRC. The SW personnel still at GRC but redeployed to other projects will be tasked with troubleshooting if required, however the ones that have left GRC are not available at all. Mitigate 1.Reassess and reassign responsibilities for existing software code to remaining software team, by 6/15/12. STATUS: Re-prioritization of work with remaining team member skills and scheduled deliverables in preparation for Phase E has been determined. Close risk (re-evaluation of software work will be tracked as part of Risk 135). RISK FOCUS Risk Score: 2 L x 3 C Timeframe: Near Term Risk Category: Cost, Schedule Owner: Denise Varga SCAN Testbed Risks Loss of Experienced Software Personnel Low 19 STATUS AS OF: 7/10/12

RankRisk IDRisk StatementApproach & PlanComments 44 SCAN-137Express Logistics Carrier (ELC) High Rate Data Line (HRDL) Repair Given the: ELC HRDLs do not function, There is a possibility that: the HRDL repair will not be completed prior to SCaN Testbed Checkout & Commissioning. Context: The ELC HRDL jumper cable is scheduled for launch on HTV-3 and on-orbit installation and checkout is planned for shortly thereafter. Mitigate 1.Request that ISS schedule HRDL repair prior to SCaN Testbed installation on ELC- 3. (completed 3/30/12) 2.In coordination with ISS, verify HRDL functions during Checkout and Commissioning, by 9/15/12. STATUS: Healthy project-ISS relationship has enabled quick, mutual acceptable resolution via IVA jumper cable approach. HRDL cable development by ISS on schedule to meet HTV3 launch. ISS Timeline states IVA install scheduled for 8/1/12. Project has provided a response to an ORR Request For Action (RFA) regarding HRDL repair planning to be presented at GRC CMC 7/16/12. RISK FOCUS Risk Score: 1 L x 4 C Timeframe: Far Risk Category: Cost, Schedule Owner: Steven Sinacore SCAN Testbed Risks Express Logistics Carrier (ELC) High Rate Data Link (HRDL) Repair STATUS AS OF: 7/10/12 Low 20

Scenario #3 Session with POIC June 8, 2012 Highlights: Avionics Activation, TWTA Activation, Harris Corporation Activation, and a Ka-band closed loop contact. Experimenters and PI’s involved in the SCaN Testbed Experiments Center; First SCAN TB specific failure (loss of 120 Vdc contingency heater power); First time scripted TWTA and Harris SDR activities in On-board Short Term Plan Viewer (OSTPV) Summary: Accomplished during window durations; Proper response to failure; Quantified power parameters during failure; Determined software module redlines; Favorable remarks from POIC counterparts MSFC POIC: POD – Jason Norwood PRO – Jessica Caudle OC – Tessa Lucas SCAN Testbed Team: MOM - Aulisio / Centeno-Gomez Flight Controller - Brown Flight Commander – Sinacore GIU Controller - Schrage / McGiffin GIU Commander - Norton APS Operator & Scheduler - McGiffin SFEP Operator - Curtis Experimenter - Downey / Sexton PI Observers – Reinhart/Johnson GIU/APS – Jeff Glass 21 Top: SCaN Testbed Team in the TSC Right: STK depicting acquisition Bottom left: OSTPV

SignOffPage