Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “continuous improvement”

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 181 records · Page 10

Combustion for future supersonic transport propulsion

Even with it's marginal performance, Concorde has demonstrated that supersonic civil aircraft are a practical proposition. A second generation machine will need sufficiently good performance for a robust operating system that can provide reliable, frequent service with competitive economics. Additionally, the propulsion system must be acceptable environmentally. That is it must create acceptable noise levels around airports and have acceptable emissions throughout its mission including cruise. Whatever devices may be used to improve the acceptability at subsonic flight conditions, the high operating temperatures at cruise can create difficult targets for the operation of the combustion system both mechanically and in the combustion process itself. While the driving force is ever better fuel consumption and weight to achieve economic viability, a future supersonic transport engine will have cycle temperatures limited only by the mechanical integrity of the major components. The environment of the major components in modern gas turbine engines is dominated by the air delivered by the compressor system. Consequently the maximum compression temperature is governed by materials available for the turbine and compressor discs. The continued improvement of the disc material leads to combustion inlet temperatures beyond today's experience and sets difficult targets for combustion system emissions. This is worsened by the requirement being at cruise and therefore maintained for the major part of the mission. Problems such as creep and oxidation of metallic parts are also considered.

B. W. Lowrie↗

Automated Rendezvous and Capture System Development and Simulation for NASA

The United States does not have an Automated Rendezvous and Capture/Docking (AR and C) capability and is reliant on manned control for rendezvous and docking of orbiting spacecraft. This reliance on the labor intensive manned interface for control of rendezvous and docking vehicles has a significant impact on the cost of the operation of the International Space Station (ISS) and precludes the use of any U.S. expendable launch capabilities for Space Station resupply. The Soviets have the capability to autonomously dock in space, but their system produces a hard docking with excessive force and contact velocity. Automated Rendezvous and Capture/Docking has been identified as a key enabling technology for the Space Launch Initiative (SLI) Program, DARPA Orbital Express and other DOD Programs. The development and implementation of an AR&C capability can significantly enhance system flexibility, improve safety, and lower the cost of maintaining, supplying, and operating the International Space Station. The Marshall Space Flight Center (MSFC) has conducted pioneering research in the development of an automated rendezvous and capture (or docking) (AR and C) system for U.S. space vehicles. This AR&C system was tested extensively using hardware-in-the-loop simulations in the Flight Robotics Laboratory, and a rendezvous sensor, the Video Guidance Sensor was developed and successfully flown on the Space Shuttle on flights STS-87 and STS-95, proving the concept of a video- based sensor. Further developments in sensor technology and vehicle and target configuration have lead to continued improvements and changes in AR&C system development and simulation. A new Advanced Video Guidance Sensor (AVGS) with target will be utilized on the Demonstration of Autonomous Rendezvous Technologies (DART) flight experiment in 2004.

Roe, Fred D.↗

Astrobee: Improving Capabilities for Free Flying Robotic Technology Demonstrations

The Astrobee Project has completed three years operating inside the ISS. Three Astrobee Free Flyers reached the ISS in April 2019 and are currently hosting a variety of users. During this time, Astrobee has advanced the state of the art in free-flying robots on ISS, operated over 100 sessions, logged over 750 hours of free-flyer operation, and made several capability improvements. Astrobee’s primary objective is to provide a highly flexible and capable free-flying robotic research platform to enable future guest scientist investigations. However, Astrobee is also demonstrating the feasibility of intra-vehicular robots (IVR) for performing key caretaking functions within exploration vehicles as part of NASA’s Moon-to-Mars exploration strategy. IVR capabilities will be especially vital during uncrewed mission phases. For example, current plans call for the lunar Gateway to be uncrewed >85% of the time. Astrobee’s baseline implementation supports free-flying camera and sensor survey use cases. Astrobee guest scientists can deploy software updates and hardware payloads to extend its capabilities. Astrobee is continuously improving its navigation robustness, general flight software maturity, and ISS interior maps, both through the baseline Astrobee operations and with the help of the ISAAC project. Astrobee began with mapping, localization, and operations in the Japanese Experiment Module (JEM), and has expanded to mapping in Node 2 and the US Lab. Astrobee has improved localization and operational robustness through improved mapping processes, algorithm updates (Soussan 2022) that reduce the occurrences of lost localization as well as developed recovery techniques to return to a good localization fix when loss of localization does occur. Future guest science experiments currently in development could demonstrate cargo transfer, fault isolation, free flyer and stationary robot collaboration, microgravity fluid transfer, and new docking mechanisms, among others. This presentation will focus on 1) Astrobee technical capabilities 2) What Astrobee can provide to a guest science experiment 3) Astrobee’s recent improvements 4) Possibilities for using Astrobee for future investigations. Soussan, R., Kumar, V., Coltin, B. and Smith, T. (2022) AstroLoc: An Efficient and Robust Localizer for a Free-flying Robot, Proc. Int. Conf. Rob. Autom. (ICRA) [to appear]

