<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 0 5 0 0 0 0 0 0 0;}
@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:11.0pt;
font-family:"Calibri",sans-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";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Courier;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">All:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Recall that at the recent Spring 2018 meetings, Area Director Mario Merri requested that we consider how the MOIMS standards might be used to support the LOP-G (Lunar Operations Platform
- Gateway). As we were requested, we had a couple of discussions about this. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Mario has consolidated material from the MOIMS WGs, and his submission to the LOPG-G management is linked below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">MOIMS <moims-bounces@mailman.ccsds.org> on behalf of "Mario.Merri@esa.int" <Mario.Merri@esa.int><br>
<b>Date: </b>Monday, May 28, 2018 at 4:13 AM<br>
<b>To: </b>"Lupisella, Mark L. (GSFC-5810)" <mark.l.lupisella@nasa.gov>, "Schlesinger, Adam M. (JSC-XS111)" <adam.m.schlesinger@nasa.gov>, "Frank.De.Winne@esa.int" <Frank.De.Winne@esa.int>, "Philippe.Schoonejans@esa.int" <Philippe.Schoonejans@esa.int>, "Ludovic.Duvet@esa.int"
<Ludovic.Duvet@esa.int>, "james.schier-1@nasa.gov" <james.schier-1@nasa.gov>, "Tai, Wallace S (9000)" <wallace.s.tai@jpl.nasa.gov>, "philip.e.liebrecht@nasa.gov" <philip.e.liebrecht@nasa.gov><br>
<b>Cc: </b>"Andrea.Accomazzo@esa.int" <Andrea.Accomazzo@esa.int>, "Michael.Schmidt@esa.int" <Michael.Schmidt@esa.int>, "cesg@mailman.ccsds.org" <cesg@mailman.ccsds.org>, "Francois.Allard@esa.int" <Francois.Allard@esa.int>, "james.afarin@nasa.gov" <james.afarin@nasa.gov>,
"moims@mailman.ccsds.org" <moims@mailman.ccsds.org>, "Thomas.Reiter@esa.int" <Thomas.Reiter@esa.int>, "Michael.McKay@esa.int" <Michael.McKay@esa.int><br>
<b>Subject: </b>[MOIMS] Use of CCSDS Standards for Mission Operations Interoperability in the LOP-G Program<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Dear Colleagues,</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">Mission operations is the program aspect that ties all systems and components together. As such, mission operations concepts and standards should be part of the very early planning phases of any
mission. It is recommended that the International Deep Space Interoperability Standards document suite include a volume dedicated to mission operations interoperability standards applicable to both space and ground segment systems.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">The Deep Space Interoperability Standards team should carefully consider adopting standards from the broad set of operations-related standards developed within the Mission Operations and Information
Management Services (MOIMS) Area of the Consultative Committee for Space Data Systems (CCSDS).</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">MOIMS standards are dedicated to interoperability services and data formats defining a basic set of interfaces, interactions and services common in the Space and Ground domains. A general trend is
the movement of intelligent applications from Ground to Space and the standards are an enabler for this movement due to their common nature and technology abstractions.
</span><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">Reasons for early inclusion of CCSDS MOIMS standards in the Deep Space Programs include:</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- Hard lessons learned in the early phases of the ISS. The lack of upfront definition of operations standards has resulted in a very complicated ground segment with duplication of the similar
interfaces </span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- The set of MOIMS standards currently available includes key standards that are commonly used in most of space missions today.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- LOP-G is already considering several related CCSDS standards for communications and security, and the same rationale is applicable for the use of MOIMS Standards.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- MOIMS Services focus on the interface boundaries, with minimal invasion into the hosting systems. Therefore, they are easily usable on new or legacy and space and ground systems.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- MOIMS Standards simplify the integration of systems (legacy and new applications) and support heterogeneous communications protocols, therefore facilitating and simplifying inter-agency
co-operation.</span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- MOIMS Standards are developed internationally and approved by the 11 CCSDS space agencies. They are the technical foundation for smooth international cooperation.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- Over time, mission operations concepts and procedure will mature and change, driving the LOP-G system in ways not currently considered. Mature interface and service standards can help simplify
system redirection / expansion.</span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- The MOIMS service framework allows easy expansion of new capabilities as locally-defined services or as new Mission Operations (MO) standards through CCSDS. In particular, its modular architecture
enables inclusion of new services at a very late stage of project development with no need to redesign the already developed components/applications.
</span><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">- MOIMS standards facilitate avoidance of unneeded software developments.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">The MOIMS area is very interested in providing its set of standards to the LOP-G community. For this reason, should we identify the need of a specific standard that is not covered by the available
set, we are ready to be flexible and, if agreed by the participating agencies, adapt the MOIMS workplan to the LOP-G needs. Clearly, LOP-G agency staff are welcomed to contribute to the work.
</span><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">We also would like to re-mark the fact that the MOIMS includes the “Telerobotics Working Group” that unfortunately has been dormant for a couple of year due to lack of interest from the agencies.
We think instead that standards in this field would be critical in a multi-asset and multi-organization set up as the LOP-G one. We would very welcome a revived interest by space agencies boosted by the LOP-G interest in order to re-start the work of this
working group.</span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">A whitepaper has been prepared to provide an overview of available mission operations standards that can directly benefit large missions such as the Lunar Orbital Platform – Gateway. The paper has
been submitted as comment to the call made by the International Deep Space Standards group (</span><a href="https://www.internationaldeepspacestandards.com/comment/"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">https://www.internationaldeepspacestandards.com/comment/</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif">,
but it is not clear if the on-line submission was successful as no positive feedback was received) and has been posted to the public CCSDS MOIMS Site at</span>
<br>
<a href="https://cwe.ccsds.org/moims/docs/MOIMS%20Area/LOP-G/180525%20CCSDS%20MOIMS%20Input%20to%20LOP-G%20Final.pdf"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/moims/docs/MOIMS%20Area/LOP-G/180525%20CCSDS%20MOIMS%20Input%20to%20LOP-G%20Final.pdf</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif">
</span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">We would appreciate if you could consider our comment and pass it to whoever may be concerned.</span>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<br>
<b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Mario Merri Brigitte Behal</span></b>
<br>
<b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">MOIMS Area Director MOIMS Deputy Area Director</span></b>
<br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">European Space Agency (ESA Centre National d'Etudes Spatiales (CNES)<br>
Robert Bosch Strasse 5 18 Avenue Edouard Belin<br>
D-64293 Darmstadt, Germany F-31401 Toulouse Cedex 9, France<br>
E-mail: </span><a href="mailto:Mario.Merri@esa.int"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Mario.Merri@esa.int</span></a><u><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:blue"> </span></u><span style="font-size:12.0pt;font-family:"Arial",sans-serif">
E-mail: </span><a href="mailto:Brigitte.Behal@cnes.fr"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Brigitte.Behal@cnes.fr</span></a><u><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:blue">
</span></u><o:p></o:p></p>
<pre>This message is sent for information and/or discussion purposes only.<o:p></o:p></pre>
<pre>It shall neither be binding nor construed as constituting a commitment for ESA.<o:p></o:p></pre>
<pre>It is intended only for the recipient(s) named above.<o:p></o:p></pre>
<pre>It may contain proprietary information and/or protected content.<o:p></o:p></pre>
<pre>Any unauthorised disclosure, use, retention or dissemination is prohibited.<o:p></o:p></pre>
<pre>If you have received this e-mail in error, please notify the sender immediately.<o:p></o:p></pre>
<pre>ESA applies appropriate organisational measures to protect personal data.<o:p></o:p></pre>
<pre>In case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</body>
</html>