TY - GEN
T1 - Science Operations Planning and Implementation for the OSIRIS-REx Mission, Part 2
T2 - 2022 IEEE Aerospace Conference, AERO 2022
AU - Balram-Knutson, Sara S.
AU - Lambert, Diane
AU - Audi, Edward
AU - Becker, Tami
AU - Boynton, William V.
AU - Dean, David
AU - Enos, Heather L.
AU - Fitzgibbon, Mike
AU - Galinsky, Ingrid
AU - Garcia, Rose
AU - Gardner, Andrew
AU - Hammond, Damian
AU - Harshman, Karl
AU - Hergenrother, Carl W.
AU - Kidd, John N.
AU - Loveridge, Michael
AU - Nelson, Joshua V.
AU - Polit, Anjani T.
AU - Selznick, Sanford
AU - Westermann, Mathilde
AU - Zeszut, Zoe
AU - Lauretta, Dante S.
AU - Anwar, Saadat
AU - Dickenshied, Scott
AU - Wren, Paul
N1 - Funding Information:
This material is based upon work supported by NASA under Contract NNM10AA11C issued through the New Frontiers Program. We would like to pay special recognition to the many team members that supported the development of J-Asteroid: Warren Hagee, Dale Noss, Ken Rios, Megan Burris, Nick Piacentine, Donald Doerres, and Shay Carter. We are grateful to the entire OSIRIS-REx Team for making the encounter with Bennu possible.
Publisher Copyright:
© 2022 IEEE.
PY - 2022
Y1 - 2022
N2 - The OSIRIS-REx mission to asteroid (101955) Bennu comprised multiple phases, each with objectives that posed unique complexities for planning and implementation of science and optical navigation observations. In response to these challenges, the Science Planning Team (SPT) and the Implementation Team (IpT) at the University of Arizona amassed a toolkit composed of both in-house and commercial tools and scripts to accomplish reliable production of safe, high-fidelity flight products on a rapid, tactical planning timeline. J-Asteroid was the primary planning and implementation tool used by SPT and IpT. Built upon the geospatial information system JMARS (Java Mission-planning and Analysis for Remote Sensing), it was developed by Arizona State University's Mars Space Flight Facility. Configurable to the mission design, J-Asteroid modeled ephemerides, asteroid shape and spin state, spacecraft trajectory, navigation uncertainty, slew and attitude profile, instrument systems, and instrument command sequencing for new observation plans. A front-end interface enabled design of spacecraft scan patterns, ability to incorporate automated commanding or an ingested library of blocks, and two-and three-dimensional visualization of instrument footprints over a global Bennu shape model. J-Asteroid checked plans against a comprehensive database of flight rules and constraints and against perturbed trajectories. J-Asteroid's Integrated Commanding Tool converted finalized plans into delivery packages. JPlanner2, a Java-based tool, automated the processing of J-Asteroid delivery packages through scripts to generate, compile, and test flight products. JPlanner2 calculated data volume, generated activity plots, performed flight rule and soft constraint checks, and produced build reports and artifacts for delivery to the Spacecraft Operations Team at Lockheed Martin. Activity Inspector was an in-house tool that produced an integrated spacecraft attitude profile and confirmed compliance with spacecraft and instrument pointing constraints, which allowed continuous and rapid verification of J-Asteroid plans. Activity Inspector generated standardized pointing telemetry products for stakeholder communication. The tool performed analyses of Monte Carlo sets of perturbed trajectories, allowing for assessment of plan stability and produced visualizations by compiling the transmitted plan against the reconstructed trajectory. SPOCFlight was an in-house, server-based data system with a web interface. This event-driven system managed, parsed, calibrated, and packaged ground, spacecraft, and science data, and enabled users to monitor data, generate reports, and execute Activity Inspector. Several planning and implementation tools and processes leveraged data products available on SPOCFlight. A library of instrument command blocks was developed to perform repeated functions, such as instrument calibrations and optical navigation imaging. Complex blocks worked with J-Asteroid to produce observation-specific sequencing. Validated blocks were stored in a spacecraft library and initiated from onboard instrument sequences. Python scripts for analysis parsed text and JSON reports output by J-Asteroid to produce tables, graphs, and additional computations, further enabling evaluation of observation plans. The scripts provided increased user efficiency. Git repositories were used to configuration-manage SPT scripts and IpT-generated flight products. JIRA, a commercial off-the-shelf work management software, was used to organize unique issue types for both SPT and IpT. The JIRA workflow included gated reviews as observations moved through planning, implementation, execution, and downlink. The OSIRIS-REx science operations toolkit of in-house and commercial tools enhanced efficiency, reduced risk, and increased flight product robustness.
AB - The OSIRIS-REx mission to asteroid (101955) Bennu comprised multiple phases, each with objectives that posed unique complexities for planning and implementation of science and optical navigation observations. In response to these challenges, the Science Planning Team (SPT) and the Implementation Team (IpT) at the University of Arizona amassed a toolkit composed of both in-house and commercial tools and scripts to accomplish reliable production of safe, high-fidelity flight products on a rapid, tactical planning timeline. J-Asteroid was the primary planning and implementation tool used by SPT and IpT. Built upon the geospatial information system JMARS (Java Mission-planning and Analysis for Remote Sensing), it was developed by Arizona State University's Mars Space Flight Facility. Configurable to the mission design, J-Asteroid modeled ephemerides, asteroid shape and spin state, spacecraft trajectory, navigation uncertainty, slew and attitude profile, instrument systems, and instrument command sequencing for new observation plans. A front-end interface enabled design of spacecraft scan patterns, ability to incorporate automated commanding or an ingested library of blocks, and two-and three-dimensional visualization of instrument footprints over a global Bennu shape model. J-Asteroid checked plans against a comprehensive database of flight rules and constraints and against perturbed trajectories. J-Asteroid's Integrated Commanding Tool converted finalized plans into delivery packages. JPlanner2, a Java-based tool, automated the processing of J-Asteroid delivery packages through scripts to generate, compile, and test flight products. JPlanner2 calculated data volume, generated activity plots, performed flight rule and soft constraint checks, and produced build reports and artifacts for delivery to the Spacecraft Operations Team at Lockheed Martin. Activity Inspector was an in-house tool that produced an integrated spacecraft attitude profile and confirmed compliance with spacecraft and instrument pointing constraints, which allowed continuous and rapid verification of J-Asteroid plans. Activity Inspector generated standardized pointing telemetry products for stakeholder communication. The tool performed analyses of Monte Carlo sets of perturbed trajectories, allowing for assessment of plan stability and produced visualizations by compiling the transmitted plan against the reconstructed trajectory. SPOCFlight was an in-house, server-based data system with a web interface. This event-driven system managed, parsed, calibrated, and packaged ground, spacecraft, and science data, and enabled users to monitor data, generate reports, and execute Activity Inspector. Several planning and implementation tools and processes leveraged data products available on SPOCFlight. A library of instrument command blocks was developed to perform repeated functions, such as instrument calibrations and optical navigation imaging. Complex blocks worked with J-Asteroid to produce observation-specific sequencing. Validated blocks were stored in a spacecraft library and initiated from onboard instrument sequences. Python scripts for analysis parsed text and JSON reports output by J-Asteroid to produce tables, graphs, and additional computations, further enabling evaluation of observation plans. The scripts provided increased user efficiency. Git repositories were used to configuration-manage SPT scripts and IpT-generated flight products. JIRA, a commercial off-the-shelf work management software, was used to organize unique issue types for both SPT and IpT. The JIRA workflow included gated reviews as observations moved through planning, implementation, execution, and downlink. The OSIRIS-REx science operations toolkit of in-house and commercial tools enhanced efficiency, reduced risk, and increased flight product robustness.
UR - http://www.scopus.com/inward/record.url?scp=85137595721&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85137595721&partnerID=8YFLogxK
U2 - 10.1109/AERO53065.2022.9843365
DO - 10.1109/AERO53065.2022.9843365
M3 - Conference contribution
AN - SCOPUS:85137595721
T3 - IEEE Aerospace Conference Proceedings
BT - 2022 IEEE Aerospace Conference, AERO 2022
PB - IEEE Computer Society
Y2 - 5 March 2022 through 12 March 2022
ER -