Improving your data analysis: finding hidden data and data quality

Improving your data

With the winter solstice now behind us and the days starting to slowly get longer (around 2 minutes a day if you hadn’t noticed) it must mean that we have now entered the new Financial Year. With the mid-year review process fast approaching, we will start the scramble to find the previous years worth of data to review how we went comparatively. Best case, we’ll find we have improved since last year, but more often than we’d like, we find we’ve made a number of the same mistakes in our analysis. But how can this happen? Surely our analysis was effective and our conclusions were correct…

In conducting our analysis, we can fall into the trap of limiting our analysis only to the same data sources/types and miss the opportunity to ask whether this is the right data. When it comes to equipment performance data, we generally have a handle on the information we need ie. Failure data, Availability, Utilisation, OEE, Uptime, MTTF, MTTR, but we often fail to question whether this data is accurate or whether there is additional information that would help.

From our experience, the two areas that most often missed during analysis and yet can have a big impact on results are, the data quality and the “hidden data”.

Firstly, hidden data is the information that maintenance personnel have scribbled on a piece of paper on their desk, is in their head or is kept on a document on their desktop. Essentially, it’s the information isn’t always tracked in a spread-sheet, but is essential to keep your maintenance system operating. As we become more reliant on computer-based systems to run our operations, we need to understand where the gaps are and how to address them. This may mean making changes to the way you capture data or the way in which your systems are set-up, either way you need to find a way to ensure all of this data is captured if you are going to conduct effective analysis.

The second consideration is data quality, which is the confirmation that the data being captured by your system is correct i.e. breakdowns being coded as planned jobs or not being captured at all. The quality of simple things like this will significantly skew the reliability data that your system can provide. Fixing this requires an understanding of how operators capture information and why they record things the way they do. This may require a review of your maintenance workflows, training or organisational structure in order to ensure that the quality of the data is aligned to your requirements if you are going to be able to use this information during analysis.

Finding the hidden data and ensuring all of your other information is accurate is rarely a simple task, which is why it’s so often neglected, but when the quality of your underlying analysis is reliant on the quality and type of data being used – it is critical. As W. Edwards Deming once said, “you can’t manage what you don’t measure,” and if the data is not there or incorrect then how can you improve?