REG NASA-LLIS-0738-2000 Lessons Learned Problem Reporting and Corrective Action System.pdf

《REG NASA-LLIS-0738-2000 Lessons Learned Problem Reporting and Corrective Action System.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0738-2000 Lessons Learned Problem Reporting and Corrective Action System.pdf（7页珍藏版）》请在麦多课文档分享上搜索。

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-04-3a71 Center Point of Contact: KSCa71 Submitted by: Wil HarkinsSubject: Problem Reporting and Corrective Action System Practice: A closed-loop Problem (or Failure) Reporting and Corrective Action System (PRACAS or FRACAS) i

2、s implemented to obtain feedback about the operation of ground support equipment used for the manned spaceflight program.Programs that Certify Usage: This practice has been used on Space Shuttle Program.Center to Contact for Information: KSCImplementation Method: This Lesson Learned is based on Reli

3、ability Practice No. PD-ED-1255; from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.Benefit:The information provided by Proplem Reporting and Corrective Action System (PRACAS) allows areas in possible need of improvement to be highlighted to engineering fo

4、r development of a corrective action, if deemed necessary. With this system in place in the early phases of a program, means are provided for early elimination of the causes of failures. This contributes to reliability growth and customer satisfaction. The system also allows trending data to be coll

5、ected for systems that are in place. Trend analysis may show areas in need of design or operational changes.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Implementation Method:A closed-loop system that collects, analyzes and records failures that o

6、ccur is developed. Documented procedures for the analysis of failures to determine their root cause and then the establishment of effective corrective action are also developed. This aids in the prevention of future reoccurrences by elimination of problem areas in the equipment.Technical Rationale:F

7、igure 1 illustrates the closed loop PRACAS with the necessary steps required to get full use out of such a system. This continuous loop provides the program with the opportunity to fine tune hardware reliability and performance through repeated iterations of reporting and corrective action.refer to

8、D descriptionD Figure 1. Closed-loop Problem Reporting and Corrective Action System Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Essentially the system must provide information on:1. What was the failure?2. How did the failure occur?3. Why did the

9、 failure occur?4. How can such failures be prevented from occurring in the future?The documentation procedures should include instructions for initiating problem reports, analyzing the failure and method of providing corrective action to the design and operation of the equipment. The most important

10、step in the process is documentation of the problem. The quality of the document will determine the effectiveness of the PRACAS for creating an acceptable solution. Minimum documentation for the problem should include:1. The location of the failure2. The date and time of the failure3. The applicable

11、 part numbers, serial numbers, model numbers4. The operation being performed5. The failure symptom6. The name and number of the reporting individual(s)7. The environment under which the failure occurred8. The impact of the failure on hardware and personnel safety9. For each test-related failure, a “

12、Stress statement“ on whether or not the failure induced any stress in the hardware.A means should also be available for tabulating the failure information for determining trends and the mean-time-between-failure of the equipment. Besides being useful to design and reliability engineering, this infor

13、mation may also be useful to maintenance personnel for determining maintenance periodicity of the equipment already in use. Failures that require “stress statements“ shall include test failures, operator induced failures, test equipment failures, environmental equipment failures, or any other proble

14、m/failures which did result in overstress, or which could have resulted in overstress, to any portion of flight hardware.Use at KSCThe KSC PRACA System provides the means to monitor and track the health of the Space Shuttle Ground Support Equipment and identify problem areas that require further inv

15、estigation. See figure 2 for the report that is used to identify and track problems at KSC. The majority of problems that are reported deal with component failures. However, any other condition that results in the system or equipment not meeting the requirements that were specified is also reported

16、(corrosion, out-of-Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-calibration, etc.).refer to D descriptionD Figure 2. KSC Problem Tracking Form Click on image for larger form in PDF format The PRACA system incorporates the following features:Provid

17、ed by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Tracking - The system encompasses the reporting, documentation, analysis and initiation of corrective actions relative to nonconformances detected during ground processing operations that are associated w

18、ith flight systems, ground support equipment and facilities. a71 Recurrence Control - The system provides a recurrence control function which is directed toward ensuring that specific problems or failures do not reoccur. a71 History - The system maintains historical data that supports ongoing proble

