GSC Sentinel-2 PDGS OCD - Emits - ESA

Some relevant use cases are presented according to this operation scenario:
GSC Sentinel-2 PDGS OCD
Issue 1 Revision 2 (draft) - 25.07.2010
GMES-GSEG-EOPG-TN-09-0008
page 293 of 350
The MSI on-board and on-ground configuration generated during the phase E-2 will be
supplied by the PDGS/MPA function;
PDGS operations reports such as the ground stations acquisition reports will be
gathered and stored for later supply to the MPA function;
The operator via the MCC HMI will generate the PDGS data-circulation / archive rules.
6.14.3.3 Coordinated Release
The scenario stands for the operator-driven release of a selected set of Mission Reference
Files. The release of such files should be done before their activation time (i.e. before they
become applicable). In some cases, the operator will explicitly define such activation time, or
leave original activation time stamped on the file as defined by the source generator.
Prior to the mission reference files release, the POM is made aware of the mission reference
changes and their expected impact and is sought for approval.
The following steps are identified for this operation scenario:
1) The POM can be reported on the mission reference files updated (e.g. affected files,
specially the ones related to the mission configuration). The MMA approves such new
configuration changes;
2) The Operator validates the selected files to be released (e.g. file validation, parameters
cross checks among different files, specific rules according to the file nature);
3) The MCC function generates a check-list to specify the mission reference files to be
released defining their activation time;
4) After successful coherency checks and the check-list generation, the selected mission
reference files are released and delivered (i.e. components are delivered according to
the data circulation rules).
Some relevant use cases are presented according to this operation scenario:
New NUC table (generated by the MPA function) is released to the FOS. It is supplied
in OBSM and a SOR form request is submitted to the FOS. The SOR form response is
autonomously processed by the MCC function and in case of update rejection, the
operator alerted;
New reference orbit scenario is delivered to the FOS and the PDGS relevant functions;
The MCC function will ensure both the on-ground and on-board applicability time
coherency when required (e.g. on-ground GIPP updates and the on-board
configuration update).
6.14.3.4 Uncoordinated Release
The scenario stands for the autonomous uncoordinated release of the configured mission
reference files as they are gathered, ingested and classified by the MCC (cf. Registration of
new Mission Reference Files).
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.