GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

4.6 System Maintenance and Evolution Concepts GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 160 of 350 The Sentinel-2 PDGS will assume a single overall configuration serving both Sentinel-2A and Sentinel-2B units. As such, the PDGS will be designed and qualified (since its first deployed configuration before Sentinel-2A launch) for operations in the dual spacecraft context, at least on a functional point of view. Nevertheless, the time separating the two launches together with the requirements on the PDGS to insure specific tasks during the commissioning-phase of the spacecrafts will impose that while the PDGS is fully operational for Sentinel-2A, it shall accommodate the gradual phase-in of the activities required to serve the second unit (e.g. PDGS sizing, non-regression testing, OSV, commissioning activities, etc). It is further anticipated that although the two units are theoretically identical [Assumption-01], slight changes might have to be accommodated before-hand on the PDGS to prepare for the assimilation of Sentinel-2B in addition to the hardware sizing increase required to cope with the dual data-flow. Hence, the PDGS operations concept shall include a specific operation scenario provisioning for the accommodation of additional constellation spacecrafts while in operations. As regarding the foreseen evolution of the Sentinel-2 mission with EDRS (cf. section 3.6) which will possibly happen subsequently to Sentinel-2A launch, similar provision shall be made in the PDGS operations concepts to allow for accommodating the new interfaces in operation. More generally, the PDGS shall account for the necessary evolutions of its system-level configuration throughout its lifetime in hardware and software as required by its operational maintenance activity. This section settles the operation baseline in this respect. Following introductory paragraphs, a common approach applicable to the PDGS operational transfer is specified. Then, specialised scenarios targeting the operational phase-in of new spacecraft units and EDRS are described. 4.6.1 REFERENCE-PLATFORM The operational maintenance activity of a system with distributed complexity such as the PDGS will not efficiently be carried out directly on the target platform. As it will commonly be installed with a dedicated environment tailored for its operational scope (e.g. without space dedicated to IV&V activities and associated teams), and considering its geographical distribution in various sites, problem troubleshooting and resolution would be doubtlessly unproductive. Hence, for self-supporting its system maintenance and evolution activities, the PDGS will include a specific Reference-Platform (RP) function. The Reference-Platform will aim at simulating the PDGS behaviours in parts or as a whole by way of a simplified local instance acting as a reference image of the deployed PDGS instance. There will be a unique Reference-Platform that will be equipped and manned specifically in order to: ○ Support the IV&V Phases 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.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 161 of 350 ○ Support problem investigations during OSV, Phase-E1 and Phase-E2 of the spacecrafts as required by the corrective-maintenance activity; ○ Support the qualification phase of all PDGS system upgrades before deployment as required by maintenance or evolution activities; ○ Support the PDGS deployment phases of the initial and upgraded versions in configuring and assembling the deployed-configuration elements to be deployed. As holding a true functional role including during the entire PDGS operational phase, the PDGS RP is intended as a specific functional item of the PDGS with a dedicated associated operations concept. 4.6.2 SYSTEM STATES AND CONFIGURATIONS Throughout its lifetime, the PDGS will evolve between several configurations and states as required by its development and maintenance activities and by the gradual phase-in of the Sentinel-2 constellation spacecrafts it will serve. As regarding the successive phase-in of the Sentinel-2 units with their respective mission phases, and while it is assumed that a single and unique PDGS system will be shared to serve the constellation, a distinction has to be made between the PDGS instance and the specific state in which it is operating. The instance of the PDGS refers to its specific existence as an integrated system. As such, there will be a single physically deployed PDGS instance. In complement, a localised (in a single location) reference instance of the PDGS called the Reference-Platform (RP) will be used for testing, simulation and long-term maintenance purposes (cf. previous section). In counterpart, the state of the PDGS refers to its capability in serving a specific spacecraft mission. Hence, it is assumed that a single PDGS instance can operate in 2 distinct states simultaneously, one per Sentinel-2 unit. E.g. the PDGS may operate operationally for Sentinel-2A at the time Sentinel-2B is launched for which it operates in pre-operational state until the end of its commissioning phase. Finally the configuration of the PDGS applies to a particular PDGS instance and is configured to operate on one or both missions each one in their respective states. The following paragraphs describe those concepts in more details. 4.6.2.1 System States As driven by the successive phases of the Sentinel-2A and Sentinel-2B missions described in section 1.3 leading to a fully operational system supporting the Sentinel-2 constellation, as well as beyond this point, the following states of the PDGS are identified: ○ Development state: In this state, the PDGS is being built and pre-assembled as a system on the RP for testing purposes. It is assumed it embeds at this point some but not necessarily all of its intended functionality and as such may support only partial services limited to testing activities in a reduced configuration e.g. external interfaces compatibility testing, etc; 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 113 and 114: ESA UNCLASSIFIED - For Official Use
Page 155: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 191 and 192: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
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:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Some relevant use cases are present
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Two main mapping services have been
Page 327 and 328:
The requirement on the cloud covera
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?