Astrobee↗

Integration of plant and microbial oil processing at oilcane biorefineries for more sustainable biofuel production

Oilcane—an oil-accumulating crop engineered from sugarcane—and microbial oil have the potential to improve renewable oil production and help meet the expected demand for bioderived oleochemicals and fuels. To assess the potential synergies of processing both plant and microbial oils, the economic and environmental implications of integrating microbial oil production at oilcane and sugarcane biorefineries were characterized. Due to decreased crop yields that lead to higher simulated feedstock prices and lower biorefinery capacities, current oilcane prototypes result in higher costs and carbon intensities than microbial oil from sugarcane. To inform oilcane feedstock development, we calculated the required biomass yields (as a function of oil content) for oilcane to achieve financial parity with sugarcane. At 10 dw% oil, oilcane can sustain up to 30% less yield than sugarcane and still be more profitable in all simulated scenarios. Assuming continued improvements in microbial oil production from cane juice, achieving this target results in a minimum biodiesel selling price of 1.34 [0.90, 1.85] USD∙L –1 (presented as median [5th, 95th] percentiles), a carbon intensity of 0.51 [0.47, 0.55] kg CO 2 e L –1 , and a total biodiesel yield of 2140 [1870, 2410] L ha –1 year –1 . Compared to biofuel production from soybean, this outcome is equivalent to 3.0–3.9 as much biofuel per hectare of land and a 57%–63% reduction in carbon intensity. While only 20% of simulated scenarios fell within the market price range of biodiesel (0.45–1.11 USD∙L –1 ), if the oilcane biomass yield would improve to 25.6 DMT∙ha –1 ∙y –1 (an equivalent yield to sugarcane) 87% of evaluated scenarios would have a minimum biodiesel selling price within or below the market price range.

09 BIOMASS FUELS↗

Oak Ridge National Laboratory Annual Sustainability Report 2023

ORNL, managed under contract by UT-Battelle LLC, is DOE’s largest science and energy laboratory and, as such, executes the widest range of mission capabilities. Diverse expertise spans a broad range of scientific and engineering disciplines, enabling research and science achievements to accelerate the delivery of solutions to the marketplace. ORNL supports DOE’s national missions of scientific discovery, clean energy, and security. To execute these activities, ORNL has grown significantly over 80 years of continuous operations, consisting of facilities with commissioning dates ranging from the 1940s to the present—an extraordinary set of distinctive scientific facilities and equipment. The complexities of such a variety of facilities require teamwork among divisions, a wide variety of conservation projects, and creative strategies to achieve the desired energy and water savings. Such a diverse and unique set of major facilities, totaling over 5.5 million square feet, with 6,000 employees, requires an innovative plan to accomplish advancements in operational efficiencies. ORNL is tasked with the management of an extraordinary set of distinctive scientific facilities and equipment for DOE. ORNL is mission-driven, and its mission has grown substantially over the decades. ORNL’s core research capabilities provide broad science and technology support for DOE in the areas of energy, environment, and national security. Currently, ORNL is a world leader in materials, neutron, and nuclear science and engineering, and in high-performance computing and data analytics. ORNL’s vast portfolio of research facilities must be maintained and carefully upgraded to protect the nation’s investment in scientific analysis. The goal of sustainable and resilient operations is to enable more effective execution of ORNL’s science and technology mission. Sustainable operational practices and enhanced resilience strive for excellent results while remaining diligent in energy conservation, environmental stewardship, asset management, and community engagement. The Sustainable ORNL Program (Sustainable ORNL) Continuous improvements in operational and business processes must be integrated into the fabric of the ORNL culture to maximize the return from the investment made in modernizing facilities and equipment. The Sustainable ORNL program promotes the legacy of system-wide best practices, management commitment, and employee engagement that will lead ORNL into a future of efficient, resilient, and sustainable operations. ORNL leadership and Sustainable ORNL champions receive regular status reports on the progress of each project and focus area (i.e., roadmap) and periodic summary reports. More information can be found at the program’s website. The Sustainable ORNL roadmap structure endorses 15 vital roadmaps. The figure below summarizes the current project assignments and demonstrates that each project contributes to the wellbeing of the whole. Continuous employee engagement and regular status reports confirm the ideals of the program. The roadmap structure is not static; as the science mission advances and the needs of the organization evolve, the Sustainable ORNL roadmap structure elements are modified to align with developing priorities. In 2022, Sustainable ORNL made roadmap changes to better align ORNL to support new federal requirements that have been issued.

