Your first robot should not be your hardest job
Most shops instinctively point automation at their worst problem. That instinct is right about where the pain is and wrong about where to start.
When we ask a plant owner what they would automate first, the answer is usually the job that hurts most: the one nobody will staff, the one with the injury history, the one that eats the schedule. That is a good instinct about priority and a poor instinct about sequence, because the jobs that hurt most are frequently the jobs that are hardest to automate.
There is a real skill curve here, and it is not about programming. It is about learning how your parts present, how your fixtures need to hold things, who owns the cell when the person who set it up is on vacation, what happens when it faults at two in the morning, and how a changeover actually goes on your floor rather than in a proposal. Those lessons are cheap to learn on a forgiving project and expensive to learn on a hard one.
Palletizing and machine tending are the usual good first projects. The part presentation is controlled, the failure modes are visible, and if the cell stops, somebody can step in and keep production running while you sort it out. Press brake tending is the opposite: it is the deepest integration we deal with, the tooling and regrip strategy have to be right before it works at all, and when it stops, your brake stops.
This is not an argument for automating something trivial. A first project should still be worth doing on its own merits, or the organization will correctly conclude the whole thing was a distraction. It is an argument for picking a project where the consequence of getting something wrong is a delayed pallet rather than a stopped line.
There is an organizational reason too. Your second project will go dramatically better than your first, whatever it is, because by then somebody in the building understands how these things behave. Spending that learning on a job where mistakes are recoverable is simply cheaper than spending it on the job that carries your schedule.
So when a shop tells us their worst job is press brake tending and they want to start there, we usually say what we would say to a friend: start somewhere else, get one working, then come back to this one in eighteen months with a team that knows what it is doing. The hard job will still be there, and you will be far better equipped to solve it.
Pick a first project where a failure delays a pallet rather than stops the plant. The hard job goes far better as your second or third.
Put it to the test on your own job
Tell Joe what you are running and he will apply this to your numbers, including telling you when a robot is the wrong answer.
More notes