Can't finish the FR5 interface while ready has two meanings

I tried received and loading available. Machine supplier says received happens immediately, loading available can follow later. That is already clearer than their timing diagram.

Good, now ask the integrator which event its sequence needs at each step. Don't simply rename the existing wire and leave the old assumption in the program.

Include the operator display in that agreement. Received should be visible while it waits. Otherwise the person at the screen sees nothing happen and tries another request. Seen that turn a clear sequence into a confusing shift report

Is loading available only ordinary sequence status, with the actual safety permissions handled separately?

Yes, Sofia. Safety functions are separate. The ordinary interface tells the sequence where the machine job has got to. Screen currently says ready for both meanings too.

Then put that distinction in the names, including on the screen.

Nina's cancellation question is worth a separate example in the walkthrough. Which side knows whether any loading has started by the time cancellation is requested?

Not agreed. Machine supplier calls cancel a new command. Integrator calls it clearing request. I think we've found the next argument.

I'd describe what the caller wants to happen instead of choosing either implementation first. Withdrawing an unaccepted request and dealing with a job already under way can need different handling.

Name the person who deals with an uncertain job too. The screen can show waiting all it likes, but someone needs authority to investigate when neither side can say whether the spacer moved

Controls lead is taking ownership. We've split not yet accepted from accepted and waiting. Cancel after acceptance stays unresolved while both suppliers agree the handling.

Can the operator read the request details while that uncertainty remains?

Please don't give them a clear button that also sends another request. Ours did, briefly. Quite a lot hidden behind one small word.

Sofia and Nina are pointing at different controls: looking at the job and changing its state. Have the screen draft show both, with the state-changing actions agreed by controls.

Screen draft now lets them view the job without changing it. Nina, no combined clear-and-request button. Bruno, thanks for separating the events first. That got both suppliers talking.

Did they agree what happens after a connection loss as well? You could have the new names right and still disagree about an old request when the link comes back.

Connection-loss cases added to the review, no agreement yet. Normal sequence wording is signed by both suppliers. I'm keeping recovery marked unfinished.

Keep that unfinished bit on the cover sheet. People love forwarding only the page with two signatures.