<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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><!--[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="color:#1F497D">Erik,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If I read your response, correctly, it sounds like you are saying that the provisional plan is for the future. However, that’s the *<b>only</b>* thing that’s called out in the current Planning Data Formats book.
Methinks there’s some straightening out of terminology that needs to be done.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Barkley, Erik J (3970) [mailto:erik.j.barkley@jpl.nasa.gov]
<br>
<b>Sent:</b> Thursday, January 28, 2016 10:20 PM<br>
<b>To:</b> John Pietras; Colin.Haddow@esa.int<br>
<b>Cc:</b> CCSDS SMWG ML (smwg@mailman.ccsds.org)<br>
<b>Subject:</b> RE: Comments on draft Planning Data Formats (CCSDS 902.2-W-0.06)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">John,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for a good set of inputs. I will just quickly note, that I think the time line business was probably predicated on that being stood up in the SE Area, but it has in fact never happened and I don’t see
any formal timeline effort happening in the foreseeable future. So yes, this probably needs to be cleaned in both GB and this BB.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The plan for some time has been to have 2 issues of the planning book and you raise an interesting point as to whether this first issue of the planning data book needs to be "forward-looking" or not. My thinking
is that standards really should only state what it is they truly define and if there is a bunch of future looking "vacuous" stuff such as the provisional plan which really won't exist until issue two of the planning data book then it should be removed. It's
absolutely fine for the concept book to have the full plan for what the future version will look like so in this case we can keep this information in the GB, but remove it from this BB.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Pietras [<a href="mailto:john.pietras@gst.com">mailto:john.pietras@gst.com</a>]
<br>
<b>Sent:</b> Thursday, January 28, 2016 8:44 AM<br>
<b>To:</b> <a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>; Barkley, Erik J (3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Cc:</b> CCSDS SMWG ML (<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>) <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> Comments on draft Planning Data Formats (CCSDS 902.2-W-0.06)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Colin and Erik,<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Here are my comments on the current draft of the Planning Data Formats book:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">1.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Typo – the document number is listed as “920…” throughout, instead of the correct “902…”. It looks like all of these document numbers are controlled from the “Document number” item in the Advanced Properties: Custom menu.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">2.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>The last sentence of 1.1.2.1 is unfinished – “Depending on the operational procedures of the Provider CSSS, the Provisional Plan”<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">3.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>The reference to the Concept Green Book (1.8 [2]) needs to be updated the published version (no longer draft).<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">4.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>This item affects the Concept Green Book as well as the Planning Data Formats. Erik may already be aware of these issues vis-à-vis the Concept Green Book and may be planning to address them issues in his update of that Green Book.<br>
<br>
According to section 8.2 (c) of the Concept Green Book, the Planning Data Formats book was to specify 7 different Info Entities: Planning Request, Provisional Plan, Communications Geometry, Sustainable Data Rate and Volume Estimates, RFI, Resource Conflicts,
and Cost Estimates. Discounting Planning Request (which will transfer to the SMURF book), this still leaves 6 different Info Entities within the covers of the Planning Data Formats book.
<br>
<br>
However, the Green Book goes on define the contents of the Provisional Plan as predicted communications geometry events, sustainable data rate and volume estimate events, predicted radio frequency interference events, predicted resource conflict events, and
cost estimates – i.e. the content of the 6 other Info Entities. As it stands, the way the Concept Green Book is currently written, one could exchange, for example, communications geometry info via either the Provisional Plan Info Entity or the separate, dedicated
Communications Geometry Info Entity.<br>
<br>
The current Planning Data Formats White Book defines only one Info Entity, the Provisional Plan. At first glance it might appear that only the Provisional Plan IE is needed, since it contains the content of the other IEs. However, it’s a bit more complicated
than that (of course it is). The Provisional Plan is defined as being communicated from the Provider CSSS to the Mission. For the sustainable data rate and volume estimate events, predicted resource conflict events, and cost estimates, the associated IEs are
also always generated by the Provider CSSS and communicated to the Mission, so those IEs could be simply folded into the Provisional Plan and discarded as separate IEs, which is what the current Planning Data book apparently does.<br>
<br>
However, the Communications Geometry and RFI IEs can also be generated by the Mission and sent to the Provider CSSS. This is outside the scope of the Provisional Plan IE. To cover these cases, the Planning Data Formats book still needs to define separate Communications
Geometry and RFI Info Entities.<br>
<br>
One possible set of simplifications/re-organizations would be to (a) get rid of the separate Sustainable Data Rate and Volume Estimates, Resource Conflicts, and Cost Estimates Info Entities in the Concept Green Book, and fold their content into the Provisional
Plan; (b) also include in the content of the Provisional Plan that of the Communications Geometry and RFI Info Entities; (c) keep the Communications Geometry and RFI Info Entities as separate Info Entities, but only for the purpose of conveying info from Missions
to Provider CSSSes; and (d) add Communications Geometry and RFI Info Entity specifications to the Planning Data Formats book. That would cover all of the use cases envisioned by the Concept Green Book.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">5.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Typo – in table 3-3, the reference to the Provisional Plan section of the Concept Green Book should be to section 5.4, not 5.3.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in">6.<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>The Concept Green Book states that the Provisional Plan (5.4), Communications Geometry (5.7), Sustainable Data Rate and Volume Estimates (5.8), RFI (5.9), Resource Conflicts (5.10), and Cost Estimates (5.11) are all “instantiation[s] of the Event Timeline
stereotype, which is described in 6.4” of the Concept Green Book. There is no mention of an Event Timeline stereotype anywhere in the Planning Data Formats book. This stereotype was touted in the Concept Green Book at the extensibility mechanism for Planning
Data Information Entities. If that is the case, then structure of the IEs in the Planning Data Formats book should reflect that. If not, then section 6.4 of the Concept Green Book and all references to it should be deleted.<o:p></o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:13.5pt;font-family:"Times New Roman","serif";color:black;background:white">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times New Roman","serif";color:black;background:white"><br>
<a href="https://filter.gst.com/canit/b.php?i=01QbDjXaI&m=9564970a0753&c=s" target="canit_note">Spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01QbDjXaI&m=9564970a0753&c=n" target="canit_note">Not spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01QbDjXaI&m=9564970a0753&c=f" target="canit_note">Forget previous vote</a></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
</div>
</div>
</body>
</html>