SOC Planning exercise SOWG8 LTP planning of one

SOC Planning exercise SOWG#8 LTP planning of one 6 -months period based on mini-SAP

Index 1. Goals of the planning exercise 2. Recap: Solar Orbiter Planning Cycle and goals of Long Term Planning (LTP) 3. Presentation of LTP Planning Period – Jan-Jul 2022: • Orbit characteristics & location of RS windows • Specific Payload constraints (RS FOVs, METIS constraints) • Data return characteristics & boundary conditions 4. Science goals for Jan-Jul 2022 (=mini-SAP) 5. Presentation of FECS and associated E-FECS constraints • List of things we will not consider 6. Building the LTP plan • Introduction to available planning tools • SOOP planning with regular checks on resource usage ------- 7. Presentation of Results (Thursday)

1. GOALS OF THE PLANNING EXERCISE

Goals of the exercise • Plan one 6 -months long planning period, based on input SAP • Test out the SOOP planning concept during SOWG meeting • First use of prototype planning software (note: we are not quite there yet …) • First use of preliminary instrument models (note: high-level ‘observation level’ only – to be evaluated) • Exercise the LTP planning interfaces: • From SAP to SOOP-plan • From FECS to E-FECS • From Data return simulations to TM corridors • Examples of LTP planning output (input to IOR generation)

2. RECAP: Solar Orbiter Planning Cycle & Goals of Long Term Planning

Recap: Solar Orbiter Planning Cycle • Mission Level Plan (SAP, covers whole mission): • science goals depend on coordinated observations during opportunity windows along mission trajectory • variable downlink & limited space onboard • restrictions on RS observation time, TM and EMC noise • Long-Term Plan (T - 12 to 6 months): coordinate payload observations in science campaigns (SOOPs) • Medium-Term Plan (T - 1 m): constraint-check detailed Instrument Operations Timelines (IORs) • Short-Term Plan (T - 1 week): upload commanding for 1 week • Very Short Term Plan VSTP (daily during RSwindows ONLY) • high-resolution FOVs require fine-pointing to target = p-VSTP [opt] • changing solar activity imposes pointing updates = p-VSTP [optional] • short turn-around for data selection & calibration updates a requires low-latency (=quicklook) data = i-VSTP

LTP - Pre-Conditions During the Mission Level Planning, the following has been achieved: 1. Mission trajectory analysis: definition of science opportunities, data return simulations 2. Science Activity Plan (SAP) has been produced by SWT+PS, incl. location of RS windows and SC roll schedule SOC downlink analysis and pass optimisation proposal ➡ Served as input to ESTRACK ground station pass request 3. Pass schedule defined by ESTRACK (may differ from requested passes!) + platform activities defined by MOC + S/C roll manoeuvres fixed by MOC/SOC ➡ FECS = Flight Event Communication Skeleton (XML file) 4. SOC feasibility analysis of SAP TM needs (high-level) + FECS + downlink concept 5. Science plan + FECS sent to Instrument Teams for preparation of SOWG meeting

LTP - Pre-SOWG 1. Instrument Teams define & provide to SOC any new science or calibration modes (SOOP ingredients) that might be needed for planned Science Activities. 2. SOC models the new instrument modes as ‘instrument observations’ in SOC planning software Ø Variable parameters may apply & dependencies on or conflicts with other instrument observations need to be modelled Ø Observation modelling automatically makes the SOOP ingredients available to planning software ‘SOOP Kitchen’ 3. SOC prepares science constraints (e. g. platform disturbance windows, EMC mandatory-quiet and EMC preferred-noisy windows, …) based on FECS, and pointing events based on SAP

