18 points of efficiency, 18 minutes after it took over.
The machine wrote its own new record. Twice.
The system keeps a best-known-good record per recipe and only overwrites it when it beats its own previous best. During the session it beat the stored record twice: first 18 minutes after the controller took over, then again at 29 minutes.
No operator intervened at any point.
The 61.65 % starting point was this machine's own best on this recipe under manual operation, held down by the same feed problem described further down this page. Machine 2 was running a different recipe, so its efficiency is not directly comparable to that record.
Same shift. Same infeed. Same pack weight.
Machines 1 and 2 ran the same 170 g pack on the same line at the same time, from the same software process: one autonomous, one operated the way it always had been. Machine 4 ran a different 142 g product on a well-fed infeed, so it is not a like-for-like comparison. It is here because it shows the system reporting a healthy machine as healthy.
| Machine | Mode | Pack | Efficiency | Giveaway / pack | Good packs |
|---|---|---|---|---|---|
| Machine 1 | autonomous | 170 g | 75.26 % | 1.06 g | 1,168 |
| Machine 2 | manual | 170 g | 71.99 % | 1.56 g | 784 |
| Machine 3 | standby | — | — | — | — |
| Machine 4 | manual | 142 g | 99.86 % | 1.38 g | 1,436 |
Swipe the table sideways to see every column
Measured session, 23 Jul 2026Counter-differenced per machine from the weigher's own good-pack, missed-cycle, overweight and total-weight counters. Machine 3 was in standby all session and produced no production data.What it looked like as it happened.
It learned your product in the time it takes to fill a pallet.
Mid-run, on a recipe it had no model for yet, the system trained and deployed its first model for that product without pausing control.
What this session was, and what it wasn't.
This was a measured 45-minute session, not sustained production experience. It is a strong proof of concept and we describe it as one.
The run prioritised efficiency over giveaway by design. Giveaway is trimmed further in a later tuning phase, so the giveaway figures are not the best this system does.
Efficiency and giveaway are derived by counter differencing (the machine's own counters) rather than from logged per-cycle averages, because counters are ground truth. Where the two disagree, we publish the counter figure even when it is less flattering.
No customer, site, equipment manufacturer, model or product brand is named anywhere on this site, by policy.
We'd rather measure your line than estimate it.
That is what a line assessment is. You get your own version of this page, from your own data.