SOWG # 6, 20/01/2015 ESAC Agenda  Finalization of the service 20 specifications  Test plans for the service20 at spacecraft level  Instruments clocks  Coordination of burst modes  Planning for the Cruise Phase (25% of the telemetry)  Status for each instrument : science operations, flight software status, service 20

Minutes Finalization of the service 20 specifications Since July there are pending inputs from some instruments on platform parameters needed by them Stefan Thuerey is centralizing now all the inputs from the platform and will produce a TN (included in the single doc) Luis Sanchez is in charge of the specification document Filippo Marliani is still the central contact for instrument teams with respects to the service 20 matters  Action for all (in-situ) teams : send to Luis Sanchez before 5 February confirmation of their own telemetry which will be put in the TM 325 telemetry inter-instrument communication packet. Add if there is any discrepancy with the instrument TM/TC ICD  Action for the project (F. Marliani) to send to the ISWG the information on the platform parameters which will go into the service 20. Due date 5 February.  Action for Luis Sanchez : finalize the “service 20 specification document” by 10 February and report to SWT

Test plans for the service 20 at spacecraft level - Filippo Marliani is still the central contact for instrument teams with respects to the service 20 ground testing. Christof Hass is the AIT/AIV responsible -A document describing the service 20 testing need to be written by AIRBUS for the the S/C CDR and need to be accessible to instruments.  Action on the ESA project (Filippo) to make this document available to the instrument teams. Due date : whenever document ready  Action on Andrew Walsh : To formalize in a TN the ideas for testing the triggers during cruise phase. Due date : 28 feb Instruments clocks (RID by A. Walsh on SWA) The RPW synchronization scheme for the regular snapshot is fine. Can SWA adopt the same scheme ?  Action on RPW send the description of the synchronization scheme before february 5. Then SWA to answer if they can follow that same scheme before 28 feb Coordination of burst modes scheduled burst mode : priority 1 Send to Tim precise description of the burst data with copy to Andrew tuesday afeternoon before SWT mini splinter Start planning for the Cruise Phase (25% of the telemetry) Status for each instrument : science operations, flight software status, service 20 Planning of the Cruise Phase - work normally for 25 % of the time or reduce cadency to 25 % ? - share amonf the ISWG the scruise phase description in user manual - Cruise phase section in the ISWG document. * phase during which instruments are free to do what they want * run normally only 25 % of the time selective downlink can only work some of the time when the SSMM is not full possibility to do selective for all in-situ, not only RPW status report : RPW : ok SWA : software CDR in the summer, meeting with SPC people EPD : nominal STIX : CDR earlier, focussing with hardware, will probably operate during

Coordination of burst modes Two kind of burst modes have been foreseen from the very beginning:  scheduled/coordinated bursts mode (equally spaced in heliocentric distance)  instruments own burst modes (either triggered via service 20 or no) For SWA it has been decided to set a priority 1 to the scheduled/coordinated bursts mode. The duration of the common burst need still to be discussed  Action for all in-situ teams: Send to Tim Horbury the precise description of the coordinated burst data (with copy to Andrew Walsh) before 10 February. This topic could then be discussed during a mini ISWG splinter on Tuesday 10 February before the SWT

Planning of the Cruise Phase  The cruise phase operations need to be discussed & coordinated within the ISWG. Assumption : ~ 25 % of the telemetry return during the cruise phase.  Two options:  work normally for 25 % of the time ?  or reduce telemetry to 25 % of the allocation ?  This topic shall be discussed again within the ISWG having in mind that the cruise phase will be used by the IS instruments with two goals  Preparing the nominal phase of the mission (checking the triggers & replies to the triggers, checking the timing of the SWA/RPW snapshots, improvement of the calibration … )  Perform innovative science Selective downlink Informations from Chris Watson :  Currently the selective downlink is not planned to work during cruise phase (not enough passes). Comment from RPW : This is an issue since the cruise phase will not be used to test this capability.  The selective downlink can only work some of the time when the SSMM is not full  There will be the possibility to do selective downlink for all in-situ, not only RPW