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 230 of 350 PDGS performances. Nevertheless, it shall be sized sufficiently to allow for real-case representative load tests on the PDGS integrated systems; ○ It aims for maximised flexibility targeting swift reconfiguration capabilities, mapping a given physical layout from available generic workstations to match the system test necessity, and supporting interactive handling of the platform itself as relevant for investigation purposes such as for the implementation of workaround solutions, the installation of operating system patches, etc. ○ It aims for deployment in an adapted environment guaranteeing sufficient space for all the staff working in the IV&V and maintenance processes, and housekeeping all reference documentation with appropriate human browsing mechanisms (in paper form or otherwise); ○ It shall be composed by hardware identical or compatible to a large extent with the one of the deployed PDGS including middleware configurations; ○ It shall be assumed network connectivity to the PDGS deployed sites will be ascertained supporting secure remote access for software deployments and troubleshooting on the operational sub-systems. ○ As a standalone PDGS, it aims for transportability in any European location clearly qualifying and quantifying associated site installation requirements (e.g. required power resources, cooling, workplace, connectivity requirements, etc). ○ It aims for maximum reuse of widely used market solutions for all system management support functions dedicated to system inventory, revision control system (e.g. GIT, SVN, CVS, etc), documentation management (e.g. InfoTrove, KnowledgeTree, etc) and system anomaly management (e.g. Jira, Mantis, Bugzilla, etc). 5.2.4.5.3 Function Interfaces The following interfaces are identified: ○ Secure network access interfaces to the PDGS centres (e.g. ssh, sftp) for troubleshooting and software deployment activities; ○ An interface to the operational MCC function via a local DC function for the provision of the mission configuration required as reference for testing and validation activities. 5.2.4.6 Collaboration Support Service (CSS) Function 5.2.4.6.1 Function Objectives and High-Level Description The CSS function is primarily aimed at providing technical support vis-à-vis the collaborative PDGS peers according to the needs of each type of collaboration expressed in sections 4.10.2.1 and 4.10.2.2, based on collaboration agreement between the peer entities and the POM. In addition, it is responsible for liaising with the POM for the definition of the collaborations and to provide associated progress reports during implementation as defined in section 4.10.3.2.4. 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 231 of 350 For hosted-processing collaborations, the CSS will be responsible for carrying out the Processor Integration Service activities defined in section 4.10.2.2.2.1 in coordination with the peer-entity. As such it will take charge of: ○ Defining and maintaining a set of documented integration guidelines with relevant technical documentation (such as a well-defined Interface Control Document between the user-processor and the PDGS host environment). This documentation set is aimed for use by the collaboration peers in providing all information required to enable the hosting of their processor as a regular IDP function and in clarifying the tools and procedure applicable throughout the collaboration. ○ Providing support to the peer entities for the definition, integration and running of their processors under the form of a help-desk activated throughout the collaboration; ○ Performing the actual integration of the user-provided IDP processing functions within the DPC environment, including the coordinated configuration of other relevant elements such as the DAG elements. Regarding data-access mirroring centre collaborations, the CSS function will take charge of: ○ Performing technical-support activities towards the collaboration peers as described in section 4.10.2.1.2 such as the provision and maintenance of software with associated documentation and the operations of a support help-desk; ○ The configuration of the core PDGS for the operational data-supply of data-products to the peer mirror centres including the set-up of dedicated network links if applicable. Regarding support to POM, the CSS function will provide dedicated reporting on the status of the collaboration and main outcome with respect to the agreed terms of the collaboration. For hosted-processing collaborations, reporting will cover in particular: ○ The overall collaboration status; ○ The maturity of the new products generated and their validation status (e.g. through scientific publications); ○ The evolution potential of the collaboration that could motivate valued-added promotion and sustained generation within the PDGS. For data-access mirroring centre collaborations, reporting will summarise the volume supplied and associated data-distribution statistics. 5.2.4.6.2 Design Drivers and Constraints As corresponding to an operational service, no specific design driver is highlighted for the CSS function beyond the compliance with its associated interfaces. 5.2.4.6.3 Function Interfaces The following functional interfaces are identified: ○ The RP function for the testing of the user processors prior to deployment and the associated configuration required to support operational integration. 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 183 and 184: ESA UNCLASSIFIED - For Official Use
Page 191 and 192: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 207 and 208: ○ Effective processing resources
Page 225: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 231 and 232: o preserving integrity of exchanged
Page 243 and 244: 6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246: o Report generation frequency and c
Page 251 and 252: ○ MSI L1A, L1B, L1C and TCI produ
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

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

Delete template?

Save as template?