LTP planning by SOWG SAP is science driven, taking into account broad mission constraints. SOOP level plan needs operational specialists to refine the science activities into feasible operations timelines. Checklist of LTP-planning tasks: 1. Review platform event skeleton (FECS), incl. RS window location and S/C roll profile (fixed!) & assess associated science planning constraints 2. Translate SAP into a set of SOOPs with clearly defined science goals 3. Assign SOOP coordinators (if not yet available) 4. Translate each SOOP into a timeline of instruments’ science observations 5. Schedule calibration observations where necessary 6. Define precursor and Low-Latency observations 7. Define on-board trigger configuration 8. Constraint-check the SOOP timeline at high level (average power consumption & instrument TM profile at SOOP-level granularity) At end of meeting, we should have SOOP timeline that works + contact point for each SOOP.

LTP – Post-SOWG In parallel: • SOC checks SOOP plan for operational constraints at lowest possible level, off-line. Problems are flagged to SOOP coordinator who modifies SOOP to fit. • SOOP coordinator double-checks plan for scientific values, off-line. Tweaking happens in coordination with Project Scientist & SOC. Once all SOOPs fit: • SOC produces TM generation corridors per instrument, over the LTP period (6 months) • SOC sends to each IT: • TM corridor • Timeline of instrument observations with parameter values, based on SOOP timeline Ø Each instrument team will use these as input for IOR generation at MTP

3. CHOSEN PLANNING PERIOD: JAN-JUL 2022 Orbit characteristics Specific Payload constraints Data return characteristics

Jan-Jul 2022 Orbit HCI XY Projection Perihelion: 0. 295 AU Inclination: 13° RSW 1 (South): 26 Feb – 08 Mar RSW 2 (Perihelion): 26 Mar – 05 Apr RSW 3 (North): 05 Apr - 14 Apr RSW Extensions start 4 days prior to RSWs 1 & 2.

Jan-Jul 2022 Orbit HCI XY Projection Perihelion: 0. 295 AU Inclination: 13° RSW 1 (South): 26 Feb – 08 Mar RSW 2 (Perihelion): 26 Mar – 05 Apr RSW 3 (North): 05 Apr - 14 Apr RSW Extensions start 4 days prior to RSWs 1 & 2.

Jan-Jul 2022 Orbit HCI XY Projection Perihelion: 0. 295 AU Inclination: 13° RSW 1 (South): 26 Feb – 08 Mar RSW 2 (Perihelion): 26 Mar – 05 Apr RSW 3 (North): 05 Apr - 14 Apr RSW Extensions start 4 days prior to RSWs 1 & 2. Radial Alignment with Earth: Between RSW 1 & 2

Jan-Jul 2022 Orbit: Heliocentric Distance Aphelia ~ 0. 9 AU Perihelion 0. 295 AU

Jan-Jul 2022 Orbit: Heliographic Latitude Max latitude 13° Spacecraft Crosses Ecliptic Plane close to time of radial alignment with Earth.

Jan-Jul 2022 Orbit: GSE XY Projection Increasing separation from Earth with time. Quadrature with Earth towards the end of RSW 2

Jan-Jul 2022 Orbit: Relative Rotation Rate Below 8° per day relative rotation during RSW 2.

Jan-Jul 2022 Orbit: SC-Sun-Earth Angle Quadrature with Earth Radial Alignment with Earth

Jan-Jul 2022: METIS off-pointing limit Metis is limit-free beyond 0. 55 AU

Jan–Jul 2022: RS Field-of-Views Min Latitude window = RSW 1 start and end (Almost) no Metis limit

Jan–Jul 2022: RS Field-of-Views Perihelion window = RSW 2 start and perihelion (~ day 5) Metis constrained to disk centre pointing only

Jan–Jul 2022: RS Field-of-Views Max lat window = RSW 3 start and end Metis significantly constrained

Jan–Jul 2022: RS Field-of-Views

