<span style=" font-size:10pt;font-family:sans-serif">Hello<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I will join late
the telecon today. I should be able to make it for the DDOR item in your
agenda at 17H55 CET.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I have inserted
my answer in </span><span style=" font-size:14pt;color:#800080;font-family:Georgia"><i> colour</i></span><span style=" font-size:10pt;font-family:sans-serif">
in your text.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">We have been practicing
DDOR support for years, internal ESA and cross agency support. implementation.
We have a unique sequence of event template, we use standardise file naming
convention for the raw data. It is simple and it works. I am reluctant
to the idea of increasing complexity unless their is a benefit.</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">I
see the DOR tones on/off times as part of the event sequence (which references
the configuration profile). Also, from local conversation, it appears that
name of the raw observation files matters for processing by the correlators.
That could also go in the configuration profile.</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#800080;font-family:Georgia"><i>-
The time pattern is changing frequently for DDOR. If you want to have an
event sequence for each, you will have to create one for nearly each new
support. It may be nice at conceptual level, but is a burden in operation.
I recommend the approach to have a single DDOR sequence, with durations
as parameters.</i></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#800080;font-family:Georgia"><i>-
The raw observation file name is not part of the request in the recommended
practice CCSDS 506.0-M-2. File name of navigation product matters
for processing, but that's covered in the relevant standard books. Does
it really make sense to leave freedom to the user to select the file name
of the result in a booking request ? The same logic would then applies
to all navigation product. Do you consider leaving a file name entry for
ranging, Doppler, meteo and so on... .</i></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">I
see the scan pattern as being part of the SMURF -- a question I have here
is whether or not the scan pattern can be template-a-sized such that it
is always referred to by some sort of identifier. My sense from the DSN
side is that this is not the case as the quasar(s) being utilized very
depending upon the mission trajectory etc. I think it will be interesting
to discuss further on this at the teleconference tomorrow if you're available.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#800080;font-family:Georgia"><i>-
The Quasars to be used change for each DDOR request. In our implementation
the Quasar name are anonymized to Q1/Q2/Q3, depending of how many Quasar
are requested in a given support. It is up to the requester to provide
the orbital predicts of the real Quasar under the relevant code name.</i></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif"><br>
<br>
Regards<br>
________________________________________<br>
Mar</span><span style=" font-size:10pt;color:red;font-family:sans-serif"><b>C</b></span><span style=" font-size:10pt;font-family:sans-serif">in
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></p>
<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">"Barkley,
Erik J (US 3970)" <erik.j.barkley@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"EXTERNAL-Unal,
Martin P (9110-Affiliate)" <Martin.Unal@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Service Mgmt WG" <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">17/06/2020
00:02</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">RE:
[EXTERNAL] Re: [cssm] Fw: DDOR configuration template</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Hello
Marcin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Here
are some quick responses as to how I think this likely fits within the
service management.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">I
see the DOR tones as being part of the configuration profile.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">I
see the DOR tones on/off times as part of the event sequence (which references
the configuration profile). Also, from local conversation, it appears that
name of the raw observation files matters for processing by the correlators.
That could also go in the configuration profile.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">I
see the scan pattern as being part of the SMURF -- a question I have here
is whether or not the scan pattern can be template-a-sized such that it
is always referred to by some sort of identifier. My sense from the DSN
side is that this is not the case as the quasar(s) being utilized very
depending upon the mission trajectory etc. I think it will be interesting
to discuss further on this at the teleconference tomorrow if you're available.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SMWG <smwg-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Martin.Unal@esa.int<b><br>
Sent:</b> Wednesday, May 27, 2020 01:26<b><br>
To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><b><br>
Cc:</b> CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><b><br>
Subject:</b> [EXTERNAL] Re: [cssm] Fw: DDOR configuration template</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Hello</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Here is a version 2 based on yesterday telecon discussion.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I have changed the configuration item names to</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">
ddor_configuration</span><span style=" font-size:10pt;font-family:Arial">
and </span><span style=" font-size:10pt;color:#000080;font-family:Verdana">spacecraft_configuration</span><span style=" font-size:10pt;font-family:Arial">.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><br>
<configuration_profile</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">service</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="deltaDor"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- DDOR configuration element defines which type of DDOR configurarion
shall be used to configure the ground station --></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- This can be used to select which type of tones to be used, how
many DL band,...--></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- The attribute and their value will probably be provider specific
--></span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><br>
<ddor_configuration</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">name</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="DDOR1"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- The spacecraft_configuration can be used to convey information
relevant for the station configuration on a per DL basis (if needed)--></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- To be open to future multi band DDOR, It is suggest to have an
dlIndex--></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#808000;font-family:Verdana"><br>
<!-- The attribute and their value will probably be provider specific
--></span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><br>
<spacecraft_configuration</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">dlIndex</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="1"
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">band</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="Xband"
</span><span style=" font-size:10pt;color:#008080;font-family:Verdana">transmitter</span><span style=" font-size:10pt;color:#800080;font-family:Verdana">="1"</span><span style=" font-size:10pt;color:#000080;font-family:Verdana">/></span><span style=" font-size:11pt;font-family:Calibri"><br>
<br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
The main part to agree with the DDOR team concern the DDOR parameter. They
are not really concerned by the configuration aspect. This is more an issue
between the flight control team and the provider.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I am still not sure where you want to have it in a SMURF request.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Will it be in provider specific parameter ? In the configuration profile
(902x05-Simple-conf-profile-Mission-Agrt) ?</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
<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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:#0082bf;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p><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>