Mauro Pecchioli, ESA/ESOCJuan María Carranza, ESA/ESTEC

Presentation to GSAWMarch 2013

The Main Concepts of the European Ground Systems – Common Core (EGS-CC)

1

© 2013 by esa. Published by The Aerospace Corporation with permission.

Background

• Within Europe, different monitoring and control systems are used by different organisations– Some of them common to Mission Operations and Spacecraft

Assembly, Integration and Testing (AIT), some specific– Often multiple systems are used even within the same mission

by different companies or at different levels (e.g. payload/system) or in different phases

– Little synergy across missions and mission phases– Difficult to exchange data between various stakeholders

• Many of the existing systems have reached or are reaching their end of life– Become excessively complex with time– Use old software technologies and hardware platforms– Are difficult to maintain and modernise

2

Objectives

• The EGS-CC Initiative aims at developing a common European M&C infrastructure enabling:– Seamless transition from spacecraft Assembly, Integration and

Testing to Mission Operations– Overall cost reductions by sharing development, sustaining and

maintenance of a single infrastructure– A reduction in the cost and risk associated to the implementation

of space projects– The modernization of legacy Electrical Ground Support

Equipment (EGSE) and Mission Control Systems (MCS) – The exchange of ancillary implementations across organizations

3

Stakeholders• EGS-CC is a collaboration of European large system

integrators and space agencies to develop a common core– Astrium Satellites– Astrium Space Transportation– CNES– DLR– ESA ESOC– ESA ESTEC– OHB System– Thales Alenia France– Thales Alenia Italy

• Initiative considered strategic by all parties

4

Collaboration Agreements• Memorandum of Understanding between the EGS-CC partners• Collaboration Agreement (legally binding) being finalised and signed• Development of the EGS-CC in open competition according to ESA

contract conditions and processes• Adoption of the EGS-CC for institutional missions and then for

commercial missions after successful operational validation in institutional missions

• Active stakeholders involvement at two levels:– Steering Board, owning the responsibility of defining and

managing the implementation of policy related aspects (e.g. funding, procurement, evolution, licensing)

– System Engineering Team, acting as a technical coordination body managing the definition and all technical aspects of the system

5

Governance

6

Steering Board

System Engineering Team

Phase X Industrial Consortium

Stakeholder

Stakeholder

.

.

.

Stakeholder

SET Leader

TO

ContributingActivities

(e.g. demonstrators)

TO

Main System Features

• Scope of the EGS-CC system features is very ambitious

– Support of all mission types and phases

– Open, component based, service oriented architecture– Generic and extensible functionality– High performance and scalability

– Layered implementation– Clear separation between generic M&C functions (kernel) and

specific features of the controlled system (adaptation layer)– Binary compatibility

– Standardised interfaces (as far as possible…)– Technology isolation (as far as possible…)– Long term maintainability

7

8

Top Level Decomposition

Kernel

ReferenceImplementation

ReferenceTest Facility

Legenda

8

Architectural Layers

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layer

Kernel LayerKernel Layer

Reference Implementation Layer

Reference Implementation Layer

Reference Test Facility Layer

Reference Test Facility Layer

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layer

Kernel LayerKernel

Reference Implementation Layer

Reference Implementation

Reference Test Facility Layer

Reference Test Facility

Legenda

9

Architectural Layers

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layer

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layerKernel:It cannot be modifiedBinary compatibility

10

Architectural Layers

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layer

Component management layerComponent management layer

Application support layerApplication support layer

Processing layerProcessing layer

M&C KernelM&C Kernel

Service layerService layer

Adaptation layerAdaptation layer

Presentation layerPresentation layer

Data layerData layer

Extension layerExtension layer

External systems layerExternal systems layer Reference Implementations:May be replaced by user’s own implementation

11

Kernel Functional Scope• Application support layer

– Run-time (component) framework– System management and administration– Access control (security)– Time synchronisation– Data archiving

• Monitoring and Control components– Monitoring and Control Model– Control activities validation, scheduling, execution and

verification– Commanding (control of the controlled system)– Procedures execution– Reporting data (parameters) processing– Event processing– Support of live, playback, retrieval and replay processing modes

12

Reference Implementations Functional Scope• Adaptation layer

– TM/TC Data I/F handlers (based on CCSDS SLE)– Monitoring and control adapters (e.g. TM/TC receiver/releaser, SCOE I/F

Protocols)– Modelling of M&C services of the controlled system (based on ECSS PUS)– Space/Ground time correlation

• User applications– User desktop– User defined displays (plots, synoptic, alphanumeric)– M&C applications (control stacks, history logs, alarm summary display)– System (administration and monitoring) displays– M&C Model browser (navigation tree)

• Off-line tools– Preparation tools– Basic post-processing and reporting

• External interfaces– Tailoring/configuration/archive data import/export– M&C services (based on CCSDS MO)– Many others (a long list…)

13

The Monitoring and Control Model• Functional core of the system• Provides capability to model the complete space system from

a monitoring and control standpoint, based on the Space System Model concept of ECSS E-70-31

• Acts as an abstraction layer for monitoring and control operations (through a hierarchy of System Elements)

• Encapsulates the main monitoring and control functions (e.g. parameter processor, activities handler, events processor)

• Provides access to all data of M&C relevance (static definitions and dynamic state)

• Interacts with the engineering data archive to store all generated data of operational relevance for later retrieval/replay

• Supports the provision of M&C services to external components

14

15

Hierarchical M&C Model

MCMProduct

SpaceSegment

GroundSegment

Spacecraft

GroundSupport

Equipment

M&CSystem

OBDH

AOCS

Activity

Event

Reporting Data

Gyro2

Gyro1

Legend

System Element

SpaceSystem

SpaceSegment

GroundSegment

Spacecraft

GroundSupport

Equipment

M&CSystem

OBDH

AOCS

Activity

Event

Reporting Data

Gyro2

Gyro1

Legend

M&C Element

15

16

MCM Data Access LayerM&C Database

MCM

M&

C D

ata

Acc

ess

Laye

r

Data Archive

OutputProcessed Data

MCM Processor

Source Data

MCMState

Monitor Reporting Data, Initiate Activities, etc

MCM

16

Data Processing Concept

Processed DataArchive

(MCM State)

MCM Input Processor

Source DataArchive

(Raw data)

MC

M A

ccess layer

MCMState

Dynamic M&C Model

ParameterProcessor

EventProcessor

ActivityHandler

raw monitoring data

Raw Data Receiver

Raw data parameterextraction

Kernel Application

EGS-CCApplication

Source monitoring data

Source monitoringdata

liveStore live and deferred raw data

replayView raw data

Source DataArchive

(Internal data)

Source monitoring data (replay)

Legenda

Kernel

ReferenceImplementation

17

Data Processing Concept - LIVE

Processed DataArchive

(MCM State)

MCM Input Processor

Source DataArchive

(Raw data)

MC

M A

ccess layer

MCMState

Dynamic M&C Model

ParameterProcessor

EventProcessor

ActivityHandler

Raw monitoring data

Raw Data Receiver

Raw data parameterextraction

Kernel Application

EGS-CCApplication

Source monitoring data

Source monitoringdata

liveStore raw data

Source DataArchive

(Internal data)

Legenda

Kernel

ReferenceImplementation

18

Data Processing Concept - REPLAY

Processed DataArchive

(MCM State)

MCM Input Processor

Source DataArchive

(Raw and internal data)

MC

M A

ccess layer

MCMState

Dynamic M&C Model

ParameterProcessor

EventProcessor

ActivityHandler

Raw data parameterextraction

Source monitoring data

replay

Legenda

Kernel

ReferenceImplementation

19

Data Processing Concept - RETRIEVAL

Processed DataArchive

(MCM State)

Source DataArchive

(Raw data)

MC

M A

ccess layer

MCMState

Dynamic M&C Model

View raw data

Legenda

Kernel

ReferenceImplementation

20

System Integration Concept

Component Run-Time Platform

EGSImplementation

Component

ImplementationUnits

