News for hackers. Stuff that matters.
Re:Tesla to raise $1B by grizzles on Wednesday March 15, 2017 @07:43PM (#13881009)
It was an exercise in creative problem solving. I'd query the data to find out where on the line the most (costly x incidence) problems were occurring and then devise a solution. If a worker was scratching the paint every time he put his tool down the secure a fastener, we'd get a heavy rubber guard fabricated, change his man assignment and have him put down the guard before he did his little peice, or even better change the tool if that was possible. If you are curious, yes there were workers who would damage the vehicle every time and let it go to rework. Don't even get me started on labor. :)
Re:Tesla to raise $1B by rblatz on Wednesday March 15, 2017 @08:42PM (#13881337)
Let me guess when asked why they said "that's how we've always done it"
Re:Tesla to raise $1B by grizzles on Wednesday March 15, 2017 @09:08PM (#13881495)
Haha, yep. That or a complaint about their man assignment changing and it being hard to keep up.
Re:Tesla to raise $1B by alphapapa on Wednesday March 15, 2017 @11:17PM (#13882190)
How did they gather comprehensive data like that? Seems like you'd need an employee to watch every employee, recording everything they did.
Re:Tesla to raise $1B by grizzles on Thursday March 16, 2017 @12:09AM (#13882417)
The line is Body Shop->Paint->Trim->Chassis->Final Vehicle.

Final Vehicle is concerned with testing and certification and whatever other finishing touches need to be performed. It also operates the repair department, and the 'yard' with all the defect jobs. Our yard was so packed the company was renting new yards away from the factory.

The repairmen who worked in the bays and yard were stone cold experts on the vehicles and they kept written logs. Those logs were typed up and put in the database by the office clerks. These were mostly signal. There were also networked terminals at some stations but not all down the line.

Finding the root cause of an issue was basically like git-bisect. You knew where a part was added and where it ended up. So you just needed to narrow it down. For a high priority issue, I'd go do a visual inspection myself at the mid station before a part got covered by another part. Broken? Go to the mid station between here and start. Not broken, go the other way. We got stumped sometimes, but mostly we could narrow it down pretty fast. For the workers, it's impossible to lose your job so there isn't a care factor about covering up shoddy workmanship.

Re:Tesla to raise $1B by bobsil1 on Thursday March 16, 2017 @12:19AM (#13882447)
Binary search :)
Re:Tesla to raise $1B by dilemma on Wednesday March 15, 2017 @08:27PM (#13881265)
>Don't even get me started on labor. :)

Wow.

Re:Tesla to raise $1B by softawre on Wednesday March 15, 2017 @09:56PM (#13881733)
Well, programmers do the same thing.

Blah blah make better software blah blah world makes better idiots.