MissionOS

Small operators often run telemetry viewers, command tools, spreadsheets and pass plans as separate tools. The state of the mission is then spread across them, and handovers between operators depend on notes.

MissionOS is designed to provide the following.

• Telemetry display and history for each spacecraft, with limits and alerts.
• Command preparation and review before release.
• Health monitoring across a fleet, with one view per spacecraft.
• Mission timelines for planned activities and ground contacts.
• Operating procedures written as repeatable, reviewable workflows.

An example of how an operations team would use MissionOS. The steps are illustrative.

1. The operator opens the plan for the next ground contact.
2. Telemetry from the previous contact is reviewed against its limits.
3. A command sequence is prepared and reviewed by a second operator.
4. The sequence is released during the contact, through SpaceShield command controls.
5. The result is written to the mission timeline for the next shift.

MissionOS takes ground contact windows from GroundNet, conjunction alerts from OrbitalIntel, anomaly findings from Aplark AI and command authorisation from SpaceShield. Interfaces to a partner spacecraft, such as telemetry formats and command definitions, are specified with that partner.

• A written mission workflow for the partner spacecraft type.
• A telemetry and command mapping for one spacecraft.
• Results of a test run against simulated telemetry.
• A list of open requirements for the partner team.

Pilots are scoped with each partner. See the Design Partner Program.

MissionOS does not replace spacecraft flight software or the ground station radio. It works with the telemetry and command interfaces that a spacecraft already provides.