GSC Sentinel-2 PDGS SRD - emits - ESA

GSC Sentinel-2 PDGS SRD
Issue 1 Revision 2 (draft) - 25.07.2010
GMES-GSEG-EOPG-RD-09-0028
page 129 of 204
S2-PDGS-DAG-205
It shall be possible to deploy and operate the PDGS/DAG function in a collaborative
CDAM centre acting as local download server.
S2-PDGS-DAG-210
The PDGS/DAG management function shall be deployed and operated locally in the
PDMC acting as central physical point of access supported by at least on PAC instance
configured as hot-redundant backup for this function.
S2-PDGS-DAG-215
The PDGS/DAG function shall supply status information over all its local processes and
resources (i.e. log information, disk volumes usage, alarms, etc.) in real-time via the
collocated M&C function.
S2-PDGS-DAG-220
The PDGS/DAG function shall operate autonomously and mechanically as triggered by
download requests and hosted-processing requests.
S2-PDGS-DAG-225
The PDGS/DAG function shall systematically notify the MMUS function of the
successful/unsuccessful completion of a product download request.
S2-PDGS-DAG-230
The PDGS/DAG function shall systematically provide a summary report to the MMUS
function on completion of every download including the volumes of data downloaded, the
time to serve the request, etc, or qualifying the source of the problem in a human
understandable message for failed downloads.
5.13.4 RAMS REQUIREMENTS
S2-PDGS-DAG-235
The PDGS/DAG function shall ensure nominal operations in hot-redundant configuration
unattended for better than 99.7% of the time computed over one month time window and
assuming a degradation of such figure for no more than one day.
S2-PDGS-DAG-240
The PDGS/DAG function shall ensure that the User-Products delivered are consistent and
complete of all data.
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.