Standardizing Your OEE Metrics for Better Verifiability
To ensure your operational data remains a trusted, single source of truth, we are updating the OEE calculation logic within L2L Dispatch to align with industry best practices. This update will go live on Wednesday, July 8, bringing all dashboards and reports into full alignment with the standard formula:
Availability × Performance × Quality = OEE
This change resolves an underlying discrepancy where OEE could not be verified simply by multiplying its individual components. By moving to this standardized approach, your reported OEE will always reconcile perfectly with your underlying metrics, providing a transparent and fully auditable version of the truth.
Handling Pitches Without an Ideal Cycle Time (ICT)
A central focus of this update is standardizing how the system treats pitches that lack an Ideal Cycle Time (ICT). On the manufacturing floor, a pitch typically misses an ICT during periods of line downtime.
Performance is the only metric that uses Ideal Cycle Time in its calculation, so it is the only score affected by a missing ICT. For instance, if a line experiences an extended period of downtime, no product runs and no cycle time can be assigned. In this situation, Performance is naturally zero because nothing was produced—regardless of whether an ICT is present. Containing this data strictly within the Performance category ensures that downtime no longer distorts your Availability or Quality percentages.
- Previous Behavior: The system completely excluded pitches missing an ICT from the final OEE calculation, while still counting them toward standalone Availability and Quality reports. This "exclusion rule" effectively hid downtime from the OEE score, which is why the report math often did not reconcile.
- New Behavior: These pitches are now included consistently across all four metrics. A pitch with a missing ICT will hold its natural Performance score of zero, allowing the overall OEE formula to calculate perfectly without throwing off your other percentages.
What This Means for Your Data
To maintain long-term data integrity, this update will apply to both current and historical data. This ensures your reporting remains completely seamless and consistent across past, present, and future timelines.
Because the new formula factors in previously hidden downtime, you may see shifts in your historical and real-time percentages depending on how deeply you are viewing the data:
- Site Level: Most data will look very similar. Many values will not change at all, while some sites may see a minor shift of 0% to 3%.
- Area Level: You may notice moderate adjustments of up to 7%.
- Line Level: You may see much larger variances on individual lines. Lines that historically experienced heavy downtime will see the most significant adjustments, correcting previously inflated OEE scores to accurately reflect actual floor activity.
Please note that your underlying Availability, Performance, and Quality metrics themselves are not changing—only the way they multiply together to form OEE.
What Action Do You Need to Take?
- Test Early in Sandbox: You do not have to wait until July 8 to see how this impacts your reporting. Sandbox environments are available for early testing, allowing your teams to review historical data and get comfortable with the updated metrics ahead of the official release.
- Monitor Data Gaps: No immediate configuration changes are required on your part. However, to help you manage data quality proactively, pitches missing an Ideal Cycle Time will now be highlighted directly in your Daily Production Summary and Weekly Production Summary reports. This added visibility allows your team to identify and resolve local data gaps on your own timeline.