Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “containment assurance”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS1986

CID-720 aircraft high-environment flight instrumentation system

The high-environment flight instrumentation system was designed to acquire Langley's structural response data during the full scale transport-controlled impact demonstration test. There was only one opportunity for data acquisition. Thus, a high reliability and crashworthy design approach was implemented. The approach featured multi-level redundancy and a vigorous quality assurance testing program. Complying with an accelerated schedule, the instrumentation system was developed, tested and shipped within 18 months to Dryden Flight Research Facility. The flight instrumentation system consists of two autonomous data systems, DAS #1 and #2, and an excellent checkout subsystem. Each data system is partitioned into four pallets. The system was designed to operate on manned and unmanned flights. There are 176 data channels per data system. These channels are sequentially sampled and encoded into 1 megabit/sec pulse code modulation (PCM) data signal. To increase the probability of success, a special PCM distribution subsystem was developed. This subsystem distributes the PCM signal to two transmitters, one delay memory, and eight recorder tracks. The data on four of these trackes was digitally delayed approximately 300 msec to maximize data acquisition during impact. Therefore each data system's data is redundantly recorded onboard and on the ground. There are two time code generators. Parallel time from each is encoded into both data systems. Serial time from each is redundantly recorded on both onboard recorders. Instrumentation power is independent of aircraft power and self-contained.

Calloway, R. S.↗
NASA NTRS1996

Space Station Furnace Facility Management Information System (SSFF-MIS) Development

This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.

Meade, Robert M.↗
NASA NTRS2014

Clearance Analysis of CTC2 (on ELC4) to S-TRRJ HRS Radiator Rotation Envelope

In response to the planned retirement of the Space Shuttle Program, International Space Station (ISS) management began stockpiling spare parts on the ISS. Many of the larger orbital replacement units were stored on the Expedite the Processing of Experiments to Space Station (EXPRESS) Logistics Carriers (ELCs) mounted on the end of the S3 and P3 truss segments, immediately outboard of the Thermal Radiator Rotary Joints (TRRJs) and their attached radiators. In an August 2009 computer-aided design (CAD) assessment, it was determined that mounting the Cargo Transport Container (CTC) 2 on the inboard face of ELC4 as planned would create insufficient clearance between the CTC2 and the rotational envelope of the radiators when the TRRJs were rotated to a gamma angle of 35.0 degrees. The true clearance would depend on how the Unpressurized Cargo Carrier Attachment System (UCCAS) was mounted to the S3 truss and how the ELC4 was attached to it. If the plane of the UCCAS attachment points were tilted even slightly inboard, it would significantly change the clearance between CTC2 and the Starboard TRRJ (S-TRRJ) radiators. Additionally, since CTC2 would be covered in multilayer insulation (MLI), the true outer profile of CTC2 was not captured in the CAD models used for the clearance assessment. It was possible that, even if the S-TRRJ radiators cleared CTC2, they could snag the MLI covering. In the fall of 2010, the Image Science and Analysis Group (ISAG) was asked to perform an on-orbit clearance analysis to determine the location of CTC2 on ELC4 and the S-TRRJ radiators at the angle of closest approach so that a positive clearance could be assured. To provide the measurements as quickly as possible to aid in the assessment, it was decided that the clearance analysis would be broken into two phases. Phase I: The location and orientation of the UCCAS fittings, which support and hold the ELC4 in place, would be measured relative to the ISS Analytical Coordinate System (ISSACS) as defined by nine preexisting Space Vision System (SVS) targets affixed to the forward/zenith side of the S1 and S3 truss segments. The location of the outboard edge of the S-TRRJ radiator would also be measured when positioned at the angle of closest approach to CTC2 (gamma = 35.0 degrees). This data would allow the Digital Pre-Assembly Group to predict how the ELC4 would sit on the UCCAS and how that would translate into the clearance between CTC2 and the S-TRRJ radiators. Phase II: After the ELC4 was delivered and installed into the UCCAS, the position of the CTC2 mounting plate on the inboard face of ELC4, would be measured in the ISSACS coordinate system relative to the SVS control points used in Phase I. Although CTC2 would not yet be mounted on ELC4, the working envelope of CTC2 could be mathematically added to the measured position of ELC4 to produce a best estimate for CTC2's mounted location. Comparing CTC2's best estimated location to the S-TRRJ radiator (measured in Phase I); relative to the ISSACS coordinate system, would provide a direct measurement of the expected clearance. Due to the impending delivery of ELC4 (scheduled for January 2011), planning for the Phase I clearance analysis began immediately. Using the Dynamic Onboard Ubiquitous Graphics (DOUG) program, ISAG designed a way to acquire images of the SVS control points on truss segments S1 and S3, the aft facing edge of the S-TRRJ Heat Rejection Subsystem (HRS) radiator, and the three UCCAS latch mechanisms mounted on the zenith face of the S3 truss using the Space Station Remote Manipulator System (SSRMS). To minimize the number of SSRMS movements, the Special Purpose Dexterous Manipulator (SPDM) would be attached to the SSRMS. This would make it possible to park the SPDM in one position and acquire multiple images by changing the viewing orientation of the SPDM body cameras using the pan/tilt units on which they are mounted. Using this implementation concept, ISAG identified four SSRMS/SPDM positions from which the majority of the needed imagery could be acquired. Five additional images would be acquired using the CP-3 external ISS camera mounted on the S1 truss immediately inboard of ELC4. Based on a photogrammetric simulation, it was estimated that the measured location of the HRS radiator and UCCAS latch points would be accurate to about 0.3 in. in each of the three axes relative to ISSACS. Working with ROBO, ISAG collected 78 images of the ISS December 29, 2010. From this imagery, the best 40 were selected for use in the analysis process. The images were radiometrically enhanced to improve color and contrast and loaded into the FotoG analysis software along with the camera parameters and control data, which consisted of the coordinates for the nine SVS targets on the S1 and S3 trusses in the ISSACS coordinate system.

