《GEIA 标准 GEIA-STD-0009-2008.pdf》由会员分享，可在线阅读，更多相关《GEIA 标准 GEIA-STD-0009-2008.pdf（72页珍藏版）》请在三一文库上搜索。
1、ANSI/GEIA-STD-0009-2008 Approved: November 13, 2008 ITAA STANDARD GEIA-STD-0009 Reliability Program Standard for Systems Design, Development, and Manufacturing GEIA-STD-0009 August 2008 INFORMATION TECHNOLOGY ASSOCIATION OF AMERICA NOTICE ITAA Engineering Standards and Publications are designed to s
2、erve the public interest by eliminating misunderstandings between manufacturers and purchasers, 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 Standar
3、ds and Publications shall not in any respect preclude any member or nonmember of ITAA 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 ITAA members, wh
4、ether the standard is to be used either domestically or internationally. Standards and Publications are adopted by ITAA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, ITAA does not assume any liability to any patent owner, nor does it assume any ob
5、ligation whatever to parties adopting the Standard or Publication. This ITAA 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 ITAA Standard and the ISO/IEC document can be made. Th
6、is Standard does not purport to address all safety 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 befor
7、e its use. (Formulated under the cognizance of the ITAA G-47, Systems Engineering Committee, Reliability and Maintainability Subcommittee.) Published by 2008 Information Technology Association of America Standards eventually, it is the user. 1.3 Tailoring This standard does not specify the details c
8、oncerning “how to” engineer a system/product for high reliability. Nor does 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
9、 customer and developer. 2 GEIA-STD-0009 1.4 Organization The standard is 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
10、are used in a specific technical way in the body of the standard. Only those 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/suc
11、cess criteria, controls and responsibilities of all organizations involved 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 producibl
12、e and sustainable. 6.0 Objective 3: Produce Reliable Systems/Products The 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 purpos
13、e of this objective is to establish and execute the requirements of a field 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
14、 Reliability Best Practices Describes the recommended reliability program 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 var
15、ious reliability activities for each objective. Annex D Known Failure Definition 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 reliabilit
16、y objectives described herein is structured as follows: Introduction Mission 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
17、 Tools (Informative) Output and Documentation (Normative) The Introduction briefly 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 Organi
18、zations subsection which introduces considerations of personnel and organization 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
19、 accomplish this design- for-reliability objective. The second part, Developed 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 T
20、ools. Application of these processes and methods should result in a reliable product. 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 th
21、at is ultimately provided to other objectives in this standard is listed under 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 ano
22、ther objective. -,-,- GEIA-STD-0009 Figure 1 Information Flow Between Objectives 5 GEIA-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 r
23、evision, and parties to agreements based on this standard are encouraged to investigate 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 Achievi
24、ng Reliability, Availability, and Maintainability, August 3, 2005 GEIA 632 (An American 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 Octobe
25、r 1998 MIL-STD-785B Military Standard, Reliability Program for Systems and Equipment 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 Progra
26、m Standard SAE JA1000-1 1999-03 (An American National Standard), Reliability Program 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 sta
27、ndard, the following definitions apply. Term Definition Customer An individual, organization, 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 Int
28、egration (CMMI) provides guidance for defining and improving an organizations processes 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 orga
29、nizational maturity and process area capability, establish priorities for improvement, 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 perfor
30、ms the process requirements of this standard. Engineering The engineering of a system/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 conditi
31、ons as the result of exposure to natural environments during system/product use. Some 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 d
32、oes not, or would not, perform as previously specified under stated conditions for a 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
33、 material due to mechanical, chemical, electrical, thermal, or other stress. Failure Mode 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.
34、g., operating outside of specified requirements, environments, or operational procedures, 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). T
35、he informative material is annotated and is contained in notes and informative appendices. 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 caus
36、ed by the failure of another item when the system/product is operated in the specified 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 packa
37、ging, handling, shipping and transportation, power on/off cycles, mechanical shock, vibration and maintenance activities (scheduled, unscheduled, recalls, retrofits and software upgrades). Logistics Footprint The users/customers burden (inventory/equipment, personnel, facilities, transportation asse
38、ts, supply, and real estate) to deploy, move, and sustain a system/product for a given 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 o
39、f reliability that is related to an items non- operating design and its application when 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).
40、 Conformance to the standard is judged solely on the basis of the normative material in 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, ope
41、ration, maintenance, and repair. Quality Function Deployment Quality Function Deployment 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 ma
42、trices. Reliability Reliability is the ability/probability of failure free performance 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
43、-,-,- 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 of attributes, tolerances, and the test and inspection requirements necessary to produce a relia
44、ble, available, and maintainable product. Reliability Assessment An activity that quantitatively evaluates reliability using a model, failure definitions and scoring criteria, and the applied life cycle loads and environmental loads Reliability Case A reasoned, auditable argument created to support
45、the contention that a defined system/product satisfies the reliability requirements. The Reliability Case report documents the reliability evidence and arguments from the Reliability Case to support the program phases. Reliability Model A methodology for estimating the systems/products ability to me
46、et the specified reliability requirements. Reliability Verification Formally determining whether the customers quantitative reliability requirements have been met. Shall A mandatory requirement to be followed in order to conform to this standard. Should Indicates that there are several possibilities
47、: one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is discouraged but not prohibited. Supplier Provides a product or group of pr
48、oducts to a customer. The supplier can be a vendor that has a product that does not need development, or a developer that must develop the product or products. System/Product A system/product is an end item that may consist of hardware, software, firmware, facilities, data, materials, personnel, ser
49、vices, techniques, and processes. Systems Engineering A branch of engineering whose responsibility is creating and executing an interdisciplinary process to ensure that customer and users needs are satisfied in a high quality, trustworthy, cost efficient, and schedule compliant manner throughout a systems entire life cycle, from development to operation to disposal. Technical Review An event at which the pro