You’re convinced that OEE tracking will transform your production. Your field teams need it. But your management is hesitating, putting off, asking for more justification. This scenario is repeated in hundreds of production plants every year. The value of a global equipment efficiency project seems obvious to those who live the production process on a daily basis, much less to those who arbitrate budgets. In this article, we share concrete strategies for building a solid case and getting the green light from skeptical decision-makers.
Why Management Hesitates: Analysis of the Causes of Resistance
We’ve Already Tried It Syndrome
Many industrial companies have failed with digitalization projects. A manufacturing execution system never adopted, an ERP painfully deployed, Excel dashboards abandoned. These experiences leave their mark. When you propose an OEE project, your management sometimes hears “yet another tool that nobody will use”.
This mistrust reflects past investments that failed to deliver on their promises. Your job is to demonstrate how this project is different. The simplicity of deployment, the involvement of operators from the outset, the rapid rate-of-return results: these elements reassure a management team scalded by the productivity losses of previous projects.
The Difficulty of Quantifying Performance Gains
A CFO thinks in numbers. When you talk to him about continuous improvement and field visibility, he translates mentally into “cost without measurable return”. The vocabulary of production and that of finance do not naturally overlap.
OEE remains an abstract concept for anyone who has never set foot on a workshop floor. Gaining 5 points on this performance indicator means nothing without translating it into euros or additional capacity. Your sales pitch needs to break through this barrier by speaking the language of decision-makers and showing the impact on overall production time.
Building a Business Case: Solutions and Key Indicators
Calculate losses due to production stoppages
Before talking gains, talk losses. How much is the lack of visibility on your production line costing you today? Estimate the time wasted searching for data, the undetected production stoppages that drag on and on, the decisions taken on a whim in the absence of reliable key performance indicators.
Take a typical one-week period and reconstruct the losses: hours of unplanned downtime multiplied by the hourly cost of the machine, avoidable rejects, series changes that exceed standards. This work produces concrete figures. One million euros of identified annual losses justifies an investment of several tens of thousands. The source of this data must be documented in a usable database.
Calculate ROI with Performance Indicators
There is a temptation to inflate earnings forecasts. Resist the temptation. Experienced management detects optimistic assumptions. Prefer a conservative calculation based on modest gains: 2 to 3 SRT points in the first year rather than the 10 points sometimes announced.
Document each assumption about equipment efficiency. Cite industry references or feedback from comparable sites. Show the impact on the uptime and cycle time of your production machines. Also include the reduction in maintenance costs thanks to better anticipation of breakdowns. This rigorous approach strengthens your credibility in the budget planning phase.
Answering Objections: Improving efficiency
“C’est Trop Cher”: Demonstrating ROI Quality
This objection often reveals a lack of understanding of current solutions. Ten years ago, OEE projects required heavy investment. Modern IoT solutions have changed all that, with plug-and-play models and affordable monthly subscriptions that improve overall equipment effectiveness.
Answer with details of the actual cost structure. Compare with the cost of one hour of machine downtime. Reduce the investment to the cost per machine per month. The employee training included in these offers accelerates adoption and guarantees quality of deployment.
“Our Operators Won’t Use It”: The Question of Membership
This legitimate concern deserves a serious response. The difference with a well-executed OEE project lies in the involvement of operators right from the design stage, and the immediate value they derive from it in terms of their day-to-day efficiency.
Suggest involving a few pilot operators in the choice of solution. Explain that the screen belongs to them, that it helps them rather than watches over them. The speed of adoption depends on this initial positioning. Cite examples of plants where operators themselves demand installation on non-equipped machines.
“No Time”: Planning for a Fast Pilot
Lack of time often reflects a fear of the deployment burden. A modern OEE project is deployed in days, not quarters. This difference in temporality changes the nature of the objection and facilitates planning.
Propose a pilot on one or two machines, deployable in a day, with visible results within two weeks. This minimalist approach doesn’t overburden anyone, and quickly produces proof of value for the equipment concerned as a whole.
Strategies for Accelerating Decision-Making
Start with a Pilot to Prove Efficiency
Don’t ask for a complete plant roll-out from the outset. Propose a limited pilot: one machine, one line, one workshop. This limited scope limits the initial investment and reduces the perceived risk. A management team that rejects a €100,000 project may accept a €5,000 test.
The pilot produces concrete results in your specific context. These local data are better than any external references for demonstrating potential improvement.
Find Sponsors and Show Results
A project run by a single production manager has trouble getting through the validation stages. Identify allies: a quality manager concerned by rejects, a maintenance manager interested in anticipating breakdowns, a supply chain manager impacted by capacity contingencies. These sponsors broaden the support base.
From the very first weeks of the pilot, share the results with decision-makers. A stoppage detected and resolved quickly, an analysis of the causes identified, an operator testifying: these concrete stories maintain support and prepare for extension.
Conclusion: Perseverance and Method
Getting skeptical management on board takes time, method and resilience. Initial refusals are not final. Each exchange refines your arguments, each objection strengthens your case.
The key is to combine a rigorous business case with a progressive approach. Start small, prove fast, expand later. This strategy minimizes perceived risk while maximizing the chances of success. Your belief in the value of OEE is well-founded. All that remains is to transform this conviction into a decision with patience and determination.
FAQ : Frequently asked questions about OEE project membership
How long does it take to validate an OEE project?
The time required varies from one organization to another. In an SME with a manager close to the ground, a few weeks may suffice. In a large group with formalized budgetary processes, allow three to six months. A low-investment pilot is generally approved more quickly.
Should the IT department be involved from the outset?
Yes, the IT department can block a project if it discovers network or security implications too late. Involving them upstream turns them into an ally. Its legitimate concerns about the database and integration deserve to be included in the specifications.
How do you react if the pilot doesn't deliver the expected results?
Honestly analyze the causes before communicating. A disappointing pilot may reveal a perimeter or training problem rather than a weakness in the solution. Correct what can be corrected, and present the lessons learned transparently.
Is it better to ask for a capital or operating budget?
Both options have their advantages. Investment is suitable for equipment purchases with depreciation. Operation avoids cumbersome CAPEX validation processes. Choose according to your company’s practices and available budgets.
0 Comments