L2L Connect: Enterprise OEE Report

 

What data inputs are used to calculate OEE?

Input	Description	Source
Scheduled Shift Time	Total shift time (i.e. 7am - 3pm = 8 hours)	User Input
Scheduled Downtime	Breaks/lunches/startup/cleanup time within a shift	User Input
Capacity Reduction	Downtime reason codes that reduce capacity (i.e. no scheduled production)	User Input
Unplanned Downtime	Time when the machine is not considered running	L2L Connect SensorBot
Baseline Target	Divided from OEE and its components to identify baseline trends	User Input
Utilization	Time when the machine is considered running	L2L Connect SensorBot
Part Count	# of pieces (or cycles)	L2L Connect SensorBot
Hourly Target	Can be either Fixed or Scheduled.  Fixed = Fixed target for all production time (i.e. always 50 pieces per hour) Scheduled = Variable target based on schedule. A weighted hourly target is calculated based on how long each scheduled target was active for during the reporting period. The Enterprise OEE Report will use Scheduled targets if available and Fixed if not.	User Input or L2L Connect SensorBot or ERP Integration
Microstoppage Time	The duration of time between machine cycles that is less than a specified threshold (i.e. any downtime under X minutes). If the asset is in a microstoppage, it will continue to remain as "active"/green in order to categorize this time as a performance loss rather than an availability loss.	L2L Connect SensorBot
Rejects/Scrap	# of pieces (or cycles) that do not meet quality standards.	User Input or L2L Connect SensorBot
Potential Production Time	Scheduled Shift Time - Scheduled Downtime - Capacity Reduction	Calculated

 

How is OEE calculated?

There are 3 components to OEE in the Enterprise Report - Availability, Performance and Quality. It is important to know that some assets may not have enough data for all 3 components.

For example, if part count is not tracked in the L2L Connect Cloud, only Availability will be calculated for the asset. Performance and Quality will remain at 100%.

 

Component #1: Availability

Availability = ((Potential Production Time - Unplanned Downtime) / Potential Production Time) / Baseline Target

 

Component #2: Performance

This can be calculated multiple ways, depending on the data inputs available.

 

    Scenario #1: No Part Count or Microstoppage Data
    Performance = 100%

 

    Scenario #2: Microstoppage Data

    Performance = ((Potential Production Time - Sum of Microstoppages) / Potential Production TIme) / Baseline Target

 

    Scenario #3: Fixed or Scheduled Target

    Performance = ((Potential Production Time - ((Actual Cycle Time - Expected Cycle Time) * Part Count) / Potential Production Time) / Baseline Target

 

Component #3: Quality

This can be calculated multiple ways, depending on the data inputs available.

    Scenario #1: No Fixed or Scheduled Target
    Quality = 100%

    Scenario #2: Fixed or Scheduled Target Data

    Quality = (Potential Production Time - (Reject/Scrap * Expected Cycle Time)) / Baseline Target

 

Finally, OEE = Availability * Performance * Quality

 

Why can't I select certain assets?

There are two reasons why an asset might be disabled in the Enterprise OEE Report:

1. Missing shift schedule - if an asset is not assigned at least one shift schedule, it will be disabled in the report.
2. Missing minimum data - an asset must at least have Utilization/Downtime data in L2L Connect Cloud.

 

What happens if I select a reporting period prior to the asset's deployment date?

The L2L Connect Reporting Engine will only request data for assets after their deployment date. This prevents the reduction in OEE values due to empty datasets.

We define the deployment date as the date the first data for an asset was transmitted to the L2L Connect Cloud.

Why do the results in the Enterprise Report differ from the Standard Plant Report?

The Enterprise OEE report uses L2L Connect's latest L2L Connect Reporting Engine (Version 3) that boasts up to 5x faster reporting speeds and other improvements. 

Minor discrepancies may be caused by rounding - discrepancies of 1-2% are the result variations of rounding and precision across the reporting pages. This does not affect the underlying results and does not indicate calculation errors are present.

A more noticeable discrepancy may be noticed due to Baseline Targets. The standard OEE report did not adjust OEE and its components except for in the Time Series chart. The Enterprise OEE Report adjusts every single value displayed on the page.

 

How can I see the specific OEE calculation properties by asset?

Clicking on any asset in the left sidebar will reveal a pop-up window that provides detailed information about the asset.

 

How are differing shift schedules taken into account?

OEE data for each asset is calculated based on its specific shift schedule, then averaged and summed to provide a set of values for each calendar day.

The Enterprise Report OEE does not require user input to interface with shift schedules.

 

How are differing time zones taken into account?

OEE data for each asset is calculated based on the time zone specified in its shift schedule.

The Enterprise Report OEE does not require user input to interface with shift schedules.

 

How can I compare assets or locations against one another?

Once you generate a report, you are prompted and encouraged to manipulate the company tree in the left sidebar. This allows you to slice and dice the data between assets & locations.

 

The report takes a long time to generate. Can it be faster?

Version 3 of the L2L Connect Reporting Engine has been optimized to handle the millions of incoming data inputs per day entering the L2L Connect Cloud but we are always looking for ways to improve the user experience.

A few tips to improve the reporting speed:

1. Reduce the number of selected assets/locations
2. Break down the reporting time ranges into smaller timeframes (i.e. report by quarter instead of year)
   
   
3. Check your internet speed/connection - as a benchmark, a weekly report for 1 asset should take no more than 5 seconds to generate.