EGS-CC CompositeComponent

21

Kernel

ReferenceImplementation

Test Facility

Legenda

System Integration Concept

EGSImplementation

Component

Component Run-Time Platform

promote

promote

EGSImplementation

Component

ImplementationUnits

EGS-CC CompositeComponent

EGS-CC Composite

Component

EGS-CC Service Composite

22

Kernel

ReferenceImplementation

Test Facility

Legenda

System Integration Concept

EGSImplementation

Component

Service Integration Platform (ESB)

Client App

Component Run-Time Platform

promote

promote

External System

WS Binding

WS Adaptor

EGSImplementation

Component

ImplementationUnits

EGS-CC CompositeComponent

Binding

Specific Adaptor (e.g. CORBA)

EGS-CC Composite

Component

EGS-CC Service Composite

Kernel

ReferenceImplementation

Test Facility

Legenda

23

System of Systems Approaches

• Independent EGS-CC System Instances

• Master / Child setup

• Merged EGS-CC System Instances

24

Technology Selection Process

• Significant use of 3rd party technologies/products but trying to avoid invasive dependencies

• Precise/severe technology selection criteria/constraints have been identified

• Areas where re-use of 3rd party technologies is expected identified (technology domains)

• Potential candidates for each domain identified• Linux (+ Windows for the user front-end) and Java selected as basic

technologies• Final selection of the other technologies/products is taking place as

part of the Technology Assessment activity taking place in Phase B• Aim is to define the best fit of technologies meeting the EGS-CC

needs (and not necessarily the best selection for each individual domain)

25

(Run-time) Technology Domains

• Component Framework• Service Integration Platform• Communication and Data

Distribution• System Run-Time Management• Logging• Security

• File Management• Data Persistence• Data Archiving• Data Modeling and Tooling

• User Interface• User Defined Displays• Post Processing &

Reporting

• Scripting• Procedures Language• Expression Language

26

Status and Plans

• Phase A has been recently completed – outputs include– Domain analysis, Use cases, User (functional and non-

functional) requirements, glossary, system concepts, conceptual architecture, external interfaces identification, preliminary technology assessment

• Phase B just started, including industrial support for:– Software Requirements Engineering and Architectural Design– Technological Proof of Concept

• Phase C/D expected to start in 2014– based on an incremental/iterative approach– continuous integration and validation of main deliverables in the

target environments (Large System Integrators and Agencies)• Operational validation through pilot projects for EGSE and MCS

applications

27

Conclusions• The EGS-CC initiative is in its early phases

• Strong stakeholders commitment

• Objectives are very ambitious but feasible

• The expected benefits justify the commitment and associated investments

• A phased approach to design and development has been adopted

• System definition (Phase A) completed

• System design (Phase B) just started

• First pilot projects expected to materialise in the 2015-2016 time horizon.

28

Thank you for your attention

29

Bonus Slides

30

Use/adoption of product standards

• TM/TC protocols (ECSS-E-ST-50-03 and 04) for packet based missions• PUS (ECSS-E-ST-70-41) for missions implementing those services• On-board control procedures (ECSS-E-ST-70-01)• M&C data definitions (ECSS-E-ST-70-31)• Procedures languages requirements (ECSS-E-ST-70-32) • Standards for exchange of information like TM/TC Data definitions (e.g.

XTCE)• Standards related to services to be used or offered: MAL (CCSDS 521.0-B)

and SLE (CCSDS 91x)• Other standards relevant to the different types of subsystems with which

EGS-CC will interface (e.g. MIL bus standards)• Technology standards (methods and tools associated to the chosen

technologies) for areas like:– Communications frameworks– Components/service frameworks– Data models

31

32

MCM Definition and Storage

ECSSE‐ST‐70‐31C

SSM

M&C Database Data Archive

MCMMCM Statetime

SE, Activities,Events, 

Reporting Data

stores stores

defined by Run‐time statusOf MCM

32

33

Monitoring Overview

MC

M A

cces

s La

yer

M&C Model

Reporting DataExtraction

ControlledSystem

e.g. TMframes