Data return characteristics Reminder October 2018 – Option E MBytes bps Better than Original Crema 3. 1 - Many regular peaks in rates - Short orbits: RS to IS data ratios high - Almost double the total potential downlink of original scenario - Lots of pass hours • LTP period for exercise covers Orbit 3 (+ a bit more) Period/Orbit 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 From 01/01/2021 05/07/2021 05/01/2022 23/06/2022 08/12/2022 26/05/2023 29/10/2023 27/03/2024 24/08/2024 13/01/2025 12/06/2025 09/11/2025 24/03/2026 06/08/2026 19/12/2026 03/05/2027 14/09/2027 19/01/2028 16/06/2028 12/11/2028 to 05/07/2021 05/01/2022 23/06/2022 08/12/2022 26/05/2023 29/10/2023 27/03/2024 24/08/2024 13/01/2025 12/06/2025 09/11/2025 24/03/2026 06/08/2026 19/12/2026 03/05/2027 14/09/2027 19/01/2028 16/06/2028 12/11/2028 11/04/2029 Available Specific Orbit Downlink Expectation GBytes Gbytes 276. 79 93. 47 153. 65 93. 01 200. 47 87. 55 311. 84 87. 55 323. 62 87. 55 127. 18 83. 19 138. 55 81. 06 70. 05 81. 06 110. 40 78. 63 75. 16 81. 06 243. 11 81. 06 181. 96 76. 03 69. 42 75. 87 85. 76 75. 87 102. 33 75. 87 95. 21 75. 87 69. 43 72. 83 115. 55 80. 82 154. 61 81. 06 202. 28 81. 06

Data return characteristics Reminder October 2018 – Option E With EID-A rates data fits in SSMM, with margin bps Fill state (%) …but not in pro-rata sized packet store. So packet stores sizes adjusted (12% more to RS and 8 less to IS) for exercise (Mbytes) Fill state (%) EPD 4639 EUI 6603 MAG 1910 METIS 3269 PHI 6622 RPW 7655 SOLO-HI 6622 SPICE 5616 STIX 192 SWA 21452

Constraints on Downlink Modelling • • Mission Level Planning (of whole mission) used optimistic ground station plan • Used extra passes • Allowed use of Cebreros and New Norcia when visibility at Malargüe short Example FECS (Flight Event and Communication Skeleton, provided by MOC) used in LTP exercise has no extra passes and no station swapping => Reality likely to be somewhere in between • Limitation in current SW => not possible to tweak of downlink according to generation peaks (same ratio applied through all period) => Packet store sizes adjusted instead

Jan–Jul 2022: Data return characteristics Close up on planning period Downlink rates (instant and daily averaged) bps Downlink less than RSW rates Spare downlink available up until second RSW Downlink less than IS only rates

Jan–Jul 2022: Data return characteristics First analysis on data generation • Extra data generation available up until the second RSW. • EID-A rates ok from second RSW • Conditions: • Boundary conditions on fill states at end of planning period are met • For this exercise we will measure the total SSMM fill state only (25971 Mbytes of science => SSMM 40% full) • Stores are empty by start of second RSW How much extra? Depends on generation profile, but as a guideline: • In-Situ could generate up to ~800% of their EID-A science in first 7 weeks, then 250% until near to RSW 2. • Remote sensing could produce 250% of their science rates in RSW 1 (and precursor) and EID-A rate from RSW 2 onwards.

Jan–Jul 2022: Data return characteristics What it could look like…. . In-Situ Fill States Remote-Sensing Fill States MB MB 70 days at end of LTP Up to 120 days in third RSW

4. SCIENCE GOALS Example SAP 01 January – 01 July 2022

