<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)">
<!--[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: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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:TimesNewRomanPS;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:"Courier New \,serif";
panose-1:2 7 3 9 2 2 5 2 4 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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",serif;}
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-style-priority:99;
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.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-weight:bold;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{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:1405953356;
mso-list-type:hybrid;
mso-list-template-ids:74733886 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{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 l0: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",serif;}
@list l0: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 l0: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 l0: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",serif;}
@list l0: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 l0: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 l0: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",serif;}
@list l0: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">
<div class="WordSection1">
<p class="MsoNormal">Hi Dan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It’s interesting that the scope of SM&C was allowed to expand outside the scope of what was allowed for the area that it resides in. This has been an on-going bone of contention and I do not expect it to abate any time soon. That said,
and as you point out, MOIMS already has a full plate of items that are strictly ground based, and it has a WG membership that understands that domain. This continuing pressure to try and force MO services and frameworks into a RT on-board environment seems
to me to be really ill advised and counter to the charter for the area as a whole. Do note that the other WG in MOIMS, DAI, Nav, and MP do not have charter scope in the on-board environment, nor does MOIMS as a whole.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think the only way forward is to treat this as an Area Charter issue and adjudicate it in the CESG.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Dan Smith <danford.s.smith@nasa.gov><br>
<b>Date: </b>Thursday, April 11, 2019 at 7:01 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Sam Cooper <sam@brightascension.com>, "Mehran.Sarkarati@esa.int" <Mehran.Sarkarati@esa.int>, Mario Merri <Mario.Merri@esa.int><br>
<b>Cc: </b>SEA-SA <sea-sa@mailman.ccsds.org>, "Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><br>
<b>Subject: </b>RE: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Peter,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt">The on-board application of MO is clearly in the charter of the SM&C working group. See the text below (with my comments in red).
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">But I do agree with you that SOIS is much better suited to handling on-board interfaces. My personal view is that until, and unless, MO is widely adopted for ground-ground inter-agency interoperability for mission
operations interactions, no effort should be expended by the SM&C working group to promote the on-board use of MO.
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>If MO is defined too broadly, SM&C will never complete the MO standards.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>The SM&C WG has discussed the fact that on-board software has its own unique considerations and that the SM&C team is comprised of ground software folks, and not flight software folks.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>SOIS is a WG of on-board software experts.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>NASA has not identified any missions or engineering groups asking for MO on-board to solve issues.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="10%" style="width:10.26%;margin-left:.5in">
<tbody>
<tr>
<td valign="top" style="padding:.75pt .75pt .75pt .75pt"></td>
<td valign="top" style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The scope of SM&C includes:
<br>
<br>
1.) Operational concept: definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of
<span style="background:yellow;mso-highlight:yellow">both ground and space segments</span>.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:red">Note that this item does not require the use of MO on-board, since we can control space segments from the ground.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
2.) Core Set of Services: definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Archiving
and Retrieval, Flight Dynamics, Mission Planning, Automation, and Performance Evaluation.
<br>
<br>
3.) Application-layer information: definition of the standard information set to be exchanged for SM&C purposes.
</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Times New Roman",serif">Rationale for Activity</span></b><o:p></o:p></p>
</td>
<td valign="top" style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The ability to standardize the interfaces for spacecraft monitoring and control (SM&C)
<span style="color:red">[the use of simple data format message exchanges without the use of MO framework and services is the next big push for SM&C]</span> will
<span style="background:yellow;mso-highlight:yellow">allow significant saving in the development of the flight components</span> and the ground segment of future space missions. In fact, it will be possible to use standardized SM&C infrastructure systems, to
seamlessly transfer data across systems, and to adopt commercial-off-the-shelf applications for monitoring and control. The high level goal of this standardization effort is to make economies by:
<br>
<br>
1.) allowing interoperability with partner system and infrastructure. <br>
<br>
2.) reducing the risk of space missions by re-using systems and operational concepts, thus increasing their reliability.
<br>
<br>
3.) <span style="background:yellow;mso-highlight:yellow">facilitating the development of generic (infrastructure) on-board and on ground</span> software that can be shared by multiple projects via simple re-configuration
<br>
<span style="color:red">This is the line that puts MO on-board.</span></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:red"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">4.) applying the SM&C approach and systems throughout all mission phases and to other M&C domains (e.g., ground stations, control centers, test facilities, etc.)</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">=========================</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><i><span style="color:#1F497D">Dan Smith</span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">NASA/GSFC</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">Code 580</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">Bldg 23, Room E443</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">8800 Greenbelt Road</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">Greenbelt, MD 20771</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D">301-286-2230</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="mailto:Dan.Smith@nasa.gov"><b><span style="font-size:9.0pt;color:#0563C1">Dan.Smith@nasa.gov</span></b></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:9.0pt;color:#1F497D"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b><i><span style="font-size:9.0pt;color:#1F497D">Believe the science. There are no “alternative facts”.</span></i></b><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b>From:</b> Shames, Peter M (312B) [mailto:peter.m.shames@jpl.nasa.gov]
<br>
<b>Sent:</b> Wednesday, April 10, 2019 4:16 PM<br>
<b>To:</b> Sam Cooper <sam@brightascension.com>; Mehran.Sarkarati@esa.int; Mario.Merri@esa.int<br>
<b>Cc:</b> SEA-SA <sea-sa@mailman.ccsds.org>; Wilmot, Jonathan J. (GSFC-5820) <jonathan.j.wilmot@nasa.gov>; Smith, Danford S. (GSFC-5800) <danford.s.smith@nasa.gov><br>
<b>Subject:</b> Re: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Sam, Mario, and Mehran,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Thank you for finally providing these inputs. I have reviewed them and I think I understand where you are coming from and what changes you wish to effect in this SOIS document.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">To be completely frank, I think that you are still trying to push what are, in effect, Area Charter changes by what you are proposing. This document was intended to compare the features of the EDS and its “eco-system”
and the MAL and its eco-system, at a technical level. You seem to be asking for this document to be turned into a description of why the MO MAL should become the supported on-board environment, and that SOIS and the CCSDS on-board architecture should become
fully compliant with the MAL.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I understand that this is your strong desire, but I again have to point out that this is not at all the point of this document, nor is it supported by the charter for your area. In point of fact, I just reviewed
that Area Charter again, which is published in the CCSDS Org & Proc Yellow Book, CCSDS A02.1-Y-4, and I do not believe that the Charter, as documented, covers spacecraft on-board services and functions. As stated in the YB, MOIMS covers the operations of
spacecraft and the utilization of spacecraft derived data, but makes absolutely no mention of spacecraft on-board applications and services. The spacecraft on-board domain is solely the province of SOIS.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">As I said before, if you do wish to propose any such Charter changes the proper place to address that is in the CESG and CMC, and not in edits to this document. That said, this is my opinion and not one that has
been reviewed by the SOIS Area, the other members of the SEA SAWG, nor the CESG itself. I am copying this reply to the SEA SAWG and also to the SOIS AD. I expect them to reply for themselves.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">If need be this issue, which is in my opinion an attempt to make an Area Charter change, will have to be brought to the CESG for discussion.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Best regards, Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Sam Cooper <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>><br>
<b>Date: </b>Wednesday, April 10, 2019 at 8:51 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, "<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>" <<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>>, Mario
Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><br>
<b>Subject: </b>Re: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
Hi Peter,<br>
<br>
We've gone through the comments that Mehran, Mario and myself raised and have produced a consolidated output (attached). Where possible we have updated the text rather than just comment as we thought that would be more productive.<br>
<br>
What is the plan regarding updating the text in response to the list you and I worked on?<br>
<br>
Best regards,<br>
Sam<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in">On 10/04/2019 00:55, Shames, Peter M (312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:1.0in">Mario, Sam, and Mehran,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">This document was originally sent in for CESG review on 8 June 2018. The revised version that the SOIS and SEA SAWG agree is adequate and accurate was sent to you on 8 Feb 2019. We believed that we had dispositioned
all of the RIDs in a manner that was suitable and appropriate. There were delays. And extensions, and now more delays. It is now two more weeks since I least heard anything.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">Please let’s get this wrapped up and out the door. It is, after all, just a Yellow Book report. It is not the UN Charter or a Brexit deal. Let’s get it done so we can all get on to more productive work.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Sam Cooper <a href="mailto:sam@brightascension.com">
<sam@brightascension.com></a><br>
<b>Date: </b>Thursday, March 28, 2019 at 2:13 AM<br>
<b>To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a>,
<a href="mailto:Mehran.Sarkarati@esa.int">"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int">
<Mehran.Sarkarati@esa.int></a><br>
<b>Cc: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a><br>
<b>Subject: </b>Re: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.5in">
Hi Peter,<br>
<br>
Just to let you know that myself, Mario and Mehran are working to provide a consolidated set of comments in the document.
<br>
<br>
It should be with you very shortly.<br>
<br>
Best regards,<br>
Sam.<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:1.5in">On 14/03/2019 21:09, Shames, Peter M (312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:1.5in">Hi Mehran,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Somehow we seem to have a real disconnect between what this document is intended to do, which is to document the features and relationships, such as they are, between SOIS and MOIMS, and what you seem to be trying
to do with your requested changes to this document, which is to change the SOIS program of work and to shift CCSDS Area boundaries. Any such changes to Areas, their programs of work, and their interfaces is not handled in this way within CCSDS. It should
be handled by some sort of formal request, to the CESG as a whole and then the CMC, to make such changes. This work is being carried out in the present context and not some future one.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">In the original round of reviews I very carefully extracted all of the comments from you, Mario, and others who participated, and inserted them into a spreadsheet. That spreadsheet and proposed resolutions was
then reviewed with all of the participants from the SEA SAWG, adjusted as needed, and then reviewed with the SOIS and MOIMS stakeholders. I think you got a copy of it a while ago. It has all of the identified issues and all of the proposed resolutions.
The final spreadsheet (attached here) was used to drive the edits to the document. It has inputs from you and Mario, inputs from me, and some added notes from the tech editor (KT) I had help me create the final doc. The final edited document was again reviewed
by the SAWG and the stakeholders.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">With a few exceptions raised by Sam, which have since been resolved, everyone else who has reviewed this document concurs with what it says and is ready to approve it. That includes the SAWG (which includes Roger
Thompson and Ray Krosley), the SOIS crew, Sam Cooper, and Richard Melvin. At this point you appear to be the sole dissenter. And, based on your comments, you are dissenting not on the basis of technical issues with what is stated, but apparently based on
a desire to change the way that these two areas work and interact. I think that this is an inappropriate way to approach this situation and am asking you to reconsider.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">If you do wish to tackle this very different problem of changing the programs of work in SOIS, and shifting the SOIS / MOIMS boundary, I suggest that you do it using the normal CCSDS channels for such requests,
i.e. the CESG and CMC. And I ask that you stand-aside and let this document be published in its current form. See A02x1y0c4, Sec 5.1.2, on Consensus:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:2.0in">
<span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif">An individual is responsible for expressing concerns; the group is responsible for resolving them. The group decides whether a concern is legitimate; the individual decides whether to concur
with the group, block, or stand aside. </span><i><span style="font-size:12.0pt;font-family:"TimesNewRomanPS",serif">All significant issues and their disposition must be documented and accepted by the group</span></i><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif">.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Are you willing to stand-aside on this matter?<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:2.0in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black"><a href="mailto:Mehran.Sarkarati@esa.int">"Mehran.Sarkarati@esa.int"</a>
<a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a><br>
<b>Date: </b>Thursday, March 14, 2019 at 11:26 AM<br>
<b>To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><br>
<b>Cc: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a><br>
<b>Subject: </b>Re: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:2.0in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:2.0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Peter,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have now finally managed to review the commented version by Sam.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I compared it to the comments I had raised on the version from 07. June 2018. I have also attached that version for your reference.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some of my comments are still not implemented. I put them back in this new version of the document (it is now the third time, I am putting the same comments in the same document). I guess it would
be more effective, if the author does not agree with a comment, to leave it in and provide an answer rather than me going back each time and checking if my previously raised comments are or are not implemented.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some of the comments were implemented through the new text in red (added by Sam?).
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">My biggest concern is the recommendation part. I think it does make sense to align the API/Interface specification part of EDS with MAL service specification.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">At least some effort shall be put in doing it for one concrete device and comparing the two XMLs.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The current document concludes, the scope is different, hence it is ok to leave everything as is and translate from one to other.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I would personally rather see two XML documents defined for one example device (e.g. a star camera with operations such as gotoMode xyz, switch on/off, ...) and a technical assessment if it makes
sense or not to align the keywords of MAL and EDS.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">My recommendation would be that SOIS EDS remains at hardware interface definition level and delegates the specification of API/Services to be done as on-baord MO Service specifications. For this
maybe MAL would need to be extended to also be able to capture the concerns such as timing, etc.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Alternatively the EDS and MAL shall be brought so much in line that the common keywords of the XML schemas are equal for the service/api specification part.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Mehran</span> <br>
<br>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Shames, Peter M (312B)"
<a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:Mehran.Sarkarati@esa.int">"Mehran.Sarkarati@esa.int"</a>
<a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a></span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:Mario.Merri@esa.int">"Mario.Merri@esa.int"</a>
<a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Sam Cooper <a href="mailto:sam@brightascension.com">
<sam@brightascension.com></a></span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">12/03/2019 18:44</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Re: [EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and
SOIS Electronic Data Sheets</span> <o:p></o:p></p>
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:2.0in"><br>
<br>
<br>
<span style="font-size:12.0pt">Hi Mehran. </span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">If it works for you to add your notes to Sam please do so. Maybe that will avoid addressing the same topic twice. I can sort out what we have agreed to already from whatever you add (at least I hope I can AND that it is not
too cumbersome).</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Please get this to me no later than CoB Thursday, 14 March. This is already long overdue.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Thanks, Peter</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt"><a href="mailto:Mehran.Sarkarati@esa.int">"Mehran.Sarkarati@esa.int"</a>
<a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a><b><br>
Date: </b>Tuesday, March 12, 2019 at 10:01 AM<b><br>
To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><b><br>
Cc: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a><b><br>
Subject: </b>[EXTERNAL] Fw: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif">Hi Peter,</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
I promised Mario to do a review already last Friday.</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
I feel very bad, that I didn't manage yet. I will try to do this and send you a feedback this week.</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
I started to look but it is now a bit difficult. There is the red-lined version that you sent. Then there is the commented version of Sam and loads of email exchange between the two of you.</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Would it be ok, if I take the commented version of Sam and add my comments (if any) on top of it?</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Regards</span><span style="font-size:12.0pt"> </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Mehran</span><span style="font-size:12.0pt"> </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:purple"><br>
----- Forwarded by Mehran Sarkarati/esoc/ESA on 12/03/2019 17:54 -----</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Mario Merri/esoc/ESA</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (312B)"
<a href="mailto:Peter.M.Shames@jpl.nasa.gov "><Peter.M.Shames@jpl.nasa.gov ></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Dan Smith
<a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)"
<a href="mailto:glenn.p.rakow@nasa.gov"><glenn.p.rakow@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)"
<a href="mailto:jonathan.j.wilmot@nasa.gov"><jonathan.j.wilmot@nasa.gov></a>, <a href="mailto:Mehran.Sarkarati@esa.int">
"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Richard Melvin
<a href="mailto:Richard.Melvin@scisys.co.uk"><Richard.Melvin@scisys.co.uk></a>, Roger Thompson
<a href="mailto:roger.s.thompson@btinternet.com"><roger.s.thompson@btinternet.com></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">08/03/2019 16:00</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Re: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:2.0in"><br>
<span style="font-size:12.0pt"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Hi Peter,</span><span style="font-size:12.0pt"> <br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Mehran and/or I will provide you additional comments by the deadline.</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Regards,</span><span style="font-size:12.0pt"> <br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
__Mario</span><span style="font-size:12.0pt"> <br>
<br>
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (312B)"
<a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><a href="mailto:Mario.Merri@esa.int">"Mario.Merri@esa.int"</a>
<a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Dan Smith
<a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)"
<a href="mailto:glenn.p.rakow@nasa.gov"><glenn.p.rakow@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)"
<a href="mailto:jonathan.j.wilmot@nasa.gov"><jonathan.j.wilmot@nasa.gov></a>, <a href="mailto:Mehran.Sarkarati@esa.int">
"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Richard Melvin
<a href="mailto:Richard.Melvin@scisys.co.uk"><Richard.Melvin@scisys.co.uk></a>, Roger Thompson
<a href="mailto:roger.s.thompson@btinternet.com"><roger.s.thompson@btinternet.com></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">07/03/2019 19:08</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Re: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:2.0in"><br>
<span style="font-size:12.0pt"><br>
<br>
<br>
Ciao Mario, <br>
<br>
I have Sam's inputs and we have identified acceptable resolutions for all of his concerns as of 28 Feb 19.
<br>
<br>
It's been two weeks since you asked for an extension. Is there any progress on this from your end?
<br>
<br>
Thanks, Peter <br>
<br>
<br>
<b><br>
From: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a><b><br>
Date: </b>Thursday, February 21, 2019 at 5:08 PM<b><br>
To: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a><b><br>
Cc: </b>Dan Smith <a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)"
<a href="mailto:glenn.p.rakow@nasa.gov"><glenn.p.rakow@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)"
<a href="mailto:jonathan.j.wilmot@nasa.gov"><jonathan.j.wilmot@nasa.gov></a>, <a href="mailto:Mehran.Sarkarati@esa.int">
"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Richard Melvin
<a href="mailto:Richard.Melvin@scisys.co.uk"><Richard.Melvin@scisys.co.uk></a>, Roger Thompson
<a href="mailto:roger.s.thompson@btinternet.com"><roger.s.thompson@btinternet.com></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a><b><br>
Subject: </b>Re: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets
<br>
<br>
Mario, <br>
<br>
Ok. Please get response to me no later than 15 March 2019. I really need to get this wrapped up. Meanwhile I will process Sam's inputs, once I have them actually in hand.
<br>
<br>
Peter <br>
<br>
<b><br>
From: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a><b><br>
Date: </b>Thursday, February 21, 2019 at 4:19 PM<b><br>
To: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a><b><br>
Cc: </b>Dan Smith <a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)"
<a href="mailto:glenn.p.rakow@nasa.gov"><glenn.p.rakow@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)"
<a href="mailto:jonathan.j.wilmot@nasa.gov"><jonathan.j.wilmot@nasa.gov></a>, <a href="mailto:Mehran.Sarkarati@esa.int">
"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Richard Melvin
<a href="mailto:Richard.Melvin@scisys.co.uk"><Richard.Melvin@scisys.co.uk></a>, Roger Thompson
<a href="mailto:roger.s.thompson@btinternet.com"><roger.s.thompson@btinternet.com></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a><b><br>
Subject: </b>Re: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
Peter,</span><span style="font-size:12.0pt"> </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
<br>
unfortunately please extend the deadline by at least 2 weeks as due to workload we were not able to process this.</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
<br>
Thanks,</span><span style="font-size:12.0pt"> </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><br>
<br>
__Mario</span><span style="font-size:12.0pt"> <br>
<br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
<br>
From: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (312B)"
<a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Mario Merri
<a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, <a href="mailto:Mehran.Sarkarati@esa.int">
"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Sam Cooper
<a href="mailto:sam@brightascension.com"><sam@brightascension.com></a>, "Roger Thompson"
<a href="mailto:roger.s.thompson@btinternet.com"><roger.s.thompson@btinternet.com></a>, Dan Smith
<a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)"
<a href="mailto:jonathan.j.wilmot@nasa.gov"><jonathan.j.wilmot@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)"
<a href="mailto:glenn.p.rakow@nasa.gov"><glenn.p.rakow@nasa.gov></a>, Richard Melvin
<a href="mailto:Richard.Melvin@scisys.co.uk"><Richard.Melvin@scisys.co.uk></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">SEA-SA
<a href="mailto:sea-sa@mailman.ccsds.org"><sea-sa@mailman.ccsds.org></a>, "CCSDS Engineering Steering Group - CESG Exec"
<a href="mailto:cesg@mailman.ccsds.org"><cesg@mailman.ccsds.org></a></span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">20/02/2019 21:45</span><span style="font-size:12.0pt">
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Re: SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:2.0in"><br>
<span style="font-size:12.0pt"><br>
</span> <o:p></o:p></p>
<p style="margin-left:2.0in">Dear MOIMS & SOIS colleagues, <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">I requested feedback on this by 22 Feb 2019. Are you going to have replies and feedback by then? I want to get this off my plate.
<o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">For those who have lost the thread, this is intended as the resolution for the Condition raised on CESG-P-2018-05-010, see
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__public.ccsds.org_polls_Lists_CESGP201805010_AllItems.aspx&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=BN62OVKal4ByIRepHNuyNT6tYCZFwitijyBBGujQm8E&m=x8gd3uD53omJL8heAGRhrDKj_yWTiulBKHhnP-zdu3Q&s=eoADL5XARO59M-jL_CRLiEDCYw_QLlmZFTYn9GJoNKU&e=">
https://public.ccsds.org/polls/Lists/CESGP201805010/AllItems.aspx</a>. <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">Thanks, Peter <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in"><b>From: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov">
<Peter.M.Shames@jpl.nasa.gov></a><b><br>
Date: </b>Friday, February 8, 2019 at 5:04 PM<b><br>
To: </b>Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>,
<a href="mailto:Mehran.Sarkarati@esa.int">"Mehran.Sarkarati@esa.int"</a> <a href="mailto:Mehran.Sarkarati@esa.int">
<Mehran.Sarkarati@esa.int></a>, Sam Cooper <a href="mailto:sam@brightascension.com">
<sam@brightascension.com></a>, Roger Thompson <a href="mailto:roger.s.thompson@btinternet.com">
<roger.s.thompson@btinternet.com></a>, Dan Smith <a href="mailto:danford.s.smith@nasa.gov">
<danford.s.smith@nasa.gov></a>, "Wilmot, Jonathan J. (GSFC-5820)" <a href="mailto:jonathan.j.wilmot@nasa.gov">
<jonathan.j.wilmot@nasa.gov></a>, "Rakow, Glenn P. (GSFC-5610)" <a href="mailto:glenn.p.rakow@nasa.gov">
<glenn.p.rakow@nasa.gov></a>, Richard Melvin <a href="mailto:Richard.Melvin@scisys.co.uk">
<Richard.Melvin@scisys.co.uk></a><b><br>
Cc: </b>SEA-SA <a href="mailto:sea-sa@mailman.ccsds.org"><sea-sa@mailman.ccsds.org></a>, CCSDS Engineering Steering Group - CESG Exec
<a href="mailto:cesg@mailman.ccsds.org"><cesg@mailman.ccsds.org></a><b><br>
Subject: </b>SEA SAWG proposed edits to the SOIS document, CCSDS 870.10-Y-1, MO Services and SOIS Electronic Data Sheets
<o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">Dear All, <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">As reported during the CESG Telecon on 7 Feb 2019, the Systems Engineering Area (SEA), using resources of the Systems Architecture Working Group (SAWG), has completed a review of the SOIS document, CCSDS 870.10-Y-1, MO Services
and SOIS Electronic Data Sheets and proposed a set of updates to resolve differences of opinion between SOIS and MOIMS and clarify the relationships. This result was derived using meeting and email discussions within the SAWG and particularly with representatives
of the two different points of view (Roger Thompson and Ramon Krosley) and the original author of the document (Richard Melvin). Before sending this document out more widely these parties were polled and they concurred in this release, with two minor issues
noted. Those issues have been dealt with in this version. <o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">Three files are attached: <o:p></o:p></p>
<p style="margin-left:2.0in">1) A "clean" version with changes accepted, but revised text left in
<span style="color:red">red</span> <o:p></o:p></p>
<p style="margin-left:2.0in">2) A raw version with all of the tracked changes visible
<o:p></o:p></p>
<p style="margin-left:2.0in">3) A spreadsheet extracted from the marked up PDF files, along with the audit trail of discussions leading to resolution
<o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">Since this is, in effect, a cross-area "working group" of sorts I would like to ask all of those who have a stake in this to review the document and provide feedback in two weeks, by 22 Feb 2019. I'd like to use a consensus process
over email and am hoping we can wrap this up quickly. We will still need to process the final result through the CESG for approval to publish.
<o:p></o:p></p>
<p style="margin-left:2.0in"> <o:p></o:p></p>
<p style="margin-left:2.0in">Thanks, Peter <o:p></o:p></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:2.0in">
<span style="font-family:"Courier New ,serif",serif"><br>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<span style="font-family:"Courier New ,serif",serif"><br>
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<span style="font-family:"Courier New ,serif",serif"><br>
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<span style="font-family:"Courier New ,serif",serif"><br>
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>).</span>
<br>
<br>
<span style="font-family:"Courier New ,serif",serif">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<br>
<span style="font-family:"Courier New ,serif",serif">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<br>
<span style="font-family:"Courier New ,serif",serif">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<br>
<span style="font-family:"Courier New ,serif",serif">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>).</span>
<o:p></o:p></p>
<pre style="margin-left:2.0in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:2.0in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:2.0in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:2.0in">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>
</blockquote>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.5in">
<br>
<br>
<br>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
<o:p></o:p></p>
</div>
</body>
</html>