19、m resolution, trend analysis and recurrence control activities. This historical problem data is needed to support reliability, maintainability, and availability analysis. a71 NASA Centers - The system provides on-line visibility of the nonconformance data to other NASA Centers. Johnson Space Center

20、and Marshal Space Flight Center can view the data on-line. Extracts of data are also provided to JSC for input to the PCAS (Program Compliance Assurance and Status) System. a71 Batch Report - The system provides for the generation of batch reports on demand, weekly and/or monthly. a71 Security - The

21、 system provides access control that ensures that only authorized personnel may write to the database and then only to areas in which authority has been established. Query capability of the system is available to valid users at any time. a71 Automated Management Document Control System (AMDCS) - The

22、 system provides for the automatic transfer of nonconformance report data to AMDCS when final acceptance data is entered. a71 Ad Hoc Reports - The system provides for the generation of ad hoc reports using a user-friendly language. It also provides for the user to save ad hoc report specification fo

23、r later use. These reports are needed for specific trend and failure reports. a71 Document Accountability Control System (DACS)- The PRACAS utilizes the DACS for document tracking by attaching a bar-code symbol to each PRACA report. As the report is routed through the closure process the bar-code sy

24、mbol is scanned at each stop. The location of the report can then be determined by query of DACS. a71 Disposition/Causes/Corrective Action - The system identifies all actions associated with troubleshooting, remedial action, cause identification, recurrence control and unexplained problem resolution

25、. Trouble shooting and remedial action steps are documented. a71 Critical Items - The system identifies the criticality of the failure mode of the problems encountered. A Critical Items List (developed from a Failure Modes and Effects Analysis) is maintained in the database and the criticality code

26、is entered based on the part number. a71 Failure Analysis - The system identifies if failure analysis is required and provides the data for the Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-analysis. a71 Orbiter Thermal Protective System - The syst

27、em provides for the documentation and disposition of the Orbiter Thermal Protective System nonconformances. This includes a diagram showing the location on each tile of the nonconformance. a71 Corrective Action Assistance Request - The system supports addition, modification and retrieval of the Corr

28、ective Action Assistance Requests. a71 Formatted Problem Report - The systems provides for the formatted problem report to be printed on local printers. a71 Status - The system provides real-time status visibility of open and closed nonconformances and constraining nonconformances. It identifies whe

29、ther the nonconformance is a constraint to further test or precludes the performance of any sequence in the work document. a71 Search and Retrieval - The system provides for interactive search and retrieval which can be displayed on a terminal or, if large volume of data, sent to a printer. a71 Numb

30、er Generation - The system provides for automatic number generation for the nonconformance documents. The automatic number generator can be turned off as is the case when the nonconformance reports that are initiated when the system is not available are entered in the system. a71 Real-Time - The sys

31、tem supports testing operations and closeouts with real-time status information. a71 Other Useful Information - The system contains other useful information such as part numbers, serial numbers, end item control numbers, next higher assemblies, FSCM (Federal Supply Code for Manufacturers), STS (Spac

32、e Transportation System) #/effectivity, when failure is detected and operational document, including document type and number of the operation being performed, name of the technician, government quality assurance and contractor quality assurance who accepted the completion of the work. Other informa

33、tion such as, the need for critical skills, the need for retest and the system restore date are provided. References:1. Reliability Engineering for Electronic Design, Norman F. Fuqua, Marcel Dekker, Inc. 1987, pp. 322-325.2. Lockheed Space Operations Company, Standard Practice Instruction, Problem R

34、eporting and Corrective Action (PRACA) System - QA-001(3)K.3. Problem Failure Reporting Procedures, Reliability Preferred Practice PD-ED-1250.4. Problem/Failure Report Independent Review/Approval, Reliability Preferred Practice PD-AP-1304.5. Risk Rating of Problem/Failure Reports, Reliability Prefer

35、red Practice PD-AP-1305.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Impact of Non-Practice: Hardware/software problems that require further investigation may not be identified and tracked. Development of corrective action and need for improvement

36、 will not be highlighted to engineering. Opportunities for early elimination of the causes of failures and valuable trending data can be overlookedRelated Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-04-3a71 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-,-,-