Liddle, Donn↗
NASA NTRS2015

Radiation Budget Instrument (RBI) for JPSS-2

Radiation Budget Instrument (RBI) will be one of five instruments flying aboard the JPSS-2 spacecraft, a polar-orbiting sun-synchronous satellite in Low Earth Orbit. RBI is a passive remote sensing instrument that will follow the successful legacy of the Clouds and Earth's Radiant Energy System (CERES) instruments to make measurement of Earth's short and longwave radiation budget. The goal of RBI is to provide an independent measurement of the broadband reflected solar radiance and Earth's emitted thermal radiance by using three spectral bands (Shortwave, Longwave, and Total) that will have the same overlapped point spread function (PSF) footprint on Earth. To ensure precise NIST-traceable calibration in space the RBI sensor is designed to use a visible calibration target (VCT), a solar calibration target (SCT), and an infrared calibration target (ICT) containing phase change cells (PCC) to enable on-board temperature calibration. The VCT is a thermally controlled integrating sphere with space grade Spectralon covering the inner surface. Two sides of the sphere will have fiber-coupled laser diodes in the UV to IR wavelength region. An electrical substitution radiometer on the integrating sphere will monitor the long term stability of the sources and the possible degradation of the Spectralon in space. In addition the radiometric calibration operations will use the Spectralon diffusers of the SCT to provide accurate measurements of Solar degradation. All those stable on-orbit references will ensure that calibration stability is maintained over the RBI sensor lifetime. For the preflight calibration the RBI will view five calibration sources - two integrating spheres and three CrIS (Cross-track Infrared Sounder ) -like blackbodies whose outputs will be validated with NIST calibration approach. Thermopile are the selected detectors for the RBI. The sensor has a requirement to perform lunar calibration in addition to solar calibration in space in a way similar to CERES instruments approach. To monitor climate change and to get stable and traceable results, it is critical to assure stable calibration over instrument lifetime.

Georgieva, Elena↗
NASA NTRS2022

Unlocking the Spacecraft and Human Habitat Microbiome to Enable the Next Generation of Space Exploration

Planetary protection is the discipline that prevents harmful contamination of the solar system during exploration activities. The current international guidelines and NASA policy addressing biological contamination on spacecraft surfaces contains prescriptive guidelines of spore requirements (e.g., 300 spores/m2, 5×105 spores per spacecraft) applicable to spacecraft bound for Mars. To verify these requirements spacecraft engineers sample spacecraft surfaces throughout the assembly, test and launch operations phase of the mission using damp water cotton swabs and polyester wipes. After sampling, the potential biological contamination is enumerated using a series of traditional microbiology techniques to include sonication, heat shocking at 80°C for 15min to select for spores, and growth on tryptic soy agar at 32°C for 72 hours. To enable crewed missions to Mars and robotic exploration of the Ocean Worlds a risk informed decision making / performance-based approach to assess biological contamination offers a promising solution in the trade space. Recognizing the need for a performance-based approach, NASA’s new Planetary Protection policies now incorporate the agility for missions to be able to leverage a performance or prescriptive approach. One of top contenders in the option space is a coupled quantitative, descriptive and functional based approach to be able to assess the quantity, types and capabilities of the biological contamination present on spacecraft surfaces. A tailored, mission by mission assurance case could then be formulated by building an argument around the target body, projected capabilities surrounding the types of organisms their potential for survival and proliferation, and ability to be transported on the target body to contaminate an area of biological interest. A performance-based requirement would then be used to demonstrate the mission’s compliance in protecting the planetary environment safety objectives. This symposium talk will showcase the background and need case for NASA to develop such a capability as well as provide an update on the efforts underway in developing a transparent and responsible performance-based approach to biological contamination assessments on spacecraft surfaces.

Habitat Microbiome↗
NASA NTRSDate not supplied

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗
NASA NTRSDate not supplied

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗
NASA NTRSDate not supplied

An Approach to Identifying Aspects of Positive Pilot Behavior within the Aviation Safety Reporting System

The National Airspace System (NAS) is constantly evolving as air traffic continues to ramp up to pre-pandemic numbers and projected to grow to unprecedented levels in the coming years. As well as increasing demand to the current system, emerging operations such as Unmanned Autonomous Systems are also expected to add to complexity in the airspace. To address these issues, the industry and government agencies supporting the NAS will need to rely upon additional automation and new technologies to address future operational requirements, while continuing to be a world-leading safe transportation system. As these new technologies are implemented, the system continues to rely on human pilots and controllers in the loop to monitor the system and intervene in situations the automation cannot handle. The goal of proactively addressing safety is of foremost concern to ensure passenger confidence. The industry has implemented various Safety Monitoring Systems to identify safety risks and proactively address them before they result in a serious incident or accident. One such program is the Aviation Safety Reporting System (ASRS). ASRS is a long-established system where pilots and controllers voluntarily and anonymously report safety incidents they experienced and observed during line operations by providing rich text narratives describing the events, the environment, and conditions leading to the safety event of concern. These narratives provide insight and context around events of interest and can be used to identify emerging problems. They can trigger investigations within Flight Operational Quality Assurance or Flight Data Monitoring programs. However, this process typically focuses on the adverse events and the unsafe aspects of the operations surrounding the reported or detected events. This perspective of investigating factors that went wrong around an adverse event is commonly referred to as Safety I. Alternatively, characterizing successful actions that operators perform every day under varying conditions that keep the system within safe operating bounds is a concept referred to as Safety II. The benefit of the Safety II view is that the scope is much larger than that of Safety I since a vast majority of the operations result in successful flights. Many of the successful techniques used to manage operational threats are not documented in standard operating procedures or taught during training. They are typically acquired over time by working with experienced pilots during line operations or in many cases after experiencing a problem for the first time and reacting to it in situ, drawing from years of experience to manage the threat. In an attempt to quantify these positive actions, we are proposing an approach to extracting key behaviors within ASRS reports that can support the Safety II concept. Our analysis assumes that ASRS reports contain some descriptions of corrective actions that operators performed to prevent a situation from leading to an accident. Leveraging recent advances in Natural Language Process modeling, we have developed an approach to extract positive sentiment from reports, embed these positive statements in a vector space where they can be numerically analyzed, and clustering these statements into similar contextual categories. From these contextualized categories we can attempt to summarized and distilled aspects of the positive behavior. The goal is to identify categories of behavior that describe consistent operator techniques that supports the Safety II concept. With this information, airlines may enable learning from these positive actions, or address procedures that need to be changed to avoid having pilots implement a workaround. These insights can provide a lens into what is “going right” in the operations that may otherwise not be known widely within the community. It is envisioned that this approach can be extended to other narrative programs such as Line Operation Safety Audit or Learning Improvement Team reports where similar observed behavior can be analyzed to extract positive actions and inform the overall operations.

NLP↗
DOE OSTI2020

Summary of BISON Milestones: NEAMS FY2020 Report

This summary report contains an overview of work performed under the work package entitled "FY2020 NEAMS Advanced Fuels Performance'', which is focused on the development and support of the fuel performance code BISON. The second chapter lists FY20 milestones titles, completion schedule, and milestone level. Subsequent chapters summarize and demonstrate completion of the milestones. The last chapter outlines FY21 proposed future work. In FY20, the NEAMS program emphasized development of BISON for its application to advanced reactors. While there are a variety of advanced fuel concepts, based on interaction with industry and the Nuclear Regulatory Commission, the fuel types we chose to develop were metallic fast reactor, UN/UC and particle fuels. The last chapter of this report documents proposed work for FY21. We plan to continue work on metallic and particle fuel in terms of developing/calibrating models and to begin rigorous validation/assessment for both fuel types. Due to the merger of the NEAMS and CASL programs, FY21 will see a return to light water reactor model development and simulation; this time focused on advanced technology fuels. Additionally, we seek to improve BISON, fundamentally. As such, we plan improvements to BISON and MOOSE in terms of algorithmic robustness, performance, ease-of-use, and quality assurance.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS2012

Extended Testability Analysis Tool

The Extended Testability Analysis (ETA) Tool is a software application that supports fault management (FM) by performing testability analyses on the fault propagation model of a given system. Fault management includes the prevention of faults through robust design margins and quality assurance methods, or the mitigation of system failures. Fault management requires an understanding of the system design and operation, potential failure mechanisms within the system, and the propagation of those potential failures through the system. The purpose of the ETA Tool software is to process the testability analysis results from a commercial software program called TEAMS Designer in order to provide a detailed set of diagnostic assessment reports. The ETA Tool is a command-line process with several user-selectable report output options. The ETA Tool also extends the COTS testability analysis and enables variation studies with sensor sensitivity impacts on system diagnostics and component isolation using a single testability output. The ETA Tool can also provide extended analyses from a single set of testability output files. The following analysis reports are available to the user: (1) the Detectability Report provides a breakdown of how each tested failure mode was detected, (2) the Test Utilization Report identifies all the failure modes that each test detects, (3) the Failure Mode Isolation Report demonstrates the system s ability to discriminate between failure modes, (4) the Component Isolation Report demonstrates the system s ability to discriminate between failure modes relative to the components containing the failure modes, (5) the Sensor Sensor Sensitivity Analysis Report shows the diagnostic impact due to loss of sensor information, and (6) the Effect Mapping Report identifies failure modes that result in specified system-level effects.

Melcher, Kevin↗
DOE OSTI2023

Predeployment progress of the Canister Deposition Field Demonstration

This report updates the high-level test plan for evaluating surface deposition on three commercial 32PTH2 spent nuclear fuel (SNF) canisters inside NUTECH Horizontal Modular Storage (NUHOMS) Advanced Horizontal Storage Modules (AHSMs) from Orano (formerly Transnuclear Inc.) and provides a summary of the surface sampling activities that have been conducted to date. The details contained in this report represent the best designs and approaches explored for testing as of this publication. Given the rapidly developing nature of this test program, some of these plans may change to accommodate new objectives or requirements. One goal of this testing is to collect defensible and detailed dust deposition measurements from the surface of dry storage canisters in a marine coastal environment to guide chloride-induced stress corrosion cracking (CISCC) research. Another goal is to provide data for the validation of computational fluid dynamics (CFD) based deposition modeling. To facilitate surface sampling, the otherwise highly prototypic dry storage systems will not contain SNF but rather will be electrically heated to mimic the decay heat and thermal hydraulic environment. Test and heater design is supported by detailed CFD modeling. Instrumentation throughout the canister, storage module, and environment will provide extensive information about the thermal-hydraulic behavior of horizontal dry cask storage systems. Manual sampling over a comprehensive portion of the canister surface at regular time intervals will offer detailed quantification and composition of the deposited particulates from a realistic storage environment. Discussions of a potential host site for the Canister Deposition Field Demonstration (CDFD) are ongoing. Until a host site is chosen, testing of key CDFD hardware components including the heater assemblies, power skid, and remote data acquisition system will continue. Functional testing of the finalized heater assemblies and test apparatus started this fiscal year. These initial heater tests have shown the assemblies are performing within design specifications. Staged surface sampling of a mockup of a canister outside the AHSM on a transfer skid was also performed. Refinements to the sampling procedures and techniques were captured from observation of these activities and lessons-learned debriefs. These updated sampling procedures and techniques are planned to be tested again in the field using the mockup in order to assure personnel are using the most accurate and repeatable methods possible prior to deployment for actual CDFD testing.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS2007

