<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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: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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:325599006;
mso-list-template-ids:925006682;}
@list l0:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@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: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 lang="DE">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal">below some of my answers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have a good weekend<o:p></o:p></p>
<p class="MsoNormal">Marcin<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> SMWG <smwg-bounces@mailman.ccsds.org> <b>On Behalf Of
</b>Colin.Haddow@esa.int<br>
<b>Sent:</b> Donnerstag, 25. Februar 2021 13:29<br>
<b>To:</b> smwg@mailman.ccsds.org<br>
<b>Cc:</b> Jean.Schuetz@esa.int<br>
<b>Subject:</b> [cssm] Use of SICF in Service Management - again<o:p></o:p></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 been checking how the SICF is originated at ESOC and it appears that generally (but not always) the Service provider is proposing the SICF and the managed parameters set up.
Not sure how other agencies handle this.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">It does however leave me somewhat confused with how the SICF is supposed to fit in with the SMURF and SPDF, e.g.</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">Who submits the SICF?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">[Marcin] Normally it would go from Mission (User) to the Station (Provider). In many cases we (DLR) do that. There are some (mostly small) projects, which
do not care (have no know-how in that area), and we set it up for them. In general I’d say, currently the one decides (and defines SICF) who has the biggest network / connections to manage (which typically is some Control Center with attached Network Operations
Center -> ESTRACK, etc…). So, for example:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:18.0pt">
<i><span style="color:red">If ESA approaches us to have a support from Weilheim, for us (DLR) it is a Mission/Customer/User who tells us what SICF (or actually SICF contents) we shall use (</span></i><i><span style="font-family:Wingdings;color:red">à</span></i><i><span style="color:red">
ESA, User). From ESA point of view, it may be ESTRACK who decides actually internally, and this can be seen as “provider” provided SICF (</span></i><i><span style="font-family:Wingdings;color:red">à</span></i><i><span style="color:red"> ESTRAC, Provider).
So, I’d say It actually depends on actual visibility of an enterprise model.<o:p></o:p></span></i></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">Does a SICF needs to be referenced in a Service Package Request?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">[Marcin] I’d say yes (how otherwise one should know which SICF shall be used for requested Service Package / Pass?)<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">Does the SICF get referenced at the Service Package level, or do we need to specify the SI at service level (possibly in both SMURF and SPDF)?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">[Marcin] As already written in one of my previous mails, DLR typically uses separate SI (or actually even multiple SI’s!) per Service (whereas one must admit,
the “service” as such is not really divided to separate carriers, etc, as in SM given). One could say, in other words, the actual individual SI’s define services.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">BUT, I admit, this may complicate things, and also for the phase-over, we could agree to have one FILE per all SI’s (and then bilaterally agreed what it
should exactly look like).<o:p></o:p></span></p>
<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">How do we handle the different approaches to the SICF, i.e. some agencies have multiple SIs per SICF, others have a one to one mapping of SI to SICF?</span>
<o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">[Marcin] As written above, I’d propose to have one SI-Package per Service Package, and the contents of this package file shall be bilaterally agreed. It
could be than ESA-DSN-Like single SICF file, or it could be a zip file with individual SI’s. That way we do not obstruct current world of SI’s and we get the most important aspect – binding to the Service Package.</span><o:p></o:p></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">Do we need to come up with a standard SICF format? (I hope the answer to this is no...)</span><o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">[Marcin] Assuming we do it as I propose above – no.</span><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Perhaps we need a splinter webex or 2 to try and thrash this out ?</span>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:red">[Marcin] Not that I have too much time for extra meetings, but it may be good, as long as we focus on this specific topic (i.e. I would not like to discuss if the permanent SI’s are better or not, because in my opinion,
this is not the point).</span><o:p></o:p></p>
<p class="MsoNormal"><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<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 is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>