Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “multiple building systems”

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 487 records · Page 27

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.

Trimble, Jay Phillip↗

Overview of the High Performance Antiproton (HiPAT) Experiment

The annihilation of matter with antimatter represents the highest energy density of any known reaction, producing 10(exp 8) MJ/g, approximately 10 orders of magnitude more energy per unit mass than chemical based combustion. To take the first step towards using this energy for propulsion applications the NASA MSFC Propulsion Research Center (PRC) has initiated a research activity examining the storage of low energy antiprotons. Storage was identified as a key enabling technology since it builds the experience base necessary to understand the handling of antiprotons for virtually all utilization and high-density storage concepts. To address this need, a device referred to as the High Performance Antiproton Trap (HiPAT) is under development at the NASA MSFC PRC. The HiPAT is an electromagnetic system (Penning-Malmberg design) consisting of a 4 Tesla superconductor, a high voltage confinement electrode system (operation up to 20 KV), and an ultra high vacuum test section (operating in the 10(exp -12) torr range). The system was designed to be portable with an ultimate goal of maintaining 10(exp 12) charged particles with a half-life of 18 days. Currently, this system is being experimentally evaluated using normal matter ions which are cheap to produce and relatively easy to handle. These normal ions provide a good indication of overall trap behavior, with the exception of assessing annihilation losses. The ions are produced external to HiPAT using two hydrogen ion sources, with adjustable beam energy and current. Ion are transported in a beam line and controlled through the use of electrostatic optics. These optics serve to both focus and gate the incoming ions, providing microsecond-timed pulses that are dynamically captured by cycling the HiPAT electric containment field like a 'trap door'. The layout of this system more closely simulates the operations expected at an actual antiproton production facility where 'packets' of antiprotons with pulse widths measured in 100's of nanoseconds could be provided. Initial dynamic capture experiments have been performed with both trap and ton source system functioning at approximately 10% of maximum levels, minimizing the potential for extraneous effects. Dynamic trapping techniques demonstrated the successful capture of millions of hydrogen ions with good agreement with the predicted loading based on the timing sequence, trap electric field, and ion beam current. These techniques will be expanded to examine multiple shot capture or 'stacking' to increase the total number of ions stored within HiPAT.

Martin, James J.↗

NASA’s Mid-Atlantic Communities and Areas at Intensive Risk Demonstration: Translating Compounding Hazards to Societal Risk

Remote sensing provides a unique perspective on our dynamic planet, tracking changes and revealing the course of complex interactions. Long term monitoring and targeted observation combine with modeling and mapping to provide increased awareness of hydro-meteorological and geological hazards. Disasters often follow hazards and the goal of NASA’s Disasters Program is to look at the earth as a highly coupled system to reduce risk and enable resilience. Remote sensing and geospatial science are used as tools to help answer critical questions that inform decisions. Data is not the same as information, nor does understanding of processes necessarily translate into decision support for disaster preparedness, response and recovery. Accordingly, NASA is engaging the scientific and decision-support communities to apply remote sensing, modeling, and related applications in Communities and Areas at Intensive Risk (CAIR). In 2017, NASA’s Applied Sciences Disasters Program hosted a regional workshop to explore these issues with particular focus on coastal Virginia and North Carolina. The workshop brought together partners in academia, emergency management, and scientists from NASA and partnering federal agencies to explore capabilities among the team that could improve understanding of the physical processes related to these hazards, their potential impact to changing communities, and to identify methodologies for supporting emergency response and risk mitigation. The resulting initiative, the mid-Atlantic CAIR project, demonstrates the ability to integrate satellite derived earth observations and physical models into actionable, trusted knowledge. Severe storms and associated storm surge, sea level rise, and land subsidence coupled with increasing populations and densely populated, aging critical infrastructure often leave coastal regions and their communities extremely vulnerable. The integration of observations and models allow for a comprehensive understanding of the compounding risk experienced in coastal regions and enables individuals in all positions make risk-informed decisions. This initiative uses a representative storm surge case as a baseline to produce flood inundation maps. These maps predict building level impacts at current day and for sea level rise (SLR) and subsidence scenarios of the future in order to inform critical decisions at both the tactical and strategic levels. To accomplish this analysis, the mid-Atlantic CAIR project brings together Federal research activities with academia to examine coastal hazards in multiple ways: 1) reanalysis of impacts from 2011 Hurricane Irene, using numerical weather modeling in combination with coastal surge and hydrodynamic, urban inundation modeling to evaluate combined impact scenarios considering SLR and subsidence, 2) remote sensing of flood extent from available optical imagery, 3) adding value to remotely sensed flood maps through depth predictions, and 4) examining coastal subsidence as measured through time-series analysis of synthetic aperture radar observations. Efforts and results are published via ArcGIS story maps to communicate neighborhoods and infrastructure most vulnerable to changing conditions. Story map features enable time-aware flood mapping using hydrodynamic models, photographic comparison of flooding following Hurricane Irene, as well as visualization of heightened risk in the future due to SLR and land subsidence.

Rogers, Laura↗

SMEX-Lite Modular Solar Array Architecture

For the most part, Goddard solar arrays have been custom designs that are unique to each mission. The solar panel design has been frozen prior to issuing an RFP for their procurement. There has typically been 6-9 months between RFP release and contract award, followed by an additional 24 months for performance of the contract. For Small Explorer (SMEX) missions, with three years between mission definition and launch, this has been a significant problem. The SMEX solar panels have been sufficiently small that the contract performance period has been reduced to 12-15 months. The bulk of this time is used up in the final design definition and fabrication of flight solar cell assemblies. Even so, it has been virtually impossible to have the spacecraft design at a level of maturity sufficient to freeze the solar panel geometry and release the RFP in time to avoid schedule problems with integrating the solar panels to the spacecraft. With that in mind, the SMEX-Lite project team developed a modular architecture for the assembly of solar arrays to greatly reduce the cost and schedule associated with the development of a mission- specific solar array. In the modular architecture, solar cells are fabricated onto small substrate panels. This modular panel (approximately 8.5" x 17" in this case) becomes the building block for constructing solar arrays for multiple missions with varying power requirements and geometrical arrangements. The mechanical framework that holds these modules together as a solar array is the only mission-unique design, changing in size and shape as required for each mission. There are several advantages to this approach. First, the typical solar array development cycle requires a mission unique design, procurement, and qualification including a custom qualification panel. With the modular architecture, a single qualification of the SMEX-Lite modules and the associated mechanical framework in a typical configuration provided a qualification by similarity to multiple missions. It then becomes possible to procure solar array modules in advance of mission definition and respond quickly and inexpensively to a selected mission's unique requirements. The solar array modular architecture allows the procurement of solar array modules before the array geometry has been frozen. This reduces the effect of procurement lead-time on the mission integration and test flow by as much as 50%. Second, by spreading the non-recurring costs over multiple missions, the cost per unit area is also reduced. In the case of the SMEX-Lite procurement, this reduction was by about one third of the cost per unit area compared to previous SMEX mission-unique procurements. Third, the modular architecture greatly facilitates the infusion of new solar cell technologies into flight programs as these technologies become available. New solar cell technologies need only be fabricated onto a standard-sized module to be incorporated into the next available mission. The modular solar array can be flown in a mixed configuration with some new and some standard cell technologies. Since each module has its own wiring terminals, the array can be arranged as desired electrically with little impact to cost and schedule. The solar array modular architecture does impose some additional constraints on systems and subsystem engineers. First, they must work with discrete solar array modules rather than size the array to fit exactly within an available envelope. The array area is constrained to an integer multiple of the module area. Second, the modular design is optimized for space radiation and thermal environments not greatly different from a typical SMEX LEO environment. For example, a mission with a highly elliptical orbit (e.g., Polar, SMEX/FAST) would require thicker coverglasses to protect the solar cells from the more intense radiation environment.

Lyons, John↗

A Concept for the Deployment of a Large Lunar Crater Radio Telescope Using Teams of Tethered Robots

Kilometer-scale craters on the far side of the Moon have unique potential as future locations for large radio telescopes, which can observe the universe at wavelengths and frequencies (> 10 m, < 30 MHz) not possible with conventional Earth or orbital-based approaches. Distinct advantages of building a Lunar Crater Radio Telescope (LCRT) on the far side include i) isolation from radio noise due to the Earth’s ionosphere, orbiting satellites, and the Sun, ii) days of uninterrupted dark/cold sky viewing during lunar night, and iii) terrain geometry naturally suited for constructing the largest mesh antenna structure in the Solar System. A key challenge to constructing LCRT on the Moon is related to the complexity of deploying a 1-km diameter antenna and hanging receiver within a lunar crater whose diameter, depth, and slope are 3-5 km, 1 km, and ~30 degrees respectively. In this paper, we first evaluate the trade space for deploying a large, complex structure within a crater, and then provide a more detailed concept evaluation of our favored approach, which employs coordinated teams of tethered rovers to extract and suspend a folded antenna from a lander at the base of a crater. NASA’s Jet Propulsion Laboratory in collaboration with California Institute of Technology (Caltech) have developed a novel robotic system for accessing extremely steep terrains; the Axel rover is a two-wheeled rugged terrain vehicle that is supported by an electro-mechanical tether that provides power, data, and tensile support from a top-side anchor location. Recently, a pair of Axel robots have been used in a DuAxel configuration that allows for four-wheel driving and repeated passive anchoring at different locations. The DuAxel system has unique advantages for deploying an LCRT antenna, including the ability to deploy from a lander near a crater, drive a distance to the crater rim to deploy an Axel, and later, retract the deployed Axel in order to sequentially lift up sections of the antenna. Our proposed concept involves delivering a packaged antenna and receiver to the bottom-center of a crater floor on a lander, then later sending a team of multiple DuAxel rovers to retrieve guide wires from the lander, which are pulled to the top of the crater. We explore this concept in detail and provide some initial quantitative analysis to demonstrate the feasibility of our system with respect to the spatial and mass properties of the antenna as juxtaposed to DuAxel capabilities. Finally, we outline next steps towards validating our concept on the way to a future lunar deployment opportunity.

Hallinan, Greg↗

Developing a Hail and Wind Damage Swath Event Database from Daily MODIS True Color Imagery and Storm Reports for Impact Analysis and Applications

Hail and damaging winds are two threats associated with intense and severe thunderstorms that traverse the Midwest and Great Plains during the primary growing season. In certain severe thunderstorm events, large swaths of agricultural crops are impacted, allowing the damage to be viewed from multiple satellite remote sensing platforms. Previous studies have focused on analyzing individual hail and wind damage swaths (HWDSs) using satellite remote sensing, but these swaths have never been officially archived or documented. This lack of documentation has made it difficult to analyze the spatial extent and temporal frequency of HWDSs from year to year. This study utilizes daily true color imagery from MODIS aboard NASA’s Terra and Aqua satellites and daily local storm reports from the Storm Prediction Center to build a database of HWDSs occurring in the months of May through August, for years 2000 through 2020. This database identified 1,646 HWDSs in 12 states throughout the Midwest and Great Plains, confirmed through a combination of archived severe weather warnings, radar information, and official storm reports. For each entry in the HWDS database, a geospatial outline is provided along with the most likely date of first visible damage from MODIS imagery as well as the physical characteristics and time of occurrence estimated from available warnings. This study also provides a summary of the radar characteristics for a portion of the database. This database will further the understanding of severe weather damage by hail and wind to agriculture to help understand the frequency of these events and assist in mapping the impacted areas.

Climatology↗

3D Printing In Zero-G ISS Technology Demonstration

The National Aeronautics and Space Administration (NASA) has a long term strategy to fabricate components and equipment on‐demand for manned missions to the Moon, Mars, and beyond. To support this strategy, NASA and Made in Space, Inc. are developing the 3D Printing In Zero‐G payload as a Technology Demonstration for the International Space Station (ISS). The 3D Printing In Zero‐G experiment ('3D Print') will be the first machine to perform 3D printing in space. The greater the distance from Earth and the longer the mission duration, the more difficult resupply becomes; this requires a change from the current spares, maintenance, repair, and hardware design model that has been used on the International Space Station (ISS) up until now. Given the extension of the ISS Program, which will inevitably result in replacement parts being required, the ISS is an ideal platform to begin changing the current model for resupply and repair to one that is more suitable for all exploration missions. 3D Printing, more formally known as Additive Manufacturing, is the method of building parts/objects/tools layer‐by‐layer. The 3D Print experiment will use extrusion‐based additive manufacturing, which involves building an object out of plastic deposited by a wire‐feed via an extruder head. Parts can be printed from data files loaded on the device at launch, as well as additional files uplinked to the device while on‐orbit. The plastic extrusion additive manufacturing process is a low‐energy, low‐mass solution to many common needs on board the ISS. The 3D Print payload will serve as the ideal first step to proving that process in space. It is unreasonable to expect NASA to launch large blocks of material from which parts or tools can be traditionally machined, and even more unreasonable to fly up multiple drill bits that would be required to machine parts from aerospace‐grade materials such as titanium 6‐4 alloy and Inconel. The technology to produce parts on demand, in space, offers unique design options that are not possible through traditional manufacturing methods while offering cost-effective, high‐precision, low‐unit on‐demand manufacturing. Thus, Additive Manufacturing capabilities are the foundation of an advanced manufacturing in space roadmap. The 3D Printing In Zero‐G experiment will demonstrate the capability of utilizing Additive Manufacturing technology in space. This will serve as the enabling first step to realizing an additive manufacturing, print‐on‐demand "machine shop" for long‐duration missions and sustaining human exploration of other planets, where there is extremely limited ability and availability of Earth‐based logistics support. Simply put, Additive Manufacturing in space is a critical enabling technology for NASA. It will provide the capability to produce hardware on‐demand, directly lowering cost and decreasing risk by having the exact part or tool needed in the time it takes to print. This capability will also provide the much‐needed solution to the cost, volume, and up‐mass constraints that prohibit launching everything needed for long‐duration or long‐distance missions from Earth, including spare parts and replacement systems. A successful mission for the 3D Printing In Zero‐G payload is the first step to demonstrate the capability of printing on orbit. The data gathered and lessons learned from this demonstration will be applied to the next generation of additive manufacturing technology on orbit. It is expected that Additive Manufacturing technology will quickly become a critical part of any mission's infrastructure.

Werkheiser, Niki↗

System Modeling of a Lunar Molten Regolith Electrolysis Plant

