<span style=" font-size:10pt;font-family:sans-serif">Hello</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
<br>
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">The
differences, elaborated as comments in the XML instance document, are:</span>
<br><span style=" font-size:10pt;font-family:sans-serif">1.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Removal
of the service indication as the DDOR service would already be indicated
in the SMURF</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">OK
- redundant information shall be removed</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">2.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Removal
of the account of scan targets as each target has an ordinal number assigned
to it so it is quite trivial to determine the number of targets if that
is needed (and less error-prone)</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">OK
- redundant information shall be removed</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">3.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">addition
of a reference to the carrier configuration profile for the spacecraft(s)
participating in the DDOR observation (in turn this will indicate the frequency
band as well as provide information for the DOR tones from the spacecraft(s))</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">OK
- <b>I suggest to group the targets description at the start.</b> </span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">This
to remove all possibility to have inconstent data.</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">Target
description shall point to the SANA name, may include the relevant "flux"
or configuration ("carrierRef") information</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">DDOR
target per scan only refers to the target named defined to remove redundant
information (possibly inconsistent) in each call</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">4.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">The
absolute start time for the scan pattern has been added -- this will help
to verify that the scan pattern time fits with the set of activities scheduled</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">Where
are defined the "activity times" ? If the information is already
present in the SMURF or in the service package, it shall not be present
again in the DDOR description. Otherwise each team will look at different
value, inconsistence will not be detected and service will be lost.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">5.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">a
slew time that can be stated for each target rather than a uniform slew
time – this may allow for optimization such that a DDOR measurement that
could not be achieved via fixed slew times can be achieved if the overall
amount of time spent slewing is reduced (of course this would be subject
to negotiation, but the purpose here is to allow for expression of the
information and not to specify behavior)</span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia"> I
disagree. The DDOR service description <u>has to specify the behaviour</u>.
DDOR is typically a service which can be implemented by multiple party.
If you give freedom on the slew time, one will optimise the slew, the other
not. Measurement will be taken at different times and correlation will
not be possible. </span>
<br><span style=" font-size:14pt;color:#800080;font-family:Georgia">What
the point of optimising 30s per slew ? I don't believe 5 minute extra have
ever prevented feasibility of a DDOR. Low benefit, high cost. "optional"
items are cost and complexity drivers for the implementation. If you say
you need it, it shall be present all the time. Otherwise, better drop it.</span><span style=" font-size:10pt;font-family:sans-serif">
<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Here is a xml
view of my proposal. I have left a "</span><span style=" font-size:10pt;color:red;font-family:sans-serif">slew
per scan</span><span style=" font-size:10pt;font-family:sans-serif">"
attribute and the </span><span style=" font-size:10pt;color:red;font-family:sans-serif">absoluteStartTime
</span><span style=" font-size:10pt;font-family:sans-serif">for the discussion.</span>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<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">"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>, "Border, James
S (US 335D)" <james.s.border@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">16/07/2020
23:32</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">DDOR
Scan Pattern format proposal</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
Martin (and my apologies for the earlier incorrect spelling),</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">The
DDOR WG Chair (Jim Border) and I have had an exchange with regard to the
proposed scan pattern for inclusion in the SMURF. Attached please
find a proposed scan pattern format -- a sample XML instance document and
a pictorial representation. This is largely based on the pattern you have
proposed. </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">The
differences, elaborated as comments in the XML instance document, are:</span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">1.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Removal
of the service indication as the DDOR service would already be indicated
in the SMURF</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Removal
of the account of scan targets as each target has an ordinal number assigned
to it so it is quite trivial to determine the number of targets if that
is needed (and less error-prone)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">addition
of a reference to the carrier configuration profile for the spacecraft(s)
participating in the DDOR observation (in turn this will indicate the frequency
band as well as provide information for the DOR tones from the spacecraft(s))</span>
<br><span style=" font-size:10pt;font-family:sans-serif">4.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">The
absolute start time for the scan pattern has been added -- this will help
to verify that the scan pattern time fits with the set of activities scheduled</span>
<br><span style=" font-size:10pt;font-family:sans-serif">5.
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia">a
slew time that can be stated for each target rather than a uniform slew
time – this may allow for optimization such that a DDOR measurement that
could not be achieved via fixed slew times can be achieved if the overall
amount of time spent slewing is reduced (of course this would be subject
to negotiation, but the purpose here is to allow for expression of the
information and not to specify behavior)</span>
<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">My
sense is that we are close to a very good workable format. I look forward
to your comments.</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: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>
Martin.Unal@esa.int <Martin.Unal@esa.int> <b><br>
Sent:</b> Wednesday, June 17, 2020 06:29<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> RE: [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>
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><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
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:Arial">
in your text.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
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><span style=" font-size:11pt;font-family:Calibri">
<br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
</span><span style=" font-size:14pt;color:#004080;font-family:Georgia"><br>
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><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<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:Arial"><br>
<br>
Regards<br>
________________________________________<br>
Mar</span><span style=" font-size:10pt;color:red;font-family:Arial"><b>C</b></span><span style=" font-size:10pt;font-family:Arial">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>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Barkley,
Erik J (US 3970)" <</span><a href=mailto:erik.j.barkley@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>erik.j.barkley@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"EXTERNAL-Unal,
Martin P (9110-Affiliate)" <</span><a href=mailto:Martin.Unal@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Martin.Unal@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"CCSDS
Service Mgmt WG" <</span><a href=mailto:smwg@mailman.ccsds.org><span style=" font-size:9pt;color:blue;font-family:Arial"><u>smwg@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">17/06/2020
00:02</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">RE:
[EXTERNAL] Re: [cssm] Fw: DDOR configuration template</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<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:12pt"><b>From:</b>
SMWG <</span><a href="mailto:smwg-bounces@mailman.ccsds.org"><span style=" font-size:12pt;color:blue"><u>smwg-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:12pt">>
<b>On Behalf Of </b></span><a href=mailto:Martin.Unal@esa.int><span style=" font-size:12pt;color:blue"><u>Martin.Unal@esa.int</u></span></a><span style=" font-size:12pt"><b><br>
Sent:</b> Wednesday, May 27, 2020 01:26<b><br>
To:</b> Barkley, Erik J (US 3970) <</span><a href=mailto:erik.j.barkley@jpl.nasa.gov><span style=" font-size:12pt;color:blue"><u>erik.j.barkley@jpl.nasa.gov</u></span></a><span style=" font-size:12pt">><b><br>
Cc:</b> CCSDS Service Mgmt WG <</span><a href=mailto:smwg@mailman.ccsds.org><span style=" font-size:12pt;color:blue"><u>smwg@mailman.ccsds.org</u></span></a><span style=" font-size:12pt">><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:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Hello<br>
<br>
Here is a version 2 based on yesterday telecon discussion.</span><span style=" font-size:12pt">
</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:12pt">
</span><span style=" font-size:10pt;color:#000080;font-family:Verdana"><br>
<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:12pt">
</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:12pt">
</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:12pt"> </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:12pt"> </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:12pt">
</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:12pt">
</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:12pt"> </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:12pt"> </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:12pt"><br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
<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:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
I am still not sure where you want to have it in a SMURF request.</span><span style=" font-size:12pt">
</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:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<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"><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:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).[attachment
"ProposedDDOR-ScanPatternFormat-eb-16Jul20.xml" deleted by Martin
Unal/esoc/ESA] [attachment "ProposedScanPatternFormat-eb-16Jul20.pptx"
deleted by Martin Unal/esoc/ESA] </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>