Our UR5e operators can start the sleeve-transfer job I helped put together, but an empty tray pocket sends them straight to my phone; looking at my own handover sheet, I have explained every normal button and none of the decisions that stop the normal sequence. Where should I begin fixing that?
Begin with the actual empty-pocket event and agree its response with the controls owner, including how the operator recognises the state and when they must stop and seek help rather than continue.
We walked through the event without running the sequence and found two people thought skip meant different things, one meant leave the pocket and one meant advance the whole tray; controls is rewriting that choice before we train it
That is worth finding before practice; once the behaviour is settled, ask each operator to explain what will happen to both the tray position and the unfinished sleeve transfer.
Thanks Leah, that question is in the draft now; I've also stopped calling the original handover complete, since interruption and restart are still untouched