Your Selections

SMCG41
Show Only

Collections

File Formats

Content Types

Dates

Sectors

Topics

Publishers

Committees

Committee Codes

 

Reliability Program Handbook

G-41 Reliability
  • Aerospace Standard
  • TAHB0009A
  • Current
Published 2019-05-03 by SAE International in United States

This Handbook provides “how to” guidance to industry and government for the reliability Activities and Methods contained in GEIASTD0009 for developing reliable products and systems, successfully demonstrating them during test and evaluation, and sustaining them throughout the system/product life cycle.

 

Reliability Program Handbook

G-41 Reliability
  • Aerospace Standard
  • TAHB0009
  • Historical
Published 2013-05-01 by SAE International in United States

This handbook provides "how to" guidance to industry and government for the reliability Activities and Methods contained in ANSI/GEIA-STD-0009 for developing reliable products and systems, successfully demonstrating them during test and evaluation, and sustaining them throughout the system/product life cycle.

 

Reliability Program Standard

G-41 Reliability
  • 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
 

Reliability Program Standard Implementation Guide

G-41 Reliability
  • 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
 

Reliability Program Standard for Systems Design, Development, and Manufacturing

G-41 Reliability
  • Aerospace Standard
  • GEIASTD0009
  • Current
Published 2008-08-01 by SAE International in United States
This standard requires the developers and customer/user’s working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations. The user’s requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user’s requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user’s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated. The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user’s documented reliability requirements and needs. The developer shall implement a set of engineering activities (included in this standard as normative activities and informative activities, refer to Section 3) so that the resulting system/product satisfies the customer’s documented requirements and needs. The multifunctional team shall verify during production that the developer has met the user’s reliability…
Datasets icon
Annotation icon