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

3) Control viewing activities through M&C control panel. The M&C function displays the<br />

monitoring information in a comprehensive manner to highlight any problem or<br />

environment deviation from expected;<br />

4) Alarms notification. The M&C function notifies such alarm via different mechanisms<br />

(e.g. electronic mail, SMS, etc) according to the configuration;<br />

5) Reporting activities. The M&C function produces reports according to the detected<br />

anomalies. In addition it produces cyclic reports on the quality of service of the<br />

monitored elements including specific information on the different <strong>PDGS</strong> functions<br />

availability.<br />

Some use cases are presented according to this operation scenario:<br />

○ Cyclic reports are generated to verify the working availability of every <strong>PDGS</strong> function<br />

allowing the calculation of different QoS parameters (e.g. MTBF);<br />

○ Network connectivity to a given interface is unavailable (e.g. towards the FOS). The<br />

M&C function control panel highlights such situation for a prompt intervention and<br />

avoid operations problems.<br />

6.17.3.4 Logs Visualisation<br />

This scenario stands for the operator-driven log visualisation activities. Accordingly the<br />

operator will be able to filter and visualise the desired information.<br />

The M&C function is the hub of all the logging activity on every centre. Accordingly the M&C<br />

function provides the required logging services to other <strong>PDGS</strong> functions (i.e. via client logs<br />

management library) and therefore they will be able to provide their logs to the M&C function.<br />

There will be a centralized access point to all the logs on every centre and as such,<br />

minimising operations effort. The operator will acknowledge the log messages when required<br />

(e.g. according to configured severity).<br />

The following steps are identified for this operation scenario:<br />

1) The <strong>PDGS</strong> functions by making use of M&C log library sends their log messages. The<br />

log messages sent to the M&C function are configurable by severity on the producer<br />

side to avoid flooding the M&C log console;<br />

2) The M&C function gathers and displays log messages in a comprehensive human<br />

friendly way;<br />

3) The operator when required acknowledges the log messages displayed on the console<br />

(i.e. alarms). The M&C function provides filtering and searching capabilities to reduce<br />

operator effort.<br />

This operation scenario supports many other <strong>PDGS</strong> operation scenarios as most of the<br />

activities performed are logged accordingly. During routine operations it is expected the<br />

operator to only perform log visualisation activities in response to anomalies and as such, the<br />

M&C function must provide the adequate filtering and searching capabilities.<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!