OPS Forum EGOS User Desktop 02.11.2007

EGOS User Desktop

The Desktop for the ESOC Ground Data SystemsM. di Giulio, Y.Doat (OPS-GI)ESOC, 02 November 2007

M. Di Giulio – OPS-G Forum 02 November 2007 Slide 2@ Copyright European Space Agency, 2007

Presentation Overview

• Introduction• Purpose of EGOS and the EGOS applications • Objectives of the EGOS User Desktop • EUD features and EUD Architecture• EUD deployment scenarios• EUD technology • Eclipse features• The EUD Launcher• Project Status• Future outlook: the Mimic capability


Introduction

• The main systems of the ground segment infrastructure (e.g. SCOS-2000, SIMSAT, Station Computer, Ground Station’s Systems, etc) include a variety of Man-Machine interfaces.

• Currently, each individual product has its own specialised approach.

• Different technologies, different look-and-feel.


EGOS Purpose

Some background information. What is EGOS ?• common approach to data systems infrastructure

development.• common set of services used by all ESA Ground Segment

applications.• distributed development of a suite of commonly usable

new / adaptive middleware software tools• Reduction of development costs on infrastructure and

mission specific developments.• Enables interoperability across systems.• Enables common software maintenance policy and a long-

term maintainability of the Ground Data Systems.• Reduces the familiarization efforts


EGOS elements and the EUD role


EGOS User Desktop OBJECTIVES

• To provide the EGOS applications with a standard interface to the operator, that is decoupled from the base “underlying” system’s processing layer

• Achieving a harmonised implementation of the MMI capabilities (display of data, user’s inputs etc).

• To standardise the look & feel of all EGOS applications.

• To provide the standard interface for interaction with the EGOS framework.


EUD Features

• The EUD provides the Presentation layer to the EGOS applications.

• The initial EUD implementation foresees communication with the EGOS System via CORBA messages: this allows the presentation layer to be present locally or remotely with seamless interfacing.

• The EUD architecture allows also different communications technologies (e.g. http-based protocols)

• The data contents of the displays is done via text configuration files (XML).


EUD Software Architecture

EUD consists of:

• EUD Framework : provides generic runtime environment for EUD displays, and the means to interface the any EGOS system

• Displays library: a set of display plug-ins which provide the specific GUIs (e.g. ANDs, messages displays etc).


EGOS UD Top-level architecture

CORE COMPONENTSEGOS SYSTEM

VIEWS EDITORS

BINDER EGOS LIBRARY

SERVICE PROXY HOME

ECLIPSEPLATFORM

EGOSUD CORE

EGOS USER DESKTOP

Pre

sent

atio

n la

yer

Pro

cess

ing

laye

r

EUD LIBRARY

Framework


Service Proxy Home

Within the Framework, the communications with the underlying system are managed via the Service Proxy Home.

• The Service Proxy Home abstracts the communication with the processing layer.

• It provides the EUD Displays with the necessary logic for accessing the EGOS services.


ServiceProxys and EGOS services

EGOSUD CORE

Ser

vice

Pro

xies

Pro

cess

ing

laye

r

Event DistributorService Proxy

EGOS Event Distributor

API (Client)

EGOS Config.Access

API(Client)

EGOS Session Manager

API(Client)

EGOS ParameterDistributorAPI(Client)

EGOS MessagesDistributorAPI(Client)

EGOS System Control

API(Client)

Configuration Access

Service Proxy

Session ManagerService Proxy

Parameter Distributor

Service Proxy

Messages Distributor

Service Proxy

System ControlService Proxy

EG

OS

S

ervi

ceP

roxi

es A

PI

EGOS Event Distributor

Service

EGOS Config.AccessService

EGOS Session ManagerService

EGOS ParameterDistributor

Service

EGOS MessagesDistributor

Service

EGOS System Control Service

EU

DC

ore


EUD deployment scenarios

Diverse deployment scenarios:

• Communication via CORBA messages: the EUD can run either locally or remotely with respect to the busyness logic of the EGOS system

• Communications via http protocol: the EGOS system is remotely distributed



EGOS SYSTEM

Processing LayerEUD Application

CORBA EGOS System in a standalone environment

EGOS System in a distributed environment

EGOS SYSTEM CLIENT “A”

