I taught our Universal Robots UR5e job for tray transfer with a molded spacer in a small production training area.
Everyone can start it, but an empty pocket or interrupted run means a call to me.
I don't think this is attitude.
Our handover covered a clean run and left the awkward decisions out.
Everyone calls me when Universal Robots UR5e pauses (tray transfer)
JamieBennett0730 · 2026年8月7日 15:59 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
A teach-back could reveal where the handover becomes unclear. What do operators understand the restart instruction to mean when they explain it without prompts?
19分During a discussion, I asked operators to explain the restart wording and received several different interpretations. That gives us a concrete ambiguity in the handover to address.
22分Use the conflicting interpretations to revise the instruction into condition, permitted action and escalation criteria. After the responsible integrator reviews it, check understanding again through an unprompted teach-back.
13分How do I stop teach-back feeling like a test of the operator? The wording was mine. I don't want to make that their failure.
8分@JamieBennett0730 On my setup, I asked people to find where my guide forced them to guess. That invited corrections instead of making them defend a wrong answer.
9分@JamieChan1078 I still don't have an agreed recovery instruction the team can use consistently. The unclear cases remain escalation points.
13分Leaving unclear cases as escalation points accurately reflects the absence of consistently understood, agreed recovery guidance.
14分