Search Results

In 1994 the SAE G-11 Reliability, Maintainability, Supportability, and Logistics (RMSL) Division chartered a software committee, G-11SW, to create several software standards and guidance documents across the RMSL spectrum, including a software supportability program standard. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has attempted to develop a standard that is consistent with a SAE G-11 system level supportability program standard and augmented by necessary software-specific support information. The G-11SW committee believes this document reflects the best current commercial practices, and meets the objectives of the United States Department of Defense Acquisition Reform initiative.

In 1994, the SAE G-11 Reliability, Maintainability, Supportability and Logistics (RMSL) Division chartered a software committee, G-11SW, to create several software standards and guidance documents across the RMSL spectrum, including a software reliability program standard. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has attempted to develop a standard that is consistent with a SAE G-11 system level reliability program standard and augmented by necessary software-specific support information. The G-11SW committee believes this document reflects the best current commercial practices, and meets the objectives of the United States Department of Defense Acquisition Reform initiative.

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.

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.

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.

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.

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

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

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. ANSI/GEIA-STD-0009 requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations using a systems engineering approach. The four Objectives of ANSI/GEIA-STD-0009 are listed below: Objective 1: Understand Customer/User Requirements and constraints. The team (developer, customer, and user), includes 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 are generated. Objective 2: Design and redesign for reliability.

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. GEIASTD0009 requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations using a systems engineering approach. The four Objectives of GEIASTD0009 are listed below: Objective 1: Understand customer/user requirements and constraints. The team (developer, customer, and user) includes 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 are generated. Objective 2: Design and redesign for reliability.

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.