Accuracy of OEE calculation

Patrick Sherwood

• June 09, 2025 20:19

Availability = Uptime / Planned Time

As far as I can see L2L calculates uptime as scheduled time - downtime, and the downtime comes from the dispatch open time (time closed - time created).  Does this mean that any delay in creating or closing the dispatch leads to an inaccurate downtime calculation which skews the OA calculation?  Does this also lead to a mismatch in the performance metric? 

In short how accurate is my OEE data?

Thanks in advance, Patrick.

0

• Official comment

  

  Krista Shaver

  • June 09, 2025 20:29

  Hello Patrick - I will open a ticket to further respond.

  L2L determines uptime by subtracting downtime from scheduled time, with downtime being measured based on the interval between when a dispatch is created and when it’s closed (time closed minus time created). Because of this, any delays in creating or closing a dispatch can indeed impact the recorded downtime, which in turn can skew your Availability calculation—and subsequently, your OEE figures.
• 

  Patrick Sherwood

  • June 09, 2025 20:38

  Thanks for the prompt response Krista...

  0
• 

  Craig Umberger

  • June 09, 2025 21:34

  We have Code Yellow Maintenance call dispatches, which are meant to be used for "running at a reduced rate." The problem we see there is that when you have one of these dispatches open and you're at a reduced rate, there's nothing coming back to OEE or OA without a secondary dispatch to account for downtime to cover the product lost by the reduced rate. It would be ideal if there was a means of calculating those reduced rate dispatches into the OA and OEE to get a more accurate number without having to do additional dispatches.

  0

Please sign in to leave a comment.