<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Dear Mario,</div>
<div><br>
</div>
<div>As we agreed during the meeting in Darmstadt, we will do this work in two phases. For the first we agreed to focus on SOIS in flight and MOIMS (MO Services, Nav, DAI, Robotics, mission planning) on the ground. There is a lot of work to be done just to
get all of these services, interfaces, terminology, and representative configurations sorted out. And there is the work to specify clearly the relationships to the other four CCSDS areas of work.</div>
<div><br>
</div>
<div>I think we should call that Phase 1.</div>
<div><br>
</div>
<div>For the second, Phase 2, we will deal with what it means to then migrate elements of the MOIMS on-board. The first will take a lot of specification work. This second phase will take a lot of analysis and negotiation, which will be made easier (but not
simple) if first have the phase 1 understanding completed.</div>
<div><br>
</div>
<div>I believe that this is what we all agreed to and it is what we intend to do. What is described in these minutes is the plan only for Phase 1. This will be reviewed and if there is agreement, and continued resources and support to get the job done, we
will start Phase 2. Nothing in Phase 1 precludes Phase 2, so there should be no conflict.</div>
<div><br>
</div>
<div>I hope you agree.</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Monday, December 7, 2015 at 1:25 AM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </span>Martin Suess <<a href="mailto:Martin.Suess@esa.int">Martin.Suess@esa.int</a>>, Richard Barton <<a href="mailto:richard.j.barton@nasa.gov">richard.j.barton@nasa.gov</a>>, Brigitte Behal <<a href="mailto:Brigitte.Behal@cnes.fr">Brigitte.Behal@cnes.fr</a>>,
Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>, Wallace Tai <<a href="mailto:Wallace.S.Tai@jpl.nasa.gov">Wallace.S.Tai@jpl.nasa.gov</a>>, Dan Smith <<a href="mailto:danford.s.smith@nasa.gov">danford.s.smith@nasa.gov</a>>,
"<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>" <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>>, "<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>" <<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>>,
Roger Thompson <<a href="mailto:Roger.Thompson@scisys.co.uk">Roger.Thompson@scisys.co.uk</a>>, Ramon Krosley <<a href="mailto:r.krosley@andropogon.org">r.krosley@andropogon.org</a>>, "<a href="mailto:yonghui@nssc.ac.cn">yonghui@nssc.ac.cn</a>" <<a href="mailto:yonghui@nssc.ac.cn">yonghui@nssc.ac.cn</a>>,
SEA-SA <<a href="mailto:sea-sa@mailman.ccsds.org">sea-sa@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: FW: SAWG Reference Architecture planning session - minutes<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div><font size="2" face="Arial">Dear Peter,</font> <br>
<br>
<font size="2" face="Arial">As I mentioned already during the Reference Architecture meeting in Darmstadt, I would like that the WG considers from the very beginning that the "big picture" Reference Architecture includes MO Services on board. This is in fact
where the relationship between MO Services and SOIS - that you would like to capture with this work - sits. It is agreeable that initially more detailed work should focus on MO Services on the ground, but I do not want that the MO Services end-to-end concept
is lost.</font> <br>
<br>
<font size="2" face="Arial">Please confirm that this is your intentions.</font> <br>
<br>
<font size="2" face="Arial">Best regards,</font> <br>
<br>
<font size="2" face="Arial">__Mario</font> <br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"Martin Suess" <<a href="mailto:Martin.Suess@esa.int">Martin.Suess@esa.int</a>>, "Richard Barton" <<a href="mailto:richard.j.barton@nasa.gov">richard.j.barton@nasa.gov</a>>,
"Mario Merri" <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>, "Brigitte Behal" <<a href="mailto:Brigitte.Behal@cnes.fr">Brigitte.Behal@cnes.fr</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Cc: </font><font size="1" face="sans-serif">"Nestor Peccia" <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>, "Tai, Wallace S (9000)" <<a href="mailto:wallace.s.tai@jpl.nasa.gov">wallace.s.tai@jpl.nasa.gov</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">02/12/2015 20:26</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">FW: SAWG Reference Architecture planning session - minutes</font><br>
<hr noshade="">
<br>
<br>
<br>
<font size="2" face="Calibri">FYI -</font> <br>
<br>
<font size="2" face="Calibri">Minutes from the CCSDS Ref Arch telecon.</font> <br>
<br>
<font size="2" face="Calibri">Peter</font> <br>
<br>
<br>
<font size="2" face="Calibri"><b>From: </b>Peter Shames <</font><a href="mailto:peter.m.shames@jpl.nasa.gov"><font size="2" color="blue" face="Calibri"><u>peter.m.shames@jpl.nasa.gov</u></font></a><font size="2" face="Calibri">><b><br>
Date: </b>Tuesday, December 1, 2015 at 4:50 PM<b><br>
To: </b>Roger Thompson <</font><a href="mailto:Roger.Thompson@scisys.co.uk"><font size="2" color="blue" face="Calibri"><u>Roger.Thompson@scisys.co.uk</u></font></a><font size="2" face="Calibri">>, Ramon Krosley <</font><a href="mailto:r.krosley@andropogon.org"><font size="2" color="blue" face="Calibri"><u>r.krosley@andropogon.org</u></font></a><font size="2" face="Calibri">>,
"</font><a href="mailto:yonghui@nssc.ac.cn"><font size="2" color="blue" face="Calibri"><u>yonghui@nssc.ac.cn</u></font></a><font size="2" face="Calibri">" <</font><a href="mailto:yonghui@nssc.ac.cn"><font size="2" color="blue" face="Calibri"><u>yonghui@nssc.ac.cn</u></font></a><font size="2" face="Calibri">><b><br>
Cc: </b>SEA-SA <</font><a href="mailto:sea-sa@mailman.ccsds.org"><font size="2" color="blue" face="Calibri"><u>sea-sa@mailman.ccsds.org</u></font></a><font size="2" face="Calibri">><b><br>
Subject: </b>SAWG Reference Architecture planning session - minutes</font> <br>
<font size="2" face="Calibri"><b><i>================================================================</i></b></font><br>
<br>
<font size="4" face="Calibri"><b><i>SAWG Reference Architecture planning session – Telecon, 1 Dec 15</i></b></font><br>
<br>
<font size="4" face="Calibri"><u>Attendees: Roger Thompson, Ramon Krosley, Hwang Yonghui, Peter Shames</u></font><br>
<br>
<font size="4" face="Calibri"><b>Agenda</b></font>
<ul>
<li><font size="4" face="Calibri">Discuss overall approach and forward plan</font></li><li><font size="4" face="Calibri">Discuss MOIMS approach</font> </li><li><font size="4" face="Calibri">Discuss SOIS approach</font> </li><li><font size="4" face="Calibri">Forward work and next meeting</font></li></ul>
<font size="4" face="Calibri"><b>Minutes</b></font> <br>
<br>
<font size="4" face="Calibri">Discuss overall approach and forward plan</font> <br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Reviewed the top level materials from the 10 Nov 2015 working session</font><font size="2" face="Calibri"></font><br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Scope of Work and Proposed Approach for WG efforts</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">SCCS-ARD (CCSDS 901x1m1) - Figure 7-4</font><br>
<font size="2" face="sans-serif">3. </font><font size="4" face="Calibri">Cross Support / Mission Operations Interactions using Standard SLE / SM Services</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">Discussed the possible adoption of UML/SysML, but decided to shelve it for now due to constrained time and resources</font><font size="2" face="Calibri"></font><br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Agree on value of developing SysML Profile for the future RASDS revision in Phase 2</font><br>
<font size="2" face="sans-serif">3. </font><font size="4" face="Calibri">Discussed the general features of the Reference Architecture for Space Data Systems (RASDS) using some of the available diagrams</font><br>
<font size="2" face="sans-serif">4. </font><font size="4" face="Calibri">Confirmed agreement to use existing RASDS PPT approach to align with SCCS-ADD/ARD</font><br>
<font size="2" face="sans-serif">5. </font><font size="4" face="Calibri">Agree to align all new materials with current PPT “cartoon” template (SCCS-ARD materials including template, pg 2, provided here)</font><br>
<font size="4" face="Calibri">Discuss overall MOIMS approach</font> <br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Reviewed the MOIMS Mission Operations Services Overview (from MOSC 520x0g3)</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">Discussed the relationships among the elements as depicted</font><br>
<font size="2" face="sans-serif">3. </font><font size="4" face="Calibri">Discussed the fact that this is just an overview example and that many different mission configurations are possible
</font><br>
<font size="2" face="sans-serif">4. </font><font size="4" face="Calibri">Discussed the evolving nature of the MOIMS functional models and that some functional groups are more developed than others</font><br>
<font size="2" face="sans-serif">5. </font><font size="4" face="Calibri">Discussed that Nav / OD is well understood, the mission planning is evolving, and that some functional groups could be further aggregated to reduce complexity of top level diagrams</font><br>
<font size="2" face="sans-serif">6. </font><font size="4" face="Calibri">Confirmed agreement for Phase 1 of this effort to limit the MOIMS to the ground and SOIS to space</font><br>
<font size="2" face="sans-serif">7. </font><font size="4" face="Calibri">Agreed to largely stick to what is already documented, but also to propose new [Future] funcitons / standards where their role appears to be clear</font><font size="2" face="Calibri"></font><br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Agree to review any such extensions with the SM&C WG</font><br>
<font size="2" face="sans-serif">8. </font><font size="4" face="Calibri">Agreed to develop at least one MOIMS / SM&C top level diagram for the next meeting</font><br>
<font size="2" face="sans-serif">9. </font><font size="4" face="Calibri">Reviewed the Nav / OD diagram from the Nav WG and agreed that the level of detail in this diagram is probably about correct for the lowest level of decomposition that we will develop</font><br>
<font size="2" face="sans-serif">10. </font><font size="4" face="Calibri">Reviewed Nestor’s "MO Services” diagram and agreed to stick to the defined SM&C / MO service names and functions</font><br>
<font size="2" face="sans-serif">11. </font><font size="4" face="Calibri">Discussed the need to cover all of MOIMS and not just SM&C and Nav, needs further thought & discussion</font><br>
<font size="4" face="Calibri">Discuss overall SOIS approach</font> <br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Reviewed the SOIS Service Architecture (from 876x0r0)
</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">Discussed the relationships among the elements as depicted</font><br>
<font size="2" face="sans-serif">3. </font><font size="4" face="Calibri">Discussed the fact that this is just an overview of the service layering and that many different mission configurations are possible
</font><br>
<font size="2" face="sans-serif">4. </font><font size="4" face="Calibri">Discussed the SOIS approach of defining abstract services and (largely) exchanges of abstract data type</font><br>
<font size="2" face="sans-serif">5. </font><font size="4" face="Calibri">Reviewed the “Plug and Play” View of SOIS Architecture (from 850x0g1)</font><br>
<font size="2" face="sans-serif">6. </font><font size="4" face="Calibri">Agreed that this is the right level of detail, but that we need to identify the types of the data exchanged among these functions</font><br>
<font size="2" face="sans-serif">7. </font><font size="4" face="Calibri">Discussed, in general, the relationship between SOIS and MOIMS (defered until Phase 2)</font><br>
<font size="2" face="sans-serif">8. </font><font size="4" face="Calibri">Agreed on an approach to include future work, where required, in the document and in the figures</font><font size="2" face="Calibri"></font><br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Use [Future] prefix marking in the document, as in SCCS-ARD, for document references</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">Use [F] suffix in the figures to distinguish future functions, protocols, data structures</font><br>
<font size="2" face="sans-serif">9. </font><font size="4" face="Calibri">Agreed to develop at least one SOIS top level diagram and one next level diagram for the next meeting</font><br>
<font size="4" face="Calibri">Forward work and next meeting</font> <br>
<font size="2" face="sans-serif">1. </font><font size="4" face="Calibri">Roger will develop a top level view of the MOIMS layered service architecture</font><br>
<font size="2" face="sans-serif">2. </font><font size="4" face="Calibri">Ray will develop a similar top level view of the SOIS layered service architecture</font><br>
<font size="2" face="sans-serif">3. </font><font size="4" face="Calibri">Yonghui will develop a view of the “Plug and Play” parts of the architecture</font><br>
<font size="2" face="sans-serif">4. </font><font size="4" face="Calibri">Peter will distribute the RASDS template and SCCS-ARD materials</font><br>
<font size="2" face="sans-serif">5. </font><font size="4" face="Calibri">Peter will setup a Doodle poll for the next meeting, either 12 or 19 Jan 2016</font><br>
<font size="1" face="sans-serif">[attachment "Figures Used in SCCS-ARD-v0x9-29July14.pptx" deleted by Mario Merri/esoc/ESA]
</font><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>
</div>
</div>
</blockquote>
</span>
</body>
</html>