You are convinced that OEE monitoring would transform your production. Your floor teams need it. But your management hesitates, delays, demands further justification. This scenario repeats itself in hundreds of manufacturing plants each year. The value of an OEE project appears obvious to those who experience the production process daily, far less so to those who allocate budgets. In this article, we share concrete strategies to build a solid business case and get the green light from skeptical decision-makers.
Why Management Hesitates: Analysis of Resistance Causes
The “We Already Tried That” Syndrome
Many industrial companies have experienced failures with digitalization projects. A manufacturing execution system never adopted, an ERP deployed painfully, abandoned Excel dashboards. These experiences leave scars. 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 task is to demonstrate how this project differs. The simplicity of deployment, operator involvement from the start, rapid results on OEE rate: these elements reassure management scarred by productivity losses from previous projects.
The Difficulty in Quantifying Performance Gains
A finance director reasons in numbers. When you talk about continuous improvement and shop floor visibility, they mentally translate it as “cost with no measurable return.” Manufacturing language and finance language don’t naturally align.
TRS remains an abstract concept for those who have never set foot on the factory floor. Gaining 5 points on this performance indicator means nothing without conversion to euros or additional capacity. Your argument must bridge this gap 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 Stoppages
Before discussing gains, talk about losses. What does the current lack of visibility on your production line cost? Estimate time lost searching for data, undetected production stoppages that drag on, decisions made on intuition due to lack of reliable key performance indicators.
Take a typical week and reconstruct the losses: hours of unplanned downtime multiplied by the machine’s hourly cost, avoidable scrap, changeovers exceeding standards. This work produces concrete figures. One million euros in 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 it. An experienced management team detects optimistic assumptions. Prefer conservative calculation based on modest gains: 2 to 3 points of TRS 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 include maintenance cost reduction through better failure anticipation. This rigor strengthens your credibility for the budget planning phase.
Addressing Objections: Improving Effectiveness
“It’s Too Expensive”: Demonstrating ROI Quality
This objection often reveals ignorance of current solutions. OEE projects from ten years ago required heavy investments. Modern IoT solutions have changed the game with plug-and-play models and affordable monthly subscriptions that improve overall equipment effectiveness.
Respond by detailing actual cost structure. Compare with the price of one hour of machine downtime. Reduce the investment to cost per machine per month. Employee training included in these offerings accelerates adoption and guarantees deployment quality.
“Our Operators Won’t Use It”: The Adoption Question
This legitimate concern deserves a serious response. The difference with a well-executed OEE project lies in operator involvement from the design stage and the immediate value they gain for their daily effectiveness.
Propose involving a few pilot operators in solution selection. Explain that the screen belongs to them, that it helps rather than monitors them. Adoption speed depends on this initial positioning. Cite examples of plants where operators themselves demand installation on unequipped machines.
“We Don’t Have Time”: Planning a Quick Pilot
Lack of time often reflects fear of deployment burden. A modern OEE project deploys in days, not quarters. This difference in timing 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 across the equipment involved.
Strategies to Accelerate Decision-Making
Start with a Pilot to Prove Effectiveness
Don’t immediately request full plant deployment. Propose a limited pilot: one machine, one line, one shop. This restricted scope limits initial investment and reduces perceived risk. Management that refuses a €100,000 project may accept a €5,000 test.
The pilot produces concrete results in your specific context. This local data is worth more than all external references for demonstrating possible improvement.
Find Sponsors and Show Results
A project carried by a single production manager struggles to pass validation stages. Identify allies: quality director concerned with scrap, maintenance manager interested in failure anticipation, supply chain director impacted by capacity variability. These sponsors broaden the base of support.
From the first weeks of the pilot, share results with decision-makers. A detected and quickly resolved stoppage, identified root cause analysis, an operator’s testimony: these concrete stories maintain support and prepare expansion.
Conclusion: Persistence and Method
Gaining skeptical management’s buy-in requires time, method, and resilience. Initial refusals are not final. Each discussion refines your argument, each addressed objection strengthens your case.
The key lies in combining a rigorous business case with a progressive approach. Start small, prove quickly, expand later. This strategy minimizes perceived risk while maximizing success chances. Your conviction about OEE’s value is founded. It remains to transform this conviction into decision with patience and determination.
FAQ: Frequently Asked Questions About OEE Project Buy-In
How long does it take to get OEE project validation?
The timeline varies by organization. In an SME with a ground-level leadership, a few weeks may suffice. In a large corporation with formalized budget processes, expect three to six months. A pilot with low investment generally gets approved faster.
Should IT be involved from the beginning?
Yes. IT can block a project if they discover network or security implications late. Involving them upfront transforms them into allies. Their legitimate concerns about databases and integration deserve to be incorporated into the specifications.
How to react if the pilot doesn’t deliver 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 investment or operating budget?
Both options have advantages. Investment suits equipment purchases with depreciation. Operating expense avoids heavy CAPEX approval processes. Choose based on your company’s practices and available envelopes.
0 Comments