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.

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

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. |

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.
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.

- Choose an Asset. Pick a site and every OEE asset under it is included.
- Choose a Date range, then press Go.
- Read the three loss cards: availability, performance and quality loss in minutes. The biggest is marked.
- Click a card to see only that loss. By asset shows which assets lost the most.
- 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.
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.
Give a Slow Run a Reason
If the operator didn't, you can code the lost minutes yourself.
- Open Ops → Operations → Performance Events.
- Select the asset and a date range, and run the report.
- Find the row with uncoded lost minutes. Each row shows the runtime, the expected and actual infeed, and the lost minutes.
- Select the row and click the add button.
- Pick a Reason Code, add a note if it helps, and save. The event moves from Uncoded to Coded.
You can split the lost minutes across several reasons when more than one thing slowed the line.
Check Your Understanding
- You want to know which category of downtime costs Machine 1 the most. Which chart do you start with?
- How do you compare downtime, slow running and scrap across a whole site?
- A speed-loss event's reason is Unassigned. What does that mean for your reports?
Answers
- Downtime By Category, then Downtime By Reason for the top category.
- Open Loss Analysis, pick the site, press Go and read the three loss cards and Top reasons.
- It still counts as loss to explain, not as coded loss. Someone needs to give it a real reason.





