[Smwg] Planning Data Formats Book - Need for a "Simple Service Request"

[Colin.Haddow at esa.int]

Hi JP,
            it would be the first case, i.e. A service as in what would be
requested via a Service Package Request.

With respect to whether it fits into the planning data formats book, this
comes back to the discussion from London, which I think we never completely
resolved, as to what the differences (if any) were between planning requests
and service package requests. Maybe that we need to close that out, your
slides from the 9th of December would be useful to drive that discussion (I
don't recall discussing these at any of the WebExs, but if it was the one I
was late for please accept my apologies)...

Cheers for now,

Colin

---------------------------------------------------------------------------------------------------------

Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,
Germany.

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int
---------------------------------------------------------------------------------------------------------





From:       "Chamoun, Jean-Pierre (GSFC-458.0)[SGT INC]"
            <jean-pierre.chamoun at nasa.gov>
To:         "Colin.Haddow at esa.int" <Colin.Haddow at esa.int>, CCSDS Service Mgmt
            WG <smwg at mailman.ccsds.org>,
Date:       05/02/2015 18:11
Subject:    Re: [Smwg] Planning Data Formats Book - Need for a "Simple
            Service Request"



Colin,

A quick question:  when you say a Simple "Service" Request do you mean
   1- A service as in what would be requested via a Service Package
Request?
   2- Or do you mean a request for planning data (as a service)?

If it is #2 then I understand why you would add this to the Planning Data
book.

If it is #2 then I feel that this input can be used to structure the
Service Package Request to have a minimally required structure that fits
this "Simple Service Request" (for example), but I don't see how it would
fit in the Planning Data book.

Can you clarify?

Best regards,
JP

--
Jean-Pierre Chamoun
NASA Goddard Space Flight Center
Space Network Ground System Sustainment (SGSS)
Code 458 Building 12 Room N204
Greenbelt, Maryland  20771


Tel: 301-286-5053
email: jean-pierre.chamoun at nasa.gov






On 2/5/15 12:02 PM, "Colin.Haddow at esa.int" <Colin.Haddow at esa.int> wrote:

>
>Dear all,
>                 I've been having some discussions here at ESOC with our
>scheduling guys and one of the real world issues that they are having to
>deal
>with is the need for a standard "Simple Service Request".  This has
>arisen in
>dealings with both a commercial organisation and an international
>partner. In
>view of this I'd like to discuss the possibility of adding such a "Simple
>Service Request" to the Planning Data Formats Book. I've got a few ideas
>from
>our discussion here and would be happy to discuss these at the next WebEx
>if
>there is room on the agenda.
>
>Essentially what is required is the ability to submit a service request
>for a
>specified time period, station and antenna along with reference to a
>configuration profile and possible (permitted) updates to some of the
>configuration profile parameters. Three operations would be supported
>
>NEW                     -  submit a new request,
>REPLACE           -    replace an existing request
>DELETE            -     delete an existing request.
>
>An initial pass at a UML model is attached below.
>
>I'd appreciate your feedback on whether you think that this is a useful
>addition to the Planning Data Formats.
>
>Cheers for now,
>
>Colin
>
>(Embedded image moved to file: pic23856.gif)
>
>
>
>--------------------------------------------------------------------------
>-------------------------------
>
>Dr. Colin R. Haddow,
>HSO-GI, European Space Agency,
>European Space Operations Centre,
>Robert-Bosch-Str 5,
>64293 Darmstadt,
>Germany.
>
>Phone; +49 6151 90 2896
>Fax;      +49 6151 90 3010
>E-Mail;  colin.haddow 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.