<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1660840006;
mso-list-template-ids:1189495196;}
@list l0:level1
{mso-level-start-at:2;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:1819608299;
mso-list-template-ids:-737239248;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-DE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">I hope my understanding is correct and the Service Agreement shall serve the purpose to characterize and ultimately agree configurations
for a set of services (configuration profiles) provided by an ESLT or perhaps even flying assets. If that is the case, I suggest basing individual service definitions on the Functional Resource Model (FRM). Such service definitions can capture the semantics
of the service on top of the semantic definitions of the underling Functional Resources (which are available to provide further information). As a bonus, the configuration parameters of the complete services are ‘falling out’ of the Functional Resources forming
the service. See the below example of a Telemetry Service defined in terms of FRs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="738" height="387" style="width:7.6875in;height:4.0312in" id="Picture_x0020_39" src="cid:image001.png@01DA4AAE.4EA370F0"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">Ultimately you may need Functional Resource Instances to capture the configuration of individual Functional Resource Instances (e.g. several
FR instances of the same type to configure redundant modems). This feature is now supported by an M2M transformation from FRM (xmi) to FRIM (ecore and xsd):
<a href="https://github.com/esa/ccsds-css-frm-editor">https://github.com/esa/ccsds-css-frm-editor</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">I think such an approach can ensure real consistency. Service Agreements use then by definition parameters consistent with those monitoring
and configuration parameters defined by FRM and made available with CSTS Monitored Data Service. Of course, you can also think of capturing available control directives in a Service Agreement, which you can invoke e.g. by means of CSTS Service Control.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US">Holger<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">SMWG <smwg-bounces@mailman.ccsds.org> on behalf of Shames, Peter M (US 312B) via SMWG <smwg@mailman.ccsds.org><br>
<b>Date: </b>Thursday, 18. January 2024 at 18:45<br>
<b>To: </b>Marcin.Gnat@dlr.de <Marcin.Gnat@dlr.de>, smwg@mailman.ccsds.org <smwg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [cssm] [EXTERNAL] CSSM: Service Agreement Parameters - Update of the presentation from Fall Meetings 2023<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Hi Marcin, et al,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">It’s great that you guys have started to develop this Service Agreement framework. I think it should be of a lot of use and that what you have produced is a good start.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">That said, I have a few comments and observations that will undoubtedly come up when this standard crosses my desk as part of a CESG review. So I thought I’d toss them out now, for your consideration.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Comments<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt">This draft makes mention of a variety of objects for which we have existing (if somewhat incompletely filled out) SANA registries, but there
is no mention of SANA anywhere. I believe that all of the following should be referenced, and that the standard should clarify how these are to be used, extended if needed, or substituted only where it is essential to do so.<o:p></o:p></span></li></ol>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/organizations/">https://sanaregistry.org/r/organizations/</a><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/contacts/">https://sanaregistry.org/r/contacts/</a><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/service_management_entity_types/">https://sanaregistry.org/r/service_management_entity_types/</a><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/service_sites_apertures/">https://sanaregistry.org/r/service_sites_apertures/</a><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/spacecraft/">https://sanaregistry.org/r/spacecraft/</a><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo1"><span lang="EN-US" style="font-size:11.0pt"><a href="https://sanaregistry.org/r/spacecraftid/">https://sanaregistry.org/r/spacecraftid/</a><o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:72.0pt"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo2"><span lang="EN-US" style="font-size:11.0pt">This seems to be exclusively focused on “standard” Earth to S/C services, but we are already in an era where there are existing “space based
services”, like the Mars orbiting missions, and the Lunar mission set, with “standardized” relay operations, is already in development. Is there a plan for addressing these other classes of missions?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo2"><span lang="EN-US" style="font-size:11.0pt">Is there a plan to build in extensibility for new service types as these are developed? This might include, for instance, Lunar PNT services,
DTN services, and DTN to IP “protocol bridging”.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">I’d be happy to discuss this at more length when you are ready.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black">SMWG <smwg-bounces@mailman.ccsds.org> on behalf of SMWG <smwg@mailman.ccsds.org><br>
<b>Reply-To: </b>"Marcin.Gnat@dlr.de" <Marcin.Gnat@dlr.de><br>
<b>Date: </b>Thursday, January 18, 2024 at 12:49 AM<br>
<b>To: </b>SMWG <smwg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [cssm] CSSM: Service Agreement Parameters - Update of the presentation from Fall Meetings 2023</span><span lang="EN-US" style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><a name="Gruß"></a><span lang="DE" style="font-size:11.0pt">Dear all,</span><span lang="EN-US" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt"> </span><span lang="EN-US" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">I had a small task to update the collection of the Service Agreement parameters, which I presented during Fall Meetings 2023. During this presentation we had a discussion and number of comments/changes,
which now I implemented. As you can see I still have there two or so “TBCs”. Except that I think it looks good for the first schema version for SA File type. I will try to set it up until our next teleconference, but not promising it….;-)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Cheers<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Marcin<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
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@esa.int).
</body>
</html>