<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Erik,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think it's a matter of practicality. As I suggested, I can't really imagine an organization stood up to be a
<span class="EmailStyle21">"Schedule Publisher" if they weren't also a "</span>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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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"?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Thursday, May 23, 2019 at 5:53 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Colin Haddow <Colin.Haddow@esa.int>, SMWG <smwg@mailman.ccsds.org>, SMWG <smwg-bounces@mailman.ccsds.org><br>
<b>Cc: </b>"wolfgang.Frase@dlr.de" <wolfgang.Frase@dlr.de><br>
<b>Subject: </b>RE: [Smwg] [EXTERNAL] Service Management Roles<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Peter,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">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? </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b>From:</b> Shames, Peter M (312B) <peter.m.shames@jpl.nasa.gov>
<br>
<b>Sent:</b> Thursday, May 23, 2019 17:43<br>
<b>To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov>; Colin.Haddow@esa.int; CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org>; SMWG <smwg-bounces@mailman.ccsds.org><br>
<b>Cc:</b> wolfgang.Frase@dlr.de<br>
<b>Subject:</b> Re: [Smwg] [EXTERNAL] Service Management Roles<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="EmailStyle21">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?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="color:black">From:
</span></b><span style="color:black">SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>> on behalf of SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Reply-To: </b>Erik Barkley <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Thursday, May 23, 2019 at 4:48 PM<br>
<b>To: </b>Colin Haddow <<a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>>, SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>>, SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>><br>
<b>Cc: </b>"<a href="mailto:wolfgang.Frase@dlr.de">wolfgang.Frase@dlr.de</a>" <<a href="mailto:wolfgang.Frase@dlr.de">wolfgang.Frase@dlr.de</a>><br>
<b>Subject: </b>Re: [Smwg] [EXTERNAL] Service Management Roles</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Colin,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Just to finally provide some sort of concurrence, via email/in writing, I think the proposed set of rules is fine.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">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. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">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.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><b>From:</b> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b><a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a><br>
<b>Sent:</b> Wednesday, May 8, 2019 17:48<br>
<b>To:</b> CCSDS SMWG ML(<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>) <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>>; SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>><br>
<b>Cc:</b> <a href="mailto:wolfgang.Frase@dlr.de">wolfgang.Frase@dlr.de</a><br>
<b>Subject:</b> [EXTERNAL] [Smwg] Service Management Roles<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Dear all,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> in response to the discussion of roles in the context of service management I propose the following;</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Schedule Publisher - for providers of the simple
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">schedule</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Provider</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">CSSS (</span><span lang="EN-GB">Provider Cross Support Service System) for providers of planning info, service packages and suchlike (i.e. the responses
to requests)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">User CSSS (User Cross Support Services System) for submitters of requests</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">I don't really see any need to go to any finer granularity of roles and the above is inline with existing CCSDS terminology.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">Cheers for now,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">Colin</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; <a href="mailto:colin.haddow@esa.int">colin.haddow@esa.int</a><br>
---------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<pre style="margin-left:1.0in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:1.0in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:1.0in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:1.0in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>