<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Courier, sans-serif;">
<div><br>
</div>
<div>Dave:</div>
<div><br>
</div>
<div>OMMs are posted on the Space-track website... see https://www.space-track.org/#/catalog far right column. </div>
<div><br>
</div>
<div>For that reason, as far as I'm concerned, the OMM should stay.</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div><br>
</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>SkySentry <<a href="mailto:finklemand@skysentry.net">finklemand@skysentry.net</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, March 4, 2015 at 8:14 PM<br>
<span style="font-weight:bold">To: </span>David Berry <<a href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </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>Re: [MOIMS-NAV-EXEC] FW: Proposed Draft Orbit Hybrid Message (OHM)<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div>I have no objection to the addition. I agree that it would overcome a deficiency for many users and potential users. However, there are certainly other essential revisions that should be implemented in the mandatory reconfirmation review. For example,
I think that the OMM should be removed. As far as I can tell, no one uses it. It was my attempt to bring the USAF into the rest of the world by accommodating TLE content in a standard formalism. Now the USAF has gained momentum in providing OEM and OPM
formats, particularly in the CDM. OMM can go. There may be new elements of information, particularly for small satellites or for intentional rather than accidental close approaches, as in ADR. </div>
<div><br>
</div>
<div>We should pursue diligently a full review and assessment. Dan's contribution is a good start. I believe that opening things up briefly will not affect the bureaucracy of implementing the OHM.</div>
<div><br>
</div>
<div>ברכות מתל אביב</div>
<div><br>
</div>
<div>Dave</div>
<div><br>
<br>
Sent from my iPad</div>
<div><br>
On Mar 5, 2015, at 12:46 AM, Berry, David S (3920) <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div><br>
</div>
<div>All: </div>
<div><br>
</div>
<div>Attached is Dan Oltrogge's work on the ODM revisions for your review and comment. If you have a chance to take a look prior to the meetings that start 23-March-2015 that would be great.</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div>P.S.: More to come!!!</div>
<div><br>
</div>
<div><br>
</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><Oltrogge>, Daniel <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, February 18, 2015 at 5:38 AM<br>
<span style="font-weight:bold">To: </span>David Berry <<a href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Fwd: Proposed Draft Orbit Hybrid Message (OHM)<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div>Proposed OHM draft document, for distribution to the group.<br>
<br>
<div><span style="background-color: rgba(255, 255, 255, 0);">// Dan Oltrogge</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">// SDC Program Mgr & Sr Research Astrodynamicist</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">// 719-482-4552 | <a href="mailto:oltrogge@agi.com">
oltrogge@agi.com</a></span></div>
</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type="cite">
<div><b>From:</b> "Oltrogge, Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><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>Cc:</b> "'Dan Oltrogge (<a href="mailto:oltrogge@agi.com">oltrogge@agi.com</a>)'" <<a href="mailto:oltrogge@agi.com">oltrogge@agi.com</a>><br>
<b>Subject:</b> <b>Proposed Draft Orbit Hybrid Message (OHM)</b><br>
<br>
</div>
</blockquote>
<div><span></span></div>
<blockquote type="cite">
<div><span>All –</span><br>
<span></span><br>
<span>From our last NAV WG meeting in London, I was tasked with scoping out an Orbit Hybrid Message (OHM) to augment the existing Orbit Data Message (ODM) types (OMM, OPM and OEM).</span><br>
<span></span><br>
<span>For your consideration and as promised (and even on time!), a proposed draft of this new message type is attached. To save you some time, most of the relevant OHM content is contained in Section 6, with additional verbiage in the earlier sections and
in Section 7 and in the appendices.</span><br>
<span></span><br>
<span>As a reminder, the principal drivers for the new message are:</span><br>
<br>
<span>(1) Additional use cases:</span><br>
<span></span><br>
<span>a. Satellite operators needing a succinct message type to contain covariance, ephemeris and/or orbital states, maneuver info</span><br>
<span></span><br>
<span>b. Small satellite (e.g. CubeSat or “sprites” mission) en masse deployments containing between 50 and 200 objects per deployment;</span><br>
<span></span><br>
<span>c. Space tracking agencies (e.g. STRATCOM, ESA, JSpOC, ISON, ComSpOC, etc) needing to share large quantities of orbital ephemeris and satellite physical characteristics info for as many as 200,000 objects as much as three times per day.</span><br>
<span></span><br>
<span>(2) Need to make the messages smaller by:</span><br>
<span></span><br>
<span>a. Allowing more optional data within a standardized set of options, so that the user only has to share the information which the user will ultimately need;</span><br>
<span></span><br>
<span>b. Combining the requisite features of multiple message types (OMM, OPM and OEM) into a single message to eliminate duplicative message header information.</span><br>
<span></span><br>
<span>I want to thank Dave Finkleman and Doug Cather and several SDA operators for their willingness to review and provide suggestions on the message and to Dave Vallado and Sal Alfano for working with me to develop overall message content.</span><br>
<span></span><br>
<span>I look forward to discussing this new proposed message format and content with you. We can discuss in detail at the upcoming meetings in Pasadena as well.</span><br>
<span></span><br>
<span>Thanks,</span><br>
<span></span><br>
<span>Dan</span><br>
<span></span><br>
<span>Daniel L. Oltrogge</span><br>
<span>SDC Program Manager & Senior Research Astrodynamicist</span><br>
<span>Center for Space Standards and Innovation</span><br>
<span>Analytical Graphics Incorporated</span><br>
<span>Voice: 719-660-5142; E-mail: <a href="mailto:oltrogge@agi.com">oltrogge@agi.com</a></span><br>
<span></span><br>
</div>
</blockquote>
<blockquote type="cite">
<div></div>
</blockquote>
</div>
</div>
</span></div>
</blockquote>
<blockquote type="cite">
<div><ODM_OHM_New_Draft_v22.pdf></div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>MOIMS-NAV-EXEC mailing list</span><br>
<span><a href="mailto:MOIMS-NAV-EXEC@mailman.ccsds.org">MOIMS-NAV-EXEC@mailman.ccsds.org</a></span><br>
<span><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>
</body>
</html>