Design Partner Program for satellite operators

The programme is for organisations that operate, or are preparing to operate, one or more satellites and want to shape the software they will use. Typical partners are:

• Commercial satellite operators with a small fleet.
• New space companies preparing a first mission.
• Research and national organisations running their own ground segment.

A pilot is a bounded piece of work, agreed in writing before it starts. It covers three things:

• Integrations: the telemetry, command, ground station and orbital data interfaces that connect OrbitalOS to the partner systems.
• Testing requirements: what must be shown, on what data, before the partner would use a workflow operationally.
• Workflows: the operating procedures, reviews and approvals the partner team follows, written as OrbitalOS workflows.

Testing starts in a simulated environment. See the OrbitalOS Simulator.

• Written integration specifications for the partner systems.
• A test plan and test results for the agreed workflows.
• Module deliverables listed on each module page, for example for MissionOS.
• Direct access to the engineers building OrbitalOS during the pilot.

Module pages: OrbitalOS modules.

Pilot projects are priced individually, after a scoping call, according to the number of spacecraft, the modules involved and the integration work. There is no standard price list for pilots.

1. Mission architecture call to understand the mission and ground segment.
2. Written pilot scope, deliverables and price.
3. Pilot, with agreed review points.
4. Review against the test requirements set at the start.
5. Annual licence, based on the number of spacecraft and modules in use.

Annual licences are structured in four tiers. Prices are starting points. Final terms are agreed with each organisation.