Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mission Systems Architecture Process Modeling”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 235 records · Page 13

Dual-Use Aspects of System Health Management

System Health Management functionality is an essential part of any space launch system. Health management functionality is an integral part of mission reliability, since it is needed to verify the reliability before the mission starts. Health Management is also a key factor in life cycle cost reduction and in increasing system availability. The degree of coverage needed by the system and the degree of coverage made available at a reasonable cost are critical parameters of a successful design. These problems are not unique to the launch vehicle world. In particular, the Intelligent Vehicle Highway System, commercial aircraft systems, train systems, and many types of industrial production facilities require various degrees of system health management. In all of these applications, too, the designers must balance the benefits and costs of health management in order to optimize costs. The importance of an integrated system is emphasized. That is, we present the case for considering health management as an integral part of system design, rather than functionality to be added on at the end of the design process. The importance of maintaining the system viewpoint is discussed in making hardware and software tradeoffs and in arriving at design decisions. We describe an approach to determine the parameters to be monitored in any system health management application. This approach is based on Design of Experiments (DOE), prototyping, failure modes and effects analyses, cost modeling and discrete event simulation. The various computer-based tools that facilitate the approach are discussed. The approach described originally was used to develop a fault tolerant avionics architecture for launch vehicles that incorporated health management as an integral part of the system. Finally, we discuss generalizing the technique to apply it to other domains. Several illustrations are presented.

Owens, P. R.↗

A Risk-Constrained Multi-Stage Decision Making Approach to the Architectural Analysis of Mars Missions

This paper presents a novel risk-constrained multi-stage decision making approach to the architectural analysis of planetary rover missions. In particular, focusing on a 2018 Mars rover concept, which was considered as part of a potential Mars Sample Return campaign, we model the entry, descent, and landing (EDL) phase and the rover traverse phase as four sequential decision-making stages. The problem is to find a sequence of divert and driving maneuvers so that the rover drive is minimized and the probability of a mission failure (e.g., due to a failed landing) is below a user specified bound. By solving this problem for several different values of the model parameters (e.g., divert authority), this approach enables rigorous, accurate and systematic trade-offs for the EDL system vs. the mobility system, and, more in general, cross-domain trade-offs for the different phases of a space mission. The overall optimization problem can be seen as a chance-constrained dynamic programming problem, with the additional complexity that 1) in some stages the disturbances do not have any probabilistic characterization, and 2) the state space is extremely large (i.e, hundreds of millions of states for trade-offs with high-resolution Martian maps). To this purpose, we solve the problem by performing an unconventional combination of average and minimax cost analysis and by leveraging high efficient computation tools from the image processing community. Preliminary trade-off results are presented.

entry, descent, and landing (EDL)↗

NASA's Space Launch System Progress Report

Exploration beyond Earth will be an enduring legacy for future generations, confirming America's commitment to explore, learn, and progress. NASA's Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program's Saturn V that sent Americans to the Moon. The SLS offers a flexible design that may be configured for the MultiPurpose Crew Vehicle and associated equipment, or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Both options support a national capability that will pay dividends for future generations. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 metric tons (mT) and will be evolvable to 130 mT. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of asteroids and Mars. With its superior lift capability, the SLS can expand the interplanetary highway to many possible destinations, conducting revolutionary missions that will change the way we view ourselves, our planet and its place in the cosmos. To perform missions such as these, the SLS will be the largest launch vehicle ever built. It is being designed for safety and affordability - to sustain our journey into the space age. Current plans include launching the first flight, without crew, later this decade, with crewed flights beginning early next decade. Development work now in progress is based on heritage space systems and working knowledge, allowing for a relatively quick start and for maturing the SLS rocket as future technologies become available. Together, NASA and the U.S. aerospace industry are partnering to develop this one-of-a-kind asset. Many of NASA's space centers across the country will provide their unique expertise to the Space Launch System endeavor. Unique infrastructure to be used includes the Michoud Assembly Facility for tank manufacturing, Stennis Space Center for engine testing, and Kennedy Space Center for processing and launch. As this panel will discuss, the SLS team is dedicated to doing things differently-from applying lean oversight/insight models to smartly using legacy hardware and existing facilities. Building on the foundation laid by over 50 years of human and scientific space flight--and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs-the SLS team has delivered both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable.

Singer, Joan A.↗

NASA Tech Briefs, October 2011

Topics covered include: Laser Truss Sensor for Segmented Telescope Phasing; Qualifications of Bonding Process of Temperature Sensors to Deep-Space Missions; Optical Sensors for Monitoring Gamma and Neutron Radiation; Compliant Tactile Sensors; Cytometer on a Chip; Measuring Input Thresholds on an Existing Board; Scanning and Defocusing Properties of Microstrip Reflectarray Antennas; Cable Tester Box; Programmable Oscillator; Fault-Tolerant, Radiation-Hard DSP; Sub-Shot Noise Power Source for Microelectronics; Asynchronous Message Service Reference Implementation; Zero-Copy Objects System; Delay and Disruption Tolerant Networking MACHETE Model; Contact Graph Routing; Parallel Eclipse Project Checkout; Technique for Configuring an Actively Cooled Thermal Shield in a Flight System; Use of Additives to Improve Performance of Methyl Butyrate-Based Lithium-Ion Electrolytes; Li-Ion Cells Employing Electrolytes with Methyl Propionate and Ethyl Butyrate Co-Solvents; Improved Devices for Collecting Sweat for Chemical Analysis; Tissue Photolithography; Method for Impeding Degradation of Porous Silicon Structures; External Cooling Coupled to Reduced Extremity Pressure Device; A Zero-Gravity Cup for Drinking Beverages in Microgravity; Co-Flow Hollow Cathode Technology; Programmable Aperture with MEMS Microshutter Arrays; Polished Panel Optical Receiver for Simultaneous RF/Optical Telemetry with Large DSN Antennas; Adaptive System Modeling for Spacecraft Simulation; Lidar-Based Navigation Algorithm for Safe Lunar Landing; Tracking Object Existence From an Autonomous Patrol Vehicle; Rad-Hard, Miniaturized, Scalable, High-Voltage Switching Module for Power Applications; and Architecture for a 1-GHz Digital RADAR.

Source record↗

Summary of Space Environment Magnetometer and Particle Replacement Experiment (SEMPRE) Study

As part of the GOES-R series follow on architecture study following the NOAA Satellite Observing System Architecture (NSOSA) study, a study team evaluated the feasibility of accommodating the GOES in-situ instruments (Magnetometer and Particle Detectors) on a dedicated spacecraft with no impact to the overall baseline mission cost assuming two large observatories. The accommodations cost on a primary operational type observatory are non-negligible requiring: a large non-magnetic boom to reduce the impact of the spacecraft interference on the magnetometer; and strict contamination control and magnetic cleanliness to prevent magnetic contamination near the magnetometers. These, along with the additional interface complexities greatly increase the cost of larger spacecraft by extending integration time with a large marching army. By contrast, a dedicated mission provides flexibility in location and refresh rate not afforded when these sensors are launched as secondary payloads. This study performed an informal industry survey of small form-factor instruments currently flying or in process of being developed. The study identified three potential particle detector suites and multiple magnetometers that will satisfy the requirements while having low enough volume and mass to allow accommodation on a rideshare class spacecraft. Using the largest of the identified particle detector suites, the Goddard Space Flight Center Mission Design Lab developed a design for a rideshare spacecraft that will accommodate the particle detector suite and magnetometer. The cost of the spacecraft, based on multiple cost models, is comparable to the cost of accommodating the magnetometer and particle detector suite on two (East and West) larger main observatories.

Todirita, Monica↗

Development Efforts Expanded in Ion Propulsion: Ion Thrusters Developed With Higher Power Levels

The NASA Glenn Research Center was the major contributor of 2-kW-class ion thruster technology to the Deep Space 1 mission, which was successfully completed in early 2002. Recently, NASA s Office of Space Science awarded approximately $21 million to Glenn to develop higher power xenon ion propulsion systems for large flagship missions such as outer planet explorers and sample return missions. The project, referred to as NASA's Evolutionary Xenon Thruster (NEXT), is a logical follow-on to the ion propulsion system demonstrated on Deep Space 1. The propulsion system power level for NEXT is expected to be as high as 25 kW, incorporating multiple ion thrusters, each capable of being throttled over a 1- to 6-kW power range. To date, engineering model thrusters have been developed, and performance and plume diagnostics are now being documented. The project team-Glenn, the Jet Propulsion Laboratory, General Dynamics, Boeing Electron Dynamic Devices, the Applied Physics Laboratory, the University of Michigan, and Colorado State University-is in the process of developing hardware for a ground demonstration of the NEXT propulsion system, which comprises a xenon feed system, controllers, multiple thrusters, and power processors. The development program also will include life assessments by tests and analyses, single-string tests of ion thrusters and power systems, and finally, multistring thruster system tests in calendar year 2005. In addition, NASA's Office of Space Science selected Glenn to lead the development of a 25-kW xenon thruster to enable NASA to conduct future missions to the outer planets of Jupiter and beyond, under the High Power Electric Propulsion (HiPEP) program. The development of a 100-kW-class ion propulsion system and power conversion systems are critical components to enable future nuclear-electric propulsion systems. In fiscal year 2003, a team composed of Glenn, the Boeing Company, General Dynamics, the Applied Physics Laboratory, the Naval Research Laboratory, the University of Wisconsin, the University of Michigan, and Colorado State University will perform a 6-month study that will result in the design of a 25-kW ion thruster, a propellant feed system, and a power processing architecture. The following 2 years will involve hardware development, wear tests, single-string tests of the thruster-power circuits and the xenon feed system, and subsystem service life analyses. The 2-kW-class ion propulsion technology developed for the Deep Space 1 mission will be used for NASA's discovery mission Dawn, which involves maneuvering a spacecraft to survey the asteroids Ceres and Vesta. The 6-kW-class ion thruster subsystem technology under NEXT is scheduled to be flight ready by calendar year 2006. The less mature 25- kW ion thruster system under HiPEP is expected to be ready for a flight advanced development program in calendar year 2006.

