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

2. 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)

3. 1. GOALS OF THE PLANNING EXERCISE

4. 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)

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

6. 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 6months): coordinate payload observations in science campaigns (SOOPs) Medium-Term Plan (T - 1m): constraint-check detailed Instrument Operations Timelines (IORs) Short-Term Plan (T - 1week): 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

7. 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

8. 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

9. 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.

10. 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

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

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

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

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

15. Jan-Jul 2022 Orbit: Heliocentric Distance Aphelia ~ 0.9 AU Perihelion 0.295 AU

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

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

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

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

20. Jan-Jul 2022: METIS off-pointing limit Metis is limit-free beyond 0.55AU

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

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

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

24. Jan–Jul 2022: RS Field-of-Views

25. Reminder October 2018 – Option E 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 Available Downlink Specific Orbit Expectation OrbitFromtoGBytesGbytes 101/01/202105/07/2021276.7993.47 205/07/202105/01/2022153.6593.01 305/01/202223/06/2022200.4787.55 423/06/202208/12/2022311.8487.55 508/12/202226/05/2023323.6287.55 626/05/202329/10/2023127.1883.19 729/10/202327/03/2024138.5581.06 827/03/202424/08/202470.0581.06 924/08/202413/01/2025110.4078.63 1013/01/202512/06/202575.1681.06 1112/06/202509/11/2025243.1181.06 1209/11/202524/03/2026181.9676.03 1324/03/202606/08/202669.4275.87 1406/08/202619/12/202685.7675.87 1519/12/202603/05/2027102.3375.87 1603/05/202714/09/202795.2175.87 1714/09/202719/01/202869.4372.83 1819/01/202816/06/2028115.5580.82 1916/06/202812/11/2028154.6181.06 2012/11/202811/04/2029202.2881.06 bps MBytes Data return characteristics

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

27. 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

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

29. 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 RSW2 onwards. Jan–Jul 2022: Data return characteristics

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

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

32. Science Objectives to be Addressed RSW1: 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 RSW2 & RSW3: 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.1- 1.3.4

33. Before RSW1 (in-situ SOOP 1) H igh 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.

34. 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.

35. 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. Interception Time Range of possible Plasma release times UT High cadence RS observations here Updated plasma release times can be used for data priority changes (EUI/PHI).

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

37. SPICE contribution to SOOP 2 250% EID-A Rate (science only) = 42.5kbps 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.

38. EUI contribution to SOOP 2 1.250% EIDA Rate = 50 kbps (i.e. 5400MB 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 Range of possible plasma release times (~20hrs?) UT Priority All images taken during release window downlinked, ~10% outside. Window time updated via iVSTP based on models & LL.

39. PHI contribution to SOOP 2 250% EID-A Rate = 50 kbps (i.e. 5400MB 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. Interception Time Range of possible Plasma release times UT

40. Metis, SoloHI, STIX (individual SOOPs) 250% EIDA throughout Window: Metis: 25kbps SoloHI: 50kbps STIX: 1.5kbps Calibrations OK beforehand. No pointing restrictions for Metis (above 0.5 AU). Metis/SoloHI: 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).

41. End RSW1 – RSW2 (in-situ SOOP 3) 1.250% EIDA for in situ. 2.Remote sensing instruments keep on downlinking data from RSW1. 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 RSW2. This should be possible with 250% EID-A.

42. RSW2 & 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 (RSW2 Only) Support from Earth Assets: YES RSW Extension (ex Precursor) Observations: YES Note: Quadrature with Earth towards end of RSW2 Summary: Observe blobs in situ with Earth/L1 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.

43. Observing Strategy, RSW2 Days 1 – 8: Connecting Blobs (SOOP 4) E E S S Near-quadrature means SoloHI can image Earth- directed 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).

44. Observing Strategy, RSW2 Days 9 –20: Zooming Out (SOOP 5) E E S S Metis and SoloHI 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 Metis/SoloHI leads. Disc centre pointing. ‘Zooming out’ effect as we move away from perihelion. Will allow Metis & SoloHI to image blobs at a range of solar distances.

45. 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

46. RS SOOP 4a: connection hunting - mosaic RS SOOP 4b: ballistic connection pointing SOOP4 (a+b part) uses 100% EID-A rate during first 8 days of RSW2 Calibrations OK beforehand, but TM incl. in the EID-A rate for the RSW. Pre-window observations with EUI, METIS (coronal context) SOOP 4a: 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 15min cadence (2 sets/SPICE map) EUI/HRI at 10-15min cadence (e.g. in EUI_SCI_CH mode) EUI/FSI synoptics SoloHI: Nominal synoptic perihelion program, but turned down to EIDA rate (e.g. near-perihelion program) STIX: On throughout. METIS in SAFE, door closed

47. SOOP4 (a+b part) uses 100% EID-A rate during first 8 days of RSW2 Calibrations OK beforehand, but TM incl. in the EID-A rate for the RSW. Pre-window observations with EUI, METIS (coronal context) SOOP 4b: 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. SoloHI: 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 4a: connection hunting - mosaic RS SOOP 4b: ballistic connection pointing

48. RS SOOP 5: Coronal blob observations (RSW2 Days 9 –20) 100% EID-A Rate during 12 last days of RSW2+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. SoloHI & Metis run a coordinated program for blob observations: Metis FLUCTS program interleaved with generic program (WIND?) SoloHI runs mixture of high-cadence TURB and lower-cadence mode STIX: On throughout at EID-A rate. (individual SOOP)

49. End RSW3 – End Planning period (IS SOOP6) 1.100% EIDA Rates for in situ. 2.EPD close mode OK to 0.7AU. 3.Selective OK for RPW.

50. 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 RSW2+3 Full calibration – 382MB – around RSW1, partial calibration later Annealing 2 weeks, preceded and followed by calibration: <RSW1 PHI/HRT & FDT calibration before RSWs where they are used: HRT calib before RSW1 (25MB+raw) & before RSW2+3 (25MB) FDT calib (110MB) only before RSW2+3 (FDT ON last 12 days) -> requires off-pointing schema for flatfield! Two 20-day annealing campaigns, before RSW1 and after RSW3 Metis Dark calibration (20MB) before RSW1 and before RSW2+3. SoloHI: Photometric calibration (200MB) before RSW1 and RSW2+3 24-hours-annealing campaign before RSW1 SPICE radiometric calibration (26MB, 1hr) at start, mid & end of each RSW STIX switch ON at start pre-RSWs (-4 days) for background calibration

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

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

53. E-FECS Science planning constraints: 1-day during RSW1

54. E-FECS Science planning constraints: 1-day during RSW2

55. E-FECS Science planning constraints: 1-day during RSW3 (days 9-20)

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

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

58. 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

59. Tools presentation: MAPPS 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

60. Tools presentation: MAPPS

61. Tools presentation: SOOP Kitchen 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

62. Tools presentation: SOOP Kitchen

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

64. 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