CCSDS 508.0-R-1, Conjunction Data Message (Red Book, Issue 1 ...

More documents

Recommendations

Info

DRAFT CCSDS RECOMMENDED STANDARD FOR CONJUNCTION DATA MESSAGESTable B-2: Heritage RequirementsID Requirement Rationale TraceCDM-H01The CDM shall be provided in, orshall include, an ASCII format.ASCII character-based messagespromote interoperability. ASCIImessages are useful in transferringdata between heterogeneouscomputing systems, because theASCII character set is nearlyuniversally used and is interpretableby all popular systems. In addition,direct human-readable dumps of textto displays, emails, documents orprinters are possible withoutpreprocessing.3.1, 4.2CDM-H02The CDM shall not require softwaresupplied by other Agencies.This principle was agreed upon earlyin the history of the CCSDS NavigationWorking Group.n/aTable B-3: Desirable CharacteristicsID Requirement Rationale TraceCDM-D01CDM-D02CDM-D03CDM-D04CDM-D05The CDM should be extensible withno disruption to existing users/uses.The CDM should be as consistentas reasonable with any relatedCCSDS Recommended Standardsused for earth-to-spacecraft orspacecraft-to-spacecraftapplications.CDM originators should maintainconsistency with respect to theoptional keywords provided in theirimplementations; i.e., thecomposition of the CDMs providedshould not change on a frequentbasis.The CDM should allow the option fororiginators to provide a probability ofcollision of the two objects involvedin the conjunction.The CDM should provide informationwith which each object’s sphericalradius may be calculated.Space agencies and operatorsupgrade systems and processes onschedules that make sense for theirorganizations. In practice, someorganizations will be early adoptersbut others will opt to wait untilperformance of a new version of theCDM has been proven in otheroperations facilities.Ideally, the set of RecommendedStandards developed by a givenCCSDS Working Group will beconsistent.Implementations that change on afrequent basis do not promote stableoperations or interoperability.Some CDM originators will beinterested in providing this datum.Cited as desirable by ISO 16158(reference [D2]).The object radius is required forcalculation of collision probability inmost methods, which usually modelobjects as spheres given the lack ofattitude information.Table 3-1n/an/aTable 3-2Table 3-4CCSDS 508.0-R-1 Page B-4 March 2012
DRAFT CCSDS RECOMMENDED STANDARD FOR CONJUNCTION DATA MESSAGESID Requirement Rationale TraceCDM-D06CDM-D07CDM-D08The CDM should provide thethreshold of close approach used bythe originator in the screening.The CDM should provide thecomponents of the relative positionat the time of closest approach.The CDM should provide the relativevelocity of the two objects in theconjunction at the time of closestapproach.This datum is desirable in order toassess the risk of collision andassess potential preventivemeasures. Cited as desirable by ISO16158 (reference [D2]).These data allow an operator toquickly do a first-order qualitativeassessment of the probability ofcollision immediately upon receipt ofa CDM.This datum is desirable in order toassess the risk of collision andassess potential preventivemeasures. Called out as desirable byISO 16158 (reference [D2]).Table 3-2Table 3-2Table 3-2CCSDS 508.0-R-1 Page B-5 March 2012
Page 5 and 6: DRAFT CCSDS RECOMMENDED STANDARD FO
Page 55: DRAFT CCSDS RECOMMENDED STANDARD FO
Page 85: DRAFT CCSDS RECOMMENDED STANDARD FO

CCSDS 508.0-R-1, Conjunction Data Message (Red Book, Issue 1 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?