our FR10 ready signal has two owners and two meanings

MayaAbbott0040 · 22 Aug 2025, 06:57 UTC

Closed
MA
MayaAbbott0040
I'm assembling the lathe handover documents. Ready means request received in one supplier's table and loading area available in the other's. Neither has noticed the other's definition. This should be a pleasant meeting.

17 replies

TH
TheoArcher0410
Replying to MayaAbbott0040

Put both definitions on the same page before that meeting. Ask each team what event causes its signal and what the other team may do after seeing it. Easier to discuss than whether ready is a good word.

8points
MA
MayaAbbott0040
Replying to TheoArcher0410

Tables side by side now. Machine supplier confirms receipt does not mean access is available.

18points
TH
TheoArcher0410
Replying to MayaAbbott0040

Then split receipt from availability in the proposed interface. Also ask what remains pending between them and who owns it. That waiting period is where a neat signal list usually runs out of explanation.

10points
IM
ImranChan1088
Replying to MayaAbbott0040

Our last class got further passing request cards across a table than staring at the interface spreadsheet; make one person delay the answer and see who thinks the job has vanished

13points
MA
MayaAbbott0040
Replying to ImranChan1088

We can do that before coding anything. No point debugging a disagreement faster.

14points
MA
MayaAbbott0040
Replying to TheoArcher0410

Walkthrough found the request being cleared on receipt while the integrator still expected it during the wait. Both teams are revising ownership.

6points
BE
BethArcher0411
Replying to MayaAbbott0040

Which team tells the operator why it's waiting, Maya? Otherwise they'll get a green received lamp and no explanation of why nothing happens

11points
PR
PriyaBennett0742
Replying to MayaAbbott0040

Does the proposal distinguish ordinary availability reporting from the safety conditions for access? I would want the responsible reviewers to make that boundary explicit

16points
MA
MayaAbbott0040
Replying to PriyaBennett0742

Beth, integrator owns the operator display. Priya, safety reviewer has flagged that distinction; ordinary receipt cannot authorise access.

20points
TH
TheoArcher0410
Replying to MayaAbbott0040

Try cancellation during the wait next. The teams need to know whether cancellation was merely requested or actually accepted, particularly if availability changes at the same time.

17points
MA
MayaAbbott0040
Replying to TheoArcher0410

They found conflicting cancellation assumptions too. Draft now includes a pending-cancel state, with the unfinished handover still identified.

22points
IM
ImranChan1088
Replying to MayaAbbott0040

Give a tutor or shift lead those cards without the authors whispering the answers, because our beautiful first version only worked while I explained what each card secretly meant

17points
MA
MayaAbbott0040
Replying to ImranChan1088

Shift lead tried the draft. Asked who to call in the review state. No answer on the sheet yet.

2points
BE
BethArcher0411
Replying to MayaAbbott0040

Put the actual first contact there, plus what the operator must leave alone while waiting; named review state isn't a recovery instruction by itself

17points
PR
PriyaBennett0742
Replying to MayaAbbott0040

Will both suppliers review the operator wording too? It should describe the behaviour they have agreed, including what remains unresolved

4points
TH
TheoArcher0410
Replying to MayaAbbott0040

And keep the crossing-response cases with the final interface document. Future changes need those examples, not only the tidy table you eventually agree.

10points
MA
MayaAbbott0040
Replying to TheoArcher0410

Priya, both suppliers will review it. Beth, escalation wording is being added. Interface and safety approvals still outstanding; no finished handover claimed.

13points

Discussion closed

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