Search NASA⌕ Search

SEARCH · Search NASA

Results for “Project Lifecycles”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

Feasibility and Compatibility of Alternative Fuels in the U.S. Rail Sector: Technoeconomic, Lifecycle, and Supply Chain Analysis

The U.S. rail sector is a cornerstone of the United States’ freight transportation system, responsible for moving approximately 40% of long-distance freight ton-miles each year (AAR, 2025). Freight demand is projected to grow over time (BTS, 2017) thereby necessitating the investigation of alternative fuels that can sustain operational efficiency while reducing emissions and cost impacts. At the same time, it is important to explore alternative fuels as new sources of energy that can increase energy security and resilience for this sector. This report investigates the feasibility and compatibility of seven alternative fuels in the U.S. rail sector, focusing on biofuels and fuels from other renewable energy sources. The study evaluates alternative fuel pathways, considering their technical, economic, and environmental aspects to provide stakeholders with a comprehensive understanding of potential solutions.

09 BIOMASS FUELS↗
NASA NTRS2009

Tool for Human-Systems Integration Assessment: HSI Scorecard

This paper describes the development and rationale for a human-systems integration (HSI) scorecard that can be used in reviews of vehicle specification and design. This tool can be used to assess whether specific HSI related criteria have been met as part of a project milestone or critical event, such as technical reviews, crew station reviews, mockup evaluations, or even review of major plans or processes. Examples of HSI related criteria include Human Performance Capabilities, Health Management, Human System Interfaces, Anthropometry and Biomechanics, and Natural and Induced Environments. The tool is not intended to evaluate requirements compliance and verification, but to review how well the human related systems have been considered for the specific event and to identify gaps and vulnerabilities from an HSI perspective. The scorecard offers common basis, and criteria for discussions among system managers, evaluators, and design engineers. Furthermore, the scorecard items highlight the main areas of system development that need to be followed during system lifecycle. The ratings provide a repeatable quantitative measure to what has been often seen as only subjective commentary. Thus, the scorecard is anticipated to be a useful HSI tool to communicate review results to the institutional and the project office management.

Whitmore, Nihriban↗
NASA NTRS2012

Integrated Atmosphere Resource Recovery and Environmental Monitoring Technology Demonstration for Deep Space Exploration

Exploring the frontiers of deep space continues to be defined by the technological challenges presented by safely transporting a crew to and from destinations of scientific interest. Living and working on that frontier requires highly reliable and efficient life support systems that employ robust, proven process technologies. The International Space Station (ISS), including its environmental control and life support (ECLS) system, is the platform from which humanity's deep space exploration missions begin. The ISS ECLS system Atmosphere Revitalization (AR) subsystem and environmental monitoring (EM) technical architecture aboard the ISS is evaluated as the starting basis for a developmental effort being conducted by the National Aeronautics and Space Administration (NASA) via the Advanced Exploration Systems (AES) Atmosphere Resource Recovery and Environmental Monitoring (ARREM) Project.. An evolutionary approach is employed by the ARREM project to address the strengths and weaknesses of the ISS AR subsystem and EM equipment, core technologies, and operational approaches to reduce developmental risk, improve functional reliability, and lower lifecycle costs of an ISS-derived subsystem architecture suitable for use for crewed deep space exploration missions. The most promising technical approaches to an ISS-derived subsystem design architecture that incorporates promising core process technology upgrades will be matured through a series of integrated tests and architectural trade studies encompassing expected exploration mission requirements and constraints.

Perry, Jay L.↗
DOE OSTI2024

Application of quantitative risk assessment to address stakeholder questions in geologic carbon storage

Ambitious international greenhouse gas emissions reduction targets demand a rapid transformation to a low-carbon economy. This transformation includes the accelerated adoption of carbon dioxide (CO2) capture and storage (CCS) technology. However, as with any large-scale engineering enterprise, the widespread commercial-scale deployment of geologic carbon storage (GCS) raises important questions about technology and cost-effectiveness, safety, environmental risk, and long-term liability. Effectively assessing and managing risks and liability associated with GCS projects is a key technical need throughout the project life cycle-from site selection and permitting to monitoring design, operational risk management, and post-operational site closure. This presentation highlights recent advancements in tools for quantitative risk assessment, being developed by the National Risk Assessment Partnership (NRAP). NRAP is a multi-year, multinational laboratory research collaboration sponsored by the U.S. Department of Energy's Office of Fossil Energy and Carbon Management. Our focus will be on these tools' applications in addressing critical stakeholder questions related to supporting permitting to ensure secure and environmentally protective storage; designing effective and efficient monitoring plans; evaluating the effectiveness of remedial actions and risk management alternatives; and informing liability assessment and investment decisions. This paper will detail the key functionality of NRAP’s Open-Source Integrated Assessment Model (NRAP-Open-IAM), a computational framework for assessing leakage risk and containment assurance. This model features streamlined workflows for calculating leakage risk profiles, delineating risk-based area of review, and assessing contingency plans and post-injection site care requirements. ORION is an open-source, observation-based ensemble forecasting toolkit to help operators assess the seismic hazard at a carbon storage site. The State of Stress Analysis Tool (SOSAT), designed to assess subsurface stress conditions and evaluate geomechanical risk resulting from CO2 injection in an area of interest will also be presented. We will also introduce a prototype model to evaluate storage project costs and liability associated with risk management. The Technoeconomic and Liability Evaluation for Storage (TALES) model uses results from forecasts of leakage and induced seismicity risk to estimate the lifecycle cost of managing risk. Finally, a preliminary example of how the NRAP Risk-based Adaptive Monitoring Plan (RAMP) tool can be used to design efficient and effective site monitoring plans and estimate the detectability of fluid leakage will be provided. The relevance of these tools for addressing key stakeholder questions amidst uncertainty will be emphasized.

decision support↗
NASA NTRS1987

SAGA: A project to automate the management of software production systems

The Software Automation, Generation and Administration (SAGA) project is investigating the design and construction of practical software engineering environments for developing and maintaining aerospace systems and applications software. The research includes the practical organization of the software lifecycle, configuration management, software requirements specifications, executable specifications, design methodologies, programming, verification, validation and testing, version control, maintenance, the reuse of software, software libraries, documentation, and automated management.

Campbell, Roy H.↗
NASA NTRS2008

Applied Space Systems Engineering: Manage Technical Data - Chapter 17

Effective space systems engineering (SSE) is conducted in a fully electronic manner. Competitive hardware, software, and system designs are created in a totally digital environment that enables rapid product design and manufacturing cycles, as well as a multitude of techniques such as modeling, simulation, and lean manufacturing that significantly reduce the lifecycle cost of systems. Because the SSE lifecycle depends on the digital environment, managing the enormous volumes of technical data needed to describe, build, deploy, and operate systems is a critical factor in the success of a project. This chapter presents the key aspects of Technical Data Management (TDM) within the SSE process. It is written from the perspective of the System Engineer tasked with establishing the TDM process and infrastructure for a major project. Additional perspectives are reflected from the point of view of the engineers on the project who work within the digital engineering environment established by the TDM toolset and infrastructure, and from the point of view of the contactors who interface via the TDM infrastructure. Table 17.1 lists the TDM process as it relates to SSE.

Kent, Peter↗
NASA NTRS1980

Software cost/resource modeling: Deep space network software cost estimation model

A parametric software cost estimation model prepared for JPL deep space network (DSN) data systems implementation tasks is presented. The resource estimation model incorporates principles and data from a number of existing models, such as those of the General Research Corporation, Doty Associates, IBM (Walston-Felix), Rome Air Force Development Center, University of Maryland, and Rayleigh-Norden-Putnam. The model calibrates task magnitude and difficulty, development environment, and software technology effects through prompted responses to a set of approximately 50 questions. Parameters in the model are adjusted to fit JPL software lifecycle statistics. The estimation model output scales a standard DSN work breakdown structure skeleton, which is then input to a PERT/CPM system, producing a detailed schedule and resource budget for the project being planned.

Tausworthe, R. J.↗
NASA NTRS2001

Methodology Development for Assessment of Spaceport Technology Returns and Risks

As part of Kennedy Space Center's (KSC's) challenge to open the space frontier, new spaceport technologies must be developed, matured and successfully transitioned to operational systems. R&D investment decisions can be considered from multiple perspectives. Near mid and far term technology horizons must be understood. Because a multitude of technology investment opportunities are available, we must identify choices that promise the greatest likelihood of significant lifecycle At the same time, the costs and risks of any choice must be well understood and balanced against its potential returns The problem is not one of simply rank- ordering projects in terms of their desirability. KSC wants to determine a portfolio of projects that simultaneously satisfies multiple goals, such as getting the biggest bang for the buck, supporting projects that may be too risky for private funding, staying within annual budget cycles without foregoing the requirements of a long term technology vision, and ensuring the development of a diversity of technologies that, support the variety of operational functions involved in space transportation. This work aims to assist in the development of in methods and techniques that support strategic technology investment decisions and ease the process of determining an optimal portfolio of spaceport R&D investments. Available literature on risks and returns to R&D is reviewed and most useful pieces are brought to the attention of the Spaceport Technology Development Office (STDO). KSC's current project management procedures are reviewed. It is found that the "one size fits all" nature of KSC's existing procedures and project selection criteria is not conducive to prudent decision-making. Directions for improving KSC's - procedures and criteria are outlined. With help of a contractor, STDO is currently developing a tool, named Change Management Analysis Tool (CMAT)/ Portfolio Analysis Tool (PAT), to assist KSC's R&D portfolio determination. A critical review of CMAT/PAT is undertaken. Directions for the improvement of this tool are provided. STDO and KSC intend to follow up on many, if not all, of the recommendations provided.

Joglekar, Prafulla↗
NASA NTRS2009

Fully Employing Software Inspections Data

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

Shull, Forrest↗
NASA NTRS2013

Creating and Testing Simulation Software

The goal of this project is to learn about the software development process, specifically the process to test and fix components of the software. The paper will cover the techniques of testing code, and the benefits of using one style of testing over another. It will also discuss the overall software design and development lifecycle, and how code testing plays an integral role in it. Coding is notorious for always needing to be debugged due to coding errors or faulty program design. Writing tests either before or during program creation that cover all aspects of the code provide a relatively easy way to locate and fix errors, which will in turn decrease the necessity to fix a program after it is released for common use. The backdrop for this paper is the Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI), a project whose goal is to simulate a launch using simulated models of the ground systems and the connections between them and the control room. The simulations will be used for training and to ensure that all possible outcomes and complications are prepared for before the actual launch day. The code being tested is the Programmable Logic Controller Interface (PLCIF) code, the component responsible for transferring the information from the models to the model Programmable Logic Controllers (PLCs), basic computers that are used for very simple tasks.

Heinich, Christina M.↗
DOE OSTI2025

Studying Aerosol, Clouds, and Air Quality in the Coastal Urban Environment of Southeastern Texas

A multi-agency succession of field campaigns was conducted in southeastern Texas during July 2021 through October 2022 to study the complex interactions of aerosols, clouds and air pollution in the coastal urban environment. As part of the Tracking Aerosol Convection interactions Experiment (TRACER), the TRACER- Air Quality (TAQ) campaign the Experiment of Sea Breeze Convection, Aerosols, Precipitation and Environment (ESCAPE) and the Convective Cloud Urban Boundary Layer Experiment (CUBE), a combination of ground-based supersites and mobile laboratories, shipborne measurements and aircraft-based instrumentation were deployed. These diverse platforms collected high-resolution data to characterize the aerosol microphysics and chemistry, cloud and precipitation micro- and macro-physical properties, environmental thermodynamics and air quality-relevant constituents that are being used in follow-on analysis and modeling activities. We present the overall deployment setups, a summary of the campaign conditions and a sampling of early research results related to: (a) aerosol precursors in the urban environment, (b) influences of local meteorology on air pollution, (c) detailed observations of the sea breeze circulation, (d) retrieved supersaturation in convective updrafts, (e) characterizing the convective updraft lifecycle, (f) variability in lightning characteristics of convective storms and (g) urban influences on surface energy fluxes. The work concludes with discussion of future research activities highlighted by the TRACER model-intercomparison project to explore the representation of aerosol-convective interactions in high-resolution simulations.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1984

SAGA: A project to automate the management of software production systems

The project to automate the management of software production systems is described. The SAGA system is a software environment that is designed to support most of the software development activities that occur in a software lifecycle. The system can be configured to support specific software development applications using given programming languages, tools, and methodologies. Meta-tools are provided to ease configuration. Several major components of the SAGA system are completed to prototype form. The construction methods are described.

Campbell, R. H.↗
NASA NTRSDate not supplied

Designing the Design Process for Early Problem Discovery for a Complex Aeronautics Systems Challenge

The earliest stage in the innovation lifecycle, problem formulation, is crucial for setting direction in an innovation effort. When faced with an interesting problem, engineers commonly assume the approximate solution area and focus on ideating innovative solutions. However, in this project, NASA and their contracted partner, Accenture, collaboratively conducted problem discovery to ensure that solutioning efforts were focused on the right problems, for the right users, and addressing the most critical needs—in this case, exploring weather tolerant operations (WTO) to further urban air mobility (UAM) – known as UAM WTO. The project team leveraged generative, qualitative methods to understand the ecosystem, players, and where challenges in the industry are inhibiting development. The complexity of the problem area required that the team constantly observe and iterate on problem discovery, effectively “designing the design process.” This report discusses the approach, methodologies, and selected results, including insights on the application of early-stage design methodologies to a complex, system-level problem.

Problem formulation↗
NASA NTRS2022

Satellite Data Applications for Sustainable Energy Transitions

Transitioning to a sustainable energy system poses a massive challenge to communities, nations, and the global economy in the next decade and beyond. A growing portfolio of satellite data products is available to support this transition. Satellite data complement other information sources to provide a more complete picture of the global energy system, often with continuous spatial coverage over targeted areas or even the entire Earth. We find that satellite data are already being applied to a wide range of energy issues with varying information needs, from planning and operation of renewable energy projects, to tracking changing patterns in energy access and use, to monitoring environmental impacts and verifying the effectiveness of emissions reduction efforts. While satellite data could play a larger role throughout the policy and planning lifecycle, there are technical, social, and structural barriers to their increased use. We conclude with a discussion of opportunities for satellite data applications to energy and recommendations for research to maximize the value of satellite data for sustainable energy transitions.

energy↗
NASA NTRS2013

Model-based Systems Engineering: Creation and Implementation of Model Validation Rules for MOS 2.0

Model-based Systems Engineering (MBSE) is an emerging modeling application that is used to enhance the system development process. MBSE allows for the centralization of project and system information that would otherwise be stored in extraneous locations, yielding better communication, expedited document generation and increased knowledge capture. Based on MBSE concepts and the employment of the Systems Modeling Language (SysML), extremely large and complex systems can be modeled from conceptual design through all system lifecycles. The Operations Revitalization Initiative (OpsRev) seeks to leverage MBSE to modernize the aging Advanced Multi-Mission Operations Systems (AMMOS) into the Mission Operations System 2.0 (MOS 2.0). The MOS 2.0 will be delivered in a series of conceptual and design models and documents built using the modeling tool MagicDraw. To ensure model completeness and cohesiveness, it is imperative that the MOS 2.0 models adhere to the specifications, patterns and profiles of the Mission Service Architecture Framework, thus leading to the use of validation rules. This paper outlines the process by which validation rules are identified, designed, implemented and tested. Ultimately, these rules provide the ability to maintain model correctness and synchronization in a simple, quick and effective manner, thus allowing the continuation of project and system progress.

Model-based Systems Engineering (MBSE)↗
NASA NTRS2011

SOFIA Program SE and I Lessons Learned

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Ray, Ronald J.↗
NASA NTRS1990

Pragmatic quality metrics for evolutionary software development models

Due to the large number of product, project, and people parameters which impact large custom software development efforts, measurement of software product quality is a complex undertaking. Furthermore, the absolute perspective from which quality is measured (customer satisfaction) is intangible. While we probably can't say what the absolute quality of a software product is, we can determine the relative quality, the adequacy of this quality with respect to pragmatic considerations, and identify good and bad trends during development. While no two software engineers will ever agree on an optimum definition of software quality, they will agree that the most important perspective of software quality is its ease of change. We can call this flexibility, adaptability, or some other vague term, but the critical characteristic of software is that it is soft. The easier the product is to modify, the easier it is to achieve any other software quality perspective. This paper presents objective quality metrics derived from consistent lifecycle perspectives of rework which, when used in concert with an evolutionary development approach, can provide useful insight to produce better quality per unit cost/schedule or to achieve adequate quality more efficiently. The usefulness of these metrics is evaluated by applying them to a large, real world, Ada project.

Royce, Walker↗