Posts Tagged ‘OEE’
Visibility in Manufacturing
Posted by gdalleave in Machine Truth Blog Tuesday, 9 August 2011 14:06 1 Comment
Manufacturing Leaders are asked to meet strategic goals set by corporate leaders. These goals are often stated in financial terms concerning cost control and margin increase. To accomplish this, Manufacturing Leaders initiate numerous programs to keep the cost of goods under control and improve production efficiency. Often times their methods involve gathering production data from the plant floor and manually inputting the data into an Enterprise Resource Planning (ERP) system or Excel spreadsheets. Manufacturing Leaders keep track of factors such as total downtime, downtime reasons, setup time, run speeds, and Overall Equipment Effectiveness (OEE), among others. This data is then used to determine where to invest continuous improvement dollars.
And you know what. It works…well, kind of.
Manufacturing Leaders are finding that they cannot get the anticipated return on their continuous improvement investment since some programs work, while others miss the mark altogether. It is a drunken walk. You may get where you want to go, but it takes a very long time and you fall down more than once. Often times you never make it. Unfortunately, this means that the task is then left to a new Manufacturing Leader. What is needed is a way to get to where you need to be as quickly and efficiently as possible.
To analyze where the problem is, we need to step back to the driving strategy. To improve their competitive position, corporate leaders often define strategic goals such as improving return on capital deployed or improving margins. A positive change in these types of financial measures often indicates that a company is managing its business well. If margins continually rise then profits go up, stock prices rise, and shareholder wealth is created.
Once the corporate strategy is in place, it becomes the Manufacturing Leader’s responsibility to manage their performance in a manner that results in meeting the strategic goal. For example, if the goal is to increase margins, the Manufacturing Leader will look at ways to keep costs per unit under control and decrease them over time. This can be done by reducing the costs of raw materials, labour and energy. This brings us back to our previous discussion: Manufacturing Leaders need to look for the right places to invest their continuous improvement dollars, in order to achieve these strategic goals.

Leaders need to take effective action. Unfortunately, it is not completely clear what that effective action is. Their recourse is to fall back to rules of thumb or groping around in the dark. It becomes ‘hit’ or ‘miss’. The hope is to ‘hit’ more often than not; there has to be a better way.
In talking with manufacturers and looking at leading industry research, the inability to make the best investment decisions comes from a lack of visibility to the plant floor. Manufacturing Leaders understand the strategic goal but cannot see into the plant floor to take effective action. The plant is a ‘black box’, raw material, energy and labour go in, finished goods and scrap come out.
Collecting data manually and inputting it into ERP systems, Business Intelligence (BI) tools or spreadsheets is one attempt at seeing into the ‘black box’. Unfortunately the data results are is Aggregated, Inaccurate and Lagging; we call it “AILing,” as in “to cause pain”, “uneasiness”, or “feeling unwell.”

Aggregated data is a problem because the Manufacturing Leader cannot view details of what is actually happening. For example, the Manufacturing Leader may know exactly how much product his plants are producing and exactly how much money, in terms of raw material, labour, and energy, is being used, but that is all he knows. He cannot break it down any further, or determine the contribution to unit costs by shift, asset, product or operator. Manufacturing Leaders have the data but they lack the visibility to determine what the corrective course of action is to impact their key metrics.
Inaccurate data is a direct result of the data gathering process. Manually collected data cannot possibly be correct. Besides the normal input errors, manually collected data suffers from an immediacy problem, since when an operator is asked to log reasons for downtime and the time taken to resolve them; the data is often entered in at the end of the shift. This is due to the immediate problem of having a stopped machine super ceding the need to collect data accurately. The operator, rightly, needs to get the machine up and running as quickly as possible – accurate data be damned. The end result is that continuous improvement programs are using inaccurate data to determine where to invest in order to meet strategic objectives. Unfortunately, inaccurate data means investment decisions in the wrong programs, causing the return on the manufacturer’s investment to suffer. We call this chasing Continuous Improvement Ghosts.
Lagging data is money poured down the drain. Even if the data is accurate, by the time the Manufacturing Leader sees the data, it is too late to do anything about the problem. The money has been lost, swept away at the end of the day. What is needed is a way to get the right data into the hands of Manufacturing Leaders and their staff in real-time, to correct a problem as it is happening. If you are waiting for the end of the shift, the end of the day, the end of the week or heaven forbid, the end of the month; it is too late. The money is lost.

