GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 322 of 350 6.18.3.6 Training and Rehearsal The training and rehearsal scenario has been introduced for anticipating such activities on the RP in case the PDGS target platforms (the on-site PDGS Facilities) are not yet available. By the way it can be justified by the long-term maintainability of the system, for training new operators on RP before they are sent on the deployed PDGS Facilities. The scenario will be triggered by a training plan or a rehearsal campaign. The following steps are identified for this operation scenario: 1) RP operator will receive a training plan and will ensure that there are no conflicts with the on-going testing activities; 2) RP operator will negotiate the training time windows; 3) RP will be set to a pre-defined configuration (e.g. the dedicated training one); 4) PDGS operators will be hosted on RP for training, where it is assumed of having a training procedure documents and course manuals; 5) RP switch-off from the training configuration. 6.19 MSI Decompression Supply (MDS) Operations 6.19.1 PRINCIPLES The MSI data decompression is preliminary activity performed as part of the MSI level-1 products generation (cf. section 4.5.4.5.1 - Level-0 Consolidation and Level-1 Processing Logic). The MSI Level-0 data is processed by the MSI Decompression SW and therefore is accordingly integrated as part of the PDGS IDP function as part of its level-1 processing activities responsibilities. Therefore the MSI Decompression SW must be compatible with the PDGS platform definition (i.e. HW, OS, etc) is accordingly supplied to the IDP function for the needed integration activities. 6.19.2 OPERATION CONSTRAINTS The MDS function will aim for the long-term maintenance of the MSI Decompression SW in support of the Long-Term Data Preservation objectives described in the section 4.5.1.6. Accordingly the MSI WICOM decompression software must evolve (i.e. to support new HW/OS platforms) coping with the PDGS system evolutions and maintenance activities that may be produced along the mission life-time and beyond (over 40 years). 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 OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 323 of 350 6.19.3 OPERATION SCENARIOS 6.19.3.1 Periodical / Scheduled New Version Delivery This operation scenario stands for the periodical and / or scheduled deliveries of new versions of the MSI Decompression SW according to the different PDGS milestones including both development and operations phases. The MDS function publishes on-line the new MSI Decompression SW versions according to agreed frequency update (e.g. one yearly delivery) or/and in support of the PDGS development phases (i.e. for integration within the IDP function in charge of the MSI level-1 processing activities). The following steps are identified for this operation scenario: 1) The MSI Decompression SW supplier prepares a new version delivery (e.g. repackaging of the latest accumulative patches, migration to new HW/OS platforms); 2) A regression tests campaigns are performed to verify and validate the new version; 3) A Software Release Note of the new version is prepared; 4) The new MSI Decompression SW is published on-line and an email is sent to the list of subscribed users; 5) The new version is then downloaded and verified at the RP function to be included in a new release of the PDGS. 6.19.3.2 Patch / Corrective Delivery This operation scenario stands for the on-request delivery of a MSI Decompression SW patch/corrective version in response to a raised anomaly. The MDS function receives a request to solve a (blocking) problem on the Decompression SW that restrains the normal operations. Accordingly, the RP function has raised an anomaly (cf. section 6.18.3.1- System Anomaly Management) and supplies all the needed information (i.e. test data to reproduce the anomaly) to the MDS function for the corrective actions. The following steps are identified for this operation scenario: 1) The RP function raises a previously verified anomaly on the MSI Decompression SW to the MDS function and supplies all the information required to reproduce it; 2) The MDS function according to the defined service agreement (i.e. provide a corrective patch in less than 5 working days) analyses the problem and implements a solution; 3) A Patch/Corrective delivery is prepared in the same manner as presented in the previous scenario; 4) The new MSI Decompression SW is published on-line and an email is sent to the list of subscribed users; 5) The new version is then downloaded and verified at the RP function to be included in a new release of the PDGS. 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:
document title/ titre du document P
Page 3 and 4:
GSC Sentinel-2 PDGS OCD issue 1 rev
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
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:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
[RD-33] Sentinel-2 MSI - Level 2A A
Page 35 and 36:
Page 37 and 38:
LES LGS Land Equipped Sites Local G
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
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:
ESA UNCLASSIFIED - For Official Use
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Table 4-5 Radiometric image quality
Page 99 and 100:
Product- Type On-Line retention Off
Page 101 and 102:
Page 103 and 104:
4.5.1.5 Scalability and Flexibility
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
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:
4.6.3 OPERATIONAL TRANSFER BASELINE
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:
Product- Type Identifier S2MSI0 S2M
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
○ Effective processing resources
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
o preserving integrity of exchanged
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246:
o Report generation frequency and c
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
○ MSI L1A, L1B, L1C and TCI produ
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 277 and 278: ESA UNCLASSIFIED - For Official Use
Page 289 and 290: Some relevant use cases are present
Page 317: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 325 and 326: Two main mapping services have been
Page 327 and 328: The requirement on the cloud covera
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?