54 ENVIRONMENTAL SCIENCES↗

Best Practices for Resilience Hub Development and Management

The Carbon League and its community partners in East St. Louis, Illinois, have identified five facilities to serve as resilience hubs. These hubs are intended to support the local community through a range of services and resources during blue-sky (everyday), gray-sky (pre-event), and black-sky (emergency) conditions. Transforming these facilities into fully functional resilience hubs requires a broad operational improvement and programmatic planning roadmap. This memo outlines best practices to guide the development of these resilience hubs in East St. Louis, including recommendations for infrastructure services; safety and physical protection; community services; operational protocols; and a phased implementation strategy aligned with realistic funding and capacity constraints. Infrastructure recommendations include strengthening electric power, communications, water, sanitation, and transportation/logistics capabilities, all of which are essential for hubs that may serve as cooling and warming centers, distribution points, and information hubs during emergencies. Safety recommendations focus on accessibility, emergency action planning, indoor air quality, and secure storage of critical equipment. A phased roadmap provides guidance from immediate, low-cost readiness actions to long-term optimization and community integration. Performance metrics and maintenance protocols ensure continuous improvement and operational readiness. This guidance draws on best practices that can be used to support the development of resilient, community-centered hubs capable of enhancing public safety, health, and well-being during everyday operations and emergencies alike.

99 GENERAL AND MISCELLANEOUS↗

The CYBER security – Competency Health and Maturity Progression (CYBER-CHAMP) model: Extending the National Initiative for Cybersecurity Education (NICE) Framework Across Organizational Security

Problem Statement: There is a pervasive talent deficit in the cybersecurity industry that prevents employers from being able to fill their open positions efficiently. A holistic approach to security is required to ensure organizations have adequate prevention and response capabilities in case of a cyberattack. Specifically, industrial control systems (ICS’s) and their operational technology (OT) components have become a constant target for cyberattacks. Research Questions: It is proposed that the NICE Framework should be extended in the following areas: 1) Include guidance regarding the job roles and competencies for both IT and OT professionals. 2) Offer step-by-step solutions, based on the work role mappings from the NICE Framework, to increase cybersecurity through employee training and education. 3) Provide a streamlined, lifecycle approach to building a cybersecurity program. Contribution: The CYBER security – Competency Health and Maturity Progression (CYBER-CHAMP©) model provides a customized solution for businesses to understand their education gaps in organizational security and target areas for improvement. Rationale: The Framework for Improving Critical Infrastructure Cybersecurity v1.1 addresses ICS but does not offer a measurement of cybersecurity maturity or clear methods to ascertain an organization’s current risk profile. In Phases 1 and 5 of the model, measurements are provided to help an organization build their current and target risk profiles. The NICE framework provides a structure for planning an IT cybersecurity workforce, but the OT aspects of cybersecurity are only briefly discussed. The model uses Phases 2-3 to examine the competencies of an organization’s workforce, which includes both IT and OT roles. Current frameworks do not offer next steps to increase an organization’s cybersecurity. During Phase 4, employees’ roles are mapped to training, education, and/or certifications from common vendors. Investigative Approach: The model provides measurements and metrics for both an organization’s status and continual improvement. This improvement methodology includes guidance for creating an overall strategic plan for security improvement via products designed to increase an organization’s operational readiness through workforce competency health. Lessons Learned: Depending on who was participating, there were contradicting answers given in Phase 1 due to different security cultures in the organization. This revelation has influenced the steps listed in the User’s Guide, where Phase 1’s first recommended step is to assemble a team that champions the facilitation and implementation of the model in the organization. During Phase 2, the discovery was made that organizations may be missing roles that are necessary to perform critical cybersecurity functions. By understanding the functional roles and competencies needed, they can contract or hire cybersecurity help to fill these gaps. Implications: Using the model, organizations can discuss quantitative measures for improvement as a business case for advancing their security program. Future research can validate and extend the present theory and model to a variety of environments. It is of interest to investigate additional security roles and knowledge domains that are used to build standardized cybersecurity curriculum.

