Your Selections

TEAG11R
Show Only

Collections

File Formats

Content Types

Dates

Sectors

Topics

Publishers

Committees

Committee Codes

Recommended Failure Modes and Effects Analysis (FMEA) Practices for Non-Automobile Applications

G-11R, Reliability Committee
  • Aerospace Standard
  • ARP5580
  • Current
Published 2012-05-08 by SAE International in United States
Recommended Failure Modes and Effects Analysis (FMEA) Practices For Non-Automobile Applications describes the basic procedures for performing a Failure Modes and Effects Analysis (FMEA). It encompasses functional, interface, and detailed FMEA, as well as certain pre-analysis activities (FMEA planning and functional requirements analysis), post-analysis activities (failure latency analysis, FMEA verification, and documentation), and applications to hardware, software, and process design. It is intended for use by organizations whose product development processes use FMEA as a tool for assessing the safety and reliability of system elements, or as part of their product improvement processes. A separate, Surface Vehicle Recommended Practice, J1739, is intended for use in automobile applications.
Datasets icon
Annotation icon

Software Supportability - An Overview

G-11R, Reliability Committee
  • Aerospace Standard
  • AIR5121A
  • Current
Published 2012-05-08 by SAE International in United States
This SAE Aerospace Information Report (AIR) provides an overview of the issues relating to the support and supportability of software in computer-based systems. It has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The software support issues and activities summarized in this report are reasonably easy to comprehend. The reader should not be mislead into believing development of supportable software is easy to achieve. The target audience for the document includes software acquisition organizations, developers, supporters, and end-use customers.
Datasets icon
Annotation icon

Software Reliability Program Standard

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1002_201205
  • Current
Published 2012-05-07 by SAE International in United States
This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.
Annotation icon

Reliability Program Standard

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1000_201205
  • Current
Published 2012-05-07 by SAE International in United States
This SAE standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a The supplier shall ascertain customer requirements b The supplier shall meet customer requirements c The supplier shall assure that customer requirements have been met
Annotation icon

Software Supportability Program Implementation Guide

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1005_201205
  • Current
Published 2012-05-07 by SAE International in United States
This SAE Recommended Practice provides recommended guidelines and best practices for implementing a supportability program to ensure that software is supportable throughout its life cycle. This Implementation Guide is the companion to the Software Supportability Program Standard, SAE JA1004, that describes, within a Plan-Case framework, what software supportability performance requirements are necessary. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented via software. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software. Applicability of specific recommended practices will depend on the support-significance of the software, application domain, and life cycle stage of the software.
Datasets icon
Annotation icon

Software Reliability Program Implementation Guide

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1003_201205
  • Current
Published 2012-05-07 by SAE International in United States
This document provides methods and techniques for implementing a reliability program throughout the full life cycle of a software product, whether the product is considered as standalone or part of a system. This document is the companion to the Software Reliability Program Standard [JA1002]. The Standard describes the requirements of a software reliability program to define, meet, and demonstrate assurance of software product reliability using a Plan-Case framework and implemented within the context of a system application. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented by software components. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of software whose reliability is an important performance parameter. Applicability of specific practices will depend on the reliability-significance of the software, application domain, and life cycle stage of the software. Following guidelines in this document does not guarantee required reliability will be…
Datasets icon
Annotation icon

Software Supportability Program Standard

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1004_201205
  • Current
Published 2012-05-07 by SAE International in United States
This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs.
Annotation icon

Software Support Concept

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1006_201205
  • Current
Published 2012-05-07 by SAE International in United States
This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers. This document is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software.
Annotation icon

Reliability Program Standard Implementation Guide

G-11R, Reliability Committee
  • Aerospace Standard
  • JA1000/1_201205
  • Current
Published 2012-05-07 by SAE International in United States
The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance of their products. Unfortunately, some reliability methods have depended upon the availability of historical data, other experiential information, or learning through extensive and time consuming tests. The new…
Datasets icon
Annotation icon

RMS Terms and Definitions

G-11R, Reliability Committee
  • Aerospace Standard
  • ARP5638
  • Current
Published 2005-03-06 by SAE International in United States
The terms used in most engineering technologies tend to be physical characteristics such as speed, rate of turn, and fuel consumption. While they may require very careful definition and control of the way in which they are measured, the terms themselves are not subject to different interpretations. Reliability, Maintainability, and Supportability (RMS) however, use terms that are defined in a variety of ways with multiple interpretations. The variety of definitions given to a single term creates problems when trying to compare the performance of one system to another. To eliminate the confusion, a literature search that listed current and past RMS terms and definitions was conducted. The literature search included input from the US Military, UK Military, NATO, SAE, IEEE, NASA, ISO, University Research, and other publications. The object was to determine the common definition of Reliability Terms from a variety of sources. It is accepted that some of the definitions may be unique because of the nature of the mission, but it is the strong conviction of the Government and Industry practitioners who make…
Datasets icon
Annotation icon