Results for “Operability” — Page 31

NASA NTRS2006

Implementing distributed operations : a comparison of two Deep Space Missions

Two very different deep space exploration missions—Mars Exploration Rover and Cassini—have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a prime mission of four years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process.

Larsen, Barbara↗

NASA NTRS2006

Cassini distributed instrument operations – what we’ve learned since Saturn orbit insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained realworld experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the “tour”) and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Woncik, Pam↗

NASA NTRSDate not supplied

ISS Payload Operations Training During the COVID-19 Pandemic: Impacts and Solutions

The onset of the COVID-19 pandemic brought a dramatic and rapid transformation to almost every aspect of humanity in 2020. The world’s space agencies and their missions were not immune to the wide-sweeping changes. One discipline principally affected was mission operations and the various groups supporting that function. Mission support teams, especially for complex and crewed missions like the International Space Station were forced to rapidly rethink how and where control center staff performed their vital work. Operations training – an essential element to mission ops, had unique hurdles to overcome. Operations training is responsible for preparing astronaut crews for their missions, providing training to flight controllers, as well as ensuring that new team members are ready to join their colleagues. Every element of training was impacted by COVID restrictions. From orientation and introductory classes for new controllers, simulations and advanced lessons, On the Job Training and final evaluations; all aspects faced new challenges. Trainers at NASA’s Marshall Space Flight Center in Huntsville, Alabama, were forced to become more efficient with trainees and resources to continue supporting payload operations. The pandemic started in the USA in March 2020. Immediately, NASA mandated that the support for ISS real-time operations was critical. As a result, physical access to key facilities was restricted. Trainers and trainees had to quickly shift to 100 percent remote learning. In the short term, this was not a problem. However, instructors discovered lessons that they were accustomed to delivering in a classroom environment did not translate to remote teaching. Another hurdle to operations training was the mandate that all simulations could only be held remotely. The logistics of even small simulations proved to be challenging due to IT restrictions and public internet limitations. With simulations essentially stopped, as well as the restrictions on most OJT, trainees were essentially stopped in their advancement towards certification. Once limitations were identified, trainers prioritized new options. Transitioning to all electronic learning materials was a relatively easy fix. Teaching to large groups took additional shifts in the training paradigm. Methods for preparing astronauts for their missions were revised. Simulation supervisors found more efficient techniques to provide realistic training experience. Communication and approvals from management was essential. In every case, the payload operations instructors found novel solutions to all functions listed. This paper will discuss the factors and solutions payloads operations trainers found to keep scientific research on the ISS flying forward to mission success.

ISS↗

NASA NTRS2021

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗

NASA NTRS2022

NASA System-Wide Safety Wildland Firefighting Operations Workshop Report

On March 9-11, 2022, NASA’s System-Wide Safety Wildland Firefighting Operations Workshop engaged the broader wildland firefighting management ecosystem in a safety-oriented discussion via a virtual platform. This enabled a better understanding of how NASA and community expertise can be leveraged in the safe development of current and future firefighting systems and operations. The goals of the workshop were to: (1) identify and prioritize the top safety-oriented risks, gaps in capabilities, and emerging technologies to enhance wildland firefighting for both near-term and far-term concepts, with a specific focus on aviation operations and (2) engage the stakeholder community in defining emergent safety-oriented scope, roles, responsibilities, and procedures for agents undergoing increasingly complex wildland firefighting operations in information-rich, but uncertain environments. Workshop participants were solicited from wildland firefighting stakeholders across government, industry, and academia. All levels of government were engaged, as NASA sought attendees from federal, state, local, and tribal government agencies. Industry participants from traditional wildland firefighting domains such as data visualization and equipment manufacturers were invited, and corporate attendees from novel application domains such as aerial robotics and autonomous systems were present as well. The top three findings were as follows: (1) Enhancing situation awareness is a safety priority, especially in the use of aerial assets; (2) Timely access to information along with data fusion and integrated displays will enhance safety-critical decision-making both inside and outside aviation contexts; and (3) Tailorable standards and common operating pictures in the field will enhance inter-agency cooperation in the wildland firefighting lifecycle and enable the optimal use of limited resources such as aerial assets. The workshop helped inform NASA of the relevant safety-related wildland firefighting concerns and aided the broader ecosystem in understanding the potential safety-oriented role NASA might play in this community. Increased engagement with crucial governmental stakeholders (e.g., U.S. Forest Service, CAL FIRE, etc.) along with industry partners in cutting- edge information -centric domains is a fundamental next step. Additionally, the workshop findings will help define the first of a series of operationally challenging demonstrations, held in concert with strategic ecosystem partners, known as the Safety Demonstrator Series for NASA’s System-Wide Safety project. The first demonstration is set in the wildland firefighting application domain and will: (1) examine high risk operational scenarios to reduce their overall risk via services, functions or capabilities that act as risk mitigators (or transfer that risk to automated systems better able to tolerate it) and (2) explore novel tools and technologies that will enhance safety margins by enabling non-traditional or neoteric operational paradigms.

wildland firefighting↗

NASA NTRSDate not supplied

Human-Autonomy Teaming Research in Support of m:N Operations

Since 2019, the NASA and industry partners have been involved in research focused on a novel paradigm for operations of remotely piloted aircraft. This paradigm involves multiple people sharing a fleet of multiple vehicles between them. Referred to as m:N (pronounced “em-to-en”), this configuration describes a ratio where m is the number of operators and N is the number of vehicles. Through force and asset multiplication, the m:N concept seeks to enable a scalable and resilient operation of remotely crewed vehicles. The primary means of obtaining such a robust operation is through allowing a flexible crew of variable size to dynamically attend to the needs of assets in while performing real-time operator workload management. It is in that sense that assets are shared between operators: as needed (such as in events of elevated workload) an operator in an m:N context can “handoff” the responsibility for some amount of assets, nh < N, to be absorbed by the m – 1 crew members on staff. At some time later, these nh assets could be returned to their original owner or they may be further distributed to other crew if called for by the mission. During this panel, I will elaborate on the research activity undertaken by the Human-Autonomy Teaming (HAT) Laboratory at NASA Ames Research Center over the previous three years. The studies conducted by the HAT Lab range from interviews with subject matter experts, a cognitive walkthrough, a task analysis, and two simulation experiments to-date. During experimentation, pilots made use of an advanced Ground Control Station developed by the HAT Lab and industry partners to simulate m:N operations in two large, metropolitan areas of Southern California: Los Angeles and San Diego. Further experimentation planned over the next few years. Results from our research to-date indicates that pilots of a moderately sized fleet of about a dozen remotely crewed aircraft adequately maintained safety performance and situation awareness of their aircraft, even when presented with unexpected situations of heightened workload.

multi-vehicle control↗

NASA NTRSDate not supplied

Extensible Traffic Management (xTM) - High-altitude Operations and Beyond

The technology development of balloons, airships, and high-altitude long-endurance (HALE) high-aspect-ratio wing aerial vehicles has expedited the deployment of high-altitude operations above Flight Level (FL) 600. It allows broader communication service area coverage than at ground level and enables efficient and precise earth observation to help address global climate change. Meanwhile, a record number of orbital launches were conducted in 2021. New mission concepts including those for small satellites, satellite constellations, suborbital tourism and point to point cargo transport are being developed. To enable efficient and safe operations of new-entrant vehicles and to alleviate the potential burden on air traffic controllers, the concept of Unmanned aircraft systems Traffic Management (UTM) explored a different approach requiring cooperative operations among operators/pilots through operational intent sharing and coordination. This concept has been extended and proposed by the community to handle traffic management for high-altitude operations. While the concept and basic system were tested in UTM, there are many critical capabilities needed for high-altitude operations. This talk will introduce the challenges brought by high-altitude operations and space operations and on-going research activities in developing critical capabilities for extensible traffic management at NASA.

Extensible Traffic Management↗

NASA NTRSDate not supplied

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 NTRSDate not supplied

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 NTRSDate not supplied

Comparative Analysis of Airspace System Accessibility for Uncrewed Aircraft Systems for Regional Operations

As part of newly developing aviation markets, fixed-wing Uncrewed Aircraft Systems (UAS) are projected to impact airspace systems and conventional air traffic in the future. The initial introduction of fixed-wing cargo UAS for regional operations is anticipated to occur at smaller under-utilized airports. Therefore, this paper assesses the integration potential of regional fixed-wing cargo UAS into the airspace system. A baseline is established to identify potential airports for UAS operations in different areas. Additionally, using 2022 data, regional aircraft eligible for future cargo UAS operations are investigated. Finally, the accessibility of these regional aircraft at the identified airports was analyzed. Based on the availability of current certified landing systems needed for initial UAS operations, the potential airports for UAS operations are compared in the areas of Germany, Texas, and California. Despite 173 identified airports for potential UAS operations in Germany, 376 in Texas, and 227 in California, only eleven of these airports provide current certified landing systems needed for initial UAS operations. However, other landing system technologies that are currently under development, such as vision-based landing systems, might support UAS accessibility at the identified airports for potential UAS operations in the future.

Uncrewed aircraft systems↗

NASA NTRSDate not supplied

Incorporating UAS Traffic Management into Wildland Firefighting Operations: Initial Findings of Subject Matter Expert Interviews

Uncrewed Aircraft Systems (UASs) are being utilized throughout the disaster and emergency response domain, including in wildland firefighting operations. While UASs can offer safety benefits in comparison to crewed aircraft, such as removing the human pilot from the vehicle so that they are not exposed to the same risks and the ability to operate in low-visibility conditions, they are not without tradeoffs. For example, it can be challenging for UAS pilots (UASPs) to build situation awareness of the airspace in which their UAS is operating. In order to address some of the challenges associated with using UASs and provide greater assistance to the firefighters and incident personnel in the wildland firefighting environment, the National Aeronautics and Space Administration (NASA) launched the Advanced Capabilities for Emergency Response Operations (ACERO) project. Building on previous NASA research, ACERO will explore the implementation of a traffic management system in the wildland fire environment to enhance safety and support situation awareness. ACERO draws on the UAS Traffic Management (UTM) system previously demonstrated in an urban environment. However, a traffic management system implemented in the wildland fire environment is expected to look and function much differently in order to meet the unique needs of this domain. At the outset of the ACERO project, interviews were conducted with five UASPs who operate UASs at wildland fire incidents. The interviews focused on exploring UASPs’ initial insights about the application of a traffic management system in wildland firefighting and understanding the unique needs of this environment. The UASPs discussed a range of topics including, the shape, size, and organization of UAS operations in the wildland fire environment, information needs for a user interface, such as traffic and map information, an alerting function when other traffic nears their operation area, and the importance of conformance monitoring. The UASPs also discussed their willingness to share operational information to support safety. In this paper, we describe the foundational work upon which ACERO will build and summarize the information and insights gathered during the UASP interviews, some of which have already informed the development of the ACERO work.

Uncrewed Aircraft System (UAS)↗

NASA NTRSDate not supplied

Incorporating UAS Traffic Management into Wildland Firefighting Operations: Initial Findings of Subject Matter Expert Interviews

Uncrewed Aircraft Systems (UASs) are being utilized throughout the disaster and emergency response domain, including in wildland firefighting operations. While UASs can offer safety benefits in comparison to crewed aircraft, such as removing the human pilot from the vehicle so that they are not exposed to the same risks and the ability to operate in low-visibility conditions, they are not without tradeoffs. For example, it can be challenging for UAS pilots (UASPs) to build situation awareness of the airspace in which their UAS is operating. In order to address some of the challenges associated with using UASs and provide greater assistance to the firefighters and incident personnel in the wildland firefighting environment, the National Aeronautics and Space Administration (NASA) launched the Advanced Capabilities for Emergency Response Operations (ACERO) project. Building on previous NASA research, ACERO will explore the implementation of a traffic management system in the wildland fire environment to enhance safety and support situation awareness. ACERO draws on the UAS Traffic Management (UTM) system previously demonstrated in an urban environment. However, a traffic management system implemented in the wildland fire environment is expected to look and function much differently in order to meet the unique needs of this domain. At the outset of the ACERO project, interviews were conducted with five UASPs who operate UASs at wildland fire incidents. The interviews focused on exploring UASPs’ initial insights about the application of a traffic management system in wildland firefighting and understanding the unique needs of this environment. The UASPs discussed a range of topics including, the shape, size, and organization of UAS operations in the wildland fire environment, information needs for a user interface, such as traffic and map information, an alerting function when other traffic nears their operation area, and the importance of conformance monitoring. The UASPs also discussed their willingness to share operational information to support safety. In this presentation, we describe the foundational work upon which ACERO will build and summarize the information and insights gathered during the UASP interviews, some of which have already informed the development of the ACERO work.

