<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>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.</div>
<div><br>
</div>
<div>Julie</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>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>
<span style="font-weight:bold">Date: </span>Thursday, January 5, 2017 at 11:59 AM<br>
<span style="font-weight:bold">To: </span>"<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>
<span style="font-weight:bold">Subject: </span>[MOIMS-NAV-EXEC] CCSDS: Maneuver Message Requirements 1/5/17 update<br>
</div>
<div><br>
</div>
<div 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">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
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;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Helvetica;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">Happy 2017, Everyone.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">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. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">There is one requirement I’d like feedback on: Requirement SMM-P15 on tab “FINAL SMMRequirements-1-4-17”.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">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 <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">FROM the single requirement:<o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:Calibri">For each maneuver, the SMM shall provide the ability to include a time series state history associated with the maneuver.<o:p></o:p></span></i></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">TO two requirements:<o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:Calibri">For each trajectory-changing maneuver, the SMM shall provide the ability to include a time series trajectory state history associated with the maneuver.<o:p></o:p></span></i></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">AND<o:p></o:p></span></p>
<p class="MsoPlainText"><i><span style="font-size:10.0pt;font-family:Calibri">For each attitude -changing maneuver, the SMM shall provide the ability to include a time series attitude state history associated with the maneuver.<o:p></o:p></span></i></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">I look forward to any feedback you have to offer on the set of requirements.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">Thank you,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">Cheryl<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">-- <o:p>
</o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">Cheryl Gramling<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri"><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="font-size:10.0pt;font-family:Calibri">[O] 301-286-8002<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:10.0pt;font-family:Calibri">[C] 240-328-5517</span><span style="font-size:10.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">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></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Hello Everyone,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> The attached spreadsheet file incorporates updates to the Maneuver Message requirements based on our telecom on 30Nov2016.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 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></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 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></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 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></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 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></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Thank you.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Best Regards,<o:p></o:p></p>
<p class="MsoPlainText"> Cheryl<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> -- <o:p></o:p></p>
<p class="MsoPlainText"> Cheryl Gramling<o:p></o:p></p>
<p class="MsoPlainText"> Senior Navigation Systems Engineer<o:p></o:p></p>
<p class="MsoPlainText"> <a href="mailto:cheryl.j.gramling@nasa.gov">cheryl.j.gramling@nasa.gov</a><o:p></o:p></p>
<p class="MsoPlainText"> [O] 301-286-8002<o:p></o:p></p>
<p class="MsoPlainText"> [C] 240-328-5517<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>