《GEIA-GEIA-STD-0009-2008.pdf》由会员分享，可在线阅读，更多相关《GEIA-GEIA-STD-0009-2008.pdf（72页珍藏版）》请在三一文库上搜索。
1、 ITAA STANDARD GEIA-STD-0009 Reliability Program Standard for Systems Design, Development, and Manufacturing GEIA-STD-0009 August 2008 INFORMATION TECHNOLOGY ASSOCIATION OF AMERICA Copyright Government Electronics eventually, it is the user. 1.3 Tailoring This standard does not specify the details c
2、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
3、 customer and developer. 2 Copyright Government Electronics the inputs to each objective are often the outputs of another objective. Copyright Government Electronics or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of actio
4、n is discouraged but not prohibited. Supplier Provides a product or group of products 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 consi
5、st of hardware, software, firmware, facilities, data, materials, personnel, services, 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 qua
6、lity, 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 progress of the technical effort is assessed relative to its governing plans and technical requirements. User Ind
7、ividual, organization, or enterprise that uses, applies, or operates the product. 9 Copyright Government Electronics that the inherent design and/or process reliability of the fielded product continue to grow based on investigation into, and elimination of, root failure causes in the design and/or r
8、elated processes; that any new system/product failure mode experienced in the field that has not been previously accounted for in reliability analyses or testing is documented and communicated to all cognizant personnel for investigation and mitigation of root failure cause; and that all reliability
9、 data collected from the field is traceable to specified system/product reliability requirements and their metrics. Copyright Government Electronics Systems and/or Design Engineering (to include Reliability Engineering); Manufacturing and/or Process Engineering; Quality Assurance/Control; and Field
10、Maintenance/Support operations. While individual stakeholders on the team and team members may change over program phases, the program shall maintain continuity of resources, skills, and assets throughout the life-cycle phases of the program. The Lead for the multifunctional team should represent th
11、e organization (e.g., the Program Manager for DoD) that is most responsible for the reliability of the system/product in the field. Accountability shall be assigned to all members of the team to support the mission and goals of this Objective. 7.4 Supporting Information As a minimum, the input infor
12、mation listed under Input Information below is needed in order to begin to monitor and track field performance. Developed Information lists the information that will be developed as data is reported and analyzed from the field using the activities included under this objective. 7.4.1 Input Informati
13、on (Normative) All data and information that is defined, collected, and analyzed during the fielding phase of the system/product life cycle shall be compatible with the requirements and reliability program activities associated with the previous life cycle phases. This compatibility requires that th
14、e data and information shall be traceable to the satisfaction of specified reliability technical and program requirements and supporting metrics. The collected data/information shall directly support the update of previously performed assessments and analyses in both content and format. Inputs to th
15、is Objective from previous life cycle phases shall include: Failure definitions/scoring criteria Specified, quantified reliability requirements Initial and current reliability assessment of system/product Current reliability verification results Current estimates of user and environmental life-cycle
16、 loads that the system/product will encounter Current estimates of the life-cycle loads that subordinate assemblies and components will encounter Reliability Program Plan elements that address reliability support and fielding activities Current product configuration data Rationale for reliability re
17、quirements 37 Copyright Government Electronics bills of materials (BOMs); component and software libraries; FMEA/FMECA results; reliability predictions; reliability centered maintenance (RCM) results; failure reporting, analysis and corrective action systems (FRACAS); reliability-critical items list
18、s (CILs); test results (accelerated life, reliability growth, reliability demonstration, etc.); statistical life data analysis (Weibull analysis, Monte Carlo simulations, etc.); physics-of-failure analysis; Design of Experiments; lessons learned databases; etc. 7.4.2 Developed Information (Normative
19、) All outputs and documentation generated as a result of this Objective shall directly or indirectly support and be traceable to specified reliability requirements and metrics. All outputs, documents, data, and information generated as part of this Objective shall be analyzed and applied in a manner
20、 that will ensure that the inherent reliability of the fielded system/product design will not be degraded by maintenance actions, processes or procedures, or change in production or quality, and that failures experienced in the field result in corrective action(s) that continue to improve and grow t
21、he reliability of the product in a cost- and resource-optimized manner. As a minimum, outputs and documentation generated and communicated during this phase of the system or product life cycle shall facilitate: 1. Identification and analysis of all scheduled and unscheduled maintenance actions based
22、 on comprehensive reporting of : a. Items affected b. Conditions under which the failure or maintenance action occurred c. All items repaired and/or replaced d. All actions taken to restore normal system/product operation e. Actions and analyses performed at all system/product hierarchy levels (e.g.
23、, assemblies, subassemblies, components, parts, and/or materials) to determine root failure cause f. Corrective actions taken, implemented, verified, and approved to ensure that root failure cause(s) have been eliminated or their effects minimized 2. Establishment of timelines to determine static as
24、sessments of system/product reliability at specific reference points, and system/product field reliability trends over intervals of performance (time/cycles/miles/etc.) 3. Identification and communication of lessons learned to all stakeholders of the multifunctional team, and to the organization as
25、a whole, to ensure that systemic problems (and their solutions) are adequately addressed to preclude repeating of past problems and failures Outputs and documentation may be generated and made available in either hardcopy, electronic, or web-based formats, but an integrated and centralized reporting
26、 and closed-loop communication process and system shall be established, if not already defined and implemented in previous Objectives of this standard. The process/system developed from previous life cycle phases shall be utilized if it remains sufficient for the fielding phase, as agreed to by the
27、customer and the developer. This process/system shall allow controlled access by all relevant multifunctional team stakeholders. Additionally, the closed-loop process/system shall be capable of capturing all review and approval signatures at appropriate levels within the organization to ensure a rig
28、orous 38 Copyright Government Electronics and Design Trades that provide the customer and developer with the opportunity for early refinement and possible down-select of multiple design options. Product Phase Objective 2: Design and redesign for reliability. This phase focuses on successful approach
29、es for designing-in reliability. Objective 2 tasks consist of the Preliminary Design Review to validate that the initial system/product design is capable of meeting the reliability requirements; Prototype Test and Evaluation that provide confirmation that the design is capable or identifies areas fo
30、r potential redesign; and the Critical Design Review incorporates the findings of the Preliminary Design Review and the Prototype Test and Evaluation to establish the final design configuration. Product Phase Objective 3: Produce reliable systems/products. This phase focuses on the production reliab
31、ility starting with limited production. Objective 3 tasks consists of the Demonstration and Qualification of the system/product which provides the body of evidence that the reliability requirements have been achieved and the design is fully capable of meeting the customers/users needs. The Final Des
32、ign incorporates all outstanding design issues, additional design concerns from the design demonstrations and qualification testing and any manufacturing process changes needed in preparation for the low rate initial production and full rate production. Objective 3 culminates with Production deliver
33、y of a proven system/product to the user/customer. Product Phase Objective 4: Monitor and assess user reliability. This phase focuses on monitoring and managing reliability once the system/product in the hands of the user. While the developer strives for “perfect parts and prefect processes” design
34、deficiencies will be 45 Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 10/25/2008 02:41:26 MDTNo reproduction or networking permitted without license from IHS -,-,- GEIA-STD-0009 surfaced thr
35、ough on-going production testing and system/product usage by the user. The developers Change Control Process is key to the continued “as designed” performance of the system/product and preventing reliability margin erosion. Once the design has been released and under formal Change Control, design ch
36、anges are made to correct design errors found during deployment, improve manufacturing assembly and reduce manufacturing cost. Changes evaluated on an individual basis typically are not significant reliability drivers, but collectively, these changes can adversely impact the design reliability analy
37、sis. Operation and Delivery data collection is needed to further correct design deficiencies uncovered by the user under actual use conditions that can not be replicated by the developer, and Delivery and Maintenance data collection through factory and depot repairs provides the needed data to asses
38、s the long term system/product field reliability assessments. References denoted as DoD guidance in the table below can be found in the DoD RAM Guide, available for download at http:/ www.acq.osd.mil/sse/docs/RAM_Guide_080305.pdf or by contacting OUSD(AT&L) DS/SE/ED via ATL-EDOSD.MIL. The informatio
39、n in this section is provided for guidance purposes only and is not intended to be an all inclusive list. Product Phase Objective 1 Objective 2 Objective 3 Objective 4 Method Reference Design Concept Design Trades Preliminary Design Review Prototype Test & Evaluation Critical Design Review Design De
40、monstration and Qualification Final Design Production Change Control Process Operation & Delivery Delivery and Maintenance Accelerated Testing Methods (such as TAFT, RDGT, HALT, ALT) DoD 4.5.2.16, SAE JA1000-1 A.1 Bayesian Techniques DoD 4.5.2.29 Benchmarking DoD 4.5.2.12 Block Diagram Development S
41、AE JA1000-1 A.2 Capability Maturity Model Integration (CMMI) Software Engineering Institute/Carnegie Mellon Commercial-Off-the-Shelf (COTS) Assessment DoD 4.5.2.20 Component Testing DoD 4.5.2.18 Condition Based Maintenance (CBM) DoD 6.5.8 46 Copyright Government Electronics & Information Technology
42、Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 10/25/2008 02:41:26 MDTNo reproduction or networking permitted without license from IHS -,-,- GEIA-STD-0009 Product Phase Objective 1 Objective 2 Objective 3 Objective 4 Method Reference Design Concept
43、Design Trades Preliminary Design Review Prototype Test & Evaluation Critical Design Review Design Demonstration Production Change Control Process Operation & Delivery Delivery and Maintenance and Qualification Final Design Critical Items List DoD 3.5.6 Data Collection, Analysis and Corrective Action
44、 System (DCACAS) DoD 4.5.2.7 Data Management Technique (PREDICT) DoD 4.5.2.8 Design for Manufacturing and Design for Assembly SAE JA1000-1 A.3 Design of Experiments (Classical) SAE JA1000-1 A.4 Design of Experiments (Taguchi) SAE JA1000-1 A.5 Design Guidelines for Reliable Surface Mount Technology P
45、rinted Board Assemblies IPC-D-279 Design Review SAE JA1000-1 A.6 Durability Analysis (Low Cycle, High Cycle, Strength of Materials, Solder Joint) DoD 6.5.1.4 Durability Verification Test DoD 1.4.5.1 Environmental and Product Usage Profile /Mission Profile DoD 4.5.2.2, SAE JA1000-1 A.7 Environmental
46、Qualification Test DoD 5.5 Environmental Stress Screening (ESS)/Highly Accelerated Stress Screening (HASS) DoD 4.5.2.33, SAE JA1000-1 A.8 Error/Mistake Proofing SAE JA1000-1 A.9 Failure Modes and Effects Analysis (FMEA)/Failure Modes Effects and Criticality Analysis (FMECA) DoD,SAE JA1000-1 A.10 and
47、 GEIA-STD-0007 Failure Reporting Analysis and Corrective Action System (FRACAS) SAE JA1000-1 A.11 47 Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Licensee=Boeing Co/5910770001 Not for Resale, 10/25/2008 02:41:26 MDTNo reproduction or n
48、etworking permitted without license from IHS -,-,- GEIA-STD-0009 Product Phase Objective 1 Objective 2 Objective 3 Objective 4 Method Reference Design Concept Design Trades Preliminary Design Review Prototype Test & Evaluation Critical Design Review Design Demonstration Production Change Control Process Operation & Deliv