Importing Maneuvers

For the complete documentation index, see llms.txt.

When a maneuver or group of maneuvers have been optimized using a third-party tool, they can be imported via the Import button in the /burn-plan page using an OCM file (CCSDS compliant). For more information, check the OCM Format. A pop up will open to allow for the file upload: Import Maneuvers

File Requirements

Your OCM file must meet several validation rules before it can be imported. Key requirements include:

File must be in OCM format (CCSDS 502.0-B-3), maximum 10 MB
Every maneuver block must include MAN_BASIS = PLANNED
Each maneuver must define a thrust vector (THR_X, THR_Y, THR_Z) with at least one non-zero component
Specific impulse (THR_ISP) is required and must be between 50 and 10,000 seconds
A physical properties block with WET_MASS is required
Maneuver IDs must not contain special characters (! * ' ( ) ; : @ & = + $ , / ? # [ ])
Maneuver time ranges must not overlap within the file
Spacecraft identifiers in the file must match your VALAR spacecraft record (case-insensitive)

For the complete list of validation rules, accepted reference frames, and field requirements, see VALAR Import Requirements.

Merging Existing Maneuvers

When a group of maneuvers is imported for the first time, new entities will be created. If data for the period already exists and needs to be merged, the following merge strategies are available:

Update: Maneuvers with a MAN_ID that already exists in VALAR will replace the existing record. The existing maneuver must be in PLANNED status — you cannot overwrite a telemetry-reported maneuver through a planned import. Maneuvers with new IDs must not overlap in time with any existing maneuvers for the same spacecraft.
Replace: All existing maneuvers within the imported time range are removed and replaced by the file contents. This action cannot be undone.

Once the import is complete, maneuvers will appear on /burn-plan. After execution, users can notify actual performance values following the reporting maneuver execution features.

API Endpoints

Importing maneuvers can be automated via the API using the endpoints:

POST /v1/maneuvers/generate/import: to update maneuvers
POST /v1/maneuvers/generate/import/override: to replace maneuvers

Troubleshooting

Below are the errors you may encounter when importing maneuvers, along with guidance on how to resolve them:

Error Message	Description
The [file] parameter is empty.	No data file was provided, or the file content is empty.
File not found:	The system could not find the file at the specified location.
File exceeds the 10MB size limit.	The file is larger than the allowed 10 MB limit.
Unsupported file format.	The file type or structure isn’t recognized or supported. Supported format is OCM.
Error encountered:	An issue occurred while parsing the file. Check that the file is well-formed OCM.
Unsupported file format: not all maneuvers include the MAN_BASIS field.	Every maneuver block must include a `MAN_BASIS` field.
Unsupported file format: no maneuvers found.	No maneuver data was found in the file. The file must contain at least one maneuver block.
Unsupported file format: not all maneuvers are planned. Conflicting maneuver:	All maneuvers in a planned import must have `MAN_BASIS = PLANNED`.
and have overlapping dates.	Two maneuvers have overlapping time ranges. Adjust the epochs so they do not overlap.
Spacecraft info mismatch. Received ID: , expected ID:	A spacecraft identifier in the file does not match the record in VALAR. Verify name, COSPAR ID, and NORAD ID.
Spacecraft with ID not found.	No spacecraft in your organization matches the identifiers in the file.
Invalid maneuver ID: . Maneuver IDs cannot contain the following characters: ! * ’ ( ) ; : @ & = + $ , / ? # [ ]	The maneuver ID contains reserved characters. Rename the maneuver ID to use only allowed characters.
Thrust vector is missing or zero for maneuver: . OCM files must include THR_X, THR_Y, THR_Z with at least one non-zero component.	All three thrust components are zero or missing. At least one must be non-zero.
ISP (specific impulse) is missing for maneuver: . OCM files must include THR_ISP.	The `THR_ISP` field is missing from the maneuver composition. Add specific impulse data.
ISP value for maneuver is outside valid range [50, 10000] seconds.	Specific impulse must be between 50 and 10,000 seconds.
WET_MASS is missing from the OCM physical properties block. OCM files must include a PHYS block with WET_MASS.	Add a `PHYS` block containing `WET_MASS` to your file.
Invalid reference frame: . Valid reference frames are:	The `MAN_REF_FRAME` is not supported. See Supported Reference Frames.
No planned maneuver found with ID .	In Update mode, the existing maneuver with this ID is not in PLANNED status and cannot be overwritten.
No maneuver found with ID .	The system could not find a maneuver with the given ID.
An unexpected error occurred.	An unknown error occurred during processing. Contact support if the issue persists.

Spacecraft Management

Orbit Analysis

Measurements

Ephemeris Generation

Maneuver Operations

Security & Access

STM

Areas of Interest

Automation

Attitude

Passes

File Requirements

Merging Existing Maneuvers

API Endpoints

Troubleshooting

​File Requirements

​Merging Existing Maneuvers

​API Endpoints

​Troubleshooting

File Requirements

Merging Existing Maneuvers

API Endpoints

Troubleshooting