uLearnMission workspace
Phase 01
Mission Intake
A satellite is operating in a region where small, fast-moving particles may strike exposed surfaces. The team’s job is to reason from a simple collision model toward a defensible protection concept.
Mission objective
Use the existing Rain Collision Lab as an analogy for relative motion, exposed area, impact angle, and particle flux. Then develop a concept-level satellite strategy that reduces meteor-strike risk while preserving mission function.
Phase 02
Requirements & Constraints
Translate the mission into testable expectations and design limits before choosing a concept.
| Type | Statement | Why it matters | Use? |
|---|
Phase 03
Concept Design
Generate candidate mitigation approaches before evaluating them. Keep concepts broad and mechanism-focused.
Phase 04
Rain Collision Lab
The Rain Collision Lab remains a RetroWeb tool. uLearn launches it and frames what to observe.
Linked RetroWeb Lab
Open the existing lab in the center, in a floating HUD window, or in a full page.
Phase 05
Analogy Mapping
Use the rain model carefully. Map the useful parts and name the limits.
| Rain model | Satellite impact model | Design implication |
|---|
Phase 06
Trade Study
Compare concepts using common criteria. This is a simple concept-screening matrix, not a final engineering analysis.
| Concept | Impact reduction | Mass penalty | Complexity | Reliability | Mission impact | Score |
|---|
Phase 07
Preliminary Design
Turn the selected concept into a coherent mitigation plan.
Phase 08
Design Review
Check that the concept is traceable, justified, and honest about limitations.
Phase 09
Final Recommendation / Handoff
Compile the mission reasoning into a clean recommendation that can be copied or downloaded.