<html 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:Courier;
panose-1:2 0 5 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:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 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:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Courier;
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;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Dan:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Thanks for doing this analysis.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">My thoughts:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">It's nice that most of the recent works of the group are well aligned.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">ODM: Let's leave the OPM, OMM, OEM unchanged. Rationale: If we change them, it could be argued that we would have to do prototype testing of these messages (which we currently do not have
to do since all that was added was a "COMMENT equivalent", i.e., "MESSAGE_ID"). Additionally, these attributes of the messages have been unchanged for at least 11 years (OMM) and 16 years (OPM, OEM). Operations software built on the older standards would have
to be updated with costs to the organizations that use them. This rationale does not apply to the OCM; the OCM setup is not a problem.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">ADM: Let's leave APM, AEM unchanged. Rationale: Same as above (except for duration of status quo). This rationale does not apply to the ACM; the ACM setup is not a problem.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">PRM: Leave unchanged. Rationale: Modifying the PRM would require us to start a new project in the CCSDS. I'd prefer we spend our collective energy (document editor time, prototyping time,
and especially internal reviewing time) on other already in-progress activities. The document will be up for 5 Year Review in 2 years and we can start a project at that time if there are other necessary/desirable changes identified.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">TDM: Leave V.2 unchanged, consider for V.3. Rationale: This issue has not been identified as a problem by the user community. Up to 5 different objects, some of which are not spacecraft,
can be identified in each metadata section of the TDM (using the "PARTICIPANT_n" keywords, n=1..5). Considering this topic as a change in TDM V.3 is fair game and Cheryl can add it to her growing list of potential changes.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">MOIMS-NAV-EXEC <moims-nav-exec-bounces@mailman.ccsds.org> on behalf of "Oltrogge, Daniel" <doltrogge@comspoc.com><br>
<b>Date: </b>Wednesday, January 20, 2021 at 7:39 AM<br>
<b>To: </b>"moims-nav-exec@mailman.ccsds.org" <moims-nav-exec@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [MOIMS-NAV-EXEC] Object name entries<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">I’ve now compared the various ways that NAV WG standards reference objects.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The findings are interesting (attached). The current OCM is well-aligned with the published CDM and RDM, only adding an ALTERNATE_NAMES field, but with all other keywords well-aligned.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">By contrast, the OPM, OEM, OMM, ADM, PRM and TDM lack the ability to reference objects with catalog names and numbers (e.g. SSC number). Perhaps the OPM, OMM and OEM and ADM should rectify this since we are actively working on these messages.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thoughts?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dan<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:dashed windowtext 1.0pt;padding:1.0pt 0in 0in 0in">
<p class="MsoNormal">Dan Oltrogge <span style="font-size:13.5pt">҉</span> Director, Integrated Operations and Research
<span style="font-size:13.5pt">҉</span> COMSPOC Corporation <span style="font-size:13.5pt">
҉</span> 719-482-4552 <span style="font-size:13.5pt">҉</span> <a href="mailto:dan@comspoc.com">
<span style="color:blue">dan@comspoc.com</span></a><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>