I helped hand over our FR10 sleeve loading job and I think we taught only the successful run. The operators can select the job and check the tray, but an empty pocket brings a call to me. Our sheet says 'resolve missing part' and then shows the start button. That is not a decision someone can follow. I want to replace it, but I do not own the recovery logic.
What happens on the screen when the pocket is empty? I ask because a training sheet can be awful, but it can also be trying to describe a screen that gives the operator no useful choice.
Then don't make the replacement sheet invent a choice. What does acknowledge actually do in the current program? That sounds like the first question for its owner.
I would also ask the operators what they think acknowledge does. Not to catch them out. Two people can press the same button while believing quite different things happened to the missing sleeve.
I had a sheet that said 'clear obstruction' with no mention of who could enter the area, then management wondered why everyone phoned maintenance. The phone call was the sensible part.
Aaron's case may need a programmer more than a new button, Theo. Acknowledging a message can be perfectly reasonable if the next state is clear. Here it isn't clear to us yet.
I wasn't proposing another button. I meant the word looks like an answer when it only dismisses the message. But yes, we need the next state before deciding how to teach it.
The programmer is here. After acknowledgment the job remains held for a recovery selection made on a separate page. Operators were not shown that page during our handover.
That is a substantial omission. Does the existing training authorise operators to make those recovery selections, or was that deliberately left with someone else? I would settle that before introducing the page.
It was left for a later training session. That session never happened. Until the owner completes it, our supervisor handles these held jobs; I have removed the misleading restart picture from the draft sheet.
That explains the calls. Was the supervisor available on every shift in your original handover plan, or did the plan simply assume you would be around?
I would put the contact arrangement in the interim handover, including break cover. Otherwise the safe instruction can still leave a person stranded beside a held job with nobody answering.
Ella, agreed. And Aaron, don't describe waiting for the authorised person as a failed operator recovery in your downtime notes. It'll send the next improvement meeting in the wrong direction.
Theo, the plan assumed I would be there. Ella, the supervisor has now named cover. The recovery training still needs arranging with the programmer, so I am not calling the handover complete.
For the training session, have somebody other than the programmer read the revised sheet back against an empty-pocket example. That should expose missing decisions before the sheet gets laminated into permanence.