Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

The Onboarding Process

The pre-mission, integration phase is called Onboarding.

Typical Work Items:

  1. The collection of information about satellite radio by Infostellar
  2. The sharing of information about the ground station with the user
  3. The selection of ground stations to use by the user
  4. The filing of ITU applications by either the user or Infostellar
  5. The creation of user accounts and assets in StellarStation by Infostellar
  6. The introduction of users to StellarStation browser tools by Infostellar
  7. The connection of the satellite mission control software to StellarStation for automated satellite mission operations
  8. The inclusion of StellarStation into satellite operational procedures by the user
  9. The testing of satellite mission operations and software with StellarStation in-the-loop

The collection of information about satellite radio by Infostellar

Infostellar will request that the satellite team understand their radio and to provide relevant documentation about the radio. This includes information such as intended usage during the mission, specifications, ICDs, etc.

The sharing of information about the ground station with the user

Infostellar will share information about the ground station with the satellite team. This includes information like the location, general availability, price, supported frequencies, etc.

The selection of ground stations to use by the user

The satellite team must choose the ground stations they want to use. It is highly encouraged to do this as early as possible.

Consider:

  1. Communication channels used (RF, Optical, etc)
  2. How much data needs to be moved
  3. How often data needs to be moved

The filing of ITU applications by either the user or Infostellar

The satellite will require proper ITU filings to operate. These filings can be made by the satellite team or with the assistance of Infostellar.

The creation of user accounts and assets in StellarStation by Infostellar

Infostellar staff will create the relevant assets in StellarStation (organization, satellite, channels, etc) and add users to the organization.

The introduction of users to StellarStation browser tools by Infostellar

Infostellar staff can introduce the users to StellarStation by refering them to this guide, walking them through the browser tools, and answering any questions the users may have.

The connection of the satellite mission control software to StellarStation for automated satellite mission operations

The satellite team must integrate with StellarStation via the CLI or API if they intend to automate operations. Infostellar staff can assist with this process.

The inclusion of StellarStation into satellite operational procedures by the user

The satellite team must consider StellarStation services and procedures when creating their own operational procedures. It is highly encouraged to ask for advice from Infostellar staff about how best to include StellarStation in operational procedures.

The testing of satellite mission operations and software with StellarStation in-the-loop

It is highly encouraged that the satellite team include StellarStation in-the-loop during testing of any integrated software and runthrough of operational procedures.

Generalized Satellite Operation Flow

Your team probably already has a good idea of how operations might work, but here is an example anyway:

Generalized Satellite Operation Flow

Generalized Mission Control Software Architecture

Your team probably already has a good idea of how the MCS should work, but here is an example anyway: Generalized Mission Control Softare Architecture

Commonly Used API Services

  1. AddTle(): Adds a new TLE to StellarStation for the satellite.
  2. GetTle(): Gets the TLE that is registered in StellarStation for the satellite.
  3. SetTleSource(): Set the TLE source to automatic (pulled from NORAD) or manual (updated by you).
  4. ListUpcomingAvailablePasses(): Gets a list of upcoming passes that are available for reservation.
  5. ReservePass(): Reserves a pass (becomes a "plan") during which communications may occur.
  6. ListPlans(): Gets a list of plans for the satellite.
  7. CancelPlan(): Cancels a plan for the satellite.
  8. OpenSatelliteStream(): Opens a bidirectional stream. Commands and ground station configuration requests can be sent. Telemetry, event, and ground station monitoring data can be received.

API Usage Tips

  1. Log usage
  2. Handle errors
  3. Test well and often
  4. Make use of ground station monitoring data