REG NASA-LLIS-0790--2000 Lessons Learned Problem Failure Report Independent Review Approval.pdf

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-04-17a71 Center Point of Contact: JPLa71 Submitted by: Wil HarkinsSubject: Problem/Failure Report Independent Review/Approval Practice: Problem/Failure (P/F) Reports are reviewed independently and approved by reliability engi

2、neering specialists to ensure objectivity and integrity in the closure process. This practice assures that the analysis realistically bounds the extent of the P/F, and the corrective action and its verification are successfully accomplished. The key elements are:a71 Analysis must address the problem

3、.a71 Corrective action must address the analysis and the problem.a71 Analysis must address the effect on other items.a71 Corrective action must have been implemented.a71 Item must have passed the gate that caused the P/F - the hardware/software must be successfully retested.Abstract: Preferred Pract

4、ice for Design & Test. The utilization of a P/F reporting system that has an independent P/F closure process is a major factor in the elimination of in-flight hardware/software failures attributed to preflight P/F that were not resolved adequately prior to launch. Problem/Failure (P/F) Reports are r

5、eviewed independently and approved by reliability engineering specialists to ensure objectivity and integrity in the closure process.Programs that Certify Usage: This practice has been used on the Mariners, Seasat, IRAS, VGR, VIK, GLL and MGN programs.Center to Contact for Information: Provided by I

6、HSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-JPLImplementation Method: This Lesson Learned is based on Reliability Practice number PD-AP-1304, from NASA Technical Memorandum 4322A, Reliability Preferred Practices for Design and Test.Benefit:Any independent rev

7、iew process increases the level of compliance of the subject process. It also broadens the scope and depth of experience available for each individual issue without the need for a large supporting staff at each supplier organization. Also, an in-place independent review structure improves the rate o

8、f data flow for a given level of effort.Implementation Method:There are several levels of independent review in a sequential review process. A Problem/Failure (P/F) not only affects the subject hardware/software but other elements of the system as well. At the first level of independent review, the

9、project/task system engineering organization reviews all identified system related P/F reports, all unknown cause P/F reports, all design related P/F reports, and all critical concern P/F reports that are identified as “Red Flag.“At any level of the independent review process, specialists in the are

10、a of the P/F can be consulted for their expertise. As a subset of the system level review all project/task systems test or ground operations P/F reports are routed to the test and operations manager for verification of closure adequacy.All P/F reports not initially sent to systems, as well as those

11、P/F reports that have been approved by systems, are sent to the project/task reliability engineering organization. Reliability engineering reviews each P/F report for adherence to the P/F reporting requirements, for completeness and lucidity of the technical contents, for uniformity of rating standa

12、rds, and for identification of generic P/F or broad issue-related P/F.At this point in the P/F review process, issue-specific specialists can be consulted on issues requiring their field of expertise (safety, environmental factors, etc.) or to explore broader issues raised by an examination of the P

13、/F that were not apparent at the internal P/F reporting level. P/F reports can be recycled back up the review chain if conditions are uncovered in the review process that warrant such an occurrence.The final step in the independent P/F closure process is the Project Management review and approval cy

14、cle. In the optimum review process, the status of closed, nonrisk P/F reports is provided by periodic P/F reporting status reports. The critical P/F reports, classified by the “Red Flag“ rating, are Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-rou

15、ted through the appropriate Project Management officials to determine the P/F impact on schedule and future funding, and to identify an element of residual mission risk.Technical Rationale:Independent P/F reporting closure is a key to reducing mission risk. On a recent mission, 25 percent of the con

16、tractor-submitted Problem/Failure Reports (P/FRs) had risk rating changes as a result of independent review by Reliability Engineering. Of the 25 percent changed, 1/4 were significant or red flag P/FRs (i.e., 1/16 or 6 percent were major issues). This process results in fewer schedule delays and att

17、endant funding problems late in the Project/Task, by providing the earliest isolation and documentation of P/F that can pose serious mission consequences. Generic P/F can be detected and consolidated in an efficient manner, with attendant cost savings. The P/F reporting system is a resource for prov

18、iding visibility to all levels of management in near real-time.References:1. “Risk Rating of Problem/Failure Reports,“ Reliability Preferred Practice PD-AP-1305.Impact of Non-Practice: The utilization of a P/F reporting system that has an effective independent P/F closure process is a major factor i

19、n the elimination of in-flight hardware/software failures attributed to preflight P/F that were not resolved adequately prior to launch.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-04-17a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-