[Smwg] [EXTERNAL] Service Management Roles

Shames, Peter M (312B) peter.m.shames at jpl.nasa.gov
Fri May 24 19:37:02 UTC 2019

Hi Erik,

Ok.  So it seems that this one slipped by.  Not sure we need a corrigendum, but maybe we do.  We can create endless Roles, there is no explicit limit on how many, the granularity, nor assigning more than one to any Org unit or sub-unit., but I wonder if a really fine granularity serves anyone?

I think it's a matter of practicality.  As I suggested, I can't really imagine an organization stood up to be a "Schedule Publisher" if they weren't also a "Cross Support Service Provider" or a "Management Service Provider".    I agree that we also have a "Conjunction Data Message Originator", but there are orgs that do that and do not necessarily also do "Flight Dynamics Data Provider".  They could easily be distinct, which is why we created the separate roles.

I agree that it's not a big deal, I just wonder if it serves us and our users?  Would we want separate roles for "F-LSE provider", "TD-CSTS Provider" as opposed to "Cross Support Service Provider", or for "SC Operator" separate from "SC Developer" and "Mission Operations Center"?

Cheers, Peter

From: Erik Barkley <erik.j.barkley at jpl.nasa.gov>
Date: Thursday, May 23, 2019 at 5:53 PM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>, Colin Haddow <Colin.Haddow at esa.int>, SMWG <smwg at mailman.ccsds.org>, SMWG <smwg-bounces at mailman.ccsds.org>
Cc: "wolfgang.Frase at dlr.de" <wolfgang.Frase at dlr.de>
Subject: RE: [Smwg] [EXTERNAL] Service Management Roles


Nope, probably not in today’s environment, but we (CESG) signed off on this. It seemed like a good idea as the time – it’s conceivable that some entity could outsource this function, but in reality not likely.  As I noted, in the future, perhaps there could be some sort of automated service discovery and this might be useful.   In any case, “not in today’s environment”.   Any thoughts on pursuing a corrigendum?

Should we (CESG) take a look at role assignments for the Conjunction Data Message…I believe that is currently a more specific role statement than generalized service provider.  If keeping that as a separate role identification makes sense, we may have more general issue to pursue as to when specific vs generic role statements should be stated in CCSDS standards.


From: Shames, Peter M (312B) <peter.m.shames at jpl.nasa.gov>
Sent: Thursday, May 23, 2019 17:43
To: Barkley, Erik J (3970) <erik.j.barkley at jpl.nasa.gov>; Colin.Haddow at esa.int; CCSDS SMWG ML(smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>; SMWG <smwg-bounces at mailman.ccsds.org>
Cc: wolfgang.Frase at dlr.de
Subject: Re: [Smwg] [EXTERNAL] Service Management Roles

Do you really need a "Schedule Publisher" role as opposed to a more generalized service provider role?  Would any org that was not also providing services, in some form, ever be a schedule publisher, and is the distinction truly useful in any practical sense?


From: SMWG <smwg-bounces at mailman.ccsds.org<mailto:smwg-bounces at mailman.ccsds.org>> on behalf of SMWG <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>
Reply-To: Erik Barkley <erik.j.barkley at jpl.nasa.gov<mailto:erik.j.barkley at jpl.nasa.gov>>
Date: Thursday, May 23, 2019 at 4:48 PM
To: Colin Haddow <Colin.Haddow at esa.int<mailto:Colin.Haddow at esa.int>>, SMWG <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>, SMWG <smwg-bounces at mailman.ccsds.org<mailto:smwg-bounces at mailman.ccsds.org>>
Cc: "wolfgang.Frase at dlr.de<mailto:wolfgang.Frase at dlr.de>" <wolfgang.Frase at dlr.de<mailto:wolfgang.Frase at dlr.de>>
Subject: Re: [Smwg] [EXTERNAL] Service Management Roles


Just to finally provide some sort of concurrence, via email/in writing, I think the proposed set of rules is fine.

It could be argued that in fact the schedule publisher role should be deprecated in favor of the two more generic CSSS role you're proposing, but I don’t think it’s worth pursuing at this time.

In some relatively distant future somebody may want to do some sort of service discovery with regard to the sanaregistry and a finer granularity may be of use but I think that is not any kind a pressing need for the foreseeable future – and we may have some new-fangled really cool registry capability in place then that makes this academic.  So, role statements are fine.

Best regards,

From: SMWG <smwg-bounces at mailman.ccsds.org<mailto:smwg-bounces at mailman.ccsds.org>> On Behalf Of Colin.Haddow at esa.int<mailto:Colin.Haddow at esa.int>
Sent: Wednesday, May 8, 2019 17:48
To: CCSDS SMWG ML(smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>) <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>; SMWG <smwg-bounces at mailman.ccsds.org<mailto:smwg-bounces at mailman.ccsds.org>>
Cc: wolfgang.Frase at dlr.de<mailto:wolfgang.Frase at dlr.de>
Subject: [EXTERNAL] [Smwg] Service Management Roles

Dear all,
             in response to the discussion of roles in the context of service management I propose the following;

Schedule Publisher - for providers of the simple
CSSS (Provider Cross Support Service System) for providers of planning info, service packages and suchlike (i.e. the responses to requests)
User CSSS (User Cross Support Services System) for submitters of requests

I don't really see any need to go to any finer granularity of roles and the above is inline with existing CCSDS terminology.

Cheers for now,


Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int<mailto:colin.haddow at esa.int>

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or

protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received

this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect

personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int<mailto:dpo at esa.int>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20190524/18049d6f/attachment-0001.html>

More information about the SMWG mailing list