Search NASA⌕ Search

SEARCH · Search NASA

Results for “Reliability analysis”

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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS1971

A guide to onboard checkout. Volume 5: Data management

The baseline data management subsystem for a space station is discussed. The subsystem consists of equipment necessary to transfer, store, and process data to and from users and subsystems. It acquires and conditions a wide variety of input data from experiments, vehicle subsystems sensors, uplinked ground communications, and astronaut-activated controls. Computer techniques for failure analysis, reliability, and maintenance checkout onboard the space station are considered.

Source record↗
NASA NTRS1971

The STAR /self-testing and repairing/ computer - An investigation of the theory and practice of fault-tolerant computer design.

This paper presents the results obtained in a continuing investigation of fault-tolerant computing which is being conducted at the Jet Propulsion Laboratory. Initial studies led to the decision to design and construct an experimental computer with dynamic (standby) redundancy, including replaceable subsystems and a program rollback provision to eliminate transient errors. This system, called the STAR computer, began operation in 1969. The following aspects of the STAR system are described: architecture, reliability analysis, software, automatic maintenance of peripheral systems, and adaptation to serve as the central computer of an outer-planet exploration spacecraft.

A Avizienis↗
NASA NTRS1972

Inflight maintenance - Design for the future.

Extensive studies in the field of in-flight maintenance are reviewed. The progress made in this technology, and the design considerations essential for meeting the constraints imposed by a manned space mission lasting several years are outlined. Concepts for the design and packaging of maintainable systems are described. The requirement of full redundancy, with capability to perform in-flight maintenance, to provide reliability in long-duration missions is demonstrated from a reliability analysis.

Descamp, V. A.↗
NASA NTRS1973

Tracking and data relay satellite system configuration and tradeoff study. Volume 1: Study summary

A study was conducted to determine the configuration and tradeoffs of a tracking and data relay satellite. The study emphasized the design of a three axis stabilized satellite and a telecommunications system optimized for support of low and medium data rate user spacecraft. Telecommunications support to low and high, or low medium, and high data rate users, considering launches with the Delta 2914, the Atlas/Centaur, and the space shuttle was also considered. The following subjects are presented: (1) launch and deployment profile, (2) spacecraft mechanical and structural design, (3) attitude stabilization and control subsystem, and (4) reliability analysis.

Hill, T. E.↗
NASA NTRS1972

Tracking and data relay satellite system configuration and tradeoff study. Volume 5: TDRS spacecraft design, part 1

A dual spin stabilized TDR spacecraft design is presented for low data rate (LDR) and medium data rate (MDR) user spacecraft telecommunication relay service. The relay satellite provides command and data return channels for unmanned users together with duplex voice and data communication channels for manned user spacecraft. TDRS/ground links are in the Ku band. Command links are provided at UHF for LDR users and S band for MDR users. Voice communication channels are provided at UHF/VHF for LDR users and at S band for MDR users. The spacecraft is designed for launch on the Delta 2914 with system deployment planned for 1978. This volume contains a description of the overall TDR spacecraft configuration, a detailed description of the spacecraft subsystems, a reliability analysis, and a product effectiveness plan.

Source record↗
NASA NTRS1975

Low cost computer subsystem for the Solar Electric Propulsion Stage (SEPS)

The Solar Electric Propulsion Stage (SEPS) subsystem which consists of the computer, custom input/output (I/O) unit, and tape recorder for mass storage of telemetry data was studied. Computer software and interface requirements were developed along with computer and I/O unit design parameters. Redundancy implementation was emphasized. Reliability analysis was performed for the complete command computer sybsystem. A SEPS fault tolerant memory breadboard was constructed and its operation demonstrated.

Source record↗
NASA NTRS1975

Decision theory in structural reliability

Some fundamentals of reliability analysis as applicable to aerospace structures are reviewed, and the concept of a test option is introduced. A decision methodology, based on statistical decision theory, is developed for determining the most cost-effective design factor and method of testing for a given structural assembly. The method is applied to several Saturn V and Space Shuttle structural assemblies as examples. It is observed that the cost and weight features of the design have a significant effect on the optimum decision.

Thomas, J. M.↗
NASA NTRS1976

Airborne Advanced Reconfigurable Computer System (ARCS)

A digital computer subsystem fault-tolerant concept was defined, and the potential benefits and costs of such a subsystem were assessed when used as the central element of a new transport's flight control system. The derived advanced reconfigurable computer system (ARCS) is a triple-redundant computer subsystem that automatically reconfigures, under multiple fault conditions, from triplex to duplex to simplex operation, with redundancy recovery if the fault condition is transient. The study included criteria development covering factors at the aircraft's operation level that would influence the design of a fault-tolerant system for commercial airline use. A new reliability analysis tool was developed for evaluating redundant, fault-tolerant system availability and survivability; and a stringent digital system software design methodology was used to achieve design/implementation visibility.

Bjurman, B. E.↗
NASA NTRS1976

Joint aircraft loading/structure response statistics of time to service crack initiation

A reliability analysis for predicting the statistical distribution of time to fatigue crack initiation for aircraft structures in service is presented. The present analysis utilizes the statistical data of the specimen fatigue tests, the full-scale structure tests, and the statistical dispersion of aircraft service loads. The statistical distribution of the time to fatigue crack initiation of the full-scale structure under laboratory loading spectrum is assumed to be Weibull. The service loads for gust turbulences are modeled as Poisson processes for transport-type aircraft, while the maneuver loads are modeled as compound Poisson processes for fighter and training aircraft. It is found that the statistical distribution of time to fatigue crack initiation for aircraft structures in service is not Weibull and that the prediction on the basis of the Weibull distribution is unconservative, in particular in the early service time.

Yang, J.-N.↗
NASA NTRS1977

Life-test methodology for mechanical components

System is based on examining and testing each part of item under evaluation to determine whether aging processes, wear, or other inherent failure modes are likely to limit life to less than that required. Procedure may be applied to many long-life devices where statistical reliability analysis would be impractical.

Dufrane, K. F.↗
NASA NTRS1978

Numerical aerodynamic simulation facility. Preliminary study extension. Executive summary

An optimized functional design of key elements of the Numerical Aerodynamic Simulation Facility was investigated. The following tasks were performed and are discussed: (1) develop, optimize, and describe the functional description of the custom hardware; (2) delineate trade-off areas between performance, reliability, availability, serviceability, and programmability; (3) develop metrics and models for validation of the candidate system's performance; (4) conduct a functional simulation of the system design; (5) perform a reliability analysis of the system design; and (6) develop the software specifications to include a user level high level programming language, a correspondence between the programming language and instruction set, and outline the operating system requirements.

Source record↗