All rights reserved © Altec ExoMars 2018 Rover Operations Control Centre ROCC to Pasteur Payload ICDs E. Ferrentino

All rights reserved © Altec Ref. Nr.  ICD Purposes  ICD Definition Process  ICD Evolution and Maintenance  Science Products Generation  Integration of Science Processors  Conventions and standards  The ROCC’s SOC Overview Date Page 2

All rights reserved © Altec Ref. Nr. Purpose of the ROCC to PPL-(i) ICD is to control:  the processing of the PPL-(i) science data on Ground, at ROCC level, and the generation of the corresponding data products  the accommodation of instrument-specific data processing software in the ROCC  the storage and sharing rules within the ROCC of the science data products required for mission operations  the transfer of the science data products to ESAC for long term archiving in the ESA PSA  the accommodation of the PPL-(i) instrument team at ROCC during simulation campaigns and during all the mission operations ICD Purposes Date Page 3

All rights reserved © Altec Ref. Nr.  ALTEC issued a ROCC to PPL-(i) ICD template (now in draft 2, dated 10.Oct.2014)  The ICD template contains:  Description of the high-level interfaces between the ROCC and the PPLs teams  Engineering and operational constraints  It provides the frame within which the PPLs teams are expected to provide their needs for proper accommodation and data handling during training, simulations and operations  Some guidelines (properly highlighted) have been placed throughout the document where information from the PPL teams is needed  After the information from the PPL team has been provided, the template is «instantiated» as an actual ICD dedicated to the specific instrument  For each PPL team, ALTEC review the ICD, start a clarification / consolidation loop with the PPL team and, on the due date, deliver the first formal issue of the document ICD Definition Process (1 / 2) Date Page 4

All rights reserved © Altec Ref. Nr. ICD Definition Process (2 / 2) Date Page 5

All rights reserved © Altec Ref. Nr.  After the formal issue has been finalized by ALTEC and delivered to the PPL team, it becomes the preferred communication channel between the ROCC and the PPL team along the mission  Each ICD will evolve independently, in accordance to the specific needs of the PPL team, following its own life-cycle  The general guidelines of the template can be replaced by team- specific ones in order to address specific topics and to help in reaching an agreement  PPLs teams should follow the guidelines where possible, and propose alternative solutions in case their needs are not met  ALTEC personnel will assess the feasibility in the context of the whole framework and, if feasible, will implement the proposed solution ICD Evolution and Maintenance (1 / 3) Date Page 6

All rights reserved © Altec Ref. Nr.  When the Programme is subject to a major change which may affect the interface between the ROCC and the PPLs teams, ALTEC will update the ICDs  For all the changes occurring before the ‘first issue deadline’ (currently March 2015), ALTEC will update  the ICDs for the PPLs teams who provided a first feedback  the ICD template for all the others  Template History: ICD Evolution and Maintenance (2 / 3) Date Page 7 Template VersionDateMain change DR19 May DR229 Sep 2014PDS4 is considered next to PDS v3 DR3Jan 2015 (planned)PDS4 is the baseline

All rights reserved © Altec Ref. Nr.  ROCC-to-Ma_Miss ICD: ICD Evolution and Maintenance (3 / 3) Date Page 8 IssueDateMain changeAuthor of change DR118 Sep 2014First feedbackMa_Miss team DR210 Oct 2014PDS4 is considered next to PDS v3 + Ma_Miss guidelinesALTEC DR3Jan 2015 (planned)PDS4 as baselineALTEC  ROCC-to-ISEM ICD: IssueDateMain changeAuthor of change DR227 Nov 2014First feedbackISEM team DR3Jan 2015 (planned)PDS4 as baseline + ISEM guidelinesALTEC  ROCC-to-ADRON-RM ICD: IssueDateMain changeAuthor of change DR21 Dec 2014First feedbackADRON-RM team DR3Jan 2015 (planned)PDS4 as baseline + ADRON-RM guidelinesALTEC

