User Guide

This guide supports those directly working within the Antaris Cloud Platform (ACP) to develop and operate satellites. Please use this document to learn about core platform concepts and workflows.

If you have any questions or comments, please contact the Antaris support team via email at [email protected].

1. Glossary

2. Satellite Design

This section describes the core satellite design process, which focuses primarily on satellite system architecture. Operational configuration and planning are addressed elsewhere.

2.1 Create a Satellite

From the DESIGN dashboard, simply click on the Create Satellite action. Give the Satellite a unique name and proceed on to the next step:

Unique Satellites may be created for many reasons, and users should feel free to use them to explore alternate design decisions. Each operational space vehicle in a constellation is represented by a unique Satellite object.

Proceed by entering a title for your satellite. Then, specify the satellite's orbital altitude and inclination

2.2 Configure Payloads

A satellite is defined primarily by the set of payloads intended to operate within it. This is critical input, as it defines the “load” to be supported by core satellite systems.

Iterate through the “Add Payload” process once for each desired payload. Components that support core system functions such as RF communication or power management are included in the satellite bus, which will come later in this process.

Selection of a payload category and subcategory allows ACP to provide more contextual filters that help identify the most appropriate Payload Device from the catalog.

The “Average Active Duration per Orbit” field helps calculate the power demand during a representative orbit. Similarly, "Required Pointing Accuracy" states the precision, allowing the payload to accurately target and capture specific areas.

If an appropriate Payload Device does not yet exist in the catalog, it may be defined using the “Add Payload Device” action:

By the end of this process, a summary of the load to be supported by the satellite will be presented in the form of “Size”, “Mass” and “Power” meters:

These requirements feed directly into the upcoming Bus Design selection process.

2.3 Configure Edge Devices

Payloads may access a nominal amount of onboard CPU, memory, and persistent storage. Satellites may optionally include Edge Devices to provide additional compute capacity to resident payloads. Edge Devices commonly contain GPUs or other hardware accelerators for specialized data processing.

To configure an Edge Device, choose from the supported components, indicate an average amount of time per orbit it will be active, and choose a quantity of SSDs to attach to it:

2.4 Choose Bus Design

When arriving at this stage, you can select different bus vendors, and ACP will have gathered enough input about the satellite to recommend an appropriate Bus Design based on the selected vendors:

As soon as you click on a Bus Design at this stage of the workflow, the load meters at the top will indicate how utilized the chosen Bus will be in each dimension. This feedback can be used to help understand how “full” the bus will be.

2.5 Configure 3D Model

To upload your own 3D model of the satellite, click on the 3D Model option. This will allow you to select and upload your model, replacing the current satellite 3D model with your custom version.

After making your selection, click “Save Satellite” and the Satellite is now ready to be used!

3. Satellite Designer

Enabling users to define and build a satellite’s profile by configuring the onboard objects. This includes specifying parameters like mass, moment of inertia (MoI), and orientation, as well as adding sensors or payloads.

To begin, click on the Satellite on the Satellite Designer. On the left panel, users will find options to add and configure sensors—currently supporting sun sensors, star trackers, and payloads. At the center of the interface, the satellite’s 3D model is visualized, allowing users to interact and understand the physical layout. The right panel displays the satellite's mass, orientation, and MoI details. At any point, clicking the satellite logo in the center will return you to the homepage.

3.1 Control Mode Configuration

Control modes define how the satellite should orient itself during different phases. These are critical for running meaningful analysis. Users can either select a predefined control mode or create a custom one.

To add a control mode, click the plus icon and enter a name for it. If your mode requires only a specific orientation, simply provide the RPY values. For more advanced control, define a vector-based control, specify the reference vector and the target entity. Once configured, your new control mode can be used in any future analysis.

3.2 Payload and Sensor Configuration

After selecting a payload, its corresponding mass and size will be displayed. Next, configure the orientation vector by defining how the payload should be aligned on the satellite bus. Set the horizontal and vertical FOV along with exclusion angles where angular limits beyond which sensor orientation should be avoided. These are set in relation to the defined entities (e.g., Earth, Sun)

The sensor analysis follows a similar workflow to payloads. Choose a sensor from the bus list, configure its properties and vector.

3.3 Analysis

This allows users to evaluate visibility and effectiveness under different scenarios. Once payload and sensor configuration is complete, move to the analysis phase. Select the duration for the analysis starting from the current UTC time, this would use the specified satellite’s orbital details as defined in the Satellite Designer. Then, add the relevant control modes that the satellite will perform during this period. You can add multiple control modes to compare results across different mission conditions. When ready, click Analyse.

3.4 Reports

After an analysis is complete, users can view detailed results in the Reports section. Each report includes both input configurations and output results. Specific to the payload or sensor used, as well as the selected control mode and entity. Users can filter or modify reports by switching between entities and control modes, enabling a flexible comparison of results.

4. Payload Development

Prior to physical satellite integration, application software must be developed to connect the SatOS™ control services to each payload. This development process utilizes ACP along with the SatOS Payload SDK. It is important that application developers review the SatOS Payload Developer Guide, as it describes the technical architecture and interfaces used to conduct this development activity.

The following diagram represents the high-level relationship between ACP and the elements operating outside of ACP:

The remainder of this section focuses on the ACP portion of the payload development process described above. It is vital that developers review the SatOS Payload Developer Guide before continuing.

4.1 Define Payload Sequence

Each Payload object contains a discrete set of Payload Sequences. Sequences represent individual requests that may be handled by Payload Application software. Individual sequences typically maps to a logical mode of operation.

Payload Sequences may also receive parameters. The “Default Sequence Parameter” field is used to set the default value sent to Payload Applications when executing a sequence. These parameters may be overridden later, as needed.

The “Data Generated” represents an estimated data that will be generated while handling the sequence. This helps in initial data modeling of the full satellite system and will be improved once representative values can be measured.

To manage Payload Sequences, first start at the DESIGN dashboard. Click on a Satellite, then choose one of its Payloads. Under the "Sequences" section, you can add a new sequence or use the available actions on each existing sequence to edit/destroy them.

4.2 Test Payload Sequence

To test a Payload Sequence, go to the "SIMULATE" and start by clicking 'Create New Scenario' Call to Action (CTA) selecting a Scenario with a HWIL instance for the target satellite. Be sure to configure all required payload interfaces correctly.

When prompted, click the "Download Remote Config" button to retrieve the required config bundle. Use this file locally with the SatOS Payload SDK to run your payload application software. The SDK will automate connecting the payload application to the ACP:

Once your payload application is successfully connected, the screen will advance to the HUD. Open the Console, and under TT&C, select the Command Type as Payload. Choose the target payload and then select a payload sequence to test. Default parameters will be set, but they may be overridden. The “Duration” represents a maximum amount of time granted to the payload application to handle the sequence before timing out. After deciding on this input, click “Execute now”:

The sequence will be encoded using an appropriate telecommand and sent for processing. then the telecommand will be acknowledged and logged in the output pane. The sequence will be forwarded by the ACP to the connected payload application for processing.

Any data that is staged for downlink by the payload application is automatically downloaded into ACP for review:

Note that the remote payload application may be restarted while its running, which can help to quickly develop application software.

5. GeoFeatures

Users can draw a fence or link a target over a specific region. These are used when creating satellite task plans, which is discussed later in this document.

5.1 Creating a GeoFeature

To define an area, users can use the Polygon tool to outline the desired region, or create a Target Track linked to that region. Alternatively, users can use the Upload option to import shapefiles in .zip format. Supported file formats include TopoJSON, GeoJSON, and KML.

Users can schedule payloads to the GeoFeatures, which will help in generating the satellite’s schedule.

6. Ground Communications

Within ACP, an operator may configure both the network of ground stations used for a mission as well as the radios employed onboard their satellites. ACP will automatically schedule ground contacts for Satellites operating on the platform, including both onboard scheduling as well as API-based scheduling via ground station provider APIs.

Users can identify which ground stations can support their mission through the "Ground Stations" section of the DESIGN dashboard.

6.1 Adding a GSP

ACP supports two main ground station providers: Atlas and Leafspace. To add them to your mission, go to the Map View, select the ground stations available under these providers, and click Add to include them in your GSP list.

6.2 Creating a Custom GSP with Ground Stations

Using the Map View and Direct Input feature users can create a Create a Custom GSP with Ground Stations

6.2.1 Creating Custom GSP via Map View

Creating GSPs through the Map View is a fast and efficient process, allowing users to quickly set up a provider and add ground stations with just a few essential details.

Go to Map View and add a ground station by providing all the required inputs. Under the Provider field, select Other, name your custom provider, and add the ground station. A new provider will be created automatically along with the ground station. Once you have configured the custom GSP with all the required ground stations for your mission, simply click Save to complete the setup.

Once you have configured the custom GSP with all the required ground stations for your mission, simply click Save to complete the setup.

6.2.2 Creating Custom GSP via Direct Input

Using the Direct Input, allows users to define the GSP in a more granular way. This level of detail is helpful later when operating the satellite.

Under the Ground Stations, click on "Add GS Provider" and choose Custom as the provider. You can then configure important details such as the API, MQTT topics, login credentials, and test configuration. Setting this up will help predict the upcoming ground passes for the ground stations added under the provider.

Once the GSP is added, you can assign individual ground stations to it.

6.3 Configuring Ground Stations within a GSP

Inside a specific GSP, users can add ground stations either by selecting them from the Map View or via direct input. Users can configure individual ground stations under their chosen GSP through either method.

6.4 MQTT Topic Configuration

Defines the ground links over which the satellite will downlink telemetry data and uplink telecommands. Setting up MQTT topics is essential for operating the satellite, Start by Specifying the the satellite ID (ideally provided by the GSP) then configure the ground links. These are defined within the scope of a Satellite object

7. Task Planning

Operational scheduling of a satellite begins with a Task Plan, which contains a prioritized set of Tasks. Each Task describes some desired activity with optional repetition and geographic requirements. Task Plans are considered generally reusable and tend to represent the “concept of operations” (ConOps) of a given satellite.

A Task Schedule is generated from a Task Plan for a desired period of time, which spans anywhere from a single orbit up to a few days. The operational state of the satellite (e.g. power level, physical location, previous activity, etc) is also considered during the scheduling process. The schedule will contain an optimized set of Tasks that will be executed onboard at specific times.

Once generated, a Task Schedule can be deployed to a target satellite during a ground station contact. Task Schedules can also be used within a Scenario to simulate mission operations, which is discussed later in this document.

7.1 Managing Tasks

Tasks must be defined before a Task Plan can be constructed. Navigate to DESIGN, choose a Satellite, click on Operations and then click on "Tasks":

Each Task represents a logical unit of work that can be scheduled. Each Task is defined by a single Payload Sequence, parametric overrides, and any relevant timing requirements.

The minimum duration field defines the minimal amount of time required for the scheduler to consider the Task for execution. The maximum duration will prevent scheduling of the Task longer than the indicated amount of time.

7.2 Managing Task Plans

Task Plans are templates of prioritized Tasks that can be used to repeatedly generate schedules for a Satellite:

It is common to define multiple Task Plans for each Satellite, typically modeling the nominal operations as well as one or more alternate plans.

When creating Task Plan, you are constructing a prioritized set of Tasks and their respective scheduling requirements.

Tasks are created ahead of time, then added to a Task Plan with additional scheduling requirements.

Several controls are available to influence when a Payload Task may be executed. The following screenshot demonstrates a "Geofence" geo-trigger.

The "Geo-Trigger" options are described below in detail:

• Use None when the task has no ground-based requirements.

• Use the Target Track option to require the satellite point towards a specific location on the ground during Task execution. Locations are defined using WGS84 latitude and longitude (decimal degrees) along with an altitude (km). The minimum elevation will limit which ground passes are considered, ensuring that Tasks are only scheduled when the satellite maintains the required elevation above the horizon as measured from the target location.

• The Geofence option limits Task execution to time periods when the satellite passes through some geographic area. A bounding box is used to define the area, represented by two WGS84 coordinates (the upper left and lower right points of the box).

The "Sun Exposure" defines lighting conditions under which the task should be executed:

• The task with Sunlit will only be executed when the satellite is in sunlight (i.e., not in Earth's shadow). This is useful for operations that rely on solar power or require illumination for imaging

• The task with Eclipse will only be executed when the satellite is in Earth's shadow (i.e., during orbital eclipse). This can be useful for observing celestial phenomena or reducing light interference.

• The task with Both can be executed regardless of whether the satellite is sunlit or in eclipse.

The "Orbit Direction" defines which part of the satellite’s orbit the task should occur in:

• The Ascending task will only be executed when the satellite is moving from the Southern Hemisphere to the Northern Hemisphere (i.e., increasing latitude).

• The Descending task will only be executed when the satellite is moving from the Northern Hemisphere to the Southern Hemisphere (i.e., decreasing latitude).

• The task with Both can be executed during either orbit direction.

In certain cases, an “Attitude Control Mode” must be selected:

• The Ground Track mode causes the satellite to maintain a stable orientation with respect to the earth. This can be useful for payloads that scan the ground such as IoT receivers or push-broom imaging sensors.

• The Sun Track mode allows the satellite to maintain a solar-oriented attitude during the Task. This can be useful for Tasks that are not sensitive to earth-relative orientation.

The "Satellite Orientation" defines how the satellite should be oriented during task execution:

• The Nadir makes the satellite points directly down toward the Earth’s surface (toward the center of the Earth). This is ideal for most Earth observation tasks like imaging, mapping, or remote sensing

• The Custom makes the satellite is oriented based on user-defined parameters, such as specific roll, pitch, and yaw angles. This is useful for specialized tasks like pointing at off-nadir targets

Use the “Frequency” controls to define the preferred number of times the Task should be scheduled within a given period of time.

8. Executing Scenarios

"SIMULATE" allows satellite developers and operators to explore a variety of real world scenarios and test how a given satellite will act.

8.1 Creating a Scenario

If you are creating the scenario for first time, Under "SIMULATE", use 'Create New Scenario' Call to Action (CTA) and select the Deployment mode as Scenario Simulation. For subsequent scenario creations, click the 'New' button in top right corner to create new scenario.

The first “Scenario Details” step prompts the user for a Scenario Title. This is a human-readable name that can be referenced later. Typically, this describes the purpose or scope of the Scenario.

8.1.1 Operation - ConOps

Choose ConOps or LEOP based on the type of operation you want to simulate Under Start Time, specify the scenario start time. This start time will later be aligned with the satellite's actual launch parameters, meaning the scenario reflects the satellite’s current state based on those inputs.

The Time Scaling Factor allows the simulation to run till 2X speed, enabling users to observe satellite operations, including onboard schedule execution, in accelerated time. This is helpful for quickly reviewing and validating tasks.

Next, add the Satellite Group that users want to include in the simulation. Once added, click on Orbital Details to configure the Initial Epoch and define the satellite’s orbital position using a timestamp and Keplerian elements. This input allows users to accurately place the satellite in orbit, ensuring that tasks can be executed and observed as intended.

Next, a user may configure the set of available Ground Stations for the Scenario. The Ground Stations listed in the interface are those that have been pre-configured for the mission. While the scheduler will automatically choose the best ground contact, it is useful to enable or disable access to certain ground stations to facilitate specific operational testing.

Users can import their own task schedule into the scenario. First, download a generated schedule—this process will be explained later in the document. Users can then modify the schedule to match specific mission requirements. Once the changes are complete, click on the Import button to upload the modified schedule to the scenario.

The final stage enables users to construct a relevant “Task Schedule” (This can be Optional) to execute within the Scenario. Choose a pre-existing Task Plan and a desired amount of simulated time:

ACP will generate a schedule, then snap the scenario (i.e. advance the simulation epoch). Drag or resize the time slider on the bottom of the screen to align it to a desired time period. In the example below, the slider has been shifted to match the two later tasks in the schedule rather than running for a large period of time between tasks:

Go to the Settings located at the bottom right of the screen to access various map options. From here, you can view eclipse zones, zoom in or out, resize the map, switch to a 3D Earth view, or change the map style to suit your preferences.

8.1.2 On-Board Schedule

This button opens a window displaying the onboard satellite schedule. It presents a sequential list of scheduled events, including telemetry and payload downlinks, payload operations, and planned uplinks.

The schedule status indicates whether each task will be executed as planned. It also highlights if a task is being preempted by a higher-priority activity, occurs outside the simulation window, or if the task’s execution conditions (as defined in the task plan) are not met due to orbital constraints.

8.2 Operation - LEOP

LEOP focuses on simulating the satellite’s initial deployment during the critical early moments following launch.Start by specifying the exact simulation start time, then proceed by adding the satellites involved in the LEOP scenario.

LEOP supports the Satellite's detumbling simulation. Following this, configure the Initial Epoch and Keplerian Elements accurately, ensuring the simulation reflects real post-launch conditions.

Define the satellite’s initial attitude conditions with Orentation and Angular rates then proceed with a desired amount of simulated time

8.2.1 Prediction Analysis

8.2.1.1 ConOps

After generating the schedule from ConOps ACP performs Prediction Analysis for a quick simulation preview to help users validate and refine their schedule efficiently

Explore satellite metrics generated after the Prediction Analysis by clicking on the Power, ADCS and Data Flow panels. This saves time and helps ensure your schedule is optimized accordingly before running full real-time simulations.

For example, if users observe that AOI scheduling or revisit times can be optimized, they can adjust the scenario metrics such as orbital parameters or simulation timeframe accordingly. These changes can be made quickly, allowing users to return to the Prediction window and reassess their impact within the simulation.

8.2.1.2 LEOP

After completing the Post-LEOP configuration, ACP performs a Prediction Analysis similar to the ConOps. You can explore the satellite metrics generated during this analysis by reviewing the Power and ADCS panels.

Once you are confident with the results of the prediction analysis, proceed to deploy the scenario.

8.3 Scenario Execution

Prior to deployment, review the Tasks in more detail using the "Schedule" action on the right side of the Task timeline: Once all inputs are set, proceed to deploy which begins execution of the Scenario

8.3.1 HUD

The Heads-Up Display offers a clear and concise view of your satellite, highlighting current tasks and upcoming events. Designed to support efficient real-time monitoring and informed decision-making.

Users can open multiple secondary windows using on-screen buttons. Each window can be dragged or pinned anywhere on the screen for ease of use.

• Top Left: Includes a Home button to return to the previous screen. Users can switch between satellite groups and individual satellites within the group using dropdown menu. The Orbital Details section provides specific orbital parameters of the selected satellite.

• Top Right: Contains 4 Quick Actions Panels: Onboard Schedule, Console, Telemetry, File Queue. Allowing full access to satellite operations directly from the HUD, ensuring operators can manage tasks efficiently in real time.

8.3.1.2 On-Board Schedule

Displays the detailed sequence of satellite events, including operations related to the Payload Server, Application, and Payload activity, followed by any changes in the ADCS control mode.

8.3.1.3 Console

The Command Console provides a real-time table of the most recent tele-commands and telemetry messages sent and received. Each entry includes whether the message is a TC or TM message, and uses color coding to indicate the message status.

Clicking on a message reveals more detailed information, including the undecoded hex data and the decoded JSON packet. These details help users analyze message behavior and system responses.

Message Colors:

• Yellow : A successful tele-command that triggered a telemetry response from the satellite

• Green : A telemetry response received in reply to a tele-command

• Blue : Beacon telemetry not triggered by any tele-command

• None : A tele-command that did not induce a detectable telemetry response by ACP

8.3.1.3.1 Commanding through the Console

The left side of the window features the Command Console, an interface that allows the user to send manual commands to the satellite. The operator can select the TT&C option to issue individual commands from the command database. Commands can be filtered by subsystem or by using the editable text field to search by command ID or command number.

Once a command is selected and configured, clicking "Execute" will send the command immediately. The corresponding telemetry related to the executed command will then be displayed to the user.

8.3.2 Plan

In addition to the HUD, the Plan and Monitor tabs, offers expanded details found in the Onboard Schedule, Ground Contacts, and Telemetry Displays.

The Plan tab contains two subtabs: Onboard Schedule and Ground Contacts.

The Onboard Schedule presents a more comprehensive list of schedule events, along with detailed information for each. Users can use the buttons in the top-right corner to manually import or generate satellite schedules.

The Ground Contacts lists all available ground stations in a table format, showing both upcoming and past ground contacts. Selecting a contact reveals additional details on the right side of the screen, including contact type, duration, start time, and a map image showing the ground station’s location.

8.3.3 Monitor

The Monitor tab offers an expanded graphical view of the satellite’s historical telemetry data, similar to what is available via the Telemetry Quick Action button, but in a larger and more detailed format.

These graphs include the same subsystem filters and analytical tools, allowing operators to efficiently analyze trends and performance metrics over time. At the top of the tab, users can switch between grid or list view based on their preference for organizing and viewing the telemetry data.

9. Mission Models

The Mission Models helps users design Satellite missions tailored to their specific needs, providing a flexible environment to design. Users can configure satellites, geofeatures, and ground stations to build their scenarios. This supports various analysis types, such as coverage, ground contact, and propulsion budget. With a visual interface and interactive tools, help users optimize and generate meaningful reports

9.1 Active Model

Users can create and manage mission elements like satellites, geofeatures, and ground stations. It provides intuitive tools to add, edit, and organize using a structured panel view. Each object type comes with flexible configuration options, allowing users to define orbital parameters, areas of interest, or ground station details. The Active Model serves for running analysis and generating reports

9.1.1 Satellites

To create new satellites, start by clicking the "+" icon under the Satellites section. You will be presented with three options: you can create a Single Satellite, set up a Group of Satellites, or import Satellites from TLE files. Each option allows for flexible configuration depending on your mission needs.

9.1.1.1 Creating Satellite

To begin, enter a name for your satellite. Next, choose the orbit type based on your mission requirements. You can select Custom to manually configure all orbital parameters, SSO which typically has an inclination of around 98°, or Polar Orbit with a fixed inclination of 90°. After selecting the orbit type, set the remaining orbital parameters as needed and click Create to add the satellite to your mission.

After a satellite is created, it will appear in the "SATELLITES" list. Click on the ellipses next to the satellite to explore more options. Use Edit to modify the satellite’s name and update its orbit configuration. Users can also duplicate, or delete the satellite using the corresponding buttons. The Config option allows users to update parameters such as the current swath, thruster configuration, and orbit color to suit their mission requirements.

9.1.1.2 Creating Group

Start by setting a reference orbit using the same steps as you would for creating a single satellite. Under Group Configuration, choose Single Plane, all satellites will share the same orbital plane. By default, satellites are spaced evenly within the plane. If you want to manually control the spacing, uncheck the "space evenly" option and enter your desired values.

Alternatively, choose Multi Plane to distribute satellites across multiple orbital planes. In this case, configure the total number of planes and the number of satellites in each plane. Use the plane separation angle to define the spacing between each plane, and apply inter-plane phasing as needed to adjust the relative positions of satellites between planes. Once all configurations are complete, click Create to generate the satellite group. In the active model, click on the group to view all the satellites associated with that group.

9.1.1.3 Creating TLE Track

Click the TLE Track option to create satellites from TLE data. Upload your TLE file, which can contain data for a single satellite or multiple satellites in bulk. If needed, you can download a sample format from ACP to help ensure your file is correctly formatted. Once the file is uploaded, ACP will automatically create satellites based on the TLE information provided.

To differentiate between manually created satellites and those uploaded via TLE, look for the launch symbol next to the satellite group. This icon indicates that the group was created using a TLE upload, helping users easily identify the source of satellite data within the active model.

You can double-click any object to rename it for better identification. Use the eye icon to hide or show objects on the map, helping reduce visual clutter during mission planning. Hover over any object to highlight its position on the map.

9.1.2 Geofeatures

Geofeatures represent AOI's on Earth. To add a new geofeature, click the “+” icon, and choose either a polygon or a point depending on your requirement. Once created, the geofeature will appear in the current list and will also be saved under the main Geofeatures section for future use.

9.1.3 Ground Stations

Displays all ground stations which are predined and user-created stations and stations available under the GSP. To add a new ground station, simply click the “+” icon and configure the necessary details. If any ground station associated with the GSP is deleted from this section, it will no longer be part of the GSP. Instead, it will appear as a standalone ground station on the "Ground Stations" page

9.2 Analysis

Enables users to evaluate their mission models. It offers tools like Coverage Analysis, Ground Contact Analysis, and Propulsion Budget Analysis. By selecting configured objects such as satellites, ground stations, and geofeatures, users can run detailed analysis over custom time durations and conditions. Each analysis provides actionable insights through reports and visual overlays.

9.2.1 Coverage Analysis

To analyze how effectively satellites observe an AOI. Start by selecting the relevant satellites and geofeatures, then define the start time and duration of the analysis period. You can specify the lighting conditions as Sunlit only, Eclipse only, or Both, depending on your mission requirements.

9.2.2 Ground Contact Analysis

This evaluates contact windows between satellites and ground stations. To perform the analysis, select the relevant satellites and ground stations, then specify the start time and duration for the analysis period.

9.2.3 Propulsion Budget Analysis

This calculates mission fuel requirements, thrust, delta-V and many more for a satellite. Start by selecting a satellite, then click the “+” icon to add a thruster, if not added already. Configure the thruster parameters based on your mission requirements. Next, define the orbit environment, satellite properties, and any perturbation forces.

9.3 Reports

All analyses generate detailed reports that include the user-configured inputs, computed outputs, and a map visualization of the relevant objects. You can filter reports by analysis type and easily differentiate them based on specific objects or configurations used.