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

Transcription

1 The Main Concepts of the European Ground Systems Common Core (EGS-CC) Mauro Pecchioli, ESA/ESOC Juan María Carranza, ESA/ESTEC Presentation to GSAW March by esa. Published by The Aerospace Corporation with permission. 1

2 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

3 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

4 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

5 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

6 Governance Steering Board Stakeholder SET Leader System Engineering Team Stakeholder Stakeholder... TO Phase X Industrial Consortium TO Contributing Activities (e.g. demonstrators) 6

7 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 Legenda Reference Test Facility Reference Kernel 8

9 Architectural Layers Presentation layer External systems layer Legenda Service layer Kernel Kernel Layer Reference Layer Adaptation layer Extension layer Reference Test Facility Facility Layer M&C Kernel Processing layer Application support layer Data layer Component management layer 9

10 Architectural Layers Presentation layer Service layer External systems layer Kernel: It cannot be modified Binary compatibility Adaptation layer Extension layer M&C Kernel Processing layer Application support layer Data layer Component management layer 10

11 Architectural Layers Presentation layer Service layer External systems layer Reference s: May be replaced by user s own implementation Adaptation layer Extension layer M&C Kernel Processing layer Application support layer Data layer Component management layer 11

12 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

13 13 Reference s 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 )

14 14 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 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

15 Hierarchical M&C Model OBDH Spacecraft Gyro2 Space Segment AOCS Space MCM System Product Ground Segment Ground Support Equipment Gyro1 Legend M&C System M&C System Element Reporting Data Activity Event 15

16 MCM Data Access Layer M&C Database MCM Monitor Reporting Data, Initiate Activities, etc M&C Data Access Layer MCM State MCM Output Processed Data MCM Processor Source Data 16 Data Archive

17 Data Processing Concept View raw data MCM Access layer Processed Data Archive (MCM State) MCM State Source Data Archive (Raw data) Store live and deferred raw data Dynamic M&C Model Parameter Processor replay Kernel Application raw monitoring data Raw Data Receiver Source monitoring data MCM Input Processor Event Processor Raw data parameter extraction EGS-CC Application Activity Handler Source monitoring data live Legenda Source Data Archive (Internal data) Source monitoring data (replay) Kernel Reference 17

18 Data Processing Concept - LIVE Kernel Application EGS-CC Application MCM Access layer Processed Data Archive (MCM State) MCM State Parameter Processor Source monitoring data MCM Input Processor Event Processor Activity Handler Source Data Archive (Internal data) Dynamic M&C Model Source monitoring data Store raw data Source Data Archive (Raw data) Raw monitoring data Raw Data Receiver Raw data parameter extraction live Legenda Kernel Reference 18

19 Data Processing Concept - REPLAY Processed Data Archive (MCM State) MCM Access layer MCM State Parameter Processor MCM Input Processor Event Processor Activity Handler Dynamic M&C Model Source monitoring data Source Data Archive (Raw and internal data) replay Raw data parameter extraction Legenda Kernel Reference 19

20 Data Processing Concept - RETRIEVAL Processed Data Archive (MCM State) MCM Access layer MCM State Dynamic M&C Model View raw data Source Data Archive (Raw data) Legenda Kernel Reference 20

21 System Integration Concept Legenda Kernel Reference Test Facility EGS-CC Composite Component EGS Component Units 21 Component Run-Time Platform

22 System Integration Concept Legenda Kernel Reference Test Facility promote EGS-CC Service Composite promote EGS-CC Composite Component EGS Component EGS-CC Composite Component Units EGS Component 22 Component Run-Time Platform

23 System Integration Concept External System Service Integration Platform (ESB) Client App Legenda Kernel Reference Test Facility Specific Adaptor (e.g. CORBA) Binding WS Adaptor WS Binding promote EGS-CC Service Composite promote EGS-CC Composite Component EGS Component EGS-CC Composite Component Units EGS Component 23 Component Run-Time Platform

24 System of Systems Approaches Independent EGS-CC System Instances Master / Child setup Merged EGS-CC System Instances 24

25 Technology Selection Process Significant use of 3 rd party technologies/products but trying to avoid invasive dependencies Precise/severe technology selection criteria/constraints have been identified Areas where re-use of 3 rd 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

26 (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

27 Status and Plans Phase A has been recently completed outputs include Domain analysis, Use cases, User (functional and nonfunctional) 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

28 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 time horizon. 28

29 29 Thank you for your attention

30 30 Bonus Slides

31 Use/adoption of product standards TM/TC protocols (ECSS-E-ST 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 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 ECSS E ST 70 31C SSM defined by MCM SE, Activities, Events, Reporting Data Run time status Of MCM MCM State time stores stores M&C Database Data Archive 32

33 Monitoring Overview Processed Data Archive MCM Definitions Reporting Data Definitions Analysis & Reporting Monitoring data Monitoring data objects definition M&C Database e.g. TM packets definition Monitoring data Monitoring Applications Monitoring Service Monitoring Displays Monitoring data MCM Access Layer Monitoring data Parameter processing MCM State M&C Model Parameter based data Reporting Data Extraction e.g. TM packets Data Reception e.g. TM frames Replayed data Controlled System Raw data Source Data Archive Raw data (e.g. TM frames/packets) 33

34 Control Operations Overview Processed Data Archive Control activities Activity objects definition MCM Definition M&C Database Command Definitions TC packets definition Control activities Planning Control Applications Control requests Control Service Control Stack app. Control activities Control activities MCM Access Layer Control activities Activity Scheduling Activity processing MCM State M&C Model Procedures Scripts Functions Commands Commands encoding & transmission Procedures Execution Script Engine System Functions TCs S/C Source Data Archive Raw data Ground Commands GSE 34

35 composite structure M&C Components M&C Components Conceptual Architecture «Kernel» System::Component «Reference» System::Component «ReferenceTestFacility» System::Component «Reference» MCM Browser Display «Kernel» Data Managers::Data Streaming «Kernel» Data Managers:: Processed Data Archiv e «Kernel» System Runtime Management::Script Engine «Provision» Data Streaming «Provision» Processed Data Storage «Kernel» Procedure Execution «Provision» Procedure Execution «Service» M&C Service «Kernel» M&C Service M&C Components «Kernel» MCM «Provision» MCM Access «Kernel» Runtime Database «Provision» Database Import/Update «Provision» Database Definition «Provision» Dynamic Configuration «Kernel» System Configuration:: System Configuration Processor «ReferenceTestFacility» External Systems:: Preparation Tools «Provision» Script Execution «Reference» Adapters::TC Packet Encoding «Kernel» System Functions «Provision» Function Execution «Provision» Activities Update «Provision» Reporting Data Update «Provision» Event Update «Reference» Adapters::TM Extraction «Provision» TC Packet Encoding «Reference» Adapters::TC Transmission «Reference» Adapters::TM Reports Handling 35

36 Conceptual Data Model EGS-CC Data Model Product Structure Func. Electr. Architecture Display Data Monitoring & Control Model Procedure Data Operational Modes Monitoring & Control Data Monitoring & Ctrl Validation Archive Engineering Category Definition Engineering Property Definition 36

37 EGS-CC System Deployment Computer 1 Computer 2 Legend Kernel Process A Process B Process C Reference Test Facility deploy deploy Service Binding = JMS Binding deploy EGS-CC Service Composite EGS-CC Composite Component EGS-CC Composite Component Deployment Plan Proxy Component EGS-CC Component EGS-CC Component EGS-CC Component A = 10 B = 3 37