European Space Operations Centre

1
European Space Operations Centre
CCSDS MOIMS AREA Standardisation over the Next
Decade
SpaceOps 2004 17th May 2004

Nestor Peccia, ESA Roger Thompson, SciSys UK
2
Overview

• CCSDS Domain
• CCSDS New Organization
• MOIMS Area drivers
• MOIMS Approach
• Spacecraft Monitoring Control WG
• Navigation WG
• Information Packaging and Registries WG
• Archiving WG
• MOIMS Cross related WG Synergies
• MOIMS The next decade

3
CCSDS Domain

• The work of CCSDS logically cleaves into three
  abstract domains that enclose the technical
  disciplines of the organization
• Space Informatics Domain, containing two Areas
• Mission Operations and Information Management
  Services (MOIMS)
• Cross Support Services
• Space Telematics Domain
• Space Systems Domain

4
CCSDS New Organization
5
MOIMS Area Drivers

• It has been a constant in recent years that
  agencies have had to reduce cost, while
  increasing
• Development of mechanisms and techniques for
  monitoring control of remote spacecraft and
  their end systems
• Automation of acquisition and ingestion of
  mission data and metadata, and their exchange
  among applications(including spacecraft control
  and navigation)

6
MOIMS Area Drivers

• The high level goal of this standardization
  effort is to make economies by
• Facilitating the development of generic on-board
  and on-ground software infrastructure
• supporting multiple projects via simple
  re-configuration
• Applying the SMC service-oriented approach and
  systems to other MC domains
• ground stations, control centers, test
  facilities, etc.
• Facilitating the development of data packaging
  techniques and their association with the
  registration of schemas/data definitions
• Streamlining current archive functionality
  usually totally ad hoc by mission or by a given
  multi-mission or final archive
• Facilitating the information exchange in the
  navigation domain (attitude, orbital elements,
  tracking, reference systems)

7
MOIMS Approach
8
Spacecraft MC WG

• The main goals of this Working Group are to
• Define common SMC operational concept (short-term
  )
• Define low-level reference on-board and on ground
  architecture (short-term)
• Define an approach to layered Service
  Definition (short-term)
• Platform Independent Information Model and
  Service Dynamics
• Application Level services, shared by multiple
  Applications
• Common Protocol Level services, used by all
  Application Level Services
• Identify Application Level SMC
  Services (short-term)
• Analyse and Identify Common Protocol Level SMC
  Services (short-term)
• Define the Common Protocol Level Services
  (medium-term)
• Define the prioritised Application Level SMC
  Services
• Core Monitoring Control Services
  (medium-term)
• Time and Location Services
  (medium-term)
• On-board Software Management Service (long-term)
• Automation, Scheduling and Mission Planning
  Services (long-term)
• Flight Dynamics Service (long-term)
• Operator Interaction Service (long-term)
• Define operational database interchange format
  (OMG XTCE) (short-term)

9
MOIMS SMC End-to-End Services
10
Navigation WG

• The main goals of this Working Group are to
• Provide a discussion forum for navigation data,
  formats, and terminology.
• Determine which areas within the realm of
  navigation data (e.g. position, velocity, and
  attitude) are likely candidates for standards.
• Establish standards for data content and data
  formats for tracking, attitude, trajectory, and
  ancillary data (e.g. gravity models, spacecraft
  orientation). Different types of missions will
  have vastly different requirements on the data
  required. (Medium/long term)
• Study the need for different or expanded
  standards for various classes of missions.

11
Information Packaging and Registries WG

• The main goals of this Working Group are to
• Refine high level common information
  architecture (short-term)
• Define the components and service
  I/Fs (short-term)
• Define generic data structures, usable by
  different applications (medium-term)
• Define extensible registry data
  models (medium-term)
• Define registry services and interfaces (medium-te
  rm)
• Assist application areas (in MCS Monitoring,
  Planning, Navigation and FDS) in the using of
  these standards
• Update EAST standard (rewrite) (long-term)
• Better describe relationships and behaviours
  (notation or language) (medium-term)
• Implement DEDSL with XML Schema (short-term)

12
Archiving WG

• The main goals of this Working Group are to
• Produce standards and guidelines supporting
  mission and multi-mission (final) archives,
  including the following
• Reference models covering various views of
  archival issues (short-term)
• Updated OAIS Reference Model version
  (medium-term)
• Interfaces between OAIS type archives (medium-ter
  m)
• Submission (ingest) methodology used by an
  archive (medium-term)
• Submission (ingest) of digital data sources to
  the archive (medium-term)
• Delivery of digital sources from the
  archive (medium-term)
• Submission of digital metadata, about digital or
  physical data sources, to the archive (medium-term
  )
• Identification of digital data within the
  archive (medium-term)

13
Archiving WG

• Identification of services among various
  functional areas (long-term)
• Search and retrieval of metadata information
  about digital and physical data sources
• Media access allowing replacement of media
  management systems without having to rewrite the
  media
• Specific physical media
• Migration of information across media and
  formats
• Evaluating formats with regard to long-term
  preservation
• Recommended archival practices (medium-term)
• Accreditation/certification of archives. (medium-t
  erm)

14
MOIMS Cross related Working Group Synergies

• The following cross-related issues and synergies
  can be addressed
• The Spacecraft MC and Navigation WGs need
• standard interfaces for mission archive
• standard on information (including metadata)
• The Information Packaging Registries WG
  produces the XML Packaging specifications to be
  used by other WGs
• The Archiving WG produces a generic SIP
  (Submission Information Package) standard, which
  can be specialised for Mission Archive
• The Information Packaging Registries and the
  Archiving WGs need to analyse information
  handling at Mission Control and Navigation
  systems.

15
MOIMS The Next Decade

• Service based architecture is gradually replacing
  monolithic architecture
• The two main drivers of the process in the MOIMS
  Area are interoperability and evolution towards
  an open architecture for MCS, based on layered
  services.
• Our task is to define
• What the services are
• What data products exist at the interfaces to
  these services, by considering a two-fold
  approach
• At the interfaces on-board and on-ground
• At the service provider and at the service user
• The standardisation of the main services will
  open the way to interoperability.