For FMCG
Capture every micro-stoppage. See the energy and yield losses hiding behind it.
High-throughput lines produce 1000+ units per shift. Operators react to visible problems. Micro-stoppages (5-30 seconds) bleed energy, time, and yield but are never logged. wiseDo captures every stoppage, every changeover, every scrap event, with timestamps and root cause.
Book an assessment
The Problem
The micro-losses that hide in plain sight.
On a 1000-unit/shift line, a 5-second stoppage happens 50 times a day. 250 seconds. Over 4 minutes of invisible waste. Nobody logs it. The supervisor doesn't know until the daily report says output is 5-10 units short.
Energy costs scale with production. If half your stoppages are changeover-related, you're running the heater/cooler for changeover duration when it could be in standby. That is energy budget spent on waste nobody can see today.
Scrap and rework get logged at end-of-shift. Was it a material batch? Line calibration? Operator error? By then, nobody remembers.
The wiseDo Solution
Continuous vision-based supervision. Pareto analysis on the micro-losses.
Every micro-stoppage, every changeover, every scrap event is captured, timestamped, and correlated against shift, line, and product. Pattern analysis identifies the high-impact improvements.
Result: idle draw becomes visible and attributable per unit of output. Changeovers optimized. Scrap and rework traced to root cause at the moment it happens.
Logged
Sub-minute stoppages captured with a reason code, automatically.
SMED timing
Each element timed, so your own best run becomes the standard.
Energy view
Consumption tied to output, so idle draw stops being invisible.
How wiseDo is deployed here
Six weeks, step by step.
A packaging or filling line running high speed and frequent SKU changes. The losses are small, constant and invisible in a daily total.
- 1
Line walk and loss agreement
We map filler, capper, labeller and case packer, and agree the numbers: micro-stoppages per hour, changeover time, energy per unit, giveaway.
- 2
Cameras and machine signals connected
Cameras watch the transfer points where jams start; machine run signals and energy meters are read at the panel. Edge box installed inside your network.
- 3
Micro-stoppage capture calibrated
Sight learns normal flow at each transfer point, so every stop under thirty seconds is logged with its location. These are the stops nobody writes down.
- 4
Changeover timing live
SMED clock starts and stops on what the cameras see, not on when someone remembers to press a button. Every changeover is compared to its best-ever time.
- 5
Energy and giveaway tied to production
Energy per case and fill-weight giveaway are computed against live output, so a slow shift shows its real cost, not just its count.
- 6
Review and scale
At week six: micro-stops, changeover time and cost of loss against your own baseline, with energy per unit where meters are available. Next line follows on the same box.
What wiseDo brings
The platform components doing the work.
One platform, one data model. Each component below reads and writes the same event spine, so nothing is re-typed and nothing is reconciled at month-end.
Sight
Every micro-stoppage captured and located, and changeovers timed from what actually happens.
PlantOps
Pareto of losses by station, shift and SKU; scrap and giveaway root-cause tagging.
Scheduler
SKU sequencing that minimises changeovers across the shift.
Energy module · in development
Consumption per unit against load and tariff, so the cheapest way to run the day is visible. Metering at the panel is part of the deployment; the optimisation layer on top is in development.
What changes on your floor
The two hundred small stops that were never logged become a ranked list with a location. Changeover time stops being an estimate. And energy becomes a per-case number the plant manager can act on.