View Single Post
  #7   Spotlight this post!  
Unread 02-04-2010, 20:46
Andrew Schreiber Andrew Schreiber is offline
Data Nerd
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,057
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: Frustrations with Minor Technicalities

Quote:
Originally Posted by 45Auto View Post
You are aware that we're up to Update 19, I hope.

The rule you quoted from Update 6 was revised in Update 7, dated 2/2/2010, 3 weeks before ship date. It hasn't been changed since then:
When do you make your chassis? While I would love to have the ability to crank out a chassis after doing prototypes but when your team consists of 5 students and a handful of mentors who are all taking too many classes at college it takes all 6 weeks to field something that runs. The chassis was built during week 1. We missed it the bolts. Our bad.

But that is neither here nor there. It happened, we are solely to blame but now the question becomes, what can we do to make sure it doesn't happen. Does anyone have any solution that could help alleviate the combination of the inspectors not knowing all the rules (or just missing things) and of teams just missing things.

Perhaps the simple solution, before you bag/crate print out the inspection form and inspect yourself. I think from this point on I will be doing that. It is no promise you will catch everything but it should help. Is this a viable option for most teams?
__________________




.