GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD
Issue 1 Revision 2 (draft) - 25.07.2010
GMES-GSEG-EOPG-TN-09-0008
page 225 of 350
o Automatically notification on the required downlink passes (pass-list) according to the
generated Mission-Plan, for their booking at the ground stations (CGS/LGS);
o Generating automatically the CGS/LGS X-Band & Ka-Band Acquisition-Schedule-Plan
according to scheduled activities;
o Generating automatically the EDRS-Booking-Plan according to scheduled activities
and static EDRS Availability Segments assigned to Sentinel-2;
o Automating explained above planning generation activities to avoid operator
intervention when possible;
o Supporting the PDGS-FOS mission planning loop. Accordingly verifying the complete
scheduling by the FOS of the Mission-Plan activities;
o Providing planning analysis & assessment capabilities (statistics generation on
generated planning such as highest, average, lowest data latency figures, total sensing
time, etc.);
5.2.4.2.2 Design Drivers and Constraints
The following drivers and constraints are identified:
○
Flexibility to adapt to different acquisition & downlink scenarios (e.g. different ground
stations assignation along mission life, ground stations roles, etc.).
○ Multi-spacecraft management capabilities (i.e. load balancing strategies between S2A
and S2B spacecrafts for acquisitions, downlinks, etc.).
○ Automation capabilities for the planning generation activities;
○ Usage of “Sentinels” Mission CFI generated by ESTEC (envisaged customisation of
the Earth Explorer CFI);
○ Operational interface for inputs/outputs through the MCC function acting as proxy;
○ Usage of the DC function for required data circulation activities;
5.2.4.2.3 Function Interfaces
The following function interfaces are identified for the MPL function:
○ The POM for the definition of the mission acquisition and downlink scenario cascading
from the HLOP;
○ The MPA function operators for specific calibration requests;
○ Input interface for relevant mission reference configuration (e.g. ground stations
database, SSCF, etc.) provided by MCC function via DC function;
○ Input interface for the FOS planning response (i.e. Plan Increment File) provided
through the MCC and DC functions;
○ Input interface for mission reference operations information (e.g. FOS PIF, predicted
orbit file, etc.) provided by the MCC function;
○ Output interface for mission reference files delivery (e.g. reference orbit file);
ESA UNCLASSIFIED – For Official Use
© ESA
The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or
communicated to any third party without written permission from ESA.