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

Who clears a request that the inspection app never saw?

MayaAli0214 · 2025年5月28日 04:40 UTC

已关闭
MA
MayaAli0214
I'm costing the handover for an FR10 sample-checking station, and the ordinary job request vanishes before the inspection app sometimes notices it. PLC contractor says the app should be quicker; developer says the PLC should hold it. Would a simple ownership table help settle this, and what needs to go in it besides who sets each bit? I don't write either side, but I need something firmer than budgeting time for them to argue again.

11 条回复

MI
MiaChan1079

Include who clears it and what the other side must have seen first. Also define accepted, busy and finished separately. Those get called 'acknowledged' interchangeably in conversations, which is economical until someone implements it.

18
MA
MayaAli0214

That is happening here. The PLC contractor calls received 'done', while the developer means inspection finished. I'll get those names agreed before the timing discussion.

19
AI
AishaBennett0779

A table helps, but make them walk through a disconnect with a request outstanding; otherwise both can agree on bit names and still build incompatible recovery.

15
HA
HazelArcher0397

I'd want a little sequence drawing too. I tried to follow one of those tables at a supplier meeting and understood every row, then realised I hadn't a clue what happened first. Not my proudest ten minutes.

17
MI
MiaChan1079

The drawing is useful. I would still keep the table as the precise definition. Draw the wait states as well as the successful exchange, or the page makes every problem look momentary.

20
MA
MayaAli0214

They've agreed the app acknowledges acceptance, not completion. PLC holds the request until that acceptance. Restart with an outstanding job is still blank, so Aisha's example is next.

3
AI
AishaBennett0779

Give that example an actual job reference, and ask both developers what they would display after reconnecting without knowing whether the inspection finished.

16
HA
HazelArcher0397

And Maya, ask who gets called when it stays in that state. Our supplier gave a very neat answer that depended on a programmer being on site. Expensive little footnote.

18
MA
MayaAli0214

We've added an unresolved state to the proposal. No automatic second inspection from that state. The two developers still disagree on which side retains the job details through restart.

17
MA
MayaAli0214

Hazel, thank you for the callout question. Neither support quote covered reconciling an interrupted job. I have asked them to price and explain that work explicitly.

9
MI
MiaChan1079

Is the retention decision still open? I would leave a named owner beside it in the handover draft. Otherwise this is exactly the sort of blank people assume the other contractor filled.

23

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .