- Conference Article
7
- 10.2514/6.2006-5691
EGOS Architecture and the Impact on Existing ESOC Ground Data Systems
- Jun 19, 2006
- Yves Doat + 4 more +4
The European Space Operations Centre (ESOC) is currently carrying out an ambitious program to standardize the infrastructure used throughout its ground segments in an effort to improve the reliability, cost effectiveness and interoperability. The end product of this program will be the ESA Ground Operation System (EGOS). This paper summarizes the program rational, its goals, the architecture, development approach and current status. I. Introduction A. Overview SOC is responsible for the provision of ground segments for the operation and control of many ESA missions. The scope of the ground segment encompasses the elements required on ground to provide the requisite monitoring and control capabilities. This ranges from the groundstations, through the mission control and flight dynamics functionality, to the archiving and distribution of data to the science community and, in some cases, the initial processing of science data. The provision of simulators for training and operations validation purposes is also covered. Many of the systems that are used in the ground segment have been developed in the past using a variety of different technologies and policies, quite often as standalone projects which did not take into account other developments. EGOS is therefore intended to provide a more standardised infrastructure, which encourages systematic reuse and thus reduce development and maintenance costs. The approach adopted is to use well established S/W engineering principles, build on existing systems and experience, use international standards where available and avoid proprietary systems/standards where possible. Initially EGOS is concentrating on the areas of mission control systems, simulators and some of the ground station equipment, in particular the base-band systems and ground station monitoring and control. In the longer term it is envisaged that the scope will be extended to cover satellite electrical ground support equipment (EGSE), flight dynamics and mission planning systems. EGOS must also permit easy expandability, as it is not possible to forecast with certainty future system requirements. The approach adopted in the architecture is one of a service oriented system based on component application development. The service and component architectures represent two views of the system and are therefore not mutually exclusive, but complementary. Within the overall architecture categories of components have been identified. The first of these are the Core components, these provide the essential services and functionality on which the other components are built. Next come the Common components, these provide widely used services such as file archiving, user management etc. The Core and Common components can effectively be thought of as middleware for the ground data systems. The third category, Custom components, consists of the applications that implement the end user needs. These map roughly onto subsystems, e.g. telemetry chain, telecommanding chain, onboard software maintenance system etc. Encapsulating the overall EGOS architecture is the Service Management Framework (SMF). This provides the mechanism through which the underlying systems expose services to external users and systems in a well defined and controlled manner. To avoid unnecessary dependencies between a set of rules has been prepared specifying whether the different categories of components may utilise the services provided by other components categories. * Head of the Ground Station Backend Section, OPS-GIB † Senior Software Engineer, Data System Infrastructure Division, OPS-GI ‡ Head of the Product Maintenance & Support Section, OPS-GIM § Head of the Operation Centre System Infrastructure Section, OPS-GIC ** Head of the Data System Infrastructure Division, OPS-GI
Read more