<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Sam,<div class=""><br class=""></div><div class="">I have not looked at the GB since quite some time and the present version is a great improvement.</div><div class=""><br class=""></div><div class="">here 2 general points.</div><div class=""><br class=""></div><div class="">1) Use cases</div><div class="">Regarding the current version (being a GB) it is important to clarify use case and rationale and </div><div class="">section 2 does address these points.</div><div class=""><br class=""></div><div class="">My main concern is that the presented use cases are very TT&C centric mimicking what is done in Space Science</div><div class="">at ESA where a single entity is interfacing for both TT&C and Payload/science data to what we call MOC and SOC</div><div class="">and assume this is always the case</div><div class=""><br class=""></div><div class="">This is not the general use case in EO neither when it is all handled by ESA nor when other institutions are </div><div class="">involved (e.g. Eumetsat) or even US partners (e.g. JPL/NASA/CNES/EUM for Sentinel 6). </div><div class="">Here the data flow and responsibility for TT&C and for payload/science data acquisition (ground station) </div><div class="">and for processing are decoupled and in some case the “science” operation are not performed directly by </div><div class="">whoever process the data. In our drawings e.g. Fig 3-8 or Fig 3-11 the Planning/command and control are currently </div><div class="">always coupled with the “data product”data flow. Note also that for EO the payload data is not called Telemetry as </div><div class="">that therm is customarily reserved for data related to TT&C (e.g. HKTM)</div><div class=""><br class=""></div><div class="">We should make clear to all data processing stakeholders that a properly implemented MO services have the potential to </div><div class="">ease their interfacing between various entities and for various purposes and not restrict it only to the domain of TT&C by</div><div class="">presenting some relevant use case.</div><div class=""><br class=""></div><div class="">I would propose therefore to define a use case where data processing entity is not the same that is responsible </div><div class="">of the the operation to show explicitly that MO is also good for these type of interfaces </div><div class="">(e.g. could be a Level 2 data processing center). I could sketch something if you like and then leave to you </div><div class="">to make it in the same graphic style as the current.</div><div class=""><br class=""></div><div class="">2) Presentation aspects</div><div class="">there is a list of “user level” functional services on page 10, but that is a bit “hidden” in a bullet list and most prominence </div><div class="">is given to the lower level mechanism to implement these that target implementors. </div><div class="">I would give more prominence to the list on page 10 as this is what a decision maker would look at. I also would not </div><div class="">mix in section 9 high level functional services with lower level things like MAL, COM etc. now they come one after</div><div class=""> the other section 9.2 and 9.3 so you get in one page “Planning” and immediately in front “Binding to TCP/IP”. </div><div class="">Most Project manager I know would understand Planning services, but would steer clear of “TCP/IP”…so I would split them </div><div class="">more clearly in the document.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Michele</div><div class=""><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 4 Mar 2019, at 10:34 , Sam Cooper <<a href="mailto:sam@brightascension.com" class="">sam@brightascension.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Dear All,<br class="">
<br class="">
Just a quick reminder for comments if you have them are due by the
8th.<br class="">
<br class="">
Best regards,<br class="">
Sam.<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 14/02/2019 13:41, Sam Cooper wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:5e13ee9e-a7e9-286b-04fd-3cbabcee36fa@brightascension.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
Dear All,<br class="">
<br class="">
Please find below the link to the latest draft of the MO Concept
Green Book for review:<br class="">
<br class="">
<a class="moz-txt-link-freetext" href="https://cwe.ccsds.org/moims/docs/MOIMS-SMandC/Draft%20Documents/Concept%20Green%20Book/Green%20Book%20Outline%20R5%20Feb%202019.docx?Web=1" moz-do-not-send="true">https://cwe.ccsds.org/moims/docs/MOIMS-SMandC/Draft%20Documents/Concept%20Green%20Book/Green%20Book%20Outline%20R5%20Feb%202019.docx?Web=1</a><br class="">
<br class="">
Please could people provide comments etc by 8th of March in three
weeks time. <br class="">
<br class="">
The contents of the book is 95% complete, just the future
directions section to be expanded on, if people could suggest
content for that as part of the review that would be very helpful.
It is also not in official CCSDS format, but that is relatively
easy to add at a later date.<br class="">
<br class="">
I think Peter has done a great job in writing this, however it has
taken far longer than we had hoped therefore I would like to
suggest that I take over the editing/updating of the document from
this point forward. If there is an issue with this suggestion
please let me know otherwise I will assume that it is acceptable.<br class="">
<br class="">
Best regards,<br class="">
Sam.<br class="">
<br class="">
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">MOIMS-SC mailing list<br class=""><a href="mailto:MOIMS-SC@mailman.ccsds.org" class="">MOIMS-SC@mailman.ccsds.org</a><br class="">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc<br class=""></div></blockquote></div><br class=""></div></div></body></html>