Ready means received on one drawing and accessible on the other

RobinAbbott0077 · 24 Jul 2025, 16:41 UTC

Closed
RO
RobinAbbott0077
Our FR10 interface review has two definitions of ready. How do I get both suppliers agreeing to one sequence?

10 replies

NI
NinaBrown0936
Replying to RobinAbbott0077

We had a handover where ready meant whatever the speaker needed it to mean. Put a concrete sequence on the table: request sent, request acknowledged, loading area available, exchange complete. Have them name the conditions for each instead of debating the adjective.

15points
RO
RobinAbbott0077
Replying to NinaBrown0936

Machine supplier uses ready as acknowledgement. Integrator expects it to allow the loading sequence. They agree those differ.

12points
NI
NinaBrown0936
Replying to RobinAbbott0077

Then the integrator cannot use that acknowledgement for its current purpose. Have both teams document the separate conditions and ownership, including what happens when one disappears halfway through. The ordinary handshake also doesn't replace the machine's safety arrangements.

16points
LU
LucaAllen0265
Replying to RobinAbbott0077

A little sequence walkthrough helped ours more than another signal list. Include the case where the machine accepts the request but isn't available yet; people tend to skip that wait when demonstrating their own side.

-2points
NI
NinaBrown0936
Replying to LucaAllen0265

Robin, did the walkthrough expose who is supposed to cancel an unfulfilled request? That's usually where my tidy diagrams stop being tidy.

22points
RO
RobinAbbott0077
Replying to NinaBrown0936

Yes. Both sides expected the other to cancel. We've assigned that question to the joint controls review.

18points
OL
OliverAli0189
Replying to RobinAbbott0077

Put the answer in the interface document when they settle it. Otherwise the most important definition will live in the one meeting the maintainer missed.

8points
IS
IsabelBarnes0561
Replying to RobinAbbott0077

Does the operator screen distinguish request received from waiting for machine access? That would spare people pressing request again because nothing visibly happened.

9points
LU
LucaAllen0265
Replying to IsabelBarnes0561

That distinction helped our discussion too, Isabel. People need to see the wait; they shouldn't need to understand the supplier argument underneath it.

6points
RO
RobinAbbott0077
Replying to IsabelBarnes0561

Screen wording is being revised. Acknowledgement and access condition are separate in the draft now. Cancellation still under review. Thanks, Nina.

15points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .