# Performance Events Check

Use these questions to prepare for the Kanoa Ops certification exam.

<details>
<summary>Which OEE loss does a performance reason explain, and how is it different from downtime?</summary>

Performance reasons explain **speed loss**: the asset was running, but slower than its standard rate. Time the asset was stopped is downtime, explained by downtime states, and is not part of a performance event. See [Performance Events](../../../kanoa-ops/performance-events.md).

</details>

<details>
<summary>How does Kanoa calculate lost minutes?</summary>

It compares the expected infeed (runtime × standard rate) with the actual infeed during runtime, and converts the missing infeed into time at the standard rate. For example, 60 minutes at a 3.75 lbs/min standard rate with 195 lbs actual is 30 lbs short, which is 8 lost minutes. See [Code Performance Events](../08-performance-events/2-code-performance-events.md).

</details>

<details>
<summary>Why is speed loss measured on the infeed rather than the outfeed?</summary>

Because it is lost **process** time, not lost output. Rejected units reduce the outfeed and are already counted in the Quality factor; measuring speed on the infeed keeps the two losses separate. See [Performance Events](../../../kanoa-ops/performance-events.md).

</details>

<details>
<summary>Does coding a performance event change the OEE performance number?</summary>

No. The loss already exists in the performance factor. Coding only explains it, and the same lost minutes can be split across several reasons. See [Code Performance Events](../08-performance-events/2-code-performance-events.md).

</details>

<details>
<summary>Why must performance reasons be linked to assets?</summary>

Linking controls which reasons can be selected when coding an asset's speed losses, so people only see reasons that apply to that equipment. Reasons that aren't linked don't appear for the asset. See [Configure Performance Reasons](../08-performance-events/1-configure-performance-reasons.md).

</details>

<details>
<summary>Machine 1 runs steadily at its scheduled rate of 3.25 lbs/min. Why does Kanoa still report lost minutes?</summary>

Expected infeed is calculated from the **standard** rate (3.75 lbs/min), not the scheduled rate. The scheduled rate is used for scheduling, to estimate how long a production order will take. Running at 3.25 lbs/min leaves about 0.5 lbs short every minute, and that gap is the speed loss that shows up as lost minutes to code. See [Code Performance Events](../08-performance-events/2-code-performance-events.md) and [Configure Production Rates](../01-base-configuration/3-configure-item-rates.md).

</details>