Our 112 starting batch doesn't answer the maintenance question (Fairino FR10)

ZaraAbbott0047 · 29 Aug 2026, 05:58 UTC

Reply to discussion
ZA
ZaraAbbott0047
I've sunk a lot of effort into getting Fairino FR10 doing pouch-to-tray loading with a small bagged hardware kit in a shared product packing bench, starting with 112. The motion works, but the products keep changing and each new bag shape needs more presentation work. I'm attached to this setup and increasingly unsure the complete process is worth maintaining

15 replies

AN
AnilBarnes0549
Replying to ZaraAbbott0047

@ZaraAbbott0047 What happens when you include fixture adjustment and operator help in the comparison with manual packing? That's the process you're deciding whether to keep.

7 points
ZA
ZaraAbbott0047
Replying to AnilBarnes0549

Including fixture work and operator assistance leaves our manual baseline competitive. The motion is repeatable after preparation, but preparing the changing packages keeps expanding beyond what we originally allowed

3 points
AN
AnilBarnes0549
Replying to ZaraAbbott0047

Use that comparison for a bounded stop-or-continue review: remaining work, likely repeat demand and a spending limit. Agree what result could justify more effort before another fixture revision.

21 points
ZA
ZaraAbbott0047
Replying to AnilBarnes0549

How much weight should the effort already spent have? I know it's gone, but closing this still feels like throwing the work away

8 points
TH
TheoAbbott0062
Replying to ZaraAbbott0047

On my own packing trial, repeated input changes led us to stop. Preserving the fixture designs and trial observations made the learning available without requiring the application to become a deployment.

5 points
AN
AnilBarnes0549
Replying to AnilBarnes0549

If the manual baseline is still competitive, I'd close it. You've already got the answer.

22 points
WI
WillAdams0139
Replying to AnilBarnes0549

@AnilBarnes0549 The baseline is relevant, but continuation also depends on remaining effort and credible repeat work. Those haven't been established, so an immediate closure recommendation goes beyond the evidence.

14 points
AN
AnilBarnes0549
Replying to WillAdams0139

Fair correction. The baseline supports a review, not an automatic stop. Compare the remaining work and demand first; closing is one possible result, not the assumed one.

12 points
ZA
ZaraAbbott0047
Replying to AnilBarnes0549

I've checked the work coming in. There's little repetition of the setup we've demonstrated. That worries me more than whether another gripper tweak could work

7 points
TO
TobyBell0666
Replying to ZaraAbbott0047

@ZaraAbbott0047 Could you keep just one bag type automated? Or does that count as changing the question?

20 points
AN
AnilBarnes0549
Replying to TobyBell0666

It's worth assessing as a separate, narrower proposal if the demand exists. Give it its own costs and stopping conditions; it shouldn't inherit approval from the broader idea.

20 points
WI
WillAdams0139
Replying to AnilBarnes0549

The narrower option needs actual workload behind it. Identifying the orders it would serve keeps the review from assuming demand simply because a smaller success would be welcome.

22 points
ZA
ZaraAbbott0047
Replying to WillAdams0139

At present I can't identify sufficient repeat work to support that narrower application. I'll retain it as an unproven option rather than treating it as our agreed direction

3 points
ZA
ZaraAbbott0047
Replying to ZaraAbbott0047

I've decided to pause open-ended fixture work and use a bounded continuation review. More development depends on demand and a credible whole-process case; I can accept a stop decision if that case isn't there

5 points
AN
AnilBarnes0549
Replying to ZaraAbbott0047

@ZaraAbbott0047 That resolves how to make the decision without pretending the application is already settled. The pause gives the review a real boundary.

22 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.