Rosetta Science Operations Experimenter to RSOC interfaces

1. Rosetta Science OperationsExperimenter to RSOC interfaces Detlef KoschnySpace Science DepartmentESA/ESTECDetlef.Koschny@esa.int Interfaces during commissioning, cruise, fly bys – data flow Interfaces during commissioning, cruise, fly bys – ImplementationInterfaces during comet phase – data flowInterfaces during comet phase - Implementation Presented at the Rosetta Science Operations Working Group Meeting (SOWG) #5, 11 Jul 2001

2. Sequence Builder Data Analyst EPS (tbd) PI Teams Interfaces during commissioning,cruise, flybys - Data flow Flight ControlTeam (FCT) Science Operations Team Ground Segment Management Management FCPs Flight dyn. Request files Overall Planning Project Scientist Approval Flight DynamicsTeam (FD) Stations andFacilitiesManagement Command history Pointing modes Trajectory, attitude Telemetry Data Archiving / Handling Raw data Data Systems RMOC Plans Science communications, databases Raw data, auxiliary data, h/k Cal. data DDS Request Raw data Flight Control Procedures, execution times FlightControl Procedures Experiment Data Analysis Experimenter teams

3. Interfaces during commissioning, cruise, flybysImplementation - I uplink Project Scientistapproves RMOCexecutes FCPs ExperimentUser Manuals Experimentersupports FCPexecution

4. Interfaces during commissioning, cruise, flybysImplementation - II • Experimenters writes Flight Control Procedures, documented in User Manual • RMOC translates them to ESOC procedures • ESOC executes them under “control” of the Experimenter • Science Operations Team puts together consolidated plan in advance of mission phase, interactively changes plans • Project Scientist approves operations and changes • Data can be retrieved from the DDS • If a Payload Operation Request (POR) file is required, it will be transferred as in comet phase

5. Sequence Builder Data Analyst EPS (tbd) PI Teams Interfaces during comet phasesLogical Flight ControlTeam (FCT) Ground Segment Management SOC Management RSOC POR File Flight dyn. Request files Science ops planning Timeline Integration Science Sequence Assembly Flight DynamicsTeam (FD) Stations andFacilitiesManagement Command history SPLs, pointing, trajectory Trajectory, attitude Telemetry Data Archiving / Handling Raw data Data Systems RMOC Plans Science communications, databases Raw data, auxiliary data, h/k Cal. data DDS Request Raw data Operational Requests, Pointing Requests Lander Operations Plan Experiment Sequence Building Experiment Data Analysis Experimenter teams

6. Interfaces during comet phasesImplementation RSDB MCSwith archive Flight DynamicsSystem • Firewall Ops Lan Relay Lan DDS RSOC FTS Router Physical interfaces2001 Jul 08, dvk RSOC Science Planning System PI 1computer PI 2computer Lander Team computer

7. Interfaces during comet phasesImplementation - II • The RSOC FTS (File Transfer System) is located at ESOC within the Relay Lan. • It will be a cold-redundant SUN workstation, maintained 24 h per day • If a file is transferred, the DDS recognises from the file name whether it is for the RSOC FTS. It will forward it to that machine • On the RSOC FTS, incoming files are checked automatically (name, syntax check for OIOR/LOR files) and acknowledged • The Science Operations Team will transfer files via secure ftp to its planning system • Thus: • There is only one physical interface for the Experimenter, the DDS at ESOC • Security and reliability are ensured