I made a map of the assemblies on the Side Wall project today. It took me pretty much all day because of how massive the project is. The map had drawings and lists of parts in each assembly so I got comfortable using AutoCAD and Inventor to make drawings which are how the process engineer puts drawings onto the Operation Sketches. This was a good experience because I got very comfortable making drawings and navigating AutoCAD to make drawings. The tree had the 100 level assembly, which is the whole side wall assembly. That branched out to the 200 level sub-assemblies. On the side wall, there are 29 sub-assemblies that I had to make drawings and lists for. Each of those sub-assemblies had at least one 300 level part that had to branch out further. Needless to say, this was a very large project. I'm happy I can make something that will have such an impact. Projects like this one are how I'm starting to understand Lean engineering and the 5s philosophy.
Today I learned a lot more about organization and documentation. Mark, my program manager, has an excel dashboard program that he uses to easily look up pieces and projects. He can look up jobs by Jedco's part number, the partner's part number, or the part's find number. It gives him back a lot of information about the part including tools used in the process, cost, quote, profit margins, and issues and comments. On one of the parts he was looking it up but none of the information was being brought back. So, in an effort to learn an important skill for engineering jobs and jobs in general, I taught myself Visual Basic, the language behind Excel formulas. At the end of the tutorial I was skimming and after about two hours of reading the code behind Mark's dashboard, I couldn't find any errors so I asked the person who wrote the code about the references and some clarifications about the code just to make sure I was clear on everything. At the end of it all, we realiz...
Comments
Post a Comment