Date

3 April 2025

Category

Blog, Engineering, Space

No comments

Sara, Work Area and Project Manager, StarionPlanetary space missions can travel for years to reach their final destination. Before they arrive, their instruments may be used during flybys of other planets, but otherwise they are likely to be inactive for most of their long journey. To ensure they are still working as planned when they finally arrive, the mission operations teams ‘wake them up’ periodically to test them.

This week and next, the instruments on the BepiColombo and Juice spacecraft will undergo routine checks over several days. This testing will be supported by SPOT Cruise, a web-based tool developed by Starion’s experts based at the European Space Agency’s (ESA’s) European Space Astronomy Centre (ESAC) in Spain. Sara de la Fuente, Starion Work Area and Project Manager, explains what SPOT Cruise is and why it’s important for the success of these ESA missions.

For space missions that have a long cruise phase, like Juice, which is due to take 8 years to reach Jupiter, it’s important that the payload teams can be confident the instruments will work when the spacecraft reaches its final destination. Periodically, therefore, the instruments are checked to make sure everything is OK. We support these payload checks for Juice and BepiColombo using the Science Planning Operational Tool (SPOT) Cruise, which was originally developed by Starion for BepiColombo and then adapted for the Juice mission.

The payload checks typically take 3 to 4 days, and are carried out approximately every 6 months. Coincidently, it just so happens that payload checks are taking place for both missions in the first half of April. For Juice, which launched 2 years ago, this will be its third payload check. For BepiColombo, which launched in 2018, this is its 13th.

BepiColombo SPOT Cruise screenshot
SPOT Cruise BepiColombo command request files (CRF) editor dashboard

What is SPOT Cruise?

The preparation and delivery of payload command requests – the instructions uploaded to the spacecraft to tell each instrument what to do – are fundamental to ground segment mission planning. These requests, typically created by payload teams, mission managers and satellite operators, are integrated into mission planning and control systems. At ESA’s European Space Operations Centre (ESOC), these payload requests are part of a broader concept known as command request files (CRFs), which encapsulate various operational requests.

SPOT Cruise was developed to generate and deliver payload operations requests (POR/PDOR), a specific subtype of CRF. These requests align with the relevant mission information database that is integrated into the ESOC ground-based data systems.

Although it was initially created solely for BepiColombo, this approach has demonstrated its adaptability in subsequent missions including Juice; the version used for the latter is commonly referred to as SPOT JUICE.

The widespread adoption of a centralised framework by ESA mission operations centres has proven to be a highly effective solution. Providing a unified platform for payload command request management streamlines interactions with diverse end-users, which enhances operational efficiency and fosters collaboration. Workflows are more efficient, operational overheads are reduced and mission planning is more accurate.

BepiColombo Mercury flyby screenshot
BepiColombo SPOT Cruise 3D visualisation of a Mercury flyby

A pivotal role for planetary mission operations

SPOT Cruise has been used many times throughout the journeys of both missions so far, supporting planetary flybys and any intervening payload checks. A standout feature of SPOT Cruise is its simulation capability, which allows teams to verify how resources, such as power and data volume, are being used. It also benefits from a 3D visualisation tool.

By combining advanced functionality with user-centric design, the SPOT Cruise tool is playing a pivotal role in supporting the scientific objectives of both missions.

Overall, this solution, developed by Starion, represents a significant advance in the management of payload command requests for ESA missions. Its successful implementation in missions like BepiColombo and Juice, and its potential adoption in future missions, both highlight its effectiveness, scalability and adaptability. It’s setting a new standard for payload command request management, ensuring efficient, reliable and cost-effective mission planning and operations support.

ESA Juice mission milestones
Milestones for ESA’s Juice mission – the long cruise phase makes it essential to check the instruments periodically. Image © ESA / ATG

Main image: Juice spacecraft; © ESA (credit ATG Medialab)