An Introduction, Basic Steps, and Examples of FRACAS Gone Wrong
Every failure has valuable information you and your team require to improve reliability. During the development process, each failure may represent a future recall. Celebrate every failure. Let your FRACAS prioritize which failures to resolve.
Failures occur, sometimes a bit too often. Some failures may lead to dangerous situations, while others may go unnoticed. Every failure has vital information. Tracking, prioritizing, and resolving the causes of product failures is a common business practice.
Let’s discuss the basics of the failure reporting and corrective action system. What issues to include. When to start tracking. Best practices concerning prioritization and root cause analysis. Plus, monitoring results of both short and long-term solutions.
The tools employed, from 3×5 cards to a whiteboard in the team room to a custom database, do not matter if the team uses the tool well. Let’s discuss striking the balance of gathering and tracking issues with the value the FRACAS provides.
This webinar will introduce you to the basic elements of FRACAS. Plus, we’ll examine a few processes that have derailed so that you can avoid a similar fate. Wrapping up with a few best practices to help you build or improve your FRACAS program.
This Accendo Reliability webinar originally broadcast on 14 March 2017.
To view the recorded webinar and slides, visit the webinar page.