<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
        {font-family:Georgia;
        panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        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";}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        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",serif;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Georgia",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:397635120;
        mso-list-type:hybrid;
        mso-list-template-ids:-360515124 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Dear Martin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Now that I finally have a copy of what you sent to Colin, of course, I have some comments :-)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">First, the instance document is not quite proper XML -- at least as Oxygen on this end looks at it. Please see the screenshot below. Attached is what I believe to
 be a properly formed version of the instance document.  <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">To set the context, as I recall, the basic question was whether or not we needed to look at another standard or augmentation to the SMURF to accommodate the interagency
 ground sequence for conducting a DDOR observation. I think the answer tends to be yes to the general question here. Presumably the spacecraft event sequence will cover when DOR tones are on/off but then of course there is the scan pattern and that has to be
 coordinated between multiple agencies. I think the instance you have submitted is a step in the right direction.  Here are some comments, questions, observations:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">It seems like this is something of a cross between a template and a fully stated instance. For each of the targets to be in the scan pattern, there appears to be a presumption that the scan will start
 at BOT plus the delay. Is it fair to assume that the DDOR supports for a mission will always fit this kind of pattern?  I suspect the answer is no and that there are either multiple patterns.  At a minimum, depending upon whether the groundstation is the "incoming"
 groundstation with regard to communications geometry or the "outgoing" groundstation then this would probably also have to have something that is stated as the offset relative to the EOT? Or perhaps we should think about allowing absolute times to be stated?<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">Recevier_2 -- this seems like an internal concern to the implementation -- I think for international standard the main thing would be to have the scan pattern identified and not which particular (open-loop)
 receiver is being used.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">Given that DDOR requires a fair amount of interagency coordination and there are constraints with regard to communication geometries and quasar of visibility, should there be some sort of provision
 for indicating the ground stations involved in this? I'm not sure that this is really needed but then again it does seem like if we are doing this interagency the data standard has to allow for being very precise and clear as to the exact apertures being requested
 to support the scan pattern -- that of course could be indicated in the aperture constraints of the SMURF.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Assuming you can attend our teleconference on May 26, I look forward to discussing this further.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><img width="1029" height="751" style="width:10.7187in;height:7.8229in" id="Picture_x0020_1" src="cid:image001.png@01D62F76.529B8AA0"></span><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></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> Thursday, May 7, 2020 08:18<br>
