I taught our saved FR10 sleeve-unloading sequence but left the interrupted-run decisions mostly in my head. Operators can start it, then need me when the physical sleeve and the displayed pocket disagree. How should we rebuild that part of the handover without teaching people to guess which one is right?
Agree the physical and application states with the process and controls owners first. Include unknown whereabouts and who resolves them. Then teach those decisions, not a collection of restart clicks.
We have listed the known-empty, known-held and unresolved cases with the operator who called me. Owners are deciding the permitted response to each. The unresolved sleeve is not treated as a free pocket merely because the job reopened.
Have the owners settled those responses now? The covering operator should try the explanation before handover closes, including finding help when the state cannot be resolved from the normal view.
Responses are agreed and the display examples now distinguish those cases. The covering operator found the right response to known empty, but couldn't find the contact for an unresolved sleeve. We've corrected that page; repeat walkthrough still to do.