[Css-csts] A#01-0510S : review of the parameter list provided by ESA

Wed Aug 11 09:57:06 EDT 2010

Dear Francois,

Thank you for your feedback regarding the candidate monitored parameters that
at last I manage to look at. For specific issues, I have inserted my response
into the table proper. In addition, I should like to share with you some more
general considerations as follows:

You are absolutely correct that the table contains quite a number of
parameters that are also accessible via the SLE (or possibly CSTS) service
interface. At first glance it therefore appears redundant to make these
parameters also accessible via a dedicated monitoring service. But the key
question here is who will be the user of these monitored parameters. Even if
I disregard for now a true cross support scenario, within ESA the SLE client
is the Flight Control Team. Their expertise is primarily on the spacecraft
side and to a lesser extent on ground stations. The team in charge of the
operating the stations is much more interested in a number of these 'SLE
parameters' than the actual SLE user and therefore even internal to ESA it
makes sense to have these SLE parameters also accessible via the separate
path of a monitored data service.

When it comes to actual cross support, this becomes even more important as
being responsible for the provisioning of services to an external client, I
want to have know exactly what is going on and therefore need the capability
to closely monitor my SLE providers although I'm not the user of the SLE
services. Granted, as this is internal to an agency one can come up with
proprietary monitoring capabilities, But if I can have the same monitoring
regardless of the station being operated by ESA or another agency, such
uniform capability is of advantage.

For the above reasons I think that what John had originally proposed is
useful in real world operations and therefore I have incorporated these
parameters following John's suggestions.

You are also correct that it should not be necessary to have parameters
monitored whose values are the result of mutually agreed configurations. On
the other hand, I have been in situations on console where due to a
combination of language and terminology issues it was very difficult to
figure out via the voice loop what the actual configuration looked like and
what one could possibly do in terms of corrective action. Therefore, although
the need to monitor these parameters will be rare, they might be very useful
in critical situations.

Best regards,

Wolfgang

(See attached file: Monitored parameters list- CNES comments WH reply.doc)

  From:       "Lassere Francois" <francois.lassere at cnes.fr>                                                                                     

  To:         <css-csts at mailman.ccsds.org>                                                                                                      

  Date:       01/06/2010 16:36                                                                                                                  

  Subject:    [Css-csts] A#01-0510S : review of the parameter list provided by ESA                                                              

  Sent by:    css-csts-bounces at mailman.ccsds.org                                                                                                

Dear CSTS WG colleagues,

Please find below attached the CNES review of the monitored data parameter
list provided by ESA with some comments or questions.
Best regards.

François
[attachment "Monitored parameters list- CNES comments.doc" deleted by
Wolfgang Hell/esoc/ESA] _______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts

-------------- next part --------------
A non-text attachment was scrubbed...
Name: =?ISO-8859-1?Q?Monitored_parameters_list-_CNES_comments_WH_rep?=
	=?ISO-8859-1?Q?ly=2Edoc?=
Type: application/msword
Size: 311296 bytes
Desc: not available
Url : http://mailman.ccsds.org/pipermail/css-csts/attachments/20100811/e6820210/ISO-8859-1QMonitored_parameters_list-_CNES_comments_WH_repISO-8859-1Qly2Edoc-0001.dot