Trajectory Predictions Data Formats Draft White Book CCSDS CSSM Technical Meetings Pasadena, CA, USA 23 – 27 March 2015 Jessica Reinert NASA/GRC

Discussion Topics Recap from London Walk through of White book Working session to address Service Management Abstract Classes Use Case Discussion (optional) Future Work

Trajectory Prediction – Refresher from the Fall Meetings Revised extensibility model to just be CCSDS format definitions vs bilateral definitions Further noted that NAVWG NDM spec defines the CCSDS formats All other parameters in trajectory prediction header deemed to be okay General model looks like diagram below [ Editorial question: will there ever be a need for mixing bi-lateral and CCSDS standard trajectory prediction formats? ]

White Book Population Questions Class Diagram Details XOR = Both sub-classes are flagged optional? BilateralTrajectorySegment – To include parameters or not to include parameters? Is there a standard describing NDM text based messages? Should the Annex describing the abstract classes be included in the Trajectory book or only a reference to the Simple Schedule book? Use of Service Management Abstract Classes / Initial input to the ICS Annex describing Bilateral Data Formats? Annex describing CCSDS Data Formats Reference XML Specification for Navigation Data Messages Blue Book Extracts from XML Specification for Navigation Data Messages Blue Book

Abstract Service Management Header (slide 1 of 2) Trajectory BookInfo Entity Implementation Details srvMgtMessageType (m) y originatingOrganization (m) [keeps as defined] [indictes provenenance of origniator -- even if just the warpping function] y ? generationTime (m) y ? status (m) [info entity specific] y ?

Abstract Service Management Header (slide 2 of 2) Trajectory BookInfo Entity Implementation Details version (m) [info entity specific] y ? startTime (m) [change to optional -- info entity specific] y but payload has timestamps endTime [change to optional -- info entity specific] y but payload has timestamps purpose (o) description (o)

Use Case Generation References for drafting Use Cases for creation and modification of Trajectory Prediction Segments Extensible Space Communication Cross Support – Service Management – Concept Space Communiation Cross Support – Service Management – Service Specification (Blue 1) XML Specification for Navigation Data Messages Blue Book Others?

Future Work TaskResponsible Parties 1.2 Applicability & 1.3 Rational J. Reinert Create Trajectory Prediction Use Case First draft: J. Reinert, Initial Reviewer ? Modify Trajectory Prediction Use Case First draft: J. Reinert, Initial Reviewer ? Sections 1.5 & 1.6J. Reinert Update references Update ICSC. Haddow, J. Reinert XMLSpy Diagram and Grid View J. Pietras, J. Reinert Update re-used sections to be in alignment with recently published SM books