It is interesting to see that the engineer came to you with the question about the robots. The engineer seemed to only pull some data from a server and did no real root cause analysis. Data is not always the only answer.
The coordination was in the build order documents. Each van was listed in order, and from Ladder I, through all of the Body Shop, Paint Shop, and Final Assembly, the build order document was the 'bible'. The problems happened when the 'bible' was not followed exactly. The spacing between frames was about 90 seconds. It took about 150 seconds for a crew to build a frame in Ladder I, so there were 2 build crews. If those 2 crews got out of sequence, either by skipping a frame or building a duplicate, problems happened. It was easy to spot a long frame / short floor or short frame / long floor mismatch, but others were not so easy.
Agreed. It also sounds like there could be more automation in the coordination of the "Ladders". Another alternative is to tag each assembly so that the stations can get the data from a central repository.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.