When I asked Bruce Welty what the warehouse robot did, he called it "a conveyance device." The robot moved from location to location. A screen told a person which item to take from a shelf and place in a box. After the pick, the robot moved to its next location.
That description gives automation a clear boundary. The machine carried distance. The person completed the physical pick. Software connected the customer's order to both. The design becomes easier to understand when you follow the work instead of starting with the machine.
The aisle revealed what needed to move
Bruce Welty said the system was built to remove as much walking as possible and simplify the moment when a person selected an item. His team cared about seconds because the same task happened at high volume. The aim was not to make the robot perform every part of the job. It was to stop spending so much human effort on travel around the useful task.
That distinction makes the automation question more precise. Which part of the work is movement, which part needs a person, and what information has to arrive before either can act?
The click depended on software no one could see
Bruce Welty described the first successful pick by tracing it back to a customer clicking a buy button. That action triggered a robot in Massachusetts, but only because several systems passed the instruction from the order to the warehouse.
The software layer mattered when Bruce searched for a replacement robotics system. He found machines that could move, but they lacked the business software his operation needed. His team concluded that building the physical robot was less complicated than building the software required to make it useful in their workflow.
The visible machine may attract the attention. The coordination behind it determines whether the order, location, person, and next action stay connected.
Accuracy needed another pair of eyes
At the volume Bruce Welty described in 2017, even a high accuracy rate could leave many wrong orders. His team tried to prevent a person from selecting the wrong item or placing it in the wrong bin. They also accepted that errors would still occur.
Their response was a separate verification step. Another person checked the work and corrected an error before shipment. Automation did not remove quality ownership from the process. It made the first control visible and left a second control in place for what the system missed.
Sketch the order before choosing the tool
Take one repetitive flow and trace it from the request through movement, human action, and verification. Mark what information starts each step. Then name what a tool would carry, what stays with a person, and where a separate check belongs.
If the machine's role or the verification step remains vague, the team has learned something useful before buying technology. The process needs a clearer definition first.
Bruce Welty ended the conversation with the question that belongs at the start of any automation decision: "What's the business problem we're trying to solve?" Following one order makes the answer concrete. It shows where the robot belongs, where the person belongs, and where the work still needs proof that the right item reached the right place.
