This document specifies four standard message formats for use in transferring spacecraft orbit information between space agencies and commercial or governmental spacecraft operators:  The Orbit Parameter Message (OPM), the Orbit Mean-Elements Message (OMM), the Orbit Ephemeris Message (OEM), and the Orbit Comprehensive Message (OCM).  Such exchanges are used for:

a)    

pre-flight planning for tracking or navigation support;

b)   

scheduling tracking support;

c)    

carrying out tracking operations (sometimes called metric predicts);

d)   

performing orbit comparisons;

e)    

carrying out navigation operations such as orbit propagation and orbit reconstruction;

f)    

assessing mutual physical and electromagnetic interference among satellites orbiting the same celestial body (primarily Earth, Moon, and Mars at present);

g)   

performing orbit conjunction (collision avoidance) studies; and

h)   

developing and executing collaborative maneuvers to mitigate interference or enhance mutual operations.

This document includes sets of requirements and criteria that the message formats have been designed to meet.  For exchanges in which these requirements do not capture the needs of the participating agencies and satellite operators, another mechanism may be selected.

This document is an international standard published under the auspices of CCSDS and International Standards Organization (ISO) Technical Committee 20, Subcommittee 13, developed jointly and in concert with the ISO TC20/SC14.  As such, this CCSDS standard is also properly labeled as ISO 26900.

The recommended Orbit Data Message format is ASCII (reference

).

This document describes both ‘Keyword = Value Notation’ (KVN) as well as Extensible Markup Language (XML) (reference 

) formatted messages.  Selection of KVN or XML format should be mutually agreed between message exchange partners.

NOTE   –    As currently specified, an OPM, OMM, or OEM file is to represent orbit data for a single spacecraft, and the OCM is to represent orbit data for either a single spacecraft or single parent spacecraft of a parent/child spacecraft deployment scenario.  It is possible that the architecture may support multiple spacecraft per file; this could be considered in the future.