<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
h1
{mso-style-link:"Heading 1 Char";
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:21.6pt;
text-indent:-21.6pt;
page-break-before:always;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:14.0pt;
font-family:"Times New Roman",serif;
text-transform:uppercase;
mso-fareast-language:EN-US;}
h2
{mso-style-link:"Heading 2 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:28.8pt;
text-indent:-28.8pt;
page-break-after:avoid;
mso-list:l0 level2 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
text-transform:uppercase;
mso-fareast-language:EN-US;}
h3
{mso-style-link:"Heading 3 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
text-indent:-36.0pt;
page-break-after:avoid;
mso-list:l0 level3 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
text-transform:uppercase;
mso-fareast-language:EN-US;}
h4
{mso-style-link:"Heading 4 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:45.0pt;
text-indent:-45.0pt;
page-break-after:avoid;
mso-list:l0 level4 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
h5
{mso-style-link:"Heading 5 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:53.85pt;
text-indent:-53.85pt;
page-break-after:avoid;
mso-list:l0 level5 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
h6
{mso-style-link:"Heading 6 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:63.0pt;
text-indent:-63.0pt;
page-break-after:avoid;
mso-list:l0 level6 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
{mso-style-link:"Heading 7 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:72.0pt;
text-indent:-72.0pt;
page-break-after:avoid;
mso-list:l0 level7 lfo1;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;
font-weight:bold;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
{mso-style-name:"Heading 9\,Index Heading 1";
mso-style-link:"Heading 9 Char";
margin:0cm;
text-align:center;
text-indent:0cm;
page-break-before:always;
page-break-after:avoid;
mso-list:l0 level9 lfo1;
font-size:14.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;
font-weight:bold;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-link:"Heading 2";
font-family:"Times New Roman",serif;
text-transform:uppercase;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:284123723;
mso-list-template-ids:-1452143918;}
@list l0:level1
{mso-level-style-link:"Heading 1";
mso-level-text:%1;
mso-level-tab-stop:21.6pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:14.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level2
{mso-level-style-link:"Heading 2";
mso-level-text:"%1\.%2";
mso-level-tab-stop:28.8pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level3
{mso-level-style-link:"Heading 3";
mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level4
{mso-level-style-link:"Heading 4";
mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:45.35pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level5
{mso-level-style-link:"Heading 5";
mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:54.0pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level6
{mso-level-style-link:"Heading 6";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:63.35pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level7
{mso-level-style-link:"Heading 7";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level8
{mso-level-number-format:alpha-upper;
mso-level-suffix:none;
mso-level-text:"ANNEX %8";
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:14.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level9
{mso-level-start-at:9;
mso-level-number-format:alpha-upper;
mso-level-style-link:"Heading 9";
mso-level-suffix:none;
mso-level-text:%9NDEX;
mso-level-tab-stop:79.2pt;
mso-level-number-position:center;
margin-left:0cm;
text-indent:0cm;
mso-ansi-font-size:14.0pt;
mso-ascii-font-family:"Times New Roman";
mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-DE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear Wes, Erik and CSTS Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I had a discussion with the MOIMS AD to sort out the 2 conditions he raised for the FRM Magenta Book. Would you as Book Captain, CSS Area Director or CSTS WG member agree to the following addition (in red) for section
1.4 Applicability:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">------------------------------------------------------------------------------------<o:p></o:p></span></p>
<h2 style="margin-left:0cm;text-indent:0cm;mso-list:none"><a name="_Toc88205257"><span lang="EN-US">1.4 Applicability</span></a><span lang="EN-US"><o:p></o:p></span></h2>
<p class="MsoNormal">This Recommended Practice is applicable to ESLT-provided cross support services that are based on CCSDS Cross Support Transfer Services and Cross Support Service Management that model functionality in terms of Functional Resources.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i><span style="color:red">If the Functional Resources would be used in a different context than an ESLT, e.g. in on-board scenarios, the relevant CCSDS recommendations to exchange the information defined by Functional Resources shall be
used. For on-board scenarios that would be MO M&C services as per [XYZ]. <o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The concepts and specifications of Functional Resources, Functional Resource Sets, and Functional Resource Strata may by applicable to other node types, but such applicability must be determined on an implementation basis
<span lang="EN-US">[…]<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">------------------------------------------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">I am not particular happy about the addition, as the applicability and scope of the current book is clearly only for ESLT, CSTSs and CSSM standards – but before entering lengthy discussions and delaying the book, I could
accept it. There are in fact discussions to use FRs for on-board communication functions and yes, it is not wrong to say that relevant CCSDS standards should be used then. It may just be a bit too early to reflect on that.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please let me know your opinion. BTW, no feedback is rated as violent agreement
</span><span lang="EN-US" style="font-family:"Apple Color Emoji"">😉</span><span lang="EN-US">.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">FYI: In the attached document I marked with comments the places, which in my mind already address the 2 MOIMS PIDs.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Holger<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">P.S. Here is the MOIMS AD PID:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">1) Section 1.3 "Scope" states that the scope is <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">limited to IOAG service cat 1 and 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Then Section 2.2.1 "FUNCTIONAL RESOURCES AS <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">ABSTRACTIONS OF REAL RESOURCES" reads:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">"FRs are abstract representations of the <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">functionality needed to provide space <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">communication and tracking services, defined at a <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">level of granularity sufficient to specify the <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">configuration parameters, monitored parameters, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">and notifiable events associated with that functionality.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">FRs exist to represent such information as it <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">applies to a cross support interface. If a <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">processing function does not have unique <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">monitored parameters, notifiable events, or any <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">configuration parameters that need to be set <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">(possibly through configuration profiles), <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">queried, or reconfigured (via real-time control <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">directives), then it does not have an FR to <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">represent it. It should be noted that only one of <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">these facets needs to be present in order for a <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">function to need to be represented by an FR."<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">It should be clarified in the text that the FRs <o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">shall be limited to hw/sw that is immediately and <o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">directly related to communication</span></b><span style="color:black;mso-fareast-language:EN-GB"> and shall not <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">be used for abstract representation of other <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">devices onboard or on the ground, e.g. a Camera <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">or a Gyro.... for such devices MO services should <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">be the prime choice for abstract representation <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">of the interface. This is consistent with the so called "London agreement".<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">2) It should be also clarified in the text <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">(Section 1.3 Scope?) that, when it goes
<b>on-board <o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">even for the RF elements, the aspects of TM/TC <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">and operations in general should be handled <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">through MO M&C services rather than using FRM for <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">monitored parameters, notifiable events, or any <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">configuration of those devices. This is <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">consistent with CCSDS 371.0-G-1 APPLICATION AND SUPPORT LAYER ARCHITECTURE<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
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).
</body>
</html>