[Moims-sc] SM&C WG WebEx#076: darft Agenda and Inputs
Mario.Merri at esa.int
Mario.Merri at esa.int
Mon Feb 16 09:38:56 UTC 2015
in preparation for the WebEx of tomorrow, please find enclosed a very
first draft agenda for the forthcoming meeting in Pasadena. I recall that
the proposed agenda will be:
1. Approval of agenda and last MoM
3. Review of actions
4. Status of documents and prototypes
5. Agenda of next SM&C WG Technical Meeting
Also PLEASE BE AWARE THAT ESA HAS SLIGHTLY CHANGED THE APPROACH TO WEBEX.
IT IS NO LONGER POSSIBLE TO BE CALLED BACK. INSTEAD YOU HAVE TO DIAL IN
USING A PROVIDED LOCAL NUMBER. FOR THE FIRST TIME, PLEASE ALLOW SOME
ADDITIONAL TIME TO JOIN THE WEBEX..
Finally, below is the status of the action to the best of my knowledge:
SC to update the SM&C-SOIS MoU with the material in the TN. Final version
(w/o change bars need to be distributed).
IH to draft a document that explains how MO service could fit to the
current ESA operational concept.
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.
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).
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.
CLOSE. RJ distributed a response to this action on 04Feb15.
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.
MZu to redline the MO Services GB (issue 3) in order to align it to
current status of SM&C, and make it more readable and user friendlier.
SG to check if the MO Service tutorial is up-to-date, in particular on how
to use the GitHub, and make it available via the MO Service Wiki on
SC, SG and IH to check the ICD of the JSC-DLR prototype and to confirm, in
case MO M&C Services are used, which parts are still needed and which
parts are now redundant and can be removed. The list of all the items that
need to be agreed between the two parties outside the standard will be
produced and a recommendation shall be provided on how to document it in
the standards. Make also a similar exercise for the COM Archive Service
both for data retrieval from the Archive and data inclusion into the
SC, SG, IH
ALL to provide SC with use cases that justify the need for the Access
SC and CC to investigate how to support PUS-C functional monitoring
feature in the M&C Check service.
CLOSED. See TN attached to email by SC of 18Dec14.
CC to compare the MO Directory Service with other similar services (e.g.
UDDI) for completeness or even need.
ALL, including the MOSSG, to provide SC with use cases for the
SC to draft a TN with the proposed expansion of the Access Control Service
and Configuration Service to meet the submitted (and implicit) use cases.
SJ 1) to rework the template for technology mappings in order to isolate
standards, implementation and encoding aspects, and 2) to map the
encodings/transports that have been already implemented in prototypes
(JMS, RMI and TCP-IP).
MW to check within DLR if there is the possibility to support, possibly
also by means of students and/or trainees, the production of a technology
BB to check if all CNES OSS could be put on GitHub (currently only the
MM to check if the EGC-CC ICD based on XTCE could be published as it may
be done for NASA/GovSat (i.e. directly in SANA).
CLOSED. Email of 17Dec14 by MM:
The ESA strategy on XTCE is to develop a tailoring of XTCE as the exchange
format for the TM/TC information of the EGS-CC, the next generation
European monitoring and control infrastructure. The scope of the EGS-CC
XTCE exchange format, XTCE-CC, has been restricted to the XTCE native
scope (TM/TC general concepts without EGS-CC specific aspects) with a
minimum set of extensions to ensure consistency of the mapping and data
exchange, without changing the semantics of the XTCE standard. In
addition, the compatibility of XTCE-CC with the ISIS XTCE (XTCE tailoring
by CNES) is being considered already for the production of the XTCE-CC.
An ICD is being produced to define the XTCE-CC tailoring, with an annex
listing the deviations with respect to ISIS ICD, and how to handle them
Response to Action
At the end of this exercise there will hopefully be a tailoring of XTCE,
XTCE-CC, that is also compatible with the CNES ISIS. This tailoring could
be a candidate for standardisation similarly as the one done by NASA with
GovSat. This will be known approximately mid 2015. It may also make sense
to wait for the publication of XTCE1.2.
A. European S/C and US MCS: Option 1: US MCS use XTCE-CC native; Option 2:
European S/C generates GovSat; Option 3: A converter exists
B. US S/C and European MCS: Option 1: European MCS use GovSat native;
Option 2: US S/C generates XTCE-CC; Option 3: A converter exists
C. Interoperability between ESA and CNES
D. Use either GovSat/XTCE-CC to exchange TM/TC info with other
applications within the ground segment (e.g. MPS, SIM, FDS)
SC to provide RJ/KR information on which M&C Service table to look at in
order to do the matching with XTCE.
CLOSED. Email 28Nov14 by SC.
SC to provide the list of M&C Services fields on which the Update
operations is enabled. Due
DS to provide an update on the status of the C++ Language API.
ALL agencies to identify whether they can support the second prototype for
the ZeroMQ binding.
DS to confirm the schedule for the C++ MAL API binding.
SC to add a README file in the root of GitHub repositories pointing to the
MO Wiki and to add relevant material from the OSS presentation in to the
CC to devise a high level tutorial and place it on the MO Wiki on GitHub.
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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: A01_15S-SMC WG Agenda v1.doc
Size: 49664 bytes
Desc: not available
More information about the MOIMS-SC