<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
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:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{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.EmailStyle23
{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:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:590358806;
mso-list-type:hybrid;
mso-list-template-ids:-1152192562 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1931616245;
mso-list-type:hybrid;
mso-list-template-ids:-1498878456 -480453058 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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">Hi Wes,<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">You brought it nicely to the point.<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">Answer to 1) would be – in my opinion – definitely yes. On the other hand, maybe there would be some implementations at some agencies where they do not care about that, so they do not need that. This was I think
the thought for SM-1 to make these fields optional. But I do not know if it still holds. In principle ALL of scheduling systems I know, use (in that way or another) status information which is exchanged between user and provider. And I soon we think about
automation services in future, it will be obligatory anyhow. <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 only reason to have that optional, which comes to my mind, is that there might be some other bilateral way (different file format, notification or carrier pigeons) to exchange the status/state.
<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">Regarding 2) we have had already several discussions about that in last years, and every time we ended with the simplest solution having just one relevant state (SCHEDULED). There are two aspects:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">a)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">The partially/fully was related in SM-1 to the fact, that one Service Package could stretch over longer time period and thus actually include several physical bookings/contacts/actions. The PARTIALLY
was an option to show the user, that some of the actions/contacts related to the SP has been already scheduled, but there are still some left (can’t be scheduled yet, due to whatever reasons). As we focused the SP in our new attempt to more or less one contact/pass,
there is no more reason for that. Either the SP is scheduled or it is not. Very binary…. ;-)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">b)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">The story behind TENTATIVE is more complicated, and I think also more controversial among providers/agencies and users. In previous SM-1 and some agencies (also partially in DLR) such status of the
pass booking is used. It should give the user some kind of the answer “yes, we booked you in this time slot, but keep in mind, that there is some other mission/customer who has higher priority, thus he might kick you out”. Typically the status changes to “SCHEDULED”
after some deadline is reached (many talk about change of “priority based scheduling” into “first come, first serve scheduling” – this may happen for example 1 week ahead of the pass). Such booking with tentative confirmations gives especially for the provider/stations
some profit, because they get better usage of their antenna. On the other hand, for many missions I work with, such status is useless, because the mission wants to know 100% sure they got the pass, so that they can set up on-board timeline. There is also some
combination of both possible, if the mission buys itself just highest priority, it will be scheduled for sure.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:18.0pt"><span style="color:#1F497D">We agreed in working group, that the case with no tentative confirmation is the one being most making sense, thus decided not to pursue the TENTATIVE branch. Nevertheless,
maybe it would not be bad to consider some optional parameter which could convey such additional information for projects/users/providers who want to play around with TENTATIVE.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:18.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So, finally, the parameters would look like this:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">servicePackageStatus (obligatory, with
</span><span style="color:#1F497D">CREATED, SCHEDULED, ALTERNATIVE, EXECUTING, REJECTED, CANCELLED, ABORTED, ARCHIVED)</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">servicePackageStatusAnnotation (optional, with either Enum or even better String, where bilaterally some additional “substatus” can be agreed – for example “TENTATIVE” or “TENTATIVE, PRIO 5” or whatever….)</span><span style="color:#1F497D"><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">What are your thoughts?<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">Marcin<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:18.0pt;text-indent:18.0pt"><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 #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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""> Eddy, Wesley M. (GRC-LCN0)[MTI SYSTEMS, INC.] [mailto:wesley.m.eddy@nasa.gov]
<br>
<b>Sent:</b> Montag, 1. Oktober 2018 18:25<br>
<b>To:</b> Gnat, Marcin; smwg@mailman.ccsds.org<br>
<b>Subject:</b> RE: AI2017-0512-54: Create draft Tech Note on State Machines<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Marcin, I like your proposal to fix and simplify the way that the service package status is indicated.<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">To be clear, we currently have two fields:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">servicePackageResultStatus (can be TENTATIVELY SCHEDULED, PARTIALLY SCHEDULED, or FULLY SCHEDULED)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">servicePackageResultType (can be NEW, UPDATE, ALTERNATE, FLEXIBILITY CHANGE)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">And both are optional.<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">If I understand correctly, you think it would be better to consolidate to a single more explicit indication of the service package state, like:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">servicePackageStatus (can be CREATED, SCHEDULED, ALTERNATIVE, EXECUTING, REJECTED, CANCELLED, ABORTED, ARCHIVED)<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">This seems basically good to me. Two questions I have are:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">1)</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Should the servicePackageStatus be mandatory? I think so. I’m not sure why the original book had the equivalent fields as optional.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:#1F497D">2)</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">How are the 3 degrees of being scheduled that the old fields conveyed (tentative, partial, or full) reflected in the state machine?<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>
<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 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b><a href="mailto:Marcin.Gnat@dlr.de">Marcin.Gnat@dlr.de</a><br>
<b>Sent:</b> Monday, October 1, 2018 8:32 AM<br>
<b>To:</b> <a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a><br>
<b>Subject:</b> [Smwg] AI2017-0512-54: Create draft Tech Note on State Machines<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a name="Gruß"></a>Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And here is another debt which I had in terms of an Action Item. Please see attached draft Tech Note on State Machines. Also some small corresponding presentation (content is more or less same).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Uploaded to CWE as well:<o:p></o:p></p>
<p class="MsoNormal">Doc:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/StateMachinesForCSSMInformationEntities_TechNote-v0x1.docx">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/StateMachinesForCSSMInformationEntities_TechNote-v0x1.docx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">PowerPoint:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/AI2017-0512-11_Service_Package_State_Machine_20181015.pptx">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/AI2017-0512-11_Service_Package_State_Machine_20181015.pptx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">MagicDraw UML File:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/SP_StateMachine_20180925.zip">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Administration/Inter%20Recommendation/Models/Information%20Entities%20State%20Machine%20Model/SP_StateMachine_20180925.zip</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I saw Erik had planned some time during Fall Meetings for the State Machine topic, so maybe it would be not bad if you could drop an eye on this stuff (one more doc to be reviewed – add to the list of “Berlin Pointers” ;-). It’s not long
though… so maybe you can make it…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards<o:p></o:p></p>
<p class="MsoNormal">Marcin<o:p></o:p></p>
</div>
</body>
</html>