<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: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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-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;}
/* List Definitions */
@list l0
{mso-list-id:1963463610;
mso-list-template-ids:-188197080;}
@list l0:level1 lfo3
{mso-level-start-at:2;}
@list l0:level1 lfo4
{mso-level-start-at:3;}
@list l0:level1 lfo5
{mso-level-start-at:4;}
@list l0:level1 lfo6
{mso-level-start-at:5;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Below, please find some initial responses from my perspective.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-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 [mailto:smwg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Colin.Haddow@esa.int<br>
<b>Sent:</b> Thursday, September 08, 2016 9:13 AM<br>
<b>To:</b> CCSDS SMWG ML(smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Cc:</b> Holger.Dreihahn@esa.int<br>
<b>Subject:</b> [Smwg] Service Management Utilisation Request Formats - Draft w0.03<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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I've just uploaded the latest draft of the Service Management Utilisation Request Formats book to CWE. This has been substantially reworked since Cleveland.. The document and model
can be found at the following URLs.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Document </span><a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20and%20Service%20Request%20Book/Service%20Management%20Utilization%20Request%20Formats%20902x9-w0.03.doc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20and%20Service%20Request%20Book/Service%20Management%20Utilization%20Request%20Formats%20902x9-w0.03.doc</span></a>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Model </span><a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20and%20Service%20Request%20Book/Service%20Management%20Utilization%20Request%20Formats%20902x9-w0.03.mdzip"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20and%20Service%20Request%20Book/Service%20Management%20Utilization%20Request%20Formats%20902x9-w0.03.mdzip</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">During the reworking I've come up with the following questions.</span>
<o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Do we need to differentiate between online and offline configuration profiles ?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I suspect that we will have to accommodate this – at least to the degree that agencies continue to
move off-line data via SLE (vs a file transfer). Its probably a bit different for CSTS (but nobody is talking about RAF-CSTS) as, to the best of my knowledge CSTS has the ability for a service instance to span both on-line and off-line. Perhaps that can
be part of one profile for CSTS (if and when we have things like RAF-CSTS; not sure if this has a bearing on FF-CSTS).
<o:p></o:p></span></p>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Is it necessary to allow for multiple scenarios to be specified in one service request ?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My understanding from the Cleveland meetings is that there is the notion of a "simple" service package.
As I recall, the simple service package defaults to a single scenario and so it does not necessarily have to be overtly defined. However, to the best of my knowledge, missions in conjunction with TTC networks have preplanned contingencies for providing service
and that multiple scenarios will address this. I suppose its possible to define a contingency service package, which would achieve the same thing, but we will need to consider the ramifications (e.g, expression in the schedule; de-contingency-a-fying one
service package in favor over another, etc.).<o:p></o:p></span></p>
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Do we need to allow Configuration Profile Constraints to be specified in both online and offline cases ?</span>
<o:p></o:p></li></ol>
<ol start="4" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo5">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Do we need the Configuration Profile Constraints at all, or has this all now been moved to the Event Sequence ?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I am on the hook to work an effort to see what moving temporal constraints solely to the domain of
Event Sequence looks like. I believe the conclusion at the Cleveland meetings was to try and simplify to the extent possible the configuration profile such that we have the various concerns map to one information entity rather than reappearing in multiple
information entities (with different semantics, etc) <o:p></o:p></span></p>
<ol start="5" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo6">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Are the constraints defined for offline sufficient (or even necessary) ?</span><o:p></o:p></li></ol>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I propose that we discuss these in Rome as I'm not going to be able to attend any of the remaining WebExs before the meeting.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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 and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</body>
</html>