NASA-STD 3001 and the Human Integration Design Handbook (HIDH): Evolution of NASA-STD-3000

The Habitability & Environmental Factors and Space Medicine Divisions have developed the Space Flight Human System Standard (SFHSS) (NASA-STD-3001) to replace NASA-STD-3000 as a new NASA standard for all human spaceflight programs. The SFHSS is composed of 2 volumes. Volume 1, Crew Health, contains medical levels of care, permissible exposure limits, and fitness for duty criteria, and permissible outcome limits as a means of defining successful operating criteria for the human system. Volume 2, Habitability and Environmental Health, contains environmental, habitability and human factors standards. Development of the Human Integration Design Handbook (HIDH), a companion to the standard, is currently under construction and entails the update and revision of NASA-STD-3000 data. This new handbook will, in the fashion of NASA STD-3000, assist engineers and designers in appropriately applying habitability, environmental and human factors principles to spacecraft design. Organized in a chapter-module-element structure, the HIDH will provide the guidance for the development of requirements, design considerations, lessons learned, example solutions, background research, and assist in the identification of gaps and research needs in the disciplines. Subject matter experts have been and continue to be solicited to participate in the update of the chapters. The purpose is to build the HIDH with the best and latest data, and provide a broad representation from experts in industry, academia, the military and the space program. The handbook and the two standards volumes work together in a unique way to achieve the required level of human-system interface. All new NASA programs will be required to meet Volumes 1 and 2. Volume 2 presents human interface goals in broad, non-verifiable standards. Volume 2 also requires that each new development program prepare a set of program-specific human factors requirements. These program-specific human and environmental factors requirements must be verifiable and tailored to assure the new system meets the Volume 2 standards. Programs will use the HIDH to write their verifiable program-specific requirements.

Pickett, Lynn↗
DOE OSTI2025

Securing the Modern Grid: Federal Investments, Digitization, and Supply Chain Strategy

Across the United States (U.S.) grid expansion and modernization is underway, paving the way for accelerated load growth and intelligent resource management. Digitization of the grid is supported by several state and federal programs, providing support for utilities installing advanced metering infrastructure (AMI), AI-powered analytics systems, battery energy storage systems (BESS), and distributed energy resource management systems (DERMS) to transform the grid from a one-way power delivery system into an intelligent, responsive network that will enable faster load growth and power expansion of data centers for advanced artificial intelligence (AI) applications. The digital transformation of America's grid presents opportunity for increased efficiency and resiliency but also introduces new digital risks that require careful management. Digital equipment often contains several vulnerabilities such as unencrypted communication protocols, and persistent remote access capabilities that could be exploited to manipulate device settings, coordinate service disruptions, or inject false data into grid operations. These digital risks become particularly important as the grid must rapidly scale to support AI-driven data centers, which the administration has identified as essential for maintaining U.S. technological leadership and economic competitiveness. These vulnerabilities are compounded by supply chain realities: Chinese manufacturers currently produce 70-90% of essential grid components including inverters, batteries, and control systems, with the U.S. lacking domestic manufacturing capacity for critical assets like extra-high voltage transformers. Recent federal legislation has established Foreign Entity of Concern (FEOC) restrictions to address these risks, requiring projects to achieve escalating thresholds of non-FEOC content to receive tax credits while utilities work to expand sourcing channels for their supply chains and strengthen security measures. These restrictions arrive precisely when utilities face unprecedented electricity demand growth driven by the rapid growth in data centers, creating a considerable challenge: rapidly expanding infrastructure while navigating complex compliance requirements while lacking viable alternatives for many critical components. Idaho National Laboratory (INL) and its partners have developed practical approaches to help utilities navigate these intersecting challenges as they leverage federal investment to strengthen and grow the grid. These solutions include Cyber-Informed Engineering (CIE) principles that build resilience directly into systems, the Cirrus tool for secure cloud migration, and enhanced procurement guidance that embeds security requirements throughout equipment lifecycles. Federal initiatives, such as the Technical Assistance for Digital Assurance (TADA) project, provide direct support to utilities implementing these approaches while facilitating knowledge sharing across the industry. While these tools and frameworks cannot eliminate all risks inherent in foreign supply chain dependencies, they offer pragmatic pathways for strengthening security posture without sacrificing the deployment momentum essential to meeting surging electricity demand. Ultimately, securing America's digital energy infrastructure demands dedicated coordination across multiple fronts: building domestic supply chains, implementing robust digital assurance practices, and maintaining the aggressive modernization timeline necessary for reliability, resilience, and energy independence.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2016

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗
DOE OSTI2025