Introduction: In-Situ Resource Utilization (ISRU) is the process of extracting local resources to produce commodities for propulsion, life support systems, and off-planet construction rather than transporting consumables from Earth. Molten Regolith Electrolysis (MRE) is a novel ISRU method of extracting oxygen gas and metal alloy from lunar regolith. The MRE process involves placing lunar regolith between two electrodes, through which current is passed, to melt the regolith and reduce the metal oxide constituents by direct electrolysis (e.g. FeO, SiO2, MgO, Al2O3) into oxygen gas and metal alloys. The oxygen is liquefied and used as propellant for landers, while the metals (e.g. Ferro-alloys) are further processed and used in structural building materials and parts manufacturing. A system model was developed that accounted for the major processes of an MRE plant (from excavation of raw materials to storage of products) to assess the feasibility of a lunar MRE plant. The System Engineering and Integration (SE&I) ISRU Modeling and Analysis (SIMA) team utilized its previously documented system sizing model, the Mission Analysis and Integration Tool (MAIT) [1] as framework of the system model. MAIT uses MATLAB/Simulink to integrate subsystem models into a complete system model of the MRE plant. Total mass, volume, and power requirements were computed for numerous iterations of a MRE plant. System Model: Figure 1: MRE Plant Block Diagram The regolith excavation model determines the mass and power needed to excavate sufficient regolith. The preheating auger initiates the regolith heating process before regolith enters the MRE re-actor to reduce the energy required to turn the solid into a molten liquid. The MRE reactor is modeled in COMSOL Multiphysics and based on the research by Dominguez, Sibille, and Schreiner [2, 3, 4]. This preliminary reactor model provides an accurate calculation of thermal equilibrium during electrochemical operation of the reactor system to assess the optimal mass and power required to process the inlet flow of regolith. The model also computes the outlet flowrates of oxygen and molten products. For this analysis, the primary components of the metal alloy considered were iron and silicon. The oxygen is then purified using an Yttrium Stabilized Zirconia (YSZ) electrode, followed by liquefaction using a 90K cryocooler to be stored as liquid oxygen in insulated cylindrical tanks. In future iterations of the system model, the molten metal tapped from the MRE reactor will undergo additional processing or refinement. However, downstream handling of metals is currently a technology gap that is missing a high TRL subsystem model. Therefore, for this analysis, the accumulated metal alloy stream terminates after leaving the MRE reactor. Study Goals: This analysis investigates multiple input variables to the system to determine the sensitivity of a (near) complete plant at full-scale. This preliminary investigation ran parametric sweeps on the MRE reactor geometry, electrical current supply, layers of multi-layer insulation (MLI) on the reactor, size of the electrodes in the oxygen purification model, and regolith composition (based on landing site location). Three production targets of oxygen (1,000, 10,000, and 50,000 kg/yr) were investigated for this analysis. The parametric sweeps conducted in this analysis provide valuable insight into the expected impact of the various model inputs on plant size. This information can be used to identify the most critical components of the plant and guide future decisions on allocating funding for research and development, providing subsystem developers with appropriate interfaces with downstream and upstream processes, and assessing the overall feasibility of MRE when compared to other ISRU plants. References: [1] Carlson, A. et al. (2024) ICES, ICES-2024-53. [2] Dominguez, D.A., and Sibille, L. (2011) AIAA, AIAA-2011-700. [3] Schreiner, S.S. (2015) MIT, Dissertation. [4] Schreiner, S.S. et al. (2016) ASR, 57(7), pp.1585-1603.

ISRU↗

Science Opportunity Analyzer (SOA) Version 8

SOA allows scientists to plan spacecraft observations. It facilitates the identification of geometrically interesting times in a spacecraft s orbit that a user can use to plan observations or instrument-driven spacecraft maneuvers. These observations can then be visualized multiple ways in both two- and three-dimensional views. When observations have been optimized within a spacecraft's flight rules, the resulting plans can be output for use by other JPL uplink tools. Now in its eighth major version, SOA improves on these capabilities in a modern and integrated fashion. SOA consists of five major functions: Opportunity Search, Visualization, Observation Design, Constraint Checking, and Data Output. Opportunity Search is a GUI-driven interface to existing search engines that can be used to identify times when a spacecraft is in a specific geometrical relationship with other bodies in the solar system. This function can be used for advanced mission planning as well as for making last-minute adjustments to mission sequences in response to trajectory modifications. Visualization is a key aspect of SOA. The user can view observation opportunities in either a 3D representation or as a 2D map projection. Observation Design allows the user to orient the spacecraft and visualize the projection of the instrument field of view for that orientation using the same views as Opportunity Search. Constraint Checking is provided to validate various geometrical and physical aspects of an observation design. The user has the ability to easily create custom rules or to use official project-generated flight rules. This capability may also allow scientists to easily assess the cost to science if flight rule changes occur. Data Output allows the user to compute ancillary data related to an observation or to a given position of the spacecraft along its trajectory. The data can be saved as a tab-delimited text file or viewed as a graph. SOA combines science planning functionality unique to both JPL and the sponsoring spacecraft. SOA is able to ingest JPL SPICE Kernels that are used to drive the tool and its computations. A Percy search engine is then included that identifies interesting time periods for the user to build observations. When observations are then built, flight-like orientation algorithms replicate spacecraft dynamics to closely simulate the flight spacecraft s dynamics. SOA v8 represents large steps forward from SOA v7 in terms of quality, reliability, maintainability, efficiency, and user experience. A tailored agile development environment has been built around SOA that provides automated unit testing, continuous build and integration, a consolidated Web-based code and documentation storage environment, modern Java enhancements, and a focus on usability

Witoff, Robert J.↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

Compatibility Assessment Tool

In support of ground system development for the Space Launch System (SLS), engineers are tasked with building immense engineering models of extreme complexity. The various systems require rigorous analysis of pneumatics, hydraulic, cryogenic, and hypergolic systems. There are certain standards that each of these systems must meet, in the form of pressure vessel system (PVS) certification reports. These reports can be hundreds of pages long, and require many hours to compile. Traditionally, each component is analyzed individually, often utilizing hand calculations in the design process. The objective of this opportunity is to perform these analyses in an integrated fashion with the parametric CADCAE environment. This allows for systems to be analyzed on an assembly level in a semi-automated fashion, which greatly improves accuracy and efficiency. To accomplish this, component specific parameters were stored in the Windchill database to individual Creo Parametric models based on spec control drawings. These parameters were then accessed by using the Prime Analysis within Creo Parametric. MathCAD Prime spreadsheets were created that automatically extracted these parameters, performed calculations, and generated reports. The reports described component compatibility based on local conditions such as pressure, temperature, density, and flow rates. The reports also determined component pairing compatibility, such as properly sizing relief valves with regulators. The reports stored the input conditions that were used to determine compatibility to increase traceability of component selection. The desired workflow for using this tool would begin with a Creo Schematics diagram of a PVS system. This schematic would store local conditions and locations of components. The schematic would then populate an assembly within Creo Parametric, using Windchill database parts. These parts would have their attributes already assigned, and the MathCAD spreadsheets could begin running through database parts to determine which components would be suited for specific locations within the assembly. This eliminates a significant amount of time from the design process, and makes initial analysis assessments more accurate. Each component that would be checked for a location within the assembly would generate a report, showing whether the component was compatible. These reports could be used to generate the PVS report without the need to perform the same analysis multiple times. This process also has the potential to be expanded upon to further automate PVS reports. The integration of software codes or macros could be used to automatically check through hundreds of parts for each location on the schematic. If the software could recognize which type of component would be necessary for each location, it is possible that simply starting the macro could completely choose all the components needed for the schematic, and in turn the system. This would save many hours of work initially selecting components, which could end up saving money. Overall, this process helps to automate initial component selections for PVS systems to fit local design specifications. These selections will automatically generate reports showing how the design criteria are met by the specific component that was chosen. These reports will contribute to easier compilation of the PVS certification reports, which currently take a great amount of time and effort to produce.

Egbert, James Allen↗

Performance Comparison of Wireless Sensor Network Standard Protocols in an Aerospace Environment: ISA100.11a and ZigBee

Wireless Sensor Networks (WSNs) can provide a substantial benefit in spacecraft systems, reducing launch weight and providing unprecedented flexibility by allowing instrumentation capabilities to grow and change over time. Achieving data transport reliability on par with that of wired systems, however, can prove extremely challenging in practice. Fortunately, much progress has been made in developing standard WSN radio protocols for applications from non-critical home automation to mission-critical industrial process control. The relative performances of candidate protocols must be compared in representative aerospace environments, however, to determine their suitability for spaceflight applications. In this paper, we will present the results of a rigorous laboratory analysis of the performance of two standards-based, low power, low data rate WSN protocols: ZigBee Pro and ISA100.11a. Both are based on IEEE 802.15.4 and augment that standard's specifications to build complete, multi-hop networking stacks. ZigBee Pro targets primarily the home and office automation markets, providing an ad-hoc protocol that is computationally lightweight and easy to implement in inexpensive system-on-a-chip components. As a result of this simplicity, however, ZigBee Pro can be susceptible to radio frequency (RF) interference. ISA100.11a, on the other hand, targets the industrial process control market, providing a robust, centrally-managed protocol capable of tolerating a significant amount of RF interference. To achieve these gains, a coordinated channel hopping mechanism is employed, which entails a greater computational complexity than ZigBee and requires more sophisticated and costly hardware. To guide future aerospace deployments, we must understand how well these standards relatively perform in analog environments under expected operating conditions. Specifically, we are interested in evaluating goodput -- application level throughput -- in a representative crewed environment in the presence of varying levels of 802.11g Wi-Fi traffic. To do so, we use the NASA Johnson Space Center Wireless Habitat Testbed (WHT), a metallic, habitation-sized module designed for co-existence testing of wireless systems. In its quiescent state, the sealed WHT provides an RF-quiet environment to which we can selectively add interfering systems; it also provides a realistic level of multi-path self-interference for systems under investigation. In our test, we deploy two representative five node networks, configured in a star topology with all nodes reporting directly to a WSN gateway. Each ZigBee network WSN node is built using a Texas Instruments (TI) CC2530 system-on-a-chip radio running TI's ZigBee Pro Z-stack. Each ISA100.11a network node is built using a Nivis VersaNode 210 system-on-a-chip radio. In both cases, radios interface with TI MSP430-F5438 microcontroller implementing a common test application. Interference is provided by a D-link 802.11g Wi-Fi router transporting traffic generated using the Iperf network testing tool. For the single-channel ZigBee network, effects of both direct and indirect Wi-Fi interference are evaluated. For the channel-hopping ISA100.11a network, effects of interference from multiple Wi-Fi routers configured in non-overlapping 802.11g channels are evaluated. Our results show that, in general, the more lightweight ZigBee network performs well at low interference levels, but performance degrades as interference increases. Conversely, the more complex and costly ISA100.11a network continues to perform well as Wi-Fi interference levels increase.

Wagner, Raymond S.↗

Adaptative Site Management for a 115 Acre Chlorinated Solvent Plume with Two Separate Source Areas at Kennedy Space Center, Florida

Background/Objectives. During Resource Conservation and Recovery Act (RCRA) Facility Investigation (RFI) activities, Geosyntec delineated a chlorinated volatile organic compound (CVOC) plume at the National Aeronautics and Space Administration’s (NASA’s) Vehicle Assembly Building (VAB) area located at KSC, Florida. The RFI activities identified an approximate 115-acre dissolved plume (primarily vinyl chloride) and a trichloroethene (TCE) source area in an active aerospace complex that is surrounded by sensitive wetland/waterbodies. Due to the size of the impacted area, the Corrective Measure Design included a multi-component strategy: (i) address the source area via bioremediation; (ii) protect sensitive wetlands from impacted groundwater discharge via biosparging; and (iii) Long Term Monitoring (LTM) of the remaining dissolved plume. After the Corrective Measures implementation (CMI), NASA and Geosyntec worked with Florida Department of Environmental Protection (FDEP) to implement an adaptive site management for the complex, 115-acre site outside of the traditional RCRA process. The adaptive site management approach relied on performing supplemental assessments and implementing Interim Measures (IMs) to further assess and implement remedies over time while working within site and budget constraints, with an overall goal of achieving enough mass reduction to transition the entire site to LTM and eventually achieve site closure. Approach/Activities. After the biosparge barrier was operational and bioremediation within the source area (referred to as Hot Spot 1) achieved the Corrective Action Objective (CAO), supplemental assessment of the area between Hot Spot 1 and the biosparge barrier was performed. The conceptual site model was updated using the supplemental assessment results and an air sparge system IM was designed to treat an approximate 1.2 acre area (referred to as Hot Spot 2). After installation of the air sparge system, supplemental assessment within the remainder of the 115-acre dissolved plume was performed and a second TCE source area was identified. The TCE source area and associated areas with elevated CVOC concentrations (referred to as Hot Spot 3) were delineated and a bioremediation IM was implemented. Also, the downgradient impacts from Hot Spot 3 were adjacent to a sensitive waterbody, and negotiations with the FDEP allowed the area to be monitored using LTM. Results/Lessons Learned. The performance of supplemental assessment activities and implementation of remedial alternatives as IMs allowed NASA to successfully address groundwater impacts over time, while working within the FDEP regulatory framework. The implementation of the CMI and multiple IMs has achieved the following goals: (i) the biosparge barrier has mitigated the potential discharge of impacted groundwater to an adjacent wetland; (ii) enhanced bioremediation within Hot Spot 1 achieved the CAO within 2 years and transitioned the area into LTM; (iii) operation of an air sparge system within Hot Spot 2 removed TCE as a constituent of concern and contributed to a reduction (approximately 43%) in the impacted groundwater area outside the air sparge treatment area (plume collapse); and (iv) bioremediation within Hot Spot 3 removed approximately 80% of the CVOC mass and contributed to a reduction (approximately 47%) in the impacted groundwater area outside the bioremediation IM treatment area. Overall, the adaptive approach is protecting the sensitive water bodies surrounding the complex site and reducing the area of impacted groundwater, which is moving the entire site towards LTM.

Rebecca C Daprato↗

Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Technology Development Overview

The successful flight of the Inflatable Reentry Vehicle Experiment (IRVE)-3 has further demonstrated the potential value of Hypersonic Inflatable Aerodynamic Decelerator (HIAD) technology. This technology development effort is funded by NASA's Space Technology Mission Directorate (STMD) Game Changing Development Program (GCDP). This paper provides an overview of a multi-year HIAD technology development effort, detailing the projects completed to date and the additional testing planned for the future. The effort was divided into three areas: Flexible Systems Development (FSD), Mission Advanced Entry Concepts (AEC), and Flight Validation. FSD consists of a Flexible Thermal Protection Systems (FTPS) element, which is investigating high temperature materials, coatings, and additives for use in the bladder, insulator, and heat shield layers; and an Inflatable Structures (IS) element which includes manufacture and testing (laboratory and wind tunnel) of inflatable structures and their associated structural elements. AEC consists of the Mission Applications element developing concepts (including payload interfaces) for missions at multiple destinations for the purpose of demonstrating the benefits and need for the HIAD technology as well as the Next Generation Subsystems element. Ground test development has been pursued in parallel with the Flight Validation IRVE-3 flight test. A larger scale (6m diameter) HIAD inflatable structure was constructed and aerodynamically tested in the National Full-scale Aerodynamics Complex (NFAC) 40ft by 80ft test section along with a duplicate of the IRVE-3 3m article. Both the 6m and 3m articles were tested with instrumented aerodynamic covers which incorporated an array of pressure taps to capture surface pressure distribution to validate Computational Fluid Dynamics (CFD) model predictions of surface pressure distribution. The 3m article also had a duplicate IRVE-3 Thermal Protection System (TPS) to test in addition to testing with the Aerocover configuration. Both the Aerocovers and the TPS were populated with high contrast targets so that photogrammetric solutions of the loaded surface could be created. These solutions both refined the aerodynamic shape for CFD modeling and provided a deformed shape to validate structural Finite Element Analysis (FEA) models. Extensive aerothermal testing has been performed on the TPS candidates. This testing has been conducted in several facilities across the country. The majority of the testing has been conducted in the Boeing Large Core Arc Tunnel (LCAT). HIAD is continuing to mature testing methodology in this facility and is developing new test sample fixtures and control methodologies to improve understanding and quality of the environments to which the samples are subjected. Additional testing has been and continues to be performed in the NASA LaRC 8ft High Temperature Tunnel, where samples up to 2ft by 2ft are being tested over representative underlying structures incorporating construction features such as sewn seams and through-thickness quilting. With the successful completion to the IRVE-3 flight demonstration, mission planning efforts are ramping up on the development of the HIAD Earth Atmospheric Reenty Test (HEART) which will demonstrate a relevant scale vehicle in relevant environments via a large-scale aeroshell (approximately 8.5m) entering at orbital velocity (approximately 7km/sec) with an entry mass on the order of 4MT. Also, the Build to Print (BTP) hardware built as a risk mitigation for the IRVE-3 project to have a "spare" ready to go in the event of a launch vehicle delivery failure is now available for an additional sub-orbital flight experiment. Mission planning is underway to define a mission that can utilize this existing hardware and help the HIAD project further mature this technology.

Hughes, Stephen J.↗

A Notional Artemis Lunar Surface Exploration Package (ArLSEP) based on the Gandalf Staff Platform

Introduction: The Artemis program is planning to deliver crew and cargo to the lunar surface, but there is no current package for supporting lunar in-struments and experiments similar to the Apollo Lunar Surface Exploration Package (ALSEP). This abstract provides a possible concept for such a package using the Gandalf Staff Platform as a common core. Gandalf Staff: The Gandalf Staff is an early prototype system developed over FY’21/FY’22 using NASA Science Technology Mission Directorate (STMD) Center Information Fund (CIF) grants to de-sign, build and test “proof-of-concept” components. These components include a 24v battery powered monopole that powers a suite of subsystems, including a Graphical User Interface (GUI) for crew, surface voice and data communications, Lunar Search and Rescue (LunaSAR) navigation and communications, LiDAR, field site external lighting, 360-degree camera, and a geothermal instrument for measuring sub-surface temperature gradient. The staff can be carried independently by an Extra-Vehicular Activity (EVA) astronaut, or can be mounted into a tripod for “hands free” support at a surface site being investigated. The staff can be attached to an external solar array and power storage system for long-duration operations. [1,2] ALSEP: An ASLEP flew on each mission Apollo 12 to Apollo 17. For Apollo 11, a simplified packaged called the Early Apollo Scientific Experiments Pack-age (EASEP) was flown. Each package included a “Central Station” that provided the power and communications connected to a variety of instruments and sensors. The power was provided by a Radioisotope Thermoelectric Generator (RTG) fueled by Plutoni-um-238 generating 70 watts of power (initially, decayed over time) [3]. The communications system provide for direct to Earth data transfer from the lunar surface. Each pack-age was stowed externally in the Lunar Module (LM) Scientific Equipment (SEQ) bay with a mass up to 163 kg (Apollo 17). The crew unloaded the ALSEP from the LM and deployed the instruments on the lunar surface. Although designed to operate for only 1 year, many sites operated for up to 8 years successfully [4]. The Active Seismic Experiment (ASE) included 3 geophones for detecting seismic waves created by mortars and thumpers deployed by the crew. Other active experiments measured the lunar atmosphere, the heat flow in the subsurface, the lunar gravity and potential gravity waves, the lunar magnetic field, the solar wind and plasma interactions in cislunar space. Passive experiments included collectors for dust and cosmic rays, and retroreflectors for precise measurements of distance using a laser from Earth. The ALSEP program continues to generate insights into lunar formation and evolution. ArLSEP Concepts: The lunar surface science package for the Artemis program will hopefully exceed the capability of the ALSEP. There are multiple issues for discussion leading to the design of a new ArLSEP, needing requirements definition from the science community, NASA mission architecture, and NASA budget planners. 1. Delivery Mechanism Two possible projects currently provide capability to deliver scientific cargo to the lunar surface: 1) the Commercial Lunar Payload Services (CLPS) [5] and the Human Landing System (HLS) [6, 7]. Each project is controlled by a different organization within NASA and budgeted with different criteria although both support lunar exploration. The HLS system delivers crew (and potentially cargo) to human landing sites. If an ArLSEP is “predeployed” to such a site, the design must include power (either from the vehicle or independently) to keep the electronics functioning until deployed by the crew. If an ArLSEP is delivered on a vehicle after the crew is present on the lunar surface, safety protocols require adequate distance from the humans for impact from descent propelled sur-face regolith ejecta. This distance can not exceed the capability of the crew to walk (if no rover) to the vehicle for ArLSEP deployment. 2. Overall Guidelines The general design of ArLSEP will likely follow the ALSEP with a common system for communications and power; however, significant architecture differences between Apollo and Artemis exist. Power: The RTG will not be available for early Artemis missions nor likely follow-on Lunar Exploration Transportation Services (LETS) missions [8]. Thus, ArLSEP power must be supplied by solar arrays with sufficient battery capability to “keep alive” necessary electronics during any lunar surface eclipse period. Communication: The Artemis program is developing a series of communications satellites for lunar orbit to provide surface transmission of data and voice to Earth. Called “LunaNET”, this network is component useful for ArLSEP since south polar locations may not always have direct “line-of-sight” to Earth [9]. 3. Concept of Operations (ConOps) The general ConOps for ArLSEP is to deliver the package to lunar surface before the crew arrives, and then have the crew deploy the package after some period of time. This requires coordinated design (for power systems) and launch window (for schedule) on both the cargo and crew missions. Once the ArLSEP is deployed, it will operate autonomously for a number of years. It should be designed to be EVA compatible for crew maintenance and upgrade. 4. Notional Design (for discussion purpose only) The landing site near the South Pole is expected to have no eclipse cycle exceeding 5 days, so the “keep alive” power is 144 hours (6 days to include margin). A 12v ArLSEP will use rechargeable LiFePO4 cells, which are common in the Electric Vehicle (EV) industry. With a current of 5 amps and a 125 watt system, the mass is about 90kg. The comm. system and structure adds another 10kg, thus the “Central Station” is approximately 100kg. The solar power is collected on four arrays (each 2m above the surface), and the entire ArLSEP is designed to stow in a 2m x 1m x 1m volume. The experiment and instrument design will vary for each installation and add mass to the total (although they are expected to fit within the 2m3 volume). Seismic wave generation will likely not be provided with mortars, thus an electric “thumper” will be required. Active instruments such as imaging systems and sensing instruments will benefit from the additional power and communication capability provided by ArLSEP. Passive systems such as retroreflectors, witness plates, and cosmic dust collectors can be added to either the landing vehicle and/or the ArLSEP. With repeated HLS missions to the same human site, the ArLSEP can be expanded and easily maintained for long duration science collection on the lunar surface.

