Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Maintenance”

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 595 records · Page 33

The Interplanetary Overlay Networking Protocol Accelerator

A document describes the Interplanetary Overlay Networking Protocol Accelerator (IONAC) an electronic apparatus, now under development, for relaying data at high rates in spacecraft and interplanetary radio-communication systems utilizing a delay-tolerant networking protocol. The protocol includes provisions for transmission and reception of data in bundles (essentially, messages), transfer of custody of a bundle to a recipient relay station at each step of a relay, and return receipts. Because of limitations on energy resources available for such relays, data rates attainable in a conventional software implementation of the protocol are lower than those needed, at any given reasonable energy-consumption rate. Therefore, a main goal in developing the IONAC is to reduce the energy consumption by an order of magnitude and the data-throughput capability by two orders of magnitude. The IONAC prototype is a field-programmable gate array that serves as a reconfigurable hybrid (hardware/ firmware) system for implementation of the protocol. The prototype can decode 108,000 bundles per second and encode 100,000 bundles per second. It includes a bundle-cache static randomaccess memory that enables maintenance of a throughput of 2.7Gb/s, and an Ethernet convergence layer that supports a duplex throughput of 1Gb/s.

Pang, Jackson↗

Systems, methods and apparatus for generation and verification of policies in autonomic computing systems

Described herein is a method that produces fully (mathematically) tractable development of policies for autonomic systems from requirements through to code generation. This method is illustrated through an example showing how user formulated policies can be translated into a formal mode which can then be converted to code. The requirements-based programming method described provides faster, higher quality development and maintenance of autonomic systems based on user formulation of policies.Further, the systems, methods and apparatus described herein provide a way of analyzing policies for autonomic systems and facilities the generation of provably correct implementations automatically, which in turn provides reduced development time, reduced testing requirements, guarantees of correctness of the implementation with respect to the policies specified at the outset, and provides a higher degree of confidence that the policies are both complete and reasonable. The ability to specify the policy for the management of a system and then automatically generate an equivalent implementation greatly improves the quality of software, the survivability of future missions, in particular when the system will operate untended in very remote environments, and greatly reduces development lead times and costs.

Hinchey, Michael G.↗

COSMIC monthly progress report

Activities of the Computer Software Management and Information Center (COSMIC) are summarized for the month of May 1994. Tables showing the current inventory of programs available from COSMIC are presented and program processing and evaluation activities are summarized. Nine articles were prepared for publication in the NASA Tech Brief Journal. These articles (included in this report) describe the following software items: (1) WFI - Windowing System for Test and Simulation; (2) HZETRN - A Free Space Radiation Transport and Shielding Program; (3) COMGEN-BEM - Composite Model Generation-Boundary Element Method; (4) IDDS - Interactive Data Display System; (5) CET93/PC - Chemical Equilibrium with Transport Properties, 1993; (6) SDVIC - Sub-pixel Digital Video Image Correlation; (7) TRASYS - Thermal Radiation Analyzer System (HP9000 Series 700/800 Version without NASADIG); (8) NASADIG - NASA Device Independent Graphics Library, Version 6.0 (VAX VMS Version); and (9) NASADIG - NASA Device Independent Graphics Library, Version 6.0 (UNIX Version). Activities in the areas of marketing, customer service, benefits identification, maintenance and support, and dissemination are also described along with a budget summary.

Source record↗

Fault Detection and Correction for the Solar Dynamics Observatory Attitude Control System

The Solar Dynamics Observatory is an Explorer-class mission that will launch in early 2009. The spacecraft will operate in a geosynchronous orbit, sending data 24 hours a day to a devoted ground station in White Sands, New Mexico. It will carry a suite of instruments designed to observe the Sun in multiple wavelengths at unprecedented resolution. The Atmospheric Imaging Assembly includes four telescopes with focal plane CCDs that can image the full solar disk in four different visible wavelengths. The Extreme-ultraviolet Variability Experiment will collect time-correlated data on the activity of the Sun's corona. The Helioseismic and Magnetic Imager will enable study of pressure waves moving through the body of the Sun. The attitude control system on Solar Dynamics Observatory is responsible for four main phases of activity. The physical safety of the spacecraft after separation must be guaranteed. Fine attitude determination and control must be sufficient for instrument calibration maneuvers. The mission science mode requires 2-arcsecond control according to error signals provided by guide telescopes on the Atmospheric Imaging Assembly, one of the three instruments to be carried. Lastly, accurate execution of linear and angular momentum changes to the spacecraft must be provided for momentum management and orbit maintenance. In th~sp aper, single-fault tolerant fault detection and correction of the Solar Dynamics Observatory attitude control system is described. The attitude control hardware suite for the mission is catalogued, with special attention to redundancy at the hardware level. Four reaction wheels are used where any three are satisfactory. Four pairs of redundant thrusters are employed for orbit change maneuvers and momentum management. Three two-axis gyroscopes provide full redundancy for rate sensing. A digital Sun sensor and two autonomous star trackers provide two-out-of-three redundancy for fine attitude determination. The use of software to maximize chances of recovery from any hardware or software fault is detailed. A generic fault detection and correction software structure is used, allowing additions, deletions, and adjustments to fault detection and correction rules. This software structure is fed by in-line fault tests that are also able to take appropriate actions to avoid corruption of the data stream.

Starin, Scott R.↗

ISS Regenerative Life Support: Challenges and Success in the Quest for Long-Term Habitability in Space

This presentation will discuss the International Space Station s (ISS) Regenerative Environmental Control and Life Support System (ECLSS) operations with discussion of the on-orbit lessons learned, specifically regarding the challenges that have been faced as the system has expanded with a growing ISS crew. Over the 10 year history of the ISS, there have been numerous challenges, failures, and triumphs in the quest to keep the crew alive and comfortable. Successful operation of the ECLSS not only requires maintenance of the hardware, but also management of the station resources in case of hardware failure or missed re-supply. This involves effective communication between the primary International Partners (NASA and Roskosmos) and the secondary partners (JAXA and ESA) in order to keep a reserve of the contingency consumables and allow for re-supply of failed hardware. The ISS ECLSS utilizes consumables storage for contingency usage as well as longer-term regenerative systems, which allow for conservation of the expensive resources brought up by re-supply vehicles. This long-term hardware, and the interactions with software, was a challenge for Systems Engineers when they were designed and require multiple operational workarounds in order to function continuously. On a day-to-day basis, the ECLSS provides big challenges to the on console controllers. Main challenges involve the utilization of the resources that have been brought up by the visiting vehicles prior to undocking, balance of contributions between the International Partners for both systems and resources, and maintaining balance between the many interdependent systems, which includes providing the resources they need when they need it. The current biggest challenge for ECLSS is the Regenerative ECLSS system, which continuously recycles urine and condensate water into drinking water and oxygen. These systems were brought to full functionality on STS-126 (ULF-2) mission. Through system failures and recovery, the ECLSS console has learned how to balance the water within the systems, store and use water for contingencies, and continue to work with the International Partners for short-term failures. Through these challenges and the system failures, the most important lesson learned has been the importance of redundancy and operational workarounds. It is only because of the flexibility of the hardware and the software that flight controllers have the opportunity to continue operating the system as a whole for mission success.

Bazley, Jesse A.↗

Method and system for diagnostics of apparatus

Proposed is a method, implemented in software, for estimating fault state of an apparatus outfitted with sensors. At each execution period the method processes sensor data from the apparatus to obtain a set of parity parameters, which are further used for estimating fault state. The estimation method formulates a convex optimization problem for each fault hypothesis and employs a convex solver to compute fault parameter estimates and fault likelihoods for each fault hypothesis. The highest likelihoods and corresponding parameter estimates are transmitted to a display device or an automated decision and control system. The obtained accurate estimate of fault state can be used to improve safety, performance, or maintenance processes for the apparatus.

Gorinevsky, Dimitry↗

Clinical Decision Support - Concepts of Operation

We are entering a new era in space exploration to return to the moon and explore Mars. These ambitious goals will require significant changes to in-flight and habitat medical care due to constraints on mass, volume, power, crew time and medical evacuation capabilities. These constraints make it absolutely necessary to develop transformative solutions using new technologies. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) pushes the boundary of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses the gap Medical-701 within the Inflight Medical Conditions risk: Enhance medical capabilities within an exploration medical system. For long-duration, deep space missions, computational and data resources will play an important role in maintaining crew health, wellness and performance where the crew will need to be more self-reliant. The aim of the CDS project is to develop and provide recommended requirements for an in-vehicle CDSS that acts as an assistant for delivering optimal health and performance and medical care during exploration missions. The CDSS is envisioned as a software-based tool that will augment a crewmembers’ knowledge, skills and abilities to assist in decision-making and crew health and performance (CHP) management thus increasing CHP systems capabilities. The human interface will be context aware and lessen the cognitive load to assimilate and use information as well as combine large disparate data sets in such a manner that provides the crew with actionable insight to decisions related to crew medical, health and performance management. Crew autonomy will be provided through a CDS that presents knowledge and data in a context aware manner to augment a crew members’ knowledge, skills and abilities during the process of observation, orientation, decisions and action. The CDS project addresses the need for crew members to operate independently during long duration space exploration missions that require medical Levels of Care (LoC) V, the highest level specified by NASA-STD-3001 and described in more detail by the ExMC interpretation of LoC document (NASA/TM-2017-219290), where significant changes to in-flight and habitat medical care necessitate increasing crew autonomy in decision making and task performance. The CDS project will develop and test a series of iterative and increasingly more complex system prototypes. These annual demonstrations of the data system integration with the crew health and performance domain will inform exploration medical system requirements for an on-board Clinical Decision Support System (CDSS) through a series of use cases that guide CDS prototype functionality. CDS concepts are based on ExMC Concept of Operations documents (presented separately) and will highlight architecture extensibility to other more complex analyses and tests using core crew health and performance integrated data management, processing and visualization capabilities. This approach also establishes how externally developed analyses and approaches could be added to expand a clinical decision support system and thus highlight how a comprehensive system can be commercially and/or globally developed. The CDS project will build upon the concept of an integrated data management approach based on the Medical Data Architecture (MDA) project to more fully address challenges associated with in-flight and habitat medical, health and performance care due to constraints on mass, volume, power, crew time and medical evacuation capabilities required for medical LoC V. These requirements will be derived through systems engineering approaches and software prototype developments over the course of the multi-year CDS project to address crew health and performance decision-making and task performance, often autonomously executed by the crew, in a manner that is consistent with the appropriate medical level of care for the mission. This presentation will provide an overview of the vision for the CDS project and highlight the initial accomplishments in project planning, implementation and requirements identification in fiscal year 2020.

clinical decision support↗

Clinical Decision Support - Overview and Update

We are entering a new era in space exploration to return to the moon and explore Mars. These ambitious goals will require significant changes to in-flight and habitat medical care due to constraints on mass, volume, power, crew time and medical evacuation capabilities. These constraints make it absolutely necessary to develop transformative solutions using new technologies. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) pushes the boundary of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses the gap Medical-701 within the Inflight Medical Conditions risk: Enhance medical capabilities within an exploration medical system. For long-duration, deep space missions, computational and data resources will play an important role in maintaining crew health, wellness and performance where the crew will need to be more self-reliant. The aim of the CDS project is to develop and provide recommended requirements for an in-vehicle CDSS that acts as an assistant for delivering optimal health and performance and medical care during exploration missions. The CDSS is envisioned as a software-based tool that will augment a crewmembers’ knowledge, skills and abilities to assist in decision-making and crew health and performance (CHP) management thus increasing CHP systems capabilities. The human interface will be context aware and lessen the cognitive load to assimilate and use information as well as combine large disparate data sets in such a manner that provides the crew with actionable insight to decisions related to crew medical, health and performance management. Crew autonomy will be provided through a CDS that presents knowledge and data in a context aware manner to augment a crew members’ knowledge, skills and abilities during the process of observation, orientation, decisions and action. The CDS project addresses the need for crew members to operate independently during long duration space exploration missions that require medical Levels of Care (LoC) V, the highest level specified by NASA-STD-3001 and described in more detail by the ExMC interpretation of LoC document (NASA/TM-2017-219290), where significant changes to in-flight and habitat medical care necessitate increasing crew autonomy in decision making and task performance. The CDS project will develop and test a series of iterative and increasingly more complex system prototypes. These annual demonstrations of the data system integration with the crew health and performance domain will inform exploration medical system requirements for an on-board Clinical Decision Support System (CDSS) through a series of use cases that guide CDS prototype functionality. CDS concepts are based on ExMC Concept of Operations documents (presented separately) and will highlight architecture extensibility to other more complex analyses and tests using core crew health and performance integrated data management, processing and visualization capabilities. This approach also establishes how externally developed analyses and approaches could be added to expand a clinical decision support system and thus highlight how a comprehensive system can be commercially and/or globally developed. The CDS project will build upon the concept of an integrated data management approach based on the Medical Data Architecture (MDA) project to more fully address challenges associated with in-flight and habitat medical, health and performance care due to constraints on mass, volume, power, crew time and medical evacuation capabilities required for medical LoC V. These requirements will be derived through systems engineering approaches and software prototype developments over the course of the multi-year CDS project to address crew health and performance decision-making and task performance, often autonomously executed by the crew, in a manner that is consistent with the appropriate medical level of care for the mission. This presentation will provide an overview of the vision for the CDS project and highlight the initial accomplishments in project planning, implementation and requirements identification in fiscal year 2020.

clinical decision support system↗

Refining the W1 and SE1 Facilities

The Engine Research Building (ERB) houses more than 60 test rigs that study all aspects of engine development. By working with Mary Gibson in the SE1 and W1A Turbine Facilities, I became aware of her responsibilities and better acquainted with the inner workings of the ERB. The SE1 Supersonic/Subsonic Wind Tunnel Facility contains 2 small wind tunnels. The first tunnel uses an atmospheric inlet, while the second uses treated 40-psig air. Both of the tunnels are capable of subsonic and supersonic operation. An auxiliary air supply and exhaust piping providing both test sections with suction, blowing, and crossfire capabilities. The current configuration of SE1 consists of a curved diffuser that studies the blockage along the endwalls. The W1A Low Speed Compressor Facility provides insight for the complex flow phenomena within its 4-stage axial compressor, sand the data obtained from W 1A is used to develop advanced models for fluid dynamic assessment. W1A is based off of a low speed research compressor developed by GE in the 1950's. This compressor has a removable casing treatment under rotor 1, which allows for various tip treatment studies. The increased size and low speed allows instrumentation to be located in the compressor s complex flow paths. Air enters the facility through a filtered roof vent, conditioned for temperature and turbulence, and then passed through the compressor W1A is described as a dynamic facility with many projects taking place simultaneously. This current environment makes it challenging to follow the various affairs that are taking place within the area. During my first 4 weeks at the NASA Glenn Research Center, I have assisted Mary Gibson in multiple tasks such as facility documents, record keeping, maintenance and upgrades. The facility has lube systems for its gearbox and compressor. These systems are critical in the successful operation of the facility. I was assigned the task of creating a facility estimate list, which included the filters and strainers required for the compressor. For my remaining time spent here, we expect to complete a facility parts listing and a virtual project summary so that W1A and SE1 will become ergonomic facilities that will make it easier for people to observe the capabilities and history of the area and the employees that operate. Bolstering our efforts in achieving these goal are the online technical tutorials, software such as Microsoft Excel. Macromedia Flash MX Macromedia Dreamweaver MX, Photoshop 6.0 and the assistance of several NASA employees.

Chambers, Rodney D.↗

Re-engineering Nascom's network management architecture

The development of Nascom systems for ground communications began in 1958 with Project Vanguard. The low-speed systems (rates less than 9.6 Kbs) were developed following existing standards; but, there were no comparable standards for high-speed systems. As a result, these systems were developed using custom protocols and custom hardware. Technology has made enormous strides since the ground support systems were implemented. Standards for computer equipment, software, and high-speed communications exist and the performance of current workstations exceeds that of the mainframes used in the development of the ground systems. Nascom is in the process of upgrading its ground support systems and providing additional services. The Message Switching System (MSS), Communications Address Processor (CAP), and Multiplexer/Demultiplexer (MDM) Automated Control System (MACS) are all examples of Nascom systems developed using standards such as, X-windows, Motif, and Simple Network Management Protocol (SNMP). Also, the Earth Observing System (EOS) Communications (Ecom) project is stressing standards as an integral part of its network. The move towards standards has produced a reduction in development, maintenance, and interoperability costs, while providing operational quality improvement. The Facility and Resource Manager (FARM) project has been established to integrate the Nascom networks and systems into a common network management architecture. The maximization of standards and implementation of computer automation in the architecture will lead to continued cost reductions and increased operational efficiency. The first step has been to derive overall Nascom requirements and identify the functionality common to all the current management systems. The identification of these common functions will enable the reuse of processes in the management architecture and promote increased use of automation throughout the Nascom network. The MSS, CAP, MACS, and Ecom projects have indicated the potential value of commercial-off-the-shelf (COTS) and standards through reduced cost and high quality. The FARM will allow the application of the lessons learned from these projects to all future Nascom systems.

Drake, Brian C.↗