Characterization of MC&A for the Molten Salt Fuel Cycle

Advanced reactor developers are exploring diverse reactor designs, including molten salt reactors (MSRs). These advanced reactors are considered for wider applications and a range of deployment locations, including supporting the integration of renewable energy sources in the grid. There are three main types of MSRs: (1) reactors in which the fuel salt freely circulates within the core; (2) reactors with the fuel salt contained within vented fuel tubes; and (3) reactors that use molten salt solely as a coolant, with the fuel in a separate, solid form. In this document, the term MSR refers specifically to the first two types, which use fuel salt—special nuclear material (enriched uranium, plutonium, and 233 U) in chloride or fluoride form mixed with chloride- or fluoride-based carrier salt in a peritectic mixture—as the primary medium for fission. The composition of fuel salt, both at startup and for makeup or refueling, varies depending on the MSR design and the chosen fuel cycle approach, which can be either once-through or closed. For MSRs, a variety of fuel cycle approaches (e.g., U, U–Pu, U–Pu–TRU, U–Th, U–Pu–Th) are being considered. Fuel in MSRs is much different than traditional solid fuel, including its preparation. The uniqueness warrants investigation into characterizing fuel preparation processes, known as fuel salt synthesis . This effort characterized major fuel preparation and synthesis processes, identifying temperature, equipment, and environmental requirements for uranium-, plutonium-, and thorium-based fuel preparation and synthesis. Because MSR fuel salt synthesis facilities handle special nuclear material in loose, bulk form, a material control and accounting plan will be required for licensing from the US Nuclear Regulatory Commission or under the US Department of Energy authorization. This effort serves as a foundation to investigate material control and accounting approaches for synthesis facilities, including determining measurement points and techniques. Because several MSR developers are planning demonstration facilities in the coming years, this effort will support stakeholders with preparing or reviewing material control and accounting plans for providing assurance that all special nuclear material is accounted for at fuel salt synthesis facilities. This report was produced for Materials Protection, Accounting, and Control Technologies (MPACT) program under the US Department of Energy (DOE), Office of Nuclear Energy, Nuclear Fuel Cycle and Supply Chain.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS2017

A Virtual Laboratory for Aviation and Airspace Prognostics Research

Integration of Unmanned Aerial Vehicles (UAVs), autonomy, spacecraft, and other aviation technologies, in the airspace is becoming more and more complicated, and will continue to do so in the future. Inclusion of new technology and complexity into the airspace increases the importance and difficulty of safety assurance. Additionally, testing new technologies on complex aviation systems and systems of systems can be challenging, expensive, and at times unsafe when implementing real life scenarios. The application of prognostics to aviation and airspace management may produce new tools and insight into these problems. Prognostic methodology provides an estimate of the health and risks of a component, vehicle, or airspace and knowledge of how that will change over time. That measure is especially useful in safety determination, mission planning, and maintenance scheduling. In our research, we develop a live, distributed, hardware- in-the-loop Prognostics Virtual Laboratory testbed for aviation and airspace prognostics. The developed testbed will be used to validate prediction algorithms for the real-time safety monitoring of the National Airspace System (NAS) and the prediction of unsafe events. In our earlier work1 we discussed the initial Prognostics Virtual Laboratory testbed development work and related results for milestones 1 & 2. This paper describes the design, development, and testing of the integrated tested which are part of milestone 3, along with our next steps for validation of this work. Through a framework consisting of software/hardware modules and associated interface clients, the distributed testbed enables safe, accurate, and inexpensive experimentation and research into airspace and vehicle prognosis that would not have been possible otherwise. The testbed modules can be used cohesively to construct complex and relevant airspace scenarios for research. Four modules are key to this research: the virtual aircraft module which uses the X-Plane simulator and X-PlaneConnect toolbox, the live aircraft module which connects fielded aircraft using onboard cellular communications devices, the hardware in the loop (HITL) module which connects laboratory based bench-top hardware testbeds and the research module which contains diagnostics and prognostics tools for analysis of live air traffic situations and vehicle health conditions. The testbed also features other modules for data recording and playback, information visualization, and air traffic generation. Software reliability, safety, and latency are some of the critical design considerations in development of the testbed.

LVC-DE↗
DOE OSTI2025

