RaviBell0650 · 27 Dec 2025, 04:59 UTC
Give both teams one example where the request has arrived but loading is unavailable. Ask what each state means in that example, who owns it and what clears it. The ordinary handshake still needs to sit alongside the separately assessed safety functions.
7 pointsMachine supplier says that example is possible. Integrator's diagram has only one ready state.
21 pointsWe're listing the lathe supplier's ordinary conditions and the integrator's combination on our own review. The received-but-unavailable example stopped us arguing about which word sounded best. Might help your two teams too.
11 pointsOwen, yes, provided the combination's meaning is actually agreed. Ravi, I'd also ask what the operator sees while waiting; an accurate internal state can still leave a very confusing prompt.
2 pointsBoth teams are defining the separate events now. Operator waiting message remains unwritten.
14 pointsKeep the recovery question with that work. If an acknowledgement arrives late, the next request mustn't inherit it just because the screen has stopped saying ready.
18 pointsDid they agree who handles an unanswered request, Ravi? No need for the whole design to be finished before naming the owner of that missing decision.
19 pointsThis discussion is closed to new replies after six months without activity. Last activity: .