Object Management Group OMG Standards Organization Update including

Object Management Group (OMG) Standards Organization Update - including XTCE discussion related to CCSDS books DAN SMITH AND KEVIN RICE NASA GSFC APRIL 9, 2018 CCSDS MEETINGS. GAITHERSBURG, MARYLAND USA

OMG Activities Background ◦ The Object Management Group (OMG) is a very broad standards group ◦ Overall, is much larger than CCSDS, but that is because its scope is much broader ◦ Space Domain Task Force (SDTF) typically has about 15 attendees ◦ Mix of vendor, contractor, and government communities ◦ Intent is to co-exist with CCSDS and not to duplicate efforts, focus is slightly different ◦ Quarterly meetings, but SDTF usually meets 3 times per year ◦ Recently decided to cancel their request to develop a new planning standard once they became aware of the CCSDS standard that was almost complete ◦ Mario Merri is the CCSDS liaison. Dan Smith is NASA’s technical rep. Recent News ◦ ◦ ◦ XTCE 1. 2 approved to begin publication cycle Command Control Message Specifications (C 2 MS) approved to begin review cycle Cubesat Reference Model in SDTF review GEMS (for controlling ground equipment) used in multiple vendor products Glossary/Ontology and display exchange potential standards being discussed April 9, 2018 OMG UPDATE 2

XTCE 1. 2 Details and XUSP Status XTCE 1. 2 was “essentially approved” by OMG at the March 2018 Reston Meeting ◦ ◦ ◦ Mostly backwards compatible syntax But some syntactic fixes: a few spelling errors, string length and arrays are larger updates Annotation: cleaned up and added to significantly Schema type cleanup – improved type to class mappings (see next page for more comprehensive list) XTCE 1. 1 to XTCE 1. 2 translator available ◦ Currently through the open source “xtce viewer” on gitlab XTCE 1. 3 Task Force created because of OMG process ◦ No specific work at this time XUSP – 1. 2 “Gov. Sat” RTF created ◦ To create alignment with XTCE 1. 2 ◦ Schedule: goal is to have a reviewable draft in the next few weeks in time for the Boston OMG meeting (June) Process started for “XTCE 2. 0” ◦ Convert to a model specification (UML), with XTCE syntax as one implementation, possibly JSON or others. ◦ No specific schedule April 9, 2018 OMG UPDATE 3

XTCE 1. 2 The Big List Of Changes A variety of small syntax changes including some misspellings and other similar issues String length modified – strings that are variable within in a fixed box are common, added Arrays changed so dimensions can be specified at the definition not just where they are used Unit is optional Fixes or additions to various float encodings Schema types cleaned up to improve type to class mappings Lots of annotations updated or added (honorable mention: where there was a list of 10 enumerated values, now there are 50 values) (To be improved) April 9, 2018 OMG UPDATE 4

What does this mean for CCSDS documents? XTCE Blue Book ◦ ◦ ◦ Must wait for final edited release from the OMG. Probably September 2018. OMG version will be distributed for Agency Up/Down vote If approved, it will be the new version of our Blue Book If approved with comments, then the comments will be provided to the OMG for future consideration If rejected, then the OMG will probably become the sole owner of the standard The first green book, the so called “manager’s book” ◦ ◦ No major updates, no minor updates… no changes? Is it time for the 5 -year review? NASA accepts the action to review to determine update need. If no changes, we should still renew it. The second green book, the “elements” book ◦ ◦ Some syntax diagrams no longer match and need to be updated Updates to diagrams, text and examples may be needed There may be a few errors/issues. A few people have suggested this but the set appears to be very limited NASA accepts the action to review and update. Should it become a new project? April 9, 2018 OMG UPDATE 5

Command Control Message Specification (C 2 MS) • Set of about 40 message formats for common interface elements of command control systems • Allows for interface commonality across vendor products and for simplified system integration • MCMS is the interim name for the GSFC GMSEC message set. It will be renamed to C 2 MS later this year. Not the GMSEC API, software, components or reference architecture. No security or message transport. • GMSEC will be C 2 MS compliant, as will many U. S. commercial products. • One could say there is some level of implied service capability, since there are several interaction patters and messages can relate to each other in some cases. It has a defined wrapper-type of header plus the message contents described in UML. The current platform specific approach is XML, but could (in theory) also generate a JSON or ASCII compliant message structures. For NASA GMSEC compliant systems, the C 2 MS first header becomes the routing field (subject name). • Where practical, C 2 MS used message contents as defined by CCSDS. Examples are the telemetry or command packets and the navigation messages. • It is following the RFC route within the OMG. This allows for proven “almost standards” which have some level of broad acceptance to become actual standards following a comment period. Very different from the group effort to define a new standard. C 2 MS met the widely accepted criteria. • Boeing is discussing an addition for XTCE query message formats. • Was submitted by NASA to the OMG in early 2018 and received approval votes from the Space Domain Task Force and the OMG Architecture Board in March 2018. It is now out for OMG review, then update, then final approval in late 2018. • Note that CCSDS MOIMS Area Director feels there is some level of overlap between C 2 MS and MO. April 9, 2018 OMG UPDATE 6

OMG New Work Cubesat Reference Model ◦ ◦ Model-based description of a cubesat Developed by the International Council on Systems Engineering (INCOSE) and broght to the OMG formal standardization Intent is to provide a working framework for the study and eventual design of cubesats Goal is to have it widely used at the University level so students can claim a common knowledge base when they look for employment ◦ Has been submitted for OMG consideration, but there were too many comments for first level of acceptance – will try again at next meeting Mission Operations and Ground Data System Glossary/Ontology ◦ CCSDS has a collection of terms defined in a SANA registry, but there is no oversight, many duplicates, no relationships, etc. ◦ OMG has suggested for years that this would be a good thing, but the benefit relative to the effort required is questionable ◦ How easy is it to define a word like “telemetry”? Display Exchange Standard ◦ A general display standard may not be possible – too many creative displays use graphics or images, are interactive, linked to other applications, etc. ◦ General guidelines – RED is bad, GREEN is good, use Microsoft cut-and-paste rule may seem trivial ◦ Possible value in an exchange format for straight-forward text-based telemetry pages so that basic display definitions can be shared or moved from one system to another. Could auto-generate a first set of displays from an XTCE file and import it to any number of telemetry and command systems of display tools. ◦ In early discussion phase, no significant work at this point April 9, 2018 OMG UPDATE 7