Science Objectives to be Addressed RSW 1: 1. 1. 4. 1. 1 Interchange Reconnection Between Open and Closed Field Lines and its Role in Slow Solar Wind Generation Other objectives that can be addressed with the same observations: 1. 2. 2. 6, 1. 1. 2. 2, 1. 1. 3. 1, 1. 1. 3. 3, 1. 2. 1. 7 RSW 2 & RSW 3: 1. 1. 2. 10 Trace Streamer blobs and other structures through the outer corona and heliosphere. Other objectives that can be addressed with the same observations: 1. 1. 2. 6, 1. 1. 3. 2(. 1) Inside and Outside RSWs: The following in situ objectives can be addressed, either in whole or in part, throughout: 1. 2. 2. 1 -1. 2. 2. 4, 1. 1. 2. 5, 1. 1. 2. 8, 1. 1. 2. 9, 1. 1. 2. 11, 1. 1. 4. 1. 6, 1. 1. 4. 1. 3, 1. 3. 1 (in situ part), 1. 3. 11. 3. 4

Before RSW 1 (in-situ SOOP 1) • High potential downlink. • In situ can generate at 800% of EIDA Rate (!) • Decrease to 250% EID-A during the RSW extension (i. e. RSW – 4 days). Note: All % of EID-A numbers quoted are with HK & LL subtracted. • Note: This will result in an unequal distribution of extra (i. e. above EIDA) downlink between in situ and remote sensing because during much of the high data rate period only in situ are baselined to operate – everyone still gets more than EIDA this period. • If we had a complete SAP this could be addressed by moving RSWs, for example, or moving pass hours from higher rate periods to optimize the science -for-downlink value. • This flexibility is not there by the time we get to LTP. • Highlights the need for a complete SAP to make the most of good downlink periods! Downlink rate can also be distributed unevenly if specified in SAP. • Recall that we are not considering out of window operations for remote sensing instruments – not baseline.

RSW 1: 1. 1. 4. 1. 1 Interchange Reconnection Between Open and Closed Field Lines and its Role in Slow Solar Wind Generation - SOOP 2 Interchange reconnection between open and closed field lines and its role in slow wind generation (coronal hole boundaries and intermediate areas of quiet Sun). To be studied for coronal holes in different locations and at different parts of the orbit (high latitude, perihelion). Window: South Window (~0. 6 -0. 5 AU, -15°) Target: Open-closed field line boundary (near ballistic connection point) VSTP: YES Support from Earth Assets: YES RSW Extension (ex Precursor) Observations: YES Summary: Try to catch with Remote Sensing instruments the dynamics at a boundary which will then be crossed in situ.

Observing Strategy SOOP 2 1. Before the window: Analyse Earth-based full disc data and models. 2. RSW Extension: Update models with EUI/PHI LL data & identify candidate boundaries, plus solar wind boundary crossing interception time with Spacecraft & therefore range of plasma release times. 3. Earliest VSTP: Point at candidate boundary. 4. Subsequent VSTPs: Update models, refine pointing & predicted release times. Range of possible Plasma release times Interception Time UT High cadence RS observations here Updated plasma release times can be used for data priority changes (EUI/PHI).

EPD, MAG, RPW, SWA - SOOP 2 • 250% EID-A rates throughout the RSW (and after). • EPD close mode throughout? • Higher Cadence 3 D VDFS from SWA? • Extra scheduled bursts (If more EMC quiet windows feasible). • Selective OK for RPW.

SPICE contribution to SOOP 2 • 250% EID-A Rate (science only) = 42. 5 kbps • SPICE runs throughout RS window. • Observing mode: Composition mapping with possibility to measure Doppler velocities. • Slit: 6” or 30” (for faster maps with the max FOV) • Exposure time/cadence and number of X positions: 180 s, X=160 or X=32 • Field of View: 16’× 11’ (with the 6” slit), 16’× 14’ (with the 30” slit) • Comments: The choice of lines, and also the number of intensities and profiles, is flexible, although the sum of the intensities and profiles is constrained to a maximum (e. g 15 for composition mapping). While varying the number of intensities and profiles, within the maximum, has no effect on the duration of the study, it will have an effect on the telemetry.

EUI contribution to SOOP 2 1. 250% EIDA Rate = 50 kbps (i. e. 5400 MB over RSW, in separate flushes) 2. Full disc context images during RSW extension. 3. Full Calibration in extended RSW 4. HRI “Coronal hole mode” 1 min cadence throughout RSW 5. Varying priority scheme to keep HRI data production manageable… 6. FSI synoptics throughout. Interception Time UT Priority Range of possible plasma release times (~20 hrs? ) All images taken during release window downlinked, ~10% outside. Window time updated via i. VSTP based on models & LL.

PHI contribution to SOOP 2 • 250% EID-A Rate = 50 kbps (i. e. 5400 MB over RSW, flush after processing) • HRT Active • LL magnetograms needed, also during RSW extension. • Calibration OK (maybe including raw data download) • Regularly spaced HRT data at medium to high resolution. • If possible focus downlink on Plasma release window after the fact (this will be more accurate since we have actual IS data from interception time). • NB: Time needed to process data? ; Best downlink rate at the beginning of the window. Range of possible Plasma release times Interception Time UT

Metis, Solo. HI, STIX (individual SOOPs) • 250% EIDA throughout Window: • Metis: 25 kbps • Solo. HI: 50 kbps • STIX: 1. 5 kbps • Calibrations OK beforehand. • No pointing restrictions for Metis (above 0. 5 AU). • Metis/Solo. HI: Context during the RSW extension. • STIX: On throughout, can select extra events. • No direct contribution to main SOOP identified (correct us if we’re wrong!). • Good opportunity to address extra science goals (But we still need to define your modes for this window).

End RSW 1 – RSW 2 (in-situ SOOP 3) 1. 250% EIDA for in situ. 2. Remote sensing instruments keep on downlinking data from RSW 1. 3. PHI does any extra necessary processing, but note that downlink performance decreases with time, so it pays to do this sooner rather than later. 4. All stores need to be empty in time for the start of RSW 2. This should be possible with 250% EID-A.

RSW 2 & 3: 1. 1. 2. 10 Trace Streamer Blobs and Other Structures Through the Outer Corona and Heliosphere (SOOP 4 & 5) Trace streamer blobs and other structures through the outer corona and the heliosphere. Study periodic density structures in the low corona and for different times in the solar cycle. Window: Perihelion & North Windows Concatenated (0. 3 -0. 45 AU, 0 - 15°) Target: Open-closed field line boundary (near ballistic connection point) VSTP: YES (RSW 2 Only) Support from Earth Assets: YES RSW Extension (ex Precursor) Observations: YES Note: Quadrature with Earth towards end of RSW 2 Summary: Observe blobs in situ with Earth/L 1 and Solar Orbiter remotely, observe Blobs in situ with Solar Orbiter, and with Earth remotely, image the connection point. Also addresses other ‘connection’ goals depending on what happens when we’re connected.

Observing Strategy, RSW 2 Days 1 – 8: Connecting Blobs (SOOP 4) E S • Near-quadrature means Solo. HI can image Earthdirected blobs • Equally Earth can image blobs that will hit Solar Orbiter • Offpoint to near ballistic Connection point • Daily SPICE N-S mosaics • Chance of imaging source region of Solar Orbiter directed blobs. • Pointing updated via VSTP • This will mean Metis is off for the first 8 days of the concatenated windows. Metis leads the last 12 days. • Data production could be biased to favour EUI/SPICE here and Metis subsequently (TBC).

Observing Strategy, RSW 2 Days 9 – 20: Zooming Out (SOOP 5) E S • Metis/Solo. HI leads. • Disc centre pointing. • ‘Zooming out’ effect as we move away from perihelion. • Will allow Metis & Solo. HI to image blobs at a range of solar distances. • Metis and Solo. HI lead with coordinated observations • Synoptic/Support from other RS. • Earth can still image Solar Orbiter directed blobs. • Opportunity to address other goals with any leftover downlink

