Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “key management”

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 91 records · Page 5

Cryogenic Propellant Storage and Transfer (CPST) Technology Maturation: Establishing a Foundation for a Technology Demonstration Mission (TDM)

As part of U.S. National Space Policy, NASA is seeking an innovative path for human space exploration, which strengthens the capability to extend human and robotic presence throughout the solar system. NASA is laying the groundwork to enable humans to safely reach multiple potential destinations, including asteroids, Lagrange points, the Moon and Mars. In support of this, NASA is embarking on the Technology Demonstration Mission Cryogenic Propellant Storage and Transfer (TDM CPST) Project to test and validate key cryogenic capabilities and technologies required for future exploration elements, opening up the architecture for large cryogenic propulsion stages (CPS) and propellant depots. The TDM CPST project will provide an on-orbit demonstration of the capability to store, transfer, and measure cryogenic propellants for a duration which is relevant to enable long term human space exploration missions beyond low Earth orbit (LEO). Recognizing that key cryogenic fluid management technologies anticipated for on-orbit (flight) demonstration needed to be matured to a readiness level appropriate for infusion into the design of the flight demonstration, the NASA Headquarters Space Technology Mission Directorate authorized funding for a one-year (FY12) ground based technology maturation program. The strategy, proposed by the CPST Project Manager, focused on maturation through modeling, studies, and ground tests of the storage and fluid transfer Cryogenic Fluid Management (CFM) technology sub-elements and components that were not already at a Technology Readiness Level (TRL) of 5. A technology maturation plan (TMP) was subsequently approved which described: the CFM technologies selected for maturation, the ground testing approach to be used, quantified success criteria of the technologies, hardware and data deliverables, and a deliverable to provide an assessment of the technology readiness after completion of the test, study or modeling activity. This paper will present the testing, studies, and modeling that occurred in FY12 to mature cryogenic fluid management technologies for propellant storage, transfer, and supply, to examine extensibility to full scale, long duration missions, and to develop and validate analytical models. Finally, the paper will briefly describe an upcoming test to demonstrate Liquid Oxygen (LO2) Zero Boil-Off (ZBO).

Doherty, Michael P.↗

Peat Archives in the Hudson Estuary - Marsh Formation, Carbon Storage and Release, and Resilience

We target deep peat stores (at least 8 meters) of carbon in the lower Hudson Estuary, which formed as the glacial fjord became an estuary with mid-Holocene sea level rise. These deep marshes play an extremely important role in the estuary health and stability in a changing climate. Never before have we faced the threats to coastal marshes that we are facing today, and the resulting sedimentation rates, inorganic/organic component histories, pollen, macrofossil, isotopic, and XRF data reveal critical information about past vegetation and climate change. Long-term shifts in organic/inorganic storage appear to be linked to drought, as watershed erosion results in more sand, silt and clay in the marshes. Climatic shifts often result in regional watershed shifts in vegetation, both locally and regionally. Understanding how these marshes are linked to human impact (disturbance, invasive species, higher nitrogen, heavy metal pollution, dams) over the last four centuries is critical to providing management of these key ecosystems, and their preservation as sea level rises. Quantification of processes that cause carbon degradation and release from these wetlands to the estuary is also key to this investigation. Peat loss would contribute to heavy metal pollution in the estuary as well as carbon loss. Young investigators from secondary schools in New York City participated in much of the fieldwork as part of the NASA/GISS NYC Research Initiative and the LDEO Secondary School Field Research Carbon Team.

Peteet, Dorothy M.↗

Traffic Aware Strategic Aircrew Requests

In 2016, a five-step roadmap was developed for the Traffic Aware Strategic Aircrew Requests (TASAR) project to achieve the full benefits of Airborne Trajectory Management (ABTM), a key enabler of the Digital Flight Vision. This presentation gives an overview of the TASAR roadmap for the ATD TIM in September 2021.

TASAR↗

Mass Economy Evaluation for Integrated ECLSS and Propulsion Architecture

As missions in Low Earth Orbit (LEO) lengthen and extend to deep space, minimizing resupply needs becomes vital for sustaining crewed operations. Traditional life support systems depend on consumables resupplied from Earth, a method that is increasingly impractical for missions beyond LEO, such as lunar outposts or Mars transit. Long-duration missions require more efficient, autonomous systems that can recycle essential resources, particularly water and oxygen, to minimize the frequency and mass of resupply missions. The Environmental Control and Life Support System (ECLSS) is essential to such missions, with the International Space Station (ISS) serving as a testbed for advanced water recovery and partial oxygen recycling via physico-chemical methods. Yet, ECLSS and propulsion subsystems generally operate independently, despite overlapping requirements and potential areas for synergy. For instance, ECLSS byproducts, water, CO₂, and hydrogen, could be repurposed for propulsion, potentially reducing dedicated propellant mass and increasing overall system efficiency. One promising approach is to develop shared-resource architectures that integrate ECLSS with propulsion systems. This study examines the potential of such integration through the Sabatier CO₂ reduction process, focusing on water management as a key factor in system mass trade-offs. The Sabatier reaction produces water and methane from metabolic CO₂ and electrolytic hydrogen, partially closing the life support loop and providing methane, which could serve as a propellant. This integration could minimize waste, reduce resupply requirements, and enhance mission mass efficiency. A dynamic modeling framework will be used to simulate resource flows over long missions, capturing interactions between life support and propulsion. By comparing integrated versus separate system configurations, the study aims to quantify mass benefits and penalties, informing future habitat designs and trade studies for missions prioritizing autonomy and mass efficiency.

ECLSS↗

Mass Economy Evaluation for Integrated ECLSS and Propulsion Architecture

As missions in low Earth orbit (LEO) lengthen and extend to deep space, minimizing resupply needs becomes vital for sustaining crewed operations. Traditional life support systems depend on consumables resupplied from Earth, a method that is increasingly impractical for missions beyond LEO, such as lunar outposts or Mars transit. Long-duration missions require more efficient, autonomous systems that can recycle essential resources, particularly water and oxygen, to minimize the frequency and mass of resupply missions. The Environmental Control and Life Support System (ECLSS) is essential to such missions, with the International Space Station (ISS) serving as a testbed for advanced water recovery and partial oxygen recycling via physico-chemical methods. Yet, ECLSS and propulsion subsystems generally operate independently, despite overlapping requirements and potential areas for synergy. For instance, ECLSS byproducts, water, CO 2 , and hydrogen, could be repurposed for propulsion, potentially reducing dedicated propellant mass and increasing overall system efficiency. One promising approach is to develop shared-resource architectures that integrate ECLSS with propulsion systems. This study examines the potential of such integration through the Sabatier CO₂ reduction process, focusing on water management as a key factor in system mass trade-offs. The Sabatier reaction produces water and methane from metabolic CO 2 and electrolytic hydrogen, partially closing the life support loop and providing methane, which could serve as a propellant. This integration could minimize waste, reduce resupply requirements, and enhance mission mass efficiency. A dynamic modeling framework will be used to simulate resource flows over long missions, capturing interactions between life support and propulsion. By comparing integrated versus separate system configurations, the study aims to quantify mass benefits and penalties, informing future habitat designs and trade studies for missions prioritizing autonomy and mass efficiency.

ECLSS↗

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Short Window Intra-Spacecraft RFID Localization

Logistics management has emerged as a key component to activities conducted in space. The RFID Enabled Autonomous Logistics Management (REALM) system has played a key role in providing cargo tracking capabilities in the noisy environment of the ISS. Currently, the inferencing engines used by REALM to predict the location of RFID tagged items operate on an hour of data. Movements aboard space stations occur on the scales of seconds. In this work we propose a new inferencing engine, that produces an embedding space that represents the location of RFID marked cargo on the scale of 30 seconds to 2 minutes of data, allowing for the categorization of movement of cargo, and predictions of a coarse location in less time than existing engines.

RFID↗

Implementing EVM Data Analysis Adding Value from a NASA Project Manager's Perspective

Data Analysis is one of the keys to an effective Earned Value Management (EVM) Process. Project Managers (PM) must continually evaluate data in assessing the health of their projects. Good analysis of data can assist PMs in making better decisions in managing projects. To better support our P Ms, National Aeronautics and Space Administration (NASA) - Marshall Space Flight Center (MSFC) recently renewed its emphasis on sound EVM data analysis practices and processes, During this presentation we will discuss the approach that MSFC followed in implementing better data analysis across its Center. We will address our approach to effectively equip and support our projects in applying a sound data analysis process. In addition, the PM for the Space Station Biological Research Project will share her experiences of how effective data analysis can benefit a PM in the decision making process. The PM will discuss how the emphasis on data analysis has helped create a solid method for assessing the project s performance. Using data analysis successfully can be an effective and efficient tool in today s environment with increasing workloads and downsizing workforces

Counts, Stacy↗

Pilot in Command: An Illustration of Autonomous Flight Management

Several years of NASA research have produced the concept for air traffic management called "Distributed Air/Ground Traffic Management," a major operational advancement that should significantly increase the capacity of the National Airspace System. A key component, "Autonomous Flight Management," introduces a new class of aircraft operations in which pilots are authorized to freely maneuver and execute optimal trajectories independent from air traffic controllers. These aircraft operators would benefit from significant increases in flexibility to optimize all flight operations and from avoiding most of the delays associated with ground-controlled operations. Responsibilities for aircraft separation and arrival flow conformance are transferred to the flight deck, and the pilots use computerized decision-support tools to accomplish these tasks. A research prototype of these tools called the "Autonomous Operations Planner" is being developed at the NASA Langley Research Center. This 14-minute video illustrates Autonomous Flight Management from the airline pilot's perspective.

Wing, David J.↗

Operations management system

The objective of an operations management system is to provide an orderly and efficient method to operate and maintain aerospace vehicles. Concepts are described for an operations management system and the key technologies are highlighted which will be required if this capability is brought to fruition. Without this automation and decision aiding capability, the growing complexity of avionics will result in an unmanageable workload for the operator, ultimately threatening mission success or survivability of the aircraft or space system. The key technologies include expert system application to operational tasks such as replanning, equipment diagnostics and checkout, global system management, and advanced man machine interfaces. The economical development of operations management systems, which are largely software, will require advancements in other technological areas such as software engineering and computer hardware.

Brandli, A. E.↗

EPOXI and Stardust NExT: The Management Challenges of Two Comet Flybys in Three Months

The EPOXI and Stardust NExT missions were missions of opportunity utilizing the Deep Impact and Stardust spacecraft, respectively. These new missions took advantage of the cost savings of utilizing spacecraft that were already flying for new science investigations. Both were retargeted to fly by an additional comet. EPOXI visited Hartley 2, significantly smaller than the other Jupiter family comets visited previously. Stardust NExT flew by Tempel 1, providing a second look at the comet previously studied by Deep Impact in 2005. Both projects were part of NASA's Discovery Program. In order to further save costs, the projects were combined into a single project office at JPL. This provided some efficiencies due to the similarity of the missions, but having the flybys space only three months apart posed challenges for the project management team to ensure each project was ready for its critical event and ensuring each received the proper support from the management team. The project office relied on an integrated calendar for tracking and scheduling meetings, reviews, and other key events. The project management team also coordinated their availability for both projects to maintain involvement with each team to ensure effective risk identification and management.

NExT (New Exploration of Tempel 1)↗

Introduction to UTM Services & Communication

This presentation provides an overview of NASA's UAS traffic management (UTM) system, defines key concepts, and gives a brief recap of the research done thus far. The UTM system is comprised of four key concepts: UAS Service Suppler (USS), USS Network, UAS Supplemental Data Service Suppliers (SDSP), and the Flight Information Management System (FIMS). Walking through an example UTM operation illustrates the basic contribution of and relationship between each of these components. While this is what a future operation could look like, today we have only started down the road. NASA, and particularly NASA Ames, has spent the last four years on UTM research, of which helped inform both regulation and industry.

Claudatos, Lauren↗

Managing the Moon Program: Lessons Learned from Project Apollo

There have been many detailed historical studies of the process of deciding on and executing the Apollo lunar landing during the 1960s and early 1970s. From the announcement of President John F Kennedy on May 25, 1961, of his decision to land an American on the Moon by the end of the decade, through the first lunar landing on July 20, 1969, on to the last of six successful Moon landings with Apollo 17 in December 1972, NASA carried out Project Apollo with enthusiasm and aplomb. While there have been many studies recounting the history of Apollo, at the time of the 30th anniversary of the first lunar landing by Apollo 11, it seems appropriate to revisit the process of large-scale technological management as it related to the lunar mission. Consequently, the NASA History Office has chosen to publish this monograph containing the recollections of key partcipants in the management process. The collective oral history presented here was recorded in 1989 at the Johnson Space Center's Gilruth Recreation Center in Houston, Texas. It includes the recollections of key participants in Apollo's administration, addressing issues such as communication between field centers, the prioritization of technological goals, and the delegation of responsibility. The following people participated: George E. Muller, Owen W. Morris, Maxime A. Faget, Robert R. Gilruth, Christopher C. Kraft, and Howard W. (Bill) Tindall. The valuable perspectives of these individuals deepen and expand our understanding of this important historical event. This is the 14th in a series of special studies prepared by the NASA History Office. The Monographs in Aerospace History series is designed to provide a wide variety of investigations relative to the history of aeronautics and space. These publications are intended to be tightly focused in terms of subject, relatively short in length, and reproduced in an inexpensive format to allow timely and broad dissemination to researchers in aerospace history.

