You are convinced that OEE tracking would transform your production. Your floor teams need it. But your leadership hesitates, postpones, asks for further justification. This scenario repeats itself in hundreds of manufacturing plants each year. The value of a global equipment effectiveness project seems obvious to those who live the production process daily, far less so to those who arbitrate budgets. In this article, we share concrete strategies to build a solid case and get the green light from skeptical decision-makers.
Why Leadership 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 with difficulty, Excel dashboards abandoned. These experiences leave marks. When you propose an OEE project, your leadership sometimes hears “yet another tool no one will use.”
This distrust reflects past investments that failed to deliver on their promises. Your job is to demonstrate how this project differs. The simplicity of deployment, operator involvement from the start, quick results on TRS: these elements reassure leadership burned by productivity losses from previous projects.
The Difficulty in Quantifying Performance Gains
A CFO reasons in numbers. When you talk about continuous improvement and floor visibility, they mentally translate it as “cost without measurable return.” The vocabulary of production and finance don’t naturally overlap.
TRS remains an abstract concept for those who’ve never set foot in a workshop. Gaining 5 points on this performance indicator means nothing without translation into euros or additional capacity. Your pitch 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
Quantify Losses Related to Production Downtime
Before talking about gains, talk about losses. How much does the lack of visibility on your production line cost today? Estimate time lost searching for data, undetected production shutdowns that drag on, decisions made on a whim due to lack of reliable key performance indicators.
Take a typical one-week period and reconstruct the losses: hours of unplanned downtime multiplied by the hourly machine cost, avoidable scrap, changeovers that exceed standards. This work produces concrete numbers. 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.
Calculate ROI with Performance Indicators
The temptation exists to inflate gain forecasts. Resist it. An experienced leadership team detects optimistic assumptions. Prefer a conservative calculation based on modest gains: 2 to 3 TRS points in year one rather than the 10 points sometimes announced.
Document each assumption about equipment efficiency. Cite sector references or feedback from comparable sites. Show the impact on runtime 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: Efficiency Improvements
“It’s Too Expensive”: Demonstrating Strong ROI
This objection often reveals unfamiliarity with 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 the actual cost structure. Compare against the price of one hour of machine downtime. Calculate the investment per machine per month. Employee training included in these offerings accelerates adoption and ensures deployment quality.
“Our Operators Won’t Use It”: The Adoption Question
This legitimate concern deserves a serious answer. The difference with a well-executed OEE project lies in operator involvement from design and in the immediate value they gain for their daily efficiency.
Propose involving a few pilot operators in the 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 request installation on unequipped machines.
“We Don’t Have Time”: Planning a Fast Pilot
Lack of time often reflects fear of deployment burden. 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 equipment involved.
Strategies to Accelerate the Decision
Start with a Pilot to Prove Efficiency
Don’t immediately ask for full plant deployment. Propose a limited pilot: one machine, one line, one workshop. This restricted scope limits initial investment and reduces perceived risk. Leadership 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 any 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 about scrap, maintenance manager interested in failure anticipation, supply chain director impacted by capacity uncertainty. These sponsors broaden the support base.
From the first weeks of the pilot, share results with decision-makers. A detected and quickly resolved shutdown, identified root cause analysis, an operator’s testimony: these concrete stories maintain support and prepare for expansion.
Conclusion: Perseverance and Method
Securing a skeptical leadership’s buy-in takes time, method, and resilience. Initial refusals aren’t permanent. Each conversation refines your pitch, each addressed objection strengthens your case.
The key lies in combining a rigorous business case with a progressive approach. Start small, prove quickly, expand next. This strategy minimizes perceived risk while maximizing success chances. Your conviction about OEE’s value is sound. Now transform that conviction into a decision with patience and determination.
FAQ: Frequently Asked Questions About OEE Project Buy-In
How long does it take to get OEE project approval?
The timeline varies by organization. In an SME with a leader close to operations, a few weeks may suffice. In a large corporation with formalized budget processes, expect three to six months. A pilot with modest investment is generally approved faster.
Should IT be involved from the beginning?
Yes. IT can block a project if they discover network or security implications too late. Involving them upfront transforms them into an ally. Their legitimate concerns about databases and integration deserve to be built 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 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 hardware purchases with depreciation. Operating budget avoids heavy CAPEX approval processes. Choose based on your company’s practices and available envelopes.
0 Comments