Uncrewed Aircraft Systems (UAS)↗

NASA NTRS2024

Terrestrial Proving Ground Capabilities Needed for Lunar In Situ Resource Utilization (ISRU) & Construction Concepts of Operation

Incorporating any new technology or system into a human exploration mission or architecture requires development well in advance of the mission to eliminate technology, cost, and schedule risk concerns. It is often stated that technologies need to be at a Technology Readiness Level (TRL) of 6, i.e. ‘system/subsystem model or prototype demonstration in a relevant environment (ground or space)’, by Authority To Proceed (ATP) or by the Preliminary Design Review (PDR) for the mission at the latest. There are two game changing capabilities for sustained human exploration of space that can have a significant effect on the overall exploration architecture and the technologies and systems included in the architecture. The first game changing capability, known as In Situ Resource Utilization (ISRU), involves the search for, acquisition, and processing of resources on the Moon and Mars into mission consumables and usable products, and the second is the ability to utilize space resources in the construction of roads, structures, and surface infrastructure. ISRU and surface construction capabilities have the potential to greatly reduce the cost and risk of human exploration while enabling sustained lunar surface and commercial operations. However, ISRU and surface construction systems are complex and must operate in extremely harsh environments, with abrasive regolith and pervasive dust, for long-periods of time, with potentially limited opportunities for maintenance and repair by humans. The complexity of these capabilities and operations also means that there are a limited number of companies that can design, build, and operate end-to-end systems on their own. The majority of the technologies being developed for these systems are by small companies and at the component or subsystem level. With the overarching strategy of the United States National Aeronautics and Space Administration (NASA) Space Technology Mission Directorate (STMD) to enable industry to implement ISRU and surface infrastructure for Artemis and space commercialization, it is therefore important to establish processes and capabilities to promote and foster collaborations among large and small companies involved in ISRU and surface infrastructure development. For ISRU and infrastructure systems and capabilities to be used in Artemis missions and future commercial lunar surface operations, a coordinated framework with virtual/physical integration and testing locations, or ‘Proving Grounds’, needs to be established and operated on a regular basis and open to all. This paper will discuss the ISRU and surface construction near and long-term concepts of operations, and review operations and lessons-learned from the previous ISRU analog field tests. From this information, requirements and capabilities will be proposed to support and enable the integration and testing of ISRU and construction systems with industry, academia, and international agencies, as well as what facilities and organizations could help establish these Proving Grounds.

ISRU↗

DOE OSTI2024

Fitness-for-Service Analysis of Reactor Components under Flexible Load-Following Operating Conditions

Conventional power-generation plants, including nuclear plants, have been traditionally designed to provide a steady baseload energy capacity, optimizing output efficiency while minimizing variable costs. However, the growing adoption of large-scale renewable energy-generation systems, which rely on intermittent sources such as solar and wind, has introduced more variability into the energy supply in interconnected electricity grids. As a result, the next generation of power plants needs to operate in what is known as the load-following mode, requiring flexible adjustments in electricity production to align with the energy demand on the grid. This transition from the steady baseload operation to load-following operating conditions can significantly increase the number of times various plant components are exposed to transient stresses. This increased thermo-mechanical cycling can lead to accelerated material degradation, thereby elevating the risk of premature failure of a component. It becomes imperative to conduct a comprehensive analysis of fatigue, creep-fatigue, and stress corrosion cracking life, to assess the resilience of the various engineering components under these flexible load-following operating conditions. This study aims to develop a comprehensive numerical model of a light-water reactor pressure vessel (RPV) to investigate its degradation under various operating scenarios. This coupled thermo-mechanical finite element analysis evaluated the stress response of the RPV caused by considering fluctuations in thermal and mechanical loads caused by the varying pressure and temperature occurring during the load-following operation. Critical locations on the RPV are subsequently identified based on the stress response. The stress intensity factors for the postulated flaws at those locations are then calculated, followed by an evaluation of the reactor's life in accordance with the ASME Boiler and Pressure Vessel Code Section XI. This comprehensive life assessment covers a number of transients expected during the flexible load-following operation, providing invaluable insights into the RPV's structural integrity. Moreover, the development methodology can be adapted to other reactor components, as well as components of conventional power stations that are affected by varying operating conditions.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

