OEE Displays and Software for Continuous Improvement of Factory Performance

OEE displays and software measure production rate, downtime, total produced and total rejected. They give a real-time indication of your lean manufacturing production line performance to help you achieve continuous improvement in your processes.

The beauty of a real-time OEE system is that you can respond immediately to any drop in performance before it becomes critical.



Our OEE software and display systems are available in a wide range of formats to suit your installation's maximum required viewing distance and can accept data in a type which best suits you, such as pulse counts, barcode scanner, manual input, csv, database query etc.

Below is a diagram showing the main components and stages of a simple OEE display system for factory performance monitoring...







Our OEE systems are modular, so we can combine as many values on the display or in the software as you would need. For example, the simplest version could show OEE, but you could additionally show Current Rate, Average rate this shift, total downtime, Quality %, Takt time, Text messages etc.

Shown below is a typical OEE software example of an Operator's screen showing real time graph of OEE versus target, with Gantt chart of all stoppages, calls for help, engineer attendance and response times etc...

New: Ex nR Atex OEE displays

How do I calculate OEE?

OEE is calculated in the display itself or in the software. If your display is a self-contained OEE version, you simply connect power and pulse inputs for total made and total rejected. You will also need to tell the display how many items your production line can produce in an hour, when operating at its peak of performance.

The pulse signals can come from NPN or PNP sensors, PLC outputs etc.

If you are using our OEE Software, the measured OEE value can be saved to a cloud-based database for viewing on your laptop, PC or phone, thanks to the latest in IoT secure technology.

Trend graphing allows you to instantly see whether performance is improving or not, and for which KPIs. The three core KPI's we look at when determining OEE are Availability, Speed Performance and Quality.

OEE = Availability x Speed x Quality

• Availability: This is the percentage of time the production line has been operational, over the chosen analysis period.
• Speed: This is the number of items produced, as a precentage of what the line would have produced ideally, over the chosen analysis period
• Quality: This is the percentage of good items produced, from the total of all items produced, over the chosen analysis period

If Availability, Speed and Quality are all 100%, OEE is 100%, because 100% of 100% is 100%. I all are 50%, the OEE is 12.5% because 50% of 50% is 25%, and 50% of 25% is 12.5%

OEE can be highly sensitive to small drops in performance in each of the 3 key measurements.

For example if your Availability, Speed and Quality were all at 80%, your OEE would drop dramatically to 51%

And if your Availability, Speed and Quality were to drop to 50%, your OEE would drop even more dramatically to under 13%

So to maintain a high OEE, you must be vigilant to any small drops in all your KPIs, Availability, Speed or Quality.

OEE needs to be treated with caution though, as it is not ideal and doesn't suit all processes equally, especially if there is a large mismatch between A P and Q. Ideally A P and Q would have similar values, in a well balanced and defined production system.

OEE can provide an unfair overall picture, if one or two of the variable are consistently poor, yet the remaining perform well. The reason for this is that the availability may be perfect, but speed and quality very poor, which penalises the apparent rating for availability, and may not give enough focus on the real problem areas, when only OEE is viewed..

Similarly, a very high speed, above 100% of rated operation, can give rise to lower quality than a lower speed, due to operator errors, machine jams etc, and the overall profit could be less than for the same OEE at a lower speed.

Examples of a basic OEE software report

We also collect the following useful information:

• Reasons for downtime, selected from a user-defined library
• Downtime per reason
• Engineer's response speed to call for help
• Engineer's time to resolve
• Average time to resolve each downtime reason

An example of a production software screen we designed for use on an Android or iPhone device.



OEE Display and Software system information leaflet