OEE
Overall Equipment Effectiveness identifies the percentage of manufacturing time that is truly productive. An OEE score of 100% means you are manufacturing only good parts, as fast as possible, with no downtime.

Fair warning though, you can get the same exact OEE number for entirely different utilization scenarios.

OEE is often considered meaningless without utilization context. To address this, many implementations stretch OEE to cover 100% of time, categorizing idle time as unplanned downtime. But is this the best approach? The Goal says it's ok to have local inefficiencies; idle time allows for more capacity planning. OEE should focus on how well we operate when we are expected to operate, but utilizing the assets have efficiently may be a bigger problem than how well they run during production. Reducing changeover, setup time, or maintenance may have a greater impact on your bottom line than reducing scrap or rework. This is not to say OEE is not important, just that it should be your only focus.
OEE Calculation
OEE is a widely accepted lean manufacturing standard, and extensive resources are available online. Here, we�ll focus primarily on how it is calculated and how it can be customized.
The term OEE was invented in the 1960s by the creator of the Total Productive Maintenance system, Seiichi Nakajima. OEE is expressed as a percentage from 0 to 100, where an OEE score of 100 percent would indicate that a manufacturing line or cell was producing only good parts at the anticipated production rate with no unexpected stops.
OEE is calculated by multiplying Availability * Performance * Quality
Availability
Availability = runtime / (runtime + unplanned downtime)
When an OEE_Enabled asset is in production mode, the amount of time the asset state is in a 'running' type state compared to an 'unplanned downtime' type state is pulled from the mes.stateEvent table to calculate Availability.
Planned downtime events such as a 'Clean In Place' step are excluded from the availability calculation.
Refer to the Asset States section of the Asset Configuration page for more info on setting up asset states and modes.
Performance
Performance = infeed count / (infeed rate * runtime)
Performance looks at infeed count and runtime, not outfeed count and total time as downtime and scrap would then skew the performance metric. Performance should only indicate processing speed issues.
If no infeed count is captured or entered for the asset, it's calculated from the outfeed and waste counts. See Calculated Counts.
The infeed rate is taken from the standard rate set for the item (material) when it is processed on the asset. The standard rate is set in the Materials Production Rate screen. Refer to Materials Configuration section of the help for more details.
Sometimes the standard rate set for an item running on an asset may be affected by other external factors such as crew size, inclement weather, or moisture content of incoming material. To handle this, the standard rate can be modified and set at the time the asset is in production via the system.kanoa.event.assetOperationChange() system function.
Quality
Quality = (infeed count - waste count) / infeed count
To be able to provide a 'Quality' metric for OEE, we're going to need at least two counts. It can be infeed and outfeed, outfeed and waste or infeed and waste. If only one count is provided, the Quality metric will default to 100%.
Calculated Counts
When a count isn't captured or entered for the asset, it's calculated from the other two:
- Infeed = outfeed count × package count + waste count
- Outfeed = (infeed count - waste count) / package count
- Waste = infeed count - outfeed count × package count, or 0 when only one count is provided
The package count is the number of infeed units in one outfeed unit, set on the item's production rate for the asset. It's 1 when not set, so when infeed and outfeed are in the same units, infeed = outfeed + waste.
Setting Up OEE for Lines and Cells
Any asset can be OEE Enabled: a line, or a cell on a line. Each OEE-enabled asset gets its own data interface tag, and its OEE comes only from its own states, counts and runs. OEE reports for an area or a site include all of its OEE-enabled assets.
There are three common ways to set up a line and its cells.
| Setup | OEE Enabled | Use it when |
|---|---|---|
| Line only | The line | The line runs as one unit and its PLC gives one state and the line's counts |
| Line, with stops by cell | The line | You want one OEE for the line, but want to know which cell caused each stop |
| Each cell | The cells (and the line, if it has its own data) | Each cell has its own state and counts, and you want OEE for each one |
Line Only
Connect the line's state and counts to its data interface tag. The line's performance is measured against the item's standard rate on the line, which should be the rate of the line's bottleneck.
Line, With Stops by Cell
Keep OEE on the line, and link each cell's own downtime states to the cell. When a cell stops the line, the PLC sets the line's Machine ID input to the cell's asset ID and State to the cell's state code. The stop is recorded on the line with the cell's state, so it counts against the line's availability and you can see which cell stopped the line. See Machine ID in Inputs Folder.
Each Cell
OEE Enable each cell and connect its own state and counts. Each cell has its own runs, so give each the item's standard rate for that cell.
Decide which asset's counts are the line's production. An order's actual quantity and an item's produced totals add up the outfeed counted on every asset that runs it, so if every cell counts outfeed, each unit is counted once per cell:
- The cell that makes the item, usually the last one, counts outfeed as normal.
- The other cells count infeed and waste only, and leave outfeed unconnected. Their performance and quality still work, because both are worked out from infeed and waste.
- Cells that test or inspect the item without making it, such as an end-of-line tester, are set up the same way: infeed is every unit tested and waste is the failures. See Cells That Don't Make the Item.
If the line is also OEE Enabled with its own counts, it counts as one more asset running the item, so only one of the line and its last cell should count outfeed.
A cell with no outfeed still shows one on its own screens, worked out as infeed − waste, but that isn't a recorded count and isn't added to the item's totals. When you report on several of the line's assets together, though:
- Infeed and waste are added up from every asset, so the combined infeed and quality include the cells that don't count outfeed.
- If only cells with no outfeed ran the item in the date range, the report works the outfeed out from the combined infeed − waste.
Color Coding OEE
Wherever we show OEE Analytics, the metrics are color-coded in green (good), orange (warning), red (bad). The thresholds for setting the coloring are configured in the Asset Configuration screen. Refer to Asset Configuration for more details.

