<span style=" font-size:10pt;font-family:sans-serif">Hi Erik,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
with respect to your points;</span>
<br>
<ol>
<li value=1><span style=" font-size:10pt;font-family:sans-serif">I'm open
to suggestion what we should call them. COMMS is the current working name
but its easy enough to change.</span>
<li value=2><span style=" font-size:10pt;font-family:sans-serif">If you
look in the Service Management Common Data Entities book you'll see that
the SrvMhtAbstractEvent class (from which all the planning events are derived)
inherits the optional identifier from the Abstract Event Class.</span>
<li value=3><span style=" font-size:10pt;font-family:sans-serif">Guilty
as charged, for some reason I don't have anything about this in my notes,
so completely forgot about it.</span>
<li value=4></ol><span style=" font-size:10pt;font-family:sans-serif">Cheers
for now,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Colin</span>
<br><span style=" font-size:10pt;font-family: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; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Barkley,
Erik J (3970)" <erik.j.barkley@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Colin.Haddow@esa.int"
<Colin.Haddow@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
SMWG ML(smwg@mailman.ccsds.org)" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">01/02/2018
19:43</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">RE:
[Smwg] 902x2-w0.16 - Planning Information Formats - Updated draft</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">Colin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">I
have managed to take a quick review of the updated recommendation in the
schema and it looks like it is going the right direction. I do have some
comments.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">1)
Perhaps we could consider classifying these as "geometry"
(short of communication geometry) events or something like that rather
than “comms”. The rationale is that eventually we do have a future
issue or issues of the PIF planned with further planning types which include
data rate and volume estimates. I think something like this could
perhaps be more directly considered as communication (presumably getting
into things like link margin etc.) whereas the information we have currently
in the PIF is really about the geometry surrounding the communication and
not so much the communication per se</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">2)
I saw the identifier element optionally included in selected
event definitions in the instance example but I don't see a corresponding
parameter listed in the UML model? </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">3)
I don't really see the planetary surface other than earth
use case being accommodated yet in the PIF. I suspect that has to do with
it being back in July that this was discussed and it isn't necessarily
on the "front burner" so to speak. Attached is a PowerPoint presentation
that has some suggestions for inclusion of this use case. My rationale
for suggesting the inclusion of this use case is that there has been a
fair amount of progress in the SIS area with regard to DTN and I think
we will need to address this use case sooner or later and as I think that
that it is not that much of a stretch sooner would be better.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">Perhaps
we can discuss these at the upcoming working group teleconference.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><a name=_MailEndCompose></a><span style=" font-size:12pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SMWG [</span><a href="mailto:smwg-bounces@mailman.ccsds.org"><span style=" font-size:11pt;font-family:Calibri">mailto:smwg-bounces@mailman.ccsds.org</span></a><span style=" font-size:11pt;font-family:Calibri">]
<b>On Behalf Of </b>Colin.Haddow@esa.int<b><br>
Sent:</b> Tuesday, January 30, 2018 5:30 AM<b><br>
To:</b> CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><b><br>
Subject:</b> [Smwg] 902x2-w0.16 - Planning Information Formats - Updated
draft</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:10pt;font-family:Arial">Dear
all,</span><span style=" font-size:12pt;font-family:Times New Roman"> </span><span style=" font-size:10pt;font-family:Arial"><br>
I've just uploaded
the latest draft of the Planning Information Formats Book to CWE, This
contains the updates discussed at San Antonio and Den Haag. 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><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
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><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
The Planning Information Formats document, model and schemas can be found
at the following URLs.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Document: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats.doc"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats.doc</u></span></a><span style=" font-size:10pt;font-family:Arial"><br>
Model: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip</u></span></a><span style=" font-size:10pt;font-family:Arial"><br>
Schemas: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20Schema.zip"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20Schema.zip</u></span></a><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Cheers for now,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Colin</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<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; </span><a href=mailto:colin.haddow@esa.int><span style=" font-size:10pt;color:blue;font-family:Arial"><u>colin.haddow@esa.int</u></span></a><span style=" font-size:10pt;font-family:Arial"><br>
---------------------------------------------------------------------------------------------------------</span><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message and any attachments are intended for the use of the addressee or
addressees only.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">The
unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">content
is not permitted.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">If
you received this message in error, please notify the sender and delete
it from your system.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">Emails
can be altered and their integrity cannot be guaranteed by the sender.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">Please
consider the environment before printing this email.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New"> [attachment
"Response to AI 2017-0512-02 (Mars Relay) 01-Aug-2017.pptx" deleted
by Colin Haddow/esoc/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p><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>