1. MOIMS Plenary CCSDS Spacecraft Monitoring & Control WG (SM&C) Workshop #02, 10-14 May 2004 Mario Merri, ESA/ESOC, Chairman

2. MOIMS Plenaryp. 2SM&C-WS#02 10-14 May 04 Agenda Status of activity Progress to date White Book: Initial results Outlook Issues and cross-issues

3. MOIMS Plenaryp. 3SM&C-WS#02 10-14 May 04 Membership (May 2004) - A strong team! Mario Merri (ESA) – chairman Roger Thompson (BNSC) - deputy chairman Martin Symonds (BNSC) Brigitte Béhal (CNES) Erwann Poupart (CNES) Harald Hofmann (DLR) Klaus Gnadl (DLR) Alessandro Ercolani (ESA, PoC) Michael Schmidt (ESA, PoC) Ivan Dankiewicz (ESA/SciSys) Sam Cooper (ESA/SciSys) Takahiro Yamada (Jaxa) Amalaye Oyake (JPL) Ashton Vaughs (JPL) Peter Shames (JPL) Donald C. Lokerson (NASA/GSFC)      = has confirmed attendance to this CCSDS workshop    

4. MOIMS Plenaryp. 4SM&C-WS#02 10-14 May 04 Progress to Date High interaction within WG (9 telecons) Initiated cross-fertilisation with SOIS  2 telecons  Produced Memorandum of Understanding Worked on White Book  4 drafts

5. MOIMS Plenaryp. 5SM&C-WS#02 10-14 May 04 WB - High Level Goal Standardisation of interfaces for Spacecraft M&C  Reduced cost of Flight Components and Ground Segment Infrastructure  Enable “plug and play” Architecture with components from different Agencies, Systems and Suppliers Enable Mission Economies through:  Interoperability with partner systems and infrastructure  Risk Reduction through re-use of systems and operational concepts: increased reliability  Facilitation of Generic Software Infrastructure (On-board and Ground-based)  Application of a common M&C Approach throughout all mission phases  Application of a common M&C Approach to other domains (Ground Stations, Control and Test Centres, etc.)

6. MOIMS Plenaryp. 6SM&C-WS#02 10-14 May 04 WB - Scope Operational concept  definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of both ground and space segments Core Set of Services  definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Product Management, Flight Dynamics, Mission Planning, Automation, and Performance Evaluation Application-layer information  definition of the standard information set to be exchanged for SM&C purposes

7. MOIMS Plenaryp. 7SM&C-WS#02 10-14 May 04 WB - Objectives Define a common SM&C operational concept Define a reference on-board and on ground architecture in close coordination with other CCSDS groups (e.g. SOIS, SEA) Define a standard approach to service specification Define minimum set of ground SM&C kernel functionality Define space-to-ground application-level interface messages Identify standard Mission Control System interfaces with M&C components:  With remote software management  With Mission Planning System  With the Flight Dynamics System

8. MOIMS Plenaryp. 8SM&C-WS#02 10-14 May 04 WB - Schedule Dec 03 Formation of WG 12 Jan 04White Book – draft 0.1 18 Feb 04White Book – draft 0.2 5 Apr 04White Book – draft 0.3 30 Apr 04White Book – draft 0.4 May 04White Book – Issue 1.0 TBDProduction of Blue books

9. MOIMS Plenaryp. 9SM&C-WS#02 10-14 May 04 WB - Service Based Architecture Defines the interface as a “contract” Consumer (client) unaware of providers implementation Popular with distributed and web based systems

10. MOIMS Plenaryp. 10SM&C-WS#02 10-14 May 04 WB - Layered Architecture Helps modularise system Supports reuse of components Can only invoke lower layers Replacement of layers is possible if combined with services

11. MOIMS Plenaryp. 11SM&C-WS#02 10-14 May 04 WB - Space System Context Uses RASDS methodology Defines reference system Defines operational context Outlines clients of the system Outlines operational areas of the system Highlight “interoperability” interfaces

12. MOIMS Plenaryp. 12SM&C-WS#02 10-14 May 04 WB - Functional View Defines areas of functionality  Taken from the operational context Defines interactions between functional areas Leads to service identification

13. MOIMS Plenaryp. 13SM&C-WS#02 10-14 May 04 WB - List of Functional Areas M&CCore Monitor and Control functional area AutomationConcerned with control and management of the automation task Schedule ExecutionComponent responsible for executing the schedule possibly generated by the planning component PlanningComponent responsible for the planning of future events in the system Software Management Onboard and also ground software version control, patching and release Flight DynamicsOrbit vector determination, event schedule production etc TimeTime correlation LocationResponsibilities include ranging, tracking, and onboard position determination AnalysisTrending and analysis Data Product Management Control, management, persistence and transfer of the data product produced by the other components

14. MOIMS Plenaryp. 14SM&C-WS#02 10-14 May 04 WB - Example: Modularity and Flexibility

15. MOIMS Plenaryp. 15SM&C-WS#02 10-14 May 04 WB - Information flow Key task is to identify the information objects Elaboration of the services will identify these objects Will also define their attributes

16. MOIMS Plenaryp. 16SM&C-WS#02 10-14 May 04 WB - Service Overview

17. MOIMS Plenaryp. 17SM&C-WS#02 10-14 May 04 WB - List of services M&CCore Monitoring and Control service AutomationActivity automation management SchedulingActivity scheduling InteractionOperator notification and interaction PlanningConstraint and resource planning Flight DynamicsOrbit determination, flight plan generation, and manoeuvre generation TimeTime correlation LocationTracking, ranging, and onboard position determination services Data Product Management File management and transfer, both ground based and onboard Software ManagementSoftware versioning, patching, and release

18. MOIMS Plenaryp. 18SM&C-WS#02 10-14 May 04 WB - Example: Core SM&C

19. MOIMS Plenaryp. 19SM&C-WS#02 10-14 May 04 WB - Example: Core SM&C

20. MOIMS Plenaryp. 20SM&C-WS#02 10-14 May 04 WB - Summary Produce CCSDS White Book  Issue date is May 2004 Analysis of operational context Use of services and layers Identification of services Will lead onto definition of services  In other CCSDS books

21. MOIMS Plenaryp. 21SM&C-WS#02 10-14 May 04 Outlook … The proposed (chairman) goals for the SM&C Montreal Meeting are:  Finalise the WB and pass it to MOIMS AD/CESG as "Final Draft Informational" document (to become Green Book)  Select 2-3 high priority services identified in the WB and propose them as "CCSDS Proposed Standards" to MOIMS AD/CESG together with their schedule and resource profiles  Ratify MOIMS-SOIS MoU and pass it to MOIMS AD/CESG  Finalise agreement between SM&C and OMG SDTF for public review of the XTCE standard. Propose this to MOIMS AD/CESG as a joint CCSDS-OMG project

22. MOIMS Plenaryp. 22SM&C-WS#02 10-14 May 04 Open Points (from last workshop) Absence of NASA/Goddard from WG  Closed with membership of D. Lokerson Relationship with OMG  Closed by CCSDS-OMG agreement Handling of OMG XTCE standard  Hopefully closed – see proposal for joint CCSDS-OMG project Potential effort duplication with OMG Space DTF RFP-2  Hopefully closed – see joint CCSDS-OMG joint session (Wed PM)

23. MOIMS Plenaryp. 23SM&C-WS#02 10-14 May 04 Cross-Issues Coordination with other Areas  SOIS: 2 telecons + MoU  SEA: ensured by key members (PS, TY)  MOIMS/NAV: to be further developed in the context of the draft WB