<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=utf-8">
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:745230617;
mso-list-template-ids:-477737170;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1722897608;
mso-list-type:hybrid;
mso-list-template-ids:566786414 -1049049336 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1:level1
{mso-level-start-at:17;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-fareast-font-family:Calibri;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear Mario,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It will probably not come as any surprise that I hold an opinion on this that diverges from the one you stated. I have pointed out, from the outset, that co-evolving these two tightly coupled standards was a recipe for trouble.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If I read this correctly, you are proposing to put the MP&S BB, which depends entirely on the SM&C BB for it’s data formats, message structures, and service interfaces, out for CESG and Agency review
<b><u>before</u></b> the SM&C BB is finalized. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To put this in simple terms, that seems a lot like an author asking to publish a book written in a new language before the details of the language are settled and agreed. Doesn’t seem like a very good idea to me.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m not interested in slowing forward progress, but I really think that this is out of order and is likely to make more work for all involved.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To my knowledge, nowhere else in CCSDS have we ever done this. The closest analogy that comes to mind is in the CSS where the new CSTS standards all depend upon the CSTS specification framework (SFW). The SFW (CCSDS 921.1-B-1) was created
first and published in April 2017. This was then used to create the MD-CSTS standard (CCSDS 922.1-B-1) which was also published in April 2017 and then used for the TD-CSTS. The SFW had to be updated when a new forward service was added, and the SFW v2 was
published in Feb 2021 and then the FF-CSTS (CCSDS 922.3-B-1), that used that new version, was published in April 2021.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have, in the SCCS-ARD MB, CCSDS 901.1-M-1, used some “forward references” to not yet finalized standards. But this is an “encyclopedia style” recommended practice, and these forward references are all carefully marked [FUTURE]. I suppose
if you wanted to adopt some similar [<u>we are not yet certain of this</u>] markings in this MP&S BB that you could do that, but I would not recommend it.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Reply-To: </b>Mario Merri <Mario.Merri@esa.int><br>
<b>Date: </b>Tuesday, February 15, 2022 at 12:19 PM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Cc: </b>Peter van der Plas <Peter.van.der.Plas@esa.int>, Mehran Sarkarati <Mehran.Sarkarati@esa.int><br>
<b>Subject: </b>[EXTERNAL] [CESG] Mission Planning and Scheduling Blue Book agencies review approach<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Dear CESG,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">the MP&S WG has proposed to MOIMS to initiate the Agency Review of their BB before the publication of the updated MAL BB, on which the MP&S BB depends. The goal
is to hopefully speed up publication of both BBs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Marc and I had some internal discussion and investigation with both the MP&S WG and the SM&C WG and we concluded to support this request and consult with the CESG
to avoid false expectations and unnecessary work.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Our conclusion comes from the following points:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Both WGs have closely worked together in the update of the MAL BB.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">To the best of the knowledge of both WGs, the agreed changes to the MAL BB are final and fully compatible
with the MP&S BB.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Should new significant discrepancies appear during the finalisation of the MAL BB, the MP&S WG agrees to
update the document and go through another Agency Review.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">It seems to us a win-win approach to the benefit of CCSDS. Please let us know any objections before end of February.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif">Marc & Mario<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Peter van der Plas <<a href="mailto:Peter.van.der.Plas@esa.int">Peter.van.der.Plas@esa.int</a>>
<br>
<b>Sent:</b> 27 January 2022 11:51<br>
<b>To:</b> Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>; Duhaze Marc <<a href="mailto:Marc.Duhaze@cnes.fr">Marc.Duhaze@cnes.fr</a>><br>
<b>Subject:</b> Mission Planning and Scheduling Blue Book agencies review approach<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear MOIMS,</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">The MP&S Blue Book is now nearing completion. However, the current work is based on some assumptions related to the evolution of the MO Services, where parallel work is ongoing
in the SM&C WG.</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">The WG however considers it beneficial to initiate the agencies review of the Blue Book in the near term, in order not to delay our work and to ensure that the envisaged publication
date remains feasible. The WG understands the risk that in case the current assumptions on the evolution of the MO Services are incorrect, an update of the Blue Book and therefore a second agencies review may be required.</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">In order to be clear towards external reviewers about the status of the Blue Book, the WG intends to provide a detailed list of assumptions and open issues together with the Blue
Book, either in its introduction or as a separate addendum, whichever preferred.</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">The WG believes that the above mentioned risk is sufficiently mitigated by the fact that the work done in SM&C is closely followed by MP&S experts, and that the Blue Book is kept
fully in line with the latest draft MAL specification. However, some artefacts such as the MP&S Service Specification can only be completed and validated once the implementation of the updated MAL API is made available by SM&C. This will merely impact the
prototyping, which is currently being completed based on an older implementation of the MAL API.</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">In any case, the current Blue Book is complete in terms of specification of services and data types. In addition, file based exchange is supported, including the XML Schemas required
for file validation.The WG expects to have the Blue Book and accompanying SANA artefacts available as input to the agencies review by the end of March 2022.</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Could you please let me know if MOIMS agrees with the proposed approach for the MP&S Blue Book agencies review?
</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards,</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter</span><span lang="EN-GB"><br>
<br>
<br>
</span><b><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">ESA - European Space Agency</span></b><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
<b>Peter van der Plas</b></span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
EGSE and Ground Systems section (TEC-SWG)<br>
Directorate of Technology, Engineering and Quality<br>
<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299, NL-2200 AG Noordwijk, The Netherlands</span><u><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#8F8F8F"><br>
</span></u><span lang="EN-GB"><a href="mailto:Peter.van.der.Plas@esa.int"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#8F8F8F">Peter.van.der.Plas@esa.int</span></a></span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> |
</span><span lang="EN-GB"><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!fob_ep1UDJkU4Ii221CkQDhId0tp0keCMlzWhtCaE1E7H0YvHu3_f1TiQOsWd6rnyzZAYqW2$"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#8F8F8F">www.esa.int</span></a></span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
Phone +31 71 565 5848 | Fax +31 71 565 5420 | Mobile +31 6 51 93 44 30</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">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).
<o:p></o:p></span></p>
</div>
</body>
</html>