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 253 of 350
○ The timeliness requirements also possibly impose the relative prioritisation of the
processing jobs to ensure the different PDGS processing priorities as RT, NRT and
reprocessing products imposing the access to a larger pool of processing resources
than the ones required for the “nominal” processing;
○ The DPC will be operable via HMI from an operator to carry out rehearsals, processing
error recovery (i.e. trigger again a given processing), reprocessing activities, etc;
○ The DPC will cope with the hosted-processing requests submitted by the PDGS frontend
services;
○ The DPC will be operable independently following several possibly conflicting
triggering mechanisms (data-driven, operator-driven, support of hosted-processing
requests). This constrains the DPC operations by an appropriate assignment and
relative apportioning of the various processing resources available to each source
trigger is well statically balanced or performed dynamically following the demand;
○ Finally, the high volumes to be processed impose a constraint on the I/O performance,
in particular versus the collocated AI function such that I/O does not become a
bottleneck in the overall performance budget.
6.2.3 OPERATION SCENARIOS
6.2.3.1 Data Processing Control Configuration
This scenario stands for the operator-driven configuration activities of the processing activities
prior to its activation and normal operations. This scenario also accounts for the operatordriven
definition and configuration of the DPC and the IDP (cf. section 6.3) functions.
The DPC function is supported by the RP function in the process of the definition of the
configuration according to the available processing resources, the expected processing load,
timeliness definitions, etc by the usage of the mission configuration validation capabilities (cf.
section 6.18.3.4) to test and rehearsal the processing activities devoted to the fine tuning
configuration.
Amongst others, the DPC and IDP functions configuration includes:
○ Processing rules definition;
○ Data fragmentation rules;
○ Parallelisation rules;
○ Processing resources definition.
The use case of this scenario is the generation of the PDGS processing configuration (i.e.
DPC/IDP functions). Such configuration is modelled to take into account the different data
product load assigned to the different processing centres and can be managed by the MCC
function (cf. section 6.14 - Mission Configuration Control (MCC) Operations) as Mission
Reference Files for their release across the federated centres.
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.