Our planned FR10 housing-blank interface uses ready for receipt on one drawing and loading availability on the other. Ordinary sequencing is already ambiguous, before the separate safety conditions are considered.
Receipt and loading availability share one FR10 label
HanaChan1057 · 12 Apr 2026, 09:48 UTC
2 replies
Replying to HanaChan1057
What happens in their examples when a request is received but loading isn't available? I'd ask both authors to show that same case, including what the operator sees.
14pointsReplying to RachelAdams0174
The joint example exposed a missing pending-request state. Both authors are adding it, with separate receipt and availability labels. Cancellation and interrupted exchange still need agreement.
8pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .