Detailed Scenarios in Context
This section provides contextual information of the detailed scenarios that have been conducted so far.
ORB17 Detailed Scenario
The ORB17 Detailed Scenario Exercise is the fourth detailed scenario exercise of the JUICE Strategic Science Planning after following the Callisto flyby 21C13 [21C13], [1C13], the Europa flyby 7E1 [7E1], and the PJ21 [PJ12] scenarios. The SOC also performed an initial internal Payload Operations Model scenario analysis [6E1].
All the relevant information of the scenario is available at the ORB17 JUICE Science Operations Confluence Page
For this exercise the SWT#22 SOC report recommended to focus on a multi-target scenario covering a (high-latitude) perijove and a flyby and a longer period, closer to a full MTP (28 days). Given that the high-latitude perijoves had not been studied in detail yet, this scenario could help confirming whether WG3 and WG4 could share resources in an effective manner or not. In addition, due to the number of similar Callisto flybys at close altitude this scenario could also be useful to extend its outcome to other flybys.
The chosen scenario period was Orbit 17 covering from Apojove 16 to Apojove 17 that includes a low altitude Callisto flyby 16C9 with an approximate period of 21 days from 2032-12-18 until 2033-01-08. The high latitude perijove ensured involvement of WG3 and WG4 whereas the Callisto flyby also guaranteed the involvement of WG1 and WG2 therefore requiring the active involvement of all the instruments in the exercise.
The objectives of the ORB17 Detailed Scenario Exercise are as follows:
to refine the planning process based on the PJ12 detailed scenario exercise,
to assess the feasibility of almost a full MTP with multiple targets,
to focus on identifying re-usability of the planning exercise outcome for other parts of the Jupiter Tour.
The ORB17 training activity is labeled as SGS-TR-2-Q4. The scenario name is S008_ORB17, more details
are provided in Scenario Name.
The complete report of the PJ12 Detailed Scenario Implementation is available at [ORB17].
Geometry
The ORB17 scenario has been developed using the trajectory crema 5_1_150lb_23_1_a3 [CRA3] as the applicable baseline for the Level 0 segmentation.
The time window covered by this scenario is from 2032-12-18T17:32:33 to 2033-01-08T21:05:31 (UTC). The duration is 21 days, 3 hours, and 33 minutes. Below we provide a summary of some relevant geometrical information of this orbit:
- Callisto Flyby:
Event Time: 2032-12-28T07:27:21Z
Altitude [km]= 304.157
Sub-SC lon [deg]= 297.2
Sub-SC lat [deg]= 6.8
Sub-SC phase [deg]= 72.2
Ground track velocity [km/s]= 5.1
- Perijove 17:
Event Time: 2032-12-31T09:28:04Z
Distance to Jupiter [RJ]= 15.75
Sub-SC lon [deg]= 1.3
Sub-SC lat [deg]= -23.6
Sub-SC phase [deg]= 74.5
Initial Segmentation and geometry from the SHT Timeline tool.
Geometry Events
The geometrical events calculated by the SOC that are present in the detailed scenario period are provided by two different files; a CSV event file and an EPS Event File (Event File (EVF)).
These events are typically ground station visibility, transits, perijoves, flybys, S/C Flip events, etc.
The location of the CSV geometry event file within the The JUICE Pre-operational Repository
is: PLANNING/SCENARIOS/<scenario_id>/ENVIRONMENT/EVENTS/GEOMETRY. Filenames are
as follows:
CSV event file:
MISSION_TIMELINE_EVENT_FILE_<scenario_id>.csvEVF event file:
EVT_GEOPIPELINE_<scenario_id>.evf
Please note that these events are already available in the Timeline Tool and they can be accessed from the Timeline configuration option.
Trajectory Segmentation
The starting point of the OTH process has been the skeleton segmentation available at kick off
(details can be found in the plan segmentation_Orb17_ONLY_OPPORTUNITIES_v3 of the SHT Timeline tool).
Besides a reduction in one of the downlink segments and the usual downlink changes to accommodate the flyby and its inbound leg, no further changes were done at segmentation level due to the updated rules for the operational blocks namely:
Wheel Off-loadings cannot be moved 1h anymore.
Optical Navigation slots are fixed and cannot be moved 24 hours
ORB17 Scenario Timeline
The ORB17 detailed Scenario process took place between November 2024 and April 2025, with an effective duration of 6 months but with interruptions due to the Payload Checkout Window 3 (PCW#3) activities.
The structure of the process was as follows:
Meetings on Thursdays at 15:30h CEST/CET with a maximum duration of 90 minutes.
SOC deliveries deadlines on Fridays EOB
PI deliveries deadlines on Wednesdays at 12:00h CEST/CET
The detailed timeline of the scenario is provided hereunder:
Event |
Item |
Time (CEST/CET) |
|---|---|---|
Meeting 1 Pre-kick-off |
Meeting |
2024-10-01 15:30:00 |
Delivery S1 (SOC→PI) Starting Kit |
SOC Delivery |
2024-11-15 12:00:00 |
Milestone 1 Activity Kick-off |
Milestone |
2024-11-21 12:00:00 |
Meeting 2 OTH#1 Kick-off |
Meeting |
2024-11-21 15:30:00 |
Meeting 2 OTH#1 Segmentation follow-up |
Meeting |
2024-11-28 15:30:00 |
Delivery S2 (SOC→PI) OPL S01P00 |
SOC Delivery |
2024-12-05 12:00:00 |
Milestone: OBS Database Frozen |
Milestone |
2024-12-05 12:00:00 |
Delivery P1 (PI→SOC) Science Plan |
PI Delivery |
2024-12-11 12:00:00 |
Delivery P2 (PI→SOC) OPL S01PYY |
PI Delivery |
2024-12-11 12:00:00 |
Meeting 3 OTH#2 Science Plan |
Meeting |
2024-12-12 15:30:00 |
Delivery S3 (SOC→PI) OPL S02P00 |
SOC Delivery |
2024-12-13 12:00:00 |
Delivery P2 (PI→SOC) OPL S02PYY |
PI Delivery |
2025-01-08 12:00:00 |
Meeting 4 Observation Plan 1 (OTH#3) |
Meeting |
2025-01-09 15:30:00 |
Delivery S4 (SOC→PI) OPL S03P00 |
SOC Delivery |
2025-01-10 12:00:00 |
Delivery P3 (PI→SOC) OPL S03PYY |
PI Delivery |
2025-01-15 12:00:00 |
Meeting 5 Observation Plan 2 (OTH#4) |
Meeting |
2025-01-16 15:30:00 |
Delivery S5 (SOC→PI) OPL S04P00 |
SOC Delivery |
2025-01-17 12:00:00 |
Pointing Design Workshop |
Workshop |
2025-01-22 14:30:00 |
Delivery P4 (PI→SOC) OPL S04PYY |
PI Delivery |
2025-01-22 12:00:00 |
Milestone 2 OPL Frozen |
Milestone |
2025-01-23 12:00:00 |
Meeting 6 Pointing Harmonisation 1 (PTH#1) |
Meeting |
2025-01-23 15:30:00 |
Delivery S6 (SOC→PI) PTR S01P00 |
SOC Delivery |
2025-01-24 12:00:00 |
Delivery P5 (PI→SOC) PTR S01PYY |
PI Delivery |
2025-02-05 12:00:00 |
Meeting 7 Pointing Harmonisation 2 (PTH#2) |
Meeting |
2025-02-06 15:30:00 |
Delivery S7 (SOC→PI) PTR S02P00 |
SOC Delivery |
2025-02-07 12:00:00 |
Delivery P5 (PI→SOC) PTR S02PYY |
PI Delivery |
2025-02-19 12:00:00 |
Meeting 8 Pointing Harmonisation 3 (PTH#3) |
Meeting |
2025-02-20 15:30:00 |
Delivery S8 (SOC→PI) PTR S03P00 |
SOC Delivery |
2025-02-21 12:00:00 |
Delivery P6 (PI→SOC) PTR S03PYY |
PI Delivery |
2025-03-05 12:00:00 |
Meeting 9 Pointing Harmonisation 4 (PTH#4) |
Meeting |
2025-03-06 15:30:00 |
Delivery S9 (SOC→PI) PTR S04P00 |
SOC Delivery |
2025-03-07 12:00:00 |
Delivery S10 (SOC→PI) PTR S05P00 |
SOC Delivery |
2025-03-07 12:00:00 |
Delivery S11 (SOC→PI) PTR S06P00 |
SOC Delivery |
2025-03-07 12:00:00 |
Delivery P7 (PI→SOC) OPL Callisto |
PI Delivery |
2025-03-12 12:00:00 |
Delivery P7 (PI→SOC) ITL S01PXX |
PI Delivery |
2025-03-12 12:00:00 |
Meeting 10 Pointing Harmonisation 5 (PTH#5) |
Meeting |
2025-03-13 15:30:00 |
Delivery S11 (SOC→PI) ITL S01P00 |
SOC Delivery |
2025-03-14 12:00:00 |
Meeting 11 Instrument Timeline Harmonisation 2 (ITH#2) |
Meeting |
2025-03-27 15:30:00 |
Delivery S12 (SOC→PI) ITL S02P00 |
SOC Delivery |
2025-03-28 12:00:00 |
Delivery P8 (PI→SOC) PTR Callisto |
PI Delivery |
2025-03-26 12:00:00 |
Delivery P9 (PI→SOC) PTR Callisto |
PI Delivery |
2025-04-03 12:00:00 |
Delivery P9 (PI→SOC) ITL S02PXX |
PI Delivery |
2025-04-03 12:00:00 |
Meeting 12 Instrument Timeline Harmonisation 3 (ITH#3) |
Meeting |
2025-04-03 15:30:00 |
Delivery S12 (SOC→PI) ITL S03P00 |
SOC Delivery |
2025-04-04 12:00:00 |
Delivery P10 (PI→SOC) PTR Callisto |
PI Delivery |
2025-04-10 12:00:00 |
Delivery P10 (PI→SOC) ITL S03PXX |
PI Delivery |
2025-04-10 12:00:00 |
Meeting 13 Instrument Timeline Harmonisation 4 (ITH#4) |
Meeting |
2025-04-10 15:30:00 |
Delivery S14 (SOC→PI) ITL S04P00 |
SOC Delivery |
2025-04-11 12:00:00 |
Milestone 3 PTR Frozen |
Milestone |
2025-04-11 12:00:00 |
Milestone 4 ITL Frozen |
Milestone |
2025-04-11 12:00:00 |
Delivery P11 (PI→SOC) Activity Feedback |
PI Delivery |
2025-04-23 12:00:00 |
Meeting 12 Wrap-up (ITH#3) |
Meeting |
2025-04-24 15:30:00 |
Delivery S14 (SOC→PI) Scenario Report |
SOC Delivery |
2025-05-12 12:00:00 |
Milestone 5 Scenario Report |
Milestone |
2025-05-12 12:00:00 |
ORB17 Detailed Scenario Timeline
PJ12 Detailed Scenario
The PJ12 Detailed Scenario Exercise is the third detailed scenario exercise of the JUICE Strategic Science Planning after following the Callisto flyby 21C13 [21C13], [1C13] and the Europa flyby 7E1 [7E1] scenarios. The SOC also performed an initial internal Payload Operations Model scenario analysis [6E1].
All the relevant information of the scenario is available at the PJ12 JUICE Science Operations Confluence Page
One of the goals of the 21C13 and 7E1 exercises was to get a realistic Data Volume (DV) generation for the flybys, as requested by the SWT as part of the Level 0 trajectory segmentation. For 21C13, the exercise was also used to assess the planning process for both generating relevant procedures and identifying lessons learnt and improvements whereas for 7E1 also used the result for a scenario performance analysis for the Mission Qualification and Acceptance Review (QAR).
The objectives of the PJ12 Detailed Scenario Exercise are to:
Validate the Pointing request harmonization process, refined after the pre-launch exercise (Europa Flyby 7E1).
Exercise the planning process with several Science Working Groups (WG3 and WG4) and instrument teams involved: exercise procedures, consolidate filename conventions, file exchanges, and timely interactions.
Prove the ability of the Instrument Teams to generate an observation schedule for the Tour Phase.
Use PJ12 analysis as a representative case of near-equatorial perijove pass at ~10 to 15Rj; dayside and nightside geometry, no flyby interruption.
The Perijove PJ12 training activity is labeled as SGS-TR-1-Q4 and was agreed following a WG4 proposal during the
SWT executive meeting on 2022-12-5 and considers around four days centered around Perijove 12 (2032-09-24) excluding the
subsequent Callisto flyby (12C5). The scenario name is S007_PJ12, more details are provided in
Scenario Name.
The complete report of the PJ12 Detailed Scenario Implementation is available at [PJ12].
Geometry
The Perijove PJ12 scenario has been developed using the trajectory crema_5_1_150lb_23_1 [CREMA] as the new baseline
for the Level 0 segmentation. In particular, the MK_IDENTIFIER used was juice_crema_5_1_150lb_23_1_v433_20230517_001.
The time window covered by this scenario is from 2032-09-22T17:52:52 to 2032-09-26T23:58:51 (UTC). The geometrical summary of PJ12 is as follows:
Event Time: 2032-09-24T21:33:36Z
Distance to Jupiter [RJ]= 10.67
Sub-SC lon [deg]= 210.1
Sub-SC lat [deg]= -3.6
Sub-SC phase [deg]= 16.4
Sub-SC loctime [hours]= 13.1
Jupiter angular size [deg]= 10.7
Energy generated over +-50h around CA [Wh]= 98894.0
Energy for science over +-50h around CA [Wh]= 38894.0
Relative generated energy amount for science compared to PJ2= 0.992
Delta-time to closest moon Flyby= 62.42 hours before the flyby of 12C5
The duration of the scenario is of 4 days 15 hours and 14 minutes. The following figure shows the geometry of the scenario in the context of the trajectory segmentation.
Initial Segmentation and geometry from the SHT Timeline tool.
Geometry Events
The geometrical events calculated by the SOC that are present in the detailed scenario period are provided by two different files; a CSV event file and an EPS Event File (Event File (EVF)).
These events are typically ground station visibility, transits, perijoves, flybys, S/C Flip events, etc.
The location of the CSV geometry event file within the The JUICE Pre-operational Repository
is: PLANNING/SCENARIOS/<scenario_id>/ENVIRONMENT/EVENTS/GEOMETRY. Filenames are
as follows:
CSV event file:
MISSION_TIMELINE_EVENT_FILE_<scenario_id>.csvEVF event file:
EVT_GEOPIPELINE_<scenario_id>.evf
Please note that these events are already available in the Timeline Tool and they can be accessed from in the Timeline configuration option.
Trajectory Segmentation
The segmentation plan that has been considered for the start of the scenario is CREMA_5_1_150LB_23_1_SEGMENTATION_v2_B
as available from the SHT Timeline tool.
The considered time window includes the Downlink (DL_) block preceding the start of the JA_PE12 segment group
and the Optical Navigation block (OP_NAV) and Downlink (DL_) following the end of the JA_PE12 segment group
(2032-09-23T02:52:11 - 2032-09-26T14:36:27). JA_PE12 has a duration of 3.49 days. These adjacent segments are
included in order to include the design of the slews for the first and last observation blocks.
PJ12 Scenario Timeline
The PJ12 detailed Scenario process took place between October 2023 and March 2024, with an effective duration of 3 months but with interruptions due to the Payload Checkout Window 1 (PCW#1) activities.
The structure of the process was as follows:
Weekly telecons on Wednesdays at 15:30 CET/CEST
SOC deliveries of harmonised products with deadlines on Thursdays at 12:00 CET/CEST
PI deliveries of products with deadlines on Tuesdays at 12:00 CET/CEST
The detailed timeline of the scenario is provided hereunder:
Event |
Item |
Time (CEST/CET) |
|---|---|---|
S1 (SOC→PI) Starting Kit |
SOC Delivery |
2023-10-02 12:00:00 |
MILESTONE #0: OBS Database Frozen |
Milestone |
2023-10-17 12:00:00 |
M1 Kick-off (OPH #1) |
Meeting |
2023-10-18 15:30:00 |
S2 (SOC→PI) OPL S02P00 |
SOC Delivery |
2023-10-20 12:00:00 |
P1 (PI→SOC) Science Plan |
PI Delivery |
2023-10-24 12:00:00 |
P2 (PI→SOC) OPL S02PYY |
PI Delivery |
2023-10-24 12:00:00 |
M2 Science Plan (ObsPlan #2) |
Meeting |
2023-10-25 15:30:00 |
S3 (SOC→PI) OPL S03P00 |
SOC Delivery |
2023-10-27 12:00:00 |
P3 (PI→SOC) OPL S03PYY |
PI Delivery |
2023-11-07 12:00:00 |
P4 (PI→SOC) ODF New/Update |
PI Delivery |
2023-11-07 12:00:00 |
M3 Observation Plan (OPH #3) |
Meeting |
2023-11-08 15:30:00 |
S4 (SOC→PI) OPL S04P00 |
SOC Delivery |
2023-11-10 12:00:00 |
P6 (PI→SOC) ODF New/Update |
PI Delivery |
2023-11-14 12:00:00 |
P5 (PI→SOC) OPL S04PYY |
PI Delivery |
2023-11-14 12:00:00 |
M4 Observation Plan (OPH #4) |
Meeting |
2023-11-16 15:30:00 |
S5 (SOC→PI) OPL S05P00 |
SOC Delivery |
2023-11-17 12:00:00 |
MILESTONE #1: OTL Frozen Skeleton PTR |
Milestone |
2023-11-17 12:00:00 |
S6 (SOC→PI) PTR S01P00 |
SOC Delivery |
2023-11-17 12:00:00 |
P7 (PI→SOC) OTL S05P01 RIDERS |
PI Delivery |
2023-11-21 12:00:00 |
P8 (PI→SOC) PTR S01PYY |
PI Delivery |
2023-11-21 12:00:00 |
M5 Pointing (PTH #1) |
Meeting |
2023-11-22 14:30:00 |
S7 (SOC→PI) PTR S02P00 |
SOC Delivery |
2023-11-24 12:00:00 |
P9 (PI→SOC) PTR P02SYY |
PI Delivery |
2023-12-19 12:00:00 |
M6 Pointing #2 (PTH #2) |
Meeting |
2023-12-20 15:30:00 |
S8 (SOC→PTR) PTR S03P00 |
SOC Delivery |
2023-12-22 12:00:00 |
P10 (PI→SOC) PTR S03PYY |
PI Delivery |
2024-02-06 12:00:00 |
M7 Pointing #3 (PTH #3) |
Meeting |
2024-02-07 15:30:00 |
S10 (SOC→PI) ITL S01P00 |
SOC Delivery |
2024-02-09 12:00:00 |
MILESTONE #2: PTR Frozen Skeleton ITL |
Milestone |
2024-02-09 12:00:00 |
S9 (SOC→PI) PTR S04P00 |
SOC Delivery |
2024-02-09 12:00:00 |
P11 (PI→SOC) ITL S01PYY |
PI Delivery |
2024-02-13 12:00:00 |
M9 Instrument (ITL #1) |
Meeting |
2024-02-14 15:30:00 |
S11 (SOC→PI) ITL S02P00 |
SOC Delivery |
2024-02-16 12:00:00 |
P12 (PI→SOC) ITL S02PYY |
PI Delivery |
2024-02-20 12:00:00 |
M10 Instrument (ITH #2) |
Meeting |
2024-02-21 15:30:00 |
S12 (SOC→PI) ITL S03P00 |
SOC Delivery |
2024-02-23 12:00:00 |
P13 (PI→SOC) ITL S03PYY |
PI Delivery |
2024-02-27 12:00:00 |
M11 Instrument (ITH #3) |
Meeting |
2024-02-28 15:30:00 |
MILESTONE #3: ITL Frozen |
Milestone |
2024-03-01 12:00:00 |
S13 (SOC→PI) ITL S04P00 |
SOC Delivery |
2024-03-01 12:00:00 |
P14 (PI→SOC) Activity Feedback |
PI Delivery |
2024-03-05 12:00:00 |
M12 Wrap-up |
Meeting |
2024-03-06 15:30:00 |
S14 (SOC→PI) Activity Report |
SOC Delivery |
2024-03-08 12:00:00 |
PJ12 Detailed Scenario Timeline
7E1 Detailed Scenario
The Europa flyby 7E1 Detailed Scenario Exercise is the first detailed scenario exercise of the JUICE Strategic Science Planning after following the Callisto flyby 21C13 [21C13], [1C13]. The SOC also performed an initial internal Payload Operations Model scenario analysis [6E1].
The main goal 7E1 exercises was to get a realistic Data Volume (DV) generation for the flybys, as requested by the SWT as part of the Level 0 trajectory segmentation.
The implementation report of the scenario is available at [7E1].
All the relevant information of the scenario is available at the 7E1 JUICE Science Operations Confluence Page