CubeSTEM Digital Twin
Plan sessions across the eight-track CubeSat journey (Tracks 0–7) with lesson packs, timing presets, and honest capability boundaries — browser-local; no login required.
Teacher Mode here is a local planning aid. It helps you choose activities, estimate timing, surface outcomes and misconceptions, and generate a copyable session plan text. It does not introduce a backend, teacher accounts, class rosters, student submissions, or auto-grading.
Timing
Pick a pacing preset, then use a lesson pack or the activity planning table to build a session.
15 min
Whole-class introduction, club demo, or a fast workshop opener.
Suggested flow
Boundary: Use the interactive activities as teaching-grade models; avoid claims of flight-certified simulation or automatic grading.
45 min
A full period with short discussion, activity time, and reflection/evidence capture.
Suggested flow
Boundary: No student accounts or roster engine in MVP-final; evidence collection is teacher-facilitated and local.
90 min
Deeper exploration with two activities, comparisons, and a structured debrief.
Suggested flow
Boundary: Hardware work remains optional and local; no public remote hardware control is introduced in this phase.
2–3 hours (extendable)
Seminar format: reasoning, assumptions, and model limitations with richer discussion.
Suggested flow
Boundary: Keep language precise: teaching models and estimates; not STK/GMAT-grade orbit propagation, not a flight simulator.
Lesson packs
Each pack links only to routes that exist today, with honest notes when a dedicated activity page is not available yet.
Start with Activity 00.1, then use the curriculum map to pick your next path.
Outcomes
Available now
Boundary: Local planning aid only. No roster, no student accounts, and no automated assessment workflow in MVPF6.
A coherent four-activity onboarding sequence: mission → subsystems → trade-offs → digital twin boundaries (local-only).
Outcomes
Available now
Links
Boundary: Local-only: no login, no roster, no submissions, and no official grading. Evidence is shared manually. No public remote hardware control.
Set expectations: what the twin helps with today, and what it does not replace.
Outcomes
Available now
Boundary: This pack is about honest capability framing. Do not promise remote labs, accounts, or automatic grading.
Teach orbit as free-fall + why contact windows are brief and scheduled.
Outcomes
Available now
Boundary: Orbit/contact routes are teaching-grade models. Avoid claims of operational orbit propagation or RF link-budget truth.
A coherent five-activity sequence: free-fall → altitude vs period → orbit-class trade-offs → ground track/coverage → contact windows (local-only).
Outcomes
Available now
Links
Boundary: Local-only: no login, no roster, no submissions, and no official grading. Evidence is shared manually. Teaching-grade orbit models only (not STK/GMAT, not certified propagator).
Coherent four-activity sequence: choose objective → payload drives mission → payload data generation → measurable success criteria (local-only).
Outcomes
Available now
Links
Optional planning surface (teaching estimate).
Boundary: Local-only: no login, no roster, no submissions, no official grading. Evidence is shared manually. Teaching-grade mission design only — not a requirements database, not CAD, not automated mission verification, not certified payload simulation.
Four-session mini-course: power budgeting → eclipse energy balance → thermal hot/cold screening → resource trade-offs (local-only). Three extension items remain honest path-only entries.
Outcomes
Available now
Links
Optional cross-check with teaching budget labels.
Boundary: Teaching-grade models only — not certified power/thermal analysis, not battery safety certification, no remote hardware. Local-only evidence — no submissions or roster visibility.
Four-session mini-course: line-of-sight basics → data rate × contact time → link margin trade-off → command/telemetry flow (local-only).
Outcomes
Available now
Links
Boundary: Teaching-grade models only — not a certified RF link budget, not ITU/regulatory or licensed-radio analysis, no real satellite command, no SDR or remote hardware. Local-only evidence — no submissions or roster visibility.
Seven-session mini-course: why pointing matters → sensor estimation → step response → contact-window pointing → PID tuning → power-aware control → daylight vs eclipse evidence (local-only).
Outcomes
Available now
Links
Boundary: Teaching-grade one-axis models only — not full 3-axis flight ADCS, not a reaction-wheel safety certification, not remote hardware control, not official attitude determination software, not a certified ADCS simulation tool. Local-only evidence — no submissions or roster visibility.
Five-session mini-course: telemetry stream basics → subsystem health thresholds → replay timeline evidence → anomaly detective → mission evidence debrief (local-only).
Outcomes
Available now
Links
Boundary: Teaching-grade telemetry models only — not real satellite telemetry, not a ground-station command interface, not certified anomaly diagnosis, not flight operations. Local-only evidence — no submissions, no roster visibility, no official grading.
Five-session mini-course: autonomy levels → features, labels & data quality → anomaly classifier → confidence and false alarms → human-in-the-loop decision review (local-only, teaching-grade).
Outcomes
Available now
Links
Boundary: Teaching-grade AI/ML models only — not certified AI, not flight software, not real onboard autonomy, not real satellite commands, not certified anomaly diagnosis. Local-only evidence — no submissions, no roster visibility, no LMS integration, no official grading.
Preview the standard activity shell used for future activity standardization.
Outcomes
Available now
Boundary: Preview-only: do not use the shell preview as the assignment route. Use Activity 00.1 as the yardstick route for a full end-to-end example, and use shell-preview only to inspect the reusable layout blocks.
Set classroom expectations for hardware vs software, safely and honestly.
Outcomes
Available now
Boundary: No remote hardware lab control or public hardware access is provided. Hardware use remains local and supervised.
Planning rows
Derived from the mission learning path. Use it to choose what to teach today, estimate timing, and keep readiness honest.
Orientation • All Levels • 15–20 min
Outcome: Student can explain what a CubeSat is, why missions need planning, and what a mission objective means in plain language.
Teacher use: 15-minute whole-class orientation before opening Mission Design; emphasize objective-first thinking.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
In one sentence, what is your mission trying to accomplish, and name one design choice that follows from it?
Expected evidence
Orientation • All Levels • 35–45 min
Outcome: Student can identify major CubeSat subsystems, explain each subsystem’s role, and justify which subsystem is involved when a mission clue or symptom appears.
Teacher use: After Activity 00.1, bridge mission objectives to architecture: students practice naming subsystems from clues before Digital Twin Before Hardware.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Identify the subsystem from a clue or symptom and justify your reasoning with one piece of evidence.
Expected evidence
Orientation • All Levels • 40–50 min
Outcome: Student can explain how a mission objective changes subsystem priorities and justify at least one engineering trade-off using evidence.
Teacher use: Run after Subsystem Detective to teach subsystem prioritization and how mission objectives drive engineering trade-offs.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Justify one trade-off created by your mission objective: which subsystem went up, which went down, and why is that defensible?
Expected evidence
+ 1 more evidence items in the activity.
Orientation • All Levels • 15–20 min
Outcome: Student can explain what a digital twin is, give one learning benefit, and name one honest limit of today’s CubeSTEM twin.
Teacher use: Frame as risk reduction: cheaper to fail in simulation; connect to classroom lab safety and iteration.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
What is one question you would ask an engineer to check whether a result came from a real simulator run vs a teaching estimate?
Expected evidence
Launch, Gravity & Orbit Basics • Middle School • 20–25 min
Outcome: Student explains orbit as continuous free fall: gravity plus sideways velocity, not “no gravity.”
Teacher use: Use the ball thought experiment before any numbers; stress language precision (microgravity vs no gravity).
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why doesn’t the satellite fall straight down to Earth even though gravity pulls it toward Earth?
Expected evidence
Launch, Gravity & Orbit Basics • High School • 25–30 min
Outcome: Student can estimate how period and speed change when altitude changes and compare two LEO cases.
Teacher use: Emphasize “estimate and reason” over memorizing exact km/s; disclose simplifying assumptions.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
If you raise orbit altitude, does period usually increase or decrease? Why, in one sentence tied to path length and speed?
Expected evidence
Launch, Gravity & Orbit Basics • High School • 20–25 min
Outcome: Student can describe at least two trade-offs between LEO and GEO (or MEO) for a CubeSat-class mission.
Teacher use: Anchor on student-built CubeSat realism: GEO is uncommon; focus on why LEO is the default classroom story.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Name one mission goal that favors LEO and one that might favor a higher orbit — and what cost or constraint comes with the higher orbit.
Expected evidence
Launch, Gravity & Orbit Basics • High School • 20–25 min
Outcome: Student can explain ground track, inclination, and why revisits happen faster in LEO than in distant orbits.
Teacher use: Pair with Earth science: revisit time, storms, or imaging cadence narratives without claiming GIS product fidelity.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
What does orbital inclination tell you about which parts of Earth the mission can see over time?
Expected evidence
Launch, Gravity & Orbit Basics • Middle School • 20 min
Outcome: Student can explain line-of-sight, why passes are brief, and how that limits downlink time.
Teacher use: Bridge to “operations realism”: short passes mean planning, queues, and sometimes partial downloads.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why can’t the ground station talk to the satellite all the time, even if both are powered on?
Expected evidence
Mission Design & Payload Thinking • Middle School • 20–25 min
Outcome: Student can state a clear mission objective and explain how it drives system requirements.
Teacher use: Use three contrasting scenario cards; force students to pick one and defend trade-offs aloud.
Readiness
Partial / teaching
Maturity: Pilot Ready
Assessment prompt
Rewrite a vague objective (“take pictures”) into a testable objective with who, what, and why it matters.
Expected evidence
Mission Design & Payload Thinking • High School • 25–30 min
Outcome: Student can explain how a chosen payload determines power, pointing, data, and thermal requirements.
Teacher use: Give a concrete payload spec (e.g., 5 MP, 1 image/min); ask what breaks first in budgets.
Readiness
Partial / teaching
Maturity: Concept Ready
Assessment prompt
If you switch from a low-rate beacon to a high-rate imager, name two subsystems that change and why.
Expected evidence
Mission Design & Payload Thinking • High School • 25–30 min
Outcome: Student can estimate data volume from a payload and relate it to downlink constraints.
Teacher use: Use round numbers first (MB/orbit) before introducing Mbps; keep RF link abstract.
Readiness
Partial / teaching
Maturity: Concept Ready
Assessment prompt
What happens to onboard storage if you collect data faster than you can downlink? Name one mitigation.
Expected evidence
Mission Design & Payload Thinking • University • 30–40 min
Outcome: Student can write a set of mission success criteria and explain how they connect to telemetry evidence.
Teacher use: Capstone prep: require one criterion tied to ADCS chart evidence and one to Mission Design risk flag.
Readiness
Partial / teaching
Maturity: Concept Ready
Assessment prompt
Pick one criterion and state exactly which telemetry or budget field would prove it passed.
Expected evidence
Power / Thermal / Budgets • High School • 25–35 min
Outcome: Student can compare average and peak bus power, explain duty-cycle effects, and read a simple margin result (safe / warning / overloaded).
Teacher use: Contrast average vs peak before numbers: payload and radio are often duty-cycled; OBC/ADCS may be closer to always-on.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why is average power not the same as peak power, and why do teams still plan for peak?
Expected evidence
Power / Thermal / Budgets • High School • 25–35 min
Outcome: Student can relate sunlight vs eclipse time, average load, and stored energy to a remaining-reserve warning (teaching estimate).
Teacher use: Emphasize energy = power × time; eclipse is the “night” problem even if sun charging looks strong.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why can a mission look power-positive in sunlight but still fail in eclipse?
Expected evidence
Power / Thermal / Budgets • High School • 20–30 min
Outcome: Student can explain when a simplified model flags hot or cold risk and what an engineer would check first (teaching-grade).
Teacher use: Stress that both overheating and overcooling can happen; vacuum changes how heat leaves the spacecraft.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why can both overheating and overcooling be mission risks for the same spacecraft?
Expected evidence
Power / Thermal / Budgets • High School • 25–35 min
Outcome: Student can allocate limited resources, interpret warnings, and justify a chosen strategy with evidence (teaching exercise).
Teacher use: Make “margin is not waste” explicit: margin buys resilience against unknowns.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why can’t payload, battery, radio, and engineering margin all be maximized at once?
Expected evidence
Power / Thermal / Budgets • Middle School • 20–25 min
Outcome: Student can explain what determines how much solar power a CubeSat receives and why eclipse is a problem.
Teacher use: Tie to climate/energy: same physics as rooftop solar, different environment.
Readiness
Partial / teaching
Maturity: Pilot Ready
Assessment prompt
Name two reasons generated solar power drops during eclipse even if payloads are off.
Expected evidence
Power / Thermal / Budgets • High School • 20–25 min
Outcome: Student can explain what data utilization means and what happens when data generation exceeds downlink capacity.
Teacher use: Emphasize bits vs bytes; use one consistent unit for the lesson.
Readiness
Partial / teaching
Maturity: Pilot Ready
Assessment prompt
If utilization stays above 100% for a week, what operational symptom would operators likely see?
Expected evidence
Power / Thermal / Budgets • University • 30–40 min
Outcome: Student can read mission risk flags, explain their severity, and propose at least one mitigation per flag.
Teacher use: Role-play review board: each student defends one mitigation under time pressure.
Readiness
Partial / teaching
Maturity: Pilot Ready
Assessment prompt
Pick the highest-severity flag and explain whether it is a mass, power, data, thermal, or ops issue first.
Expected evidence
Communication / Ground Link • High School • 20–25 min
Outcome: Student can explain why ground-station contact depends on satellite visibility above the horizon and on a minimum elevation angle.
Teacher use: Stress that contact is not continuous — a CubeSat sees most ground stations only during short passes when the satellite is above the horizon at sufficient elevation.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why does a ground station only see a CubeSat for a short window each pass, and why does minimum elevation matter?
Expected evidence
Communication / Ground Link • High School • 20–25 min
Outcome: Student can compute a teaching-grade data budget (data rate × contact time × passes) and identify when payload data exceeds available downlink.
Teacher use: Reinforce that data rate alone is not enough — contact time and number of passes per day are the real bottleneck for many CubeSat missions.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why can a CubeSat with a fast radio still fail to downlink all its payload data in a day?
Expected evidence
Communication / Ground Link • High School • 25–30 min
Outcome: Student can read a teaching-grade margin badge (safe / weak / failed) and explain one trade-off and one improvement (teaching-grade only).
Teacher use: Use the lab to surface that pushing one knob (e.g. data rate) too far breaks margin — link planning is a balance, not a single optimization.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
If the teaching margin is weak, name two changes (one operational, one design) that could push it back to safe — and a cost or downside of each.
Expected evidence
Communication / Ground Link • High School • 20–30 min
Outcome: Student can explain what gets sent first when contact time is short and what happens to lost packets in a teaching priority queue (no real radio).
Teacher use: Stress that uplink and downlink are different — small command bytes go up; big science data goes down — and short passes force prioritization.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
When contact time is short and packet loss is non-zero, why must operators set priorities for what gets sent first?
Expected evidence
Attitude Control & Pointing • Middle School • 15–20 min
Outcome: Student can explain why attitude control is needed and what pointing error means.
Teacher use: Tie beam-on-target demo to antenna gain, camera framing, and solar wing illumination.
Readiness
Partial / teaching
Maturity: Concept Ready
Assessment prompt
Name two mission functions that fail or degrade if pointing error stays large for minutes.
Expected evidence
Attitude Control & Pointing • High School • 25–30 min
Outcome: Student can describe the target angle, actual angle, and error trend from a real simulator run.
Teacher use: Have students predict overshoot before showing chart; compare prediction to evidence.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
From your run, how do you know the spacecraft reached the target within acceptable error?
Expected evidence
Attitude Control & Pointing • High School • 25–30 min
Outcome: Student can measure overshoot and settling time from a step response chart and relate them to controller tuning.
Teacher use: Bridge to tuning ethics: fast but gentle on actuators and power.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
If you increase proportional gain, what usually happens to overshoot and why might operators care?
Expected evidence
Attitude Control & Pointing • High School • 25–30 min
Outcome: Student can explain the pointing requirement for a contact window and observe it in the simulator.
Teacher use: Emphasize ops story: acquire → track → handoff; relate to download planning.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why might operators care about pointing error even if the radio is technically transmitting?
Expected evidence
Attitude Control & Pointing • University • 30–35 min
Outcome: Student can compare settling time, overshoot, and wheel effort for gentle and aggressive control settings.
Teacher use: Use A/B replay to teach evidence-based tuning debates, not guesswork.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
When would you accept slower settling to protect power and mechanical wear?
Expected evidence
Attitude Control & Pointing • University • 30–35 min
Outcome: Student can explain how a power-limited scenario changes controller behaviour and mission safety.
Teacher use: Explicitly separate wheel torque limits from true bus voltage collapse physics.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
What is one observable telemetry sign that the spacecraft is being gentler on actuators in power-aware mode?
Expected evidence
Attitude Control & Pointing • University • 30–35 min
Outcome: Student can explain why eclipse changes power availability for control and what the system must do differently.
Teacher use: Connect to energy logistics: less solar → less aggressive ADCS unless mission-critical.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why might operators schedule non-critical maneuvers outside eclipse if power margin is thin?
Expected evidence
Telemetry, Evidence & Operations • Middle School • 20–25 min
Outcome: Student can identify at least four telemetry channels and explain what each one measures.
Teacher use: Pair with vocabulary wall: angle, error, rate, wheel, power indicators.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Which channel would you watch first to know if pointing is improving, and why?
Expected evidence
Telemetry, Evidence & Operations • University • 35–40 min
Outcome: Student can interpret each telemetry subsystem channel and explain its mission-level significance.
Teacher use: Use jigsaw groups: each group masters one subsystem, then teaches the class.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Pick one yellow flag: which subsystem owns it first, and what confirming channel would you check next?
Expected evidence
Telemetry, Evidence & Operations • High School • 25–30 min
Outcome: Student can replay a run, identify key events in the telemetry, and write a short mission debrief statement.
Teacher use: Require evidence quotes: timestamp + channel + value trend.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
What is one claim you would not make without replay evidence, and what chart proves it?
Expected evidence
Telemetry, Evidence & Operations • University • 25–30 min
Outcome: Student can identify stale telemetry, explain its risk, and describe a mitigation strategy.
Teacher use: Discuss cyber-physical trust: stale data is an ops problem, not only a math problem.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Why is acting on stale attitude data sometimes worse than having no data?
Expected evidence
Telemetry, Evidence & Operations • University • 50–60 min
Outcome: Student can complete a full mission journey and produce an evidence-based report connecting all tracks.
Teacher use: Schedule as 2-session block: design + run, debrief + revision.
Readiness
Partial / teaching
Maturity: Pilot Ready
Assessment prompt
What single chart would you show a reviewer to prove your spacecraft met its pointing goal?
Expected evidence
AI / ML & Autonomy • High School • 20–25 min
Outcome: Student can describe three levels of spacecraft autonomy, explain what each level is allowed to do, and state why human-in-the-loop review matters even in the highest autonomy mode.
Teacher use: Use as entry point to the AI/ML mini-course. Ask: 'What would go wrong if a satellite acted on every alert without a human check?'
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Describe one situation where 'recommend action' autonomy is safer than 'execute' autonomy, and explain why.
Expected evidence
AI / ML & Autonomy • High School • 30–35 min
Outcome: Student can define feature and label, select useful features from telemetry, assign a correct label to a given example, and explain how a biased dataset degrades classifier performance.
Teacher use: Position as a data ethics conversation: what happens when training data is mostly nominal? Ask students to find a dataset gap.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Name two ways a biased or incomplete training dataset could cause a fault classifier to make dangerous mistakes.
Expected evidence
AI / ML & Autonomy • High School • 25–30 min
Outcome: Student can run a classifier on a telemetry example, interpret the predicted class and confidence score, identify the key contributing features, and explain the difference between rule-based and ML-based detection.
Teacher use: Use think-aloud protocol: ask students to narrate what each top feature tells the classifier. Stress that confidence ≠ correctness.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Give one example of a telemetry pattern that looks abnormal but is actually expected during a planned mode change — and explain how a classifier might incorrectly flag it.
Expected evidence
+ 1 more evidence items in the activity.
AI / ML & Autonomy • High School • 30–35 min
Outcome: Student can explain the trade-off between sensitivity and false alarm rate, read a confusion matrix, and justify a sensitivity setting based on mission risk tolerance.
Teacher use: Ask: 'Would you rather miss one real fault, or get seven false alarms per day?' Use student answers to surface the mission-specific trade-off.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
A detector has TP=14, FP=7, TN=13, FN=1. Calculate precision and recall, and state which setting would cause alarm fatigue and why.
Expected evidence
AI / ML & Autonomy • High School • 35–40 min
Outcome: Student can review telemetry evidence cards, apply a safety rule check to a proposed action, choose an appropriate response, and write a one-paragraph decision debrief.
Teacher use: Run as a structured debate: two students choose different actions for the same anomaly, then each explains their evidence-card reasoning. Stress that asking for human review is always valid.
Readiness
Implemented
Maturity: Pilot Ready
Assessment prompt
Give one scenario where entering safe mode too early wastes science, and one where waiting too long risks the spacecraft bus — explain how evidence cards would help you decide.
Expected evidence
+ 1 more evidence items in the activity.
| Activity | Level / time | Outcome | Readiness | Route |
|---|---|---|---|---|
What is a CubeSat Mission? Orientation Teacher use: 15-minute whole-class orientation before opening Mission Design; emphasize objective-first thinking. | All Levels 15–20 min | Student can explain what a CubeSat is, why missions need planning, and what a mission objective means in plain language. Prompt: In one sentence, what is your mission trying to accomplish, and name one design choice that follows from it? | Available Implemented Maturity: Pilot Ready | Open activity → |
Subsystem Detective Orientation Teacher use: After Activity 00.1, bridge mission objectives to architecture: students practice naming subsystems from clues before Digital Twin Before Hardware. | All Levels 35–45 min | Student can identify major CubeSat subsystems, explain each subsystem’s role, and justify which subsystem is involved when a mission clue or symptom appears. Prompt: Identify the subsystem from a clue or symptom and justify your reasoning with one piece of evidence. | Available Implemented Maturity: Pilot Ready | Open activity → |
Mission / Subsystem Trade-off Orientation Teacher use: Run after Subsystem Detective to teach subsystem prioritization and how mission objectives drive engineering trade-offs. | All Levels 40–50 min | Student can explain how a mission objective changes subsystem priorities and justify at least one engineering trade-off using evidence. Prompt: Justify one trade-off created by your mission objective: which subsystem went up, which went down, and why is that defensible? | Available Implemented Maturity: Pilot Ready | Open activity → |
Digital Twin Before Hardware Orientation Teacher use: Frame as risk reduction: cheaper to fail in simulation; connect to classroom lab safety and iteration. | All Levels 15–20 min | Student can explain what a digital twin is, give one learning benefit, and name one honest limit of today’s CubeSTEM twin. Prompt: What is one question you would ask an engineer to check whether a result came from a real simulator run vs a teaching estimate? | Available Implemented Maturity: Pilot Ready | Open activity → |
From Launch to Orbit Launch, Gravity & Orbit Basics Teacher use: Use the ball thought experiment before any numbers; stress language precision (microgravity vs no gravity). | Middle School 20–25 min | Student explains orbit as continuous free fall: gravity plus sideways velocity, not “no gravity.” Prompt: Why doesn’t the satellite fall straight down to Earth even though gravity pulls it toward Earth? | Available Implemented Maturity: Pilot Ready | Open activity → |
Orbit Speed and Altitude Launch, Gravity & Orbit Basics Teacher use: Emphasize “estimate and reason” over memorizing exact km/s; disclose simplifying assumptions. | High School 25–30 min | Student can estimate how period and speed change when altitude changes and compare two LEO cases. Prompt: If you raise orbit altitude, does period usually increase or decrease? Why, in one sentence tied to path length and speed? | Available Implemented Maturity: Pilot Ready | Open activity → |
Low Earth Orbit vs Higher Orbit Launch, Gravity & Orbit Basics Teacher use: Anchor on student-built CubeSat realism: GEO is uncommon; focus on why LEO is the default classroom story. | High School 20–25 min | Student can describe at least two trade-offs between LEO and GEO (or MEO) for a CubeSat-class mission. Prompt: Name one mission goal that favors LEO and one that might favor a higher orbit — and what cost or constraint comes with the higher orbit. | Available Implemented Maturity: Pilot Ready | Open activity → |
Ground Track and Coverage Launch, Gravity & Orbit Basics Teacher use: Pair with Earth science: revisit time, storms, or imaging cadence narratives without claiming GIS product fidelity. | High School 20–25 min | Student can explain ground track, inclination, and why revisits happen faster in LEO than in distant orbits. Prompt: What does orbital inclination tell you about which parts of Earth the mission can see over time? | Available Implemented Maturity: Pilot Ready | Open activity → |
Contact Window Basics Launch, Gravity & Orbit Basics Teacher use: Bridge to “operations realism”: short passes mean planning, queues, and sometimes partial downloads. | Middle School 20 min | Student can explain line-of-sight, why passes are brief, and how that limits downlink time. Prompt: Why can’t the ground station talk to the satellite all the time, even if both are powered on? | Available Implemented Maturity: Pilot Ready | Open activity → |
Choose a Mission Objective Mission Design & Payload Thinking Teacher use: Use three contrasting scenario cards; force students to pick one and defend trade-offs aloud. | Middle School 20–25 min | Student can state a clear mission objective and explain how it drives system requirements. Prompt: Rewrite a vague objective (“take pictures”) into a testable objective with who, what, and why it matters. | Preview Partial / teaching Maturity: Pilot Ready | Open activity → |
Payload Drives the Mission Mission Design & Payload Thinking Teacher use: Give a concrete payload spec (e.g., 5 MP, 1 image/min); ask what breaks first in budgets. | High School 25–30 min | Student can explain how a chosen payload determines power, pointing, data, and thermal requirements. Prompt: If you switch from a low-rate beacon to a high-rate imager, name two subsystems that change and why. | Preview Partial / teaching Maturity: Concept Ready | Open activity → |
Payload Data Generation Mission Design & Payload Thinking Teacher use: Use round numbers first (MB/orbit) before introducing Mbps; keep RF link abstract. | High School 25–30 min | Student can estimate data volume from a payload and relate it to downlink constraints. Prompt: What happens to onboard storage if you collect data faster than you can downlink? Name one mitigation. | Preview Partial / teaching Maturity: Concept Ready | Open activity → |
Mission Success Criteria Mission Design & Payload Thinking Teacher use: Capstone prep: require one criterion tied to ADCS chart evidence and one to Mission Design risk flag. | University 30–40 min | Student can write a set of mission success criteria and explain how they connect to telemetry evidence. Prompt: Pick one criterion and state exactly which telemetry or budget field would prove it passed. | Preview Partial / teaching Maturity: Concept Ready | Open activity → |
Power Budget Basics Power / Thermal / Budgets Teacher use: Contrast average vs peak before numbers: payload and radio are often duty-cycled; OBC/ADCS may be closer to always-on. | High School 25–35 min | Student can compare average and peak bus power, explain duty-cycle effects, and read a simple margin result (safe / warning / overloaded). Prompt: Why is average power not the same as peak power, and why do teams still plan for peak? | Available Implemented Maturity: Pilot Ready | Open activity → |
Day / Night Energy Balance Power / Thermal / Budgets Teacher use: Emphasize energy = power × time; eclipse is the “night” problem even if sun charging looks strong. | High School 25–35 min | Student can relate sunlight vs eclipse time, average load, and stored energy to a remaining-reserve warning (teaching estimate). Prompt: Why can a mission look power-positive in sunlight but still fail in eclipse? | Available Implemented Maturity: Pilot Ready | Open activity → |
Thermal Hot / Cold Case Power / Thermal / Budgets Teacher use: Stress that both overheating and overcooling can happen; vacuum changes how heat leaves the spacecraft. | High School 20–30 min | Student can explain when a simplified model flags hot or cold risk and what an engineer would check first (teaching-grade). Prompt: Why can both overheating and overcooling be mission risks for the same spacecraft? | Available Implemented Maturity: Pilot Ready | Open activity → |
Mass / Volume / Resource Trade-off Power / Thermal / Budgets Teacher use: Make “margin is not waste” explicit: margin buys resilience against unknowns. | High School 25–35 min | Student can allocate limited resources, interpret warnings, and justify a chosen strategy with evidence (teaching exercise). Prompt: Why can’t payload, battery, radio, and engineering margin all be maximized at once? | Available Implemented Maturity: Pilot Ready | Open activity → |
Solar Power Generation Power / Thermal / Budgets Teacher use: Tie to climate/energy: same physics as rooftop solar, different environment. | Middle School 20–25 min | Student can explain what determines how much solar power a CubeSat receives and why eclipse is a problem. Prompt: Name two reasons generated solar power drops during eclipse even if payloads are off. | Preview Partial / teaching Maturity: Pilot Ready | Open Learn hub → |
Data Budget and Downlink Limit Power / Thermal / Budgets Teacher use: Emphasize bits vs bytes; use one consistent unit for the lesson. | High School 20–25 min | Student can explain what data utilization means and what happens when data generation exceeds downlink capacity. Prompt: If utilization stays above 100% for a week, what operational symptom would operators likely see? | Preview Partial / teaching Maturity: Pilot Ready | Open Learn hub → |
Risk Flags and Engineering Decisions Power / Thermal / Budgets Teacher use: Role-play review board: each student defends one mitigation under time pressure. | University 30–40 min | Student can read mission risk flags, explain their severity, and propose at least one mitigation per flag. Prompt: Pick the highest-severity flag and explain whether it is a mass, power, data, thermal, or ops issue first. | Preview Partial / teaching Maturity: Pilot Ready | Open Learn hub → |
Line-of-Sight Communication Communication / Ground Link Teacher use: Stress that contact is not continuous — a CubeSat sees most ground stations only during short passes when the satellite is above the horizon at sufficient elevation. | High School 20–25 min | Student can explain why ground-station contact depends on satellite visibility above the horizon and on a minimum elevation angle. Prompt: Why does a ground station only see a CubeSat for a short window each pass, and why does minimum elevation matter? | Available Implemented Maturity: Pilot Ready | Open activity → |
Data Rate × Contact Time Communication / Ground Link Teacher use: Reinforce that data rate alone is not enough — contact time and number of passes per day are the real bottleneck for many CubeSat missions. | High School 20–25 min | Student can compute a teaching-grade data budget (data rate × contact time × passes) and identify when payload data exceeds available downlink. Prompt: Why can a CubeSat with a fast radio still fail to downlink all its payload data in a day? | Available Implemented Maturity: Pilot Ready | Open activity → |
Link Margin Trade-off Communication / Ground Link Teacher use: Use the lab to surface that pushing one knob (e.g. data rate) too far breaks margin — link planning is a balance, not a single optimization. | High School 25–30 min | Student can read a teaching-grade margin badge (safe / weak / failed) and explain one trade-off and one improvement (teaching-grade only). Prompt: If the teaching margin is weak, name two changes (one operational, one design) that could push it back to safe — and a cost or downside of each. | Available Implemented Maturity: Pilot Ready | Open activity → |
Command / Telemetry Flow Communication / Ground Link Teacher use: Stress that uplink and downlink are different — small command bytes go up; big science data goes down — and short passes force prioritization. | High School 20–30 min | Student can explain what gets sent first when contact time is short and what happens to lost packets in a teaching priority queue (no real radio). Prompt: When contact time is short and packet loss is non-zero, why must operators set priorities for what gets sent first? | Available Implemented Maturity: Pilot Ready | Open activity → |
Why Pointing Matters Attitude Control & Pointing Teacher use: Tie beam-on-target demo to antenna gain, camera framing, and solar wing illumination. | Middle School 15–20 min | Student can explain why attitude control is needed and what pointing error means. Prompt: Name two mission functions that fail or degrade if pointing error stays large for minutes. | Preview Partial / teaching Maturity: Concept Ready | Open activity → |
Attitude Hold Basics Attitude Control & Pointing Teacher use: Have students predict overshoot before showing chart; compare prediction to evidence. | High School 25–30 min | Student can describe the target angle, actual angle, and error trend from a real simulator run. Prompt: From your run, how do you know the spacecraft reached the target within acceptable error? | Available Implemented Maturity: Pilot Ready | Open activity → |
Step Response to +10 Degrees Attitude Control & Pointing Teacher use: Bridge to tuning ethics: fast but gentle on actuators and power. | High School 25–30 min | Student can measure overshoot and settling time from a step response chart and relate them to controller tuning. Prompt: If you increase proportional gain, what usually happens to overshoot and why might operators care? | Available Implemented Maturity: Pilot Ready | Open activity → |
Contact Window Pointing Attitude Control & Pointing Teacher use: Emphasize ops story: acquire → track → handoff; relate to download planning. | High School 25–30 min | Student can explain the pointing requirement for a contact window and observe it in the simulator. Prompt: Why might operators care about pointing error even if the radio is technically transmitting? | Available Implemented Maturity: Pilot Ready | Open activity → |
Gentle vs Aggressive Control Attitude Control & Pointing Teacher use: Use A/B replay to teach evidence-based tuning debates, not guesswork. | University 30–35 min | Student can compare settling time, overshoot, and wheel effort for gentle and aggressive control settings. Prompt: When would you accept slower settling to protect power and mechanical wear? | Available Implemented Maturity: Pilot Ready | Open activity → |
Power-Aware Attitude Control Attitude Control & Pointing Teacher use: Explicitly separate wheel torque limits from true bus voltage collapse physics. | University 30–35 min | Student can explain how a power-limited scenario changes controller behaviour and mission safety. Prompt: What is one observable telemetry sign that the spacecraft is being gentler on actuators in power-aware mode? | Available Implemented Maturity: Pilot Ready | Open activity → |
Daylight vs Eclipse Response Attitude Control & Pointing Teacher use: Connect to energy logistics: less solar → less aggressive ADCS unless mission-critical. | University 30–35 min | Student can explain why eclipse changes power availability for control and what the system must do differently. Prompt: Why might operators schedule non-critical maneuvers outside eclipse if power margin is thin? | Available Implemented Maturity: Pilot Ready | Open activity → |
Telemetry Dashboard Basics Telemetry, Evidence & Operations Teacher use: Pair with vocabulary wall: angle, error, rate, wheel, power indicators. | Middle School 20–25 min | Student can identify at least four telemetry channels and explain what each one measures. Prompt: Which channel would you watch first to know if pointing is improving, and why? | Available Implemented Maturity: Pilot Ready | Open activity → |
Subsystem Interpretation Walkthrough Telemetry, Evidence & Operations Teacher use: Use jigsaw groups: each group masters one subsystem, then teaches the class. | University 35–40 min | Student can interpret each telemetry subsystem channel and explain its mission-level significance. Prompt: Pick one yellow flag: which subsystem owns it first, and what confirming channel would you check next? | Available Implemented Maturity: Pilot Ready | Open activity → |
Replay and Mission Debrief Telemetry, Evidence & Operations Teacher use: Require evidence quotes: timestamp + channel + value trend. | High School 25–30 min | Student can replay a run, identify key events in the telemetry, and write a short mission debrief statement. Prompt: What is one claim you would not make without replay evidence, and what chart proves it? | Available Implemented Maturity: Pilot Ready | Open activity → |
Telemetry Trust and Stale Data Telemetry, Evidence & Operations Teacher use: Discuss cyber-physical trust: stale data is an ops problem, not only a math problem. | University 25–30 min | Student can identify stale telemetry, explain its risk, and describe a mitigation strategy. Prompt: Why is acting on stale attitude data sometimes worse than having no data? | Available Implemented Maturity: Pilot Ready | Open activity → |
Mission-Based STEM Capstone Telemetry, Evidence & Operations Teacher use: Schedule as 2-session block: design + run, debrief + revision. | University 50–60 min | Student can complete a full mission journey and produce an evidence-based report connecting all tracks. Prompt: What single chart would you show a reviewer to prove your spacecraft met its pointing goal? | Preview Partial / teaching Maturity: Pilot Ready | Open activity → |
What Does Autonomy Mean? AI / ML & Autonomy Teacher use: Use as entry point to the AI/ML mini-course. Ask: 'What would go wrong if a satellite acted on every alert without a human check?' | High School 20–25 min | Student can describe three levels of spacecraft autonomy, explain what each level is allowed to do, and state why human-in-the-loop review matters even in the highest autonomy mode. Prompt: Describe one situation where 'recommend action' autonomy is safer than 'execute' autonomy, and explain why. | Available Implemented Maturity: Pilot Ready | Open activity → |
Features, Labels and Training Data AI / ML & Autonomy Teacher use: Position as a data ethics conversation: what happens when training data is mostly nominal? Ask students to find a dataset gap. | High School 30–35 min | Student can define feature and label, select useful features from telemetry, assign a correct label to a given example, and explain how a biased dataset degrades classifier performance. Prompt: Name two ways a biased or incomplete training dataset could cause a fault classifier to make dangerous mistakes. | Available Implemented Maturity: Pilot Ready | Open activity → |
Anomaly Classifier AI / ML & Autonomy Teacher use: Use think-aloud protocol: ask students to narrate what each top feature tells the classifier. Stress that confidence ≠ correctness. | High School 25–30 min | Student can run a classifier on a telemetry example, interpret the predicted class and confidence score, identify the key contributing features, and explain the difference between rule-based and ML-based detection. Prompt: Give one example of a telemetry pattern that looks abnormal but is actually expected during a planned mode change — and explain how a classifier might incorrectly flag it. | Available Implemented Maturity: Pilot Ready | Open activity → |
Confidence and False Alarms AI / ML & Autonomy Teacher use: Ask: 'Would you rather miss one real fault, or get seven false alarms per day?' Use student answers to surface the mission-specific trade-off. | High School 30–35 min | Student can explain the trade-off between sensitivity and false alarm rate, read a confusion matrix, and justify a sensitivity setting based on mission risk tolerance. Prompt: A detector has TP=14, FP=7, TN=13, FN=1. Calculate precision and recall, and state which setting would cause alarm fatigue and why. | Available Implemented Maturity: Pilot Ready | Open activity → |
Human-in-the-Loop Decision AI / ML & Autonomy Teacher use: Run as a structured debate: two students choose different actions for the same anomaly, then each explains their evidence-card reasoning. Stress that asking for human review is always valid. | High School 35–40 min | Student can review telemetry evidence cards, apply a safety rule check to a proposed action, choose an appropriate response, and write a one-paragraph decision debrief. Prompt: Give one scenario where entering safe mode too early wastes science, and one where waiting too long risks the spacecraft bus — explain how evidence cards would help you decide. | Available Implemented Maturity: Pilot Ready | Open activity → |
Guidance
A small set of high-frequency misconceptions to watch for in early CubeSat lessons.
Misconception
Orbit means there is no gravity.
Correction (teacher-friendly)
In orbit, gravity is still strong. The spacecraft is in continuous free-fall with high sideways velocity, so it keeps “missing” Earth.
Misconception
A digital twin is the same as real hardware.
Correction (teacher-friendly)
A digital twin is a software representation used to practice, plan, or explain. It can support learning, but it does not replace hardware integration, measurement noise, or operational constraints.
Misconception
Teaching-grade simulation equals a flight simulator.
Correction (teacher-friendly)
These routes are designed for conceptual understanding and bounded estimates. They are not flight-certified simulators or operational mission design tools.
Misconception
Mission objective and payload are the same thing.
Correction (teacher-friendly)
The objective is the mission goal (what you must accomplish). The payload is the instrument/service used to meet that goal, which then drives subsystem requirements.
Misconception
A contact window means you can communicate continuously.
Correction (teacher-friendly)
Contact windows are brief periods of line-of-sight. Operations require planning, prioritization, and sometimes partial downloads.
Misconception
Satellites are floating — not falling.
Correction (teacher-friendly)
Satellites are falling the entire time. They keep falling around Earth because their sideways velocity carries them forward as gravity pulls inward.
Facilitation
A simple structure to help you pace a session without relying on rosters, submissions, or backend tools.
Copyable plan
Choose a lesson pack and timing preset to generate a plan you can copy into slides, a doc, or your lesson notes. This stays local in your browser (no backend).
Orientation starter — Teacher session plan Audience / level: All Levels Duration: 15 min (15-minute demo) Learning outcomes: - Students can explain what a CubeSat is and why missions start with objectives. - Students can name basic subsystems (power, comms, pointing, payload). Activities and routes: - What is a CubeSat Mission?: /twin/learn/activities/orientation_what_is_cubesat - Curriculum map: /twin/learn/curriculum - Choose mode: /twin/modes Before class: - Pick one misconception to foreground (see Misconception guide). - Decide what evidence you want students to produce (one artifact, one sentence, or one screenshot). - Open the route(s) on the projector and confirm the page loads in your classroom network. During class (suggested flow): - Hook (2 min): What is a mission objective? - Activity (8–10 min): run one interactive route together - Debrief (3–5 min): one misconception + one evidence prompt Facilitation prompts: - Ask: “Who benefits from your mission, and how would they know it worked?” - Prompt: “Objective first — hardware later. What changes once the objective changes?” Expected evidence: - One-sentence mission objective (student or group) - Top three subsystems identified for the objective - One trade-off stated (e.g., power vs data, payload vs pointing) Assessment prompts: - In one sentence, what is your mission trying to accomplish, and name one design choice that follows from it? Boundary note: Local planning aid only. No roster, no student accounts, and no automated assessment workflow in MVPF6. Capability boundary (product): No backend, no login, no roster, no automatic assessment submission in MVP-final Phase 6. Assessment engine (Phase 8) and evidence engine (Phase 9) arrive later.
Quick links
Teacher Mode pairs with the curriculum map, Demo Pack, and yardstick activity routes across Tracks 0–7.
Student route note: Student Mode foundation is now available on /twin/student (local progress only; no accounts).
Capability boundary