Source record↗

Autonomous power expert fault diagnostic system for Space Station Freedom electrical power system testbed

The goal of the Autonomous Power System (APS) program is to develop and apply intelligent problem solving and control to the Space Station Freedom Electrical Power System (SSF/EPS) testbed being developed and demonstrated at NASA Lewis Research Center. The objectives of the program are to establish artificial intelligence technology paths, to craft knowledge-based tools with advanced human-operator interfaces for power systems, and to interface and integrate knowledge-based systems with conventional controllers. The Autonomous Power EXpert (APEX) portion of the APS program will integrate a knowledge-based fault diagnostic system and a power resource planner-scheduler. Then APEX will interface on-line with the SSF/EPS testbed and its Power Management Controller (PMC). The key tasks include establishing knowledge bases for system diagnostics, fault detection and isolation analysis, on-line information accessing through PMC, enhanced data management, and multiple-level, object-oriented operator displays. The first prototype of the diagnostic expert system for fault detection and isolation has been developed. The knowledge bases and the rule-based model that were developed for the Power Distribution Control Unit subsystem of the SSF/EPS testbed are described. A corresponding troubleshooting technique is also described.

Truong, Long V.↗

Effective Materials Property Information Management for the 21st Century

This paper discusses key principles for the development of materials property information management software systems. There are growing needs for automated materials information management in various organizations. In part these are fueled by the demands for higher efficiency in material testing, product design and engineering analysis. But equally important, organizations are being driven by the need for consistency, quality and traceability of data, as well as control of access to sensitive information such as proprietary data. Further, the use of increasingly sophisticated nonlinear, anisotropic and multi-scale engineering analyses requires both processing of large volumes of test data for development of constitutive models and complex materials data input for Computer-Aided Engineering (CAE) software. And finally, the globalization of economy often generates great needs for sharing a single "gold source" of materials information between members of global engineering teams in extended supply chains. Fortunately, material property management systems have kept pace with the growing user demands and evolved to versatile data management systems that can be customized to specific user needs. The more sophisticated of these provide facilities for: (i) data management functions such as access, version, and quality controls; (ii) a wide range of data import, export and analysis capabilities; (iii) data "pedigree" traceability mechanisms; (iv) data searching, reporting and viewing tools; and (v) access to the information via a wide range of interfaces. In this paper the important requirements for advanced material data management systems, future challenges and opportunities such as automated error checking, data quality characterization, identification of gaps in datasets, as well as functionalities and business models to fuel database growth and maintenance are discussed.

Ren, Weiju↗

Framework for Processing Citizens Science Data for Applications to NASA Earth Science Missions

Citizen science (or crowdsourcing) has drawn much high-level recent and ongoing interest and support. It is poised to be applied, beyond the by-now fairly familiar use of, e.g., Twitter for natural hazards monitoring, to science research, such as augmenting the validation of NASA earth science mission data. This interest and support is seen in the 2014 National Plan for Civil Earth Observations, the 2015 White House forum on citizen science and crowdsourcing, the ongoing Senate Bill 2013 (Crowdsourcing and Citizen Science Act of 2015), the recent (August 2016) Open Geospatial Consortium (OGC) call for public participation in its newly-established Citizen Science Domain Working Group, and NASA's initiation of a new Citizen Science for Earth Systems Program (along with its first citizen science-focused solicitation for proposals). Over the past several years, we have been exploring the feasibility of extracting from the Twitter data stream useful information for application to NASA precipitation research, with both "passive" and "active" participation by the twitterers. The Twitter database, which recently passed its tenth anniversary, is potentially a rich source of real-time and historical global information for science applications. The time-varying set of "precipitation" tweets can be thought of as an organic network of rain gauges, potentially providing a widespread view of precipitation occurrence. The validation of satellite precipitation estimates is challenging, because many regions lack data or access to data, especially outside of the U.S. and in remote and developing areas. Mining the Twitter stream could augment these validation programs and, potentially, help tune existing algorithms. Our ongoing work, though exploratory, has resulted in key components for processing and managing tweets, including the capabilities to filter the Twitter stream in real time, to extract location information, to filter for exact phrases, and to plot tweet distributions. The key step is to process the "precipitation" tweets to be compatible with satellite-retrieved precipitation data. These key components for processing and managing "precipitation" tweets (and additional ones to be developed) are not limited to precipitation, nor are they limited to the Twitter social medium. Indeed, to maximize the value of our work for NASA earth science programs, these components should be generalized and be part of an overall framework for processing citizen science data for science research. In this paper, we outline such a framework.

earth science satellite data↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