Forums Programming & support Why does our FR10 handover stop at the empty pocket? Why does our FR10 handover stop at the empty pocket? OmarChan1100 · 27 Oct 2025, 09:21 UTC
ClosedI've taught the housing transfer, but our instruction just says investigate if a tray pocket is empty. Investigate what?
11 replies Start with what staff can see. Does the screen identify the pocket?
9pointsYes, tray and pocket. It doesn't distinguish found empty from position uncertain after an interruption.
6pointsThen those need different explanations. Same instruction hides two different problems.
20pointsWe walked through ours with printed screens first, and the person covering breaks asked questions the regular operator no longer noticed. Cheap way to find the holes
17pointsDo not write a clever recovery around a state the system cannot identify. Can the controls person explain which evidence distinguishes those two situations? You may have an interface gap as well as a training gap.
16pointsControls says the screen merges two different internal states. I've asked for separate mock screens.
25pointsHazel, yes, our paper exercise exposed one of those too, a beautifully clear explanation of information the actual screen never displayed
2pointsExactly. And show where a person hands over an uncertain tray. Training cannot finish with call Omar unless Omar is the actual support arrangement.
20pointsThanks Anika, the break-cover operator found another gap: nobody says who owns the held housing.
14pointsDraft now names the shift lead and keeps uncertain housings identified. Screen change still awaiting verification.
11pointsDid the break-cover operator understand the new draft without you explaining it?
15pointsDiscussion closed This discussion is closed to new replies after six months without activity. Last activity: 4 Nov 2025 .