<span style=" font-size:10pt;font-family:sans-serif">Hello<br>
<br>
Recent ESA missions use multiple instances per file, and individual
files per functional group.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Individual instance
covers for various combination of service (Timely/Complete) for each VC.
Complemented by cltu and offline as needed.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">The functional
group is used to differentiate different band (e.g. X/KA) or mode (e.g.
Safe vs nominal)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">e.g. JUICE</span>
<br><span style=" font-size:10pt;font-family:sans-serif">FG1
13 SIs</span>
<br><span style=" font-size:10pt;font-family:sans-serif">FG2
6 Sis</span>
<br><span style=" font-size:10pt;font-family:sans-serif">FG3
12 Sis</span>
<br><span style=" font-size:10pt;font-family:sans-serif">FG4
6 Sis</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">This means 4 files
for each SLE providers.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Just for ESTRACK,
3 stations with prime+backup = 24 files for a total of 222 SIs.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
CFDP makes the picture a bit more complex as we have CFDP provider at the
station which also connect to the SLE providers with their own SIs.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">We have no fsp
usage so far. But on paper it allows more complex scenario.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">However, the usage
is quite simple in term of support request. (at least for ESTRACK)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Our tailoring
defines a high level support type which refer to an agreed configuration.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Most mission have
only one, the most complex has 5.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">e.g.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">TTC_1,
X/X</span>
<br><span style=" font-size:10pt;font-family:sans-serif">TTC_2
S/X (MEX)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">DDOR_1
X</span>
<br><span style=" font-size:10pt;font-family:sans-serif">DDOR_2
Ka (Bepi)</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">SICF are loaded
as required by the support type.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">On top of the
support type, some parameters can be used to specify TM/TC rate or the
DDOR sequence. But this as no influence on the SICF usage.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">In summary, internally
to ESTRACK, the "service type" string is sufficient to refers
to all SICF needed for the support.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <br>
________________________________________</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Colin.Haddow@esa.int</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">smwg@mailman.ccsds.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">23/02/2021
19:03</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[cssm]
Use of SICF in service managemnt</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SMWG"
<smwg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Dear all,</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
just working
thro' what using the SICF means for the SMURF and SPDF, if my memory serves
me correctly there should be one and only one SICF used during a pass.
This being the case it would imply that per service package there would
be at most one SICF referenced. Also I think that the SICF would be needed
for Offline Services.</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Are these valid assumptions ?</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Cheers for now,</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Colin</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
<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; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------</span>
<br><tt><span style=" font-size:12pt">This message is intended only for
the recipient(s) named above. It may contain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemination
is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (dpo@esa.int).<br>
</span></tt><tt><span style=" font-size:10pt">_______________________________________________<br>
SMWG mailing list<br>
SMWG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/smwg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt>
<br>
<br><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>