29.11.2014 Views

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>OCD</strong><br />

Issue 1 Revision 2 (draft) - 25.07.2010<br />

GMES-GSEG-EOPG-TN-09-0008<br />

page 74 of 350<br />

For <strong>Sentinel</strong>-2B and future replacement units, the CP will cover S2CP requirements and<br />

coordinate the overall <strong>PDGS</strong> operations considering its operational state within the <strong>GSC</strong><br />

versus the satellites in the operational constellation.<br />

EDRS data-repatriation and dissemination system interfaces will be commissioned separately<br />

when the respective EDRS capabilities are available.<br />

As applied to the spacecraft under commissioning, it is anticipated that the <strong>PDGS</strong> operations<br />

cascading from S2CP will require in particular:<br />

○ A fast planning and re-planning loop with the FOS to schedule the spacecraft<br />

according to the plan and deviations from the plan in case of contingencies;<br />

○ The operational supply of Level-0 and Level-1 data-products to the CNES/CST to carry<br />

out instrument in-flight characterisation and calibration;<br />

○ The operational supply of X-Band HKTM data to the FOS;<br />

○ The coordination of payload and ground processor configuration changes from CNES<br />

input, associated configuration control and upload as required to the satellite via the<br />

FOS nominal interface;<br />

○ The coordination with the EDRS exploitation segment for the effective planning of data<br />

downlinks via the OCP and the EDRS data-relay transponder;<br />

○ The independent assessment of the mission performance.<br />

4.3.2.2 Mission Evolutions<br />

4.3.2.2.1 Spacecraft Phase-in<br />

The <strong>Sentinel</strong>-2 mission program includes the gradual phase-in of spacecraft units in the<br />

constellation, starting with the launch of <strong>Sentinel</strong>-2B 18-30 months after <strong>Sentinel</strong>-2A<br />

[Assumption-03], and subsequently followed by the recurrent launches of replacement units.<br />

This imposes a number of constraints to sustain the operational services particularly at the<br />

transitory phases from the launch of a new spacecraft until its successful commissioning in<br />

operations.<br />

4.3.2.2.2 EDRS Phase-in<br />

The GMES <strong>Sentinel</strong>s program includes the future complementary usage of the EDRS<br />

capacities (cf. section 3.7) starting in the 2013 timeframe as from the current plan. This<br />

planned rendezvous, although coinciding well in time with the availability of <strong>Sentinel</strong>-2A does<br />

not lead to setting-off the <strong>Sentinel</strong>-2 operational services with EDRS, and an X-Band only<br />

CGS network is taken as baseline.<br />

This programmatic constraint imposes that the <strong>PDGS</strong> operation concepts are designed with<br />

embedded flexibility and scalability to be able to swiftly accommodate the substantial<br />

enhancements brought in by EDRS for data relay, multicast repatriation and broadcast<br />

dissemination capabilities in the future operation baseline (cf. [RD-47]). It also imposes that<br />

the <strong>PDGS</strong> operations account for a significant operation baseline change while the <strong>PDGS</strong> is<br />

already providing its operational services based on the initial baseline.<br />

<strong>ESA</strong> UNCLASSIFIED – For Official Use<br />

© <strong>ESA</strong><br />

The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied or<br />

communicated to any third party without written permission from <strong>ESA</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!