Analytics are a significant enabler to get high value in the manufacturing industry. But how can you prove that you deliver value?
According to Gartner, more than half of all analytics projects fail because they are not completed within budget or on schedule, or because they fail to deliver the features and benefits that are optimistically agreed at the outset.
Based on my International experience, the approach and methodology works the same way everywhere.
Here are eight crucial tips to help you avoid misleading the project with poor problem forecasting and solving.
1. Start with the right business question and get started
Many analytic projects fail because the right business questions have not been discovered. For instance, analytics might discover that a small change within a process leads to much more efficiency, and save the company millions. This justifies the implementation of analytics, machine learning or predictive maintenance. Therefore, the very first step in applying data analytics successfully is a deep dive into business questions. If you have the right question – even if it seems small – it will be much easier to get your project started on the right footing.
2. Define the ‘why’ to help understand the ‘how’
After collecting the business questions to be answered by analytics, ask yourself: Is the right data available? Am I allowed to make use of the available data? Is this viable as well as feasible?
Once the business pain points and potential business improvements are determined and validated, the project must get kicked off. Together with a business consultant, goals, budget and a clear roadmap must be lined up. Determine clearly how you are going to measure success, in cooperation with your project sponsors, as well as the operations, IT and finance teams.
3. Dig below the surface and address the root cause
I have recently been working in the plastic molding injection industry, and our customer wanted to predict failures. Accurate predictions would enable the redeployment of workloads to other presses in the unlikely event of a loss of production. An unexpected failure to a heavy mechanical or hydraulic part could impact machine availability for days, as faulty parts must be sourced and replaced.
Nobody could understand the cause of one particular faulty part. It seemed the fault itself was a consequence, rather than the root cause of the machine failure. That faulty part was changed, but the signs of a new failure were still unknown. However, over time a drop in hydraulic pression, increased axis vibration and overheating components were all found to be indicators of an imminent failure. New IoT instruments could be added to monitor these new factors, and avoid intrusion in the press. The increased data was then used to better understand equipment behaviour and boost prediction accuracy.
4. Make sure you have the right methodology
There are no good or bad methodologies, as every one of them has its own strengths and weaknesses. Ultimately, no single methodology works across every business model and industry. One size does not fit all.
Consider your resources, the industry, and the kind of projects you will be managing before deciding on a methodology. I am in favour of brainstorming ideas from all team members, but also with business consultants in the same industry from other countries. Checking the feasibility of any methodology considering time to operationalization versus cost is very important. A simple pilot is relevant to validate a concept based only on data files. Start small and grow bigger.