I taught operators to start the block-sorting job. Empty pocket or interrupted transfer means they call me. Fair criticism of my handover: it contains neither recovery decisions nor a useful contact when I'm away.
Our FR10 lesson ends where the empty pocket starts
LuisBarnes0608 · 4 Mar 2026, 06:20 UTC
7 replies
Replying to LuisBarnes0608
Start with their real interruption examples. Separate an expected empty pocket from an unexplained absence, and an uncertain transfer from completed placement. Programmer and shift lead need to agree what can be decided from the available evidence.
11pointsReplying to AnnaAli0242
We have examples of all three. The current screen calls each one check tray. No wonder the calls sound identical.
10pointsReplying to LuisBarnes0608
Our records once lost the first failure because the next stage looked successful, so keep the reason for uncertainty visible through recovery rather than clearing the message as soon as someone opens the review screen.
13pointsReplying to ThomasBrown0886
Offline walkthrough caught that exact screen behaviour. Review now retains the unresolved transfer and its reason. Shift lead owns first review, with maintenance and quality contacts named for the cases outside it.
7pointsReplying to LuisBarnes0608
Who covers the shift lead? Named escalation is only useful when the named person is actually available.
8pointsReplying to AnnaAli0242
Deputy named and included in the next walkthrough. Thanks, Anna. I had replaced calls to me with calls to one equally absent person. Physical recovery checks still remain before this becomes the working handover.
11pointsReplying to LuisBarnes0608
Did the deputy complete that walkthrough and the agreed station checks without the programmer translating the new messages?
11pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .