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 292 of 350 To support the effective file collection and release mechanisms, file transfers to and from the MCC function interfaces will be managed via a collocated Data-Circulation function. As such, effective data-circulation is considered out of the strict scope of the MCC function operation. 6.14.3 OPERATION SCENARIOS 6.14.3.1 Definition of the MRF Configuration Rules This scenario accounts for the operator-driven definition of the Mission Reference Files Configuration Control rules. This scenario includes the various configuration-control rules applicable to each kind of mission reference file (i.e. identified by the file-type), associating for each one typically: The assigned release mechanism MR-C or MR-U; Data circulation configuration (retrieval and delivery operations and associated I/F definitions); The operator will define and maintain along time the data management possibly adding new components, modifying them or removing deprecated ones as relevant. Some use cases are presented here according to this operation scenario: Initialisation of the function configuration. Preliminary rules will be defined and tested until OSV; Preparation for second spacecraft S2B operations. Additional rules for spacecraft specific configuration will be added neither affecting nor conflicting current operational S2A ones; Change the data-management rule for a given file-type (e.g. once mission planning has been well validated and used it may be released automatically under MR-U, previously configured under MR-C for the operator supervision). 6.14.3.2 Registration of new Mission Reference Files This scenario accounts for the new mission reference files registration by the MCC function. It includes the mission reference files gathering from the other PDGS functions and the operator-driven generation of own MCC responsibility mission reference files. The following steps are identified for this operation scenario: 1) The MCC function gathers autonomously all the Mission Reference Files generated by other PDGS functions; 2) The MCC function supports via an adequate HMI the operator on the generation of the Mission Reference Files under its responsibility; 3) The MCC function autonomously or triggered by the operator performs the validation (i.e. syntax, semantics, specific verification on mission rules, etc); 4) The MCC function keeps under configuration and control the new Mission Reference Files. 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.
Some relevant use cases are presented according to this operation scenario: GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 293 of 350 The MSI on-board and on-ground configuration generated during the phase E-2 will be supplied by the PDGS/MPA function; PDGS operations reports such as the ground stations acquisition reports will be gathered and stored for later supply to the MPA function; The operator via the MCC HMI will generate the PDGS data-circulation / archive rules. 6.14.3.3 Coordinated Release The scenario stands for the operator-driven release of a selected set of Mission Reference Files. The release of such files should be done before their activation time (i.e. before they become applicable). In some cases, the operator will explicitly define such activation time, or leave original activation time stamped on the file as defined by the source generator. Prior to the mission reference files release, the POM is made aware of the mission reference changes and their expected impact and is sought for approval. The following steps are identified for this operation scenario: 1) The POM can be reported on the mission reference files updated (e.g. affected files, specially the ones related to the mission configuration). The MMA approves such new configuration changes; 2) The Operator validates the selected files to be released (e.g. file validation, parameters cross checks among different files, specific rules according to the file nature); 3) The MCC function generates a check-list to specify the mission reference files to be released defining their activation time; 4) After successful coherency checks and the check-list generation, the selected mission reference files are released and delivered (i.e. components are delivered according to the data circulation rules). Some relevant use cases are presented according to this operation scenario: New NUC table (generated by the MPA function) is released to the FOS. It is supplied in OBSM and a SOR form request is submitted to the FOS. The SOR form response is autonomously processed by the MCC function and in case of update rejection, the operator alerted; New reference orbit scenario is delivered to the FOS and the PDGS relevant functions; The MCC function will ensure both the on-ground and on-board applicability time coherency when required (e.g. on-ground GIPP updates and the on-board configuration update). 6.14.3.4 Uncoordinated Release The scenario stands for the autonomous uncoordinated release of the configured mission reference files as they are gathered, ingested and classified by the MCC (cf. Registration of new Mission Reference Files). 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
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 261 and 262: ESA UNCLASSIFIED - For Official Use
Page 287: 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
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?