3 hours every other day? Sorry, not enough time in there.
A week for conceptual design is too long. 3 days
2 weeks for narrow design is too long. 1 week. But you are including part fabrication time in there, so maybe 2 weeks, if at the end you have almost all the bits and mostly need to assemble it all.
Quote:
Originally Posted by F22Rapture
- How many people do you have on your teams?
- What is your subteam breakdown like? How many programmers, how many designers.
- When do you start building in some capacity? When do you have something drivable?
- How many people participate in the nitty-gritty of turning concepts into blueprints?
- How much time do you spend training?
- At what point in the 6 weeks is your robot "complete?" (in the context of fully-functional)
|
1. 80-ish
2. Programming has 4-6, electrical 6-8, pneumatics 4, mechanical 18, plus integration & testing (5). The rest are CAD, non-technical, construction (e.g., the field elements), and a few are just consuming oxygen.
2a. Everyone has input to the design, but I'd guess maybe 16 are actively designing parts.
3. Day 4 (Wednesday) the drivetrain team goes off and does their thing. It's driveable week 2.
4. Blueprints? What's that?
Our prototypes are our blueprints. Unfortunately our CAD team follows later.
5. 8 sessions x 4 hours each in the fall, really aimed at new team members (taught by existing team members).
6. Never, but almost there in week 5.