How to use OEE waterfall reports to add value to food manufacturing operations

Ask production staff how well the morning run has gone and the conversation could go one of several ways.  “It was OK, we managed to get the order out” or “It was terrible, everything that could go wrong went wrong”.  Neither is particularly helpful to the maintenance or continuous improvement teams trying to get to the facts to assess what really needs to be done.

The OK comment could easily be hiding a multitude of problems – we may have managed to meet the order demand, but at what cost?  We remember talking to one first-line manager who felt the first six hours of the shift had been OK but had not realised 90 minutes had been lost through a variety of speed losses and stoppages. 90 minutes lost in six hours is probably not 'OK' by most measures.

The “everything went wrong” comment is probably worse, “it’s making a funny noise” doesn’t really help the maintenance team when they arrive, especially when the noise has already stopped.

Step forward, the "OEE Waterfall" technique. When the technique is applied to OEE it becomes a consistent and user-friendly way of showing the real impact of production performance.  A waterfall might appear to be an unusual model on which to base an OEE production report but when the object of the exercise is to reduce wasted time in the production process it’s a good way to visualise how well, or how badly, things are working.


The OEE waterfall graph for a food manufacturer

The OEE Waterfall graph shows one day of production.

Plan - our production aspiration, the time we intend to run the plant to fulfil the order demand, they are planning to run for 18 hours per day.

Mechanical/electrical. Downtime associated with mechanical or electrical faults.

Operational issues. Downtime such as slow running machinery,

Planned – Planned downtime has been scheduled in and would cover off product changeovers, breaks etc.

Short stoppages – Short stops - these can be particularly damaging for OEE.

Variance to standard – Poor product quality.

Waiting for internal – Waiting for internal resources, this will drill down to labour, ingredients etc.

Added value – ‘Added Value’ the true point of the exercise, our production aspiration was 18 hours but we managed to add value to the business for just 9.5 hours.


Baseline captured, time to improve.

Once that baseline of Added Value is generated, in the above example 10 hours, we can continue to capture accurate data and create an improvement culture.

Publish the results. Many customers chose to highlight KPIs on large TVs in the canteen so everyone can see the improvements made.


Techniques to improve.

  1. Agree to a blame amnesty; it’s not about fault it’s about resolution

  2. Create a top 5 or top 10 loss wall in the CI campaign room

  3. Take a series of photographs of the loss to be improved

  4. Take a photograph of the person accountable for that improvement

  5. Show the position of that loss by generating a graph of top 5 or top 10 losses

  6. Generate a graph for the specific loss over time, usually thirteen weeks

  7. Document an improvement plan of action to resolve the issue

  8. Record progress and meet weekly to monitor resolution

  9. React to a lack of progress and provide additional support to the person accountable as required

  10. Don’t change direction when things get tough, or change the system

  11. Just keep remembering the effect of a low ‘added value’ score. In the illustration above the factory has funded the assets, labour, materials and energy costs to the tune of 18 hours per day but has only gained 9.5 hours of effective production output, fit for sale, in return. It’s sobering to consider that virtually every improvement that increases that value of 9.5 hours either reduces the loss or goes straight to the bottom line as profit.


Previous
Previous

Checklist for robotic transformation

Next
Next

Do I need a thick or thin client solution for autocoding?