I put both suppliers' sequence notes side by side. The machine supplier sets ready when it receives a loading request. Our integrator waits for ready to mean the loading area is available. Neither description mentions the other event.
This is the ordinary job interface, not the safety permissions. I need the two teams to stop approving the same word while describing different sequences.
Ask them to name request receipt and loading availability separately, with the owner of each value. Then walk one request through both descriptions. Can either team show which request the acknowledgement belongs to?
Not in the present sheet. It lists request and ready as bits with no attempt identity. The integrator thought the machine would retain the request until completion.
I'd have both authors explain the normal sequence in one meeting before anybody adds more bits. If their definitions disagree, extra signals can give you a larger disagreement with nicer names.
Beth, the machine clears its received state on its next internal transition. The integrator had assumed it would remain until the application acknowledged completion. We have a joint walkthrough arranged.
We once had a walkthrough stop at the successful load. Nobody asked what a timeout meant until the operator met one. Include no reply, delayed reply and reconnect while work is outstanding, not just the path everyone hopes to see.
Cancellation is not defined yet. The walkthrough now includes it and Nina's interruption cases. Our lead integrator owns the combined interface decision.
Bring the intended operator display into those cases too. A correct exchange can still be taught badly if the page calls request received ready to load.
I'd keep an unresolved outcome visibly different from a rejected request. Otherwise someone may think the obvious fix is to ask again when the first job could still exist.
The draft now separates receipt, availability and outcome. Both authors have agreed who writes each. Clearing after interruption and cancellation remain under review; no revised interface tested yet.