You are convinced that OEE monitoring would transform your production. Your field teams need it. But your management is hesitant, putting it off, asking for more justification. This scenario is repeated in hundreds of production plants every year. The value of an overall equipment effectiveness project seems obvious to those who experience the production process on a daily basis, but much less so to those who decide on 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
The "We've Already Tried That" Syndrome
Many industrial companies have experienced failures with digitization projects. A manufacturing execution system that was never adopted, an ERP system that was deployed with great difficulty, Excel dashboards that were abandoned. These experiences leave their mark. When you propose an OEE project, your management sometimes hears "yet another tool that no one will use."
This mistrust reflects past investments that did not 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, and rapid results in terms of yield: these elements reassure a management team that has been burned by the productivity losses of previous projects.
The Difficulty of Quantifying Performance Gains
A CFO thinks in terms of numbers. When you talk to them about continuous improvement and visibility on the ground, they mentally translate this into "costs without measurable returns." The vocabulary of production and finance do not naturally overlap.
OEE remains an abstract concept for those who have never set foot in a workshop. Gaining 5 points on this performance indicator means nothing without translating it into euros or additional capacity. Your argument must overcome 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
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 you today? Estimate the time lost searching for data, undetected production stoppages that drag on, and decisions made on gut feeling due to a lack of reliable key performance indicators.
Take a typical week and calculate the losses: hours of unplanned downtime multiplied by the hourly cost of the machine, avoidable scrap, and series changes that exceed 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 a usable database.
Calculate ROI with Performance Indicators
There is a temptation to inflate profit forecasts. Resist this temptation. Experienced management will detect optimistic assumptions. Opt for a conservative calculation based on modest gains: 2 to 3 points of OEE 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 operating time and cycle time of your production machines. Also include the reduction in maintenance costs thanks to better anticipation of breakdowns. This rigor will strengthen your credibility for the budget planning phase.
Responding to Objections: Improving Efficiency
"It's Too Expensive": Demonstrate the Quality of the ROI
This objection often reveals a lack of knowledge about current solutions. OEE projects ten years ago required heavy investment. 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 it to the price of one hour of machine downtime. Break down the investment to the cost per machine per month. The employee training included in these offers accelerates adoption and ensures the quality of the deployment.
"Our Operators Won't Use It": The Issue of Buy-in
This legitimate concern deserves a serious response. The difference with a well-executed OEE project lies in the involvement of operators from the design stage and the immediate value they derive from it in their daily 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 monitors them. The speed of adoption depends on this initial positioning. Cite examples of factories where operators themselves are asking for it to be installed on machines that are not yet equipped.
"We Don't Have Time": Planning a Quick Pilot
Lack of time often reflects a fear of the deployment burden. A modern OEE project can be deployed in days, not quarters. This difference in timeframe changes the nature of the objection and makes planning easier.
Propose a pilot on one or two machines, deployable in a day, with visible results within two weeks. This minimalist approach does not overload anyone and quickly produces evidence of value across all the equipment concerned.
Strategies to Accelerate Decision Making
Start with a Pilot to Prove Effectiveness
Don't ask for a full factory deployment right away. Propose a limited pilot: one machine, one line, one workshop. This limited scope reduces the initial investment and lowers the perceived risk. A management team 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 more valuable than any external references in demonstrating the potential improvement.
Find Sponsors and Show Results
A project led by a single production manager will struggle to get through the validation stages. Identify allies: the quality manager concerned with scrap, the maintenance manager interested in anticipating breakdowns, the supply chain manager impacted by capacity fluctuations. These sponsors will broaden the support base.
From the first weeks of the pilot, share the results with decision-makers. A shutdown detected and resolved quickly, an analysis of the causes identified, an operator who testifies: these concrete stories maintain support and prepare for expansion.
Conclusion: Perseverance and Method
Gaining the support of a skeptical management team takes time, method, and resilience. Initial refusals are not final. Each exchange refines your argument, and each objection addressed strengthens your case.
The key lies in combining a rigorous business case with a gradual approach. Start small, prove yourself quickly, then expand. 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 turn that belief into a decision with patience and determination.
FAQ: Frequently Asked Questions about Joining OEE Projects
How long does it take to get an OEE project approved?
The timeframe varies depending on the organization. In an SME with a hands-on manager, a few weeks may be enough. In a large group with formalized budget processes, allow three to six months. A low-investment pilot project 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 at a late stage. Involving them early on turns them into an ally. Their legitimate concerns about the database and integration deserve to be included in the specifications.
How should you respond if the pilot does not deliver the expected results?
Honestly analyze the causes before communicating. A disappointing pilot may reveal a problem with scope or training rather than a weakness in the solution. Correct what can be corrected and present the lessons learned transparently.
Is it better to request an investment or operating budget?
Both options have their advantages. Investment is suitable for equipment purchases with depreciation. Operating expenses avoid cumbersome CAPEX validation processes. Choose according to your company's practices and available budgets.
0 Comments