EPD, MAG, RPW, SWA in SOOPs 4 & 5 All IS instruments follow a nominal program throughout the 2 concatenated RSWs (Standard In Situ SOOP). • 100% EID-A rates throughout the RSWs (and after). • Normal modes with regular burst modes for all instruments. • EPD in close mode at least up to end of the RSWs • Selective OK for RPW

RS SOOP 4 a: connection hunting - mosaic RS SOOP 4 b: ballistic connection pointing • SOOP 4 (a+b part) uses 100% EID-A rate during first 8 days of RSW 2 • Calibrations OK beforehand, but TM incl. in the EID-A rate for the RSW. • Pre-window observations with EUI, METIS (coronal context) • SOOP 4 a: POINTING MOSAIC (3 hours each day) • Daily N-S mosaic driven by SPICE composition maps (6” slit) Proposal: 6 positions, 30 mins dwell time – duration: 3 hrs + slews • PHI/HRT mode 2 (TBC) at 15 min cadence (2 sets/SPICE map) • EUI/HRI at 10 -15 min cadence (e. g. in EUI_SCI_CH mode) • EUI/FSI synoptics • Solo. HI: Nominal synoptic perihelion program, but turned down to EIDA rate (e. g. near-perihelion program) • STIX: On throughout. • METIS in SAFE, door closed

RS SOOP 4 a: connection hunting - mosaic RS SOOP 4 b: ballistic connection pointing • SOOP 4 (a+b part) uses 100% EID-A rate during first 8 days of RSW 2 • Calibrations OK beforehand, but TM incl. in the EID-A rate for the RSW. • Pre-window observations with EUI, METIS (coronal context) • SOOP 4 b: OFF-POINTING TO MODELLED BALLISTIC CONNECTION • SPICE composition and dynamics interleaved • PHI/HRT synoptic program at EID-A rate, ideally regular flushes. • EUI/HRI & FSI synoptic program at EID-A rate, regular flushes. • Solo. HI: Nominal synoptic perihelion program, but turned down to EIDA rate (e. g. near-perihelion program) • STIX: On throughout. • METIS in SAFE, door closed

RS SOOP 5: Coronal blob observations (RSW 2 Days 9 – 20) • 100% EID-A Rate during 12 last days of RSW 2+3 (Earth - SO in quadrature) • Disk-centre pointing • Calibration of PHI/FDT at start of this SOOP (incl. in the EID-A rate) • Calibration of METIS at start of this SOOP if necessary • SOOP 5 observations: • • SPICE synoptic program (to be defined) • PHI/FDT synoptic program at EID-A rate, regular flushes. • EUI/FSI synoptic program at EID-A rate, regular flushes if possible. • Solo. HI & Metis run a coordinated program for blob observations: Metis FLUCTS program interleaved with generic program (WIND? ) Solo. HI runs mixture of high-cadence TURB and lower-cadence mode STIX: On throughout at EID-A rate. (individual SOOP)

End RSW 3 – End Planning period (IS SOOP 6) 1. 100% EIDA Rates for in situ. 2. EPD close mode OK to 0. 7 AU. 3. Selective OK for RPW.

Calibration plan: proposal based on User Manuals • MAG calibration roll in between RSW 1 and 2 (see FECS roll event) • EUI calibration sequences before (and after? ) RSW 1 and RSW 2+3 • • Full calibration – 382 MB – around RSW 1, partial calibration later • Annealing 2 weeks, preceded and followed by calibration: <RSW 1 PHI/HRT & FDT calibration before RSWs where they are used: • HRT calib before RSW 1 (25 MB+raw) & before RSW 2+3 (25 MB) • FDT calib (110 MB) only before RSW 2+3 (FDT ON last 12 days) -> requires off-pointing schema for flatfield! • Two 20 -day annealing campaigns, before RSW 1 and after RSW 3 • Metis Dark calibration (20 MB) before RSW 1 and before RSW 2+3. • Solo. HI: • Photometric calibration (200 MB) before RSW 1 and RSW 2+3 • 24 -hours-annealing campaign before RSW 1 • SPICE radiometric calibration (26 MB, 1 hr) at start, mid & end of each RSW • STIX switch ON at start pre-RSWs (-4 days) for background calibration

