[Moims-sc] Actions 140402-02 and 140402-03
Mario.Merri at esa.int
Mario.Merri at esa.int
Tue Aug 19 08:51:41 UTC 2014
For your Info.
__Mario
----- Forwarded by Mario Merri/esoc/ESA on 19/08/2014 10:50 -----
From: "Jones, Ronald A. (GSFC-443.0)[ASRC MANAGEMENT SERVICES INC]"
<ronald.a.jones at nasa.gov>
To: Mario Merri <Mario.Merri at esa.int>, "Smith, Danford S. (GSFC-5800)"
<danford.s.smith at nasa.gov>,
Date: 18/08/2014 21:44
Subject: FW: [Moims-sc] SM&C WG WebEx #074
Mario,
Action Item responses.
140402-02) SOIS schema compatibility to XTCE
There is a certain amount of ?compatibility? between some parts of these
two schemas making conversion between an instance document in one to the
other possible, even desirable. The SOIS schema is partially based on
XTCE. However because SOIS is ?tuned? towards flight software and since
XTCE is ?tuned? to ops, there?s some conceptual differences reflected in
the syntax. The part of each that has significant overlap is in regards
to telemetry and command definitions ? although not all aspects of them
are represented one to one between the two schemas. For example, it is
possible to convert a telemetry packet definition in a SOIS XML document
to an XTCE XML document. However, there are caveats. It is known that
there is not always a one to one mapping between FSW constructs and ops
definitions of a telemetry packets at various institutions. Typically
these are ?header? areas or other items which involve ?bit level sub
addressing? of a telemetry word in a telemetry packet definition. For
example at GSFC the Flight Software (FSW) may represent the CCSDS header
in C using a ?struct? syntax perhaps with some bit-masks or something to
that effect to get at ?bit subfields?. On the ground however the various
items in the CCSDS header may be separated out as individual telemetry
parameters, even 1 bit parameters. The two XML descriptions (SOIS, XTCE)
would not be a simple one to one mapping. Although, in some cases it
would be. Instead, a user with knowledge of their institutions ?way of
doing things? should be able to write conversion tools between them. Some
information in XTCE will not go into SOIS. Example, alarms are not used
in FSW. Likewise state machines describable in SOIS syntax would not be
transferred to XTCE as it would not make sense to do so. For the main
areas of overlap, the description the telemetry and command packets in FSW
and XTCE conversion is possible. It should be noted I do not know of any
significant effort in this area that has been undertaken to prove the
concept, however GSFC is interested in this ?SOIS use case.? No one has
implemented such a conversion effort to date that Goddard is aware of.
140402-03) XTCE 1.2
The OMG XTCE RTF (Revision Task Force) has been meeting weekly for several
months to resolve the 1.2 issues. The OMG XTCE issues database has
accumulated 361 issues since 2008. The effort is centered around
reviewing, dispensing or accepting the issues. The RTF has successfully
gone through this process and captured about approximately 50 issues that
will constitute XTCE 1.2. The goal now is to produce a new schema with
significant backwards compatibility to XTCE 1.1 while at the same time
addressing the real issues that are effecting all users, to improve XTCE
so it is more usable and transferrable between parties, and with less
customization needed. Further the RTF has pledged to produce a public
domain conversion tool from XTCE 1.1 and XTCE 1.2 this will greatly help
the user community. There is a candidate XTCE 1.2 schema that addresses
all of the approximately 50 items. It is still however being reviewed
by participants and it is likely to change somewhat in the next few weeks.
The changes should at this point be minor. There is a review period
though September 2014 (OMG Quarterly Meeting in Austin, TX). Then
complete the required OMG documents (Change Form) for submission during
the December 2014 OMG Quarterly Meeting. A ?fall-back? schedule has the
OMG documents submitted at the Spring Quarterly Meeting in Reston
Virginia. The goal is to produce in the same time frame the conversion
tool.
--
Ronald A. Jones
ASRC Federal Space and Defense (AS and D), Inc.
Customer Focused, Operationally Excellent
7000 Muirkirk Meadows Drive, Suite 100
Beltsville, MD 20705-2518.
AS&D Cell Phone (best number to reach me): 410-596-1796
ASRCA Front Desk Phone: 301-837-5500
ASRCA E-Mail: ronald.jones at asrcfederal.com
NASA/GSFC JWST Project (Code 443)
NASA/GSFC Phone: 301-286-6781
NASA/GSFC Fax: 301-286-7021
NASA E-Mail: Ronald.A.Jones at nasa.gov
From: Mario Merri <Mario.Merri at esa.int>
Date: Thursday, July 31, 2014 5:25 AM
To: "moims-sc at mailman.ccsds.org" <moims-sc at mailman.ccsds.org>
Subject: [Moims-sc] SM&C WG WebEx #074
Hi everyone,
I would like to add a new agenda item to discuss "M&C Services RIDs". I
propose that Sam distributes in advance of the WebEx any major outstanding
issue. If need be we might then organise a dedicated WebEx. The updated
proposed agenda (please provide any amendment) is now:
1. Approval of agenda and last MoM
2. Review of actions
3. Status of documents and prototypes
4. Agenda of next SM&C WG Technical Meeting
5. CWE Schedule Update
6. Technology Binding Poll
7. M&C Services RIDs
8. AOB.
Regards,
__Mario
----- Forwarded by Mario Merri/esoc/ESA on 31/07/2014 11:22 -----
From: Mario Merri/esoc/ESA
To: moims-sc at mailman.ccsds.org,
Date: 30/07/2014 11:20
Subject: SM&C WG WebEx #074
I would like to organise a WG WebEx and I propose the 19Aug14. I will
distribute an invitation. The proposed agenda (please provide any
amendment) include
1. Approval of agenda and last MoM
2. Review of actions
3. Status of documents and prototypes
4. Agenda of next SM&C WG Technical Meeting
5. CWE Schedule Update
6. Technology Binding Poll
7. AOB.
The status of action is as below.
Regards,
__Mario
ID
Action
Due
Actionee
Status
111102-01
SC and Stuart to update the SM&C-SOIS MoU with the material in the TN.
Final version (w/o change bars need to be distributed).
01Nov14
SC
OPEN.
130416-03
IH to draft a document that explains how MO service could fit to the
current ESA operational concept.
30Jun14
IH
OPEN.
131029-02
BB to investigate the possibility of documenting the ISIS zeroMQ
Technology Binding into a draft CCSDS BB.
30Jun14
BB
OPEN.
131029-04
SC to establish a public repository of known issues on published books and
distribute instructions on how to consult the repository and on how to
submit new issues.
30Jun14
SC
OPEN.
131031-04
MM to identify way of collecting information on activities relevant to MO
services (e.g. lists of studies, developments, prototypes, OSS, ?), maybe
using the CCSDS Wiki).
30Jun14
MM
OPEN.
140204-01
Following the response to Action 131029-05 (see MoM of WebEx #071), DS to
validate if the MO data model for the parameter service fits with XTCE
using a side-by-side table.
01Nov14
DS
OPEN.
140331-01
SC to finalise a first cut of the CCSDS MO Tool Kit Wiki for developers (
https://github.com/esa/CCSDS_MO/wiki, inform the WG and request
contributions/extensions.
30Apr14
SC
OPEN.
140331-02
SC to agree with PS and document 2 or 3 scenarios where the SCCS-ARD
charts could be extended to include MO services/MO Stack.
30Jun14
SC
OPEN.
140331-03
MM to update the CWE to reflect the agreement that the old Data Product
Management Service is split into File Management Service and Mission Data
Product Distribution Service.
30Jun14
MM
CLOSED.
140401-01
All agencies (who have not yet done so) to respond to the poll on the best
G2G Technology Bindings.
30Apr14
ALL
CLOSED.
140401-02
SJ to draft a list of criteria against which each proposed Transport level
binding will be evaluated.
07May14
SJ
OPEN.
140401-03
ALL to review at high level the Common Service BB to identify macroscopic
errors or missing material.
30Jun14
ALL
OPEN.
140401-04
NC to distributed to the WG the Common Service specifications defined by
the ISIS contractors.
30May14
NC
OPEN.
140401-05
SC/RT to define a schedule for the production of the Common Services BB.
30Apr14
SC/RT
CLOSED. SC confirmed that the first draft of Common will be available for
end of Aug14
140401-06
ALL to review the MO Brochure.
15Apr14
ALL
CLOSED.
140402-01
MM to distribute the ESA tailoring of XTCE to the WG.
30Apr14
MM
CLOSED. Distributed on 10Jun14.
140402-02
DS/RJ to report on the SOIS use of XTCE for Electronic Data Sheets to
ensure compatibility with XTCE.
30Apr14
DS/RJ
OPEN.
140402-03
RJ to distribute to the WG the 52 XTCE changes that are proposed to be
implemented into XTCE1.2 (also to confirm that we do not need a
prototype).
30Apr14
RJ
OPEN.
140402-04
MM to use the TRL to document the status of the MO services and its
roadmap.
30Jun14
MM
OPEN.
140402-05
SC to put the MO Services GB and the Reference Model MB on GoogleDocs and
to inform the WG members by providing basic instructions/conventions on
how to review the documents.
30Apr14
SC
CLOSED.
140402-06
IH to draft a concept paper on Emergency Service.
01Nov14
IH
CLOSED.
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.
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20140819/99e15866/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20140819/99e15866/attachment.txt>
More information about the MOIMS-SC
mailing list