Orientation
What is a CubeSat Mission?
Learn what a CubeSat is, typical sizes (1U/3U), and why every mission starts with a clear objective before hardware.
- Time estimate
- 15–20 min
- Complexity
- introductory
- Maturity
- pilot ready
- Simulator readiness
- implemented
- Software available now
- Implemented as CubeSat Mission System Builder — interactive activity on `/twin/learn/activities/orientation_what_is_cubesat`.
Student flow
Do this in order
Step 1
Choose learner level
Step 2
Choose mission objective
Step 3
Inspect subsystems + requirement cards
Step 4
Generate brief + write reflection
Step 5
Local self-check (assessment)
Step 6
Capture evidence (copy/export)
Step 7
Choose next activity
Local-only learning activity. Nothing is submitted; use copy/export or a screenshot to share evidence manually.
Learning outcomes
Student can explain what a CubeSat is, why missions need planning, and what a mission objective means in plain language.
- Define CubeSat and explain why a 1U/3U form factor matters.
- Name at least two mission objectives (e.g., imaging, communication).
- Explain why a satellite needs power and attitude control.
Key vocabulary
- CubeSat
- A small standardized satellite form factor (often 10×10×10 cm per unit) used for educational and research missions.
- Mission objective
- The clear statement of what the mission must accomplish for users or science goals on Earth.
- Payload
- The instrument or service the mission delivers — the reason the spacecraft exists beyond staying alive.
- Subsystem
- A major spacecraft function group such as power, communications, attitude, or data handling.
- Digital twin
- A software representation used to practice, plan, or explain mission behavior before or alongside hardware.
Concept primer
Learn what a CubeSat is, typical sizes (1U/3U), and why every mission starts with a clear objective before hardware.
Open the CubeSat Mission System Builder at `/twin/learn/activities/orientation_what_is_cubesat` — interactive software in the browser that maps mission objectives to subsystems (not a flight simulator).
Sketch a simple satellite; label bus, payload, and antenna; write one-sentence objective.
Interactive lab
Teaching-grade software activity slot — not a flight simulator or certified propagator.
Choose learner level
Default: Middle School. Wording, prompts, and labels below adapt to this choice — one page, no separate routes.
Choose a mission objective
CubeSat subsystem map
Select a mission objective to highlight which parts of the spacecraft matter most.
Payload
OBC / computer
EPS / power
ADCS / pointing
Communication
Structure / thermal
Ground station / ops
Local self-check
Assessment (practice only)
Use this as a self-check and discussion starter. It is local-only and not a grade.
Optional: attaches a local summary (completed / quick checks / checklist count).
Quick check
Multiple choice self-check
This is a local self-check to support discussion. It is not a grade.
Quick check: What is a payload (in a CubeSat mission)?
Quick check: Which subsystem most directly sends mission data to Earth?
Quick check: Why does mission objective change which subsystems matter most?
Discussion prompt
Short answer (local only)
Write notes for yourself or your group. Nothing is submitted.
Short answer: For your chosen objective, explain one trade-off (example: more data → more downlink time and power).
Checklist
Local checklist self-check
Use this to verify you covered key ideas. Nothing is submitted.
Checklist: Before you claim you have a mission concept, can you say…
0 / 5 checked
Rubric preview
Rubric (self-check / discussion guide)
Optional local self-check selections. This is not a gradebook and is not saved to an account.
Rubric preview (self-check): mission reasoning and boundary awareness
Teacher preview: use rubric rows as a discussion guide. Local-only and not a gradebook row.
Objective clarity
No selection
Beginning
Objective is vague or restates a payload without stating what success means.
Developing
Objective is stated but missing who benefits or how success is measured.
Proficient
Objective is clear and connects to a user/science outcome.
Extension
Objective includes constraints/trade-offs (time, coverage, data, power) and success criteria.
Subsystem reasoning (objective → constraints)
No selection
Beginning
Lists subsystems but cannot explain why they matter for the objective.
Developing
Explains one dependency (e.g., payload needs power) but misses key links.
Proficient
Explains how the objective drives at least 2 subsystems (power/data/pointing/comms).
Extension
Defends a design emphasis with a realistic trade-off (e.g., data vs downlink vs power).
Boundary awareness
No selection
Beginning
Treats the twin as reality without caveats.
Developing
Mentions a limitation but cannot connect it to evidence needed to verify claims.
Proficient
States a clear limitation and names what evidence would strengthen the claim.
Extension
Uses precise language (teaching model vs simulator vs hardware) and proposes a validation step.
Local summary
Assessment summary (practice only)
Completion
0 / 6 sections complete
Quick checks
0 / 3 correct
Shown only to support self-check.
Checklist
0 / 5 items checked
Reminder
Local-only practice summary. Not a grade and not submitted anywhere.
What this preview is / is not
Assessment engine v0 boundary note
- Student view (local practice): use this as a self-check and discussion starter.
- Local-only preview/practice: your answers are not submitted.
- No backend, no accounts, no roster, and no LMS integration.
- Not a grade. No credential or official scoring is implied.
- Teacher visibility into student answers is not implemented in MVPF8.
- Evidence runtime engine arrives in Phase 9 (not in this preview).
Capture
Evidence capture (local-only)
Capture what you did, what changed, what you observed, and how you explain it. This stays in your browser unless you copy/share it manually.
Selected inputs
- Learner level: Middle School
- Mission objective: (not selected)
Generated outputs
- Generated outputs: (none captured yet)
Checklist
Evidence checklist
0/4 checked
Evidence artifact (local-only)
What is a CubeSat Mission?
Captured: 2026-05-16T07:38:32.284Z · Level: Middle School · Track: orientation
Summary
Copyable class summary
Copy a readable summary for class notes, or copy JSON for a structured record. Local-only: nothing is submitted.
Evidence artifact (v1) Activity: What is a CubeSat Mission? Track: orientation Learner level: Middle School Captured: 2026-05-16T07:38:32.284Z Mission brief: (not provided) Selected inputs: - Learner level: Middle School - Mission objective: (not selected) Generated outputs: - (none captured) Checklist: - [ ] I can identify what the payload does for this objective. - [ ] I can explain a power or energy need for this mission. - [ ] I can name a data or communication constraint. - [ ] I can explain why pointing (ADCS) may matter for this mission. Observations: (not provided) Reflection: (not provided) Model boundary note: Teaching-grade software activity. Not a flight simulator, not a hardware run, no submission or grade. Policy reminder: - Local-only capture. Not submitted anywhere. Not a grade.
Evidence capture
Expected outputs learners should be able to show after the lab (Phase 9 evidence engine preview available).
- Selected mission objective recorded in the activity
- Top three subsystems identified for that objective
- One-sentence mission objective stated in the mission brief panel
- Self-check: payload, power, data/communication, and pointing considerations addressed
Reflection
Read a short mission brief; answer: what must this satellite accomplish for people on Earth?
Responses are not persisted in this preview unless a specific activity component adds storage later.
Assessment / quick check
In one sentence, what is your mission trying to accomplish, and name one design choice that follows from it?
Teacher notes
15-minute whole-class orientation before opening Mission Design; emphasize objective-first thinking.
Teacher guide
Run this in class
Next steps
Optional continuation: Track 1 orbit activities are available from the Learn hub (not required for Orientation).
15 min demo
Whole-class walkthrough + 1 objective decision + debrief.
45 min lesson
Pairs choose objectives, justify subsystems with cards, short reflection.
90 min lab extension
Add deeper trade-offs + rubric self-check + evidence capture + compare teams.
Facilitation prompts
- Ask teams to defend their top subsystems using requirement cards, not subsystem names.
- Have teams compare two objectives: what changed (power/data/pointing/comms) and why?
- Prompt an honest boundary sentence: what would you need to verify on real hardware or a higher-fidelity sim?
Expected evidence
- Chosen mission objective + primary payload phrase
- Top subsystems (with requirement-card justification)
- Short reflection on trade-offs and boundary awareness
- Local self-check summary (optional)
Common misconceptions
Mission objective is the same thing as the payload.
Objective is the goal; payload is the tool/service that supports it.
The CubeSat bus is basically just the payload.
Bus subsystems (power, comms, ADCS, OBC, structure, ground ops) make the payload possible.
Digital twin = real hardware / flight-ready proof.
This is teaching-grade software. It supports reasoning, not flight certification.
Communication is continuous.
Spacecraft contact is intermittent; downlink strategy matters.
Evidence = a grade.
Evidence here is copyable local notes; not submitted and not a gradebook row.
Local-only: this activity does not submit work, assign grades, or provide teacher visibility into student evidence.
Next activity
Suggested progression from the mission learning path. Links avoid missing activity routes.