標準號：SAE ARP 5580-2001
中文標準名稱：針對非汽車應用推薦的失效模式及影響分析(FMEA)實踐
英文標準名稱：Recommended Failure Modes and Effects Analysis (FMEA) Practices for Non-Automobile Applications
標準類型：V05
發布日期：2001/7/1 12:00:00
實施日期：1999/12/31 12:00:00
中國標準分類號：V05
國際標準分類號：49.020
引用標準：MIL-HDBK-217-1991;RTCA DO-178B-1992;SAE J 1739-2000;SAE ARP 926B-1997;SAE ARP 1834-1986;SAE ARP 4761-1996;Advisory Circular 25.1309-1A;FMD-97;MIL-HDBK-338-1;MIL-STD-1629;NPRD-95;NUREG-0492;TR-TSY-332
適用范圍：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. Purpose: In developing this procedure the subcommittee has endeavored to develop a procedure that reflects the best current commercial practices. This procedure was developed in recognition of todays intense and competitive market demands for high reliability, affordability, and speed to market. The subcommittee had several objectives in defining the FMEA process: 1. Define a basic methodology to include functional, interface, and detailed FMEA. This will facilitate performing the analysis throughout the design process, from early in the conceptual stage to implementation and production. 2. Extend the methodology to include both product and process FMEAs. The methodology can be applied to the many technologies (e.g., mechanical, electrical, software, etc.) used in the development of a product. This helps to facilitate communications between all the parties involved in the development of a system and is useful in a concurrent engineering environment. 1. Provide simple techniques for ranking failure modes for corrective actions and for identifying fault equivalencies. 2. Define the types of information needed for the FMEA in electronic databases, thus facilitating semi-automation of the analysis. 3. Provide procedures for managing the FMEA and for getting the most benefit from the analysis.