1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there
2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2013 SAE International All rights reserved. No part of this p
3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/GEIASTD0009 TECHNICAL REPORT GEIA-STD-0009 Issued 2008-08 Reliability Program Sta
5、ndard for Systems Design, Development, and Manufacturing NOTICE This document has been taken directly from the original TechAmerica document and contains only minor editorial and format changes required to bring it into conformance with the publishing requirements of SAE Technical Standards. The rel
6、ease of this document is intended to replace the original with the SAE International document. Any numbers established by the original document remain unchanged. The original document was adopted as an SAE publication under the provisions of the SAE Technical Standards Board (TSB) Rules and Regulati
7、ons (TSB 001) pertaining to accelerated adoption of specifications and standards. TSB rules provide for (a) the publication of portions of unrevised specifications and standards without consensus voting at the SAE committee level, and (b) the use of the existing specification or standard format. Tec
8、hAmerica Standard GEIA-STD-0009 Reliability Program Standard for Systems Design, Development, and Manufacturing GEIA-STD-0009 August 2008 NOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderstandings between manufacturers and pur
9、chasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TechAm
10、erica from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used either domestically or internationally.
11、Standards and Publications are adopted by TechAmerica in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publi
12、cation. This TechAmerica Standard is considered to have International Standardization implications, but the ISO/IEC activity has not progressed to the point where a valid comparison between the TechAmerica Standard and the ISO/IEC document can be made. This Standard does not purport to address all s
13、afety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (Formulated under the cognizance o
14、f the TechAmerica G-47, Systems Engineering Committee, Reliability and Maintainability Subcommittee.) Published by 2009 TechAmerica Standards eventually, it is the user. 1.3 Tailoring This standard does not specify the details concerning “how to” engineer a system/product for high reliability. Nor d
15、oes it mandate the methods or tools a developer would use to implement the process requirements. The tailoring is dependent upon customers funding profile, developers internal policies and procedures and negotiations between the customer and developer. 2 GEIA-STD-0009 1.4 Organization The standard i
16、s organized as described in Table 1: Table 1 Organization of Standard Section Title Description 2.0 Informative References Lists other standards that are referred to in the text. 3.0 Definitions Gives definitions for words that are used in a specific technical way in the body of the standard. Only t
17、hose terms for which the normal dictionary definition does not suffice are included. 4.0 Objective 1: Understand Customer/User Requirements and Constraints The first objective defines the reliability requirements, assessment/success criteria, controls and responsibilities of all organizations involv
18、ed for program success. 5.0 Objective 2: Design and Redesign for Reliability The focus of this second objective is on designing a system/product that satisfies reliability specifications, user requirements, and is both producible and sustainable. 6.0 Objective 3: Produce Reliable Systems/Products Th
19、e purpose of this objective is to ensure that systems/products are manufactured with minimum impact on the inherent reliability during the execution of Objective 2. 7.0 Objective 4: Monitor and Assess User Reliability The purpose of this objective is to establish and execute the requirements of a fi
20、eld reliability monitoring system comprised of data collection, analysis, maintenance and closed-loop feedback activities Annex A Methods Matrix Methods and tools that support the normative activities in Objectives 1 - 4 Annex B Reliability Best Practices Describes the recommended reliability progra
21、m best practices that may be used to ensure that the reliability program requirements are met during the execution of Objectives 1 through 4. Annex C Key Documents Matrix Provides references for the detailed “how to” for the various reliability activities for each objective. Annex D Known Failure De
22、finition and Scoring Criteria References to mandatory failure definition and scoring criteria of the DoD Services. Annex E Acronyms List of acronyms used in this standard 1.4.1 Structure of Objectives Each of the four reliability objectives described herein is structured as follows: Introduction Mis
23、sion and Goals People and Organizations 3 GEIA-STD-0009 4 Supporting Information (Normative) Input Information (Normative) Developed Information (Normative) Activities, Methods, and Tools Activities (Normative) Methods and Tools (Informative) Output and Documentation (Normative) The Introduction bri
24、efly introduces the objective. The subsection, Mission and Goals, provides additional background and context that are needed so one can develop a clear understanding of this objective. It is followed by a People and Organizations subsection which introduces considerations of personnel and organizati
25、on that must be addressed when designing reliability into a product. The Supporting Information subsection contains two parts. The first part, Input Information, lists essential input information that is needed in order to accomplish this design-for-reliability objective. The second part, Developed
26、Information, lists the information that is developed during the accomplishment of this objective. As shown in Figures 1 thru 5, the input information feeds the processes and methods contained in Activities, Methods, and Tools. Application of these processes and methods should result in a reliable pr
27、oduct. Activities, Methods, and Tools contains two parts, a normative (mandatory) set of activities and an informative set of methods and tools that are provided for guidance information only. The developed information that is ultimately provided to other objectives in this standard is listed under
28、Outputs and Documentation. 1.4.2 Development and Flow of Information Between Objectives Figure 1 depicts the information that flows into and out of each objective; the inputs to each objective are often the outputs of another objective. GEIA-STD-0009 Figure 1 Information Flow Between Objectives 5 GE
29、IA-STD-0009 2 Informative References The following references were used as guidance for the development of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investiga
30、te the possibility of applying the most recent editions of the standards indicated below. Crow, Larry H., Operational Reliability Management, CRR 522, Crow Reliability Resources, Inc., May 2008 DOD Guide for Achieving Reliability, Availability, and Maintainability, August 3, 2005 GEIA 632 (An Americ
31、an National Standard), Processes for Engineering a System IEEE 1332-1998 (An American National Standard), Standard Reliability Program for the Development and Production of Electronic Systems and Equipment, 2 October 1998 MIL-STD-785B Military Standard, Reliability Program for Systems and Equipment
32、and Development and Production, 15 September 1980 Reliability Information Analysis Center (RIAC) Blueprints for Product Reliability, 15 May 1996 SAE JA1000 1998-06 (An American National Standard), Reliability Program Standard SAE JA1000-1 1999-03 (An American National Standard), Reliability Program
33、Standard Implementation Guide Tiku, Sanjay, Reliability Capability Evaluation for Electronics Manufacturers, Ph.D. dissertation, University of Maryland, 2005 6 GEIA-STD-0009 3 Definitions For the purposes of the standard, the following definitions apply. Term Definition Customer An individual, organ
34、ization, or enterprise that commissions the engineering of a product, is a prospective purchaser of the product, or is the acquirer of the product. Capability Maturity Model Integration Capability Maturity Model Integration (CMMI) provides guidance for defining and improving an organizations process
35、es and the organizations ability to manage the development, acquisition, and maintenance of products and services. CMM Integration places proven practices into a structure that helps the organization assess its organizational maturity and process area capability, establish priorities for improvement
36、, and guides the implementation of these improvements. Design Reliability The set of design, development, and manufacturing tasks by which reliability is achieved. Developer An enterprise or organization that performs the process requirements of this standard. Engineering The engineering of a system
37、/product is accomplished by applying a set of processes to each element of the hierarchy by a multifunctional team of people who have the requisite knowledge and skills. Environmental Loads Defined stressing conditions as the result of exposure to natural environments during system/product use. Some
38、 typical natural environment stressing conditions are storage and operating temperatures, humidity, diurnal cycles, and solar loading . Failure The events, or inoperable state, in which any item or part of an item does not, or would not, perform as previously specified under stated conditions for a
39、stated period of time. Failure Mechanism The physical, chemical, electrical, thermal, or other process that results in failure. For example: fatigue, fracture, electro-migration, electrical overstress, depletion of material due to mechanical, chemical, electrical, thermal, or other stress. Failure M
40、ode The consequence of the mechanism through which an item fails (e.g., short, open, fracture, excessive wear, etc.). Induced Failure A failure due to a condition and not due to its own internal failure pattern (e.g., operating outside of specified requirements, environments, or operational procedur
41、es, improper handling, support equipment, or operator error). 7 GEIA-STD-0009 Term Definition Informative Material/Activities Explanatory material to help the user understand the standard (the informative parts). The informative material is annotated and is contained in notes and informative appendi
42、ces. Inherent Failure A failure that occurs without being caused by the failure of another item. Inherent Reliability A measure of reliability which is related to an items design and its application and is not caused by the failure of another item when the system/product is operated in the specified
43、 operation and support environments for a specified duration. Life Cycle Loads Stressing conditions as the result of exposure to normal system/product use. Some typical system/product stressing conditions are packaging, handling, shipping and transportation, power on/off cycles, mechanical shock, vi
44、bration and maintenance activities (scheduled, unscheduled, recalls, retrofits and software upgrades). Logistics Footprint The users/customers burden (inventory/equipment, personnel, facilities, transportation assets, supply, and real estate) to deploy, move, and sustain a system/product for a given
45、 service use profile. Multifunctional A group of individuals representing various product disciplines such as engineering, manufacturing, software, quality, reliability, etc. Non-operational Reliability A measure of reliability that is related to an items non-operating design and its application whe
46、n the system/product is stored in an environmentally protected and/or unprotected location. Normative Material/Activities The portion of the standard that prescribes mandatory implementation (the standard itself). Conformance to the standard is judged solely on the basis of the normative material in
47、 this standard Operational Reliability A measure of the systems/products performance during the items operational life that includes the combined effect of the items design, installation, quality, environment, operation, maintenance, and repair. Quality Function Deployment Quality Function Deploymen
48、t is designed to help planners focus on characteristics of a new or existing product or service from the viewpoints of market segments, company, or technology-development needs. This technique yields graphs and matrices. Reliability Reliability is the ability/probability of failure free performance
49、of the system/product, over the expected service use profile and environmental conditions over a given period of time. Reliability is expressed in terms of operational reliability and non-operating reliability. 8 GEIA-STD-0009 Term Definition Reliability Activity The set of design, development, manufacturing, and maintenance tasks performed to identify, quantify, and qualify product characteristics in terms