ALSEP↗

SSME Condition Monitoring Using Neural Networks and Plume Spectral Signatures

For a variety of reasons, condition monitoring of the Space Shuttle Main Engine (SSME) has become an important concern for both ground tests and in-flight operation. The complexities of the SSME suggest that active, real-time condition monitoring should be performed to avoid large-scale or catastrophic failure of the engine. In 1986, the SSME became the subject of a plume emission spectroscopy project at NASA's Marshall Space Flight Center (MSFC). Since then, plume emission spectroscopy has recorded many nominal tests and the qualitative spectral features of the SSME plume are now well established. Significant discoveries made with both wide-band and narrow-band plume emission spectroscopy systems led MSFC to develop the Optical Plume Anomaly Detection (OPAD) system. The OPAD system is designed to provide condition monitoring of the SSME during ground-level testing. The operational health of the engine is achieved through the acquisition of spectrally resolved plume emissions and the subsequent identification of abnormal emission levels in the plume indicative of engine erosion or component failure. Eventually, OPAD, or a derivative of the technology, could find its way on to an actual space vehicle and provide in-flight engine condition monitoring. This technology step, however, will require miniaturized hardware capable of processing plume spectral data in real-time. An objective of OPAD condition monitoring is to determine how much of an element is present in the SSME plume. The basic premise is that by knowing the element and its concentration, this could be related back to the health of components within the engine. For example, an abnormal amount of silver in the plume might signify increased wear or deterioration of a particular bearing in the engine. Once an anomaly is identified, the engine could be shut down before catastrophic failure occurs. Currently, element concentrations in the plume are determined iteratively with the help of a non-linear computer code called SPECTRA, developed at the USAF Arnold Engineering Development Center. Ostensibly, the code produces intensity versus wavelength plots (i.e., spectra) when inputs such as element concentrations, reaction temperature, and reaction pressure are provided. However, in order to provide a higher-level analysis, element concentration is not specified explicitly as an input. Instead, two quantum variables, number density and broadening parameter, are used. Past experience with OPAD data analysis has revealed that the region of primary interest in any SSME plume spectrum lies in the wavelength band of 3300 A to 4330 A. Experience has also revealed that some elements, such as iron, cobalt and nickel, cause multiple peaks over the chosen wavelength range whereas other elements (magnesium, for example) have a few, relatively isolated peaks in the chosen wavelength range. Iteration with SPECTRA as a part of OPAD data analysis is an incredibly labor intensive task and not one to be performed by hand. What is really needed is the "inverse" of the computer code but the mathematical model for the inverse mapping is tenuous at best. However, building generalized models based upon known input/output mappings while ignoring details of the governing physical model is possible using neural networks. Thus the objective of the research project described herein was to quickly and accurately predict combustion temperature and element concentrations (i.e., number density and broadening parameter) from a given spectrum using a neural network. In other words, a neural network had to be developed that would provide a generalized "inverse" of the computer code SPECTRA.

Hopkins, Randall↗

Path Toward a Unifid Geometry for Radiation Transport

The Direct Accelerated Geometry for Radiation Analysis and Design (DAGRAD) element of the RadWorks Project under Advanced Exploration Systems (AES) within the Space Technology Mission Directorate (STMD) of NASA will enable new designs and concepts of operation for radiation risk assessment, mitigation and protection. This element is designed to produce a solution that will allow NASA to calculate the transport of space radiation through complex computer-aided design (CAD) models using the state-of-the-art analytic and Monte Carlo radiation transport codes. Due to the inherent hazard of astronaut and spacecraft exposure to ionizing radiation in low-Earth orbit (LEO) or in deep space, risk analyses must be performed for all crew vehicles and habitats. Incorporating these analyses into the design process can minimize the mass needed solely for radiation protection. Transport of the radiation fields as they pass through shielding and body materials can be simulated using Monte Carlo techniques or described by the Boltzmann equation, which is obtained by balancing changes in particle fluxes as they traverse a small volume of material with the gains and losses caused by atomic and nuclear collisions. Deterministic codes that solve the Boltzmann transport equation, such as HZETRN [high charge and energy transport code developed by NASA Langley Research Center (LaRC)], are generally computationally faster than Monte Carlo codes such as FLUKA, GEANT4, MCNP(X) or PHITS; however, they are currently limited to transport in one dimension, which poorly represents the secondary light ion and neutron radiation fields. NASA currently uses HZETRN space radiation transport software, both because it is computationally efficient and because proven methods have been developed for using this software to analyze complex geometries. Although Monte Carlo codes describe the relevant physics in a fully three-dimensional manner, their computational costs have thus far prevented their widespread use for analysis of complex CAD models, leading to the creation and maintenance of toolkit-specific simplistic geometry models. The work presented here builds on the Direct Accelerated Geometry Monte Carlo (DAGMC) toolkit developed for use with the Monte Carlo N-Particle (MCNP) transport code. The workflow for achieving radiation transport on CAD models using MCNP and FLUKA has been demonstrated and the results of analyses on realistic spacecraft/habitats will be presented. Future work is planned that will further automate this process and enable the use of multiple radiation transport codes on identical geometry models imported from CAD. This effort will enhance the modeling tools used by NASA to accurately evaluate the astronaut space radiation risk and accurately determine the protection provided by as-designed exploration mission vehicles and habitats

Lee, Kerry↗