SEARCH · Search NASA
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.
This paper demonstrates the use of Neural Networks as a device modeling tool to increase the reliability analysis accuracy of circuits targeted for space applications. The paper tackles a number of case studies of relevance to the design of Flight hardware. The results show that the proposed technique generates more accurate models than the ones regularly used to model circuits.
No abstract available
In FY01 we learned that hardware reliability models need substantial changes to account for differences in software, thus making software reliability measurements more effective, accurate, and easier to apply. These reliability models are generally based on familiar distributions or parametric methods. An obvious question is 'What new statistical and probability models can be developed using non-parametric and distribution-free methods instead of the traditional parametric method?" Two approaches to software reliability engineering appear somewhat promising. The first study, begin in FY01, is based in hardware reliability, a very well established science that has many aspects that can be applied to software. This research effort has investigated mathematical aspects of hardware reliability and has identified those applicable to software. Currently the research effort is applying and testing these approaches to software reliability measurement, These parametric models require much project data that may be difficult to apply and interpret. Projects at GSFC are often complex in both technology and schedules. Assessing and estimating reliability of the final system is extremely difficult when various subsystems are tested and completed long before others. Parametric and distribution free techniques may offer a new and accurate way of modeling failure time and other project data to provide earlier and more accurate estimates of system reliability.
The analysis followed five selected motors through initial design, development, test, qualification, manufacture, and final flight reports. An audit was conducted at the manufacturing plants to complement the literature search with firsthand observations of the current philosophies and practices that affect reliability of the motors. A second literature search emphasized acquisition of spacecraft and satellite data bearing on solid motor reliability. It was concluded that present practices at the plants yield highly reliable flight hardware. Reliability can be further improved by new developments of aft-end bonding and initiator/igniter nondestructive test methods, a safe/arm device, and an insulation formulation. Minimum diagnostic instrumentation is recommended for all motor flights. Surplus motors should be used in margin testing. Criteria should be established for pressure and zone curing. The motor contractor should be represented at launch. New design analyses should be made of stretched motors and spacecraft/motor pairs.
The system concept and requirements for an Advanced Information Processing System (AIPS) are briefly described, but the emphasis of this paper is on the evaluation methodologies being developed and utilized in the AIPS program. The evaluation tasks include hardware reliability, maintainability and availability, software reliability, performance, and performability. Hardware RMA and software reliability are addressed with Markov modeling techniques. The performance analysis for AIPS is based on queueing theory. Performability is a measure of merit which combines system reliability and performance measures. The probability laws of the performance measures are obtained from the Markov reliability models. Scalar functions of this law such as the mean and variance provide measures of merit in the AIPS performability evaluations.
Explore the source record for details and available documents.
The International Space Station (ISS) was originally designed to operate until 2015 with a plan for deorbiting the ISS in 2016. Currently, the international partnership has agreed to extend the operations until 2020 and discussions are underway to extend the life even further to 2028. Each partner is responsible for the sustaining engineering, sparing, and maintenance of their own segments. National Aeronautics and Space Administration's (NASA's) challenge is to purchase the needed number of spares to maintain the functional availability of the ISS systems necessary for the United States On-Orbit Segment s contribution. This presentation introduces an analytical approach to assessing uncertainty in ISS hardware necessary to extend the life of the vehicle. Some key areas for consideration are: establishing what confidence targets are required to ensure science can be continuously carried out on the ISS, defining what confidence targets are reasonable to ensure vehicle survivability, considering what is required to determine if the confidence targets are too high, and whether sufficient number of spares are purchased. The results of the analysis will provide a methodological basis for reassessing vehicle subsystem confidence targets. This analysis compares the probability of existing spares exceeding the total expected unit demand of the Orbital Replacement Unit (ORU) in functional hierarchies approximating the vehicle subsystems. In cases where the functional hierarchies' availability does not meet subsystem confidence targets, the analysis will further identify which ORUs may require additional spares to extend the life of the ISS. The resulting probability is dependent upon hardware reliability estimates. However, the ISS hardware fleet carries considerable epistemic uncertainty which must be factored into the development and execution of sparing risk postures. In addition, it is also recognized that uncertainty in the assessment is due to disconnects between modeled functions and actual subsystem operations. Perhaps most importantly, it is acknowledged that conservative confidence targets per subsystem are currently accepted. This presentation will also discuss how subsystem confidence targets may be relaxed based on calculating the level of uncertainty for each corresponding ORU-function. The presentation will conclude with the various strengths and limitations for implementing the analytical approach in sustaining the ISS through end of life; 2020 and beyond.
This paper introduces an analytical approach, Probability and Confidence Trade-space (PACT), which can be used to assess uncertainty in International Space Station (ISS) hardware sparing necessary to extend the life of the vehicle. There are several key areas under consideration in this research. We investigate what sparing confidence targets may be reasonable to ensure vehicle survivability and for completion of science on the ISS. The results of the analysis will provide a methodological basis for reassessing vehicle subsystem confidence targets. An ongoing annual analysis currently compares the probability of existing spares exceeding the total expected unit demand of the Orbital Replacement Unit (ORU) in functional hierarchies approximating the vehicle subsystems. In cases where the functional hierarchies availability does not meet subsystem confidence targets, the current sparing analysis further identifies which ORUs may require additional spares to extend the life of the ISS. The resulting probability is dependent upon hardware reliability estimates. However, the ISS hardware fleet carries considerable epistemic uncertainty (uncertainty in the knowledge of the true hardware failure rate), which does not currently factor into the annual sparing analysis. The existing confidence targets may be conservative. This paper will also discuss how confidence targets may be relaxed based on the inclusion of epistemic uncertainty for each ORU. The paper will conclude with strengths and limitations for implementing the analytical approach in sustaining the ISS through end of life, 2020 and beyond.
Performance test summary and hardware reliability for orbiting geophysical observatories
NASA's successful development of next generation space vehicles, habitats, and robotic systems will require reliable hardware and software systems. The aim of this initiative is to develop modeling methodology and tools to support Model-Based Systems Engineering (MBSE) for software assurance and reliability analysis. This effort expands the Unified Modeling Language (UML) software design models to include fault data for the extraction of Failure Modes and Effects Criticality Analysis (FMECA) and Fault Tree Analysis (FTA) for software. We explored different modeling approaches to integrate the UML software design models with the Systems Modeling Language (SysML) system models to generate an integrated model and reliability tools that take into account software and hardware interfaces.The benefits of this concept directly affect the safety community with quick turnarounds to produce software assurance and reliability analysis artifacts and the ability to visualize failure effects, both hardware and software. The result is enhanced system design integrity and early identification of system risks. This initiative will enable software assurance activities early in the system design lifecycle, facilitating the discovery of design weaknesses and enhancing the capability to produce safe, hazard-free systems
To show how NASA’s Moon-to-Mars (M2M) program can use hardware reliability assessments and comprehensive Probabilistic Risk Assessments (PRAs) to estimate risk of future missions and manage risk via safety and mission success requirements from the top down, so that this risk can be balanced with other program metrics like cost and schedule. These PRAs and reliability assessments can be used during the concept, design, and operational phases of development. This presentation also provides some thoughts on how the NASA process can be utilized for a lunar surface power grid development.
The National Aeronautics and Space Administration (NASA) is developing new launch systems and preparing to retire the Space Shuttle by 2010, as directed in the United States (U.S.) Vision for Space Exploration. The Ares I Crew Launch Vehicle (CLV) and the Ares V heavy-lift Cargo Launch Vehicle (CaLV) systems will build upon proven, reliable hardware derived from the Apollo-Saturn and Space Shuttle programs to deliver safe, reliable, affordable space transportation solutions. This approach leverages existing aerospace talent and a unique infrastructure, as well as legacy knowledge gained from nearly 50 years' experience developing space hardware. Early next decade, the Ares I will launch the new Orion Crew Exploration Vehicle (CEV) to the International Space Station (ISS) or to low-Earth orbit for trips to the Moon and, ultimately, Mars. Late next decade, the Ares V's Earth Departure Stage will carry larger payloads such as the lunar lander into orbit, and the Crew Exploration Vehicle will dock with it for missions to the Moon, where astronauts will explore new territories and conduct science and technology experiments. Both Ares I and Ares V are being designed to support longer future trips to Mars. The Exploration Launch Projects Office is designing, developing, testing, and evaluating both launch vehicle systems in partnership with other NASA Centers, Government agencies, and industry contractors. This paper provides top-level information regarding the genesis and evolution of the baseline configuration for the Ares V heavy-lift system. It also discusses riskbased, management strategies, such as building on powerful hardware and promoting common features between the Ares I and Ares V systems to reduce technical, schedule, and cost risks, as well as development and operations costs. Finally, it summarizes several notable accomplishments since October 2005, when the Exploration Launch Projects effort officially kicked off, and looks ahead at work planned for 2007 and beyond.
Despite their expense tape silos are still often the only affordable option for petabytescale science data archives, particularly when other factors such as data reliability, floor space, power and cooling load are accounted for. However, the complexity, management software, hardware reliability and access latency of tape silos make online data storage ever more attractive. Drastic reductions in low-cost mass-market PC disk drivers help to make this more affordable (approx. 1$/GB), but are challenging to scale to the petabyte range and of questionable reliability for archival use, On the other hand, if much of the science archive could be "virtualized", i.e., produced on demand when requested by users, we would need store only a fraction of the data online, perhaps bringing an online-only system into in affordable range. Radiance data from the satellite-borne Moderate Resolution Imaging Spectroradiometer (MODIS) instrument provides a good opportunity for such a virtual archive: the raw data amount to 140 GB/day, but these are small relative to the 550 GB/day making up the radiance products. These data are routinely processed as inputs for geophysical parameter products and then archived on tape at the Goddard Earth Sciences Distributed Active Archive (GES DAAC) for distributing to users. Virtualizing them would be an immediate and signifcant reduction in the amount of data being stored in the tape archives and provide more customizable products. A prototype of such a virtual archive is being developed to prove the concept and develop ways of incorporating the robustness that a science data archive requires.
Project Longshot, an exercise in the Advanced Design Program for Space, had as its destination Alpha Centauri, the closest star system to our own solar system. Alpha Centauri, a trinary star system, is 4.34 light years from earth. Although Project Longshot is impossible based on existing technologies, areas that require further investigation in order to make this feat possible are identified. Three areas where advances in technology are needed are propulsion, data processing for autonomous command and control functions, and reliability. Propulsion, possibly by antimatter annihilation; navigation and navigation aids; reliable hardware and instruments; artificial intelligence to eliminate the need for command telemetry; laser communication; and a reliable, compact, and lightweight power system that converts energy efficiently and reliably present major challenges. Project Longshot promises exciting advances in science and technology and new information concerning the universe.
A system reliability approach is discussed which is based on a quantitative assessment of both the engine system and hardware reliability during the design process. The approach makes it possible to evaluate design trades as the design matures. It is concluded that the system reliability assessment approach offers the following benefits. The uncertainty of each design variable is explicitly considered in the analysis process. The most significant design variables are ranked in order of their effect on reliability. Design trades can be assessed for reliability impact. It is concluded that the approach facilitates communication between disciplines and thus aids in concurrent engineering.
This study is a direct result of an on-going project to model the reliability of a large real-time control avionics system. In previous modeling efforts with this system, hardware reliability models were applied in modeling the reliability behavior of this system. In an attempt to enhance the performance of the adapted reliability models, certain software attributes were introduced in these models to control for differences between programs and also sequential executions of the same program. As the basic nature of the software attributes that affect software reliability become better understood in the modeling process, this information begins to have important implications on the software development process. A significant problem arises when raw attribute measures are to be used in statistical models as predictors, for example, of measures of software quality. This is because many of the metrics are highly correlated. Consider the two attributes: lines of code, LOC, and number of program statements, Stmts. In this case, it is quite obvious that a program with a high value of LOC probably will also have a relatively high value of Stmts. In the case of low level languages, such as assembly language programs, there might be a one-to-one relationship between the statement count and the lines of code. When there is a complete absence of linear relationship among the metrics, they are said to be orthogonal or uncorrelated. Usually the lack of orthogonality is not serious enough to affect a statistical analysis. However, for the purposes of some statistical analysis such as multiple regression, the software metrics are so strongly interrelated that the regression results may be ambiguous and possibly even misleading. Typically, it is difficult to estimate the unique effects of individual software metrics in the regression equation. The estimated values of the coefficients are very sensitive to slight changes in the data and to the addition or deletion of variables in the regression equation. Since most of the existing metrics have common elements and are linear combinations of these common elements, it seems reasonable to investigate the structure of the underlying common factors or components that make up the raw metrics. The technique we have chosen to use to explore this structure is a procedure called principal components analysis. Principal components analysis is a decomposition technique that may be used to detect and analyze collinearity in software metrics. When confronted with a large number of metrics measuring a single construct, it may be desirable to represent the set by some smaller number of variables that convey all, or most, of the information in the original set. Principal components are linear transformations of a set of random variables that summarize the information contained in the variables. The transformations are chosen so that the first component accounts for the maximal amount of variation of the measures of any possible linear transform; the second component accounts for the maximal amount of residual variation; and so on. The principal components are constructed so that they represent transformed scores on dimensions that are orthogonal. Through the use of principal components analysis, it is possible to have a set of highly related software attributes mapped into a small number of uncorrelated attribute domains. This definitively solves the problem of multi-collinearity in subsequent regression analysis. There are many software metrics in the literature, but principal component analysis reveals that there are few distinct sources of variation, i.e. dimensions, in this set of metrics. It would appear perfectly reasonable to characterize the measurable attributes of a program with a simple function of a small number of orthogonal metrics each of which represents a distinct software attribute domain.
The National Aeronautics and Space Administration (NASA) is developing new launch systems in preparation for the retirement of the Space Shuttle by 2010, as directed in the United States (U.S.) Vision for Space Exploration. The Ares I Crew Launch Vehicle (CLV) and the Ares V heavy-lift Cargo Launch Vehicle (CaLV) systems will build upon proven, reliable hardware derived from the Apollo Saturn (1961 to 1975) and Space Shuttle (1972 to 2010) programs to deliver safe, reliable, affordable space transportation solutions. This approach leverages existing aerospace talent and a unique infrastructure, as well as the vast amount of legacy knowledge gained from almost a half-century of hard-won experience in the space enterprise. Beginning early next decade, the Ares I will launch the new Crew Exploration Vehicle (CEV) to the International Space Station (ISS) or to low-Earth orbit for trips to the Moon and, ultimately, Mars. Late next decade, the Ares V's Earth Departure Stage will carry larger payloads such as the lunar lander into orbit, and the Crew Exploration Vehicle will dock with it for missions to the Moon, where astronauts will explore new territories and conduct science and technology experiments. Both the Ares I and Ares V systems are being designed to support longer future trips to Mars. The Exploration Launch Projects Office, located at NASA's Marshall Space Flight Center, is designing, developing, testing, and evaluating both launch vehicle systems in partnership with other NASA Centers, Government agencies, and industry contractors. This paper provides top-level information regarding the genesis and evolution of the baseline configuration for the Ares V heavy-lift system. It also touches on risk-based management strategies, such as building on powerful hardware and promoting common features between the Ares I and Ares V systems to reduce technical, schedule, and cost risks, as well as development and operations costs. Finally, it gives a summary of several notable accomplishments over the past year, since the Exploration Launch Projects effort officially kicked off in October 2005, and looks ahead at work planned for 2007 and beyond.
Shuttle-Derived Launch Vehicle (SDLV) concepts have been developed by a collaborative team comprising the Johnson Space Center, Marshall Space Flight Center, Kennedy Space Center, ATK-Thiokol, Lockheed Martin Space Systems Company, The Boeing Company, and United Space Alliance. The purpose of this study was to provide timely information on a full spectrum of low-risk, cost-effective options for STS-Derived Launch Vehicle concepts to support the definition of crew and cargo launch requirements for the Space Exploration Vision. Since the SDLV options use high-reliability hardware, existing facilities, and proven processes, they can provide relatively low-risk capabilities to launch extremely large payloads to low Earth orbit. This capability to reliably lift very large, high-dollar-value payloads could reduce mission operational risks by minimizing the number of complex on-orbit operations compared to architectures based on multiple smaller launchers. The SDLV options also offer several logical spiral development paths for larger exploration payloads. All of these development paths make practical and cost-effective use of existing Space Shuttle Program (SSP) hardware, infrastructure, and launch and flight operations systems. By utilizing these existing assets, the SDLV project could support the safe and orderly transition of the current SSP through the planned end of life in 2010. The SDLV concept definition work during 2004 focused on three main configuration alternatives: a side-mount heavy lifter (approximately 77 MT payload), an in-line medium lifter (approximately 22 MT Crew Exploration Vehicle payload), and an in-line heavy lifter (greater than 100 MT payload). This paper provides an overview of the configuration, performance capabilities, reliability estimates, concept of operations, and development plans for each of the various SDLV alternatives. While development, production, and operations costs have been estimated for each of the SDLV configuration alternatives, these proprietary data have not been included in this paper.