GSC Sentinel-2 PDGS OCD - Emits - ESA
GSC Sentinel-2 PDGS OCD - Emits - ESA
GSC Sentinel-2 PDGS OCD - Emits - ESA
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<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 165 of 350<br />
○ A <strong>PDGS</strong> deployed configuration with a hybrid state starting at the time the <strong>PDGS</strong><br />
infrastructure is upgraded from a single mission sizing to its final sizing required to<br />
support the constellation. From this event onwards, the <strong>PDGS</strong> assumes nominal<br />
operations for <strong>Sentinel</strong>-2A while tests are carried out in parallel to prepare for<br />
readiness of <strong>Sentinel</strong>-2B operational phase-in;<br />
○ A <strong>PDGS</strong> configuration reaching the validation state for the <strong>Sentinel</strong>-2A/B constellation<br />
only after the completion of OSVs applicable to <strong>Sentinel</strong>-2B;<br />
○ A <strong>PDGS</strong> configuration with full functionality vis-à-vis the <strong>GSC</strong> for the <strong>Sentinel</strong>-2A/B<br />
constellation after successful <strong>Sentinel</strong>-2B commissioning.<br />
The hybrid-state <strong>PDGS</strong> configuration immediately following its full-size reconfiguration to<br />
support <strong>Sentinel</strong>-2B preparatory activities will be the critical step of this scenario. It will<br />
impose:<br />
○ A careful configuration of all Data-Access elements of the <strong>PDGS</strong> so that user access is<br />
not spoilt by the testing activity performed on the <strong>Sentinel</strong>-2B specific dataflow.<br />
○ A careful configuration of the <strong>PDGS</strong> mission-planning elements, in particular vis-à-vis<br />
the FOS, so that the mission planning function continues operating nominally for<br />
<strong>Sentinel</strong>-2A independently from <strong>Sentinel</strong>-2B test planning;<br />
○ A thorough pre-configuration and validation on the RP of new infrastructure elements<br />
shared between <strong>Sentinel</strong>-2A and <strong>Sentinel</strong>-2B before deployment in operations;<br />
○ Specific functional, interface and reliability requirements at system and sub-system<br />
level as appropriate to ensure conflict-free <strong>Sentinel</strong>-2A and <strong>Sentinel</strong>-2B mission<br />
dataflows within the <strong>PDGS</strong>;<br />
○ Well-defined operational procedures dedicated to this phase-in scenario, validated and<br />
rehearsed initially as part of the pre-<strong>Sentinel</strong>-2A launch <strong>PDGS</strong> IV&V activity.<br />
4.6.5 EDRS PHASE-IN<br />
The launch of the EDRS piggyback payload is currently planned in the 2013 timeframe,<br />
hence in the same timeframe as the <strong>Sentinel</strong>-2A launch and start of operations. At this stage,<br />
it is however not foreseen to commission <strong>Sentinel</strong>-2A together with EDRS within the short<br />
time allocated for commissioning. Hence, unless EDRS is launched and commissioned wellbefore<br />
<strong>Sentinel</strong>-2, the approach described here foresees as general case an EDRS<br />
operational phase-in while <strong>Sentinel</strong>-2A is already in operations.<br />
The phase-in of EDRS imposes at term a drastic change to the mission operation scenario<br />
due to the reshaping of the CGS network required from the strict X-Band scenario. It is hence<br />
expected that a commissioning period of <strong>Sentinel</strong>-2 with EDRS will be required in parallel to<br />
the <strong>Sentinel</strong>-2A operational service before this change is effectively carried out.<br />
This paragraph describes the resulting two-step phase-in approach.<br />
4.6.5.1 Commissioning of EDRS Capabilities with <strong>Sentinel</strong>-2<br />
As described in 3.7.2, the <strong>Sentinel</strong>-2 <strong>PDGS</strong> foresees the use of EDRS capabilities at three<br />
levels, being the data-relay, data repatriation and data-dissemination. As the latter is<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>.