GSC Sentinel-2 PDGS SRD - emits - ESA

More documents

Recommendations

Info

GSC Sentinel-2 PDGS SRD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-RD-09-0028 page 128 of 204 S2-PDGS-DAG-165 The PDGS/DAG function shall be able to accept and manage hosted-processing requests submitted by the users from the MMUS function using the local processing capabilities and data available in each PDGS centre. S2-PDGS-DAG-170 The PDGS/DAG function shall be able to route the hosted processing requests in an optimal way amongst the distributed DPC function instances available for processing considering the data locally available for processing at each centre. S2-PDGS-DAG-175 The PDGS/DAG function shall support the simultaneous management of several hostedprocessing transactions and several product download transactions performed in parallel. 5.13.2 PERFORMANCE REQUIREMENTS S2-PDGS-DAG-180 The PDGS/DAG function shall complete the download of a product assembling 9 Level-1C tiles (300km x 300km) comprehensive of all bands within less than 1 second over the time required to transfer all product components through the network via the standard FTP protocol. S2-PDGS-DAG-185 The PDGS/DAG function shall complete the download of a full swath MSI Level-0 product and of 6640 km along-track comprehensive of all bands within less than 5 seconds over the time required to transfer all product components through the network via the standard FTP protocol. S2-PDGS-DAG-190 The PDGS/DAG function shall support the parallel processing of at least 100 product download requests from a single archive centre. S2-PDGS-DAG-195 The PDGS/DAG function shall support the parallel management of at least 100 hostedprocessing requests versus a single processing centre. 5.13.3 OPERATIONAL REQUIREMENTS S2-PDGS-DAG-200 The PDGS/DAG function shall be deployed and operated locally in CGSs and PACs acting as local data download and/or hosted-processing servers. 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.
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.
Page 1 and 2:
Appendix B D O C U M E N T document
Page 3 and 4:
GSC Sentinel-2 PDGS SRD issue 1 rev
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
GSC Sentinel-2 PDGS SRD Issue 1 Rev
Page 11 and 12:
Page 13 and 14:
[RD-11] GMES Sentinel-2 Phases B2,
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
ESA UNCLASSIFIED - For Official Use
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76: 5.3 Data Processing Control (DPC) R
Page 77 and 78: GSC Sentinel-2 PDGS SRD Issue 1 Rev
Page 85 and 86: 5.4 Instrument Data Processing (IDP
Page 91 and 92: ESA UNCLASSIFIED - For Official Use
Page 103 and 104: 5.8 Long-Term Archive (LTA) Service
Page 117 and 118: the geographical footprint of the d
Page 125: GSC Sentinel-2 PDGS SRD Issue 1 Rev
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
S2-PDGS-NET-065 The DCN shall provi
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
show all

GSC Sentinel-2 PDGS SRD - emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?