[Smwg] Planning Data Formats Book - Need for a "Simple Service Request"
Marcin.Gnat at dlr.de
Marcin.Gnat at dlr.de
Fri Feb 6 08:48:42 UTC 2015
Dear All,
I agree with Erik, that we should discuss that in more deep. As I know our WG, this will lead to longer discussion during Pasadena meetings...
Anyway, some points which come to my mind immediately:
- first of all I find it not right to put Service Request into the Planning Book (this dilutes even more our already diluted ;-) book-system)
- we may think to expand the Service Package Request and Service Package Book with another info entity which would be "Simple Service Request"
- DLR is coming rather also from the "simple things" corner, and we welcomed very much the "Simple Schedule", which is definitely simpler that SM-1 Schedule of Services...
- ... but I already let me convince from SMWG-gurus, that for the Schedule Request (which is what we principally use right now) in the SM-future we will have just Service Package Request and it will be enough. So now I do not completely follow why we should have another type of request for service...
- I agree with Erik also that the notion of "new", "replace" and "delete" goes into direction of automation or other words something which belongs rather to "Management Services" book which is planned to 2019/2020. And as far I recall, we did not really touched on that yet (apart of the keeping in mind SM-1).
- on the other hand - we also noticed that we launched with file format books pretty nicely, but completely disregarding the "2020 framework", and so we already need corrections for example with respect to header information. Maybe we need to talk already now about automation and what shadows it casts on every information entity file format and its usage. What is the point here - we risk here larger delays in our plan (I do not think we can manage yearly cycle of books, but this is just my opinion). Also as we include all this general-management stuff into each info entity file, we will have to cope with that during prototyping (again - less hope it will be simple nice file exchange).
Best regards
Marcin
-----Original Message-----
From: smwg-bounces at mailman.ccsds.org [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Barkley, Erik J (3970)
Sent: Freitag, 6. Februar 2015 03:53
To: Chamoun, Jean-Pierre (GSFC-458.0)[SGT INC]; Colin.Haddow at esa.int
Cc: CCSDS Service Mgmt WG
Subject: RE: [Smwg] Planning Data Formats Book - Need for a "Simple Service Request"
Colin,
I believe we can certainly make room for the follow-up discussion from the London meetings which we really have not gotten into very much (for obvious reasons due to more immediate concerns). I think we definitely need to have that discussion. At the moment my main concern is that we haven't had time to consider the ramifications on the overall concept as it appears that this is also starting to touch upon the eventual automation recommendation by discussion of operation such as new replace, etc.
To perhaps help regain some of the context (for those who were not able to attend the London meetings) my recollection from the London meetings is that ESA prefers an ability to request very refined sets of potential service opportunities (i.e. return of planning data) as opposed to the general NASA practice (as best as I understand it) of returning a fairly broad set of information and letting the user then select and sort through the information of use to them. The discussion was then that there are potentially some conceptual parallels between expressing such constraints for planning data return and those constraints for expressing specific service (execution) commitments. My sense is that both of these play into what ESA calls "standing orders". Perhaps we can start here as a conceptual basis for the discussion on the WebEx/teleconference next week?
Best regards,
-Erik
-----Original Message-----
From: smwg-bounces at mailman.ccsds.org [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Chamoun, Jean-Pierre (GSFC-458.0)[SGT INC]
Sent: Thursday, February 05, 2015 9:35 AM
To: Colin.Haddow at esa.int
Cc: CCSDS Service Mgmt WG
Subject: Re: [Smwg] Planning Data Formats Book - Need for a "Simple Service Request"
Colin,
The comment from ESOC is a very good one that we need to keep in mind as it is applicable to other networks as well (such as NEN and NOAA).
We've yet to discuss the action from London regarding the "synergies"
between the planning data request and the service package request. We can address this topic along with that at the next telecon.
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:29 PM, "Colin.Haddow at esa.int" <Colin.Haddow at esa.int> wrote:
>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.
>
_______________________________________________
Smwg mailing list
Smwg at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/smwg
_______________________________________________
Smwg mailing list
Smwg at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/smwg
More information about the SMWG
mailing list