<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yves Bourgeois on Medium]]></title>
        <description><![CDATA[Stories by Yves Bourgeois on Medium]]></description>
        <link>https://medium.com/@bourgey?source=rss-cf508f68a5a0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*77FPNmSesW2VQqASdJHyLg.jpeg</url>
            <title>Stories by Yves Bourgeois on Medium</title>
            <link>https://medium.com/@bourgey?source=rss-cf508f68a5a0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:35:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bourgey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Moving beyond theory: 3 practical cases for OEE]]></title>
            <link>https://medium.com/factry/moving-beyond-theory-3-practical-cases-for-oee-ef577a13c7cf?source=rss-cf508f68a5a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef577a13c7cf</guid>
            <category><![CDATA[oee]]></category>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <dc:creator><![CDATA[Yves Bourgeois]]></dc:creator>
            <pubDate>Wed, 25 Mar 2020 08:00:00 GMT</pubDate>
            <atom:updated>2020-04-08T09:36:45.200Z</atom:updated>
            <content:encoded><![CDATA[<p>OEE is not a new concept. Its origin dates back all the way to the nineteen-eighties, the decade of economic growth and relocation of manufacturing to the East (and of course the decade of Pac-man). OEE was first described -as a central component of the TPM methodology- in Seiichi Nakajima’s book ‘TPM tenkai’. Not accidently in Japan, given the expansion of the economy, manufacturing boom and need for increased output.</p><h3>Mid-life crisis</h3><p>A concept of 40 years old and well-established practice should have inspired an abundance of practical case studies, you might think. Well, unfortunately, the internet is not exactly the treasure chest for the case study raider. Before we partially solve that predicament, let’s make sure we are on the same page conceptually.</p><p>OEE doesn’t need a lot of defining, because it is so well known. So just as a brief recap: OEE is a measure of how well a manufacturing process is utilized, compared to its full potential when it is scheduled to be used. An OEE of 100% means that only good parts are produced (100% <strong>Quality</strong>), at the maximum speed (100% <strong>Performance</strong>), and without interruption (100% <strong>Availability</strong>).</p><p>When it comes to OEE, the devil is in the detail. Not just in the calculation of the OEE, but in the explanatory value as well. If you know that a production line has a 80% <strong>Availability</strong>, that’s one thing. If your OEE calculations teach you that is because of a specific machine with intermittent drops in <strong>Availability</strong>, that’s a different story.</p><p>Imagine it would even teach you which part of that machine is causing the downtime. OEE shifts from an informational metric to an operational metric, but it is all based on real-time analysis and enormous detail.</p><h3>Marketing has a request</h3><p>Let’s consider for a moment a contemporary situation in a dairy processing company. Operators and plant managers are scrambling to get the current production at an OEE of 85%. Then, along comes the marketing department with the request to label a batch with a promotional message. In a heavily customer-centric company the mandate for production management to refuse such a request is thin. However, their arguments may be very legitimate.</p><blockquote><em>Production faces an invisible cost of such requests, whereas marketing will peacock charts of rising sales. It’s like bringing a knife to a gun fight.</em></blockquote><p>So with the right level of detail about the <strong>Availability</strong> and <strong>Performance</strong> of a specific line and its equipment, production management is now able to evaluate the marketing request with hard figures. Imagine that the required labelling machine has an unavailability of 20%, it is quite easy to calculate the cost for a line that has 4.000 units of output every hour. If their analysis would show that the cost of such a request is higher than the ‘expected’ returns, it is not a matter of customer centricity, but stakeholder thinking that the request is refused.</p><p>OEE can balance out the power shifts that are taking place in many customer-centric companies.</p><h3>Operators are invisible — sometimes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u7opQ4f3y0x9-lel.jpg" /></figure><p>Another example is a weaving company. Every production change, operators are required to tie 1.800 knots on every machine. This technical process has a high cost: it’s labor intense and vulnerable for human errors. By setting up an OEE automation process, the company would become able to calculate the cost of every operator on a machine. They would not only finally have hard metrics about the <strong>Quality</strong>, but also the <strong>Availability</strong>.</p><p>Of specific interest here is the inter-operator variable. Are there people in need of additional training or supervision? Is there a difference between daytime and nighttime operations? How come? And what would be an approach to close that gap. This is a clear example of the benefit of a bottom-up OEE calculation. It contains a lot of details that can be leveraged for operational decisions.</p><h3>How one number can cost you</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8iDYop02HqO-2-YN.jpg" /></figure><p>A Belgian company is producing beer (duh!) and packaging in six-packs, but also eight-packs. Due to some arbitrary decisions, it produces like this: 6,8,6 in 24 hours, meaning that the packaging machine setup needs to be changed two times in this sequence. There is no need to change this cycle as it is unclear what the cost is of this sequentialism. OEE would clearly measure the cost of the downtime between batches.</p><p>Although people have an underpinning gut feeling for this type of cost, it is much better to base these decisions on hard facts since our intuition can be completely off.</p><p>Take this for an example: a yoghurt producing company had a machine that went intermittently down for just 20 seconds, a so-called microstop. Since it did not have a high impact on production — according to the gut feeling of the involved — they let it be. OEE calculations however, showed that the machine was down, for no less than 20 minutes a day, with a cost high above what was deemed acceptable. The problem was raised to the manufacturer who then claimed it was a known problem that could easily be fixed.</p><blockquote><em>It’s like a leaking faucet: it seems like no big deal but spills a thousand liters.</em></blockquote><h3>In conclusion</h3><p>OEE is a well-known but underutilized metric. If you’re stuck in manual calculations, top-down high-level measuring and simple trends and benchmarks, you are clearly not reaping all the benefits of OEE.</p><p>With the current technology and automation capabilities, the concept can thrive forty years after its conception. It will serve not just as an informational metric, but as an operational tool to further optimize a production environment, which is of specific importance to European companies faced with high costs.</p><p>In our next article we will outline how to implement an automated OEE and leverage it as an operational decision making tool.</p><p><em>Originally published at </em><a href="https://www.factry.io/blog/oee-moving-beyond-theory/"><em>https://www.factry.io</em></a><em> on March 25, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef577a13c7cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/factry/moving-beyond-theory-3-practical-cases-for-oee-ef577a13c7cf">Moving beyond theory: 3 practical cases for OEE</a> was originally published in <a href="https://medium.com/factry">Factry</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Recurring Benefits of the Process Historian]]></title>
            <link>https://medium.com/factry/five-recurring-benefits-of-the-process-historian-7a0c0ec527fd?source=rss-cf508f68a5a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a0c0ec527fd</guid>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[industry]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <category><![CDATA[historians]]></category>
            <dc:creator><![CDATA[Yves Bourgeois]]></dc:creator>
            <pubDate>Sun, 04 Nov 2018 15:00:00 GMT</pubDate>
            <atom:updated>2019-12-13T12:38:12.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uB0kbUNaNRNp0rDqKAb-g.jpeg" /></figure><p>In a previous article, <a href="https://www.factry.io/blog/process-historian-for-small-businesses/">Process Historian for Small Businesses</a>, we have talked about the disruption that is occurring in industry, where the use of open technologies and open source, is extending the tool belt of every production manager and plant engineer. Using new technologies, we can provide a Process Historian that was previously only affordable for large companies in captital-intensive sectors — such as Oil and Gas, and the Pharmaceutical industry.</p><p>However, a Process Historian is still an investment, of both time and money, that requires a clear and thorough evaluation of its value, to answer the important question:</p><blockquote><em>“What will we gain using a historian?”</em></blockquote><p>To evaluate its value, one needs to be aware that the implementation of a historian happens in two distinct phases. First, the historian is introduced as a solution. In this phase, data acquisition, instrumentation, and trending are the focus. Second, the Process Historian will become a technology, a platform if you will, in which the acquired data itself becomes a source for advanced Data Analytics and Data Science purposes. Both phases bring merit to any company in industry and both have their distinct added values.</p><p>In this article, we focus on the virtues of a Process Historian by introducing it as a solution — data acquisition, instrumentation, and trending. But first, let us take a step back, and have a look at what you already have: SCADA and DCS systems.</p><p>Most companies in process and discrete manufacturing have already invested in either SCADA or DCS systems, according to their specific needs. These level 0–2 systems provide adequate real-time monitoring of the production process, and guide the operator in making the correct decisions in case of alarms or fault-states during the production process. Both SCADA and DCS systems even provide an, albeit limited, ability for trending of historical data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sQJ3R9Bv2r_JKRUF.png" /><figcaption>The Industry Automation Pyramid</figcaption></figure><p>However, both control systems also come with severe limitations in regard to data analysis. They only provide a limited amount of historical data, if any, and they are limited to their particular data silo: it is only possible to examine the data for which these systems are responsible, say a single production line, without providing an aggregated overview of the entire plant. Furthermore, these systems are inescapably locked in their proprietary software model, which makes it very hard, if not impossible, to perform data analysis on the restricted data, in both scope and accessibility, that is contained within them.</p><p>The Process Historian, on the other hand, operates on level 3 of the Industry Automation pyramid. It aggregates the data of the entire plant — over all production lines — and it keeps this data available for as long as needed, if not forever. Factry Historian in particular makes the collected data free as in speech, by putting no limitations in making this data available for other software to consume. It creates a perfect link between Operation Technology and Information Technology, in which production savvy people will be able to use the technological infrastructure to analyze the actual production process.</p><p>Now, let’s have a look at five of the most important benefits a Process Historian can bring you, when introduced as a solution.</p><h3>Single Source of Truth</h3><p>Acquired data from sensors (such as temperatures, pressures, etc.) can be linked to contextual data, e.g. the start and end time of an order or a specific batch produced. This will allow you, with the click of a button, to visualize the specific circumstances of the production process.</p><p>This not only saves time for operations and quality managers to find the data they are looking for, which is already a direct cost reduction. It will also keep the focus of said users on the problem at hand, as it gives them the confidence that all the necessary data is precise — for it is automatically acquired -, and no data is overlooked. This allows them to make informed decisions based on facts, and not on presumptions.</p><h3>Continuous Improvement of Quality</h3><p>The Process Historian, as already hinted at, is also a tool that is of importance for quality managers within each plant. When quality issues occur, the Process Historian will allow for a thorough examination of the exact conditions in which a certain batch — or order — was produced. As such, it will be possible to either indicate or exclude whether the production process was the reason for any quality issues. The first will then allow for a better training and education of the operators, and to prevent such quality issues in the future, which will have a direct impact on the yield of production.</p><p>Being able to quantify exact problems in the production process provides a basis for the Continuous Improvement of said production process, as different parameters of the production process can be measured and fine-tuned to maximize the quality of the product. This has a direct impact on the overall productivity of the plant and reduces costs directly by avoiding production blunders in the future.</p><h3>Less Unplanned Downtime through Anomaly Detection</h3><p>Having all sensory data available will also enable you to detect anomalies during the production process, anomalies which would otherwise go undetected. Anomaly detection could be used to discover e.g. leaks or unexpected temperatures, as quickly as possible. This will limit the cost of both damage and repair to a bare minimum. Anomaly detection can occur either manually, by having the trends show the user what exactly is happening — and alarms defined for automatic alerting, or it can occur automatically, through the historian software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/0*IiRj9OAPYPwLIL9G.jpg" /><figcaption>Simple anomaly</figcaption></figure><p>At Factry, we already saw the benefits of anomaly detection at one of our clients: they pinpointed a previously undiscovered leak, which ultimately saved them tens of thousands of euros in unplanned downtime and damages. And this already in the second week our Process Historian was active!</p><h3>Improved Predictive Maintenance</h3><p>The Process Historian will not only capture the amount of product that has run through your flow-meter, but it will also show exactly how long your pump has been pumping product, or how long a generator has been running. This gives you precise information which can in turn be used to schedule predictive maintenance, and send preemptive warning messages to the responsible people when certain thresholds are bound to be exceeded.</p><p>The importance of predictive maintenance has been examined by the <a href="http://www3.weforum.org/docs/WEFUSA_IndustrialInternet_Report2015.pdf">World Economic Forum and Accenture</a>, and the results are staggering: using predictive maintenance, the cost of scheduled maintenance is, on average, reduced by 12%, while the total cost of maintenance is reduced by 30%. But most importantly, predictive maintenance eliminated <strong>70%</strong> of unplanned downtime. As plant downtime is immensely costly, it is clear that predictive maintenance is a must.</p><h3>Energy Consumption Improvement Projects</h3><p>The Process Historian should not be limited to production data — i.e. sensory data, such as temperatures, pressures, etc.-, but can also capture data that is indirectly related to the production process, such as energy consumption. As energy consumption has become one of the primary costs in the production industry — next to the cost of labour and of raw materials-, having exact data about energy consumption for each part of the production line has become a need by itself, be it in kWh or volume of fuel spent.</p><p>The Process Historian provides you with just that: awareness of where the big consumers of energy are, by exact monitoring. It offers the possibility to use these figures to set up energy-saving projects and influence the bottom line of the business directly.</p><p>In this article, we outlined five benefits that the Process Historian can offer you on day one when it is introduced as a solution. It provides you with the necessary toolkit to instrumentalize all data that is available in the plant. By doing so, you will be able to use this data to make informed, empirical decisions on a variety of problem cases, and even use it in Continuous Improvement projects, be it quality or energy related. This will ultimately reflect in an improvement of different facets of the production process, such as cost reduction, yield improvement and minimizing unplanned downtime.</p><p><em>Originally published at </em><a href="https://www.factry.io/blog/recurring-value-of-process-historian/"><em>https://www.factry.io</em></a><em> on November 4, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a0c0ec527fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/factry/five-recurring-benefits-of-the-process-historian-7a0c0ec527fd">Five Recurring Benefits of the Process Historian</a> was originally published in <a href="https://medium.com/factry">Factry</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>