Can Harmonization be Achieved via

Standardization?: New Concrete Opportunities

from the CCSDS Mission Operations Services

CCSDS Spacecraft Monitoring & Control Working Group (SM&C)

M i Merri
Mario M i (ESA),
(ESA) Chair
Ch i

GSAW, Los Angeles, USA - 1 Mar 2011

 Spacecraft
Monitoring
& Control
Working Group

2016
2 Harmonisation via CCSDS MO Services
 Spacecraft
Monitoring
& Control
Putting Together Mission X
Working Group

 Mission X
 Spacecraft & Launcher
 Ground Stations
 Mission Control System
(Command and Control)
 Flight Dynamics System
 Mission Planning System
 Automation System
 Data Distribution System

3 Harmonisation via CCSDS MO Services

 Spacecraft http://www.ccsds.org/MO_Services-App-Store
Monitoring
& Control
Working Group

CCSDS MO app store

4 Harmonisation via CCSDS MO Services

 Spacecraft http://www.ccsds.org/MO_Services-App-Store
Monitoring
& Control
Working Group

CCSDS MO app store

CCSDS App Store Welcome to the CCSDS Mission

O
Operations
i Applications
A li i Store
S

Ground Segment
…please select the segment on the left pane
Space Segment

5 Harmonisation via CCSDS MO Services

 Spacecraft http://www.ccsds.org/MO_Services-App-Store
Monitoring
& Control
Working Group

CCSDS MO app store

CCSDS App Store

You-Control-It
SCOS-3000
Category: MCS
Category: MCS
Released: 30 Sep 2015
Released: 1 Jan 2016
Ground Segment
$$$
• Ground Station Free
• Mission Control System
• Flight Dynamics System
• Mission Planning System
• Automation System
• Data Distribution System M&C Suite
In-CONTROL
Category: MCS
Category: MCS
Released: 30 Sep 2015
Released: 1 Jan 2014
Space Segment Free
$$$

All these applications are CCSDS MO certified

6 Harmonisation via CCSDS MO Services

 Spacecraft Assembling Mission X Ground Segment from
(Harmonised) Components
Monitoring
& Control
Working Group

Mission
Control
System
Ground
Station
Services
Flight
Dynamics
Mission
System
Planning
System

Data
Distribution
Automation System
System Infrastructure

• Application-Level Components communicate via standardised Services

• Services are supported by a distributed Infrastructure
• Reusable components “Plug-in” via Service Interfaces to the Infrastructure
• Both Components and Infrastructure are replaceable with minimum impact to rest of
system
7 Harmonisation via CCSDS MO Services
 Spacecraft
CCSDS Spacecraft M&C (SM&C) Working
Group
Monitoring
& Control
Working Group

 Established December 2003

 ESA Chair (Mario Merri); UKSA Deputy
 Active Participation of 10 Space Agencies
 One of the Most Active CCSDS Working Groups
 Establishing a Service Oriented Architecture for Mission Operations
 Monitoring & Control
 Planning, Scheduling and Automation
 Navigation
 On-board
On board Software / Configuration Management

 Multiple Prototypes – now going operational at NASA/JSC for ISS

8 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
Distributable Mission Operations Functions
& Control
Working Group
Spacecraft
M&C (Status, Control)
Automation (Procedures, Timelines)
Planning (Tasks, Goals)
Mission Data ((Products))
Flight Dynamics (Orbit, Attitude)
On-board Software

Payload/Science Team Mission Control Centre Another Agency

Mission Operations Services:

Organisational Boundaries
Spacecraft Manufacturer
Functional Boundaries
System Boundaries
Long-Term Data Persistence

9 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
Characteristics of Mission Operations Services
Working Group

 Service Oriented Architecture (SOA) for

Spacecraft Mission Operations
Application Level Services for Mission Operations
g Components:
Enable Plug-in p Applications & Infrastructure

Semantic Interaction: Information not Data

Extensible Framework: C
Common and
d Generic
G i Elements
El t

Distributable: Independent of Deployment Architecture