97 MATHEMATICS AND COMPUTING↗

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗

Milestone 1.2.10: Steady-state H 2 “roll over” point data for aluminum alloys 1100 and 6061

Extended (> 50 years) dry storage is being evaluated by the U.S. Department of Energy (DOE) for the disposition of ~ 18 metric tons of aluminum-clad spent nuclear fuel (ASNF). Transition of the current ASNF inventory into dry storage—using the standard DOE canister—necessitates a rigorous, predictive understanding of the long-term physical and chemical factors that may influence the integrity of the proposed storage canister, including radiolytic molecular hydrogen (H 2 ) generation. Current model predictions employ initial radiolytic yields of H 2 , the values of which change as the cladding’s H 2 -precursor inventory is depleted and H 2 itself becomes progressively more involved in radiolytic and surface dissociation processes. Consequently, the absorbed radiation dose that this steady-state H 2 yield corresponds to is essential for the evaluation and improvement of model predictions. Here, we report our findings on the long-term generation of H 2 from the gamma irradiation (≤ 36 MGy) of corroded AA1100 and AA6061 coupons in helium environments at ambient temperature and ~ 50% RH. Our findings show that AA1100 systems reached steady-state by ~ 36 MGy, while higher doses were necessary for AA6061 systems. This discrepancy was attributed to the AA6061 coupons developing a thicker corrosion layer that led to the trapping of H 2 and its precursors, and potentially additional chemistries, ultimately delaying the depletion of H 2 precursors and the system’s “roll over” point. Further, current model predictions—based on previous AA1100 data—do not show steady-state attainment until above 120 MGy, which is not the case for the AA1100 data collected here. Consequently, the new alloy dependent data presented here are important for the continued improvement of predictive computer models for evaluating the feasibility of extended storage of ASNF in helium backfilled canisters.

38 RADIATION CHEMISTRY, RADIOCHEMISTRY, AND NUCLEA↗

Engineering plants for spaceflight environments

The conversion efficiency of radiation into biomass and yield has steadily increased for centuries because of continued improvement in both plant genetics and environmental control. Considerable effort has gone into improving the environment for plant growth in space, but work has only begun to engineer plants for spaceflight. Genetic manipulation offers tremendous potential to improve our ability to study gravitational effects. Genetic manipulation will also be necessary to build an efficient regenerative life support system. We cannot fully characterize plant response to the spaceflight environment without understanding and manipulating their genetic composition. Identification and selection of the existing germplasm is the first step. There are thousands of cultivars of each of our major crop plants, each specifically adapted to a unique environment on our planet. Thousands of additional lines are held in national germplasm collections to maintain genetic diversity. Spaceflight imposes the need to tap this diversity. Existing lines need to be evaluated in the environment that is characteristic of closed-system spaceflight conditions. Many of the plant growth challenges we confront in space can be better solved through genetic change than by hardware engineering. Ten thousand years of plant breeding has demonstrated the value of matching genetics with the environment. For example, providing continuous light can increase plant growth in space, but this often induces calcium deficiencies because Ca is not supplied by guttation during a dark period. This deficiency cannot be eliminated through increased root-zone and foliar Ca applications. It can be solved, in wheat, through genetic selection of lines that do not have the deficiency. Subsequent comparison of lines with and without the Ca deficiency has also helped us understand the nature of the problem.

Non-NASA Center↗

Concurrent Engineering for the Management of Research and Development

