GOTCha Chart - Revision history

Jwb: /* Project GOTChA chart */

2018-10-19T20:46:39Z

‎Project GOTChA chart

Jwb: /* Course schedule */

2018-10-19T20:27:11Z

‎Course schedule

Jwb: /* Project GOTChA chart */

2018-10-19T20:26:19Z

‎Project GOTChA chart

Jwb: 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 ..."

2018-10-19T19:43:41Z

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 ..."

New page

=== 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|GOTChA chart]].

{| border=1 width=100%
|- valign=top
| width=50% |
==== Goals ====
* Build an integrated team (SCI-Arc + Caltech) that can win the 2011 Solar Decathlon
* 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 our design
| width=50% |

==== Technical Challenges ====
* Bring 20-30 new Caltech students from diverse backgrounds and skill levels up to speed quickly
* Integration of SCI-Arc and Caltech activities (people, goals, schedule, deliverables)
* Some existing baseline designs are not very complete; need more work and re-validation
* Some subsystems have no baseline design
|- valign=top
| width=50% |

==== Objectives ====
* Assign students to subsystems and teams, with linkages between teams with overlapping functionality or interfaces
* For subsystems with existing baseline designs:
** 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 SCI-Arc teams
** 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
** Evaluate technology options that can be incorporated into our design and perform cost analysis for each
* For subsystems without existing baseline designs:
** 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 SCI-Arc teams
** 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
** Provide a design capable of full capability (max points) with net-zero energy consumption for 95th percentile day
** Provide a design capable of 90% max points on worst case day (over last 20 years)
| width=50% |

==== Approach ====
* Stick to summer 2010 system architecture decisions; avoid re-inventing the wheel
* Hold off on alterations to the baseline until we have a fully analyzed, documented and costed baseline
* Schedule planning event with Caltech + SCI-Arc to help people meet each other and align goals, milestones and schedule
* Make use of the project wiki as a mechanism to document and enhance team communication
* 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
* Milestones
** 13 Oct: each subsystem team knows what SD rules apply to their subsystem + understand existing baseline design
** 27 Oct: revalidated/preliminary baseline design computations for each subsystem (depending on initial state); shared decision making between SCI-Arc and Caltech
** 10 Nov: rigorously analyzed and documented baseline designs complete for all subsystems
** 23 Nov: design development documentation complete and delivered to DOE
** 10 Dec: final reports for each student due, with complete subsystem documentation available on project wiki
|}
<br>
=== Course schedule ===