Protocol Agnostic: Independent of Transport Technology

g g Neutral:
Language Independent of Deployment Language

10 Harmonisation via CCSDS MO Services

 Spacecraft
SOA: Integrated Systems vs. Modular
Components
Monitoring
& Control
Working Group

In traditional modular With SOA, more loosely

system design, components coupled components can be
can be integrated into just assembled into a range of
one system. similar systems.

11 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
End-to-End Services and Layering
Working Group End-to-End Communication:
Information Concepts (Invitation: Who, What, Where, When)
Standard Pattern of Interaction (Invite, Respond)

Transport Layer:
Packaging
Mission Mission
Operations Operations
Physical
Communications
Infrastructure

I shall Invite
She has
I Graciously
Thou art Invited I Graciously
Thou art Invited My Lord has
my Lady to a
Accepted
p Accept
to a Accept
to a IInvited
Shall Accept
me to
Feast a Feast
Banquet
B Banquet
B

I shall Invite
my Sweetheart My Beau has
to a Ball Invited me to
a Ball
B ll

I’ll Invite my Hey, Babe, Hey, Babe,

Girlfriend to a Wanna Come Wanna Come My Boyfriend
Party to a Party? to a Party? has Invited me
to a Party

U 12 Come 2
I’ll Invite my Rave? You
Girlfriend to a Have My Boyfriend
Rave Mail has Invited me
to a Rave

12 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
Mission Operations Framework Layers
Working Group

Application
Layer Consumer/Provider

Mapping to
implementation
language
Common Services Functional Services
Directory, Login, … M&C, Automation, Scheduling, Time, … Abstract service
p
specification defined
MO Services in terms of the COM
Layer &MAL

Common Object Model

Generic service
Identify Definition,
Identify, Definition Occurrence,
Occurrence Status specification defined
in terms of the MAL

Message
Abstraction Messaging
g g Abstraction Layer
y Abstract messaging
infrastructure
Layer Generic Interaction Patterns, Access Control, Quality of Service

Mapping of the MAL

to encoding and
Transport
transport
Layer Messaging Technology

13 Harmonisation via CCSDS MO Services

 Spacecraft
Mission Operations Services Interoperability
and Portability
Monitoring
& Control
Working Group

Language
Binding

SM&C Core Service

JAVA JAVA
C++
Consumer Application Provider Application

JAVA JAVA
C++
JAVA JAVA
C++
SM&C SM&C
SM&C
Common SM&C Core SM&C
SM&C Core
Core Common
Common

JAVA C++
JAVA
SM&C MAL for AMS
JMS SM&C MAL for AMS
JMS

AMS
JMS AMS
JMS

Interoperability Technology Binding:

Requires Encoding (e.g. XML)
Wire Protocol Transport
p (e.g. FTP)

14 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
MAL Protocol Bridging
Working Group

Consumer Provider
Application Application

M&C Service M&C Service

MAL MAL Bridge MAL

MAL Adapter A A MAL Adapter A MAL Adapter B B MAL Adapter B

Transport Technology A Transport Technology B

 Applications
pp a o hosted
o d in different
d transport
a po technology
o ogy environments:
o
 ESA / NASA
 Space / Ground
 CORBA / JMS

 Mission Operations Services transparently bridged at MAL layer

 Supports all Services overlaid on MAL
 Supports all Applications built on those Services

15 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
Clever Engineering of the MO Services
& Control

 Technology and location independent

Working Group

 Application computer language

 Transport and encoding
 Interoperable
 On Ground and/or space
 Discoverable: not duplicated via directory service

 Implementing common features in the same way

 Messages (standard header, construction rules)
 Interaction
te act o patte
patternss (Se
(Send,
d, Sub
Submit,
t, Request,
equest, Invoke,
o e, Progress,
og ess,
Publish-subscribe)
 Data types
 Error handling
 Common
C service
i templatel (archiving/retrieval,
( hi i / i l activity
i i
monitoring, events, configuration)
 Common services (e.g. directory, login,…)

16 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
API Standardisation
Working Group
MO Java MO MAL MO Service
Language Binding Specification Specification

References References

Implements Implements Implements

Uses
Java Transform MAL Model MO Service Model

Generates Generates

MAL MO Service
Java API Java API

 Approach Compatible with Model Driven Development and Autocoding

 Extensible
bl Approach:
h Only
l one Magenta Bookk required
d per Language

17 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
Specific MO Service Definition
Working Group

 Requires:
 Definition of Information Model (Service Objects)
 Definition of Service Operations (mapped to Interaction Patterns)
 Service Configuration (Object Definitions) [for Service
Deployment]

 Does not Require:

 Message
essage Encoding/Binding
cod g/ d g to o Messaging
essag g Technology
ec o ogy
Standard Technology Binding applies to all MO Services
 Specific Definition of API
Standard Language
g g Transform applies
pp to all MO Services
 Definition of Service Discovery, Login, Authentication, etc.
Covered by MO Common Service Specifications
 Specification of dedicated Service History Model
Covered by MO Common Object Model
18 Harmonisation via CCSDS MO Services
 Spacecraft
CCSDS Mission Operations Book Structure
and Status
Monitoring
& Control
Working Group

Mission Operations Services Published Books:

520.0 Specifications Technology Language
• MO Concept
MO Mappings Mappings • Reference Model
Concept
522.0 M&C • MAL
Service Specific
Service
Encoding
Draft Books:
Specifications
520.1 (optional)
y COM
52x.y
Reference
Model
Language
API
• Java API
Common
Object Model • COM
MAL
521.0 MAL Encoding • Common Services
Message
Abstraction • M&C Services
Layer (MAL)
Green Book • Space Packet Binding
Application
Magenta Book Profile

Blue Book Planned Books:

• Motion Imagery
Service
 Green Book = Informational
• JMS Binding
 Magenta Book = Recommended Practice
• C++ API
 Blue Book = Standard

19 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
Example: Mission Planning and Service Orchestration
Working Group
End-Users
Operations Planning Request
Other MPS
On-board Orbital Event
Flight Software
Dynamics
y Manoeuvres Software Loads Management Contact Schedulingg
Planning
Activity Scheduling
Request
Service
Orbital Events

Mission Contact Ground

Orbital
Event Planning
Scheduling Station
Service Complex
Service Engine [SLE-Man]

Scheduling
Service

On-board Schedule Ground Schedule

On-board Ground
Schedule Schedule
Management Execution

20 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
MAL Prototyping Validation
Working Group

 Mandatory CCSDS (ESA-CNES) Prototype

 Completely automated
 16840 individual tests!
 The two implementations interoperated perfectly!

 NASA/JSC-DLR Prototype
 DLR’s MCS (SCOS 2000) and JSC Simulator (legacy systems!)
 Conclusion: “DLR GSOC and NASA/JSC successfully exchanged actions,
parameters and alerts .... The interoperability prototype demonstrated
that the Message Abstraction Layer is transport and technology agnostic
and that space agencies can use the Mission Operations standards for
interoperability among existing legacy systems. … our findings provide
support for the overall viability of the standards.”

 ISS will be first operational user of MO Services

 Decision: PLATO (Power Level Analysis Tool @ NASA/JSC) to be a client
of the M&C Parameter service. Operational as of 2012

21 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
Conclusion
& Control

 MO service
service’ss underlying framework (RM,
(RM MAL) is ready
Working Group

 M&C and Common Services books are in advanced status

and will come next,
next hopefully by the end of the year

 Next MO services to be tackled depend

p on the interests
and needs of the community
 Planning?, Flight Dynamics?
 Suggestions
gg and active participation
p p of interested groups
g p are
welcome

 MO service standardisation provide the framework that

will allow real harmonisation of services (and
components) for mission operations

22 Harmonisation via CCSDS MO Services

 Spacecraft
Monitoring
& Control
Working Group

Let MO Services do the boring part

of the job so that YOU can focus
on the smart part

23 Harmonisation via CCSDS MO Services