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 159 of 350
4.5.6 PDGS END-TO-END OPERATIONS
On a daily basis, the PDGS will schedule the CGS network for data-reception according to
the mission plan preliminarily settled with the FOS (cf. 4.5.3.1). Then, as driven by the
downlink plan (cf. 4.5.4.2), the PDGS will operate systematically via configurable rules
commanding all elaboration steps cascading from data-reception, including:
○ Antenna acquisition, signal demodulation, front-end processing, Level-0 processing
and archiving (cf. sections 4.5.4.3.2 for MSI data and 4.5.5 for HKTM data);
○ Systematic processing of all MSI acquired raw-data to higher levels (cf. sections
4.5.4.3.2 and 4.5.4.6);
○ Systematic essential quality-control over the MSI acquired and processed data (cf.
section 4.5.4.7);
○ Systematic inventory and archiving of all data with well-defined retention (cf. section
4.5.4.9.1);
○ Systematic and data-driven internal data circulation among the distributed stations and
centres according to a coordinated and well-defined configuration (cf. section
4.5.4.9.2)
○ Systematic data distribution towards external interfaces (cf. sections 4.5.2 for MSI
products and 4.5.5 for HKTM)
This overall process will be carried out in a FIFO manner as driven by the downlink scenario
defined in section 4.5.4.2.
The generation of the Level-2A prototype product will be triggered interactively by authorised
users via the hosted processing functionality (cf. 4.5.4.6).
As driven either by the Cal/Val agenda or recurrently following a predefined agenda, the
PDGS will perform the following operations in the background:
○ Systematic Cal/Val activities (cf. section 4.5.4.10) with retrofit on the instrument and
ground-processing chains configurations (cf. section 4.5.3.3);
○ Systematic Quality Control over the globally processed data and on the overall mission
performance (cf. section 4.5.3.2) in the short to longer term.
Contingency operations will be triggered on malfunctions in the nominal data flow covering:
○ Recovery of malfunctions in the Level-0 processing chain (cf. section 4.5.4.3.2),
○ Recovery of higher-level productions (cf. section 4.5.4.8.2),
○ Recovery of problems throughout the data archiving and circulation network (cf.
section 4.5.4.9).
Reprocessing operations will be performed as driven by the required evolutions of the
Sentinel-2 Level-1 and Level-2 datasets in the long term (cf. section 4.5.4.8.1).
All above operations are described in more details in Chapter-6 according to the functional
breakdown provided in Chapter-5.
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.