非汽车应用的推荐故障模式和影响分析（FMEA）规程描述了执行故障模式和影响分析（FMEA）的基本程序。它包括功能、接口和详细的FMEA，以及某些分析前活动（FMEA规划和功能需求分析）、分析后活动（故障延迟分析、FMEA验证和文档），以及硬件、软件和过程设计的应用。其目的是供其产品开发过程将FMEA用作评估系统要素安全性和可靠性的工具的组织使用，或作为其产品改进过程的一部分。 单独的地面车辆推荐规程J1739适用于汽车应用。目的:在制定本程序时，小组委员会努力制定一个反映当前最佳商业实践的程序。该程序的开发是为了认识到当今激烈竞争的市场对高可靠性、可承受性和上市速度的需求。小组委员会在定义FMEA过程时有几个目标:1。定义基本方法，包括功能、接口和详细的FMEA。 这将有助于在整个设计过程中进行分析，从概念阶段的早期到实施和生产。2.扩展方法，以包括产品和过程FMEA。该方法可应用于产品开发中使用的许多技术（例如，机械、电气、软件等）。这有助于促进参与系统开发的各方之间的通信，在并行工程环境中非常有用。1.提供简单的技术，对故障模式进行排序，以采取纠正措施，并识别故障等效性。 2.在电子数据库中定义FMEA所需的信息类型，从而促进分析的半自动化。3.提供管理FMEA和从分析中获得最大利益的程序。

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 today's 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.