1. The sonar room

Tom Clancy’s The Hunt for Red October makes sonar operators into heroes because they interpret faint signals under pressure. The desktop’s ground team has a similar job: watch a distant machine through limited sensors, decide what is normal, and intervene only when necessary. Good operations is not heroic. It is boring, until it is not.

Entry 190 designed the communications architecture. This entry sketches the people and processes on the ground.

2. The lean operations team

A first-generation desktop should be operated by a small team: perhaps five to ten people covering flight software, mission planning, payload integration, communications, and customer support. This is much smaller than a NASA mission control room, but larger than a single cubesat operator.

The team does not need to be in one building. Distributed operations, with on-call rotations and cloud-based tools, is realistic for a commercial platform.

3. Routine operations: scheduled and automated

Most routine work should be automated: power management, thermal control, attitude pointing, ground pass scheduling, and payload sequencing. The ground team reviews logs, updates schedules, and handles exceptions. The goal is that the desktop runs for days without manual commands.

Automation also reduces operations cost, which entry 179 identified as a critical risk.

4. Payload operations: customer-driven

Customer payloads need tasking. The operations model should let customers request tasks through a web interface or API: point the camera here, print this part, process this dataset, move the tug there. The operations team approves, schedules, and monitors execution.

As trust builds, some customers can be given direct scheduling windows with automated safety checks, reducing the operations bottleneck.

5. Anomaly response

When something goes wrong, the team needs a clear escalation path: automated safe mode first, then ground intervention, then customer notification if a payload is affected. The desktop should have multiple levels of safe mode, from temporary pause to full survival configuration.

The key discipline is to practice responses before they are needed. Anomaly drills, like fire drills, feel silly until they matter.

6. Software updates and maintenance

The desktop’s software will need updates: bug fixes, security patches, new features, new payload interfaces. The operations model must include a way to upload, verify, and roll back software changes. A failed update should always have a recovery path.

This is standard practice on the ground but harder in orbit. The desktop inherits the second platform’s software update discipline.

What this changes

  • The desktop is operated by a small, distributed team with heavy automation.
  • Routine operations run autonomously; customer tasking is scheduled through an interface.
  • Anomaly response starts with automated safe modes and escalates to human intervention.
  • Software updates require verification and rollback capability.
  • The next leisure entry can estimate what all of this costs.