• DocumentCode
    2796732
  • Title

    Best practices for a FRACAS implementation

  • Author

    Hallquist, Erik J. ; Schick, Todd

  • Author_Institution
    Relex Software Corp., Greensurgh, PA, USA
  • fYear
    2004
  • fDate
    26-29 Jan. 2004
  • Firstpage
    663
  • Lastpage
    667
  • Abstract
    Many companies use a FRACAS (failure reporting analysis and corrective action system) process, better known as a closed-loop analysis and correction action process, to track and report problems or failures. Very few companies, however, fully realize all of the possible benefits of a FRACAS process, such as improving quality and productivity while reducing costs. Although many issues may prevent an effective implementation, there are three areas of concern that may cause negative impacts irrespective of the best-intentioned technology. In particular, complex organization interaction, inefficient and ineffective data tracking, and a lack of prioritized goals prevent the dramatic results that can be achieved with a FRACAS. By following the suggested eight step methodology and best practices presented, the potential for implementing a high-performance FRACAS can be greatly increased.
  • Keywords
    closed loop systems; failure analysis; closed-loop analysis; complex organization interaction; corrective action system; data tracking; failure reporting analysis; Best practices; Costs; Data engineering; Databases; Failure analysis; Guidelines; Product development; Productivity; Reliability engineering; Testing;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Reliability and Maintainability, 2004 Annual Symposium - RAMS
  • Print_ISBN
    0-7803-8215-3
  • Type

    conf

  • DOI
    10.1109/RAMS.2004.1285523
  • Filename
    1285523