
choose realistic inputs, use our orbit simulation to test competing fire-watch plans and their trade-offs, and choose one with a weighted decision matrix.
Phase 4: Build
Do Now. Which of these is a realistic input for our orbit simulation, and why are the others not: an altitude of 50 km, 700 km, or 500,000 km?
Why is 50 km an unrealistic altitude for a satellite?
Mission designers, today you prototype. For an orbit, the prototype is a tested plan inside the simulation. You choose inputs (altitude, number of satellites, orbit type), run the model, and compare the outputs against the client’s criteria.
Step 1: criteria and constraints. Criteria: revisit (how often a new fire is seen), detail (how small a fire can be seen), latency (how fast data reach crews) and coverage of the whole region. Constraints: the partnership’s budget, the number of launches, satellite mass and responsible use of space.
Step 2: choose logical inputs. Low orbits from about 400 to 1,000 km (below 400 km drag shortens a satellite’s life quickly; our model cannot show that), and the geostationary altitude of 35,786 km. For detail, assume the same telescope on every satellite, so the pixel size grows in proportion to distance: 35,786/700 = 51 times coarser from geostationary orbit.
Worked example 1: four plans in the model.
| Plan (model output) | Altitude | Period | Orbits per day | Passes over the region | Detail (pixel size, relative) | Launches |
|---|---|---|---|---|---|---|
| A. One low polar satellite | 700 km | 98.6 min | 14.6 | About 2 a day | 1× | 1 |
| B. Four low satellites in one polar plane | 700 km | 98.6 min | 14.6 each | About 8 a day (the model assumes evenly spread) | 1× | 1–2 |
| C. One geostationary satellite | 35,786 km | 23.93 h | 1.00 | Continuous view | 51× coarser | 1 (larger rocket) |
| D. Hybrid: C plus two low polar satellites | 35,786 + 700 km | Both | — | Continuous, plus about 4 detailed passes | 51× and 1× | 3 |
Pass counts assume a polar orbit sees a given mid-latitude region about twice a day (one daytime and one nighttime pass), as real polar weather satellites do; detail figures are model ratios, not instrument specifications.
Worked example 2: the decision matrix. Mei’s team weights the criteria and scores each plan from 1 to 5:
| Criterion (weight) | A | B | C | D |
|---|---|---|---|---|
| Revisit (×3) | 1 → 3 | 3 → 9 | 5 → 15 | 5 → 15 |
| Detail (×3) | 5 → 15 | 5 → 15 | 1 → 3 | 4 → 12 |
| Latency (×1) | 3 → 3 | 3 → 3 | 5 → 5 | 4 → 4 |
| Cost (×2) | 5 → 10 | 3 → 6 | 3 → 6 | 1 → 2 |
| Total | 31 | 33 | 29 | 33 |
B and D tie at 33. A tie tells the team to look harder: B’s revisit score depends on the model’s assumption that four satellites in one plane spread their passes evenly through the day. Next lesson tests that assumption. The team also notes a trade-off it cannot score yet: every added satellite adds to the crowding of low orbit.
Interpreting results. A simulation result is a prediction about the real system. For each plan, write one sentence predicting what it would mean for crews on the ground, for example: “With plan A, a fire that starts just after a pass could burn for up to about 12 hours before it is seen.”
Run your spreadsheet for each plan, then answer.
Finish your team’s design record.
Record your criteria and constraints, the inputs you chose and why they are realistic, the model outputs for at least three plans, your weighted decision matrix with a reason for each weight, and your version 1.
Version 1 is chosen. Next lesson, a gallery critique and a hard look at the model’s assumptions.
Exit ticket: name one input you chose, why it is realistic, and one output the model predicted for it. What did the output tell you about the plan?
Materials: devices with the team spreadsheets, matrix templates, chart paper.
Setup: pass counts and detail ratios are simplified model outputs; say so. The twice-a-day pass for polar orbits matches how real polar weather satellites cover mid-latitudes.
Listen for: inputs below about 400 km or above the Moon; weights changed after totals; treating a model ratio as an instrument specification.
Support / stretch: provide a spreadsheet with columns built. Stretch: add a column for the one-way signal delay from each altitude to the ground, h/c.