EUD ApplicationProcessing Layer

(SERVER)

EGOS SYSTEM SERVER “A”

CORBA



EGOS System remote distributed environment



(SERVER)


CORBA

EGOS SYSTEMREMOTE CLIENT

JAVA WEB

START

Web Server

HTTP DOWNLOAD

DEPLOYMENT



(SERVER)


HTTP

EGOS SYSTEMREMOTE CLIENT

JAVA WEB

START

Web Server

HTTP DOWNLOAD

DEPLOYMENT


TECHNOLOGY

• The EUD is based on the Eclipse platform

• Java technology for platform-independent applications


EUD Technology

Eclipse features:

• open-source, platform-independent, written in Java, for building "rich-client” applications.

• It runs on multiple operating systems, so it is adaptable to different operational requirements within the ESOC ground segment.

• native look and feel on major platforms (e.g. Linux, Solaris and Windows) thanks to the SWT graphic library, standardized component model, extensibility and integrated update mechanism.

• Allows easy tailoring and extension of the basic platform, by means of plug-in (e.g. in the EUD the Displays and the Service Proxy, according to the operational requirements).


Eclipse Plug-in Architecture

• Eclipse has an open architecture based on plug-ins which are built on a platform runtime

• The plug-ins are layered through extensions to lower-level plug-ins providing new functionalities for the underlying plug-ins.

• The plug-in is the mechanism of extensibility in the Eclipse platform. New plug-ins can add new functionalities to existing plug-ins.

• The plug-in is the smallest unit of the Eclipse platform function that can be developed and delivered separately.

• The platform runtime core implements the runtime engine that starts the platform base and dynamically discovers and runs the plug-ins.

The following figure illustrates the different plug-ins layers


Eclipse Plug-ins interactions

P1

P2

P3

P4

Exten

sion

Poin

t

ExtensionsHost

extensionP1

P2

P3

P4

Exten

sion

Poin

t

ExtensionsHost

extension

Platform (org.eclipse.core.runtime)

P1P2 P3 P4

Platform (org.eclipse.core.runtime)

P1P2 P3 P4

P1

P2

P3

P4


Eclipse’s Workbench, Perspectives and Views

• Workbench – it is a plug-in which implements the user interface and defines a number of extension points that supports other plug-ins contributions

• Perspectives – A perspective is a set of views or editors disposed in the workbench window. It defines the initial visibility, the layout and the action visibility

• Views and Editors – are the draggable parts that make up the bulk of a workbench window’s contents, through the perspectives. They are visual elements that work as containers of widgets (buttons, tables, etc)


EUD Displays

• The initial EUD design foresees a basic set of Displays (Views): ANDs, Message Display, Navigation Tree, Task Display etc).

• In the next project phase, more sophisticated or system-specific displays will be developed (scroll display, history display, mimic capability) etc.

• The new Displays will be plugged-in


Examples of EUD applications structure

SCOS SIMSAT

V1 V4V2 V3 V1

Workbenches

Views or Editors

User Management

Commanding ChainPerspectives User Management Other

Host

Extension

MonitoringChain

V5


EUD preliminary look and feel


The EUD Launcher

• The EUD Launcher: specific tailoring of the EUD framework, for controlling and monitoring multiple EGOS systems from a centralised position;

• Start-up and Shut-down EGOS systems;

• Monitor and Control EGOS systems, via a set of dedicated displays.


The EUD Launcher


Project Status

EUD Phase 1 (in 2006) :– SW Requirements Specification- SW Req. Review;– SW Design Document – PDR;– Prototype.

EUD Phase 2 (in 2007-2008):– Consolidation of Phase 1 results;– Delta -SW Design Document – Delta PDR;– SW Detailed Design and Coding;– FAT and first SW delivery by June 2008;– Integration into SIMSAT for validation.


Functionality in Preparation

• A comprehensive Mimic capability is under definition, and will be added to the basic EUD

• It will be developed based on Eclipse native tools (e.g. GEF)

• It will be plugged-in to the basic EUD project as any other component


Examples of mimic needs (from the ESA Ground Station)


Examples of mimic needs (from the ESA Ground Station)

FEC Console screen


EGOS User Desktop

Thank you for your attention !

Questions ?