What does each team expect the other side to do when ready turns on?
Both suppliers ticked ready while describing different events
AdamBlair · 17 Oct 2025, 07:29 UTC
19 replies
Can you draw the sequence with event names instead of signal names? I would take ready off the first draft altogether.
-2 pointsWho clears it?
24 pointsRebecca's approach helped us untangle a similar table, though we still needed the eventual signal names alongside it for maintenance to follow the screen.
8 pointsMaya, one team expects us to wait after ready and the other expects the sequence to proceed. Sam, they also disagree about who clears it. Rebecca's event-only version may save us another meeting about the spelling.
22 pointsYasmin, yes, event wording first and screen wording beside it once the meanings agree.
16 pointsAdam, what happens to an accepted request when communication drops? That is where our tidy drawing fell apart.
21 pointsWas yours forgotten, Rebecca, or repeated?
1 pointsRepeated in the software test. The receiver remembered accepting it, but the sender restarted as though nothing had happened. We needed the controls people to sort that out, not another label.
16 pointsRebecca, ours has a blank box for communication loss. I had treated that as a later detail. Your example is useful; I have added it to the supplier discussion alongside the normal loading sequence.
13 pointsA blank box is easy to overlook when the normal path fills a page, and the operator will meet that box without the two suppliers beside them.
13 pointsAlso, request received must not be treated as permission to enter the machine area.
23 pointsAgreed, Maya. We are calling it request accepted in the discussion copy and keeping the access conditions separate. Neither team has signed the revised sequence, so these are proposed meanings, not a commissioned interface.
15 pointsMaya, would you put the access conditions on the same drawing? Ours became hard to read once every dependency was squeezed in.
24 pointsLinked detail is fine, Rebecca, as long as the sequence points to it unambiguously.
4 pointsAdam, is there a request identifier in the proposal?
17 pointsSam, I would let their controls teams choose the mechanism, but I do want them to explain how a delayed answer is matched to the request it belongs to.
-2 pointsSam and Yasmin, nothing has been chosen for matching requests yet. I have asked for a worked example with a delayed answer after reconnect. Thanks Rebecca for the restart story; it made the missing case much easier to explain.
8 pointsGood. Ask them to walk it from both ends. We each thought the other application was retaining the bit that mattered.
25 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .