SEARCH · Search NASA

Results for “Life-cycle assessment”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Probabilistic/Fracture-Mechanics Model For Service Life

Computer program makes probabilistic estimates of lifetime of engine and components thereof. Developed to fill need for more accurate life-assessment technique that avoids errors in estimated lives and provides for statistical assessment of levels of risk created by engineering decisions in designing system. Implements mathematical model combining techniques of statistics, fatigue, fracture mechanics, nondestructive analysis, life-cycle cost analysis, and management of engine parts. Used to investigate effects of such engine-component life-controlling parameters as return-to-service intervals, stresses, capabilities for nondestructive evaluation, and qualities of materials.

Watkins, T., Jr.↗

NASA NTRS1985

Advanced vehicle systems assessment. Volume 3: Systems assessment

The systems analyses integrate the advanced component and vehicle characteristics into conceptual vehicles with identical performance (for a given application) and evaluates the vehicles in typical use patterns. Initial and life-cycle costs are estimated and compared to conventional reference vehicles with comparable technological advances, assuming the vehicles will be in competition in the early 1990s. Electric vans, commuter vehicles, and full-size vehicles, in addition to electric/heat-engine hybrid and fuel-cell powered vehicles, are addressed in terms of performance and economics. System and subsystem recommendations for vans and two-passenger commuter vehicles are based on the economic analyses in this volume.

Hardy, K.↗

NASA NTRS1997

Wake Vortex Systems Cost/Benefits Analysis

The goals of cost/benefit assessments are to provide quantitative and qualitative data to aid in the decision-making process. Benefits derived from increased throughput (or decreased delays) used to balance life-cycle costs. Packaging technologies together may provide greater gains (demonstrate higher return on investment).

Crisp, Vicki K.↗

NASA NTRS1997

The Package-Based Development Process in the Flight Dynamics Division

The Software Engineering Laboratory (SEL) has been operating for more than two decades in the Flight Dynamics Division (FDD) and has adapted to the constant movement of the software development environment. The SEL's Improvement Paradigm shows that process improvement is an iterative process. Understanding, Assessing and Packaging are the three steps that are followed in this cyclical paradigm. As the improvement process cycles back to the first step, after having packaged some experience, the level of understanding will be greater. In the past, products resulting from the packaging step have been large process documents, guidebooks, and training programs. As the technical world moves toward more modularized software, we have made a move toward more modularized software development process documentation, as such the products of the packaging step are becoming smaller and more frequent. In this manner, the QIP takes on a more spiral approach rather than a waterfall. This paper describes the state of the FDD in the area of software development processes, as revealed through the understanding and assessing activities conducted by the COTS study team. The insights presented include: (1) a characterization of a typical FDD Commercial Off the Shelf (COTS) intensive software development life-cycle process, (2) lessons learned through the COTS study interviews, and (3) a description of changes in the SEL due to the changing and accelerating nature of software development in the FDD.

Parra, Amalia↗

NASA NTRS1989

Dynamic systems-engineering process - The application of concurrent engineering

A system engineering methodology is described which enables users, particulary NASA and DOD, to accommodate changing needs; incorporate emerging technologies; identify, quantify, and manage system risks; manage evolving functional requirements; track the changing environment; and reduce system life-cycle costs. The approach is a concurrent, dynamic one which starts by constructing a performance model defining the required system functions and the interrelationships. A detailed probabilistic risk assessment of the system elements and their interrelationships is performed, and quantitative analysis of the reliability and maintainability of an engineering system allows its different technical and process failure modes to be identified and their probabilities to be computed. Decision makers can choose technical solutions that maximize an objective function and minimize the probability of failure under resource constraints.

Wiskerchen, Michael J.↗

NASA NTRS1992

C-130 Advanced Technology Center wing box conceptual design/cost study

A conceptual design was developed by Northrop/LTV for an advanced C-130 Center Wing Box (CWB) which could meet the severe mission requirements of the SOF C-130 aircraft. The goals for the advanced technology CWB relative to the current C-130H CWB were: (1) the same acquisition cost; (2) lower operating support costs; (3) equal or lower weight; (4) a 30,000 hour service life for the SOF mission; and (5) minimum impact on the current maintenance concept. Initially, the structural arrangement, weight, external and internal loads, fatigue spectrum, flutter envelope and design criteria for the SOF C-130 aircraft CWB were developed. An advanced materials assessment was then conducted to determine the suitability of advanced materials for a 1994 production availability and detailed trade studies were performed on candidate CWB conceptual designs. Finally, a life-cycle cost analysis was performed on the advanced CWB. The study results showed that a hybrid composite/metallic CWB could meet the severe SOF design requirements, reduce the CWB weight by 14 pct., and was cost effective relative to an all metal beefed up C-130H CWB.

Whitehead, R. S.↗

NASA NTRS1994

Experiences in improving the state of the practice in verification and validation of knowledge-based systems

Knowledge-based systems (KBS's) are in general use in a wide variety of domains, both commercial and government. As reliance on these types of systems grows, the need to assess their quality and validity reaches critical importance. As with any software, the reliability of a KBS can be directly attributed to the application of disciplined programming and testing practices throughout the development life-cycle. However, there are some essential differences between conventional software and KBSs, both in construction and use. The identification of these differences affect the verification and validation (V&V) process and the development of techniques to handle them. The recognition of these differences is the basis of considerable on-going research in this field. For the past three years IBM (Federal Systems Company - Houston) and the Software Technology Branch (STB) of NASA/Johnson Space Center have been working to improve the 'state of the practice' in V&V of Knowledge-based systems. This work was motivated by the need to maintain NASA's ability to produce high quality software while taking advantage of new KBS technology. To date, the primary accomplishment has been the development and teaching of a four-day workshop on KBS V&V. With the hope of improving the impact of these workshops, we also worked directly with NASA KBS projects to employ concepts taught in the workshop. This paper describes two projects that were part of this effort. In addition to describing each project, this paper describes problems encountered and solutions proposed in each case, with particular emphasis on implications for transferring KBS V&V technology beyond the NASA domain.

Culbert, Chris↗

NASA NTRS1990

The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage.

Green, Scott↗

NASA NTRS2006

Framework for Defining and Assessing Benefits of a Modular Assembly Design Approach for Exploration Systems

A comprehensive modular assembly system model has been proposed that extends the art from modular hardware, to include in-space assembly, servicing and repair and it s critical components of infrastructure, agents and assembly operations. Benefits of modular assembly have been identified and a set of metrics defined that extends the art beyond the traditional measures of performance, with emphasis on criteria that allow life-cycle mission costs to be used as a figure of merit (and include all substantive terms that have an impact on the evaluation). The modular assembly approach was used as a basis for developing a Solar Electric Transfer Vehicle (SETV) concept and three modular assembly scenarios were developed. The modular assembly approach also allows the SETV to be entered into service much earlier than competing conventional configurations and results in a great deal of versatility in accommodating different launch vehicle payload capabilities, allowing for modules to be pre-assembled before launch or assembled on orbit, without changing the space vehicle design.

Dorsey, John T.↗

NASA NTRS1976

Technical and Economic Assessment of Span-Distributed Loading Cargo Aircraft Concepts

A 700,000 kg (1,540,000-lb) aircraft with a cruise Mach number of 0.75 was found to be optimum for the specified mission parameters of a 272 155-kg (600,000-lb) payload, a 5560-km (3000-n.mi.) range, and an annual productivity of 113 billion revenue-ton km (67 billion revenue-ton n. mi.). The optimum 1990 technology level spanloader aircraft exhibited the minimum 15-year life-cycle costs, direct operating costs, and fuel consumption of all candidate versions. Parametric variations of wing sweep angle, thickness ratio, rows of cargo, and cargo density were investigated. The optimum aircraft had two parallel rows of 2.44 x 2.44-m (8 x 8-ft) containerized cargo with a density of 160 kg/cu m (10 lb/ft 3) carried throughout the entire 101-m (331-ft) span of the constant chord, 22-percent thick, supercritical wing. Additional containers or outsized equipment were carried in the 24.4-m (80-ft) long fuselage compartment preceding the wing. Six 284,000-N (64,000-lb) thrust engines were mounted beneath the 0.7-rad (40-deg) swept wing. Flight control was provided by a 36.6-m (120-ft) span canard surface mounted atop the forward fuselage, by rudders on the wingtip verticals and by outboard wing flaperons.

Johnston, W. M.↗

NASA NTRS1992

Automation life-cycle cost model

The problem domain being addressed by this contractual effort can be summarized by the following list: Automation and Robotics (A&R) technologies appear to be viable alternatives to current, manual operations; Life-cycle cost models are typically judged with suspicion due to implicit assumptions and little associated documentation; and Uncertainty is a reality for increasingly complex problems and few models explicitly account for its affect on the solution space. The objectives for this effort range from the near-term (1-2 years) to far-term (3-5 years). In the near-term, the envisioned capabilities of the modeling tool are annotated. In addition, a framework is defined and developed in the Decision Modelling System (DEMOS) environment. Our approach is summarized as follows: Assess desirable capabilities (structure into near- and far-term); Identify useful existing models/data; Identify parameters for utility analysis; Define tool framework; Encode scenario thread for model validation; and Provide transition path for tool development. This report contains all relevant, technical progress made on this contractual effort.

Gathmann, Thomas P.↗

NASA NTRS1980

Advanced electric propulsion system concept for electric vehicles. Addendum 1: Voltage considerations

The two electric vehicle propulsion systems that best met cost and performance goals were examined to assess the effect of battery pack voltage on system performance and cost. A voltage range of 54 to 540 V was considered for a typical battery pack capacity of 24 k W-hr. The highest battery specific energy (W-hr/kg) and the lowest cost ($/kW-hr) were obtained at the minimum voltage level. The flywheel system traction motor is a dc, mechanically commutated with shunt field control, and due to the flywheel the traction motor and the battery are not subject to extreme peaks of power demand. The basic system uses a permanent-magnet motor with electronic commutation supplied by an ac power control unit. In both systems battery cost were the major factor in system voltage selection, and a battery pack with the minimum voltage of 54 V produced the lowest life-cycle cost. The minimum life-cycle cost for the basic system with lead-acid batteries was $0.057/km and for the flywheel system was $0.037/km.

Raynard, A. E.↗

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 NTRS1978

Solar thermal power systems point-focusing distributed receiver /PFDR/ technology - A project description

The goal of the Project is to support the industrial development of PFDR technology that will provide favorable life-cycle costs per unit of electrical or thermal energy produced. The technology will be made available in the early 1980s for applications project experiments. PFDR systems utilize concentrator dishes to furnish energy to their own individual receivers and power conversion subsystems. Initial effort is with steam Rankine and gas Brayton cycles. Periodic assessments will be made to confirm or change the cycles initially selected. Subsystems will be designed, fabricated and tested together in modules as appropriate. This paper describes PFDR systems briefly, outlines the project goals and organization, discusses the plans and current status of the project, and lists the benefits of PFDR technology concepts.

Lucas, J. W.↗

NASA NTRS1987

Technical and economic study of Stirling and Rankine cycle bottoming systems for heavy truck diesel engines

Bottoming cycle concepts for heavy duty transport engine applications were studied. In particular, the following tasks were performed: (1) conceptual design and cost data development for Stirling systems; (2) life-cycle cost evaluation of three bottoming systems - organic Rankine, steam Rankine, and Stirling cycles; and (3) assessment of future directions in waste heat utilization research. Variables considered for the second task were initial capital investments, fuel savings, depreciation tax benefits, salvage values, and service/maintenance costs. The study shows that none of the three bottoming systems studied are even marginally attractive. Manufacturing costs have to be reduced by at least 65%. As a new approach, an integrated Rankine/Diesel system was proposed. It utilizes one of the diesel cylinders as an expander and capitalizes on the in-cylinder heat energy. The concept eliminates the need for the power transmission device and a sophisticated control system, and reduces the size of the exhaust evaporator. Results of an economic evaluation indicate that the system has the potential to become an attractive package for end users.

Kubo, I.↗

NASA NTRS1997

Assessment and Management of the Risks of Debris Hits During Space Station EVAs

The risk of EVAs is critical to the decision of whether or not to automate a large part of the construction of the International Space Station (ISS). Furthermore, the choice of the technologies of the space suit and the life support system will determine (1) the immediate safety of these operations, and (2) the long-run costs and risks of human presence in space, not only in lower orbit (as is the case of the ISS) but also perhaps, outside these orbits, or on the surface of other planets. The problem is therefore both an immediate one and a long-term one. The fundamental question is how and when to shift from the existing EMU system (suit, helmet, gloves and life support system) to another type (e.g. a hard suit), given the potential trade-offs among life-cycle costs, risks to the astronauts, performance of tasks, and uncertainties about new systems' safety inherent to such a shift in technology. A more immediate issue is how to manage the risks of EVAs during the construction and operation of the ISS in order to make the astronauts (in the words of the NASA Administrator) "as safe outside as inside". For the moment (June 1997), the plan is to construct the Space Station using the low-pressure space suits that have been developed for the space shuttle. In the following, we will refer to this suit assembly as EMU (External Maneuvering Unit). It is the product of a long evolution, starting from the U.S. Air Force pilot suits through the various versions and changes that occurred for the purpose of NASA space exploration, in particular during the Gemini and the Apollo programs. The Shuttle EMU is composed of both soft fabrics and hard plates. As an alternative to the shuttle suit, at least two hard suits were developed by NASA: the AX5 and the MRKIII. The problem of producing hard suits for space exploration is very similar to that of producing deep-sea diving suits. There was thus an opportunity to develop a suit that could be manufactured for both purposes with the economies of scale that could be gained from a two-branch manufacturing line (space and deep sea). Of course, the space suit would need to be space qualified. Some of the problems in adopting one of the hard suits were first that the testing had to be completed, and second that it required additional storage space. The decision was made not to develop a hard suit in time for the construction and operation of the ISS. Instead, to improve the safety of the current suit, it was decided to reinforce the soft parts of the shuttle EMU with KEVLAR linings to strengthen it against debris impacts. Test results, however, show that this advanced suit design has little effect on the penetration characteristics.

Pate-Cornell, Elisabeth↗

NASA NTRS1995

A Validation of Object-Oriented Design Metrics

This paper presents the results of a study conducted at the University of Maryland in which we experimentally investigated the suite of Object-Oriented (00) design metrics introduced by [Chidamber and Kemerer, 1994]. In order to do this, we assessed these metrics as predictors of fault-prone classes. This study is complementary to [Lieand Henry, 1993] where the same suite of metrics had been used to assess frequencies of maintenance changes to classes. To perform our validation accurately, we collected data on the development of eight medium-sized information management systems based on identical requirements. All eight projects were developed using a sequential life cycle model, a well-known 00 analysis/design method and the C++ programming language. Based on experimental results, the advantages and drawbacks of these 00 metrics are discussed and suggestions for improvement are provided. Several of Chidamber and Kemerer's 00 metrics appear to be adequate to predict class fault-proneness during the early phases of the life-cycle. We also showed that they are, on our data set, better predictors than "traditional" code metrics, which can only be collected at a later phase of the software development processes.

Basili, Victor R.↗

NASA NTRS1997

A Validation of Object-Oriented Design Metrics as Quality Indicators

This paper presents the results of a study in which we empirically investigated the suits of object-oriented (00) design metrics introduced in another work. More specifically, our goal is to assess these metrics as predictors of fault-prone classes and, therefore, determine whether they can be used as early quality indicators. This study is complementary to the work described where the same suite of metrics had been used to assess frequencies of maintenance changes to classes. To perform our validation accurately, we collected data on the development of eight medium-sized information management systems based on identical requirements. All eight projects were developed using a sequential life cycle model, a well-known 00 analysis/design method and the C++ programming language. Based on empirical and quantitative analysis, the advantages and drawbacks of these 00 metrics are discussed. Several of Chidamber and Kamerer's 00 metrics appear to be useful to predict class fault-proneness during the early phases of the life-cycle. Also, on our data set, they are better predictors than 'traditional' code metrics, which can only be collected at a later phase of the software development processes.

Basili, Victor R.↗