Patterson, Michael J.↗

NASA Tech Briefs, November 2008

Topics covered include: Digital Phase Meter for a Laser Heterodyne Interferometer; Vision System Measures Motions of Robot and External Objects; Advanced Precipitation Radar Antenna to Measure Rainfall From Space; Wide-Band Radar for Measuring Thickness of Sea Ice; Vertical Isolation for Photodiodes in CMOS Imagers; Wide-Band Microwave Receivers Using Photonic Processing; L-Band Transmit/Receive Module for Phase-Stable Array Antennas; Microwave Power Combiner/Switch Utilizing a Faraday Rotator; Compact Low-Loss Planar Magic-T; Using Pipelined XNOR Logic to Reduce SEU Risks in State Machines; Quasi-Optical Transmission Line for 94-GHz Radar; Next Generation Flight Controller Trainer System; Converting from DDOR SASF to APF; Converting from CVF to AAF; Documenting AUTOGEN and APGEN Model Files; Sequence History Update Tool; Extraction and Analysis of Display Data; MRO DKF Post-Processing Tool; Rig Diagnostic Tools; MRO Sequence Checking Tool; Science Activity Planner for the MER Mission; UAVSAR Flight-Planning System; Templates for Deposition of Microscopic Pointed Structures; Adjustable Membrane Mirrors Incorporating G-Elastomers; Hall-Effect Thruster Utilizing Bismuth as Propellant; High-Temperature Crystal-Growth Cartridge Tubes Made by VPS; Quench Crucibles Reinforced with Metal; Deep-Sea Hydrothermal-Vent Sampler; Mars Rocket Propulsion System; Two-Stage Passive Vibration Isolator; Improved Thermal Design of a Compression Mold; Enhanced Pseudo-Waypoint Guidance for Spacecraft Maneuvers; Altimetry Using GPS-Reflection/Occultation Interferometry; Thermally Driven Josephson Effect; Perturbation Effects on a Supercritical C7H16/N2 Mixing Layer; Gold Nanoparticle Labels Amplify Ellipsometric Signals; Phase Matching of Diverse Modes in a WGM Resonator; WGM Resonators for Terahertz-to-Optical Frequency Conversion; Determining Concentration of Nanoparticles from Ellipsometry; Microwave-to-Optical Conversion in WGM Resonators; Four-Pass Coupler for Laser-Diode-Pumped Solid-State Laser; Low-Resolution Raman-Spectroscopy Combustion Thermometry; Temperature Sensors Based on WGM Optical Resonators; Varying the Divergence of Multiple Parallel Laser Beams; Efficient Algorithm for Rectangular Spiral Search; Algorithm-Based Fault Tolerance Integrated with Replication; Targeting and Localization for Mars Rover Operations; Terrain-Adaptive Navigation Architecture; Self-Adjusting Hash Tables for Embedded Flight Applications; Schema for Spacecraft-Command Dictionary; Combined GMSK Communications and PN Ranging; System-Level Integration of Mass Memory; Network-Attached Solid-State Recorder Architecture; Method of Cross-Linking Aerogels Using a One-Pot Reaction Scheme; An Efficient Reachability Analysis Algorithm.

Source record↗

Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits and difficulties that a migration to cloud-based computing philosophies has uncovered when compared to the legacy Mission Control Center architecture. The team consists of system and software engineers with extensive experience with the MCC infrastructure and software currently used to support the International Space Station (ISS) and Space Shuttle program (SSP).

Martin, Keith↗

Path Planning Algorithms for the Adaptive Sensor Fleet

The Adaptive Sensor Fleet (ASF) is a general purpose fleet management and planning system being developed by NASA in coordination with NOAA. The current mission of ASF is to provide the capability for autonomous cooperative survey and sampling of dynamic oceanographic phenomena such as current systems and algae blooms. Each ASF vessel is a software model that represents a real world platform that carries a variety of sensors. The OASIS platform will provide the first physical vessel, outfitted with the systems and payloads necessary to execute the oceanographic observations described in this paper. The ASF architecture is being designed for extensibility to accommodate heterogenous fleet elements, and is not limited to using the OASIS platform to acquire data. This paper describes the path planning algorithms developed for the acquisition phase of a typical ASF task. Given a polygonal target region to be surveyed, the region is subdivided according to the number of vessels in the fleet. The subdivision algorithm seeks a solution in which all subregions have equal area and minimum mean radius. Once the subregions are defined, a dynamic programming method is used to find a minimum-time path for each vessel from its initial position to its assigned region. This path plan includes the effects of water currents as well as avoidance of known obstacles. A fleet-level planning algorithm then shuffles the individual vessel assignments to find the overall solution which puts all vessels in their assigned regions in the minimum time. This shuffle algorithm may be described as a process of elimination on the sorted list of permutations of a cost matrix. All these path planning algorithms are facilitated by discretizing the region of interest onto a hexagonal tiling.

