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

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 223 of 350<br />

5.2.4 SYSTEM CONTROL FUNCTIONS<br />

5.2.4.1 Mission Configuration Control (MCC) Function<br />

5.2.4.1.1 Function Objectives and High-Level Description<br />

The MCC function is responsible for keeping under controlled environment all relevant<br />

mission reference files. MCC function controls critical configuration and essential operations<br />

information to allow a configuration control on critical parameters and resulting operations.<br />

As such, it is in charge of:<br />

○ Keep under a controlled environment all critical configuration parameters and essential<br />

operation reports into a central repository. Comprehensive management of all<br />

essential configuration and operations data over time;<br />

○ Manage the release of mission reference files updates, providing the functionality to<br />

activate (release) a specific system configuration throughout the distributed <strong>PDGS</strong><br />

from a single point. The release and activation implies information delivery to<br />

applicable interfaces in a coordinated manner;<br />

○ File edition capabilities to generate required configuration parameters files (i.e. MCC<br />

function generates some configuration parameters files and others are gathered from<br />

applicable interfaces);<br />

○ Collection of all operation reports derived from configuration gathered from applicable<br />

interfaces. In addition delivery of such operations reports to applicable interfaces in a<br />

coordinated manner (i.e. acknowledged and triggered by the operator) or<br />

autonomously according to configuration (making use of the DC function);<br />

○ Providing query capabilities to the operator on the relevant aspects of the mission<br />

reference files management (e.g. ingestion time, release time, applicability time, etc.);<br />

5.2.4.1.2 Design Drivers and Constraints<br />

The following drivers and constraints are identified:<br />

○ Single point for the <strong>PDGS</strong> relevant parameters configuration management and<br />

release;<br />

○ Usage of the DC function for required data circulation activities;<br />

5.2.4.1.3 Function Interfaces<br />

The following function interfaces are identified for the MCC function:<br />

○ MSI on-ground and on-board configuration gathered from the applicable interfaces<br />

(e.g. NUC tables and GIPP provided by the CNES/CST during the phase-E1 and the<br />

<strong>PDGS</strong>/MPA function during the phase-E2);<br />

○ Operation information and reports gathered from applicable interfaces (e.g. AI function<br />

archive reports);<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!