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 290 of 350 EDRS Availability Segments On-ground data processing parameters (e.g. GIPP) On-board payload parameters (e.g. MSI NUC tables for S2A and S2B) On-board platform parameters (e.g. thermal tables for S2A and S2B) [TBC] PDGS circulation rules PDGS archive rules 6.14.1.2.2 Operation Files The MCC function regroups all essential measurements and operation reports as part of the mission reference files. Operation files are centrally collected for configuration management purposes and released for assessment (i.e. delivered to MPA for performance assessment activities). Managed operation files will either relate to spacecraft-specific data (e.g. station acquisition report) or globally to the constellation. Typical examples include: The Payload plan The FOS Scheduled plan The ground stations Acquisition-Schedule-Plan The EDRS Booking-Plan Unavailability reports Stations acquisition reports PDGS processing reports PDGS archiving reports PDGS circulation reports 6.14.1.3 Mission Reference Files Management 6.14.1.3.1 Applicability Time The PDGS/MCC function will provide for the managed configuration the final applicability time resulting of its coordination role. Applicability time is the period (applicability start time & stop time tags) when a given component version should be officially used by the target systems. Although the MCC function managed files that are gathered from other interfaces can already provide an estimated applicability time, it will be MCC in last instance the one defining components versions official activation time when released. On the other side, the managed mission reference files with operations information do already provide final applicability time (provided by the originator function) and they are usually related to their operations or reporting time period every component refers to. In this case the MCC is not required to change the applicability time. 6.14.1.3.2 Release Concept The MCC function as for a proxy in the PDGS for what mission reference files release concerns. The release of a reference file is intended for its delivery to the applicable interfaces with a reference time (activation-time) for its usage. As explained in the previous section, the MCC function in some cases will define the files applicability time and therefore their activation time (i.e. the applicability start time). Generally 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 291 of 350 the MCC is likely to define this activation-time in coordination with other reference files and / or coordination with other interfaces for the applicability and usage time definition are required. In other cases, it is the source generation of the mission reference file the one in charge of defining this applicability for its official release although the MCC function will be able to override it if required. Driven by the required mission reference files management, the MCC function will provide releases: Mission Reference – Coordinated release (MR-C): the MCC function, when triggered by the operator, will release the selected set of mission reference files. Accordingly it is the operator who decides when to perform such release driven by the activation-time of the released files (e.g. PDGS circulation & archive rules); Mission Reference – Uncoordinated release (MR-U): according to configuration, the MCC function will automatically release the mission reference files that do not require update on the activation time already defined by the source (e.g. FOS PIF). 6.14.1.3.3 Support to FOS Special Operation Request The MCC function handles the payload on-board configuration updates (as part of the mission reference files) that are released to the FOS for the uplink and activation on-board. The managed payload configuration updates (cf. section 4.5.3.3.2) are supplied by the MPA function, generated as part of the performed Cal/Val activities, but released by the MCC according to the FOS required interface. Every single on-board configuration update is composed by the applicable payload table in the agreed format -SPF or OBSM- (cf. section 6.16.4.3) accompanied with a Special Operation Request (SOR) form (cf. section 4.5.3.3.2) submitted to the FOS. This mechanism is applicable to the update of the payload on-board configuration handled under both, MR-C and MR-U release mechanisms. In addition, the MCC function processes the SOR form response provided by the FOS to acknowledge the scheduled uplink time or the update rejection. 6.14.2 OPERATION CONSTRAINTS The MCC function will be centrally operated from the Payload Management Coordination Centre. As such, MCC operations will have to: Cope with the asynchronous generation of the different mission reference files fetched from throughout the PDGS and other ground-segment interfaces (e.g. FOS) and automatically register the data in a common repository; Support operator-driven mechanisms for the coordinated release (MR-C) of critical data; Support autonomous asynchronous file delivery mechanisms for the uncoordinated releases (MR-U) (e.g. most of operations 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: 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 285: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 289 and 290: Some relevant use cases are present
Page 325 and 326: Two main mapping services have been
Page 327 and 328: The requirement on the cloud covera
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?