View Single Post
  #6   Spotlight this post!  
Unread 14-07-2015, 07:58
IKE's Avatar
IKE IKE is offline
Not so Custom User Title
AKA: Isaac Rife
no team (N/A)
Team Role: Mechanical
 
Join Date: Jan 2008
Rookie Year: 2003
Location: Michigan
Posts: 2,149
IKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond repute
Re: Design Documentation Best Practices

Thank you all for sharing so far. One of the benefits of South East Michigan is that you can visit with teams and have lunch with friends that run/have run teams.
I had lunch the other day with two mentors that were the only technical mentors for a team for several years. While this was not the most competitive team, it often did very well, especially considering that there was a very high turn-over with their school, so they had a bit of "perpetual rookie syndrome" from the student perspective.
These mentors said a lot of their success was due to "standard work". IE, there are a set of chassis calculations they run for geartrain analysis that leads the design effort. There is a period of rule reading, and then strategic objective ranking, and several other exercises.
The benefit of the standard work was not allowing simple things to fall through the cracks or for the knowledge to fall to the side as "we always use 8 inch wheels..." and other best practices that turn into assumptions.

This "standard work" reminded me a lot of the influence and practices I read about in "The checklist manifesto". I originally read this book as I thought it would help me make better checklists for pit/match preparation. While reading it, I realized it has a lot of potential for utilizing a Design Checklist.
The team I worked with this year did not use such a list, and after starting build, we realized a very awkward problem. We were 1/2" short in several directions from having a good battery placement. We ultimately found a compromise, but had we used a checklist to verify placement of key components before starting build, we would ahve realized the issue, and just designed in the chassis the extra 1/2". This would have dropped the batter position about 4 inches lower, which would have been beneficial from a Center of Gravity perspective.

What items might a Chassis Standard Work Checklist include?