All rights reserved © Altec Ref. Nr.  Science TM and derived science products are processed, stored and controlled by the ROCC Operations Control System (ROCS)  The ROCS is equipped with processors capable of performing basic pre-processing steps and generating low-level products (up to L2 of CODMAC – Experimental Data Record generation)  Due to the specific knowledge needed for science data processing, the PPLs teams are requested to provide the processors for further medium- / high-level processing  The PPLs Processors will be integrated in the ROCS and executed, when needed, either automatically or manually by an operator belonging to the specific PPL team  In the frame of the ICD template, PPLs teams are expected to provide information about other instruments’ and / or Rover subsystems’ data they need in order to perform their computations Science Products Generation Date Page 9

All rights reserved © Altec Ref. Nr.  Scientists are encouraged to integrate their processors in the ROCS in order to:  Be sure the processors are executed at the right time, as soon as the inputs are available, minimising delays  Treat data in a homogenous way, facilitating data archiving, linking, consultation and retrieval  Speed up and ease the operator interaction, by the usage of a common HMI  Integration helps in fulfilling the tight time constraints of the tactical planning, maximising the scientific return of the mission  Scientists can use external processors not integrated in the ROCS:  When integration is not feasible  When operating from remote sites  Both internal and external SW shall be able to populate the ROCC’s Data Archive and Retrieve (DAR), in order to ensure the maximum level of sharing and improve the overall quality of the scientific investigation Integration of Science Processors Date Page 10

All rights reserved © Altec Ref. Nr.  All the data formats, naming conventions and operational procedures and rules for science data archiving comply to the PDS4 standard, as stated in the Data Archive Plan (DAP)  Some PDS4 related activities may be required for the ExoMars 2018 mission, in particular:  Definition of a Local Data Dictionary (LDD)  Definition of a global namespace  Definition of more detailed namespaces (e.g. per instrument, data type, mission objective)  Definition of Bundle and Collection IDs  Definition of the procedure for Logical Identifiers (LIDs) generation  These activities will be performed by ALTEC by following the indications provided by ESAC  PPLs teams will be consequently informed by updating the ICD and / or the ICD template Convention and standards Date Page 11

All rights reserved © Altec Ref. Nr.  Accommodation in the SOC:  The PPLs teams will be hosted in the Science Operations Control (SOC) area of the ROCC. It is a 120 sm room (3 m high) in the ALTEC Centre, separated in cubicles  Each instrument team will have dedicated positions for 2 persons during normal shift (4 persons are foreseen during the 1 hour handover period in case of multiple shifts)  SOWG meeting room for Science Activity Plan consolidation  Science Themes Labs  Science-dedicated general-purpose meeting room PPLs Teams accommodation in the ROCC Date Page 12

All rights reserved © Altec Ref. Nr.  Each working position in the SOC is equipped with:  N. 1 Operation Console (workstation with double 24” monitors) able to run all the ROCS standard applications  N. 1 Ops Support Console (windows PC with double 24” monitors, with MS applications), in order to access operations support tools, Internet, etc.  N. 1 Telephone / VoIP  The room is also equipped with:  N. 4 Wall Time Display (with associated time display server with dedicated configurable applications)  N. 2 Colour Printer (A3/A4) (including fax, copier, scanner)  Wi-Fi connectivity  N. 9 Whiteboards  N. 18 Cabinets SOC Working Positions Date Page 13

All rights reserved © Altec Ref. Nr.  Some guidelines in the ICD are intended to help the PPLs teams in thinking about the equipment they may need during training, simulations and operations  Specific accommodation and equipment can be agreed between ALTEC and the PPLs teams in order to address specific needs, for instance:  Room for personal equipment (e.g. Laptops, dedicated hardware, testbenches)  Additional workstations  Additional screens  Additional support material (projectors, tables, whiteboards, cabinets, etc.) Common and team-specific accommodations Date Page 14