# Read OEE and Production Counts

OEE is one number, but three different problems can pull it down. This lesson shows you how to read OEE, work out which
part is the problem, and check the production counts behind it.

## How OEE Is Made

OEE is **Availability × Performance × Quality**. Each part answers a different question.

| Part | How it's worked out | A low number means |
| --- | --- | --- |
| **Availability** | Runtime / (runtime + unplanned downtime). Planned downtime, such as a clean in place, is left out. | The machine stopped too much. |
| **Performance** | Infeed count / (infeed rate × runtime) | The machine ran slower than its standard rate. |
| **Quality** | (Infeed count - waste count) / infeed count | Too much of what went in was scrapped. |

Performance uses infeed and runtime, so downtime and scrap don't distort it. Quality needs at least two counts. With only
one, quality shows 100%.

::embed-section{src="../../kanoa-ops-analysis/oee.md#oee-calculation" collapsed="true" summary="Reference Materials: OEE Calculation - Availability, performance and quality."}

## Read the OEE Chart

![OEE report](https://docs.kanoa.ai/img/analysis/oeeDashboard.png)

The OEE chart shows the parts of OEE side by side over time.

1. Open **Ops → Analysis → OEE**.
2. Choose an asset, or an area or site to include everything under it.
3. Choose a date range.
4. Read the chart. Kanoa picks the interval for you: hourly for one day, daily for several days, weekly across months. You
   can choose another, but a year by hour doesn't render well.
5. Read the average OEE, availability, performance and quality on the right.
6. Click a name in the chart legend to hide or show that plot.

OEE is colour-coded wherever it's shown: green is good, orange is a warning and red is bad. The thresholds are set per
asset.

![OEE colour coding](https://docs.kanoa.ai/img/analysis/oeeColorCoding.png)

![Modes as pies](https://docs.kanoa.ai/img/analysis/modePies.png)

:::tip
The same OEE can hide very different utilization, as in these mode pies. Look at where the asset's time went, not only the
percentage.
:::

## Find Which Part Drove It

Compare the three averages. The lowest part is where to look next.

- Low **availability**: go to the downtime reasons in the previous lesson.
- Low **performance**: look at speed-loss events and their reasons.
- Low **quality**: look at the scrap reasons, below.

**Loss Analysis** does this in minutes. It shows OEE with its parts at the top, then the three loss cards, with the biggest
marked. See the previous lesson.

::embed-section{src="../../kanoa-ops-analysis/reliabilityKPI.md#the-figures-at-the-top" collapsed="true" summary="Reference Materials: Loss Analysis figures - TEEP, utilization, OEE and its parts."}

## Check Production Counts Against Target

The **Production Counts** chart shows how an asset's infeed, outfeed and waste built up against its target. The same chart
is on the Asset Operation page as the **Asset Run Analysis** dashboard.

![Production Counts chart](https://docs.kanoa.ai/img/analysis/productionChart.png)

1. Select an OEE asset and a date range, then click **Go**. The chart covers up to 7 days.
2. Read the lines. Each is a running total, so it rises while the asset produces and stays flat while it doesn't.
3. Compare **Outfeed** with the dashed **Target** line. The gap shows how far ahead or behind you are.
4. Look at the **Waste** line, and at the **Scrap** row under the timeline.
5. Hover over the chart to see the totals at that time and what the asset was doing.

Under the counts, the timeline shows what was **Scheduled** against what **Actual**ly ran, with the **Downtime** and
**Speed Loss** rows. The shading shows time in modes other than Production.

::embed-section{src="../../kanoa-ops-analysis/productionCounts.md#reading-the-chart" collapsed="true" summary="Reference Materials: Reading the Chart - Lines, target, modes and the timeline."}

## Read the Totals

The panel on the right of the chart shows totals for the range. It lists each run, and the time in each downtime state and
speed-loss reason, longest first. **Scrap Reasons** lists the waste recorded against each reason, and **Uncoded (no
reason)** is waste with none.

Most sections open something when you click them. Click a run to open its count editor. Click **Scrap Reasons** to open the
Scrap editor.

## Code Uncoded Scrap

Waste with no reason hides what to fix. The **Scrap** row marks two kinds of waste:

| Marker | Meaning |
| --- | --- |
| Red cross (✕) | Coded scrap: waste counted with a reason. |
| Hollow amber diamond (◇) | Uncoded scrap: an hour where waste with no reason reached 5% of the infeed, by default. |

![The Scrap editor](https://docs.kanoa.ai/img/analysis/scrapEditor.png)

1. In the totals panel, click **Scrap Reasons** to open the **Scrap** editor.
2. Select the rows to code. **Select uncoded** selects them all.
3. Pick a reason in the list, then click **Set reason**.

**Clear reason** puts selected counts back to uncoded, and **Delete** removes a wrong count. Delete asks you to click again
to confirm.

{/*
TODO: Confirm which security function the Scrap editor and the count editor need. The count editor needs Edit Operations
in the Asset Operation docs; the Production Counts docs only say a user logged in with the right to do so.
*/}

::embed-section{src="../../kanoa-ops-analysis/productionCounts.md#coding-scrap" collapsed="true" summary="Reference Materials: Coding Scrap - Group, set, clear and delete waste counts."}

## Check Your Understanding

1. An asset's OEE is 55%. Availability is 95% and quality is 98%. Which part is the problem?
2. On the Production Counts chart, how do you see whether the asset is ahead of or behind target?
3. What does a hollow amber diamond on the Scrap row mean?

<details>
<summary>Answers</summary>

1. Performance. The machine ran, and little was scrapped, but it ran slower than its standard rate.
2. Compare the **Outfeed** line with the dashed **Target** line. The gap is how far ahead or behind it is.
3. An hour in which waste counted with no reason reached the threshold, 5% of the infeed by default. The waste needs a
   reason.

</details>