{| border=1 width=100%
|-
|| Week || Date || Topic || Reading/Activities || Homework
|- valign=top
|
===== 1 =====
| 27 Sep (M)
| [[Media:L1_kickoff-27Sep10.pdf|Organizational meeting]]
* Reed: Solar Decathlon overview [15 min]
* Fei: Baseline overview [15 min]
* Richard: CS/EE/ME 75 organization [20 min]
* Q&A [5 min]
|
* Submit [[Media:cem75_signup-fa10.pdf|signup and scheduling sheet]] by Wed @ noon to box outside 109 Steele
* Read SD rules and baseline design descriptions (see HW #1)
* Team assignments (required for HW #1) will be available by Thursday (30 Sep)
| [[CS-EE-ME 75 Fall 2010 Homework 1|HW #1]]
* SD competition rules
* Subsystem baseline description
* Wiki user page creation
|-
|

===== 2 =====
| 4 Oct (M)
| Project schedule
* Overall SD schedule [Reed]
* SCI-Arc/Caltech master schedule for fall [Reed]
* GOTChA charts [Richard]
* Milestone "party" (9 Oct?)
|
Team meetings start. Joint scheduling event with Sci-Arc on 9 Oct (?)
| [[CS-EE-ME 75 Fall 2010 Homework 2|HW #2]]: Team schedules, subsystem GOTChAs
|-
|

===== 3 =====
| 11 Oct (M)*
| System specifications
* Baseline specifications [Fei]
* Documentation format [Reed]
|
| 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)
|}

← Older revision		Revision as of 20:27, 19 October 2018
Line 47:		Line 47:
	\|}		\|}
	<br>		<br>
−
−	~~=== Course schedule ===~~
−
−	~~{\| border=1 width=100%~~
−	\|-
−	~~\|\| Week \|\| Date \|\| Topic \|\| Reading/Activities \|\| Homework~~
−	~~\|- valign=top~~
−	\|
−	~~===== 1 =====~~
−	~~\| 27 Sep (M)~~
−	~~\| [[Media:L1_kickoff-27Sep10.pdf\|Organizational meeting]]~~
−	* Reed: Solar Decathlon overview [15 min]
−	* Fei: Baseline overview [15 min]
−	* Richard: CS/EE/ME 75 organization [20 min]
−	* Q&A [5 min]
−	\|
−	* Submit [[Media:cem75_signup-fa10.pdf\|signup and scheduling sheet]] by Wed @ noon to box outside 109 Steele
−	* Read SD rules and baseline design descriptions (see HW #1)
−	* Team assignments (required for HW #1) will be available by Thursday (30 Sep)
−	~~\| [[CS-EE-ME 75 Fall 2010 Homework 1\|HW #1]]~~
−	* SD competition rules
−	* Subsystem baseline description
−	* Wiki user page creation
−	\|-
−	\|
−
−	~~===== 2 =====~~
−	~~\| 4 Oct (M)~~
−	~~\| Project schedule~~
−	* Overall SD schedule [Reed]
−	* SCI-Arc/Caltech master schedule for fall [Reed]
−	* GOTChA charts [Richard]
−	* Milestone "party" (9 Oct?)
−	\|
−	~~Team meetings start. Joint scheduling event with Sci-Arc on 9 Oct (?)~~
−	~~\| [[CS-EE-ME 75 Fall 2010 Homework 2\|HW #2]]: Team schedules, subsystem GOTChAs~~
−	\|-
−	\|
−
−	~~===== 3 =====~~
−	\| 11 Oct (M)*
−	~~\| System specifications~~
−	* Baseline specifications [Fei]
−	* Documentation format [Reed]
−	\|
−	~~\| 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)~~
−	\|}

@@ Line 1: / Line 1: @@
 === 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|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_Background | GOTChA chart]].
 {| border=1 width=100%

@@ Line 7: / Line 7: @@
 | width=50% |
 ==== Goals ====
-* Build an integrated team (SCI-Arc + Caltech) that can win the 2011 Solar Decathlon
+* 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
-* Evaluate and explore options for providing some technology ''sizzle'' in our design
+* Evaluate and explore options for providing some technology ''sizzle'' in the system design
 | width=50% |
 ==== Technical Challenges ====
-* Bring 20-30 new Caltech students from diverse backgrounds and skill levels up to speed quickly
+* Bring 20+ new Caltech students from diverse backgrounds and skill levels up to speed quickly
-* Integration of SCI-Arc and Caltech activities (people, goals, schedule, deliverables)
+* Integration of JPL and Caltech activities (people, goals, schedule, deliverables)
-* Some existing baseline designs are not very complete; need more work and re-validation
+* Many existing baseline designs are not very developed; need more work and re-validation
 * Some subsystems have no baseline design
 |- valign=top
@@ Line 24: / Line 24: @@
 * For subsystems with existing baseline designs:
 ** 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 SCI-Arc teams
+** 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
 ** 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:
 ** 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 SCI-Arc teams
+** 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
 * 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) with net-zero energy consumption for 95th percentile day
+** Provide a design capable of full capability (max points)
-** Provide a design capable of 90% max points on worst case day (over last 20 years)
+** Provide a design capable of 90% max points on worst case
 | width=50% |
 ==== Approach ====
-* Stick to summer 2010 system architecture decisions; avoid re-inventing the wheel
+* Analyze, document, and cost a baseline solution
-* Hold off on alterations to the baseline until we have a fully analyzed, documented and costed baseline
+* Schedule planning event with Caltech + JPL to help people meet each other and align goals, milestones and schedule
-* Schedule planning event with Caltech + SCI-Arc to help people meet each other and align goals, milestones and schedule
+* Make use of the project wikis, websites, Slack, Git, etc. as a mechanism to document and enhance team communication
-* Make use of the project wiki as a mechanism to document and enhance team communication
 * 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
 * Milestones
-** 13 Oct: each subsystem team knows what SD rules apply to their subsystem + understand existing baseline design
+** TBD
-** 27 Oct: revalidated/preliminary baseline design computations for each subsystem (depending on initial state); shared decision making between SCI-Arc and Caltech
-** 10 Nov: rigorously analyzed and documented baseline designs complete for all subsystems
-** 23 Nov: design development documentation complete and delivered to DOE
-** 10 Dec: final reports for each student due, with complete subsystem documentation available on project wiki
 |}
 <br>
 === Course schedule ===