Modifying OEE
We're not actually suggesting you modify OEE because it is a standard and bear in mind that OEE is math, if you use it the way it was intended, it can be quite useful in planning.
Example: Using OEE to Estimate Order Completion If the average OEE for an asset is 67% and the standard deviation is fairly low, you can use this number to determine how long it will take to complete an order. For example, Order XYZ requires 10,000 cases of Product A. With a Standard Rate of 200 cases per hour and an OEE of 67% (due to downtime and scrap), the actual expected production rate becomes: Standard Rate x OEE = 134 cases per hour Total Estimated Order Time = 10000 Cases / 134 cases per hour = 74.6 hrs.
Having said all that, the data points needed to determine OEE (runtime, downtime, std Rate, counts etc.) are exposed by our system functions.
If you really want to change the way OEE that is returned, you can see how we calculate it in our stored procedures. We recommend making a copy of the stored procedure and using your own version within the application, as our procedures may be updated periodically.
OEE Analytics
OEE Analytics are shown throughout the application, from the asset card on the enterprise view to the 'Operator Station' screen. Regardless of where you get your OEE number, it is calculated from the same data source using one of several functions...
- system.kanoa.event.getOEEDataByInterval()
- system.kanoa.event.getOEEDataByIntervalByShift()
- system.kanoa.event.getOEEDataSummary()
To understand more about how OEE is calculated and how it can be modified, please refer to OEE Configuration.
The OEE Chart visualizes the individual component parts that comprise OEE.

You can choose to chart OEE data for a specific asset or for all assets in an area, or at a site, for the given date range. By default, the interval (time period) is automatically determined based on the date range selected. If a range of one day is selected, an hourly interval is chosen. If the date range crosses multiple days, the interval will be by day. If the date range crosses months, the interval will be by week. You can choose the interval you want, be aware that showing a years worth of data by hour may not render that well in the bar chart.
On the right side of the chart, the average OEE, availability, performance, and quality values are displayed.
Each of the plots can be toggled on or off by clicking in the chart legend.