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 76 of 204 S2-PDGS-DRX-265 The PDGS/DRX function shall support a reference time synchronized for its geographically distributed deployments and for required time-tagging activities (e.g. headers time-stamp, acquisition reports, etc). 5.2.5 RAMS REQUIREMENTS S2-PDGS-DRX-270 The PDGS/DRX function shall be designed to be reconfigured and operational in 30 minutes in case of failure possibly in full or degraded mode. S2-PDGS-DRX-275 The PDGS/DRX function shall provide reception capabilities with an availability of 99.7% computed over one month time window and assuming a degradation of such figure for no more than one day. The same availability figure is required for both X-band and Ka-band reception chains. S2-PDGS-DRX-280 The PDGS/DRX function shall ensure that received and demodulated data, including related acquisition confidence data, is recorded and archived with an availability figure of 99.7% computed over a period of 2 weeks. 5.2.6 DESIGN & DEVELOPMENT REQUIREMENTS S2-PDGS-DRX-285 The DRX function architecture design shall be such as to ensure that the data supply operations acquired of one spacecraft (e.g. S2A) do not impact in any manner the data acquisition and/or the data supply operations possibly carried out in parallel of another spacecraft (e.g. S2B). (This may imply in particular the separation at hardware level of the specific subsystems responsible for data storage/delivery (e.g. storage disk, network interface, interface server, etc). S2-PDGS-DRX-290 It shall be possible to extend the DRX function capabilities to support additional spacecrafts by simple configuration and addition of the required hardware as necessary. 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.
5.3 Data Processing Control (DPC) Requirements GSC Sentinel-2 PDGS SRD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-RD-09-0028 page 77 of 204 5.3.1 FUNCTIONAL REQUIREMENTS S2-PDGS-DPC-005 The PDGS/DPC function shall be responsible within the PDGS for generating the Level-0 product data from the downlinked raw-data input and orchestrating all cascading upper level processing activities performed through the IDP & OLQC functions. S2-PDGS-DPC-010 The PDGS/DPC function shall be able process to the raw-data real-time dataflow in a data-driven manner according to configurable rules. S2-PDGS-DPC-015 The PDGS/DPC function shall be able to support operator-driven processing activities (e.g. to perform the validation of a new processor, test new auxiliary parameters, reprocessing campaigns definition, etc). S2-PDGS-DPC-020 The PDGS/DPC function shall be able to receive and process the S2A and S2B raw data supplied in real-time by the DRX function during the satellite acquisitions. S2-PDGS-DPC-025 The PDGS/DPC function shall orchestrate all the data production in a data-driven manner and according to a FIFO mechanism based on the order at which the MSI raw data is supplied from the DRX function. S2-PDGS-DPC-030 The PDGS/DPC function shall be able to receive and process the MSI raw data ISPs. S2-PDGS-DPC-035 The PDGS/DPC function shall be able to manage the overlaps introduced in the MSI data downlinks throughout the CGS network and coherently reconstruct a continuous and overlap-free product timeline for archiving. Comment: The Satellite MMFU will be commanded (cf. MPL function) to generate some data overlaps on the MSI timeline by duplication of some MSI scenes to streamline the processing activities on-ground without the need for data circulation between stations (cf. Sentinel-2 MMFU Design Adaptations – S2-CR-ESA-SY-0009). 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: GSC Sentinel-2 PDGS SRD Issue 1 Rev
Page 29 and 30: ESA UNCLASSIFIED - For Official Use
Page 73: GSC Sentinel-2 PDGS SRD Issue 1 Rev
Page 85 and 86: 5.4 Instrument Data Processing (IDP
Page 103 and 104: 5.8 Long-Term Archive (LTA) Service
Page 117 and 118: the geographical footprint of the d
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
ESA UNCLASSIFIED - For Official Use
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?