Architecture and evolution of Goddard Space Flight Center Distributed Active Archive Center

The Goddard Space Flight Center (GSFC) Distributed Active Archive Center (DAAC) has been developed to enhance Earth Science research by improved access to remote sensor earth science data. Building and operating an archive, even one of a moderate size (a few Terabytes), is a challenging task. One of the critical components of this system is Unitree, the Hierarchical File Storage Management System. Unitree, selected two years ago as the best available solution, requires constant system administrative support. It is not always suitable as an archive and distribution data center, and has moderate performance. The Data Archive and Distribution System (DADS) software developed to monitor, manage, and automate the ingestion, archive, and distribution functions turned out to be more challenging than anticipated. Having the software and tools is not sufficient to succeed. Human interaction within the system must be fully understood to improve efficiency to improve efficiency and ensure that the right tools are developed. One of the lessons learned is that the operability, reliability, and performance aspects should be thoroughly addressed in the initial design. However, the GSFC DAAC has demonstrated that it is capable of distributing over 40 GB per day. A backup system to archive a second copy of all data ingested is under development. This backup system will be used not only for disaster recovery but will also replace the main archive when it is unavailable during maintenance or hardware replacement. The GSFC DAAC has put a strong emphasis on quality at all level of its organization. A Quality team has also been formed to identify quality issues and to propose improvements. The DAAC has conducted numerous tests to benchmark the performance of the system. These tests proved to be extremely useful in identifying bottlenecks and deficiencies in operational procedures.

Bedet, Jean-Jacques↗

Propulsion Control Technology Development in the United States A Historical Perspective

This paper presents a historical perspective of the advancement of control technologies for aircraft gas turbine engines. The paper primarily covers technology advances in the United States in the last 60 years (1940 to approximately 2002). The paper emphasizes the pioneering technologies that have been tested or implemented during this period, assimilating knowledge and experience from industry experts, including personal interviews with both current and retired experts. Since the first United States-built aircraft gas turbine engine was flown in 1942, engine control technology has evolved from a simple hydro-mechanical fuel metering valve to a full-authority digital electronic control system (FADEC) that is common to all modern aircraft propulsion systems. At the same time, control systems have provided engine diagnostic functions. Engine diagnostic capabilities have also evolved from pilot observation of engine gauges to the automated on-board diagnostic system that uses mathematical models to assess engine health and assist in post-flight troubleshooting and maintenance. Using system complexity and capability as a measure, we can break the historical development of control systems down to four phases: (1) the start-up phase (1942 to 1949), (2) the growth phase (1950 to 1969), (3) the electronic phase (1970 to 1989), and (4) the integration phase (1990 to 2002). In each phase, the state-of-the-art control technology is described and the engines that have become historical landmarks, from the control and diagnostic standpoint, are identified. Finally, a historical perspective of engine controls in the last 60 years is presented in terms of control system complexity, number of sensors, number of lines of software (or embedded code), and other factors.

Jaw, Link C.a↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

PMDT: AI-Enabled Predictive Maintenance Digital Twins for Advanced Nuclear Reactors

Our team made substantial technical progress on various fronts during the course of the program. Multiple milestones were geared towards demonstrating the feasibility of machine learning based predictive maintenance digital twins towards reducing O&M costs, whereas some other milestones actually focused on identifying technical gaps and developing technologies such as humble AI to provide necessary robustness to the ML-based models. We were able to demonstrate in many cases that Machine learning-based methods can be successfully adapted for Nuclear plant environments especially for remote monitoring applications. Detailed analyses were carried out with plant and full scope simulation data along with capabilities of enhanced analytics to assess and set realistic expectations on cost reductions in O&M. These assessments are paving the way for investments towards reactor design improvements as well project planning for SMR projects as they develop and mature in the next few years. Technology developed under this program got direct visibility to GE Hitachi and their utility customers and resulted in positive intents to deploy some of the elements from design phase. The project additionally resulted in several reports, publications, software and data generation that will be useful in deployment and O&M services for BWRX300 fleets.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

The ICARE Method

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

Henke, Luke↗

Extended Duration: The SIRIUS 21 Crew Perspective

The SIRIUS (Scientific International Research In a Unique terrestrial Station) missions represent a collaborative effort between NASA and Russia’s Institute for Biomedical Problems (IBMP) to conduct a series of long duration isolation and confinement spaceflight analog missions. Three missions of 17-day, 4-month, and 8-month duration (SIRIUS 17, 19, and 21) have been completed at IBMP’s Ground-Based Experimental Complex / Nazemnyy eksperimental'nyy kompleks (NEK) in Moscow, Russia. The international SIRIUS 21 crew comprising representatives from the United States, United Arab Emirates and Russia recently completed the 8-month analog lunar mission. The extended duration mission included simulated lunar transit, orbital, and surface operations with corresponding deep space communication delay, during which the crew participated in nearly 70 studies, eight of which were sponsored by NASA’s Human Research Program. The studies examined the effect of isolation and confinement on the behavioral health of research subjects, and investigated medical countermeasures, team performance, crew dynamics, crew autonomy, food system risks, consequences of confinement and associated physiological stressors. SIRIUS 21 crewmembers also participated in operational tasks such as Rover and CubeSat assembly, simulated lunar sample assessment, VR activities, robotic arm training, environmental systems monitoring, exercise, greenhouse maintenance and 3D printing. Communication with Mission Control was limited to 30-minute periods every two hours. Since access to the internet and email was restricted, simulated ground support provided the Crew’s primary source of daily news and mission information. This panel discussion will include presentations from the US SIRIUS 21 crewmembers – William Brown and Ashley Kowalski – about their experience participating in the mission and science. A facilitated question and answer session will follow with attendees encouraged to ask questions and join in discussion with the SIRIUS 21 crewmembers about their experiences. William Brown came to SIRIUS 21 with experience spread across multiple industries, including the military, defense contracting, healthcare consulting, software engineering, and logistics. He has lived in the Middle East, Central Asia, and Russia. A former Boren Scholar, Brown is fluent in Russian. He holds a Master of International Business degree from the University of South Carolina’s Darla Moore School of Business. Prior to that, he earned a bachelor’s degree in Russian language, literature, and culture from the University of South Carolina. There, he also completed additional undergraduate coursework in computer science. Ashley Kowalski is a Project Leader in The Aerospace Corporation’s International Partnerships Department, where she works with, represents, and provides technical support to the the U.S. Space Force Space Systems Command International Affairs (SSC/IA) office. Through her numerous national and international assignments (Russia, China, and Germany), she has worked on topics related to international space systems, national security space systems, civil systems (including human spaceflight and civil launch projects), space policy, satellite industry analysis, and satellite manufacturing start-ups. She is proficient in Russian and German, and fluent in Polish. Kowalski received her Bachelor of Science and Master of Science degrees in mechanical and aerospace engineering from George Washington University in 2011 and 2012, respectively.

S. E. Whiting↗

Inductive System Monitors Tasks

The Inductive Monitoring System (IMS) software developed at Ames Research Center uses artificial intelligence and data mining techniques to build system-monitoring knowledge bases from archived or simulated sensor data. This information is then used to detect unusual or anomalous behavior that may indicate an impending system failure. Currently helping analyze data from systems that help fly and maintain the space shuttle and the International Space Station (ISS), the IMS has also been employed by data classes are then used to build a monitoring knowledge base. In real time, IMS performs monitoring functions: determining and displaying the degree of deviation from nominal performance. IMS trend analyses can detect conditions that may indicate a failure or required system maintenance. The development of IMS was motivated by the difficulty of producing detailed diagnostic models of some system components due to complexity or unavailability of design information. Successful applications have ranged from real-time monitoring of aircraft engine and control systems to anomaly detection in space shuttle and ISS data. IMS was used on shuttle missions STS-121, STS-115, and STS-116 to search the Wing Leading Edge Impact Detection System (WLEIDS) data for signs of possible damaging impacts during launch. It independently verified findings of the WLEIDS Mission Evaluation Room (MER) analysts and indicated additional points of interest that were subsequently investigated by the MER team. In support of the Exploration Systems Mission Directorate, IMS is being deployed as an anomaly detection tool on ISS mission control consoles in the Johnson Space Center Mission Operations Directorate. IMS has been trained to detect faults in the ISS Control Moment Gyroscope (CMG) systems. In laboratory tests, it has already detected several minor anomalies in real-time CMG data. When tested on archived data, IMS was able to detect precursors of the CMG1 failure nearly 15 hours in advance of the actual failure event. In the Aeronautics Research Mission Directorate, IMS successfully performed real-time engine health analysis. IMS was able to detect simulated failures and actual engine anomalies in an F/A-18 aircraft during the course of 25 test flights. IMS is also being used in colla

Source record↗