# Find Lost Time

A machine loses time in two ways: it stops, or it runs slower than it should. Kanoa records both, and the reason an
operator gave is what turns a number into something you can fix. This lesson shows you how to find the biggest losses and
the ones nobody has explained yet.

## Read Downtime for One Asset

Kanoa has a ready-made **Downtime** analysis page. It looks at one asset at a time, so pick a line or a cell it has
collected data for.

![Downtime report](https://docs.kanoa.ai/img/downtime/downtimeDashboard.png)

1. Open **Ops → Analysis → Downtime**.
2. Click the **asset selector** and choose an OEE asset, such as **Machine 1**.
3. Choose a date range, such as **Yesterday**, or set a custom range.
4. If you only want the long stops, set the **Duration Filter** to a number of minutes.
5. To focus on the worst, set the **Top Downtime Filter** to show only the top N states or reasons.

![The filter bar](https://docs.kanoa.ai/img/downtime/filterBar.png)

## Find the Top Reasons

The page has several charts, each a different view of the same data.

| Chart | Use it to |
| --- | --- |
| **Downtime By Category** | See which category affects you most, such as maintenance or personnel. The pareto line marks the 80/20 breakpoint. |
| **Downtime By Reason** | See the specific reasons the asset was not producing. |
| **Downtime By Day** | Find a bad day. Each day is stacked by reason. |
| **Downtime By Pie** | See category and reason as pies, plus downtime by shift. |
| **Downtime Table** | See the raw events. Export them to Excel. |

![Downtime by category](https://docs.kanoa.ai/img/downtime/downtimeByCategory.png)

Start with **Downtime By Category**, then open **Downtime By Reason** for the category at the top. Downtime outside any
scheduled shift is grouped under *no Shift defined* in the shift pie.

::embed-section{src="../../kanoa-ops-analysis/downtime.md#filters" collapsed="true" summary="Reference Materials: Downtime Filters - Asset, date range, duration and top downtime."}

## Compare Losses Across a Site

The downtime page is one asset at a time. To compare a whole line, area or site, open **Loss Analysis** from
**Ops → Analysis → Loss Analysis**. It shows every loss in minutes, so downtime, slow running and scrap can be compared
directly.

![Loss Analysis](https://docs.kanoa.ai/img/reliability/loss-analysis.png)

1. Choose an **Asset**. Pick a site and every OEE asset under it is included.
2. Choose a **Date range**, then press **Go**.
3. Read the three **loss cards**: availability, performance and quality loss in minutes. The biggest is marked.
4. Click a card to see only that loss. **By asset** shows which assets lost the most.
5. Read **Top reasons** to see why. Click the **x** to go back.

Loss that no reason covers shows as **Unassigned**. That includes automatic speed-loss events nobody has explained yet.

**Events** lists the events behind the selected loss, with the most minutes first. **Export** saves them to Excel.

::embed-section{src="../../kanoa-ops-analysis/reliabilityKPI.md#losses-and-drill-down" collapsed="true" summary="Reference Materials: Losses and Drill-down - The loss cards, top reasons and the Unassigned reason."}

## Read Speed Loss

When a machine runs below 95% of its standard rate for 5 minutes, Kanoa opens a speed-loss event on its run, and the
operator can give it a reason from the info panel. The event starts as **Unassigned**.

Those events show in two places:

- The **Speed Loss** row of the timeline on the **Asset Run Analysis** dashboard, in each reason's colour.
- **Ops → Operations → Performance Events**, where an event still **Unassigned** counts as loss to explain, not as coded
  loss.

Performance events only cover slow running. Time the machine was stopped is downtime, and is tracked separately.

::embed-section{src="../../kanoa-ops/speed-loss.md#the-speed-loss-event" collapsed="true" summary="Reference Materials: The Speed-Loss Event - When one opens, what it counts and how it ends."}

## Give a Slow Run a Reason

If the operator didn't, you can code the lost minutes yourself.

1. Open **Ops → Operations → Performance Events**.
2. Select the asset and a date range, and run the report.
3. Find the row with uncoded lost minutes. Each row shows the runtime, the expected and actual infeed, and the lost minutes.
4. Select the row and click the add button.
5. Pick a **Reason Code**, add a note if it helps, and save. The event moves from **Uncoded** to **Coded**.

{/*
TODO: Confirm on a gateway the exact buttons on the Performance Events screen, and which security function it needs.
The product docs describe a Performance Events panel for the run with a Reason Code list and a Save step, and the
developer training describes selecting a row and using the add button. The speed-loss card on the info panel needs
Edit Operations.
*/}

You can split the lost minutes across several reasons when more than one thing slowed the line.

::embed-section{src="../../kanoa-ops/performance-events.md#coding-a-performance-event" collapsed="true" summary="Reference Materials: Coding a Performance Event - Reason codes and lost minutes."}

## Check Your Understanding

1. You want to know which category of downtime costs Machine 1 the most. Which chart do you start with?
2. How do you compare downtime, slow running and scrap across a whole site?
3. A speed-loss event's reason is **Unassigned**. What does that mean for your reports?

<details>
<summary>Answers</summary>

1. **Downtime By Category**, then **Downtime By Reason** for the top category.
2. Open **Loss Analysis**, pick the site, press **Go** and read the three loss cards and **Top reasons**.
3. It still counts as loss to explain, not as coded loss. Someone needs to give it a real reason.

</details>
