简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Saved FR5 job starts easily, recovery still calls me back

WendyCampbell · 2026年6月16日 14:48 UTC

回复讨论
WE
WendyCampbell
I handed over our spacer-loading job and the operators can start it, but an empty pocket or interrupted run brings them straight back to me. Looking at my handover, I taught the happy sequence and left out the decisions. What should I add before blaming anyone's confidence?

18 条回复

YA
YasminBell0615

What do you tell them when the pocket is empty? Start with your actual decision.

9
WE
WendyCampbell

I check where the spacer is, which step stopped and whether the saved position can still be trusted. None of that is in the sheet. It just says call me for a problem.

16
DI
DineshBrooks0821

Then capture the information that supports that judgement and distinguish cases they may handle under an approved method from cases needing review. The handover should not turn your undocumented judgement into an instruction to guess where the spacer went.

15
CA
CallumBennett0708

Don't make empty pocket mean skip it automatically, because that pocket could be empty after a pickup while the spacer is somewhere you haven't accounted for

11
LU
LucaAllen0265

I'd include the interrupted state separately from an observed empty source pocket before a request. They can look similar at the tray, but the evidence about a held or placed spacer may be quite different.

24
YA
YasminBell0615

Luca, would you give those different screen messages, or one explanation with the unknowns listed?

20
LU
LucaAllen0265

Depends on what the system can establish. I'd rather a plain uncertainty message with the relevant job and locations than a precise-sounding diagnosis inferred from one empty pocket. The approved next action needs to match that uncertainty too.

2
WE
WendyCampbell

We have a draft with separate observed-empty and interrupted-uncertain cases now. The latter does not offer resume from the saved pocket. Controls still needs to review what the screen can reliably establish.

21
DI
DineshBrooks0821

Who covers review when you are absent? A better explanation can still end at the same unavailable person, which would leave the support arrangement unchanged.

5
CA
CallumBennett0708

And give that person the actual job and fixture identity, not a message saying Wendy's spacer problem

17
YA
YasminBell0615

That would be a memorable label and a terrible handover.

14
WE
WendyCampbell

Maintenance lead will own the uncertain-state review, with shift cover named. Thanks Dinesh, I had improved the decision text without changing the part where everything still depended on me.

20
LU
LucaAllen0265

Will an intended operator read the draft without you explaining it first? Interested in what they think the uncertainty message permits, rather than whether they say it looks clear.

10
DI
DineshBrooks0821

Include break cover in that reading too, Wendy. A regular operator may supply missing context from experience that the person covering lunch does not have.

14
WE
WendyCampbell

Our draft review exposed exactly that: one cover operator read held for review as waiting to resume automatically. We are changing the wording and keeping the unresolved physical state explicit.

22
CA
CallumBennett0708

Make the actual behaviour agree with the words before handover, because a clearer warning isn't enough if reopening still offers the old saved position as a restart point

11
YA
YasminBell0615

Has controls checked reopening as well as the interruption screen itself?

9
WE
WendyCampbell

Not yet. That is now an explicit review case, alongside the revised text and shift escalation. I have not called the handover complete or authorised independent recovery from these drafts.

6

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。