DOE OSTI2024

Estimation of General Area Dose Rates During Closure Weld Operations on the DOE Standard Canister Pacific Basin Nuclear Conference 2024

The Department of Energy (DOE) Spent Nuclear Fuel (SNF) Road Ready Demonstration Project is an effort to package DOE-managed SNF for road-ready dry storage. A key operation in this demonstration is performing the closure weld on the DOE Standard Canister after it has been loaded with the SNF. Planning the closure weld operations is ongoing and must consider what parts of the operations (if any) can be done manually and what parts must be done remotely. A key parameter to inform the evolving planning of these operations is the dose rate in the vicinity of the canister and the dose hazard posed to the closure weld operators and collocated workers. This study developed a Monte Carlo N-Particle (MCNP) model of the closure weld operation, which was used to estimate general area dose rates as well as dose rates to the welding location, weld operators, and collocated workers. These estimates provide some insight into the potential radiation exposure hazard for workers during the operations and are a factor to be considered in the ongoing development of designs, technology, processes, and administrative controls for packaging DOE-managed SNF for road-ready dry storage.

11 - NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

NASA NTRS2012

Improving operations: Metrics to Results

As a result of the mission failure of the Mars Climate Orbiter (MCO) spacecraft in 1999, the Jet Propulsion Laboratory (JPL) initiated the development of a Mission Operations Assurance (MOA) program to be implemented across all flight projects managed by JPL. One of the initiatives undertaken in 2001 was the collection of data on command file errors occurring in the operational phase of the mission. This paper defines command file errors and how and where they occur in the operations process. It also describes the problem reporting system (PRS) in use for mission operations at JPL. We examine the recent modifications to the PRS that enable the collection of metrics, specifically on command file errors. This paper discusses what the data show us since metrics have been collected for the operational missions conducted by JPL. We examine the evolution of an operational working group initiative to evaluate proximate, contributing, and root causes for the errors. As part of this discussion we see what the metrics have indicated over a decade. At the macro level, we can say that the aggregate command file error rate has been cut to roughly one third of the initial 2001 level by the end of 2011. Additionally, we explore efficient and innovative means to continually integrate the findings and recommendations from the working group back into the flight operations environment.

command file errors↗

NASA NTRS2017

Concept of Operations for RCO SPO

Reduced crew operations (RCO) refers to the reduction of crew members flying long-haul or military operations with more than one pilot onboard. Single pilot operations (SPO) refers to flying a commercial transport aircraft with only one pilot on board the aircraft, assisted by advanced onboard automation andor ground operators providing piloting support services. Properly implemented, RCO/SPO could provide operating cost savings while maintaining a level of safety no less than conventional two-pilot commercial operations. A concept of operations (ConOps) for any paradigm describes the characteristics of its various components and their integration in a multi-dimensional design space. This paper presents key options for humanautomation function allocation being considered by NASA in its ongoing development of RCO/SPO ConOps.

ConOps↗

DOE OSTI2025

Preliminary Evaluation of Joint Electricity-Hydrogen Concept of Operations

An initial thermal power dispatch (TPD) concept of operations was evaluated that couples a nuclear power plant to a nearby hydrogen production plant. GSE Systems’ generic pressurized water reactor full-scope simulator was modified with a TPD model comprised of a thermal power extraction and delivery system. A prototype human-system interface (HSI) was developed to interact with the TPD model and allow participants to execute the basic operating scenarios for normal operations. Four retired operators performed the evaluation, and due to COVID-19 travel restrictions, the original in-person experimental design was restructured to support a remote participator evaluation using a web meeting platform. Data from operator feedback, observations from the research team, and quantitative survey responses revealed that the initial TPD concept of operations is feasible. The operators were comfortable with the engineered system and HSI and could manage it without adverse impacts to reactor power, plant safety, or equipment. Findings are discussed in terms of both the TPD system design and HSI performance.

human factors↗