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>ESA</strong> UNCLASSIFIED – For Official Use<br />

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

centres using it. In consequence, it will be also checked that all <strong>PDGS</strong> centres are<br />

using same set of reference mission data.<br />

○ Archive Performance<br />

This check aims to monitor that all generated production is properly archived within the<br />

<strong>PDGS</strong>. <strong>PDGS</strong> generation reports and archive reports will be cross-checked to detect<br />

any inconsistency and highlight any missing product in the <strong>PDGS</strong> archive.<br />

○ Data Accessibility Performance<br />

This check aims to monitor the <strong>PDGS</strong> Data accessibility performance. The <strong>PDGS</strong> will<br />

verify that all archived products are available to the users through the Data Access<br />

function. This is mainly a cross-check comparison between the <strong>PDGS</strong> archive<br />

inventory with the data collections catalogue available to the users.<br />

Typical access statistics are generated (typically on a monthly basis) per data type and<br />

provides comprehensive statistics qualified by user base origin, sentinel-2 spacecraft,<br />

geographical zone (e.g. continents), data-age, retrieval latency, etc as appropriate and<br />

providing compound figures on the volumes downloaded (supported by the MMUS<br />

datawarehouse capabilities).<br />

○ End-to-End Performance<br />

This check aims at measure the <strong>PDGS</strong> end-to-end performance providing a complete<br />

and comprehensive view at system level over the global production and detected<br />

malfunctions.<br />

The reports can be generated automatically according to a defined schedule (e.g. daily,<br />

monthly) or on-demand by the MPA operator.<br />

The MPA reports are systematically used to summarise the end-to-end mission performance<br />

over all the <strong>PDGS</strong> subsystems. They are provided routinely to the POM for assessment as<br />

part of nominal reporting (cf. mission support services defined in section 4.10.3.2).<br />

6.16.6.3 Service Performance Reports to the CDS/CQC<br />

This scenario stands for the autonomous generation and supply of the Service Performance<br />

Reports to the CDS/CQC as defined in section 4.10.1.4.<br />

6.17 Monitoring & Control (M&C) Operations<br />

6.17.1 PRINCIPLES<br />

6.17.1.1 M&C Centre Scope<br />

The <strong>PDGS</strong> Monitoring & Control function will be responsible for ensuring that all the available<br />

resources (i.e. hardware, software and network) required by the <strong>PDGS</strong> for its nominal<br />

operations are available, ready and running under the expected conditions. The Monitoring &<br />

Control function will allow detecting anomalies that may involve working on problems in the<br />

functional chain or help finding the cause of any malfunction of any <strong>PDGS</strong> function.<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!