Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Process design and operation”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

The Spacecraft Mass Balance as a Diagnostic Tool for Cabin Air Quality

The spacecraft-level mass balance is a powerful tool for diagnosing and decoupling factors influencing cabin air quality, especially with respect to trace contaminant propagation. Successful implementation of this approach relies upon accurate and temporally relevant air quality measurements, which are often challenging to attain for emerging trace contaminants. In addition to the proper interpretation of air quality data trends, a thorough understanding of subsystem-level mass transfer is required to characterize process performance. For many Environmental Control and Life Support System processes, subsystem mass transfer may be predicted based on physicochemical properties and classic unit operation design approaches. Gaps in understanding of process performance should be supplemented with thorough ground testing. A high confidence in the fidelity of one of these two aspects, air quality data or process performance, may help offset uncertainties in the other. At minimum, thresholding assumptions and numerical methods can be imposed to constrain unknown parameters within the physical envelope of the situation at hand. Finally, the complexity of cabin-wide integrated mass balances may be reduced by implementing a phenomenological approach towards subsystem discretization.

Cabin Air-quality↗
NASA NTRS1994

A software architecture for automating operations processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Miller, Kevin J.↗
NASA NTRS2011

Asynchronous Message Service Reference Implementation

This software provides a library of middleware functions with a simple application programming interface, enabling implementation of distributed applications in conformance with the CCSDS AMS (Consultative Committee for Space Data Systems Asynchronous Message Service) specification. The AMS service, and its protocols, implement an architectural concept under which the modules of mission systems may be designed as if they were to operate in isolation, each one producing and consuming mission information without explicit awareness of which other modules are currently operating. Communication relationships among such modules are self-configuring; this tends to minimize complexity in the development and operations of modular data systems. A system built on this model is a society of generally autonomous, inter-operating modules that may fluctuate freely over time in response to changing mission objectives, modules functional upgrades, and recovery from individual module failure. The purpose of AMS, then, is to reduce mission cost and risk by providing standard, reusable infrastructure for the exchange of information among data system modules in a manner that is simple to use, highly automated, flexible, robust, scalable, and efficient. The implementation is designed to spawn multiple threads of AMS functionality under the control of an AMS application program. These threads enable all members of an AMS-based, distributed application to discover one another in real time, subscribe to messages on specific topics, and to publish messages on specific topics. The query/reply (client/server) communication model is also supported. Message exchange is optionally subject to encryption (to support confidentiality) and authorization. Fault tolerance measures in the discovery protocol minimize the likelihood of overall application failure due to any single operational error anywhere in the system. The multi-threaded design simplifies processing while enabling application nodes to operate at high speeds; linked lists protected by mutex semaphores and condition variables are used for efficient, inter-thread communication. Applications may use a variety of transport protocols underlying AMS itself, including TCP (Transmission Control Protocol), UDP (User Datagram Protocol), and message queues.

Burleigh, Scott C.↗
DOE OSTI2022

Removal of Bond Sodium from Full-Length Unirradiated Fermi-1 Blanket Elements and Assembly via Melt-Drain-Evaporate Process

Equipment was designed, fabricated, tested, and operated in an inert atmosphere radiological glovebox at Idaho National Laboratory to demonstrate the removal of bond sodium from full-length unirradiated Fermi-1 radial blanket elements and an entire radial blanket assembly using a Melt-Drain-Evaporate process. A series of three runs was performed with individual and multiple radial Fermi-1 blanket elements, and a fourth run was conducted with an entire Fermi-1 radial blanket assembly. After each run, the depleted uranium alloy slugs in every element slid out of its cladding, mechanically exhibiting the effectual absence of bond sodium. Quantitative and further qualitative analyses of the treated Fermi-1 material revealed the substantive, if not complete, absence of sodium metal in blanket element components. Indeed, entire columns of depleted uranium alloy slugs and associated cladding from select treated elements were separately contacted with water to react with residual sodium metal on the element surfaces, forming hydrogen gas. Samples of the resultant gas were analyzed to quantify the hydrogen concentration, which correlated to a residual sodium metal content for the treated element. Accordingly, no detectable sodium metal (<7 µg) was found on the surfaces of multiple depleted uranium alloy slugs after removal from its cladding. Detectable sodium metal, ranging from 14 to 30 µg, was found on the surfaces of one separated column of slugs and two separated full-length cladding segments. Each element originally contained ~25 g of bond sodium, resulting in quantitative sodium metal removal efficiencies of =99.9998%. The remaining separated uranium alloy slugs and cladding segments from the four runs were piece-wise immersed in alcohol while videorecording possible gas bubble formation as an additional qualitative analysis for residual sodium metal on treated surfaces, which identified the predominant absence of sodium reactivity on the balance of treated Fermi-1 blanket material. The results of this demonstration substantiate a path forward for treatment and disposal of 34 metric tons heavy metal of irradiated sodium-bonded Fermi-1 blanket material currently stored at Idaho National Laboratory.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS2006

