<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; } @font-face { font-family: 'Cambria Math'; } @font-face { font-family: Calibri; } p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; } a:link, span.MsoHyperlink { color: rgb(5, 99, 193); text-decoration: underline; } a:visited, span.MsoHyperlinkFollowed { color: rgb(149, 79, 114); text-decoration: underline; } p.MsoPlainText, li.MsoPlainText, div.MsoPlainText { margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; } span.PlainTextChar { font-family: Calibri, sans-serif; } .MsoChpDefault { font-family: Calibri, sans-serif; } @page WordSection1 { margin: 1in; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">The OMG SpaceDTF met in Reston, Virginia March 16th & 17th. Here are the meeting highlights:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">1) XTCE</p>
<p class="MsoPlainText">XTCE 1.2 proceeds towards adoption/publication. The remaining issues (about 75) which have been agreed to and resolved must be polled and voted upon. This will occur in the next few weeks. A few minor issues have been raised by early
users of XTCE 1.2, and those items will be submitted into the OMG database and resolved or deferred before publication.<br>
</p>
<p class="MsoPlainText">---- The remaining submission paperwork is being readied to submit to the OMG Architecture Board. The AB reviews revision reports during the four weeks before each quarterly OMG Meeting and votes on adoption at the meeting. There
are a few additional steps to adoption and publication after the meeting, but this is the major technical hurdle. The 2016 OMG meetings are in March (Reston), June (Orlando), September (Chicago), and December (Coronado, CA). We should be able to get the
revision report submitted prior to the June or the September meeting if no other issues arise.<br>
</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">2) Space Information Day</p>
<p class="MsoPlainText">The SDTF is planning an OMG Space Information Day with a focus on XTCE vendors and open source tools for the OMG Meeting Dec 2016 in Coronado, CA. A list of known XTCE users and contributors was discussed at the meeting, we plan on
developing this list further and reaching out to them for participation interest, including the following: Ball Cosmos, Hawaii Cosmos, Hummingbird, Boeing (Iridium NEXT), Kratos, Harris, LM, Braxton, NASA GSFC, NASA JSC , NASA JPL, Northrop Grumman.</p>
<p class="MsoPlainText"> <br>
</p>
<p class="MsoPlainText">3) Charter RTF for GEMS 1.5</p>
<p class="MsoPlainText">No issues are currently filed against 1.4, but there was discussion of a standard "device" definition for asynchronous status subscription, and a JSON PSM for GEMS.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">4) Enterprise Ground Services (EGS</p>
<p class="MsoPlainText">The USAF has tasked Mitre with writing specifications for its Enterprise Ground Services architecture for future USAF ground systems. USAF/SMC/AD desires inputs from industry and partners through a wiki to be launched in the near future.
The OMG is actively pursuing a role in the specification process, as it did with the DoD Software Defined Radio specifications and procurements.
</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">5) RFPs</p>
<p class="MsoPlainText">The following RFPs are being developed for future publication. This list is in the current task force priority. There are many existing recommendations/specifications/standards related to the proposed RFPs, for example, SLE, PAIS,
GMSEC, and DDS, but there is interest by the SDTF industry participants in a focused specification for interoperability of products and information exchange. Compatibility with existing standards will be addressed in the RFP, and are usually described in
the RFP as a platform-specific model (PSM) requirement. <br>
</p>
</div>
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">a) Ground Data Delivery Interface (interface model for a Front-End Processor including encryption, providing/sending packets/frames). Scope <span style="font-size: 11pt;">identified in RFP template and a requirements brainstorming
session was held. Draft RFP </span><span style="font-size: 11pt; color: rgb(0, 0, 0);">developed and publication planned </span><span style="font-size: 11pt; color: rgb(0, 0, 0);">f</span><span style="font-size: 11pt;">o</span><span style="font-size: 11pt;">r
next SDTF </span><span style="font-size: 11pt;">meeting.</span></p>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">b) Satellite Operations Data Archive (interface model for satellite housekeeping telemetry and operations data archive)</p>
</div>
</div>
</div>
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">c) Display Page Information Exchange (Describe grouping and formatting of telemetry items for telemetry pages)</p>
</div>
</div>
</div>
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">d) Engineering Level Interface Specification (interface model for providing real-time telemetry and accepting command requests from ground system applications)</p>
</div>
</div>
</div>
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">e) Alarm and Event interface</p>
</div>
</div>
</div>
<div style="color:rgb(33,33,33)">
<div>
<div class="WordSection1">
<p class="MsoPlainText">f) Glossary of Ground System Terms (definition of terms for SDTF specifications and relationship to terms used in other space communities)<br>
</p>
</div>
</div>
</div>
</blockquote>
<span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(33, 33, 33);"></span><br>
</body>
</html>