Stoneking, Eric↗

Asynchronous Message Service Reference Implementation

This software provides a library of middleware functions with a simple application programming interface, enabling implementation of distributed applications in conformance with the CCSDS AMS (Consultative Committee for Space Data Systems Asynchronous Message Service) specification. The AMS service, and its protocols, implement an architectural concept under which the modules of mission systems may be designed as if they were to operate in isolation, each one producing and consuming mission information without explicit awareness of which other modules are currently operating. Communication relationships among such modules are self-configuring; this tends to minimize complexity in the development and operations of modular data systems. A system built on this model is a society of generally autonomous, inter-operating modules that may fluctuate freely over time in response to changing mission objectives, modules functional upgrades, and recovery from individual module failure. The purpose of AMS, then, is to reduce mission cost and risk by providing standard, reusable infrastructure for the exchange of information among data system modules in a manner that is simple to use, highly automated, flexible, robust, scalable, and efficient. The implementation is designed to spawn multiple threads of AMS functionality under the control of an AMS application program. These threads enable all members of an AMS-based, distributed application to discover one another in real time, subscribe to messages on specific topics, and to publish messages on specific topics. The query/reply (client/server) communication model is also supported. Message exchange is optionally subject to encryption (to support confidentiality) and authorization. Fault tolerance measures in the discovery protocol minimize the likelihood of overall application failure due to any single operational error anywhere in the system. The multi-threaded design simplifies processing while enabling application nodes to operate at high speeds; linked lists protected by mutex semaphores and condition variables are used for efficient, inter-thread communication. Applications may use a variety of transport protocols underlying AMS itself, including TCP (Transmission Control Protocol), UDP (User Datagram Protocol), and message queues.

Burleigh, Scott C.↗

Modeling Constellation Virtual Missions Using the Vdot(Trademark) Process Management Tool

The authors have identified a software tool suite that will support NASA's Virtual Mission (VM) effort. This is accomplished by transforming a spreadsheet database of mission events, task inputs and outputs, timelines, and organizations into process visualization tools and a Vdot process management model that includes embedded analysis software as well as requirements and information related to data manipulation and transfer. This paper describes the progress to date, and the application of the Virtual Mission to not only Constellation but to other architectures, and the pertinence to other aerospace applications. Vdot s intuitive visual interface brings VMs to life by turning static, paper-based processes into active, electronic processes that can be deployed, executed, managed, verified, and continuously improved. A VM can be executed using a computer-based, human-in-the-loop, real-time format, under the direction and control of the NASA VM Manager. Engineers in the various disciplines will not have to be Vdot-proficient but rather can fill out on-line, Excel-type databases with the mission information discussed above. The author s tool suite converts this database into several process visualization tools for review and into Microsoft Project, which can be imported directly into Vdot. Many tools can be embedded directly into Vdot, and when the necessary data/information is received from a preceding task, the analysis can be initiated automatically. Other NASA analysis tools are too complex for this process but Vdot automatically notifies the tool user that the data has been received and analysis can begin. The VM can be simulated from end-to-end using the author s tool suite. The planned approach for the Vdot-based process simulation is to generate the process model from a database; other advantages of this semi-automated approach are the participants can be geographically remote and after refining the process models via the human-in-the-loop simulation, the system can evolve into a process management server for the actual process.

Hardy, Roger↗

Multidisciplinary Dynamic Testing Challenges in Validating the NASA Artemis Architecture

