I asked both suppliers to describe their ready signal without using that word. Machine side means it received our request. Integrator means the loading area is available. At least the disagreement has a shape now, but each wants to keep the old signal name. How do we turn this into a handover somebody else can follow?
Give the two events separate names and descriptions. Or rather, agree the events first, then stop one name doing both jobs. Do they even occur at the same time?
Can the machine receive a request while the loading area is unavailable? That example may settle the naming argument more cheaply than another meeting about preferred words.
Yes, it can accept the request and wait. The integrator's current sketch treats that first response as though the wait is over. That's the part I want corrected before it reaches the operator sheet.
Then it is a sequence disagreement, not merely untidy names. Show the waiting state explicitly. The application needs to know a request exists without assuming the loading step can proceed.
Put Gabriel's ownership question in a shared state table with the events. Include what makes each state become true and what ends it, not just arrows between boxes.
The authors are working through that table. Their first version covers request receipt and later availability separately, but clearing after a withdrawn request is still disputed. Safety functions remain separate from these ordinary job states.
And a lost connection after receipt. Don't let reconnect turn a remembered request into permission for a new one. That needs agreement while both authors are still looking at the same table.
David, yes. The normal sequence is the easy bit. I'd rather leave recovery marked unfinished than squeeze it under a vague reset arrow so the drawing looks complete.
It says request received, waiting for loading-area availability. Operator understood that distinction, but asked who to call when the wait continues. We've added the support role. Withdrawal and reconnect rules are still being agreed.
Thanks for reporting the operator's question. A technically correct waiting state can still leave someone standing there wondering whether anyone else knows about it.
Yes, the active request reference is in details with the selected sleeve job. I have not called the interface finished; the two unresolved recovery cases are visible in the handover draft.