[Moims-sc] MO Mission Data Product Distribution Services
Michele Zundo
michele.zundo at esa.int
Tue Oct 27 18:19:21 UTC 2015
Yes, Dan,
I agree completely. I had the (maybe wrong) impression we were forcing specific
format strategies/logic and asking a formatting service. we should discuss how to cleanly address all different needs during the meeting though.
See you in Darmstadt
Sent from my iPhone
> On 27 Oct 2015, at 19:00, Smith, Danford S. (GSFC-5800) <danford.s.smith at nasa.gov> wrote:
>
> Michele,
>
> I will be interested to hear your thoughts in Darmstadt.
>
> I would hope that the Mission Data Product Distribution Service would work regardless of the product type or format. There may be a hundred or more different file formats and new missions may each have several unique products.
>
> I would not expect the Product Distribution Service to actually generate any products. Its job is to distribute them. Other services may exist for the product generation.
>
> If we assume it is a file distribution service, then users can subscribe to different file types, indicate how often they want files provided, identify missing files in their own list and request those, ask what is available, etc. I would assume there is an authorization process that occurs prior to a new request being honored.
>
> I am not sure that our working group needs to define the formats for inside each of the file types.
>
> Dan
>
>
> =========================
> Dan Smith
> NASA/GSFC
> Code 580
> Bldg 23, Room E443
> 8800 Greenbelt Road
> Greenbelt, MD 20771
> 301-286-2230
> Dan.Smith at nasa.gov
>
> From: moims-sc-bounces at mailman.ccsds.org [mailto:moims-sc-bounces at mailman.ccsds.org] On Behalf Of Michele Zundo
> Sent: Tuesday, October 27, 2015 11:29 AM
> To: Mehran.Sarkarati at esa.int
> Cc: moims-sc at mailman.ccsds.org
> Subject: Re: [Moims-sc] MO Mission Data Product Distribution Services
>
> Dear Mehran,
>
> thanks for this.
>
> One high level comment regards the scope for such service, which covers in
> your draft type of data coming from M&C type of systems but leave out the
> “real” mission data, “mission" being the end-product of the mission i.e. science products and related data
> either downloaded on payload link or produced by payload data processing canters
>
> I believe that we should include in the scope of this service not only TT&C TM (packets, parameters, etc)
> but also science and related data e.g. as formatted file products (level 0, Level 1 etc).
> We have already working practice and formats description standards and we
> should make sure that we define service in a generic way so that we can support that
> as well.
>
> I can elaborate more during the meeting in November.
>
> Michele
>
>
>
> On 27 Oct 2015, at 12:36 , Mehran.Sarkarati at esa.int wrote:
>
> <MDPDS.pptx>
>
> -----------------------------------------
> Michele Zundo
>
> Head of Ground System Definition and Verification Office
> EOP-PEP
> European Space Agency, ESTEC
> e-mail: michele.zundo at esa.int
>
>
>
>
>
>
>
>
> 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/20151027/390c6ba4/attachment.html>
More information about the MOIMS-SC
mailing list