[Css-csts] Proposed agenda items for intermediate CSS Plenary

[Yves.Doat at esa.int]

Dear Erik,

The CSTS charter only commit to two new services: Return Unframed Telemetry
and Radiometric services as a demonstration of the SLE Toolkit approach. As
such the monitoring service is not part of our charter.
Having said that and as you have noticed, JPL has distributed (in agreement
with the Working Group) a first draft of a possible monitoring service. The
idea of this first draft was mainly to identify the possible impact of this
service on the Toolkit definition.

It looks to me more important to address the relation between the toolkit and
the Service Management rather than focussing on one particular service only.

In my opinion the discussion should focus on how to specify this relation and
how to make sure that any future service consider the Service management in
terms of:
   Requirements:
   The new service shall identify those parameters that impact its
   configuration, its provision.
   From this list what are the parameters that impact SM?
   From this list is there new parameters that SM shall consider?
   Constraints:
   Is there any limitation in what a new service can cover?
   Is there area/parameters that a new service can or cannot modify?
   e.g. can the service modify parameters that belongs to service provision
   and/or service production?
   Do we have to foresee a mechanism that ensure SM to be aware of any
   modification?

I would therefore propose to extend your agenda item into a definition of the
relation Toolkit/future services and the SM.

Best regards.
Yves
OPS-GIB
ESA/ESOC
Robert-Bosch str.5
D-64293 Darmstadt
Tel.: (+49)-6151-902288


                                                                                                                                               
                      Erik Barkley                                                                                                             
                      <Erik.Barkley at jpl.nasa.         To:      Gerard Lapian <gerard.lapaian at cnes.fr>, Yves Doat <Yves.Doat at esa.int>           
                      gov>                            cc:      Peter Shames <Peter.Shames at jpl.nasa.gov>, Charles Ruggier                       
                      Sent by:                        <Charles.Ruggier at jpl.nasa.gov>, CCSDS Service Mgmt WG <smwg at mailman.ccsds.org>, CCSDS    
                      css-csts-bounces at mailma         CSTS-WG <css-csts at mailman.ccsds.org>                                                     
                      n.ccsds.org                     Subject: [Css-csts] Proposed agenda items for intermediate CSS Plenary                   
                                                                                                                                               
                                                                                                                                               
                      24/08/2005 21:53                                                                                                         
                                                                                                                                               
                                                                                                                                               




Dear Gerard, Yves,

I would like to propose an agenda item for the intermediate plenary CSS
meeting in Atlanta on Wednesday, September 14. Namely, coordination between
the emerging monitor service (which is a utilization of the generic
transfer service currently being developed under CSTS working group) and
its aspects that relate to overall service management.  For example:

1) Is the monitoring service required to guarantee that all monitor data
updates are provided to the service user? If not, is there something in the
service agreement that indicates the percentage of monitor data updates
guaranteed to be returned? Should this be flexible on a per contact/service
instance basis?

2) The service packages in the emerging service management specification
allow for a user to indicate an event sequence for such situations as an
orbiter being occulted by a planetary body, or changes in modulation index,
symbol rates, etc..  Should the  monitoring service report that these
events have successfully occurred (as determined by the service provider)
or is it simply to be inferred  by changes in the monitor data (by the
service user)?  If pursuing the former approach, then would it be a good
idea to provide event identifiers from service management to the monitoring
service?

3) Does the monitoring service provide indication of parameters/values that
have gone out of range or are approaching agreed-upon thresholds?  If so,
are the agreed-upon thresholds "absolute" or specified via a service
agreement and provided from service management to the monitoring service?

4) The emerging service management specification includes identifiers for
each service package, each scenario of a service package, and each service
instance within a particular scenario.  Presumably the monitoring service
will make use of these identifiers?

 From the above examples, I believe you can gain a sense of the types of
issues that I see needing coordination between Service Management and Cross
Support Transfer Services working groups.  If we could arrange for some
time to discuss these types of issues at the intermediate plenary I believe
it would be to everyone's benefit.  I believe this also represents (a
small) part of the overall set of discussions leading to a definition of a
Cross Support Services Architecture in general.

Best regards,

-Erik.



_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts