IEEE 1332-2012 en Reliability Program for the Development and Production of Electronic Products《电子产品生产和开发的电气与电子工程师学会(IEEE)标准可靠性程序》.pdf

《IEEE 1332-2012 en Reliability Program for the Development and Production of Electronic Products《电子产品生产和开发的电气与电子工程师学会(IEEE)标准可靠性程序》.pdf》由会员分享，可在线阅读，更多相关《IEEE 1332-2012 en Reliability Program for the Development and Production of Electronic Products《电子产品生产和开发的电气与电子工程师学会(IEEE)标准可靠性程序》.pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、IEEE Standard Reliability Program forthe Development and Production of Electronic Products Sponsored by the Standards Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA 16 January 2013 IEEE Reliability Society IEEE Std 1332-2012 (Revision of IEEE Std 1332-1998) IEEE Std 1332-2012 (Revision of

2、IEEE Std 1332-1998) IEEE Standard Reliability Program for the Development and Production of Electronic Products Sponsor Standards Committee of the IEEE Reliability Society Approved 5 December 2012 IEEE-SA Standards Board Approved 28 October 2014American National Standards InstituteAbstract: A standa

3、rd set of reliability program objectives for use between customers and producers, or within product development teams, to express reliability program requirements early in the development phase of electronic products and systems is provided in this document. Keywords: electronic equipment, electroni

4、c systems, electronics, IEEE 1332, reliability, reliability program, reliability program standard The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2013 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved.

5、 Published 16 January 2013. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Copyright 201

6、3 IEEE. All rights reserved. iv Notice to users Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers o

7、f the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This documen

8、t is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document a

9、vailable for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new editions or

10、may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given documen

11、t is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/standards.ieee.org/index.html or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the

12、IEEE standards development process, visit IEEE-SA Website at http:/standards.ieee.org/index.html. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata perio

13、dically. Copyright 2013 IEEE. All rights reserved. v Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence or vali

14、dity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may i

15、ndicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Essential Patent Cl

16、aims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or co

17、nditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is

18、 entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2013 IEEE. All rights reserved. viParticipants At the time this IEEE standard was completed, the Reliability Assessment Working Group had the following membership: Michael Pecht, Ph

19、. D., Chair Michael H. Azarian, Ph. D., Vice Chair Louis J. Gullo, Sponsor Committee Chair and SA Liaison Lori Bechtold Joseph Childs Michael Cushing, Ph. D. Diganta Das, Ph. D. Carla Head Tyrone Jackson Jason Mackinlay Keith Moore Timothy Pohland Fred Schenkelberg Benjamin Werner The following memb

20、ers of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Satish Aggarwal James Arnold Michael H. Azarian, Ph. D. Hugh Barrass Michael Basler Thomas Basso Lori Bechtold Wallace Binder Pieter Botman Bill Brown Malcom Brown Gus

21、tavo Brunello William Byrd Paul Cardinal Juan Carreon Joseph Childs Keith Chow Michael Cushing, Ph. D. Diganta Das, Ph. D. Ratan Das Matthew Davis Ray Davis Patrick Diamond Thomas Dineen Neal Dowling Gary Engmann David Fuschi David Gilmer James Gleason Chris Gorringe Lowell Goudge Randall Groves Lou

22、is J. Gullo Michael Gundlach Werner Hoelzl D. Hoffman Gary Hoffman Akio Iso Atsushi Ito Kenneth Karg Stuart Kerry Yuri Khersonsky Yongbum Kim Joseph L. Koepfinger Jim Kulchisky Saumen Kundu Greg Luri Ahmad Mahinfallah Edward McCall Georges Montillet Jeffrey Moore R. Murphy Ryan Musgrove Michael S. N

23、ewman Ted Olsen William Petit Annette Reilly Ted Riccio Michael Roberts Sergio Santos Bartien Sayogo Robert Schaaf Fred Schenkelberg Stephen Schwarm Alexander Sinyak Jeremy Smith Jerry Smith Joseph Stanco Walter Struppler William Taylor Eric Udren Srinivasa Vemuru John Vergis Hung-Yu Wei Matthew Wil

24、kowski Forrest Wright Oren Yuen Daidi Zhong Copyright 2013 IEEE. All rights reserved. vii When the IEEE-SA Standards Board approved this standard on 5 December 2012, it had the following membership: Richard H. Hulett, Chair John Kulick, Vice Chair Robert M. Grow, Past Chair Konstantinos Karachalios,

25、 Secretary Satish Aggarwal Masayuki Ariyoshi Peter Balma William Bartley Ted Burse Clint Chaplin Wael Diab Jean-Philippe Faure Alexander Gelman Paul Houz Jim Hughes Joseph L. Koepfinger* David J. Law Thomas Lee Hung Ling Oleg Logvinov Ted Olsen Gary Robinson Jon Walter Rosdahl Sam Sciacca Mike Seave

26、y Yatin Trivedi Phil Winston Don Wright *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Patrick Gibbons IEEE Standards Program Manager, Document Development Michael Kipness IEEE Sta

27、ndards Program Manager, Technical Program Development Copyright 2013 IEEE. All rights reserved. viii Introduction This introduction is not part of IEEE Std 1332-2012, IEEE Standard Reliability Program for the Development and Production of Electronic Products. The original version of IEEE Std 1332TMw

28、as developed in 1998 in response to the impending cancellation of MIL-STD-785, “Reliability Program for Systems and Equipment Development and Production.” The intent was to create a reliability program standard that would be equally useful to both the commercial and military sectors of industry. Ini

29、tial recommendations from industry, government, and academia were solicited through a questionnaire published in the April 1994 IEEE Reliability Society Newsletter. The recommendations formed the basis for the documents philosophy. The current revision of IEEE Std 1332 incorporates concepts and prac

30、tices introduced in the two recently issued reliability program-related standards, IEEE Std 1624TMB6aand ANSI/GEIA-STD-0009 B3. IEEE Std 1624 defines the term, “organizational reliability capability,” and provides specific criteria for assessing the capability of organizations to design and produce

31、systems and products that consistently meet reliability requirements. These criteria were structured around three reliability program objectives defined in the original version of IEEE Std 1332 and were elaborated through the identification of eight key practices with associated activities. ANSI/GEI

32、A-STD-0009 provides additional requirements for reliability management practices, design, and testing activities that make up an effective reliability program, without being prescriptive with regards to the specific methods used to accomplish those requirements. This document recognizes the reliabil

33、ity program structures described in IEEE Std 1624 B6 and ANSI/GEIA-STD-0009 B3 and incorporates these into the compliance requirements for an effective reliability program. It has been written to address the needs of both military program managers, where products are typically developed on the basis

34、 of contractual specifications, and the commercial sector, where products may be designed and manufactured without the prior receipt of an order. aThe numbers in brackets correspond to those of the bibliography in Annex A Copyright 2013 IEEE. All rights reserved. ix Contents 1. Overview 1 1.1 Scope

35、. 1 1.2 Purpose 1 1.3 Objectives of a reliability program 2 2. Suppliers reliability program . 2 3. The first objective requirements 3 3.1 Background 3 3.2 Reliability requirements. 4 3.3 Planning . 5 3.4 Training . 6 3.5 Additional communication 7 4. The second objective engineering . 7 4.1 Backgro

36、und 7 4.2 Parts, materials, and process selection . 8 4.3 Designing for reliability within item life conditions 8 4.4 Assessing reliability capability of the supply chain . 8 4.5 Identifying the critical-failure mechanisms . 9 4.6 Applying physics-of-failure principles 9 4.7 Reliability testing 10 5

37、. The third objective feedback 10 5.1 Background .10 5.2 Verification and validation .11 5.3 Failure data tracking and analysis .11 5.4 Reliability improvement .11 Annex A (informative) Bibliography 13 Copyright 2013 IEEE. All rights reserved. 1 IEEE Standard Reliability Program for the Development

38、and Production of Electronic Products IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, health, or environmental protection, or ensure against interference with or from other devices or networks. Implementers of IEEE Standards documents are responsible for determining and

39、 complying with all appropriate safety, security, environmental, health, and interference protection practices and all applicable laws and regulations. This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publica

40、tions containing this document and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html. 1. Overview 1.1 Scope This document provid

41、es a standard set of reliability program objectives for use between customers and producers, or within product development teams, to express reliability program requirements early in the development phase of electronic products and systems. 1.2 Purpose The purpose of this document is to establish a

42、standard set of objectives which provide an effective structure for the life-cycle activities needed to design, manufacture and utilize reliable electronic products and systems across the supply chain. IEEE Std 1332-2012 IEEE Standard for Reliability Program for the Development and Production of Ele

43、ctronic Products Copyright 2013 IEEE. All rights reserved. 2 1.3 Objectives of a reliability program The objectives of a reliability program apply to products, systems, or systems of systems, which are referred to as “items” for the purposes of this standard. An electronic system refers to both hard

44、ware and software. The reliability program has three objectives. The reliability program is integrated to the engineering life cycle, and the objectives of the reliability program are included in the overall engineering goals during the entire engineering life cycle for the item (IEEE Std 15288 B81)

45、 contains descriptions and requirements for systems engineering life cycle processes, which are applied during a life cycle for a particular item). The three objectives provide a flexible structure to promote necessary and sufficient interaction between the customer and supplier. The “supplier” is a

46、n entity that designs or produces electronic items. For the purposes of this standard, the supplier represents the community of developers and producers for the particular item. The “customer” is the entity that either purchases the electronic item from the supplier or is the recipient of the item f

47、rom within the same organization. The customer represents the community of users who will actually use the item. In the case of commercial off the shelf (COTS) items, for which requirements are not communicated directly from a customer to the suppler, any references in this standard to the customers

48、 reliability requirements refer to the suppliers reliability specifications for the item. Any of these requirements can be used to define the items reliability requirements. A reliability program plan that is written in accordance with the objectives of a reliability program and the requirements (i.

49、e., “shall” statements) as defined in this standard will be deemed conformant to this standard. The supplier shall create a reliability program plan and manage the reliability program activities through the execution of the reliability program plan. The reliability program plan shall include all the activities needed to accomplish at least the following three objectives: Objective 1 (requirements): The supplier shall determine the items requirements generated from customer requirements or other means described in Clause 3. The suppliers