You are convinced that OEE monitoring would transform your production. Your floor teams need it. But your management hesitates, postpones, asks for more justifications. This scenario repeats itself in hundreds of manufacturing plants every year. The value of an overall equipment effectiveness project seems obvious to those who experience the production process daily, much less so for those who allocate budgets. In this article, we share concrete strategies to build a solid case and get the green light from skeptical decision-makers.
Why Management Hesitates: Analysis of Resistance Causes
The “We’ve Already Tried” Syndrome
Many industrial companies have experienced failures with digitalization projects. A manufacturing execution system never adopted, an ERP deployed painfully, Excel dashboards abandoned. These experiences leave traces. When you propose an OEE project, your management sometimes hears “another tool that no one will use.”
This mistrust reflects past investments that didn’t deliver on their promises. Your job is to demonstrate how this project differs. The simplicity of deployment, operator involvement from the start, rapid results on performance rates: these elements reassure management burned by the productivity losses of previous projects.
The Difficulty of Quantifying Performance Gains
A finance director thinks in numbers. When you talk about continuous improvement and floor visibility, they mentally translate to “cost without measurable return.” The vocabulary of production and finance don’t naturally overlap.
OEE remains an abstract concept for those who have never set foot on the shop floor. Gaining 5 points on this performance indicator means nothing without translation into euros or additional capacity. Your argument must cross 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
Quantifying Losses Related to Production Downtime
Before talking gains, talk losses. How much does the lack of visibility on your production line cost today? Estimate the time lost searching for data, undetected production stoppages that drag on, decisions made on gut feeling due to lack of reliable key performance indicators.
Take a typical one-week period and reconstruct the losses: hours of unplanned downtime multiplied by machine hourly cost, avoidable rejects, changeovers that exceed standards. This work produces concrete figures. One million euros of identified annual losses justifies an investment of tens of thousands. The source of this data must be documented in an exploitable database.
Calculating ROI with Performance Indicators
The temptation exists to inflate gain forecasts. Resist. Experienced management detects optimistic assumptions. Prefer a conservative calculation based on modest gains: 2 to 3 OEE points in the first year rather than the 10 points sometimes announced.
Document each assumption about equipment effectiveness. Cite sector references or experience feedback from comparable sites. Show the impact on operating time and cycle time of your production machines. Also integrate the reduction in maintenance costs through better anticipation of failures. This rigor reinforces your credibility for the budget planning phase.
Addressing Objections: Efficiency Improvement
“It’s Too Expensive”: Demonstrating ROI Quality
This objection often reveals a lack of knowledge about current solutions. OEE projects from ten years ago required heavy investments. Modern IoT solutions have changed the game with plug-and-play models and accessible monthly subscriptions that improve overall equipment effectiveness.
Respond by detailing the actual cost structure. Compare with the price of one hour of machine downtime. Break down the investment to cost per machine per month. The employee training included in these offers accelerates adoption and guarantees deployment quality.
“Our Operators Won’t Use It”: The Question of Adoption
This legitimate fear deserves a serious answer. The difference with a well-conducted OEE project lies in involving operators from the design phase and the immediate value they get from their daily efficiency.
Propose involving some pilot operators in choosing the solution. Explain that the screen belongs to them, that it helps them rather than monitors them. Adoption speed depends on this initial positioning. Cite examples of factories where operators themselves request installation on non-equipped machines.
“We Don’t Have Time”: Planning a Rapid Pilot
Lack of time often translates to fear of deployment workload. A modern OEE project deploys in days, not quarters. This difference in timeline changes the nature of the objection and facilitates planning.
Propose a pilot on one or two machines, deployable in one day, with visible results within two weeks. This minimalist approach doesn’t overload anyone and quickly produces proof of value on the overall equipment concerned.
Strategies to Accelerate Decision-Making
Starting with a Pilot to Prove Effectiveness
Don’t immediately ask for a complete plant deployment. Propose a limited pilot: one machine, one line, one workshop. This restricted scope limits the initial investment and reduces perceived risk. Management that refuses a €100,000 project might accept a €5,000 test.
The pilot produces concrete results in your specific context. This local data is worth more than all external references to demonstrate possible improvement.
Finding Sponsors and Showing Results
A project carried by a single production manager struggles to pass validation stages. Identify allies: quality director concerned with rejects, maintenance manager interested in failure anticipation, supply chain director impacted by capacity uncertainties. These sponsors broaden the support base.
From the first weeks of the pilot, share results with decision-makers. A stoppage detected and resolved quickly, identified root cause analysis, an operator who testifies: these concrete stories maintain support and prepare for extension.
Conclusion: Perseverance and Method
Getting buy-in from skeptical management requires time, method, and resilience. Initial refusals are not final. Each exchange refines your argument, each objection addressed strengthens your case.
The key lies in combining a rigorous business case with a progressive approach. Start small, prove quickly, then expand. This strategy minimizes perceived risk while maximizing chances of success. Your conviction about OEE value is founded. It remains to transform this conviction into decision with patience and determination.
FAQ: Frequently Asked Questions on OEE Project Buy-In
How long does it take to get validation for an OEE project?
The timeline varies by organization. In an SME with a manager close to operations, a few weeks may suffice. In a large group with formal budget processes, count on three to six months. A low-investment pilot generally gets approved faster.
Should IT be involved from the beginning?
Yes. IT can block a project if it discovers network or security implications too late. Involving them upstream transforms them into an ally. Their legitimate concerns about databases and integration deserve to be integrated into the specifications.
How to react if the pilot doesn’t give expected results?
Honestly analyze the causes before communicating. A disappointing pilot may reveal a scope or training problem rather than a solution weakness. Correct what can be corrected and present lessons learned with transparency.
Is it better to request an investment or operating budget?
Both options have their advantages. Investment suits equipment purchases with depreciation. Operating avoids heavy CAPEX validation processes. Choose according to your company’s practices and available envelopes.
0 Comments