I handed over the saved FR10 block-transfer job after showing a full tray run. The operators can repeat that perfectly well. When a pocket is empty or the sequence is interrupted, they call me because my instructions stop being specific at exactly that point.
I have been answering from memory, which is not a handover. I want the application owner and trainer to agree the decisions before I rewrite the lesson. The first uncertainty is whether an empty pocket was intended for that order or means a transfer went missing.
Why does every empty FR10 tray pocket still require me?
LouisChan1094 · 22 Apr 2026, 04:19 UTC
13 replies
Replying to LouisChan1094
Start with the order definition and tray fill arrangement. The operator needs a way to distinguish an intended short order from an unexpected gap, and the application needs an agreed response to each before the trainer explains it.
23pointsReplying to FelixChan1067
Our short orders use the first pockets in sequence. The screen only names the full tray job, so it gives the operator no visible expected count for that run.
22pointsReplying to LouisChan1094
That explains one call. For interruptions, what can they see about the last completed transfer? I would not assume the count tells them where a block physically ended up.
11pointsReplying to LouisChan1094
Nor that the selected tray is the fitted tray.
7pointsReplying to VictorAbbott0011
Hazel, they see a count but no attempt detail. Victor, tray identity is on the tray, not checked by this saved job. Both omissions are on the review now.
13pointsReplying to LouisChan1094
Who covers the calls while that review is unfinished?
11pointsReplying to JamieCarter0991
Jamie raises a practical gap. Louis, assign a named support route in the interim handover; an unclear recovery decision should not become an operator's experiment because the programmer is away.
19pointsReplying to FelixChan1067
Shift lead now takes those calls and contacts the application maintainer where the transfer state is uncertain. The proposed screen shows expected order count and tray identity. Maintainer is defining the interrupted-attempt view.
14pointsReplying to LouisChan1094
Let the covering operator try interpreting that view before polishing the lesson. They should be able to say what is known, what is uncertain and whom to call without somebody pointing at the answer.
12pointsReplying to HazelAllen0310
Include an unexpected gap, not only a short order.
12pointsReplying to VictorAbbott0011
And make it a defined exercise with the application maintainer and shift lead. Training should use the agreed recovery behaviour, not invent it during a demonstration.
23pointsReplying to FelixChan1067
That exercise is booked with both. The operator has reviewed the mock-up but hasn't tried the station cases yet. Thank you, Jamie; naming the interim contact already stopped the calls bouncing between two absent people.
7pointsReplying to LouisChan1094
Good. Keep that contact route after the lesson is improved too.
20pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .