# Performance Events

You have already given Kanoa reasons for two of the three OEE losses: **downtime states** explain lost availability, and **item states** explain lost quality. Performance reasons complete the picture by explaining why an asset ran **slower** than its standard rate while it was running.

| OEE factor | Kanoa concept | What it explains |
|---|---|---|
| Availability | Downtime states | Why the asset wasn't running |
| Quality | Item states / waste reasons | Why units were rejected or scrapped |
| Performance | Performance reasons | Why the asset ran below its expected speed |

Kanoa calculates *that* a speed loss happened by comparing the expected infeed (from the standard rate) with the actual infeed during runtime. People then record *why* it happened by coding the lost minutes with a performance reason. That coding step turns "performance was low today" into "performance was low today mostly because of tool wear on Machine 1."

::embed-section{src="../../../kanoa-ops/performance-events.md" collapsed="true" summary="Reference Materials: Performance Events - Code speed losses with performance reasons."}

In this section you will:

- Create performance reasons for the machining area and link them to Machine 1.
- Review the speed losses Kanoa calculates for Machine 1 and code them with reasons.
- Add the performance reason widgets to a dashboard.