<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=utf-8">
<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;}
@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:11.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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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: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;}
/* List Definitions */
@list l0
{mso-list-id:1273561538;
mso-list-template-ids:1537007770;}
@list l0:level1 lfo3
{mso-level-start-at:2;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Colin,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Glad to hear that things are moving along. It's really what is needed for the SM WG and also for the whole registry concept to provide the value it was designed to deliver. So thanks for picking up the flag and marching it downfield.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Other comments, etc <span style="color:#0070C0"><<in-line>></span> below.<o:p></o:p></p>
<p class="MsoNormal"><br>
Cheers, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">SMWG <smwg-bounces@mailman.ccsds.org> on behalf of Colin Haddow <Colin.Haddow@esa.int><br>
<b>Date: </b>Thursday, November 7, 2019 at 9:37 AM<br>
<b>To: </b>SMWG <smwg@mailman.ccsds.org><br>
<b>Cc: </b>"EXTERNAL-Reynolds, John G (9110-Affiliate)" <john.reynolds@esa.int>, Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Subject: </b>[EXTERNAL] [Smwg] SANA Registry Updates.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> okay I'm going to be responsible for coordinating the updates for the ESA entries in the SANA registry. Is there any documentation on the underlying database design ? As far as
I can figure out the main relations (ignoring Operator and Owner etc.) for the Sites Service and Apertures registry is with the Aperture and Aperture Link registry, similarly for the Spacecraft ID the main relation would appear to be with Spacecraft.</span>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#0070C0"><<The database design, per se, is abstractly defined in the RMP, CCSDS 313.1-y-1. Look at sec 2.4.6, 3.3.2.4, and at Annex B4. We can, if need be, get the full database design from the SAANA, but I think these
sections will spell out what the registries are intended to contain. Your assumption about the SS&A relationship to the Aperture DB is correct. I think fig B-5 spells it out pretty clearly. >></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Also with respect to the Contact registry for the ESA entries at least there are names that go way back in history and are long retired. Can these be removed from the registry or are they required
to maintain consistency ? If they are required for consistency what would be the appropriate status to use to indicate that these contacts are no longer valid ?</span>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#0070C0"><<We maintain the original contact who created entries and would need the names for consistency. But we do also need to know who is currently responsible. That can be determined by looking at the Contacts registry
and filtering on AR. Maybe that is a little obscure and we should think about adding a filtered link to the SS&A page (and the SCID registry page) that provides a hot link to the latest info. Would that help?>></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Couple of other points that have come up during our initial discussions -
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:10.0pt;font-family:"Arial",sans-serif">On the spacecraft registry there is an alias field. This would also be useful on the Aperture Registry - could be used to handle things like DSN giving DSN station identifiers
to ESA stations etc.</span> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#0070C0"><<We do have a name and an abbreviation field. I suspect that we can add an alias field as well, as we did for Spacecraft. We probably will need to
develop some guidelines about how to fill all of these fields out. I was thinking we might need a sort of "cheat sheet" for these different AR roles. We had not thought of that before, but as this turns real maybe we need to create such a modest guidance
document. How does that sound to you?>></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo3">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:10.0pt;font-family:"Arial",sans-serif">One of the guys I'm working with (John Reynolds) is also involved with the IOAG Spacecraft Emergency W/G. He's told me that IOAG are considering setting up their own registry
for use in that context as they've currently not found the CCSDS SSA very useful (not to mention out of date). We've had a quick look at the information contained in the various SSA related registries and think that pretty much all of the needed data is there
(or at least will be once the registry is updated). Possibly what would be needed is some sort of query that pulls this together into a more useful format ?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#0070C0"><<Since the source of a lot of the current SS&A material was the earlier IOAG RF Asset DB what we have in the SANA, in a real database, should both look
familiar and provide the needed functionality. From a CCSDS / SM WG point of view I cannot imagine that we would not want to have the necessary info to handle S/C emergencies in the SANA SS&A DB. I would think that having such a DB where you could find assets
that were suitable to support emergency situations would be a really good thing.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#0070C0">That said, I would like to better understand what you really mean by "</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">some sort
of query that pulls this together into a more useful format </span><span style="color:#0070C0">". Just what would that "useful format" contain? I am sure that we can ask the SANA Operaotr to build a specialized query to do whatever is needed, and display
it in whatever way is needed, if only we knew what that was.>></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Once we've got a bit further with reviewing and updating the data I'll maybe organise a WebEx with you (and possibly the SANA operator) to disuss any changes (such as the above 2) that we think would be useful.</span>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#0070C0"><<Whenever you are ready. Let me know>></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Colin</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal">Cheers, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>