# Operator Effectiveness

OEE tells you how well an **asset** performed but it can't tell you why a line wasn't running: was it a mechanical fault, was nobody scheduled, did the scheduled crew not show up, or were people there but waiting on material? **Operator Labor Effectiveness (OLE)** and **Productive OLE (POLE)** apply the same OEE math to **labor**, by bringing in who was supposed to be on a line and who actually was.

| Metric | Availability is... | Answers |
|---|---|---|
| OEE | Asset running time ÷ scheduled time | Was the machine running? |
| OLE | Operator logged-in time ÷ operator's scheduled time | Was the operator there? |
| POLE | Time logged in **and** the asset running ÷ scheduled time | Was the operator there **and** was work happening? |

All three share the same Performance and Quality factors. The gap between OLE and POLE is time people were present but the line wasn't producing: changeovers, waiting on parts, downtime absorbed by labor. Kanoa shows it as the **Labor Gap**.

::embed-section{src="../../../kanoa-ops/ole-pole-analysis.md" collapsed="true" summary="Reference Materials: OLE / POLE Labor Effectiveness Analysis."}

The feature has three pieces, and this section covers each in turn:

1. **Scheduling**: crews and shift assignments say who *should* be on which line.
2. **Operator login**: operators badge in and out of the line they're working, recording who *was* there.
3. **Analysis**: the Operators dashboard combines both with the line's own run data.

You'll use the `operator` and `tempOperator` users from [Managing Users](../04-managing-users/index.md) and the Day Shift from [Shifts](../02-scheduling/1-shifts.md).