<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:x="urn:schemas-microsoft-com:office:excel" 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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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:"Times New Roman","serif";}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> I think these could represent valuable pieces of information for dissemination. Thanks for sharing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:10.0pt;color:blue">dav</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:10.0pt;color:blue">David A Vallado</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:7.5pt;color:blue">Senior Research Astrodynamicist, CSSI/AGI
</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:7.5pt;color:blue">719-573-2600, 719-573-9079 FAX, 610-981-8614 direct</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Moving things through space and time since 1989. AGI proudly celebrates
<a href="http://blogs.agi.com/agi/2014/01/17/weve-gone-silver-agi-celebrates-25-years/">
25 years</a>!</span><span style="font-size:11.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> moims-nav-exec-bounces@mailman.ccsds.org [mailto:moims-nav-exec-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Tim.Flohrer@esa.int<br>
<b>Sent:</b> Monday, September 07, 2015 6:07 AM<br>
<b>To:</b> moims-nav-exec@mailman.ccsds.org<br>
<b>Cc:</b> Alexandru.Mancas@esa.int; Holger.Krag@esa.int<br>
<b>Subject:</b> [MOIMS-NAV-EXEC] Data messages for re-entry and fragmentation events<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear colleagues,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">as mentioned and very briefly discussed at the last telecon of the MOIMS Navigation Working Group, we are working at ESA on data formats that cover the exchange of information on re-entry and fragmentation
events. This work has been triggered by actual needs from the operational support that ESA's Space Debris Office is providing to missions, and, in parallel, during the developments and architectural analysis performed in ESA's SSA program in the Space Surveillance
and Tracking (SST) segment. My colleague Luis Martin (my predecessor in the working group for the SSA/SST) made a first statement on planned developments at the London meeting of the CCSDS.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">With this email we want to provide to you additional information on both formats. It would be very interesting for us to learn about your opinions and expectations on whether such topics are of
interest for a wider community and, hence, on whether the working group may want to address these needs.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">We are ready to give more detailed presentations on the drafted data messages at the Darmstadt meeting.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Tim and Alexandru</span>
<br>
<br>
<br>
<b><span style="font-family:"Georgia","serif"">Re-entry Data Message (RDM)</span></b>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">The exchange of spacecraft re-entry event data has been developed for the ESA SSA/SST project. The used format is inspired by CCSDS messages.</span>
<o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">Satellite operators exchange several types of messages already covered by CCSDS, describing orbits, observations, attitude state and conjunctions. However, currently no message for spacecraft (re-)entry exists.
</span><o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">Predictions on re-entry epochs, sometimes also including the estimated location, are already exchanged at technical level, e.g., in the frame of test campaigns run by the Inter-Agency Space Debris Coordination
Committee (IADC). These test campaigns aim at comparing prediction techniques and tools, and verifying readiness and technical expertise for high-risk re-entry events. With an increase in Space Surveillance and Tracking (SST) activities, it is expected that
re-entry tracking campaigns will become more frequent and the need for simpler, standardised data exchange will increase. The developed format facilitates data sharing and interoperability, for example for analysis and visualisation. For instance, during the
last orbits of a re-entering spacecraft, agency A might not have the sensors to track the spacecraft, but agency B does and provides up to date information about the re-entry (such as the projected impact location), without having to exchange tracking data.</span>
<o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">The <i>Re-entry Data Message</i> contains information about an object entering the Earth's atmosphere. It is not intended to describe a controlled re-entry, or a landing, or to provide detailed orbit information
for the object. Re-entry data are expected to be exchanged between entities monitoring the space environment, spacecraft operators and national or international authorities. The types of information currently exchanged in re-entry monitoring campaigns include:
object name, class and properties (mass, cross-sectional area), the predicted epoch and location of the re-entry event, and the concise description of used models.</span>
<o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">A CCSDS-like <i>Re-entry Data Message</i> has been drafted for the ESA SSA/SST system and aims at enabling a simpler exchange of re-entry data between different entities and/or agencies.</span>
<o:p></o:p></p>
<p><br>
<b><span style="font-family:"Georgia","serif"">Fragmentation Data Message (FDM)</span></b>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">The exchange of spacecraft fragmentation event descriptions has been developed for the ESA SSA/SST project. The used format is inspired by CCSDS messages.</span>
<o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">A system observing the space environment and determining the orbits of the covered objects can determine when and where a fragmentation event occurred, and can issue the appropriate warnings. With an increase in
Space Surveillance and Tracking (SST) activities, it is expected that fragmentation detection campaigns will become more frequent and the need for simple, standardised data exchange will increase. The developed format facilitates data sharing and interoperability,
e.g., for analysis and visualisation. For example, agency A does not have fragmentation detection capabilities and a fragmentation event occurs in the same orbital regime as one of its spacecraft. Agency B does have the capability and provides agency A with
the fragmentation information, which enables agency A to assess the risk to its spacecraft, without having to exchange tracking data.
</span><o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">The <i>Fragmentation Data Message</i> contains information about fragmentation events in orbit around Earth. It is not intended to provide detailed orbit information for the originator or the generated fragments.
Fragmentation data includes, as far as available, information about the progenitor object (physical properties, COSPAR ID, etc.), spatial coordinates and epoch of the fragmentation event, the spread in orbital properties of the fragments, a list of fragments
and their detection epochs, and the increase in object spatial density due to the fragmentation event. If the fragmentation was caused by a collision, the properties of the second colliding spacecraft and the reference to the CDM describing the conjunction
can also be exchanged as an option.</span> <o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">A CCSDS-like <i>Fragmentation Data Message</i> has been drafted for the ESA SSA/SST system and aims at enabling for a simpler exchange of fragmentation data between different entities and/or agencies.</span>
<o:p></o:p></p>
<p style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
-- <br>
Tim Flohrer, PhD<br>
ESA/ESOC Space Debris Office (HSO-GR)<br>
Robert-Bosch-Strasse 5, DE-64293 Darmstadt, Germany<br>
+49-6151-90-3058 (phone), +49-6151-90-2625 (fax)<br>
</span><a href="http://www.esa.int/debris"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">http://www.esa.int/debris</span></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</body>
</html>