Nov 16, 2026 | 863 words | 9 min read
18.6. Milestone 3 - Design Memo (Team)#
At a Glance
What you will do: Before you write any implementation code, create at least two substantively different designs. Each design pairs a hardware selection with a controller architecture. Compare the designs with a weighted decision matrix, commit to one, and specify it with a flowchart.
What you will submit: One Design Memo (PDF) per team.
The Milestone 4 acceptance test judges your implementation. This design memo is judged on your engineering decisions. The teaching team looks at whether you considered real alternatives, compared them against criteria that matter, and specified the chosen design precisely enough to build.
18.6.1. Required Sections#
Open a new MS Word document and include the following sections in your design memo.
1. Requirements Recap#
Carry forward the GHU-2 requirements from your Milestone 2 failure investigation. Use the revised version if you have one. Add the constraints from the Mission Brief annex that apply to your design. These are the actuator limits, the one-way valve, the lack of cooling, the lack of a dehumidifier, the known K30 fault, and the determinism requirement. Add the acceptance criteria from the primer. Every candidate must meet these numbers, and the \(600\ \text{kg}\) launch-mass ceiling is one of them.
Give the humidity requirement particular attention. Your M2 analysis showed what humidity did on GHU-1, and the hardware list explains the cause. GHU-2 has no actuator that removes moisture, and its only water input also raises humidity. In this section, assess whether the client’s \(40\%\) to \(60\%\) RH requirement is fully achievable with this hardware. If your answer is no, say so and propose a revised, achievable humidity requirement. State the evidence from M2 and the reasoning from the hardware that support the revision. You will revisit this assessment with your own test data in Milestones 4 and 5.
2. Candidate Designs (at least two)#
Present at least two substantively different designs. A design is a hardware selection (glazing and heater, from your Milestone 2 analysis) paired with a controller architecture. Candidates may differ in hardware, in architecture, or in both. The same design with different gain values does not count as a second candidate. For each candidate, include the following items.
The glazing and heater, and the estimated launch mass (glazing, heater, and battery)
What the hardware demands of the controller, including whether the heater saturates on the coldest nights and whether the glazing leaves the crop short of light in a dust storm
The strategy that controls each of the four actuators
How the design handles disagreement between the CO2 sensors
The state the controller remembers between ticks
A list of strengths and risks
Choose strategies from the primer. Mixing strategies across actuators is encouraged. Each candidate has a named owner, a different team member for each candidate, who develops and presents it. The team scores the matrix in the next section jointly.
3. Weighted Decision Matrix#
Compare the candidates in a Weighted Decision Matrix. Download the template and save as M3_WDM_team_#.xlsx.
Your team chooses the criteria. Possible criteria include expected performance, launch mass, complexity and the risk of getting it wrong, testability, and robustness to the storm and the K30 fault. In the matrix, you must justify both the criteria and their weights, in one sentence each.
In your design memo, explain why you chose these criteria and why one is worth more than another. Score the candidates, total the scores, and state the decision. If the matrix result surprised you and you overrode it, say so and defend the override.
4. The Chosen Design#
State the hardware selection (glazing and heater) and the estimated launch mass of the chosen design. Then create the flowchart and the parameter table described below. If the choice changes your Milestone 2 hardware, say what changed and why.
A flowchart of one complete control tick, from sensor readings in, through the decisions, to actuator commands out. It must show the CO2 sensor-trust rule, any integral and windup handling, and every clamp. Someone who has never met your team should be able to trace any sensor reading to its actuator response.
A short table of every tunable parameter in the design (gains, thresholds, the sensor-disagreement cutoff). Give your initial value and a one-line rationale for each. Milestone 4’s tuning log starts from this table.
5. AI Use Log#
Include an AI Use Log as an appendix to this memo. Follow the format in the AI Usage Policy, which also lists the uses of AI tools that it permits.
18.6.2. Submission#
Weighted Decision Matrix Submission
Submit your WDM with your technical report for milestone 3. DO NOT submit your WDM with your design memo.
Save your design memo as a PDF file (M3_design_memo_team_#.pdf) and submit as a
group to 18.6 Milestone 3 - Design Memo (Team) on Gradescope.
Submit before the deadline on the Course Schedule.
Learning Objectives
- UC02:
Schematic Representation of Systems - Describe engineering systems or processes using schematic diagrams that represent inputs, outputs, and accumulations.
- IF01:
Idea Generation - Generate a wide range of solution ideas, including non-obvious or combined approaches.
- EB04:
Metrics and Weighting - Justify evaluation metrics and weighting based on stakeholder priorities.
- EB06:
Reasoned Decision Explanation - Clearly articulate reasoning when evaluating alternatives or making decisions.
- PS05:
Problem Revision - Revise the problem statement based on new evidence or insights.
- EC02:
Recognize Limits, Trade-offs, and Confidence - Recognize limitations, trade-offs, and uncertainty in engineering work and communicate appropriate levels of confidence in conclusions.
- AI05:
Communicate clearly and effectively about AI usage and the choices surrounding it in a given field.