Skip to main content

Day 5

Today I got to learn more about assemblies in Autodesk Inventor, the CAD software. The team I'm working on has an assembly model with all the parts they are manufacturing for Pratt and Whitney so once I got to the assembly section of the excel sheet I had to isolate parts and put together the assembly in cad instead of just finding one part and taking a screenshot. This was the first time I had worked with assemblies in CAD instead of just parts. I had a lot of problems at first. I was using the wrong shortcuts, opening more parts than I meant to, and navigating the blueprint to know which parts to select was also confusing.

Figuring out the blueprint was the first solution. I read through the print to understand the levels of the assembly before I continued learning the program. Then once I was comfortable with what I had to do, I did my research about the program and found a very easy way to hide pieces of the model so I could only see what I needed for the screenshots. Once I did that and took the screenshots it was back to putting them into excel. I had a few more problems with the excel dashboard programming but I've gotten very comfortable fixing them because of all the problems I've had so I debugged much quicker today.

Comments

Post a Comment

Popular posts from this blog

Day 2

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...
1 comment
Read more

Expectations and Goals

I have known I wanted to be an engineer for a long time. I enjoy problem-solving and have always had excellent spatial reasoning. I began tinkering at a young age with old computers and RC cars. At 11 I ruined one of my RC cars trying to drive it on water. I was still so happy because it skimmed on water for a good three seconds before the frame caught and dragged it down. The only failure was not sealing off the electronics well enough but I was so happy to have done something without a kit or instructions. It was all around fun. I kept going with legos, robots, computer programs, I got to know my way around a wood shop freshmen year and learned about 3d printing and machine guided cutting from CNC machining to laser cutting. As I leave for college I feel completely prepared to tackle any engineering challenge that comes my way. I have a strong base in math and calculus that can only grow in the years to come. And an even stronger base of experience with tinkering and making ...
1 comment
Read more

Day 4

There exists no perfect environment and, as an engineer, it is made my goal to make a perfect environment. I made the first sheet I was working on work. Since I worked out the bugs on that one and improved the functionality I got an explanation of the 5s system and Toyotas Lean engineering philosophy to understand the impact of what I was doing. The Lean system and the 5s system are philosophies that all good engineering companies hold which say the organization of work and the standardization upfront pay off astronomically in the long run. Tyler, who I work with did his thesis on the last company he worked at about implementing Lean engineering, and the impact of it on the company because the company didn't hold the philosophy at all. Tyler determined that the company could save $50,000 a year by organizing workspaces, purchasing tools for each workspace instead of making the production team walking across the plant when they need a new tool on each assembly. Needless ...
1 comment
Read more