NASA is in the midst of bold and exciting next steps in human exploration and spaceflight. The designs of the new Space Launch System (SLS), the Orion spacecraft and the Exploration Ground Systems (EGS) for vehicle processing and launch are essentially complete and there has been significant progress in manufacturing and assembly of specific hardware for the Artemis I and Artemis II missions. Equally as important, the program level and integrated system level testing and analyses are also well underway to support integrated verification, validation, and certificate of flight readiness (CoFR) for the first Artemis mission. Testing and analysis are key to addressing technical challenges that the Artemis missions offer. Building block approaches are required that provide the right balance between component, system, and/or element level testing that satisfies verification and validation objectives and where, uncertainties are quantified and minimized. Artemis I is a system of systems that requires a fusion of test and analysis that adeptly characterizes critical interfaces between major program elements. NASA is implementing new in-situ testing that fuse traditional aerospace structures with civil structures, such as the Integrated Modal Test for the Artemis I vehicle where the Mobile Launcher and Crawler Transporter serve as a support structure whose dynamics couple with that of the Artemis I vehicle. This new paradigm requires a closer inspection of structural behavior of the Crawler Transporter and the Mobile Launcher as they now serve multiple purposes. This requires a paradigm shift to look beyond experimental modal techniques and incorporates operational modal analysis techniques to validate dynamic models from data collected during rollout to the launch pad. A further complicating factor is the Crawler Transporter generated ground forces have numerous harmonics making extracting dynamic responses of the Artemis I, Mobile Launcher, and Crawler Transporter coupled system challenging. This discussion explores all these challenges with and attempts to understand how we best build confidence in systems and system-of-systems performance capabilities and margins and understand uncertainties.

Joel W Sills↗

Autonomous Ocean World Exploration: Advancement of a Virtual Testbed

The search for life (extinct or extant) and potentially habitable bodies in our solar system and beyond is one of the 12 priority science questions outlined in the National Acadamies’ 2022 decadal survey [5]. Extraterrestrial destinations containing liquid water present an opportunity to search for life as we know it, and in recent years an increasing number of such locations have been discovered within our solar system. Several Jovian moons—Europa, Ganymede, and Callisto [10]—and the Saturnian moons Enceladus [8] and Titan [9] are known or suspected to harbor massive subsurface oceans. Of these "ocean worlds", Europa is the focus of at least one planned NASA orbiter mission, Europa Clipper [4], and an early lander mission concept, the Europa Lander [2, 3]. Whereas most robotic missions to the Moon and Mars (e.g. orbiters, rovers, landers) to date have had ground controllers on Earth tightly involved in mission operations, missions to more distant worlds will require a high degree of onboard autonomy due to long communication lags and blackouts, harsh environments (radiation, cold), and more limited battery and hardware life. The past decade has seen great advances in both AI technologies and computing scalability and performance that offer promising solutions for spacecraft autonomy and motivate the software system and research programs described in this paper. The Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS) [1], which has been in development at the NASA Ames Research Center since 2018, is a virtual environment for testing lander autonomy solutions. It is built on the Robot Operating System (ROS), runs on consumer-grade Linux workstations, and was released as open source in 2020. OceanWATERS provides a physical and visual simulation of a prototypical lander in a Europa-like environment (Figure 1). The lander was modeled after requirements and specifications made in JPL’s Europa Lander Study of 2016 [3]. Simulated lander systems include stereo cameras and spotlights mounted on an antenna mast that pans and tilts, a 6 degrees of freedom (DoF) robotic arm with a force-torque sensor and two interchangeable end effectors, and a battery pack power system. The environment consists of multiple terrain models including a highly detailed model sourced from the FROST dataset [11], simulation of surrounding planetary bodies based on an ephemeris model, and lighting from the sun with associated surface illumination, reflectance, and shadows. Operations supported by OceanWATERS include panoramic and directed imaging of the environment and lander workspace, Cartesian and joint-level arm commanding, grinding of the terrain surface (e.g. digging a trench), and scooping of ground material (Figure 2) which can be discarded or collected as science samples in a receptacle that can be emptied (science operations themselves are not simulated). These operations are realized as ROS Actions and are complimented by a wide selection of telemetry that is continually produced by each lander subsystem. The power system model is driven by the open-source Generic Software Architecture for Prognostics (GSAP) [11] that predicts the battery’s remaining useful life and other characteristics. As a testbed for high-level autonomy, OceanWATERS provides an execution framework based on PLEXIL [12], an open-source plan specification language and execution engine developed largely at Ames. NASA's initial development of OceanWATERS, as well the Ocean Worlds Lander Autonomy Testbed (OWLAT) [6], a complimentary physical testbed developed at JPL, was the first step in a plan for realizing candidate onboard autonomy solutions for such planetary landers. In 2020 NASA solicited applications for its Autonomous Robotics Research for Ocean Worlds (ARROW) program, and in 2021 the similar Concepts for Ocean worlds Life Detection Technology (COLDTech) program. Collectively six research teams, based in universities and companies across the United States, were awarded grants to develop and demonstrate autonomy solutions on OceanWATERS and OWLAT. These 1–2-year projects have now finished or are nearing completion, and a wide variety of autonomy challenges in ocean world surface missions were addressed. Prototyped and demonstrated solutions have included autonomous discovery, response and adaptation to system faults and unexpected environmental events, world model synthesis through perception, plan synthesis using learned models, methods to optimize sample target selection and prioritize science data transmission, extension of PLEXIL for stochastic decision-making, and an integration of a model of JPL’s mission-ready COLDArm [7]. Technologies used in these projects include many forms of machine learning, causal reasoning, automated planning, Markov decision processes, formal methods, and other advanced techniques. A more detailed summary of the ARROW and COLDTech projects is given herein. OceanWATERS has had significant enhancements since its open-source release in 2020. Many of its new features were driven or shaped by feedback from the ARROW and COLDTech teams and requirements of their projects. In support of enabling autonomous adaptation to spacecraft faults (a specific capability solicited by both programs), a fault injection and detection framework was developed that supports a wide and growing range of fault types such as locked joints, image loss, and battery failures. The power system model was completed and integrated into the simulator, starting as a single-cell battery model and later upgraded to a multi-cell model with associated faults such as cell disconnection. Arm/terrain interaction was improved by adding a force-torque sensor and associated faults, and an analytic dig force model based on the Balovnev bucket force equations. Environment fidelity was increased by modeling terrain deformation resulting from digging and scooping; visual improvements were made in textures, lighting, and shadows. To facilitate interoperation with OWLAT, a unified command and telemetry interface between the testbeds was developed at the ROS level, along with a PLEXIL interface. The number of lander operations was greatly expanded (e.g. with Cartesian-based arm and antenna movement), and a framework was designed for users to build their own lander actions. A GUI for PLEXIL plan selection was created (Figure 3), and an expansive set of plans were added, such as those that illustrate patterns for fault handling. This paper provides a self-contained high-level description of OceanWATERS, focusing on more detailed coverage of the aforementioned enhancements. It provides a high-level summary of the projects undertaken by participants in the ARROW and COLDTech programs and how these efforts have helped shape OceanWATERS. Finally, potential future work and directions for the testbed are listed, as likely informed by the recent planetary science decadal survey [5].

K Michael Dalal↗

Strategy for Developing Technologies for Megawatt-class Nuclear Electric Propulsion Systems

In late fiscal year 2020, the Space Nuclear Propulsion (SNP) project began the process of formulating an investment strategy to support development of the technologies required for a high-power (megawatt-class) nuclear electric propulsion (NEP) system capable of performing human-scale missions. This activity was initiated concurrent with several high-level studies and assessments were either under way or had just concluded. Studies of human-scale Mars missions have been performed several times over the past two decades. One of the most recent studies examined opposition-class human Mars missions to occur in the late 2030s timeframe [1,2]. The mission architecture assumed a hybrid NEP/chem-propelled vehicle that used a high specific impulse (Isp) NEP-system and a liquid oxygen (LOx)-liquid methane high thrust chemical stage (two 110 kN (25 klbf) thrust, 365 s Isp engines) for maneuvers performed to enter and exit gravity wells. Trajectory analyses performed in this study showed that such a mission could be performed with 2-4 MWe directed into the electric propulsion system (operating for 20,000+ hours), with the large range representing different opposition-class Mars mission opportunities and permutations on the trajectory design, concept of operations, and technology choices. In 2020, the NASA Engineering and Safety Center (NESC) performed a study to evaluate the maturity of the different technologies required for nuclear propulsion systems [3]. The executive summary of this report provided the following top-level conclusions: • “The majority of critical technologies for… NEP/Chem… systems are relatively immature” • “TRLs [technology readiness levels] in the literature are often overestimated” • “The majority of critical technologies… for NEP/Chem… systems are at a relatively high level of advancement degree of difficulty (AD2 > 4) for maturation, requiring a dual development approach” • “The proper assessment of baseline TRL and AD2 values and the estimation of requirements and resources required for advancement have been consistent issues for NEP,” • “Non-advocate reviews should occur at the start of a technology program and at all key milestones.” In 2021, the National Academies of Science, Engineering, and Medicine (NASEM) issued a separate report [4] identifying the “primary technical and programmatic challenges, merits, and risks for maturing space nuclear propulsion technologies of interest to a future human Mars exploration mission.” That work contained several important findings, including: • “Developing a MWe-class NEP system for the baseline mission would require increasing power by orders of magnitude relative to NEP system flight- or ground-based technology demonstrations completed to date.” • “Subscale in-space flight testing of NEP systems cannot address many of the risks and potential failure modes associated with the baseline mission NEP system. With sufficient M&S [modeling & simulation] and ground testing, including modular subsystem tests at full scale and power, flight qualification requirements can be met by the cargo missions that will precede the first crewed mission to Mars. Fully integrated ground testing may not be required.” • “As a result of low and intermittent investment over the past several decades, it is unclear if even an aggressive program would be able to develop an NEP system capable of executing the baseline mission in 2039.” These efforts motivated the SNP project to investigate the technologies available for a megawatt-class high power nuclear electric propulsion system. That system is illustrated schematically in Figure 1 and is comprised of five separate top-level critical technology elements (CTEs). 1. Nuclear Reactor – Thermal power source for the system, utilizing high-assay low enriched uranium (HALEU) as the nuclear fuel. Reactor radiation shielding is also included in this CTE. 2. Power Conversion – Operates as a thermodynamic cycle, accepting nuclear reactor thermal power as an input and converting it to mechanical power. 3. Power Management and Distribution (PMAD) – Accepts as an input mechanical power from the power conversion system, which is used to generate electrical power. The PMAD system also distributes the generated electrical power to all other parts of the spacecraft, including the high-power EP system. The PMAD system may also perform duties such as isolation, fault detection, and power transformation/rectification for different spacecraft systems, including the thrusters. 4. Electric Propulsion (EP) – Accepts as an input electrical power, which is used to accelerate a propellant to high speeds to produce thrust. This system includes the power processing unit (PPU), which converts the power it receives to the correct current and voltage required by the thrusters, and the propellant storage and feed systems, which contain and meter the flow of propellant to the thrusters. 5. Thermal Management (Radiators/Heat Rejection) – The cold side of the thermodynamic power conversion cycle, accepts thermal power from the power conversion system and radiatively rejects that heat to space. In this paper, we describe the SNP project formulation and investment strategy that aims to accomplish the research and development required to advance the technology readiness for each CTE. The strategy relies heavily upon experimental testing supported by modeling and simulation to yield realistic assessments of the technologies, which in turn will be used to inform future NEP system-level design decisions and any potential technology downselects.

Kurt A Polzin↗

Enhancements and Evolution of the Real Time Mission Monitor

The Real Time Mission Monitor (RTMM) is a visualization and information system that fuses multiple Earth science data sources, to enable real time decision-making for airborne and ground validation experiments. Developed at the National Aeronautics and Space Administration (NASA) Marshall Space Flight Center, RTMM is a situational awareness, decision-support system that integrates satellite imagery, radar, surface and airborne instrument data sets, model output parameters, lightning location observations, aircraft navigation data, soundings, and other applicable Earth science data sets. The integration and delivery of this information is made possible using data acquisition systems, network communication links, network server resources, and visualizations through the Google Earth virtual globe application. RTMM has proven extremely valuable for optimizing individual Earth science airborne field experiments. Flight planners, mission scientists, instrument scientists and program managers alike appreciate the contributions that RTMM makes to their flight projects. We have received numerous plaudits from a wide variety of scientists who used RTMM during recent field campaigns including the 2006 NASA African Monsoon Multidisciplinary Analyses (NAMMA), 2007 Tropical Composition, Cloud, and Climate Coupling (TC4), 2008 Arctic Research of the Composition of the Troposphere from Aircraft and Satellites (ARCTAS) missions, the 2007-2008 NOAA-NASA Aerosonde Hurricane flights and the 2008 Soil Moisture Active-Passive Validation Experiment (SMAP-VEX). Improving and evolving RTMM is a continuous process. RTMM recently integrated the Waypoint Planning Tool, a Java-based application that enables aircraft mission scientists to easily develop a pre-mission flight plan through an interactive point-and-click interface. Individual flight legs are automatically calculated for altitude, latitude, longitude, flight leg distance, cumulative distance, flight leg time, cumulative time, and satellite overpass intersections. The resultant flight plan is then generated in KML and quickly posted to the Google Earth-based RTMM for interested scientists to view the planned flight track and then compare it to the actual real time flight progress. A description of the system architecture, components, and applications along with reviews and animations of RTMM during the field campaigns, plus planned enhancements and future opportunities will be presented.

Goodman, Michael↗

ESAS-Derived Earth Departure Stage Design for Human Mars Exploration

The Vision for Space Exploration has set the nation on a course to have humans on Mars as early as 2030. To reduce the cost and risk associated with human Mars exploration, NASA is planning for the Mars architecture to leverage the lunar architecture as fully as possible. This study takes the defined launch vehicles and system capabilities from ESAS and extends their application to DRM 3.0 to design an Earth Departure Stage suitable for the cargo and crew missions to Mars. The impact of a propellant depot in LEO was assessed and sLzed for use with the EDS. To quantitatively assess and compare the effectiveness of alternative designs, an initial baseline architecture was defined using the ESAS launch vehicles and DRM 3.0. The baseline architecture uses three NTR engines, LH2 propellant, no propellant depot in LEO, and launches on the Ares I and Ares V. The Mars transfer and surface elements from DRM 3.0 were considered to be fixed payloads in the design of the EDS. Feasible architecture alternatives were identified from previous architecture studies and anticipated capabilities and compiled in a morphological matrix. ESAS FOMs were used to determine the most critical design attributes for the effectiveness of the EDS. The ESAS-derived FOMs used in this study to assess alternative designs are effectiveness and performance, affordability, reliability, and risk. The individual FOMs were prioritized using the AHP, a method for pairwise comparison. All trades performed were evaluated with respect to the weighted FOMs, creating a Pareto frontier of equivalently ideal solutions. Additionally, each design on the frontier was evaluated based on its fulfillment of the weighted FOMs using TOPSIS, a quantitative method for ordinal ranking of the alternatives. The designs were assessed in an integrated environment using physics-based models for subsystem analysis where possible. However, for certain attributes such as engine type, historical, performance-based mass estimating relations were more easily employed. The elements from the design process were integrated into a single loop, allowing for rapid iteration of subsystem analyses and compilation of resulting designs.

