Last week I provided an introduction to Failure Reporting, and its importance. This week, I’ll go a bit deeper. I’ve always stressed two things when talking about Failure Reporting:
- Report the failure! I know, it sounds silly. But if you aren’t doing any type of formal failure reporting today, then it’s a cultural change to get people to start doing it.
- Data Quality. Wait … let me say that again: Data Quality! So, you get to the point where failures are reported, but the quality of the data sucks. Then you really haven’t gotten anywhere, other than having more data, more work, but little to no information to base decisions on–other than the fact that you now know you need to improve the quality of your data.
Let’s start with some basics when it comes to reporting failures and the quality of the data reported. First and foremost, it centers around how your organization defines a failure (refer back to last week’s tip regarding definition). Below are some key considerations for reporting failures and data quality:
- Define and apply a uniform definition of what a failure is, and a method for classifying failures
- Define the boundaries of the equipment or process for failure reporting
- Define your objectives for collecting data
- Develop a data collection plan: who, what, where, when, why and how
- Investigate the source of the data to ensure relevant data of sufficient quality exists
- Prioritize the completeness of the data … what’s mandatory, what’s highly desirable, what’s nice to have
- Develop a plan on how the data will be assembled, reported and transferred into some type of failure reporting database
- Make a plan for how the data will be reviewed and verified. Note: I prefer using a Failure Review Board (FRB) process
- Organize, train and motive the people that will be reporting the data
The above key considerations are to get you to start thinking about failure reporting if you’re not currently doing it. And if you are currently doing it, but could use some improvement, hopefully the above may jump start your troubleshooting.
Remember, if you want to start improving the reliability of your equipment or service, start reporting failures and ensure the quality of the data is sufficient for making accurate, informed decisions.
In next week’s tip, we’ll move to the Analysis part of the FRACAS process.
© 2017 by LinRich Solutions, LLC. All rights reserved
