
“Before you fly anything, your team needs to know who runs what.”
Assign the three roles, then go and find the spacecraft on the console. Ten questions are scored in the platform, and seven of them are about the fleet rather than the crew.
BRIEF THE MISSION
Mission One puts your team on nine identical Microsat spacecraft in low Earth orbit, with three ground stations holding continuous contact and forty minutes of run time at real speed. Nothing is scripted to go wrong, and that is deliberate: this is the only mission where the platform does not act on you. Identical is the word that matters. A reading you take off one spacecraft is a reading that should hold across all nine, so anything that does not match is telling you something.
- Spacecraft
- Nine identical Microsats
- Orbit regime
- Low Earth orbit, circular
- Altitude
- About 722 km
- Inclination
- 40 degrees
- Run
- 2400 seconds at 1.0x
- Ground stations
- London, Dubai, Singapore
- Scripted events
- None
Orient the team and run nominal operations.
THREE ROLES, NINE SPACECRAFT
Nine identical Microsats, three ground stations in continuous contact, and nothing scripted to go wrong. The work splits three ways and it is not an even split: Satellite Operations carries the spacecraft and the link, Payload Operations carries the power chain, and the Mission Lead carries the authority calls. Click a role to see what it holds this mission.
You direct. You do not work a console.
- · Own the objective for the window
- · Declare go for payload operations once comms checkout is complete
- · Name who commands the sun-pointing manoeuvre and who verifies it
- · Take the first call when downlink quality will not carry the tasking
- · Call go / no-go on commanded actions

READING THE SPACECRAFT
Five reads carry Mission One: where to look, where the spacecraft are, what they are making, where they are pointed, and how well they are heard. Nine identical vehicles means a reading that holds on one should hold on all nine, so each read is also a comparison. Click a step for the reasoning behind it.
Controls, Images, Schedule, Telemetry, Messages, Plots, Map and Timeline. Two of them can hold the same quantity in different forms, so before you go looking, name what you need: a value, a trend, a position, or a time. The surface follows from the kind of question. An operator who skips that step searches instead of reads, and a contact window does not wait.
FLY THE MISSION IN ZENDIR
Zendir, the digital twin and mission simulation platform Kestrel procured, replicates your satellite operations center. Everything you rehearsed here you now do for real inside it: one mission objective and ten scored questions. The ten questions land on the console reads and the authority calls you just walked. Run it in three steps: take your assigned consoles, fly the one objective and answer the ten questions in platform where they are scored, then note the score and come back here for the debrief. Your facilitator provides Zendir access, and two things must be true before you fly.
This mission is worth 100 points, scored in-platform. Points accumulate across Missions One through Five, and the highest cumulative team finishes as the Top SCOR Team.
NOW THAT YOU ARE BACK
Zendir scored your mission out of 100 toward the Top SCOR Team standings. Note where you landed, then run the debrief while it is fresh. Work these three questions in order; the last one is the one that becomes an engineering update in the quarterly SCOR exercise, the standing review where SCOR and Satellite Design & Engineering act on mission findings.
Go around the crew once, one observation each, no discussion until everyone has spoken. Write the observations down before debating them; the first answer is usually the honest one.
FOCUS.
Mission One is complete: you flew it in Zendir and your score is on the board. Mission Two takes the same crew into a working Earth-observation flight, where the windows are short, the tasking is real, and there is a product at the end that somebody downstream will act on.