In order to meet the financial strategic goals established by the corporation, Manufacturing Leaders need the right visibility to determine what the effective action needs to be. The key to this, is having visibility directly into the plant through accurate, real-time, high resolution information. Manufacturing Leaders need to see into the ‘black box,’ that is their plants, and shine a light directly on the problem areas to eliminate them.
![]()
![]() |
George Dalle AveGeorge Dalle Ave is the Director of Solutions Development at Shoplogix Inc. |
|---|
Fareva rolls out Shoplogix™ Plantnode® across its contract packaging operations
In the competitive world of contract manufacturing, reducing costs, improving efficiencies and maintaining margins is essential. Leading European contract cosmetic and pharmaceutical manufacturer, Fareva, is committed to improving productivity at its operations with a Continuous Improvement program supported by Shoplogix™ Performance Management Solution Plantnode®. “There’s more and more pressure from our customers to cut costs, decrease the lead time and improve the service level,” says Marc Spiniella, Fareva’s Continuous Improvement and Methods Director. “If we want to lower costs, we really need to be extremely efficient in our manufacturing. You cannot improve performance if you don’t measure it.”
That’s where Plantnode comes in. The Plantnode Performance Suite provides manufacturers with an accurate, uniform and automated source of plant level performance data which is critical to strategic and operational decision making. At Fareva, Plantnode is being used to measure run speed, downtime, OEE, scraps helping to uncover opportunities for improvement. “This project is an important step for Fareva in our goal to achieve ‘industrial excellence’,” says Spiniella.
ABOUT FAREVA
Fareva is a high-volume contract manufacturer in cosmetics, pharmaceuticals and household goods. The family-owned business, which employs 5,000 people at 27 plants in Europe and around the world, offers customers impeccable service by providing tailored R&D, production and packaging facilities. Fareva has more than 800 customers worldwide. For more information about Fareva, visit the company’s web site at www.fareva.com.
shopTALK – Episode #2: OEE for Continuous Improvement
Posted by admin in Machine Truth Blog Thursday, 24 February 2011 19:54 No Comments

|
QUESTION: How do you use OEE as a measurement for Continuous Improvement? ANSWER: A lot of people are using OEE, overall equipment effectiveness is what it stands for. However, you can calculate it without having a tool like Plantnode, you can take just the total number of units that have been produced, divide it by the amount of time you’re planning to run and the expected rate the machine should be running at so you can get an OEE number. Though, it’s really a target, it’s something that you’re trying to hit, and it’s a percentage, a percentage of the expected time you were supposed to be running, and a percentage of the run speed rate that you’ve entered. After all that’s been calculated the real benefit of OEE is to understand who can I make my OEE better? How can I improve? Ultimately OEE is an efficiency measure it’s a way to measure how am I doing against where I expect to be, our best customers actually move the bar frequently throughout their lifecycle of adoption of OEE so today they might be at 95% OEE and they might change the expected rate to be higher than what it is today so their OEE drops the next day their 75%. So the OEE of “World Class 85%” or whatever the world class happens to be for your industry is merely a measurement point it’s not an end goal. You can improve and improve on where you are, you can always get better, and the way you get better is by making your standards harder and harder to achieve. What a lot of our customers that use OEE really like about the Plantnode tool is that it provides more information and a breakdown of where your losses are coming from. OEE as a number is really not that meaningful unless you understand the elements that make it up. There are those three elements of: Availability – which is your uptime percentage, your Performance – which is your run speed as a percentage of the target you are trying to hit. And your Quality ratio – Which is your good product divided by the total product, or a measure of scrap or first pass at yield. What’s interesting is, when you look at the individual components: they are mutually exclusive and collectively exhaustive, you can’t hide one really good result with another really poor one, or cover up a poor result with a really good one because the OEE will still be reflected when you multiply the two. Based on our customers experience using OEE, the value that they get out of our tool is that they’re able to use it to diagnose why their OEE gets low or why their OEE is where it is currently, they can also universally apply that same standard across all their plants in their entire enterprise. So we can help them diagnose the issue: if the OEE is low, is it because of a run speed problem?, is it because you have a lot of downtime?, and if it is downtime, what’s the reason for the downtime?, is it shortstops?, is it changeovers? Is it other unexpected maintenance problems you weren’t planning on happening? Those types of things are what really makes OEE useful is once you understand what the components are that are causing your OEE to not be what you want it to be. |
|---|
![]()
![]() |
|
Michael Dedrick
|
|---|