<b>To:</b> smwg@mailman.ccsds.org<br>
<b>Subject:</b> [EXTERNAL] [cssm] Fw: DDOR configuration template<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"><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>
---------------------------------------------------------------------------------------------------------<br>
</span><br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">----- Forwarded by Colin Haddow/esoc/ESA on 07/05/2020 17:17 -----</span>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Martin Unal/esoc/ESA</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Colin Haddow/esoc/ESA@ESA</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Holger Dreihahn/esoc/ESA@ESA</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">06/11/2019 17:24</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">DDOR configuration template</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello<br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have drafted a proposal of xml layout for DDOR support based on our experience on ESTRACK</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This need to be tune to the SMURF, but all the element of information shall be there.</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">From our operational experience, using the formulare in the magenta leave room to build invalid contradicting entries.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">And it did happen many time.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This minimum set of value, together with the element contain in the SMURF request could be used to write the old text format in the magenta book (see below) to support backward compatibility if needed.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For memory</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><b><span style="font-size:12.0pt;font-family:"Times New Roman",serif">C1 EXAMPLE 1</span></b>
<br>
<b><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><Maven-Abbrev>_DDOR_2014_228_2014_250_v2.des</span></b>
<br>
<tt><span style="font-size:8.0pt">$ddorGroundObservationsEventSequence</span></tt>
<br>
<tt><span style="font-size:8.0pt">RequestId = 2014-205T15:50:00;</span></tt> <br>
<tt><span style="font-size:8.0pt">FormatVersion = 1;</span></tt> <br>
<tt><span style="font-size:8.0pt">orginatingOrganization = DSN;</span></tt> <br>
<tt><span style="font-size:8.0pt">MissionId = <Maven-Abbrev>;</span></tt> <br>
<tt><span style="font-size:8.0pt">$START</span></tt> <br>
<tt><span style="font-size:8.0pt">ddorConfigProfileId = 202F2;</span></tt> <br>
<tt><span style="font-size:8.0pt">ScIndex____ScId____DorOn____DorOff =</span></tt>
<br>
<tt><span style="font-size:8.0pt">SC01 <Maven-Abbrev> 2014-228T02:25:00 2014-228T03:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">QuIndex____QuId____QuFlux =</span></tt> <br>
<tt><span style="font-size:8.0pt">QU01 P_1504-167 0.52</span></tt> <br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">TrkStnId____TrackStart____TrackEnd =</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site1>-<Apper1> 2014-228T02:25:00 2014-228T03:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site2>-<Apper2> 2014-228T02:25:00 2014-228T03:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site3>-<Apper3> 2014-228T02:25:00 2014-228T03:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">DdorEpoch = 2014-228T02:25:00;</span></tt> <br>
<tt><span style="font-size:8.0pt">ScanNum____ScanSource____ScanStart____Duration =</span></tt>
<br>
<tt><span style="font-size:8.0pt">1 SC01 00:00:00 00:01:00</span></tt> <br>
<tt><span style="font-size:8.0pt">2 QU01 00:03:00 00:05:00</span></tt> <br>
<tt><span style="font-size:8.0pt">3 SC01 00:10:00 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">4 QU01 00:18:00 00:07:30</span></tt> <br>
<tt><span style="font-size:8.0pt">5 SC01 00:27:30 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">6 QU01 00:35:30 00:07:30</span></tt> <br>
<tt><span style="font-size:8.0pt">7 SC01 00:45:00 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">8 QU01 00:53:00 00:05:00</span></tt> <br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">$END</span></tt> <br>
<tt><span style="font-size:8.0pt">$START</span></tt> <br>
<tt><span style="font-size:8.0pt">ddorConfigProfileId = 202F2;</span></tt> <br>
<tt><span style="font-size:8.0pt">ScIndex____ScId____DorOn____DorOff =</span></tt>
<br>
<tt><span style="font-size:8.0pt">SC01 <Maven-Abbrev> 2014-250T01:25:00 2014-250T02:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">QuIndex____QuId____QuFlux =</span></tt> <br>
<tt><span style="font-size:8.0pt">QU01 P_1519-273 1.12</span></tt> <br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">TrkStnId____TrackStart____TrackEnd =</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site1>-<Apper1> 2014-250T01:25:00 2014-250T02:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site2>-<Apper2> 2014-250T01:25:00 2014-250T02:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt"><Site3>-<Apper3> 2014-250T01:25:00 2014-250T02:25:00</span></tt>
<br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">DdorEpoch = 2014-250T01:25:00;</span></tt> <br>
<tt><span style="font-size:8.0pt">ScanNum____ScanSource____ScanStart____Duration =</span></tt>
<br>
<tt><span style="font-size:8.0pt">1 SC01 00:00:00 00:01:00</span></tt> <br>
<tt><span style="font-size:8.0pt">2 QU01 00:03:00 00:05:00</span></tt> <br>
<tt><span style="font-size:8.0pt">3 SC01 00:10:00 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">4 QU01 00:18:00 00:07:30</span></tt> <br>
<tt><span style="font-size:8.0pt">5 SC01 00:27:30 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">6 QU01 00:35:30 00:07:30</span></tt> <br>
<tt><span style="font-size:8.0pt">7 SC01 00:45:00 00:06:00</span></tt> <br>
<tt><span style="font-size:8.0pt">8 QU01 00:53:00 00:05:00</span></tt> <br>
<tt><span style="font-size:8.0pt">;</span></tt> <br>
<tt><span style="font-size:8.0pt">$END</span></tt> <br>
<tt><span style="font-size:8.0pt">$$EOF</span></tt><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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> <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>