Adrian Hooke, CESG ChairESTEC, Noordwijk, Netherlands

27 Oct 2009

SERVICE ARCHITECTURE FOR SPACE:

why this BOF?

1

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

“Communications View” of Space Mission Operations

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

Space Link Access Service Provision (“SLE”)

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

Data Relay Service Provision (Prox-1)

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

Surface Service Provision (new Surface BOF)

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

Space Internet Service Provision (IOAG-SISG)

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

Mission Operations Application Service Provision

CFDP, AMSAudio, Video

CFDP, AMSAudio, Video

Link Link Link Link

Network Network NetworkNetwork Network

CommonOperations

Services

CommonOperations

Services

UserApplications

UserApplications

The SM&C View?

?

• We don’t understand what you are trying to standardize (Operations Concept), or why (User Requirements)

• It looks like you are (at best) ignoring a whole bunch of painstaking work that has been done to date or you are (at worst) trying to throw it all out and force everyone to “do it our way”

• Either go away and stop annoying us, or learn to communicate better

To paraphrase the initial CESG reaction to SM&C:

But on further reflection came the recognition:• We don’t have an agreed “business model” for CCSDS

standardization• We don’t have an agreed architectural model of the services

that we are trying to standardize

Cross SupportPartner

SpacecraftA

GroundStation

B

ControlCenter

A

SpacecraftB

GroundStation

A

ControlCenter

A

SpacecraftA

GroundStation

A

ControlCenter

A

SpacecraftB

GroundStation

B

ControlCenter

B

Is our business model -

Commonality?

Cross Support?

Interoperability?

Hence --• Form a cross-cutting team

from across the Areas to define our business model and some kind of service framework into which all of our work can be referenced and evaluated

• Be prepared to merge in several related working groups which have been chipping away at parts of the problem

• Try to get something really useful, really quickly so that we don’t cause uncertainty in ongoing work