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 116 of 350 The PDGS mission planning operations will be hence be defined according to the above constraints and provision for: ○ A nominal planning scenario, activated recurrently according to a pre-defined interval (every two weeks or more) during working days only, and feeding the FOS with mission-planning input covering the plan increment required for autonomous operations until the next PDGS plan interval with appropriate margin (i.e. 15 days or more according to the defined plan update interval); ○ A re-planning scenario, activated seldomly and when strictly required (e.g. unplanned events, commissioning-phase requirements, etc). The nominal planning scenario will be phased with the agreed S-Band pre-allocated uplink scenario described above and account for at least 3 working-days margin as nominally required by the FOS. The re-planning scenario activation will be constrained with a nominal 3 working-days margin that can be relaxed to one working-day in special situations. Each planning session, whether of the nominal planning or re-planning scenario will be performed in closed-loop with the FOS as follows: ○ The PDGS will provide a conflict-free 2 planning file of the required coverage such as to systematically describe the operations up to the beginning of the next PDGS plan interval with appropriate margin. All operations will be tagged under the OPS scheme except for operations specifically requiring MTL programming. ○ In response, the FOS will verify the PDGS generated plan against satellite safety constraints, detect any other potential conflict with other constraints (i.e. Flight Dynamics planned activities, Flight Control Team operations, etc.), and acknowledge the effective planning back to the PDGS, reporting failures on specific requests if any. Any rejected request will invalidate the entire planning session, and trigger contingency operations followed by a new planning loop. Contingencies on the planning-loop will be handled on a case-by-case basis as theoretically seldom and corresponding either to unforeseen events occurring at satellite or FOS levels or not well anticipated at PDGS level. According to the specific conflict reported by the FOS, and in the case an unforeseen spacecraft safety constraint was violated, the generation of new plan aiming at satisfying the constraint will be attempted. 4.5.3.1.2 EDRS/OCP Scheduling Although not precisely known at this stage, downlink capabilities via the OCP are anticipated to support the potential mission enhancements via EDRS outlined in section 3.7. The constraints applicable to OCP operations (cf. 4.3.8.6), together with the effective downlink budget and effective data-relay opportunities that will be provided are currently TBD or TBC. In this respect, the PDGS operations concepts will provisionally include the commanding of data-downlinks via the OCP based on the following assumptions: 2 The spacecraft operations constraints to be verified by the mission plan will be identified in a coordinated document called the Spacecraft Safety Constraints File (SSCF). This interface, maintained by the FOS throughout the mission lifetime under the form of a document, characterises the constraints and provides a relative apportioning of the ones to be verified at PDGS level, FOS level or both. The PDGS will explicitly refer to the applicable version of the SSCF used for the planning in every plan provided to the FOS. 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.
ESA UNCLASSIFIED – For Official Use GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 117 of 350 ○ OCP downlink commanding will be performed via the FOS similarly to X-Band downlinks; ○ The FOS will require that the PDGS provides the location (or identification) of the EDRS spacecraft associated to a data-relay downlink to allow consistent commanding of OCP pointing activities towards the relay GEO transponder; ○ The FOS will transparently take charge of commanding the OCP preparatory operations required for an effective downlink according to the PDGS provided downlink segments. As per the above assumptions, the commanding of OCP operations vis-à-vis the FOS will be managed by the PDGS similarly to the case of X-Band downlinks, with additional parameterisation of the downlink requests related to the identification of the EDRS GEO spacecraft required by the FOS to manage OCP pointing and activation activities. Regarding the PDGS interface to the EDRS exploitation segment, no recurrent and dynamic scheduling will apply. 4.5.3.1.3 PDGS Downstream Planning and Scheduling Operations To a high-level, the PDGS operations will be entirely driven by the raw-data downlinked from the spacecrafts supported by complementary deterministic and predefined schedules of activities targeting mission performance overall assessment and control (cf. next paragraph). Hence, there will be very limited explicit planning of the PDGS operations beyond the scheduling of data-reception operations at the CGS network that will trigger most of all downstream operations in cascade and in a systematic manner. Those operations are outlined in section 4.5.6. In addition, data-reception at the LGS network will be scheduled as described in section 4.5.4.3. 4.5.3.2 Mission Performance Monitoring and Control Operations As a background task, the PDGS will perform routine monitoring of the mission performance and retrofit configuration changes as required to ensure the mission overall quality over time. The scope of this activity will comprehensively cover the performance monitoring of all mission elements including the spacecrafts and its payload, the FOS and the PDGS with particular focus on the availability, reliability and quality of the data delivered to end users according to HLOP mission quality targets. The monitoring of the product-quality and overall mission performance will be ensured through well-defined Quality-Control (QC) procedures. QC operations will be performed following a predefined and recurrent schedule such as e.g. daily, monthly or following the 10- days repeat cycle or in a data-driven manner on reception of specific data takes pre-planned for this purpose. They will cover: ○ The systematic short to long-term assessment of the payload performance, the products quality and overall mission performance; ○ The systematic retrofit on the system configurable items impacting on the mission performance based on the output of assessment activities. © 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 67 and 68: ESA UNCLASSIFIED - For Official Use
Page 97 and 98: Table 4-5 Radiometric image quality
Page 99 and 100: Product- Type On-Line retention Off
Page 103 and 104: 4.5.1.5 Scalability and Flexibility
Page 111: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 163 and 164:
ESA UNCLASSIFIED - For Official Use
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:
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

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

Delete template?

Save as template?