<font size=2 face="Arial">Dear CMC and CESG,</font>
<br>
<br><font size=2 face="Arial">Please find below the report in subject.</font>
<br>
<br><font size=2 face="Arial">Regards,</font>
<br>
<br><font size=2 face="Arial">__Mario</font>
<br>
<br><font size=2 face="Arial">==========================================</font>
<br>
<br><font size=4 face="Arial"><b>CCSDS-OMG Liaison: Report to CMC and CESG</b></font>
<br>
<br><font size=2 face="Arial">MOIMS AD attended the Object Management Group
(OMG) Space Domain Task Force (SDTF) meeting in his function as CCSDS liaison.</font>
<br><font size=2 face="Arial">The meeting took place 08Jun17 between 09:00-12:00
in Brussels.</font>
<br>
<br><font size=2 face="Arial"><b>Participants:</b></font>
<br><font size=2 face="Arial">- Brad
Kizzort, Harris corp</font>
<br><font size=2 face="Arial">- Thomas
Vergnaud, Thales (part time)</font>
<br><font size=2 face="Arial">- Steven
MacLaird, OMG staff</font>
<br><font size=2 face="Arial">- Jeff
Smith, Multi Agency Collaboration Environment (MACE) (part time)</font>
<br><font size=2 face="Arial">- Mario
Merri, CCSDS MOIMS.</font>
<br>
<br><font size=2 face="Arial">Brad Kizzort delivered a presentation on
the OMG process and on the SDTF current and future work (attached).</font>
<br>
<br><font size=2 face="Arial"><b>SDTF Active Specifications:</b></font>
<br><font size=2 face="Arial">- XTCE
1.1 (2008)</font>
<br><font size=2 face="Arial">- XTCE
for US government S/C conformance profile (XUSP) (2015)</font>
<br><font size=2 face="Arial">- Ground
Equipment Monitoring Service (GEMS 1.4) (2015)</font>
<br><font size=2 face="Arial">- Satellite
Operations Language Metamodel (SOLM) (2012)</font>
<br>
<br><font size=2 face="Arial">The last 3 specifications will most likely
be adopted by the US Air Force in the context of their Enterprise Ground
Services (EGS).</font>
<br>
<br><font size=2 face="Arial"><b>SDTF On-going Work:</b></font>
<br><font size=2 face="Arial">- XTCE
1.2, RTF has disposed 196 out of 226 RIDs.</font>
<br><font size=2 face="Arial">o Version
1.2 is meant to be forward compatible with version 1.1. Boeing is developing
a tool to convert from 1.1 to 1.2, which will be open source</font>
<br><font size=2 face="Arial">o SDTF
plan to have the final draft 4 weeks before the New Orleans meeting that
will start on 25Sep17</font>
<br><font size=2 face="Arial">o In order
to adopt the new version (as done already for version 1.1., CCSDS will
probably have to do a yes/no Agency Review on Version 1.2</font>
<br><font size=2 face="Arial">o Regarding
the CCSDS Prototyping: either changes in 1.2 do not require additional
prototype effort (current baseline) or NASA could leverage on the already
existing tools developed by Boeing (open sourced) and Northrop Grumman</font>
<br><font size=2 face="Arial">- Upgrade
of XUSP has to wait for finalisation XTCE 1.2</font>
<br><font size=2 face="Arial">- GEMS
1.5: Current version, 1.4, supports ASCII and XML. Vendors would like to
extend to Javascript Object Notation (JSON)</font>
<br>
<br><font size=2 face="Arial"><b>SDTF Short Term Roadmap</b></font>
<br><font size=2 face="Arial">- CubeSat
Reference Model</font>
<br><font size=2 face="Arial">o INCOSE
group led by Dave Kaslow has defined a system engineer process to be used
for cubesats.</font>
<br><font size=2 face="Arial">o They
will submit an RFC to OMG in 2017</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: No overlapping identified</font>
<br><font size=2 face="Arial">- GMSEC
Message Specification</font>
<br><font size=2 face="Arial">o Defines
GMSEC message set as a model driven specification</font>
<br><font size=2 face="Arial">o Submission
of RFC planned for the September meeting in New Orleans</font>
<br><font size=2 face="Arial">o Dan
Smith has very successfully lobbied with the US AF to get GMSEC adopted
in their EGS.</font>
<br><font size=2 face="Arial">o MM will
ask Dan Smith for an early draft of the submission</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: Needs to be coordinated with SM&C</font>
<br><font size=2 face="Arial">- Archive
Exchange</font>
<br><font size=2 face="Arial">o The
purpose is to exchange satellite operations archive (mainly TM/TC) between
operations centres so that the receiving control centre could take over
operations seamlessly.</font>
<br><font size=2 face="Arial">§ This
project is promoted by two US vendors: Harris and Crayton</font>
<br><font size=2 face="Arial">§ Considered
use cases are:</font>
<br><font size=2 face="Arial">· For
transfer of integration archive from satellite integrator to initial operator</font>
<br><font size=2 face="Arial">· For
transfer of operations archive between satellite operators</font>
<br><font size=2 face="Arial">· For
transfer of operations archive during ground system technical refresh</font>
<br><font size=2 face="Arial">§ The
work has not started yet, it may require to define a canonical format (or
schema) for an operational archive.</font>
<br><font size=2 face="Arial">§ Danger
of overlapping: we agreed that Brad will share any initial material with
the DAI through the liaison.</font>
<br><font size=2 face="Arial">o The
purpose is to exchange satellite operations archive (mainly TM/TC) between
operations centres so that the receiving control</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: Needs to be coordinated with DAI</font>
<br><font size=2 face="Arial">- GEMS
1.5 (JSON): see above.</font>
<br>
<br><font size=2 face="Arial"><b>Future Activities (at this time only vaguely
in the radar of the SDTF)</b></font>
<br><font size=2 face="Arial">- Telemetry
Display Page Definition Exchange</font>
<br><font size=2 face="Arial">o The
purpose is to transfer displays across control centres</font>
<br><font size=2 face="Arial">o Maybe
an extension to XTCE</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: no overlapping identified.</font>
<br><font size=2 face="Arial">- Ground
Data Delivery Interface</font>
<br><font size=2 face="Arial">o The
purpose is to move binary TM and TC directly to/from the modem in the ground
station</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: To be looked by CSS. The concept may be that the CC talks
to the GS via SLE and that within the GS this new standard is used to talk
to the GS modem.</font>
<br><font size=2 face="Arial">- Alert
Management</font>
<br><font size=2 face="Arial">o How
do I notify a network of users of significant event in the system</font>
<br><font size=2 face="Arial">o The
OMG C4I specs meets already the needs of the US Airforce. The SDTF will
not pursue this further</font>
<br><font size=2 face="Arial">- Goddard
Core Flight Services</font>
<br><font size=2 face="Arial">o Goddard
has SW capabilities called CFS for OB standardisation of cubesat that they
consider standardising via OMG.</font>
<br><font size=2 face="Arial">o CCSDS-OMG
liaison view: no overlapping identified.</font>
<br><font size=2 face="Arial">- Spacecraft
Operations Ontology</font>
<br><font size=2 face="Arial">o RFI
issued</font>
<br><font size=2 face="Arial">o Looked
at SANA</font>
<br><font size=2 face="Arial">o Most
likely this work will no progress as there is now little support by US
AF.</font>
<br><font size=2 face="Arial">MoU</font>
<br><font size=2 face="Arial">OMG prefers an informal interface. Nevertheless
Steve agreed on the proposal that I will draft the CCSDS-OMG MoU.</font>
<br>
<p><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>