The Management of Research and Development (R&D) is facing the challenges of reducing time from R&D to customer, reducing the cost of R&D, having higher accountability for results (improved quality), and increasing focus on customers. Concurrent engineering (CE) has shown great success in the automotive and technology industries resulting in significant decreases in cycle time, reduction of total cost, and increases in quality and reliability. This philosophy of concurrency can have similar implications or benefits for the management of R&D organizations. Since most studies on the application of CE have been performed in manufacturing environments, research into the benefits of CE into other environments is needed. This paper presents research conducted at the NASA Glenn Research Center (GRC) investigating the application of CE in the management of an R&D organization. In particular the paper emphasizes possible barriers and enhancers that this environment presents to the successful implementation of CE. Preliminary results and recommendations are based on a series of interviews and subsequent surveys, from which data has been gathered and analyzed as part of the GRC's Continuous Improvement Process.

DelRosario, Ruben↗

Lessons Learned from Astrobee Operations on the International Space Station

Since its launch in 2019, NASA has been operating three Astrobee free-flying robots providing an autonomous and adaptable research platform aboard the International Space Station (ISS). These robots have not only facilitated a myriad of national and international research endeavors in microgravity but have also served as a STEM outreach platform for student competitions aboard the ISS. Amidst its extensive operational tenure, spanning over five years and exceeding 1200 hours of cumulative free-flyer operation as of April 2024, the Astrobee robots have encountered software and hardware anomalies. Despite its inherent design for on-orbit repair or replacement, certain anomalies have proven to be complex, necessitating remote resolution via software and firmware updates or, in extreme cases, hardware replacements or the return of faulty units to NASA's ground facilities for repair. Such challenges underscore the delicate balance between the autonomous functionality of Astrobee and the occasional need for human intervention to maintain optimal performance. One recurring point of failure identified during Astrobee's operational lifespan has been the SD card, a critical component utilized by the different Astrobee processors and the Dock Station. The occurrence of SD card anomalies, both on orbit and within ground units, has provided invaluable insights into the improvement of Astrobee's systems and mitigation to future faults. This presentation will focus on four key areas: 1. Overview of Faults and Anomalies: A comprehensive examination of the diverse array of faults and anomalies encountered by Astrobee and its associated systems both in orbit and on the ground. From software glitches to hardware malfunctions, this section provides insights into the challenges faced during Astrobee's operational tenure. 2. Resolution Processes and Procedures: An in-depth discussion of the methodologies and procedures implemented to resolve the encountered anomalies. This includes remote troubleshooting, software patches, firmware updates, and, when necessary, the logistics involved in hardware replacements or down-massing for repair. 3. Implementation of Software Updates and Hardware Upgrades: A detailed exploration of the strategies employed to mitigate the risk of recurring anomalies through the implementation of software updates and hardware upgrades. This section highlights the iterative nature of Astrobee's development, emphasizing the continuous pursuit of robustness and reliability. 4. Lessons Learned and Future Directions: Reflecting on the insights gained from addressing anomalies, this section examines the lessons learned and outlines future directions for enhancing Astrobee's robustness and resilience. It underscores the iterative nature of space exploration and the importance of adaptability and continuous improvement in the pursuit of scientific discovery. Through a nuanced examination of Astrobee's operational challenges and the strategies employed to overcome them, this presentation sheds light on the complexities of operating autonomous robotic systems in the ISS environment. It underscores NASA's commitment to pushing the boundaries of exploration and innovation while navigating the inherent challenges of space exploration.

Astrobee↗

Lessons Learned from Astrobee Operations on the International Space Station

