<font size=2 face="sans-serif">Hello<br>
<br>
I have uploaded my comments:</font>
<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"><font size=2 color=blue face="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</font></a>
<br>
<br><font size=2 face="sans-serif">The document is a very early shape.
it is hard to really make an opinion at that point.</font>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="sans-serif">Many reference are made to SANA registry,
which is a good idea in principle. </font>
<br><font size=2 face="sans-serif">But the poor quality of the actual SANA
registry discredit this document. </font>
<br><font size=2 face="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>
________________________________________</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif"><Marcin.Gnat@dlr.de></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><smwg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">28/12/2016 11:30</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Smwg] Response
to AI 2016-1019-8: Service Catalog Review</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"SMWG"
<smwg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><a name="Gruß"></a><font size=2 face="Calibri">Hi CCSDSCSSSMWG Colleagues,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I just reviewed and commented the draft
for the Service Catalog:</font>
<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"><font size=2 color=blue face="Calibri"><u>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</u></font></a>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">General observations:</font>
<br><font size=2 face="Calibri">- 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.</font>
<br><font size=2 face="Calibri">- 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.</font>
<br><font size=2 face="Calibri">- Depending
on how big the SCCS Resources Used parts will be, maybe it would be worth
to consider table form for services?</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Best Regards and Happy New Year</font>
<br><font size=2 face="Calibri">Marcin</font><tt><font size=2>_______________________________________________<br>
SMWG mailing list<br>
SMWG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>