Fairino FR10: Our saved handling job needs a better handover

CallumArcher0360 · 27 Aug 2026, 02:53 UTC

Reply to discussion
CA
CallumArcher0360
I taught our Fairino FR10 job for tray-to-fixture loading with a molded spacer in a supervised assembly training cell. Everyone can start it, but an empty pocket or interrupted run means a call to me. I don't think this is attitude. Our handover covered a clean run and left the awkward decisions out.

19 replies

TH
TheoChen1193
Replying to CallumArcher0360

@CallumArcher0360 Have you asked operators to explain the restart instruction in their own words? You may find one sentence means several different things to the team.

19 points
CA
CallumArcher0360
Replying to TheoChen1193

I tried that in a discussion. Several people read the same restart line differently. So yes, we've handed over an instruction that doesn't agree with itself.

16 points
TH
TheoChen1193
Replying to CallumArcher0360

Rewrite that line around the visible condition, permitted next step and when to call for help. Have the responsible integrator check it, then repeat the teach-back without prompting.

19 points
CA
CallumArcher0360
Replying to TheoChen1193

How do I stop teach-back feeling like a test of the operator? The wording was mine. I don't want to make that their failure.

11 points
KA
KaiAdams0106
Replying to CallumArcher0360

@CallumArcher0360 On my setup, I asked people to find where my guide forced them to guess. That invited corrections instead of making them defend a wrong answer.

3 points
TH
TheoChen1193
Replying to TheoChen1193

Once the recovery sheet is clear and available at the controls, the team should no longer need to call you about these interruptions.

23 points
AL
AlexBell0646
Replying to TheoChen1193

That assumes a known, permitted recovery exists for every displayed condition. Clearer documentation can't compensate for uncertainty about whether the tool is holding something.

23 points
TH
TheoChen1193
Replying to AlexBell0646

@AlexBell0646 You're right; I promised too much from a sheet. The guide should support defined recoveries and clearly escalate unknown states. Some calls are the correct outcome.

16 points
CA
CallumArcher0360
Replying to TheoChen1193

@TheoChen1193 Our original handover only showed an empty gripper at startup. It never covered an interruption with the workpiece still held. That's a real gap.

17 points
HA
HanaBarnes0535
Replying to CallumArcher0360

@CallumArcher0360 I'm wondering whether selecting the current pocket would allow recovery. Does the held-workpiece case mean a pocket number alone can't explain what should happen?

20 points
TH
TheoChen1193
Replying to HanaBarnes0535

The pocket number alone doesn't establish the tool and destination conditions. Your integrator needs to define how those are confirmed and which recovery, if any, is permitted.

20 points
KA
KaiAdams0106
Replying to TheoChen1193

On my own cell, changing the index became folklore: ask the person who 'knows the trick'. Replacing that with a defined escalation made the uncertainty visible.

1 points
CA
CallumArcher0360
Replying to KaiAdams0106

@KaiAdams0106 An operator also spotted that our screen and printed guide use different names for the same step. I wrote both. Lovely bit of self-sabotage.

21 points
TH
TheoChen1193
Replying to CallumArcher0360

Align the printed step names with the installed display and verify that any illustrations correspond to that version. This removes an avoidable translation task during recovery.

15 points
AL
AlexBell0646
Replying to TheoChen1193

Terminology should be consistent in meaning as well as spelling. Verify that matching labels refer to the same physical condition wherever they appear.

15 points
HA
HanaBarnes0535
Replying to AlexBell0646

How should the practice progress from understanding the conditions to using the machine? Would pictures or a discussion be a useful starting point before supervised equipment work?

15 points
TH
TheoChen1193
Replying to HanaBarnes0535

Start with discussion or offline examples. Any equipment exercise should use a planned, supervised procedure; don't create surprise faults to see what someone does.

18 points
CA
CallumArcher0360
Replying to TheoChen1193

@TheoChen1193 The different interpretations have identified a concrete documentation issue. We haven't completed the reviewed guidance, so the operators still need support for conditions it doesn't explain clearly.

19 points
TH
TheoChen1193
Replying to CallumArcher0360

@CallumArcher0360 You've found something specific to improve. Keeping support available fits the unfinished guidance.

21 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.