Polaris Project: Autonomous Satellite Technology for Resilient Application (ASTRA)
Explore the source record for details and available documents.
flight following mode↗
Engineering topics
Fernando Figueroa
Publications and source records attributed to Fernando Figueroa.
Artificial Thought is Required for Sustained Autonomy
Current literature primarily addresses what is referred to as “Systems Thinking.” Dr. Marie Morganelli from Southern New Hampshire University states that “Systems thinking is a holistic way to investigate factors and interactions that could contribute to a possible outcome [1]. A mindset more than a prescribed practice, systems thinking provides an understanding of how individuals can work together in different types of teams and through that understanding, create the best possible processes to accomplish just about any-thing.” So, a “Thinking System” is a system that is capable of “systems thinking,” as it should be able to “ …create [utilize] the best possible processes, and possess the [intelligence] to accomplish just about anything.” To achieve this capability, hu-man-like thinking is required. A truly autonomous system must be one that is capable of human-like thinking. Sustained autonomy requires “Thinking Autonomy” (TA) that is enabled by a “Thinking System.”
Autonomous systems↗
Autonomy Voice Assistant for NPAS (NASA Platform for Autonomous Systems)
A prototype voice interaction system, Autonomy Voice Assistant (AVA), is described in this paper. AVA is designed to seamlessly integrate into the NASA Platform for Autonomous Systems (NPAS), an autonomy software platform, and to enable an operator to interact with NPAS autonomy applications through voice conversations. By integrating VA with NPAS, a major enhancement to NPAS applications is facilitated, enabling interaction through natural language expressions. An AVA prototype has been designed incorporating two principles:(1) self-containment (no external data or computations required), and (2) a readily modifiable, reconfigurable, and flexible architecture. By using voice messages in an NPAS application, an additional layer of user interface capability is enabled, thereby enhancing a user’s overall experience. Advancements, over the past several decades in speech recognition and natural language processing technologies has made it possible for AVA to implement robust messaging capabilities while still being lightweight. The main objective of incorporating a voice assistant like AVA is to augment the number and effectiveness of interactions a user has with a system that typically uses mouse-based interaction, while simultaneously enriching the user experience and providing heightened system awareness.
Lucian Murdock↗
A Case Study on the Challenges and Opportunities for the Deployment of PHM Capabilities in Existing Engineering Systems
The field of Prognostics and Health Management (PHM) of engineering systems has experienced considerable growth over the last decade. From benefits associated with faster and more powerful hardware in the form of wireless sensors, edge devices, and general computing capabilities (GPU’s and cloud computing), to development of powerful algorithms for anomaly detection and remaining useful life (RUL) estimation, the number of engineering systems featuring advanced diagnostics and prognostics capabilities continues to grow at an increasingly faster pace. However, the deployment of PHM capabilities as part of the upgrade of existing engineering systems presents multiple challenges to the PHM practitioner charged with retrofitting such systems. Issues include a lack of specific instrumentation needed to capture the signals of interest; insufficient data and sampling rates required for fault detection and diagnosis, and for detection of failure/degradation indicators; and difficulties in the identification of a system’s nominal behavior as a result of age induced degradation. Today’s PHM practitioner must be able to quickly identify and assess these types of issues to effectively evaluate and select the optimal PHM strategies required to achieve the desired results. This paper presents results from the preliminary evaluation of the High-Pressure Gas Facility (HPGF) infrastructure at NASA’s Stennis Space Center in Hancock County, Mississippi. This evaluation is part of a feasibility study conducted prior to the deployment of prognostics and diagnostics capabilities in the pumps skids of the liquid nitrogen (LN2) system of the HPGF.
Condition Based Maintenance↗
Model-Based Systems Engineering, Real-Time Operations, and Autonomy
Model-Based Systems Engineering has been enabled by the development of the SysML language and software tools to create systems models. Systems models described in SysML incorporate frames (Diagrams) that represent behaviors (activities, sequences, state machines, use cases), requirements, and structure (definitions, internal structure, parametric formulation, and packaging). The SysML models are, in turn, used by applications to do analysis and studies of the designs and operational capabilities. These uses of the model are based on simulations, and do not include hardware. This paper presents a software environment and processes that enables more comprehensive systems models for MBSE, and use of these rich models for real-time operations. The paper describes a software platform that enables creation of comprehensive models, beyond what is now possible with SysML and related software tools, called the NASA Platform for Autonomous Systems (NPAS). The platform encapsulates a paradigm and infrastructure for creating systems models with complexity levels comparable to the ones handled by SysML software tools, but with additional fidelity that includes detailed design diagrams encompassing sensors, components, and design topologies. Furthermore, NPAS enables incorporation of data, information, and knowledge (DIaK) to implement autonomy and Integrated System Health Management (ISHM) and the inherent integration of content encompassing SysML structure and behavior diagrams throughout the NPAS modelAnd lastly, the NPAS models are used in real-time operations, taking advantage of the fidelity and complexity encompassed in the models in order to implement “thinking” ISHM and/or autonomous operations. . Incorporation of SysML model content into an NPAS model is briefly discussed.
MBSE↗
Model-Based Systems Engineering, Real-Time Operations and Autonomy
Explore the source record for details and available documents.
MBSE↗
A Case Study on the Challenges and Opportunities for the Deployment of PHM Capabilities in Existing Engineering Systems
Explore the source record for details and available documents.
Federico Piatti↗
NPAS - NASA Platform for Autonomous Systems
Explore the source record for details and available documents.
Fernando Figueroa↗
Enabling a Voice Management System for Space Applications, Design and Software Development
Sustainable missions, beyond low Earth orbit, will require autonomous capabilities in order to achieve NASA’s Artemis program objectives. Correspondingly, the crew must have a means to efficiently interact with these autonomous systems; this can be facilitated via voice and speech communications. Voice-based controls enable the user to access autonomous systems hands-free/eyes-free, allowing the user to better focus on critical tasks. The goal of this project was to explore the knowledge and technology needed to successfully design effective voice interfaces for autonomous systems. The main objective was to understand how a crew member, through voice interaction, could most efficiently and intuitively communicate with a notional autonomous vehicle system manager. This project leveraged prior research conducted by the University of Michigan’s Bioastronautics and Life Support System (BLiSS) team as part of a NASA Moon to Mars eXploration Systems and Habitation (M2M X-Hab) 2020 Academic Innovation Challenge. The X-Hab 2020 work from the BliSS Team resulted in an intuitive graphical user interface/user experience that was built on an Internet of Things (IOT) platform. The Voice User Interface (VUI) design for the M2M X-Hab 2021 project leveraged this technology and incorporated a voice-based assistant and NASA’s Platform for Autonomous Systems (NPAS) software. This required technologies to convert voice to text, conduct semantic interpretations, and convert responses from the autonomous system to text and to speech; additionally, the background noise environment of spacecraft was assessed, and a relatable personality for the autonomous system to facilitate human-like conversations was created. This work’s success was largely due to the diverse team that included expertise in Space Systems Engineering, Human Computer Interaction, Aerospace Engineering, Computer Science, Biomedical Engineering, and Applied Physics. The differing perspectives fostered elaborate discussions, resulting in the conception of three main interactions: (1) User-System, (2) NPAS-System, and (3) Environment-System. The system developed, i.e. the VUI, had to be unique, efficient, and intuitive; thus, the team crafted a personality for the system to enable human-like conversation. User surveys sent to students and young professionals were used to help determine these personality traits by capturing perspectives and expectations of the “Artemis Generation Astronauts”. To further simulate human-like conversations, the system had to be able to quickly interpret user speech and be able to integrate with NASA’s NPAS system for quick and reliable information transfer. Results of this research include (1) a working prototype user interface, that is compatible with NASA’s NPAS system; (2) software that demonstrates the ability to interpret user requests and respond appropriately; (3) the capability to implement fully expanded conversations between user and system using intuitive communication in four request categories; and (4) software and hardware recommendations that optimize the system’s ability to operate, i.e. be heard, in a noisy environment. The technologies chosen for this project’s demonstrations included the following: Raspberry Pi, RASA, Mozilla Deep Speech, Coqui, RTX Voice and Adobe XD. This work has laid the foundation for the development of VUI’s used for autonomy, and is intended to provide guidance for future VUI development.
Tara Vega↗
Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions
To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.
Autonomous Systems↗
Thinking Autonomous Systems
Explore the source record for details and available documents.
Fernando Figueroa↗
Sistemas Autónomos Pensantes
Explore the source record for details and available documents.
Fernando Figueroa↗
Enabling a Voice Management System for Space Applications
The sustainable missions beyond Low Earth Orbit (LEO) envisioned for NASA’s Artemis program will require autonomous capabilities. Moreover, Artemis mission crews will need a means to efficiently interact with a spacecraft’s autonomous systems. This interaction can be facilitated by voice and speech communications because voice-based controls enable users to interact hands- and eyes-free, allowing the user to better focus on critical tasks. The goal of our project was to explore the knowledge and technology needed to successfully design effective Voice User Interfaces (VUIs) for autonomous systems utilizing Human Centered Design (HCD) principles. The focus of the human factors’ aspect of engineering, pays close attention to psychological and physiological principles in the development of autonomous crew operation systems. A main objective was to understand how a crew member, through voice interaction, could efficiently and intuitively communicate with a notional autonomous vehicle system manager. This project was a part of the NASA Moon to Mars eXploration Systems and Habitation (M2M X-Hab) 2020 Academic Innovation Challenge. The work from the BLiSS Team, at the University of Michigan, resulted in the design of a system persona, Diego, to which an astronaut may quickly build trust with autonomous systems, to alleviate known stressors on mental health expected during long duration space missions. Optimal software to facilitate integration of the system persona into a reference Lunar orbiting Gateway station was defined. Additionally, a Speech to Text (STT) system and a Graphical User Interface (GUI) that could be implemented in future missions was developed on an Internet of Things (IOT) platform. The Voice User Interface (VUI) design for the M2M X-Hab 2020 project leveraged previous technology developed by the BLiSS team to incorporate a voice-based interface into NASA’s Platform for Autonomous Systems (NPAS) software. This required technologies to convert voice to text, conduct semantic interpretations, and convert responses from the autonomous system to text and to speech; additionally, the spacecraft background noise environment was assessed, a noise mitigation technique was developed, and a relatable personality for the autonomous system was developed in order to facilitate human-like conversations. The success of our effort was largely due to the diversity of the team that included expertise in Space Systems Engineering, Human Computer Interaction, Aerospace Engineering, Computer Science, Biomedical Engineering, and Applied Physics. The diverse perspectives fostered elaborate discussions, resulting in the conception of three main subsystems: (1) User-System, (2) NPAS-System, and (3) Environment-System. The VUI was unique and had to be efficient and intuitive. For this project, 5 subteams were formed, each with a separate objective, Voice Design team, Background Noise Mitigation team, Software Integration team and Graphical User Interface team. The BLiSS team crafted a personality for the VUI to enable human-like conversation and drive user adoption and trust. User surveys were completed and used to help determine the required VUI system personality traits by capturing perspectives and expectations of prospective “Artemis Generation Astronauts”. To further simulate human-like conversations, the system had to be able to quickly interpret user speech and be able to integrate with NASA’s NPAS platform for quick and reliable information transfer. The outcomes of our research were: (1) a working prototype user interface, that is compatible with NASA’s NPAS platform; (2) software that demonstrates the ability of the VUI system to interpret user requests and respond appropriately; (3) the capability to implement fully expanded conversations between user and system using intuitive communication in four request categories; and (4) software and hardware recommendations that optimize the system’s ability to operate in a noisy environment. Our research has laid the foundation for the development of VUI’s for autonomy, and provides a baseline for future VUI developments.
Voice user interface↗
Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions
To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.
Fernando Figueroa↗
Comportamiento Autónomo con Sistemas Pensantes
Explore the source record for details and available documents.
Fernando Figueroa↗
Trusted Autonomy and the NASA Platform for Autonomous Systems (NPAS)
Explore the source record for details and available documents.
Fernando Figueroa↗
A Decision Support System for Extravehicular Operations Under Significant Communication Latency
Within the next few decades, humanity hopes to perform extravehicular activities (EVAs) on the surface of Mars; however, several technical and operational challenges must first be overcome. Foremost among these challenges is managing a significant two-way communication latency between Earth and Mars. Current and historical paradigms of EVA operations have required near-real-time communication between the crewmember(s) performing an EVA and an Earth-based mission control. Next-generation operational paradigms for supporting deep space exploration will necessitate a distributed decision authority system, including delayed Earth-based mission control, the on-planet extravehicular crewmember(s), and intermediate mission support from intravehicular crewmember(s) within real-time communication range. This latter group is of particular interest: they must provide operations support without the plentiful resources available to mission control on Earth. For this purpose, NASA is developing the Personalized EVA Informatics and Decision Support (PersEIDS) software platform. PersEIDS is designed to bolster operator situational awareness and offload operator workload by automating the tracking and projection of consumables usage over an EVA timeline, providing real-time probabilistic safety assessments of an EVA timeline given consumables constraints, and recommending alternative EVA timeline(s) when the active timeline is not expected to be completed under consumables limits. The PersEIDS concept of operations, use cases, and models will be presented. A limited version of PersEIDS was demonstrated during a three-day-long study where each day a roughly four-hour-long simulated Martian EVA was performed in virtual reality at the NASA Johnson Space Center. The first day was a control trial without PersEIDS support; the second and third days represented different levels of decision support provided by PersEIDS to the intravehicular crewmember acting as mission control. With PersEIDS support, the IV crewmember was able to manage the mission to completion faster and with more remaining consumables; however, additional testing is required to understand confounding factors, e.g. training bias.
Mars↗
A Thinking System and Thinking Autonomy
There are many definitions of what a “Thinking System” (TS) is. The literature primarily addresses what is called “Systems Thinking.” Dr. Marie Morganelli from Southern New Hampshire University states that “Systems thinking is a holistic way to investigate factors and interactions that could contribute to a possible outcome. A mindset more than a prescribed practice, systems thinking provides an understanding of how individuals can work together in different types of teams and through that understanding, create the best possible processes to accomplish just about anything.” So, a TS is a system that is capable of “systems thinking,” as it should be able to “ … create [utilize] the best possible processes [and intelligence] to accomplish just about anything.” To achieve this capability, human-like thinking is required. A truly autonomous system must be one that is capable of human-like thinking. This paper will address “Thinking Autonomy” (TA) enabled by a “Thinking System.” It will describe an architecture with the elements required to achieve the “thinking” behavior: understanding, intellect, reason, decision, will. The paper will further describe the contents and functionality of these elements and how to implement them, including software capabilities needed. Finally, the paper will provide details of a software platform that enables TA, the NASA Platform for Autonomous Systems (NPAS), and describe implementations of thinking systems. Thinking systems will enable a fundamental change how AI and autonomy are implemented. It will change from a “brute force” approach that results in one-time implementations that are minimally intelligent or autonomous to a “thinking” approach where implementations evolve continuously and enable powerful intelligence and autonomy on systems of high complexity as well as on systems-of-systems.
Thinking systems↗