HOME  |  NEWS  |  BLOGS  |  MESSAGES  |  FEATURES  |  VIDEOS  |  WEBINARS  |  INDUSTRIES  |  FOCUS ON FUNDAMENTALS
  |  REGISTER  |  LOGIN  |  HELP
Comments
View Comments: Newest First|Oldest First|Threaded View
<<  <  Page 2/2
Tim
User Rank
Platinum
Data
Tim   7/31/2012 9:44:19 PM
NO RATINGS
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.

GlennA
User Rank
Gold
Re: Engineering communication
GlennA   7/31/2012 9:33:36 AM
NO RATINGS
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.

naperlou
User Rank
Blogger
Re: Engineering communication
naperlou   7/31/2012 8:58:26 AM
NO RATINGS
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.

notarboca
User Rank
Gold
Engineering communication
notarboca   7/31/2012 8:47:54 AM
NO RATINGS
Wow, sounds like a lot of hardship could be avoided by a conference between Ladder I and Ladder II as to coordinating build orders.  Sort of reminds me of "how spec'd vs. how built".

<<  <  Page 2/2


Partner Zone
Latest Analysis
This year, Design News is getting a head start on the Fourth of July celebration. In honor of our country and its legacy of engineering innovation -- in all of its forms -- we are taking you on an alphabetical tour through all 50 states to showcase interesting engineering breakthroughs and historically significant events.
Software developers beware: Your open-source components may not be secure.
For companies that have gone into corporate venturing, sponsoring and nurturing startup companies, the subsequent IP transfer is tricky.
Learn how to build Raspberry Pi controllers using Python during this free Continuing Education Center class presented by Design News and Digi-Key.
Earlier this year paralyzed IndyCar drive Sam Schmidt did the seemingly impossible -- opening the qualifying rounds at Indy by driving a modified Corvette C7 Stingray around the Indianapolis Motor Speedway.
More:Blogs|News
Quick Poll
The Continuing Education Center offers engineers an entirely new way to get the education they need to formulate next-generation solutions.
Jul 6 - 10, Building Raspberry Pi Controllers with Python
SEMESTERS: 1  |  2  |  3  |  4  |  5  |  6 |  7


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.
Learn More   |   Login   |   Archived Classes
Twitter Feed
Design News Twitter Feed
Like Us on Facebook

Sponsored Content

Technology Marketplace

Copyright © 2015 UBM Canon, A UBM company, All rights reserved. Privacy Policy | Terms of Service