Application of State Analysis and Goal-Based Operations to a MER Mission Scenario

State Analysis is a model-based systems engineering methodology employing a rigorous discovery process which articulates operations concepts and operability needs as an integrated part of system design. The process produces requirements on system and software design in the form of explicit models which describe the behavior of states and the relationships among them. By applying State Analysis to an actual MER flight mission scenario, this study addresses the specific real world challenges of complex space operations and explores technologies that can be brought to bear on future missions. The paper describes the tools currently used on a daily basis for MER operations planning and provides an in-depth description of the planning process, in the context of a Martian day's worth of rover engineering activities, resource modeling, flight rules, science observations, and more. It then describes how State Analysis allows for the specification of a corresponding goal-based sequence that accomplishes the same objectives, with several important additional benefits.

mission planning↗
NASA NTRS1994

Concurrent engineering: Spacecraft and mission operations system design

Despite our awareness of the mission design process, spacecraft historically have been designed and developed by one team and then turned over as a system to the Mission Operations organization to operate on-orbit. By applying concurrent engineering techniques and envisioning operability as an essential characteristic of spacecraft design, tradeoffs can be made in the overall mission design to minimize mission lifetime cost. Lessons learned from previous spacecraft missions will be described, as well as the implementation of concurrent mission operations and spacecraft engineering for the Near Earth Asteroid Rendezvous (NEAR) program.

Landshof, J. A.↗
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 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 real-world 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.

Cassini↗
NASA NTRS2005

Development of the Architectural Simulation Model for Future Launch Systems and its Application to an Existing Launch Fleet

A significant portion of lifecycle costs for launch vehicles are generated during the operations phase. Research indicates that operations costs can account for a large percentage of the total life-cycle costs of reusable space transportation systems. These costs are largely determined by decisions made early during conceptual design. Therefore, operational considerations are an important part of vehicle design and concept analysis process that needs to be modeled and studied early in the design phase. However, this is a difficult and challenging task due to uncertainties of operations definitions, the dynamic and combinatorial nature of the processes, and lack of analytical models and the scarcity of historical data during the conceptual design phase. Ultimately, NASA would like to know the best mix of launch vehicle concepts that would meet the missions launch dates at the minimum cost. To answer this question, we first need to develop a model to estimate the total cost, including the operational cost, to accomplish this set of missions. In this project, we have developed and implemented a discrete-event simulation model using ARENA (a simulation modeling environment) to determine this cost assessment. Discrete-event simulation is widely used in modeling complex systems, including transportation systems, due to its flexibility, and ability to capture the dynamics of the system. The simulation model accepts manifest inputs including the set of missions that need to be accomplished over a period of time, the clients (e.g., NASA or DoD) who wish to transport the payload to space, the payload weights, and their destinations (e.g., International Space Station, LEO, or GEO). A user of the simulation model can define an architecture of reusable or expendable launch vehicles to achieve these missions. Launch vehicles may belong to different families where each family may have it own set of resources, processing times, and cost factors. The goal is to capture the required resource levels of the major launch elements and their required facilities. The model s output can show whether or not a certain architecture of vehicles can meet the launch dates, and if not, how much the delay cost would be. It will also produce aggregate figures of missions cost based on element procurement cost, processing cost, cargo integration cost, delay cost, and mission support cost. One of the most useful features of this model is that it is stochastic where it accepts statistical distributions to represent the processing times mimicking the stochastic nature of real systems.