ProcessedData Archive

Mon

itorin

gSe

rvic

e

Anal

ysis

&R

epor

ting

Mon

itorin

gD

ispl

ays

MCMDefinitions

DataReception

e.g. TMpackets

Source DataArchive Raw data

(e.g. TM frames/packets)

Parameterprocessing

Parameterbaseddata

Monitoringdata

Monitoring dataMonitoring dataobjects definition

Monitoringdata

Reporting Data

Definitions

e.g. TM packetsdefinitionM&C Database

Mon

itorin

gAp

plic

atio

ns MCMState

Monitoringdata

Raw data

Replayeddata

33

34

Control Operations Overview

MC

M A

cces

s La

yer

M&C Model

S/CTCs

ProcessedData Archive

Con

trol

Ser

vice

Pla

nnin

g

Con

trol

Sta

ck a

pp.

MCMDefinition

Commandsencoding &transmission

Commands

Source DataArchive Raw data

Activityprocessing

Controlactivities

Control activitiesActivity

objects definition

Controlactivities

Controlrequests

GSEGroundCommands

SystemFunctions

ProceduresExecution

Functions

Procedures

Controlactivities

CommandDefinitions

TC packetsdefinitionM&C Database

MCMState

Con

trol

App

licat

ions

Controlactivities

ScriptEngineScripts

ActivityScheduling

34

35

M&C Components Conceptual Architecture composite structure M&C Components

«Service»M&CService

«Kernel»M&C Serv ice

«Service»M&CService

«Provision»MCM Access

«Provision»Reporting DataUpdate

«Provision»ActivitiesUpdate

«Provision»EventUpdate

«Kernel»MCM

«Provision»MCM Access

«Provision»Reporting DataUpdate

«Provision»ActivitiesUpdate

«Provision»EventUpdate

«Provision»DatabaseDefinition

«Provision»DatabaseImport/Update

«Kernel»Runtime Database

«Provision»DatabaseDefinition

«Provision»DatabaseImport/Update

«Provision»ProcessedData Storage

«Kernel»Data Managers::Processed Data

Archiv e

«Provision»ProcessedData Storage

«Provision»ProcedureExecution

«Kernel»Procedure Execution

«Provision»ProcedureExecution

«Provision»FunctionExecution

«Kernel»System Functions

«Provision»FunctionExecution

«Provision»ScriptExecution

«Kernel»System Runtime

Management::Script Engine

«Provision»ScriptExecution

«ReferenceImplementation»MCM Browser Display

«ReferenceImplementation»Adapters::TM Extraction

«ReferenceImplementation»Adapters::TC Transmission

«Provision»TC PacketEncoding

«ReferenceImplementation»Adapters::TC Packet Encoding

«Provision»TC PacketEncoding

«Kernel»System::Component

«ReferenceImplementation»System::Component

«ReferenceTestFacility»System::Component

«Provision»DynamicConfiguration

«Kernel»System Configuration::System Configuration

Processor

«Provision»DynamicConfiguration

M&C Components

«Provision»DataStreaming

«Kernel»Data Managers::Data

Streaming «Provision»DataStreaming

«ReferenceImplementation»Adapters::TM Reports Handling

«ReferenceTestFacili ty»External Systems::Preparation Tools

35

EGS-CC Data Model

Conceptual Data Model

Product Structure

Engineering Category Definition

Monitoring & Control Model

Monitoring & Control Data

Func. Electr. Architecture Procedure Data Monitoring &

Ctrl Validation

Display Data ArchiveOperational Modes

Engineering Property Definition

36

Computer 1 Computer 2

37

EGS-CC System Deployment

EGS-CCImplementation

Component

EGS-CCImplementation

Component

EGS-CCImplementationComponent

A = 10B = 3

EGS-CCCompositeComponent

ProxyImplementation

Component

EGS-CCComposite

Component

EGS-CC Service Composite

Service Binding = JMS Binding

DeploymentPlan

deploy

Process BProcess A

deploy

Process C

deploy

Kernel

ReferenceImplementation

Test Facility

Legend

37