Who clears a request that the inspection app never saw?

MayaAli0214 · 28 May 2025, 04:40 UTC

Closed
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 replies

MI
MiaChan1079
Replying to MayaAli0214

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 points
MA
MayaAli0214
Replying to MiaChan1079

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 points
AI
AishaBennett0779
Replying to MayaAli0214

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 points
HA
HazelArcher0397
Replying to MayaAli0214

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 points
MI
MiaChan1079
Replying to HazelArcher0397

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 points
MA
MayaAli0214
Replying to AishaBennett0779

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 points
AI
AishaBennett0779
Replying to MayaAli0214

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

16 points
HA
HazelArcher0397
Replying to MayaAli0214

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 points
MA
MayaAli0214
Replying to AishaBennett0779

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 points
MA
MayaAli0214
Replying to HazelArcher0397

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 points
MI
MiaChan1079
Replying to MayaAli0214

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 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .