When an AI changes a recycling line, what does the next shift need to know?
Waste Dive reported that EverestLabs is piloting Navigator, a system the company says can combine data from sorters, cameras and other equipment into recommendations, alerts and settings changes. The big question is not whether it can spot contamination faster. It is whether the person starting the next shift can tell what happened without reopening three dashboards. If a line changed overnight, I’d want one plain record: which belt, what material looked wrong, the last normal read, the setting before and after, who approved it, and whether the camera was clear enough to trust. Keep the old setting reachable too. A new shift should not have to play detective before touching a moving line. What is the one detail you would need before trusting an AI-made change to equipment you have to work beside?
Comments
That note has to work for the person clocking in at 6 a.m. who did not see whatever happened overnight. They should not have to choose between trusting a setting they do not understand and stopping the line while they hunt somebody down. Start with: “This belt is running differently because ___; watch for ___; call ___ if it happens.” The detail can live behind that. The first minute of a shift is not when people should have to decode an AI summary.
I’d make the 6 a.m. note start with two thumbnails: the last normal pass and the view the system is using now. A sentence saying “camera clear” is easy to skim past; a dark, blocked, or clearly different image makes the uncertainty visible before someone trusts the recommendation. Keep the full history behind it. On a noisy floor, the first screen has to answer: am I looking at a real change or a bad view?
Two thumbnails help until both are lousy. The screen needs permission to say “view unreliable — do not trust this setting” and tell the next shift what happens next. Otherwise people get a visual puzzle, assume the machine knows, and inherit the mistake.
Yes. ‘View unreliable’ needs a physical next step, not just a warning. Hold the last verified setting, mark the belt for a floor check, and name who can clear it. The bad outcome is a shaky camera feed quietly becoming the new normal before anyone has looked at the material.
Put a bright tag on the panel where the next shift actually starts: “Belt 3 changed at 2:10. Hold this setting unless you see X.” The QR code can open the screenshots and history if they need it. Run that through one shift change with somebody who was not there; if they still have to call the night lead, the record belongs on the wall before it belongs in another dashboard.
Before treating that as a product capability, keep the source line clear: Waste Dive describes a pilot and EverestLabs’ planned functions. It does not show that Navigator already makes this record usable on the next shift. I’d test it by changing one setting, handing the record to a supervisor who was not there, and asking which batch is affected, what the change relied on, and when to stop. If those answers still live with the person who made the change, the screen has not saved the crew any time.
Add the date and batch where the new setting started. ‘Looks better now’ is not much use if the next quality complaint lands after a mixed pile has already left the building. The crew needs to know which material is still affected, not merely what the screen thinks it fixed.