Weight

[ChrisH]

Originally Posted by Mike Martus

There are several important concerns that have been brought up here.

1. The 130 weight is a design constraint, part of the challenge.
2. Safety - 130 divided by two persons 65 each that is still a lot of weight if you fall or have a distance to go. A Major safety concern.
3. Next year I believe that the battery will not be included in the weight and there may be a gain if say FIRST decides that 120 lbs is the weight without the battery. A net gain of about 4 pounds or more.

No matter what the limit is set at, I believe that there will always be the "pushing of the limit" to build the best durable machine.

Teams that are consistently designing and end up with weight problems need to look at their design process and make corrections in "Weight Management".

Some tips for Weight Management

1) "budget" no more than 90% of the weight limit. ie if the limit is 130 lbs then the total estimated weight of all systems should be no more than 117 lbs.

2) Identify and quantify non-negotiable weight first. So know how much your controller, breakers, lights etc. weigh. Subtract this weight from the budget.

3) what is left is available for adding non-essential systems. Note: depending on the game, a drive system may be negotiable.

4) Assign budgets for all subsystems based on criticality. A really critical system should have a bigger budget than a nice-to have.

5) Do a weight estimate for any proposed subsystem BEFORE you build it. Hint we've found that Inventor is pretty good at weight estimates if you put in the correct material data.

6) Use your estimates to trade off between systems.

7) Resist the temptation to say "I think I can get a couple of pounds out" and then use the lower number. Every item in your estimate should have documentation to back it up. If you think you can take weight out, fine. Prove it first, then change the number.

8) Track the weight of each subsystem continually. If possible weigh each part before it goes onto the robot.

9) Use a spreadsheet for your weight tracking. Constantly compare actual vs estimated weight. Beat on the designers of subsystems that are over weight to get the weight out. The spreadsheet can also be used to identify "heavy hitters". Items that are extraordinarily heavy (and thus prime targets for speed holes) or items that use a lot of weight for minimal functionality.

10) Assign a single person whose whole job is to make sure you meet weight. We call ours the "weight czar" a term that comes straight out of the aircraft biz. In fact, at the "bird factory" I work in, every program has a whole department dedicated to tracking the current estimated and actual weight of the aircraft. We wouldn't do that if we didn't think it was important, there too many other things we need to throw bodies at to waste them on something unimportant.

11) Remember that nothing ever gets done within the budget. That's why you only allowed 90% at the beginning, to account for unknowns and overruns. If that doesn't work this year, then next year cut the budget to 85%