[MOIMS-NAV-EXEC] FW: Requesting your input on proposed SANA entries in support of future CCSDS International standards for space data exchange

[Oltrogge, Daniel]

Here is the latest set of SANA registry entries that Julie and I have been iterating on, for our discussions next week.

As you can see below, I've reached out to 35 large space operators to solicit their inputs as well, and those are starting to come in (useful inputs).

For us to discuss on Monday.

David, I'm interested in what sorts of formats, equations/typesets, figures, etc. that SANA could support (?)

Dan

Daniel L. Oltrogge
SDC Program Mgr. and Sr. Research Astrodynamicist
Center for Space Standards and Innovation
Analytical Graphics, Incorporated
Voice: 719-482-4552; E-mail: oltrogge at agi.com

From: Oltrogge, Daniel
Sent: 31 Oct 2017 09:38
Subject: Requesting your input on proposed SANA entries in support of future CCSDS International standards for space data exchange

Flight Dynamics, operations and astrodynamics colleagues -

The Space Assigned Numbers Authority (SANA) is the registrar function for the protocol registries created under the Consultative Committee for Space Data Systems (CCSDS).  I support the Navigation Working Group (Nav WG) within CCSDS, and we develop international standards for data exchange of navigation-related elements of information.

We are currently exploring the use of the SANA registry as a "living" reference support document to contain definitions of content that are currently duplicated (sometimes inconsistently) across many of the CCSDS standards.  The concept is to have the next generation of CCSDS standards instead reference the SANA registry as the single unified and up-to-date source for definitions of parameters.

I would like to get your input on the attached proposed table of entries for definition of:

(1)    Time systems

(2)    Orbit element sets;

(3)    Absolute and relative reference frames;

(4)    Attitude and attitudinal dynamics definitions and parameters;

In each table, you can see the proposed "key" name and its associated definition.  What I'd like to know is:  Do the attached tables and content define what you are currently using operationally?  Is there anything missing (again that you are actively using in your operations) that you would like us to consider including in these tables?

If so, please let me know this week for inclusion into our CCSDS Fall meeting discussions next week.

Dan

Daniel L. Oltrogge
SDC Program Mgr. and Sr. Research Astrodynamicist
Center for Space Standards and Innovation
Analytical Graphics, Incorporated
Voice: 719-482-4552; E-mail: oltrogge at agi.com<mailto:oltrogge at agi.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20171102/3fc4770a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CCSDS Candidate_SANA_Registry_Entries_for_Timing_RefFrames_ElSets_06.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 45869 bytes
Desc: CCSDS Candidate_SANA_Registry_Entries_for_Timing_RefFrames_ElSets_06.docx
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20171102/3fc4770a/attachment.docx>