Characterization of Tank 9H Annulus Sample in Support of Residual Material Inventory Determinations

The Savannah River National Laboratory (SRNL) was requested by Savannah River Mission Completion (SRMC) to provide sample preparation and characterization of the Tank 9H annulus sample in support of Residual Material Inventory Determinations. One Tank 9H sample in three vials [HTF-9-25-13, HTF-9-25-14 and HTF-9-25-15], with each vial containing approximately 200 mL of the Tank 9H annulus salt solution, were delivered to the SRNL Shielded Cells for sample preparation and characterizations in February 2025. The density of the “as-received” solution contained in each of the three Tank 9H annulus sample vials were determined followed by a solid-liquid separation on each one using 0.45-micron Nalgene® nylon filter membranes. The resulting filtrates were combined to form the Tank 9H annulus sample with a total volume of about 600 mL. The combined wet solid fractions, about a total of 4.8 grams of salt material, remaining on the filter membranes were air-dried in the Shielded Cells for 72 hours. The total weight of the air-dried solids was 2.1 grams. These air-dried solids were washed with deionized water (DI water) at a phase ratio of 60 mL DI water/gram of solids to recover insoluble solids, if any. No visible or measurable quantity of insoluble solids were recovered after DI water washing of the air-dried solids because the air-dried solids completely dissolved in the DI water. The solid fraction-wash water was not combined with the 600 mL of the filtrate solution, and the resulting solution was not screened or analyzed for radionuclides. Aliquot sample volumes of the undiluted Tank 9H annulus sample were sent to the SRNL analytical services groups for radionuclides, elementals, anions and total mercury analysis by various methods including radiochemical separations/counting methods, inductively coupled plasma-atomic emission spectroscopy (ICP-AES), and Inductively Coupled Plasma Mass Spectroscopy (ICP-MS) and special preparations. All sample analyses were performed in triplicate. This report presents the analytical characterization results for the Tank 9H annulus sample. The results are also reported where analytical methods yielded additional analytes, other than those requested by SRMC. In the characterization of the Tank 9H annulus sample, the detection limits for all the analytes, as specified in the Technical Task Request (TTR) and Task Technical and Quality Assurance Plan (TTQAP), were met.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2024

Synthesis of Correct Digital Controller Models from Specifications by Model Transformation (21-0320)

The design of high consequence controllers (in weapons systems, autonomy, etc.) that do what they are supposed to do is a significant challenge. Testing simply does not come close to meeting the requirements for assurance. Today circuit designers at Sandia (and elsewhere) typically capture the core behavior of their components using state models in tools such as STATEFLOW. They then check that their models meet certain requirements (e.g. “The system bus must not deadlock” or “both traffic lights at an intersection must not be green at the same time”) using tools called model checkers. If the model checker returns “yes” then the property is guaranteed to be satisfied by the model. However, there are several drawbacks to this industry practice: (1) there is a lot of detail to get right, this is particularly challenging when there are multiple components requiring complex coordination (2) any errors returned by the model checker have to be traced back through the design and fixed, necessitating rework, (3) there are severe scalability problems with this approach, particularly when dealing with concurrency. All this places high demands on the designers who now face not only an accelerated schedule but also controllers of increasing complexity. This report describes a new and fundamentally different approach to the construction of safety-critical digital controllers. Instead of directly constructing a complete model and then trying to verify it, the designer can start with an initial abstract (think “sketch”) model plus the requirements, from which a correct concrete model is automatically synthesized. There is no need for post-hoc verification of required functional properties. Having tool to carry this out will significantly impact the nation’s ability to ensure the safety of high-consequence digital systems. The approach has been implemented in a prototype tool, along with a suite of examples, including ones that reflect actual problems faced by designers. Our approach operates on a variant of Statecharts developed at Sandia called Qspecs. Statecharts are a widely used formalism for developing concurrent reactive systems, supporting scalability through allowing state models containing composite states, which are the serial or parallel composition of substates which can themselves contain statecharts. Statecharts enable an incremental style of development, in which states are progressively refined to incorporate greater detail in an incremental model of software development. Our approach formulates a set of constraints from the structure of the models and the requirements and propagates these constraints to a fixpoint. The solution to the constraints is an inductive invariant along with guards on the transitions. We also show how our approach extends to implementation refinement, decomposition, composition, and elaboration. We currently handle safety requirements written in LTL (Linear Temporal Logic)

42 ENGINEERING↗