Since its launch in 2019, NASA has been operating three Astrobee free-flying robots providing an autonomous and adaptable research platform aboard the International Space Station (ISS). These robots have not only facilitated a myriad of national and international research endeavors in microgravity but have also served as a STEM outreach platform for student competitions aboard the ISS. Amidst its extensive operational tenure, spanning over five years and exceeding 1200 hours of cumulative free-flyer operation as of April 2024, the Astrobee robots have encountered software and hardware anomalies. Despite its inherent design for on-orbit repair or replacement, certain anomalies have proven to be complex, necessitating remote resolution via software and firmware updates or, in extreme cases, hardware replacements or the return of faulty units to NASA's ground facilities for repair. Such challenges underscore the delicate balance between the autonomous functionality of Astrobee and the occasional need for human intervention to maintain optimal performance. One recurring point of failure identified during Astrobee's operational lifespan has been the SD card, a critical component utilized by the different Astrobee processors and the Dock Station. The occurrence of SD card anomalies, both on orbit and within ground units, has provided invaluable insights into the improvement of Astrobee's systems and mitigation to future faults. This presentation will focus on four key areas: 1. Overview of Faults and Anomalies: A comprehensive examination of the diverse array of faults and anomalies encountered by Astrobee and its associated systems both in orbit and on the ground. From software glitches to hardware malfunctions, this section provides insights into the challenges faced during Astrobee's operational tenure. 2. Resolution Processes and Procedures: An in-depth discussion of the methodologies and procedures implemented to resolve the encountered anomalies. This includes remote troubleshooting, software patches, firmware updates, and, when necessary, the logistics involved in hardware replacements or down-massing for repair. 3. Implementation of Software Updates and Hardware Upgrades: A detailed exploration of the strategies employed to mitigate the risk of recurring anomalies through the implementation of software updates and hardware upgrades. This section highlights the iterative nature of Astrobee's development, emphasizing the continuous pursuit of robustness and reliability. 4. Lessons Learned and Future Directions: Reflecting on the insights gained from addressing anomalies, this section examines the lessons learned and outlines future directions for enhancing Astrobee's robustness and resilience. It underscores the iterative nature of space exploration and the importance of adaptability and continuous improvement in the pursuit of scientific discovery. Through a nuanced examination of Astrobee's operational challenges and the strategies employed to overcome them, this presentation sheds light on the complexities of operating autonomous robotic systems in the ISS environment. It underscores NASA's commitment to pushing the boundaries of exploration and innovation while navigating the inherent challenges of space exploration.

Astrobee↗

An Evaluation and Recommendations for Further CFD Research Based on the NASA Common Research Model (CRM) Analysis from the AIAA Drag Prediction Workshop (DPW) Series

The six Drag Prediction Workshops (DPW) have drawn a total of 125 participants submitting 225 data entries. Over half of these occurred in the last three workshops dealing with the NASA Common Research Model (CRM). Participants have ranged from North America, Europe, Asia, and South America, representing Government, Industry, Academia, and Commercial/Vendors. The DPW Series has generated a tremendous amount of CFD data, freely available to the public domain. A continuous improvement of the results as measured by: the reduction of the spread of drag predictions for the specified “nominal” cruise point, accuracy of drag increment, and the angle-of-attack sweep behavior, has been noted. Although it has been difficult separating out the parts and pieces that contribute to errors in CFD drag predictions, part of the improvements over the years can be attributed to grid resolution. The scatter in predicted drag in the continuum has been reduced dramatically from plus or minus 50 counts in DPW-I to around plus or minus 5 counts for DPW-V and - VI. During the six workshops, the grid size has grown dramatically. The average size of the medium wing-body meshes in DPW-I through DPW-IV have been 3.2, 5.4, 7.8 and 10.9 million, respectively. This represents a growth rate of approximately 17 percent per year during the eight years between DPW-I and DPW-IV. For DPW-VI, this number has grown from 25 to 50 million points for the various families of grids available. The finest level grids have increased steadily, from just over 3 million grid points in DPW-I to 225 million for the WBNP (Wing-Body-Nacelle-Pylon) in DPW-VI. While progress has been made, persistent problems with grid generation and separated flow prediction continue. The experiences and recommendations presented here are consistent with those espoused in the “CFD Vision 2030 Study: A Path to Revolutionary Computational Aerosciences,” NASA/CR-2014-218178.

Tinoco, Edward N.↗

Data-Driven Buy Clean: Decarbonization and Beyond

This report was compiled to provide recommendations on the availability of public background data from the U.S. Federal life cycle assessment (LCA) Data Commons to be conformant with the Association for Life Cycle Assessment (ACLCA) 2022 Product Category Rule (PCR) Open Standard to build technical tools that can assist industry in creating more comparable Type II Environmental Product Declarations (EPDs) for Federal Buy Clean and sustainability initiatives. The Federal LCA Commons is not only a public data source but also a consistently structured, self-referencing mega-repository for data developed by federal agency experts (in agency repositories) and by academia, nonprofit organizations, and industry (via the US Life Cycle Inventory Database). The Federal LCA Commons Technical Working Group is continuously improving the standardization of data documentation, formatting, and nomenclature to ensure lossless data loading and accurate data representation. This report and appendixes include the following: 1) An introduction to data-driven Buy Clean and decarbonization initiatives at the federal level; 2) The current status and associated challenges with LCA data and EPD standards and comparability; 3) Opportunities for the Federal LCA Commons to support conformance with the ACLCA 2022 PCR Open Standard and provide resources to implement the Federal Sustainability Plan, Buy Clean Program, and Inflation Reduction Act (IRA) sustainability goals and objectives. To date, the Federal LCA Commons is the result of coordinated work by National Renewable Energy Laboratory (NREL), the U.S. Department of Agriculture (USDA), the Environmental Protection Agency (EPA), the National Energy Technology Laboratory (NETL), the Argonne National Laboratory (ANL), the U.S. Army Corps of Engineers (USACE), the Federal Highway Administration (FHWA), the U.S. Forest Service (USFS), the Federal Aviation Administration (FAA), the Department of Defense (DoD) and the National Institute of Standards and Technologies (NIST). The Federal LCA Commons will continue to combine databases from the collaborating agencies while remaining a public resource. There are several initiatives among the collaborating agencies to expand the Federal LCA Commons and dedicated federal funding and resources could accelerate and strengthen these initiatives.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Laboratory for Atmospheres 2002 Technical Highlights

How can we improve our ability to predict the weather-tomorrow, next week, and into the future? How is the Earth's climate changing? What causes such change? And what are its costs? What can the atmospheres of distant planets teach us about our own planet and its evolution? The Laboratory for Atmospheres is helping to answer these and other scientific questions about our planet and its neighbors. The Laboratory conducts a broad theoretical and experimental research program studying all aspects of the atmospheres of the Earth and other planets, including their structural, dynamical, radiative, and chemical properties, with the overarching goal to provide better understanding and to improve prediction of the Earth's climate. Vigorous research is central to NASA's exploration of the frontiers of knowledge. NASA scientists play a key role in conceiving new space missions, providing mission requirements, and carrying out research to explore the behavior of planetary systems, including, notably, the Earth's. Our Laboratory's scientists also supply outside scientists with technical assistance and scientific data to further investigations not immediately addressed by NASA itself. Laboratory scientists submit competitive research proposals with diverse scientific or technological approaches to NASA and other Federal agencies to acquire research support. The Laboratory management strives to provide a working environment that promotes creativity, competition, and openness. The Laboratory for Atmospheres is a vital participant in NASA's research program. Our Laboratory often has relatively large programs, sizable satellite missions, or observational campaigns that require the cooperative and collaborative efforts of many scientists. We ensure an appropriate balance between our scientists' responsibility for these large collaborative projects and their need for an active individual research agenda. This balance allows members of the Laboratory to continuously improve their scientific credentials. The Laboratory places high importance on promoting and measuring quality in its scientific research. We strive to assure high quality through peer-review funding processes that support approximately 90% of the work in the Laboratory. The overall quality of our scientific efforts is evaluated periodically by committees of advisors from the external scientific community, as detailed in Appendix 2 of this document. Members of the Laboratory interact with the general public to support a wide range of interests in the atmospheric sciences. Among other activities, the Laboratory raises the public's awareness of atmospheric science by presenting public lectures and demonstrations, by making scientific data available to wide audiences, by teaching, and by mentoring students and teachers. Section 6 presents details of the Laboratory's outreach activities during 2002. The Laboratory is also committed to addressing the demographic imbalances that exist today in the atmospheric and space sciences. We must address these imbalances for our field to enjoy the full benefit of all of the Nation's talent. The Laboratory makes substantial efforts to attract new scientists to the fields of atmospheric and space sciences. We strongly encourage the establishment of partnerships with Federal and state agencies that have operational responsibilities to promote the societal application of Earth sciences.

Steven E. Platnick↗

P52D-1583 - Further Improvements to Constraints on Titan’s Atmospheric n-Butane, via Ground-Based Observations