Flaherty, Kevin↗

Strategic Deconfliction Performance: Results and Analysis from the NASA UTM Technical Capability Level 4 Demonstration

Unmanned Aircraft System (UAS) Traffic Management (UTM) refers to the service-based, cooperative approach to the management of small UAS in the National Airspace System that is safe, scalable, and fair. UTM provides the means to manage the airspace in a complementary manner that does not burden the current air traffic control workforce or infrastructure but allows the Air Navigation Service Provider to maintain its regulatory and operational authority of the airspace. A key feature of UTM is the ability to provide operators the means to strategically deconflict operations from others in the airspace through the digital exchange of information via supporting services. Through this approach, the four-dimensional operation volumes that encompass the intent of operators in a given area are discoverable and can be used for airspace awareness as well as planning conflict free operations that account for and avoid other operations. In certain cases, it is also possible to negotiate volume intersections for shared airspace use without the need to re-plan. In the NASA UTM concept, strategic deconfliction is the first layer of three in the overall conflict management model. The three layers of the conflict management model, which follow the International Civil Aviation Organization’s scheme [ICAO 2005] are: strategic conflict management, separate provision, and collision avoidance. In UTM, the strategic layer mostly occurs prior to departure, but is applicable to en route operations with sufficient planning horizon. The initial requirements for a strategic deconfliction capability within UTM are defined in a NASA publication [Rios 2018]. Within the concept and implementation of service-provided strategic deconfliction is the notion of priority. It is understood that there are instances in which an operation requires a priority designation within the UTM system and special handling accordingly to provide situation awareness and facilitate appropriate responses from other airspace users. Examples of situations requiring priority designation include: when an operator declares an emergency due to problems with the vehicle or its immediate surroundings; operations that are in support of certain organizations (e.g., public safety and first responders); or special missions that also require priority use of airspace (e.g., emergency medical deliveries). UAS Volume Reservations (UVRs) also relate to the topic of priority in the sense that the airspace that the volume encompasses has a different status or classification in which unassociated operations must vacate if inside, or avoid if outside, through strategic deconfliction with the volume. Operations that are specially permitted to access the UVR area are typically assigned priority status given the nature of their mission and their associated credentials. The ability to perform strategic deconfliction, handle certain operations with a priority distinction, and establish UVRs that are communicated throughout the UTM system, is predicated on an architecture that has been established through an evolutionary process in response to close collaboration with stakeholders from government and industry. Another important and influential aspect of these capabilities and architecture is the live, distributed flight tests that have been conducted across the Technical Capability Levels (TCLs) that culminated with a set of complex tests performed as part of TCL4 [Rios 2020]. The TCL4 flight test involved two FAA-designated UAS test sites building teams to collaborate with NASA’s UTM Project on the execution of several detailed, small UAS scenarios in urban environments.

conflict management↗

Orion Absolute Navigation System Progress and Challenge

The absolute navigation design of NASA's Orion vehicle is described. It has undergone several iterations and modifications since its inception, and continues as a work-in-progress. This paper seeks to benchmark the current state of the design and some of the rationale and analysis behind it. There are specific challenges to address when preparing a timely and effective design for the Exploration Flight Test (EFT-1), while still looking ahead and providing software extensibility for future exploration missions. The primary onboard measurements in a Near-Earth or Mid-Earth environment consist of GPS pseudo-range and delta-range, but for future explorations missions the use of star-tracker and optical navigation sources need to be considered. Discussions are presented for state size and composition, processing techniques, and consider states. A presentation is given for the processing technique using the computationally stable and robust UDU formulation with an Agee-Turner Rank-One update. This allows for computational savings when dealing with many parameters which are modeled as slowly varying Gauss-Markov processes. Preliminary analysis shows up to a 50% reduction in computation versus a more traditional formulation. Several state elements are discussed and evaluated, including position, velocity, attitude, clock bias/drift, and GPS measurement biases in addition to bias, scale factor, misalignment, and non-orthogonalities of the accelerometers and gyroscopes. Another consideration is the initialization of the EKF in various scenarios. Scenarios such as single-event upset, ground command, and cold start are discussed as are strategies for whole and partial state updates as well as covariance considerations. Strategies are given for dealing with latent measurements and high-rate propagation using multi-rate architecture. The details of the rate groups and the data ow between the elements is discussed and evaluated.

Holt, Greg N.↗