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 Principle Investigator L. Aponte-Richter, Resource Analyst June 7, 2012 1
25
Embed
GRC SPACE OPERATIONS PROJECT OFFICE Space Communications Office SCAN Testbed Project Monthly Status Review D. Malarik, Project Manager M. Zernic, Deputy.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• 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
– Adjusted Board membership per Plan, Rev. A– Provided 2 sets of document drops + supporting information
• Conducted GIU-GPS ERB (5/25)– Preparation to install JPL GPS antenna (B333 roof) and provide additional ground
capability• Approval of ORR/KDP-E Plan (5/25)
Briefed CMC on Plan, Rev. A (5/24); GRC Deputy Center Director signed (5/25)• Conducted JAXA De-briefing for Project info exchange (5/29)• Conducted ORR Dry Run (5/30)• Briefed SCaN TSD Director at PSR (5/31)• Received themed visual summaries from first 2 (of 3) Lessons
Learned workshops…. 5
Lessons Learned Themed Visual SummariesExamples
6
ORR Preparation
• Conducted Kick-off with ORR Board• ORR documents available for review
– 2 drops + Supporting Material
Board Membership:Kevin McPherson –
Chair, GRC/ISS Facility Payload Ops
Gary Morse - HQ/SCaN ProgramDevin Bitner - GSFC/SN, NENLee Jankowski - MSFC/ISS POICFrank Gati - GRC/Systems EngineeringRich Reinhart - GRC/PIDennis Rohn - GRC/Systems, OpsTim Best - GRC/S&MAJim Budinger - GRC/Communications
9:10 Summary of Verification and Validation S. Hall
9:30 Operations Overview S. Sinacore, L. Gray
10:15 Break
10:25 ISS Ground Systems M. Aulisio
10:40 SN/NEN Ground Systems S. Sinacore
10:55 Checkout Schedule D. Centeno-Gomez
11:10 Checkout Procedures J. Norton
11:20 Off-Nominal Procedures J. Keller
11:30 Anomaly Resolution Process R. Pavlik
11:50 Data Management Plan B. Curtis
12:10 Working Lunch
Building 54, Rm 101
9
ORR Agenda – Afternoon SessionJune 5, 2012
Time Topic Presenter12:45 Training Plan and Records M. Aulisio
1:00 Ops Assessment of SW Anomalies S. Sinacore
1:20 Software Status J. Keller
1:40 Experiment Integration Approach A. Sexton
1:55 Ground Systems for Sustaining Engineering A. Rybar
2:10 S&MA Assessment R. Plastow
2:20 Certification of Flight Readiness Status D. Kiefer
2:30 Break
2:45 Top Project Risks M. Zernic
2:55 Schedule J. Lekan
3:05 Resources and PM Assessment D. Malarik
3:15 PI Assessment R. Reinhart
3:30 ORR Board Caucus ORR Board
4:30 ORR Outbrief K. McPherson
Building 54, Rm 101
ORR June 5, 2012
• Top Picture: Mission Ops Team member, Mike Aulisio, briefs ORR Board Members during one of the 20+ agenda topics.
• Left Picture: ORR Board members eagerly await the next item on the agenda.• Right Picture: Venus Transit occurs on June 5, 2012, “Finally the planets align for CoNNeCT”,
Laura Spayd. Photo taken by SE&I Lead, Steve Hall.
10
ORR Summary
• The ORR Board recommends the SCaN Testbed Project proceed into Phase E Operations, pending the completion of:
– Off-nominal procedures for known off-nominal conditions deemed likely to occur from the JIRA and CPAR review process
– Ops team training and familiarity review with the above off-nominal procedures• Top Board Findings
– 4 Project Strengths: Thorough documentation; Risk management; POIC and SN/NEN coordination; Efficient training approach
– ORR Entrance Criteria: 5 Green, 1 Green/Yellow (off-nominal procedures)– ORR Success Criteria: 3 Green, 1 Green/Yellow (depth of critical personnel & functions)– KDP-E Criteria: 10 Green, 6 Green/Yellow (ref Concerns/RFAs), 2 Yellow (Budget/staffing)– 3 Concerns: Budget/staffing; HRDL fix contingency; Prep for off-nominal– 4 RFAs: Contingency plan for HRDL fix; Lack of GIU Spares; Review for Experiment Phase; Insure
offset center frequency with GSFC FDF• Project Response
– Document comment responses back to ORR Board members– EMB on 6/28 PRB on 6/29 CMC on 7/12
• SCaN Program KDP-E approval on (TBR)
11
Scenario #3 Session with POICJune 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
Top: SCaN Testbed Team in the TSCRight: STK depicting acquisitionBottom left: OSTPV
13
NASA and JPL Experiments StatusInitial Set for On-Orbit Execution (Waveform/Experiment Development ≤ FY12)
#1 S-band SDR Technology (TRL Advancement, TDRSS launch waveforms)– Flight data analysis books underway– GIU SDR characterization underway; new GD SDR Test engineers– Experiment Plans underway
#2 Ka-band SDR Technology (TRL Advancement, TDRSS launch waveforms)– Flight data analysis books underway– GIU SDR characterization underway; new Harris SDR Test engineers– Experiment Plans underway
#3 IPv4 routing/networking– Consolidated work under new contract, experienced transition delays– Conducted requirements decomposition of avionics and experimenter software interface– Preparations for design review underway (target June)– Experiment planning underway
#4 GPS L1, L2, L5– L2c data captured and able to track (development continues)– Very first L5 data captured with prototype (development continues)– GIPSY ground processing completed for L1-C/A
14
SBIR 2011 Phase I Experiment Formulation/Concept Development in FY12
#7, Radio Navigation Waveform (Codeless GPS), Emergent– Developing concept of operations for spectral compression positioning technique– Developing performance analysis for spectral compression positioning technique at SCaN Testbed
location onboard ISS, based on payload location on ELC-3#8, Agile Cognitive (Signal detection) – Space Micro
– Updating objectives wrt SN LGA antenna placement and HW operational parameters– Gathered detailed documentation of the JPL SDR to develop a good understanding of the system
operation as well as the interface points for the waveform (ASR) firmware. Identified firmware connection points that allows transfer of analog RF data into VHDL digital domain for process in as well as the VHDL control points allowing VHDL control of the JPL SDR hardware. The ASR experiment intends to process the entire USB uplink band at one time, channelize the observed signals, categorize and report the finds.
#9, Scintillation Hardened GPS (Solar Flare Study) – Comm Largo– Developed a MATLAB tracking simulation that allows selectable evaluation of a Kalman filter and a
conventional PLL filter as a phase detector for GPS signals undergoing scintillation. The scintillation is produced according to the Cornell Scintillation Model.
– Performed testing using the GNSS SDR receiver waveform on the Ettus Research USRP-N210 SDR. The current design allows a selectable interface of either signal samples or a live RF receiver.
– Started preliminary design of the Eclipse-based plugin for developing STRS-compliant waveforms.
15
Pursuit of SCaN Testbed Utilization
• SBIR Experiment Calls– 2011 Phase II – Proposals expected Fall 2012. 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 June 2012 for Commercial/Academic/OGA– First users expected late 2013/early 2014 (depends on funding & development time)
• Planned participation in– ISS Utilization Conference (June 26-28th in Denver, CO)– International Communications Satellite Systems Conference (ICSSC) and Ka-Band Conference
(September 24-27th in Ottawa, Ontario)• Group travel via ground transportation under investigation
• HRDL Repair Timeline– After the initial ~7 days of checkout that the SCAN team can get through without
HRDL, schedule will slip day for day• Without the HRDL, the SCAN team will not have the necessary telemetry to continue on
with checking out the S-band and Ka-band experiment functions• Not a safety concern since safety telemetry via ISS 1553 path; no Hazard Report change
– Crew Time allocation may not enable HRDL jumper cable installation until after HTV3 undocking (~30 days)
• De-couple SCaN Testbed impacts from CoFR approval to avoid unnecessary confusion• Continue to work with ISS to accommodate repair within overall crew activity prioritization
Readiness Review, June 21, 2012– Post-ORR Findings Briefing to CMC, July 12, 2012– Space Communication and Navigation Program Key Decision Point-E
concurrence, July 12, 2012 (TBR)
• International Space Station Utilization Conference, June 26-28 in Denver, Colorado
– Present at Spacecraft Systems Technology Session
• Pre-Launch ISS-POIC Simulation #2, July 12, 2012
• Transfer Vehicle (HTV3) Launch, July 21, 2012 (Japanese time)
Back-up
20
Rank Risk ID Risk Statement Approach & Plan Comments
1è
SCAN-135 Underfunded 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 FY13 - 15, 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.
Mitigate1. 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 to address software status and include PI assessment. ORR scheduled for June 2012, and KDP-E to occur shortly thereafter.
RISK FOCUS
Risk Score: 4L x 5CTimeframe: Near Term
Risk Category: TechnicalOwner: Diane Malarik
SCAN Testbed RisksUnderfunded Operations and Experiments Phase
HIGH
21
STATUS AS OF: 5/31/12
Rank Risk ID Risk Statement Approach & Plan Comments
2è
SCAN-123 Experimenter 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.
Mitigate1. 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.
RISK FOCUS
Risk Score: 3L x 4C Timeframe: Near-term
Risk Category: Cost, Schedule
Owner: Steve Hall
SCAN Testbed RisksExperimenter Software Interface
MED
22
STATUS AS OF: 5/31/12
Rank Risk ID Risk Statement Approach & Plan Comments
3è
SCAN-136 Loss 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.
Mitigate1. Reassess and reassign
responsibilities for existing software code to remaining software team, by 6/15/12.
STATUS: • Re-prioritization of work is underway
with remaining team member skills and scheduled deliverables in preparation for Phase E.
RISK FOCUS
Risk Score: 2L x 3C Timeframe: Near Term
Risk Category: Cost, Schedule
Owner: Denise Varga
SCAN Testbed RisksLoss of Experienced Software Personnel
Low
23
STATUS AS OF: 5/31/12
Rank Risk ID Risk Statement Approach & Plan Comments
4è
SCAN-137 Express 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.
Mitigate1. 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.
RISK FOCUS
Risk Score: 1L x 4C Timeframe: Far
Risk Category: Cost, Schedule
Owner: Steven Sinacore
SCAN Testbed RisksExpress Logistics Carrier (ELC) High Rate Data Link (HRDL) Repair