<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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: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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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.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.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Georgia",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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">Marcin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">I can certainly sympathize with your concern about getting into special cases. I think part of the analysis around this will be to determine whether or not this is
truly a special case. As I understand it the time windows in some sense are related to what ESA might call "standing orders". But I think we will indeed have to have a further conversation as to how SN employs these. And then I think we will need to compare
and contrast to the closest mechanisms of various agencies and then tease out whether or not this moves forward as part of the “main body” of the SMURF or as some agency specific extension or as something else.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:12.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Marcin.Gnat@dlr.de <Marcin.Gnat@dlr.de> <br>
<b>Sent:</b> Wednesday, March 28, 2018 4:15 AM<br>
<b>To:</b> wesley.m.eddy@nasa.gov; Colin.Haddow@esa.int; smwg@mailman.ccsds.org; Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Subject:</b> RE: scheduling windows<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Dear all,<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">Without recalling very good what we talked about this during den Haag meetings (it was for sure my jetlag ;-), I wanted to give some comment from my side to scheduling windows.<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">As I understand, this idea covers some specific use of the Space Network, whereas users may send to the provider a bunch of time windows in which they are going to use specific service. And as I understand it
is somehow equivalent to the direct schedule request (or multiple schedule requests in that term) with specific tolerances. Scheduling Windows give user some more nice functionality to user, as they can decouple the decision on visibilities from the actual
service request.<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">There will be already my first question: we now have SERVICE requests in SM, and we try to get away from schedule requests or pass requests as typically used. Are such multiple scheduling windows stretching over
single service? Or one should see it rather as multiple services (accidentally same type) one after another? In the latter case, there would be really no difference to the “normal” service or service package request.<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">Secondly, my impression is that with that we put here an actual user (or provider) functionality into the interface. I’m afraid with such rather “special” cases, we will blow our standards again to the sizes
of SM-1 (or even larger as a matter of fact). I know someone could say this part is “optional” and so on, but still when implementing we have to somehow take care of that.
<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">We will definitely discuss it during Spring Meetings, but in general I’d opt for keeping things simple. The point of the common standard is to have a common version everybody understands, and not to have collection
of versions from everybody. And finally, as our SM is “Extensible” it should be easily extensible for specific uses for individual users. So maybe this would be the way to go…<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"><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"> SMWG [<a href="mailto:smwg-bounces@mailman.ccsds.org">mailto:smwg-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Eddy, Wesley M. (GRC-LCI0)[MTI SYSTEMS, INC.]<br>
<b>Sent:</b> Dienstag, 20. März 2018 16:41<br>
<b>To:</b> <a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>; CCSDS SMWG ML (<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>)<br>
<b>Cc:</b> Barkley, Erik J (JPL-3970)[Jet Propulsion Laboratory]<br>
<b>Subject:</b> [Smwg] scheduling windows<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Colin et al, here is a description of scheduling windows (TSWs) as used in the Space Network today, which may help in understanding the use case.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is text in the SNUG that describes how users can either use the start times in their requests, or TSWs to make sure their services are scheduled within timeslots that make sense:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864">A MOCC is responsible for ensuring its own customer platform-to-TDRS visibility prior to adding a schedule event. The MOCC may do this directly by submitting schedule requests with start
time tolerances that comply with customer platform-to-TDRS visibility requirements or indirectly by submitting TDRSS Scheduling Windows (TSWs) to the NCCDS and then submitting schedule requests that specify that they are to fit within these TSWs. Use of TSWs
makes it feasible to submit schedule requests that specify TDRS flexibility and with start time tolerances that exceed a single TDRS view.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The further description of how TSWs relate to the scheduling process is:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864">Each TSW message contains TSWs applicable to a specified time period for a single customer-defined TSW set for a single TDRS. The TSWs may be transmitted before, after, or at the same
time as the schedule requests that depend on the TSWs. However, if a schedule request requires TSWs from a particular TSW set for a particular TDRS during a certain time period, it cannot be processed if applicable TSWs have not been received.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864">Each TSW set contains the TSWs applicable to a particular combination of customer visibility constraints based on factors such as antenna type, power, and frequency. Each customer may
define as many TSW sets as needed, and may define new TSW sets at any time without negotiation with the NCCDS.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#203864">Each SSC
</span><i>(an “SSC” in the SN is equivalent to a configuration profile for us)</i>
<span style="color:#203864">either specifies the TSW set applicable to the scheduling of the service specified by that SSC, or specifies that TSWs are not applicable. A TSW set is a re-specifiable parameter.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If it is useful, I can provide a description of the fields in a TSW, but the short story relevant to Colin’s question about included/excluded times is that a TSW set consists of the included windows, and there is not a notion of excluded
windows. If not in the included windows, then a time is understood to be excluded.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>