CCSDS Spacecraft Monitor

1
CCSDSSpacecraft Monitor Control Working
Group(SMC WG)

• SpaceOps 2004

2
Membership

• ESA
• Mario Merri (chairman), Michael Schmidt,
  Alessandro Ercolani
• Ivan Dankiewicz, Sam Cooper
• BNSC
• Roger Thompson (deputy chairman), Martin Symonds
• NASA/JPL
• Amalaye Oyake, Peter Shames
• NASA/GSFC
• Donald Custis Lokerson
• CNES
• Brigitte Béhal, Erwann Poupart
• DLR
• Harald Hofmann
• JAXA
• Takahiro Yamada

3
High Level Goal

• Standardisation of interfaces for Spacecraft MC
• Reduced cost of Flight Components andGround
  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 MC Approach throughout
  all mission phases
• Application of a common MC Approach to other
  domains (Ground Stations, Control and Test
  Centres, etc.)

4
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.
• Set of Application 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 SMC purposes.

5
Objectives

• Define a common SMC operational concept
• Define a reference on-board and on ground
  architecture in close coordination with other
  CCSDS groups (e.g. SOIS, SEA)
• Identify standard Mission Control System
  interfaces with MC components
• with remote software management
• with Mission Planning System
• with the Flight Dynamics System
• Define a standard approach to service
  specification
• Define application-level service access points
• Define SMC Common protocol layer

6
Schedule

• Dec 03 Formation of WG (1st meeting)
• Apr 04 SMC Service Framework (WB draft 0.4)
• Dec 04 Green Book
• advanced concept papers on
• Common SMC Protocol Service
• Core SMC Application Service

7
Service Based Architecture

• Defines the interface as a contract
• Consumer (client) unaware of providers
  implementation
• Popular with distributed and web based systems

8
Service Layering
MOIMS Mission Operations Information Management
Systems SOIS Spacecraft On-Board Interface
Services
9
MOIMS Service Interfaces
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ProviderApplications
Service Access Points
Service Message Protocol
MOIMS
MOIMSApplication Services
MOIMSApplication Services
MOIMS Common Protocol Service
MOIMS Common Protocol Service
SLS, SOIS or Other
CommunicationsService
CommunicationsService
CommunicationsService
CommunicationsService
10
Network Adapters
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ProviderApplications
Service Access Points
Service Message Protocol
MOIMS
MOIMSApplication Services
MOIMSApplication Services
MOIMS Common Protocol Service
MOIMS Common Protocol Service
11
PUS Adapter
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ClientApplications
Service ProviderApplications
Service Access Points
PUS
MOIMS
MOIMSApplication Services (PUS Adapters)
MOIMSApplication Services (PUS Adapters)
SLS
CommunicationsService
CommunicationsService
CommunicationsService
CommunicationsService
Interoperable Interface
12
Space System Context

• Defines reference system
• Defines operational context
• Outlines clients of the system
• Outlines operational areas of the system

13
Functional View

• Uses RASDS methodology
• Defines areas of functionality
• Taken from the operational context
• Defines interactions between functional areas
• Leads to service identification

14
Modularity and Flexibility
15
Information flow

• Key task is to identify the information objects
• Elaboration of the services will identify these
  objects
• Will also define their attributes

16
Service Overview
17
List of services
18
Summary

• Work done
• drafted CCSDS White Book
• analysed operational context
• identified services
• used layered architecture
• Future work
• CCSDS Green Book
• CCSDS standard specifications of each service