Rabadi, Ghaith↗
NASA NTRS1990

Vehicle processing operations database

The Vehicle Processing Operations Data base (VPOD) has been designed and constructed to enable the collection and preliminary analysis of data relative to the processing of planetary exploration vehicles in low Earth orbit. VPOD has the capability to hierarchically store the events, assemblies, and equipment data needed for performing vehicle processing analysis, to whatever level of detail available. This permits some analysis to be performed even during the very early phases of vehicle and mission design. As more data about the events, assemblies, or equipment become available, the analysis can then be refined using the increased level of detail. VPOD output is based on a mission defined by selecting from the VPOD Events data base the events that are required to perform the desired tasks. The outputs available include total crew time, crew skill requirements, equipment needed, assemblies worked per event, to any available level of detail. The VPOD design is structured to interface with an operations simulation capability which is currently in the requirements definition phase. The simulator will use information from the VPOD to perform operations analysis for missions being conducted in low Earth orbit. VPOD information, along with information from the science missions operations data base and a Space Station configuration data base, will be used by the simulator to provide a capability to study total system operations and resources requirements.

Ganoe, George G.↗
DOE OSTI2026

Pilot-Scale Modular Research Facility for Acidic Water Pollution Cleanup and Domestic Production of Critical Minerals for National Security

A recent study by Penn State researchers revealed that Pennsylvania AMD streams originate from abandoned mines, with coal refuse piles of the lower Kittanning coal seam containing the most valuable heavy rare earth elements. Penn State has developed a three-stage process to recover these critical minerals, tested it for proof of concept, and secured a patent. Funded by the US DOE, a modular pilot-scale research and development unit has been designed and built to process 1,000 gallons per day of AMD from a site managed by the Pennsylvania Department of Environmental Protection (PA DEP). The system will selectively recover iron, aluminum, rare earth elements, and cobalt-nickel-manganese concentrates from AMD, followed by a proprietary downstream purification process. These operations aim to produce concentrates of critical minerals while treating acid mine drainage to meet environmental standards and evaluate different feedstocks. This presentation will describe the design, operation, and innovations of the proposed process and pilot facility, emphasizing its role in promoting sustainable recovery of critical minerals from legacy waste streams.

Pisupati, Sarma V [Center for Critical Minerals, T↗
NASA NTRS2006

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, the pace of this process was never intended to be continued indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5-day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

mission operations↗
NASA NTRS2006

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, there was never an intention of maintaining the pace of this process indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5- day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

Mars exploration↗
DOE OSTI2023

Decision-Making Framework to Evaluate Opportunities for Recovery of Rare Earth Elements and Critical Minerals in Produced Water Networks

Oil and gas development activities require a significant amount of water. Given the environmental impacts associated with high consumption and subsequent disposal of this water, there is a need for strategies to support effective reuse of, treatment of, and/or resource recovery from this produced water. These streams can contain appreciable concentrations of rare earth elements (REE) and critical minerals (CM) (e.g., Lithium), which are critical for many important applications in electronics, technology, manufacturing, energy, and medicine [1]. Along with REE/CM present in produced water, other waste streams such as fly ash from coal-fired power plants and acid mine discharge present other potential sources for recovery of REE/CM [2-4]. And with increases in demand for REE/CM, the need for recovery from wastewater streams is becoming even more important. There is a need to develop effective decision-making tools to evaluate the economic and environmental potential for REE/CM recovery from produced water networks while supporting the needs of drilling and hydraulic fracturing activities. In this work, we present our progress in developing a decision-making framework to efficiently design and operate produced water networks for REE/CM recovery. Our approach considers REE/CM recovery from produced water streams alongside other potential wastewater sources. The models consider the location and capacity of storage and decentralized treatment processes as well as the design and operation of pipeline and transportation networks to connect different sources and effectively schedule inventories, reuse, and recovery opportunities. We focus on the evaluation of opportunities for REE/CM recovery with treatment constraints on composition and flow. We demonstrate this framework with an illustrative case study that features diverse production sites, storage facilities, transportation, and treatment sites. This proposed framework will be deployed in an open-source software package that is compatible with the PARETO framework to deliver analysis and decision-making tools that allow stakeholders to quantitatively evaluate potential opportunities for REE/CM recovery in produced water networks.

Pulsipher, Joshua↗
NASA NTRS1994

Recommended techniques for effective maintainability. A continuous improvement initiative of the NASA Reliability and Maintainability Steering Committee

This manual presents a series of recommended techniques that can increase overall operational effectiveness of both flight and ground based NASA systems. It provides a set of tools that minimizes risk associated with: (1) restoring failed functions (both ground and flight based); (2) conducting complex and highly visible maintenance operations; and (3) sustaining a technical capability to support the NASA mission using aging equipment or facilities. It considers (1) program management - key elements of an effective maintainability effort; (2) design and development - techniques that have benefited previous programs; (3) analysis and test - quantitative and qualitative analysis processes and testing techniques; and (4) operations and operational design techniques that address NASA field experience. This document is a valuable resource for continuous improvement ideas in executing the systems development process in accordance with the NASA 'better, faster, smaller, and cheaper' goal without compromising safety.

Source record↗
NASA NTRS1999

A Cognitive Game Theoretic Analysis of Conflict Alerts in Air Traffic Control

The current research was motivated by the recommendation made by a joint Government/Industry committee to introduce a new traffic control system, referred to as the Free Flight. This system is designed to use recent new technology to facilitate efficient and safe air transportation. We addressed one of the major difficulties that arise in the design of this and similar multi-agent systems: the adaptive (and slippery) nature of human agents. To facilitate a safe and efficient design of this multi-agent system, designers have to rely on assessments of the expected behavior of the different agents under various scenarios. Whereas the behavior of the computerized agents is predictable, the behavior of the human agents (including air traffic controllers and pilots) is not. Experimental and empirical observations suggest that human agents are likely to adjust their behavior to the design of the system. To see the difficulty that the adaptive nature of human agents creates assume that a good approximation of the way operators currently behave is available. Given this information an optimal design can be performed. The problem arises as the human operator will learn to adjust their behavior to the new system. Following this adjustment process the assumptions made by the designer concerning the operators behavior will no longer be accurate and the system might reach a suboptimal state. In extreme situations these potential suboptimal states might involve unnecessary risk. That is, the fact that operators learn in an adaptive fashion does not imply that the system will become safer as they gain experience. At least in the context of Safety dilemmas, experience can lead to a pareto deficient risk taking behavior.

Erev, Ido↗
NASA NTRS2001

Extensional Rheology Experiment Developed to Investigate the Rheology of Dilute Polymer Solutions in Microgravity

A fundamental characteristic of fluid is viscosity; that is, the fluid resists forces that cause it to flow. This characteristic, or parameter, is used by manufacturers and end-users to describe the physical properties of a specific material so that they know what to expect when a material, such as a polymer, is processed through an extruder, a film blower, or a fiber-spinning apparatus. Normally, researchers will report a shear viscosity that depends on the rate of an imposed shearing flow. Although this type of characterization is sufficient for some processes, simple shearing experiments do not provide a complete picture of what a processor may expect for all materials. Extensional stretching flows are common in many polymer-processing operations such as extrusion, blow molding, and fiber spinning. Therefore, knowledge of the complete rheological (ability to flow and be deformed) properties of the polymeric fluid being processed is required to accurately predict and account for the flow behavior. In addition, if numerical simulations are ever able to serve as a priori design tools for optimizing polymer processing operations such as those described above, an accurate knowledge of the extensional viscosity of a polymer system and its variation with temperature, concentration, molecular weight, and strain rate is critical.

Logsdon, Kirk A.↗