We have acquired high spectral resolution ground-based observations of Titan in the mid-infrared from NASA Infrared Telescope Facility’s Texas Echelon Cross Echelle Spectrograph instrument , designed to constrain the abundances of new molecules within Titan’s atmosphere. The target molecule for this work, n-butane (n-C H ), though predicted by photochemical models of Titan’s atmosphere , has never been detected. Using the NEMESIS radiative transfer code , we retrieved a disk-averaged temperature profile for Titan by modeling CH emission in the 1248 cm region. Using this temperature profile, we then retrieved disk-averaged profiles of ethene (C H ), propane (C H ), and propene (C H ) in the 956 and 965 cm regions, which are also home to the strong and vibrational features of n-butane. We used an n-butane pseudoline list from JPL in order to systematically introduce a range of n-butane mixing ratios into the model, to constrain the molecule’s abundance based on the model’s changing fit to the data. We derive 3-confidence upper limits at an altitude of 150 km of 48 and 31 ppb for n-butane, via the and bands in the 956 and 965 cm regions, respectively. These are significantly tighter upper limits when compared to the ~300 ppb upper limit found in our recent work which used the same methodology but on much lower resolution limb data collected by the Cassini spacecraft. Upper limits on gas abundances are important for continued improvement of photochemical models of Titan’s atmosphere, which is understood to be an important analog for the prebiotic Earth atmosphere . They are also important for understanding the composition of Titan’s lakes and seas, which are likely to contain these larger hydrocarbons . Finally, as larger molecules like C ’s are thought to be able to serve as formation sites for building haze particles, constraining their abundances is important for understanding the process of haze formation at Titan and at Earth Ref: [1] J. H. Lacy, et al., PASP, 2002. [2] Y.L. Yung, et al., ApJS, 1984. [3] M. Dobrijevic, et al., Icarus, 2021. [4] P. G. J. Irwin et al., JQSRT, 2008. [5] K. Sung, et al., JQSRT, 2020. [6] B. L. Steffens, et al., PSJ, 2022. [7] Clarke & Ferris, Origins Life Evol. Biosphere, 1997. [8] D. Cordier, et al., ApJ, 2008. [9] D. B. Curtis, et al., JPCA, 2005.

Brendan Steffens↗

Full Life-Cycle Defect Management Assessment: Initial Inspection Data Collection Results and Research Questions for Further Study

It is often the case in software projects that when schedule and budget resources are limited, the Verification and Validation (V&V) activities suffer. Fewer V&V activities can be afforded and moreover, short-term challenges can result in V&V activities being scaled back or dropped altogether. As a result, too often the default solution is to save activities for improving software quality until too late in the life-cycle, relying on late-term code inspections followed by thorough testing activities to reduce defect counts to acceptable levels. As many project managers realize, however, this is a resource-intensive way of achieving the required quality for software. The Full Life-cycle Defect Management Assessment Initiative, funded by NASA s Office of Safety and Mission Assurance under the Software Assurance Research Program, aims to address these problems by: Improving the effectiveness of early life-cycle V&V activities to make their benefits more attractive to team leads. Specifically, we focus on software inspection, a proven method that can be applied to any software work product, long before executable code has been developed; Better communicating this effectiveness to software development teams, along with suggestions for parameters to improve in the future to increase effectiveness; Analyzing the impact of early life-cycle V&V on the effectiveness and cost required for late life-cycle V&V activities, such as testing, in order to make the tradeoffs more apparent. This white paper reports on an initial milestone in this work, the development of a preliminary model of inspection effectiveness across multiple NASA Centers. This model contributes toward reaching our project goals by: Allowing an examination of inspection parameters, across different types of projects and different work products, for an analysis of factors that impact defect detection effectiveness. Allowing a comparison of this NASA-specific model to existing recommendations in the literature regarding how to plan effective inspections. Forming a baseline model which can be extended to incorporate factors describing: the numbers and types of defects that are missed by inspections; how such defects flow downstream through software development phases; how effectively they can be caught by testing activities in the late stages of development. The model has been implemented in a prototype web-enabled decision-support tool which allows developers to enter their inspection data and receive feedback based on a comparison against the model. The tool also allows users to access reusable materials (such as checklists) from projects included in the baseline. Both the tool itself and the model underlying it will continue to be extended throughout the remainder of this initiative. As results of analyzing inspection effectiveness for defect containment are determined, they can be shared via the tool and also via updates to existing training courses on metrics and software inspections. Moreover, the tool will help satisfy key CMMI requirements for the NASA Centers, as it will enable NASA to take a global view across peer review results for various types of projects to identify systemic problems. This analysis can result in continuous improvements to the approach to verification.

Shull, Forrest↗