RobinAbbott0077 · 24 Jul 2025, 16:41 UTC
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.
15 pointsMachine supplier uses ready as acknowledgement. Integrator expects it to allow the loading sequence. They agree those differ.
12 pointsThen 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.
16 pointsA 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.
-2 pointsRobin, did the walkthrough expose who is supposed to cancel an unfulfilled request? That's usually where my tidy diagrams stop being tidy.
22 pointsYes. Both sides expected the other to cancel. We've assigned that question to the joint controls review.
18 pointsPut the answer in the interface document when they settle it. Otherwise the most important definition will live in the one meeting the maintainer missed.
8 pointsDoes the operator screen distinguish request received from waiting for machine access? That would spare people pressing request again because nothing visibly happened.
9 pointsThat distinction helped our discussion too, Isabel. People need to see the wait; they shouldn't need to understand the supplier argument underneath it.
6 pointsScreen wording is being revised. Acknowledgement and access condition are separate in the draft now. Cancellation still under review. Thanks, Nina.
15 pointsThis discussion is closed to new replies after six months without activity. Last activity: .