MinaAbbott0076 · 8 Mar 2026, 15:49 UTC
Neither until they agree what it means. Renaming one signal is cheap; quietly keeping two meanings will follow you into every fault discussion.
18 pointsI'd be happier renaming both. Did either team actually describe what happens if the request is received but the loading area isn't available yet?
4 pointsAnd please get the words on the eventual operator screen to match, otherwise a covering operator will inherit the argument without either drawing.
13 pointsThe machine drawing stays in preparation. The robot drawing has already advanced. They used the same arrow number as well, which hid the difference during our first meeting.
-1 pointsIs another permission shown, or just that ready arrow?
17 pointsSeparate safety conditions are outside this process sketch. The missing process event is loading access available. I have asked both teams to show that explicitly, not treat request acceptance as a substitute.
8 pointsGood. Now put a delayed preparation example through those arrows; the happy-path picture let both teams think they agreed.
8 pointsOmar, I'd do the delay before anybody redraws the whole thing. Let each team say where it waits on the existing sketch and write down the disagreement there.
15 pointsThat's what I meant by through the arrows.
23 pointsMina, who is writing the screen wording once these events have names?
20 pointsThe integrator owns the screen text. I sent them the delayed-preparation example first. Thanks, Omar Ali; marking the two different waiting points made the call much shorter.
12 pointsAmara, I have also put the screen wording on their list. It was absent from both teams' handover scope.
4 pointsDoes cancellation leave either team still waiting for the old request?
14 pointsThat's the awkward one. The request can disappear while preparation is still finishing. I don't know their interface, but I'd want to hear what each side thinks it is acknowledging then.
13 pointsHave they agreed on the names yet, Mina?
9 pointsRequest accepted and loading access available are agreed. Cancellation exposed another difference: the machine team had retained the accepted request, while the robot sketch started a new exchange.
10 pointsWill the operator see that an exchange was cancelled, or only that the cell is waiting?
3 pointsOnly waiting in the current screen draft. The integrator is revising it to distinguish the cancelled exchange. We have not settled how a fresh request is authorised after that.
10 pointsUseful catch before implementation. Who owns that remaining decision?
12 pointsI'd keep the cancellation example attached to the agreed names, Mina; it's the bit someone will otherwise drop when they tidy up the drawing.
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .