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 196 of 350 ○ a system-level functionality expected to be translated into an automated behaviour of the PDGS through actual systems but which is intentionally left at system-level to maximise the opportunity of fulfilling it by reusing aggregate or customisable existing solutions; 5.2 Functional Model This section describes the decomposition of the PDGS overall functionality into complementary high-level primary Functions. 5.2.1 DESIGN LOGIC Based on the overall design rationale presented in the previous paragraph, the functional decomposition aims at defining a logical split of the PDGS overall required functionality into primary Functions which can optimally be distributed across centres to globally implement the operation baseline of the PDGS. As such, the functional breakdown comprehensively aims at: ○ Providing a first-level layout of primary Functions each one solving part of the problem in coordination with others in a logical way; ○ Providing a clear basis for the definition of operation concepts at Function-level that logically aggregate at system-level in responding to the PDGS baseline services; ○ Isolating Functions in view of optimising the logical-to-physical mapping into macrofunctional roles for the definition of PDGS Centres; ○ Isolating Functions according to typical existing market solutions that can be reused in parts or entirely from previous PDGS developments, while concentrating the specificities of the Sentinel-2 PDGS into other dedicated Functions; ○ Providing a clear view over the envisaged enhancements compared to previous developments, to meet the particular challenges of the Sentinel-2 mission; ○ Ensuring the functional blocks can be clearly associated to their key design-drivers in view of their implementation; ○ Embedding the required flexibility and scalability in the design in view of the distributed but yet unknown physical layout of the PDGS; Following a first section defining the breakdown, each identified function is then separately detailed with its specific objective, design-drivers and logical interfaces to the other functional blocks. The design rationale pertinent to each function group or function is described recalling the source operation constraints and drivers of section 4.3. Specific relevance to the PDGS operation baseline definitions outlined in chapter 4 is also pointed out. 5.2.2 FUNCTIONAL BREAKDOWN The first-level of the PDGS functional decomposition discriminates between Data Management functions, System Control functions and Data-Communication functions. 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 197 of 350 Whilst the first group refers to the primary core duty of the PDGS of translating the satellite acquired data into data-access services to the Sentinel-2 product users, the second regroups all Functions required at system-level to control, manage and coordinate the overall system behaviour. Some specific Functions although relevant to both groups have been allocated to a specific one, with the logic that they mostly apply to the specificities of the allocated group by their primary functionality and main drivers. The last group includes all physical data communication functions between or within Data- Management or System-Control functions. The following paragraphs follow this first level decomposition and provide the second and final breakdown into the PDGS Functions. 5.2.2.1 Data Management Functions 5.2.2.1.1 Core Objective As primary goal, the Data-Management Functions aim at reliably and systematically transporting the Sentinel-2 constellation data from the antenna down to its authorised users into elaborated user-products of controlled quality, timeliness and access performances. 5.2.2.1.2 Design Drivers The main drivers shared by all data-management functions are mostly driven by the Data- Access services characteristics complemented by the baseline requirements on the data products as defined in section 4.3. Associated drivers are highlighted such as: ○ The reliability of service for the systematic and timely availability of products on-line at the user interfaces according to the baseline plan including NRT and daily timeliness at the latest; ○ The uniform, well-defined and controlled quality of all products delivered; ○ The capability for discovery of products according to user-defined criteria including time geographical coverage and cloud-cover; ○ User-oriented supply mechanisms allowing the products to be delivered according to the strict user-needs in terms of format and contents; ○ The high expected demand for Sentinel-2 high-resolution optical products considering the open data-policy; ○ The long-term outlook of the PDGS services for data-supply of daily refreshed data during the 7 to 12 years of each spacecraft lifetime and to be extended for 25 years beyond. On a functional design point of view, the following drivers and constraints are highlighted: ○ The gradual phase-in of spacecrafts in the constellation during operations imposes that the data-management functions are designed with multi-spacecraft embedded features since the beginning allowing to clearly discriminate each spacecraft dataflow on a logical point of view; 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 147 and 148: ESA UNCLASSIFIED - For Official Use
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 191: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 207 and 208: ○ Effective processing resources
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 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?