Difference between revisions of "GOTCha Chart"
From Robotics
(Created page with "=== Project GOTChA chart === This quad chart gives a snapshot of the planned activities for the term, at a high level. This information is presented here in the form of a ...") |
(→Project GOTChA chart) |
||
| Line 7: | Line 7: | ||
| width=50% | | | width=50% | | ||
==== Goals ==== | ==== Goals ==== | ||
| − | * Build an integrated team | + | * Build an integrated team of Caltech Undergraduates, Graduates, and JPL Engineers that can win the DARPA SubTerranean Challenge |
* Complete the design development phase of the Solar Decathlon competition and submit design documents on time | * Complete the design development phase of the Solar Decathlon competition and submit design documents on time | ||
| − | * Evaluate and explore options for providing some technology ''sizzle'' in | + | * Evaluate and explore options for providing some technology ''sizzle'' in the system design |
| width=50% | | | width=50% | | ||
==== Technical Challenges ==== | ==== Technical Challenges ==== | ||
| − | * Bring 20 | + | * Bring 20+ new Caltech students from diverse backgrounds and skill levels up to speed quickly |
| − | * Integration of | + | * Integration of JPL and Caltech activities (people, goals, schedule, deliverables) |
| − | * | + | * Many existing baseline designs are not very developed; need more work and re-validation |
* Some subsystems have no baseline design | * Some subsystems have no baseline design | ||
|- valign=top | |- valign=top | ||
| Line 24: | Line 24: | ||
* For subsystems with existing baseline designs: | * For subsystems with existing baseline designs: | ||
** Revalidate the baseline design computations and verify that baseline can achieve maximum points for relevant competition(s) | ** Revalidate the baseline design computations and verify that baseline can achieve maximum points for relevant competition(s) | ||
| − | ** Communicate and agree on specifications and choices with IPT and | + | ** Communicate and agree on specifications and choices with IPT and JPL teams |
** Perform model-based analysis of system performance in a form that can be used for trade-off studies | ** Perform model-based analysis of system performance in a form that can be used for trade-off studies | ||
** Document the baseline design in a manner that is compatible with design development phase deliverable | ** Document the baseline design in a manner that is compatible with design development phase deliverable | ||
| Line 30: | Line 30: | ||
* For subsystems without existing baseline designs: | * For subsystems without existing baseline designs: | ||
** Analyze options design with performance, cost, electrical load, thermal load estimates | ** Analyze options design with performance, cost, electrical load, thermal load estimates | ||
| − | ** Establish a baseline design that can achieve maximum points for relevant competition(s), in agreement with IPT and | + | ** Establish a baseline design that can achieve maximum points for relevant competition(s), in agreement with IPT and JPL teams |
** Document the baseline design in a manner that is compatible with design development phase deliverable | ** Document the baseline design in a manner that is compatible with design development phase deliverable | ||
* Develop and maintain system-level cost and energy budgets and use these to verify ability to maximize points on engineering-driven competitions | * Develop and maintain system-level cost and energy budgets and use these to verify ability to maximize points on engineering-driven competitions | ||
| − | ** Provide a design capable of full capability (max points) | + | ** Provide a design capable of full capability (max points) |
| − | ** Provide a design capable of 90% max points on worst case | + | ** Provide a design capable of 90% max points on worst case |
| width=50% | | | width=50% | | ||
==== Approach ==== | ==== Approach ==== | ||
| − | * | + | * Analyze, document, and cost a baseline solution |
| − | + | * Schedule planning event with Caltech + JPL to help people meet each other and align goals, milestones and schedule | |
| − | * Schedule planning event with Caltech + | + | * Make use of the project wikis, websites, Slack, Git, etc. as a mechanism to document and enhance team communication |
| − | * Make use of the project | + | |
* Identify individual students who will be responsible for insuring good cross-project integration between appropriate groups | * Identify individual students who will be responsible for insuring good cross-project integration between appropriate groups | ||
* Develop analytical or computational models demonstrating that specifications can be met | * Develop analytical or computational models demonstrating that specifications can be met | ||
* Milestones | * Milestones | ||
| − | ** | + | ** TBD |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
|} | |} | ||
<br> | <br> | ||
| + | |||
=== Course schedule === | === Course schedule === | ||
Revision as of 12:26, 19 October 2018
Contents
Project GOTChA chart
This quad chart gives a snapshot of the planned activities for the term, at a high level. This information is presented here in the form of a GOTChA chart.
Goals
|
Technical Challenges
|
Objectives
|
Approach
|
Course schedule
| Week | Date | Topic | Reading/Activities | Homework |
1 |
27 Sep (M) | Organizational meeting
|
|
HW #1
|
2 |
4 Oct (M) | Project schedule
|
Team meetings start. Joint scheduling event with Sci-Arc on 9 Oct (?) |
HW #2: Team schedules, subsystem GOTChAs |
3 |
11 Oct (M)* | System specifications
|
HW #3: Project specifications | |
4 |
18 Oct (M) | System modeling | HW #4: Baseline model and analysis | |
5 |
25 Oct (M)* | Design review process | Design reviews (midterms) | |
6 |
1 Nov (M) | Team presentation | ||
7 |
8 Nov (M)* | Team presentation | ||
8 |
15 Nov (M)* | Team presentation | Design review | |
9 |
22 Nov (M) | Project review | Building information model, design drawings and project manual due | |
10 |
29 Nov (M) | Lessons learned and plans for second term | Project documentation due (end of finals) |
