<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=us-ascii">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
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:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Martin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks for taking a look and posting the comments. A few notes in reply.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Given that a magenta book is a best practices kind of book in CCSDS I tend to agree with you that this recommendation should offer guidance on what is contained
in the service catalog versus being a service catalog per se. It is of course likely that there will need to be some examples supplied as to how the practice is applied so some of the material that is in here currently may in fact go into making that up. It
will be an interesting discussion to see what the key characteristics of a particular service should be. From my point of view, it seems to me that telemetry service, for example, should indicate everything from frequency bands, modulation and coding schemes
supported, minimum and maximum data rates (in relation to receiving antenna gain vs transmitting antenna power), as well as the terrestrial transfer aspects. Perhaps others on this email list could indicate the kind of things that are important for describing
service in their agencies. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Re SANA I think the current state of the SANA registries is one of being in flux. In particular, I know that the current RF Assets registry is unsatisfactory
and lacking in the ability to support real-world operations -- information which the Sites and Apertures registry is supposed to address. In particular, for the simple schedule services this is registry (Sites and Apertures) is cited in the book that is about
to be sent to the Secretariat's office. My understanding is that the SANA Operator has put a first draft of the sites and apertures registry together but this is still largely blank pending population with real-world data. My assumption is that proper real-world
data will eventually make its way in here and I will be sure to take an interest in seeing that this does happen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SMWG [mailto:smwg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Martin.Unal@esa.int<br>
<b>Sent:</b> Tuesday, January 24, 2017 6:50 AM<br>
<b>To:</b> smwg@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Smwg] Response to AI 2016-1019-8: Service Catalog Review<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello<br>
<br>
I have uploaded my comments:</span> <br>
<a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Catalog/SCCS-SM_902.7-M-0.2%20(2016%2010%2014)%20MU.docx"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Catalog/SCCS-SM_902.7-M-0.2%20(2016%2010%2014)%20MU.docx</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The document is a very early shape. it is hard to really make an opinion at that point.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In its current state, it gives the impression to be a service catalogue rather than a standard on how to establish a service catalogue, I assume this is normal at this stage.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Many reference are made to SANA registry, which is a good idea in principle.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">But the poor quality of the actual SANA registry discredit this document.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If the SANA issue is not tackled this document will not be usable (Who as one million $ to pay for the necessary effort ? :( )
<br>
<br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 Fax +49 6151 90 3190<br>
________________________________________</span> <br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><<a href="mailto:Marcin.Gnat@dlr.de">Marcin.Gnat@dlr.de</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">28/12/2016 11:30</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">[Smwg] Response to AI 2016-1019-8: Service Catalog Review</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"SMWG" <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<a name="Gruß"></a><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Hi CCSDSCSSSMWG Colleagues,</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">I just reviewed and commented the draft for the Service Catalog:</span>
<br>
<a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Catalog/SCCS-SM_902.7-M-0.2%20(2016%2010%2014)_mgn.docx"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Service%20Catalog/SCCS-SM_902.7-M-0.2%20(2016%2010%2014)_mgn.docx</span></a>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">General observations:</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">- The draft book looks like an extension to the IOAG Service Catalog. I do not know yet if it’s good or not, definitely some starting point.</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">- The most interesting part, the reference to related components (SCCS Resources Used) is missing, which may be will fill the book with “life” in future.</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">- Depending on how big the SCCS Resources Used parts will be, maybe it would be worth to consider table form for services?</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Best Regards and Happy New Year</span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Marcin</span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SMWG mailing list</tt><br>
<tt><a href="mailto:SMWG@mailman.ccsds.org">SMWG@mailman.ccsds.org</a></tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</body>
</html>