5. FECS AND E-FECS Platform events (FECS) & Associated Science planning constraints (E-FECS)

Presentation of FECS See SOUS-CHEF with timeline of FECS constraints. Pay particular attention to RS windows, passes & antenna pointings, WOLs 1/3 days, scheduled rolls (MAG only)

E-FECS Science planning constraints: 1 -day during RSW 1

E-FECS Science planning constraints: 1 -day during RSW 2

E-FECS Science planning constraints: 1 -day during RSW 3 (days 9 -20)

E-FECS Science planning constraints: 1 -day outside RS windows

6. BUILDING THE LTP PLAN Ready to start? GO!

Building the LTP plan See SOOP Kitchen & SOUS-CHEF prototypes and MAPPS planning software Checklist: Review platform event skeleton (FECS), incl. RS window location and S/C roll profile (fixed!) & assess associated science planning constraints 1. Translate SAP into a set of SOOPs with clearly defined science goals 2. Assign SOOP coordinators (if not yet available) 3. Translate each SOOP into a timeline of instruments’ science observations and link those together in the planning tool * 4. Schedule calibration observations where necessary 5. Define precursor and Low-Latency observations 6. Define on-board trigger configuration 7. Constraint-check the SOOP timeline at high level (average power consumption & instrument TM profile at SOOP-level granularity) note that step 4 with * requires functionality which is not yet available

Tools presentation: MAPPS/EPS is an extensive Science Planning Software package that takes as input: • Low-level Instrument Models (modules with resource usage, modes that combine particular module states, MIB actions, constraints, …) • High-level Instrument Observations: science activities that consume power (profile), generate data (profile) and can take parameters and constraints on other observations or events • Spacecraft models (SSMM, antenna, platform) • Timelines with instrument and spacecraft activities (e. g. IORs) • Timelines of events (e. g. FECS) And gives as output: • Timelines of resource usage (power, data-rate, packet store fill states) • List of warnings and errors based on payload and platform constraints • PORs = Payload Operation Requests to be sent to MOC • (PTRs = Pointing Requests) – not for Solar Orbiter

Tools presentation: MAPPS

Tools presentation: SOOP Kitchen is a LTP planning tool that is built on top of the MAPPS/EPS planning software. Currently only a PROTOTYPE is available. It is designed to plan instrument observations over a 6 -months period, i. e. : • Schedule pre-defined instrument observations, adjust parameters and assess the impact on resource usage • Plan coordinated science plans SOOPs among many different instruments • Schedule science planning events based on FECS events & additional planning information * • Highlight observational constraints * • Write out instrument timelines • Produce E-FECS * • Assess high-level resource usage over whole planning period * Ø Make the LTP planning process in a meeting feasible Note that functionalities with * are not yet available

Tools presentation: SOOP Kitchen

Tools presentation: SOUS-CHEF visualizes the plan being build in SOOP Kitchen & (E)-FECS events Will likely be merged into SOOP kitchen at some point

Aspects we are not (yet) considering During this exercise we do NOT consider the following aspects: • Switch-ON activities and Door activations (heatshield door operations likely to end up in E-FECS) • Constraint checks: observation-observation and observation-event • Communication rolls (were not needed in this planning period) • Data flows to ‘Turn-Around Calibration packet-store’ (TAC) • Detailed EMC planning and accounting (awaiting list of noisy instrument activities) Some of the functionality that is still missing: • Consolidation SOOP Kitchen and SOUS-CHEF • Observations grouping into SOOPs • Flexible adjustment of SOOPs and observation plan (dragging & dropping? ) • Non-standard data downlink shares • Currently LL and HK data are being modelled very crudely in background