<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 11 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Helvetica",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Helvetica",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">That makes sense to me. Is this another case illustrating the need to perhaps consider a more functional decomposition of the standards so that each one doesn’t have to have time, propagation,
attitude, etc? Rather, they could refer to the standard on each of those sub topics and whatever differentiators are required for the specific issue at hand.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span lang="EN" style="font-size:10.0pt;font-family:"Times New Roman",serif;color:blue">dav</span><span style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span lang="EN" style="font-size:10.0pt;font-family:"Times New Roman",serif;color:blue">David A Vallado</span><span style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span lang="EN" style="font-size:7.5pt;font-family:"Times New Roman",serif;color:blue">Senior Research Astrodynamicist, CSSI/AGI
</span><span style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span lang="EN" style="font-size:7.5pt;font-family:"Times New Roman",serif;color:blue">719-573-2600, 719-573-9079 FAX, 610-981-8614 direct</span><span style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Times New Roman",serif;color:black">There is a new STK ... <a href="http://agi.com/ThisOneGoesTo11" target="_blank" title="http://agi.com/ThisOneGoesTo11
Cmd+Click or tap to follow the link"><span style="color:blue">agi.com/ThisOneGoesTo11</span></a></span><span style="font-size:11.0pt;font-family:"Times New Roman",serif;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><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><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> MOIMS-NAV-EXEC [mailto:moims-nav-exec-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Oltrogge, Daniel<br>
<b>Sent:</b> Sunday, January 08, 2017 9:14 AM<br>
<b>To:</b> Thienel, Julie K. (GSFC-5990) <julie.k.thienel@nasa.gov>; Gramling, Cheryl J. (GSFC-5950) <cheryl.j.gramling@nasa.gov>; moims-nav-exec@mailman.ccsds.org<br>
<b>Subject:</b> Re: [MOIMS-NAV-EXEC] CCSDS: Maneuver Message Requirements 1/5/17 update<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I think I’m aligned with Julie’s thoughts to keep it generic. Perhaps something like:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">For each maneuver, the SMM shall provide the ability to include orbit and/or attitude time series state histories associated with the maneuver.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I’m not sure how we’ll meet such a requirement in the OCM since attitude is not currently present in it, but at least the above might capture what we’re trying to accomplish.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><br>
Dan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Daniel L. Oltrogge<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">SDC Program Manager & Senior Research Astrodynamicist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Center for Space Standards and Innovation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Analytical Graphics Incorporated<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Voice: 719-482-4552; E-mail:
<a href="mailto:oltrogge@agi.com">oltrogge@agi.com</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><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><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> MOIMS-NAV-EXEC [<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">mailto:moims-nav-exec-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Thienel, Julie K. (GSFC-5990)<br>
<b>Sent:</b> Sunday, January 08, 2017 5:41 AM<br>
<b>To:</b> Gramling, Cheryl J. (GSFC-5950) <<a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a>>;
<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a><br>
<b>Subject:</b> Re: [MOIMS-NAV-EXEC] CCSDS: Maneuver Message Requirements 1/5/17 update<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">I think maybe it should remain generic ‘for each maneuver’, rather than splitting by maneuver type. The split associates a time series trajectory state with a trajectory-changing maneuver, but
you may want an attitude state history during a trajectory-changing maneuver as well. And vice versa if the attitude changing maneuver is done with thrusters.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Julie<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">From: </span></b><span style="font-size:11.0pt;color:black">MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">moims-nav-exec-bounces@mailman.ccsds.org</a>> on behalf
of "Gramling, Cheryl J. (GSFC-5950)" <<a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a>><br>
<b>Date: </b>Thursday, January 5, 2017 at 11:59 AM<br>
<b>To: </b>"<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>[MOIMS-NAV-EXEC] CCSDS: Maneuver Message Requirements 1/5/17 update<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Happy 2017, Everyone.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">The attached spreadsheet of maneuver message requirements has two new tabs: “Requirements for SMM-14Dec2016” that shows the updates from the telecom on 12/14/16;
“FINAL SMMRequirements-1-4-17” that attempts to clean up the requirements as we’ve dispositioned them to date, re-align them in a logical ordering, for a [soon-to-be] final set of maneuver message requirements. My hope is that by following the comments on
the “…14Dec2016” tab one should be able to trace to the requirements on the “FINAL…1-4-17” tab.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">There is one requirement I’d like feedback on: Requirement SMM-P15 on tab “FINAL SMMRequirements-1-4-17”.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">This was to consolidate all the separate requirements for an epoch, state, end state, and state during the maneuver into optionally providing a state history
file. I formulated the requirement in a generic sense in order to provide a multi-element state for orbit, attitude, or both, along with time. This is in line with our discussions on the interaction between a maneuver that is planned for one purpose (e.g.
orbit inclination change), but that has an impact on both the trajectory and the attitude of the spacecraft. The text between the square brackets “[xx-changing]” may be removed from the requirement in order to maintain the generic aspect. However, if we want
to include separate options for a trajectory state and for an attitude state, then I could split the requirement and include the specific maneuver. So the requirement would go </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">FROM the single requirement:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">For each maneuver, the SMM shall provide the ability to include a time series state history associated with the maneuver.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">TO two requirements:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">For each trajectory-changing maneuver, the SMM shall provide the ability to include a time series trajectory state history associated with the maneuver.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">AND</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">For each attitude -changing maneuver, the SMM shall provide the ability to include a time series attitude state history associated with the maneuver.</span></i><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">I look forward to any feedback you have to offer on the set of requirements.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Thank you,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Cheryl</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">--
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Cheryl Gramling</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">[O] 301-286-8002</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">[C] 240-328-5517</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black">On 12/9/16, 1:29 PM, "Gramling, Cheryl J. (GSFC-5950)" <<a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a>> wrote:<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Hello Everyone,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> The attached spreadsheet file incorporates updates to the Maneuver Message requirements based on our telecom on 30Nov2016.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> There are three tabs. The right-most tab [….history] has all of the original requirements, the suggested updates, comments from our telecons of 16 and 30 Nov, and the resultant update to the requirements
and rationale with new requirement numbering. There is also a new Comments column for the updated requirements.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> From the […history] tab, I created the left-most tab […Dec2016] that only contains a listing of the resultant requirements, rationales, and updated requirement numbers, along with the associated comments
column. This allows us to work with a fresh listing of the requirements, hopefully for clarity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> The third sheet in the file is the center tab [Definitions] that lists terms and descriptions. Some of these terms are not currently used in the requirements set, but we may use these in the text of the
Standard so I did not delete them. We can always update the listing with additions/deletions later.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> I’d appreciate your feedback on the […Dec2016] and [Definitions] tab, particularly on requirements SMM-P15, SMM-P20, SMM-P26, and SMM-P30.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Thank you.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Best Regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Cheryl<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> -- <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Cheryl Gramling<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> Senior Navigation Systems Engineer<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <a href="mailto:cheryl.j.gramling@nasa.gov">
cheryl.j.gramling@nasa.gov</a><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> [O] 301-286-8002<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> [C] 240-328-5517<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>