Loading...
 
ESA > Join & Share > AMOC
Print

AMOC

Introduction and Objectives

The main purpose of the AMOC system is to automate the monitoring and control tasks carried out in the PDGS and data processing centres facilities in general. As emerging from the technical analysis, there is a gap in the availability of the software that would cover the expectations of the target facilities. The main issues relate to:

  • Reusability of the software for different data centres or even for different processing scenarios (e.g. ESA missions) within the same facility (e.g. PDGS);
  • Feature addition or customization requires a considerable effort and cost for conceptually similar functionalities;
  • Insufficient level of automation, forcing a manual approach on M&C activities.

The developed prototype aims at fulfilling the gap and solve the issues mentioned above.

Expected Results

The main results is the evolution of the current Horus system concept and the modification of the existing execution model, driven by the new approach
to the monitoring activities.
The current Horus system is a request-response system with the user being the principal source of requests. This means that the response containing results of data processing has to be formatted and delivered to user in the expected format, and in the shortest time possible. This execution model creates a strong dependency between the data processing, visualisation and dissemination due to its performance requirements constrains. It works well for its purpose and it gives a very high degree of freedom to the user in terms of online reports runtime configuration. However, this requires from
the user to actively use the Horus interface and provide the system with the specific operation request in order to retrieve the specific monitoring information (e.g. missing products).
The automation of monitoring operations changes this model considerably. It requires from the system to be able to trigger the operations by itself, whereas the user can remain in standby, until a specific monitoring piece of data is delivered to him. As a consequence, an additional decision-making, triggering and execution logic has to be added to the current system, together with an upgrade of the system configuration capabilities. It is a major change to the system architecture and it affects almost all system components.

Schedule

MilestoneDate Place Description
KO2015-12-01ESRINKO
M12016-06-24S&TTR1
M22016-11-25ESRINTR2
M32017-06-08S&TSRR/PDR
M52018-05-31S&TAR
M62018-06-30ESRINFP

Contractor

Science & Technology Corporation (S&T)


Contributors to this page: Michele Iapaolo .

Page last modified on Tuesday 30 of October 2018 11:21:44 CET by Michele Iapaolo.