<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)">
<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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@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";}
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:12.0pt;
font-family:"Times New Roman",serif;}
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-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.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-family:"Georgia",serif;color:#1F497D">Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I finally had a chance to more thoroughly analyze the planning information that is used here (NASA/JPL) for Mars relay coordination. The good news is that it appears to basically
map out into the PIF format as it currently is defined. However, not surprisingly, there are some details and considerations to go over. Attached please find a presentation about this. I propose to put this on the agenda for the July 31<sup>st</sup> teleconference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",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 <smwg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Colin.Haddow@esa.int<br>
<b>Sent:</b> Friday, June 29, 2018 7:20 AM<br>
<b>To:</b> CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Cc:</b> Matteo Renesto <matteo.renesto@telespazio-vega.de><br>
<b>Subject:</b> [Smwg] 902x2-w0.17 - Planning Information Formats - Updated draft<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">Dear all,</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
I've just uploaded the latest draft of the Planning Information Formats Book to CWE, This contains the updates discussed at Gaithersburg (essentially dealing with the landed asset case). I've also uploaded the updated UML model and Schemas.
Note that the UML model and the schemas also contain the updates required for the revised Service Management Common Data Entities Book.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Also included in the Schemas are a couple of examples for the Planning Information, along with the extra schema required to get the extended Planning Information to work.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The Planning Information Formats document, model and schemas can be found at the following URLs.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Document: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats.doc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats.doc</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Model: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Schemas: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats%20-%20Schema.zip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.17%20-%20Planning%20Information%20Formats%20-%20Schema.zip</span></a><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Colin</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; <a href="mailto:colin.haddow@esa.int">colin.haddow@esa.int</a><br>
---------------------------------------------------------------------------------------------------------</span><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 (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</body>
</html>