Although failure reporting, analysis, and corrective action system (FRACAS) has two management perspectives, its tasks and related information, the previous researches and applications mainly have focused on the data management. This study is to develop a process-oriented FRACAS which supports the operation of the failure-related activities. The development procedures are (1) to define the reporting and analysis tasks, (2) to define the information to be used at each task, and (3) to design a computerized business process model and set the attributes such as durations, rules, and document types. This computerized FRACAS process can be activated in a business process management system (BPMS) which employs the enactment functions, deliver tasks to the proper workers, provide the necessary information, and alarm the abnormal status of the tasks (delay, incorrect delivery, cancellation). Through implementing the prototype system, improvements are found for automation of the tasks, prevention of disoperation, and real-time activity monitoring. 1. Introduction Recently, the reliability of products or services is recognized as a key factor to accomplish the competitiveness of a company. Reliability refers to the ability of a system or a component to perform its required functions under the stated conditions for a specified period of time. In reliability engineering, it is important to collect and analyze the related information in diverse phases, development, testing, production, and operation. FRACAS is a management tool which is established to identify and correct deficiencies in a system or a component, and thus prevents further occurrence of them [1]. Its objective is to provide engineering data for corrective actions, assess historical reliability performance (mean time between failure, mean time to recover, availability, etc.), develop patterns for the deficiencies, and provide data for statistical analysis [2]. FRACAS is composed of various components such as engineers, equipment, documents, product specifications and organizations. Also, it has been widely implemented in diverse industries which are larg sized and complicated with many participants and organizations such as military [1], aerospace [3], railroad [4], nuclear power plant [5], medical [6], and distribution industry [7]. Many of difficulties in implementing FRACAS come from these features. Hallquist pointed out that the major problems are complex organization interaction, inefficient and ineffective data tracking, and a lack of prioritized goals [8]. Normally, the management of FRACAS has
References
[1]
MIL-HDBK-338B, Military Handbook: Electronic Reliability Design Handbook, U.S. Department of Defense, 1998.
[2]
M. Villacourt, “Failure reporting, analysis and corrective action system in the US semiconductor manufacturing equipment industry: a continuous improvement process,” in Proceedings of the IEEE/CHMT International Electronics Manufacturing Technology Symposium, 1992.
[3]
A. Mukherjee, “Integrated FRACAS systems for F117 Infrared Acquisition Designation System (IRADS) support yield higher MTBMA,” in Proceedings of Annual Reliability and Maintainability Symposium, pp. 26–29, January 2005.
[4]
J. E. Oh and C. Y. Kang, “Study on the application of FRACAS system for rolling stock,” in Proceedings of the Conference of the Korean Society for Railway, pp. 487–497, 2006.
[5]
S.-W. Hwang, J.-Y. Oh, and M. Jae, “Development of web-based reliability data analysis algorithm model and its application,” Annals of Nuclear Energy, vol. 37, pp. 248–255, 2009.
[6]
J. Krouwer, “Using a learning curve approach to reduce laboratory errors,” Accreditation and Quality Assurance, vol. 7, no. 11, pp. 461–467, 2002.
[7]
J. Moltoft, “Reliability engineering based on field information—the way ahead,” Quality and Reliability Engineering International, vol. 10, no. 5, pp. 399–409, 1994.
[8]
E. J. Hallquist and T. Schick, “Best practices for a FRACAS implementation,” in Proceedings of the Annual Reliability and Maintainability Symposium, pp. 663–667, January 2004.
[9]
J. A. Jones and J. A. Hayes, “Use of a field failure database for improvement of product reliability,” Reliability Engineering and System Safety, vol. 55, no. 2, pp. 131–134, 1997.
[10]
C. Nagynémedi, E. Harkai, D. Rigler, R. Kovács, B. Balogh, and P. Gordon, “Failure analysis results systematization,” in Proceeding of the 32nd International Seminar on Electronics Technology: Hetero System Integration, the Path to New Solutions in the Modern Electronics (ISSE '09), May 2009.
[11]
C. Magniez, A. C. Brombacher, and J. Schouten, “The use of reliability-oriented field feedback information for product design improvement: a case Study,” Quality and Reliability Engineering International, vol. 25, no. 3, pp. 355–364, 2009.
[12]
C. Bunea, T. A. Mazzuchi, S. Sarkani, and H.-C. Chang, “Application of modern reliability database techniques to military system data,” Reliability Engineering and System Safety, vol. 93, no. 1, pp. 14–27, 2008.
[13]
J. Jauw and P. Vassiliou, “Field data is reliability information: implementing an automated data acquisition and analysis system,” in Proceeding of Annual Reliability and Maintainability Symposium, pp. 24–27, Los Angeles, Calif, USA, 2000.
[14]
M. Ciemian, “Increasing the effectiveness of FRACAS,” in Proceedings of the 54th Annual Reliability and Maintainability Symposium (RAMS '08), January 2008.
[15]
A. Katz, N. Argov, A. Shapira, I. Gershman, and N. Refaeli, “The efficacy of a test and ESS program,” Quality and Reliability Engineering International, vol. 18, no. 2, pp. 99–109, 2002.
[16]
J. Ling, P. Hsieh, and T. Cowing, “Reliability engineering practice in the light duty dodge ram truck chassis program,” Quality and Reliability Engineering International, vol. 21, no. 1, pp. 1–11, 2005.
[17]
L. H. Crow, “Studies and methods for improving the effectiveness of reliability tasks,” in Proceeding of the Annual Reliability and Maintainability Symposium, pp. 14–19, January 2005.
[18]
K. M. Whaling and D. C. Kemp, “Driving the feedback loop reliability and safety in the full life cycle,” in Proceedings of the Annual Reliability and Maintainability Symposium, pp. 61–67, January 2004.
[19]
A. Mettas and D. Rock, “Intellectual capital: utilizing the web for knowledge management and data utilization in reliability engineering,” in Proceedings of the Annual Reliability and Maintainability Symposium, pp. 379–385, January 2002.
[20]
Lockheed Space Operations Company, “Standard Practice Instruction, Problem Reporting and Corrective Action (PRACA) System—QA-001(3)”.
