简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
RobinAbbott0077 · 2025年7月24日 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分Machine supplier uses ready as acknowledgement. Integrator expects it to allow the loading sequence. They agree those differ.
12分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.
16分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.
-2分Robin, did the walkthrough expose who is supposed to cancel an unfulfilled request? That's usually where my tidy diagrams stop being tidy.
22分Yes. Both sides expected the other to cancel. We've assigned that question to the joint controls review.
18分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.
8分Does the operator screen distinguish request received from waiting for machine access? That would spare people pressing request again because nothing visibly happened.
9分That distinction helped our discussion too, Isabel. People need to see the wait; they shouldn't need to understand the supplier argument underneath it.
6分Screen wording is being revised. Acknowledgement and access condition are separate in the draft now. Cancellation still under review. Thanks, Nina.
15分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .