CCSDS SM&C Green Book Revision ToC

(draft 2.0, 16 Sep 05))

Introduction

Goals

Identification of the problem

Cost of training operational staff on different systems

Cost of mission specific developments and deployments

Incompatibility of infrastructure of different agencies.

Static and monolithic system architecture that does not allow re-distribution of functionality

Unavailability of commercial generic tools

Inability of replacing the used technology without major system redesign.

What is needed to solve problem

Service based, open architecture

Layering thus ability of replacing used technology

Non prescriptive of component implementation (only interfaces are standardized)

Respect legacy systems

Expected benefits

Interoperability

Stress importance of standardization within agency

Modularity of components and thus flexible boundaries.

Standardization of a limited number of services as opposed of a large number of interfaces.

Capability of moving services from ground to on-board

Ability to establish common multi-mission infrastructure

Increase competition (cost reduction) on commercial tools

Vendor independence

Ability to select the “best” product for the task.

Scope

What are mission operations?

Describe scope of MO

System boundaries

Variability of system configuration makes interfaces either internal or external. If internal, proprietary solution, but if external standardization would help

Interoperable Interfaces

Introduce diagram and describe various levels of interoperability (across, within, between …)

Future evolution of interoperable interfaces

Relationship to other CCSDS activities

Packet TC/TM

SLE

AMS

Approach

Introduce main functions based on experience

Identify interfaces across functions

Identify common type of information flow

Identify the operations associated with provision or delivery of information

Group homogeneous operations into services

Identify common pattern/sub-services across services

Introduce service basics

Capability set

Directory service (publish/subscribe)

Stress the fact that no aggregation of functionality is suggested

Give a couple of examples

Evolution not revolution (you do not have to do all in one go)

Handling of legacy systems

Briefly introduce the list of identified services and stress the fact that more can be added

Describe the layering approach

SM&C Common Service

SM&C Protocol (Target-Controller paradigm)

Lower layers

Documents Roadmap

Introduce document tree.

Document priority.

2

Green Book Revision ToC

Mario Merri

2005-10-25

ESA