Search Results

This AIR by the G-11AT (Automation and Tools) subcommittee, examines the failure mode, effects and criticality analysis (FMECA) requirements and procedures as performed on current and earlier vintage engineering programs. The subcommittee has focused on these procedures in relation to the concurrent engineering (CE) environment to determine where it may be beneficial, to both FMECA analysts and users, to automate some or all of the FMECA processes. Its purpose is to inform the reader about FMECAs and how the FMECA process could be automated in a concurrent engineering environment. There is no intent on the part of the authors that the material presented should become requirements or specifications imposed as part of any future contract. The report is structured to include the following subjects: a A FMECA overview b The current FMECA process c FMECA in the concurrent engineering environment d FMECA automation e The benefits of automation

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.

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.

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.

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.

Historically, the supportability aspects of software have been given a very low priority in the overall program requirements. This was particularly prevalent during the acquisition phase, where funding and timing constraints were usually the top priorities. The result was inadequate product supportability, inadequate support funding, lack of good field data, and no meaningful analysis and optimization of possible support alternatives. In order to alleviate these historical concerns, this document presents a top-level structured overview of an overall software support concept and the information associated with it. This document was developed by the Supportability Subcommittee of the Society of Automotive Engineers (SAE) G-11 Reliability, Maintainability, Supportability, and Logistics (RMSL) Software Committee (G-11SW).

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.

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 and implementation guidelines. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has developed a standard (JA1002) and these implementation guidelines (JA1003) that are consistent with a SAE G-11 system level reliability program standard (JA1000) and guidelines (JA1000-1), augmented by necessary software-specific information. The G-11SW committee believes these documents reflect the best current commercial practices, and meet the objectives of the United States Department of Defense Acquisition Reform initiative and the North Atlantic Treaty Organization (NATO) Reliability Program.

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 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 mathematically defined. As a result, there are more than 2000 terms defined in just the documents reviewed so far, many of which have multiple interpretations. This proliferation of definitions of the terms leads to problems when one attempts to compare the performance of one system to another. For example, the RMS performance of a transport aircraft from the commercial arena is measured using metrics that are not the same as those for a fighter or attack aircraft from a military service.

Provide a high level standard that resolves the gaps of SAE J1739 and other FMEA standards to support companies that currently use the cancelled MIL-Std-1629a FMECA Standard. The new standard will define: 1) the relationship and connection between FMEA/FMECA and maintainability and Supportability. 2) define the purpose of qualitative and quantitative criticality analysis and recommendations on usage of each within FMEA/FMECA. 3) how and when to incorporate Model-Based systems engineering to support FMEA/FMECA