[Smwg] 902x2-w0.16 - Planning Information Formats - Updated draft

Thu Feb 1 19:13:32 UTC 2018

Hi Erik,
              with respect to your points;

I'm open to suggestion what we should call them. COMMS is the current 
working name but its easy enough to change.
If you look in the Service Management Common Data Entities book you'll see 
that the SrvMhtAbstractEvent class (from which all the planning events are 
derived) inherits the optional identifier from the Abstract Event Class.
Guilty as charged, for some reason I don't have anything about this in my 
notes, so completely forgot about it.

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:   "Barkley, Erik J (3970)" <erik.j.barkley at jpl.nasa.gov>
To:     "Colin.Haddow at esa.int" <Colin.Haddow at esa.int>
Cc:     "CCSDS SMWG ML(smwg at mailman.ccsds.org)" <smwg at mailman.ccsds.org>
Date:   01/02/2018 19:43
Subject:        RE: [Smwg] 902x2-w0.16 - Planning Information Formats - 
Updated draft

Colin,

I have managed to take a quick review of the updated recommendation in the 
schema and it looks like it is going the right direction. I do have some 
comments.

1)      Perhaps we could consider classifying these as "geometry" (short 
of communication geometry) events or something like that rather than 
?comms?.  The rationale is that eventually we do have a future issue or 
issues of the PIF planned with further planning types which include data 
rate and volume estimates.  I think something like this could perhaps be 
more directly considered as communication (presumably getting into things 
like link margin etc.) whereas the information we have currently in the 
PIF is really about the geometry surrounding the communication and not so 
much the communication per se
2)     I saw the identifier element optionally included in selected event 
definitions in the instance example but I don't see a corresponding 
parameter listed in the UML model? 
3)     I don't really see the planetary surface other than earth use case 
being accommodated yet in the PIF. I suspect that has to do with it being 
back in July that this was discussed and it isn't necessarily on the 
"front burner" so to speak. Attached is a PowerPoint presentation that has 
some suggestions for inclusion of this use case. My rationale for 
suggesting the inclusion of this use case is that there has been a fair 
amount of progress in the SIS area with regard to DTN and I think we will 
need to address this use case sooner or later and as I think that that it 
is not that much of a stretch sooner would be better.

Perhaps we can discuss these at the upcoming working group teleconference.

Best regards,
-Erik

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of 
Colin.Haddow at esa.int
Sent: Tuesday, January 30, 2018 5:30 AM
To: CCSDS SMWG ML(smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>
Subject: [Smwg] 902x2-w0.16 - Planning Information Formats - Updated draft

Dear all, 
                 I've just uploaded the latest draft of the Planning 
Information Formats Book to CWE, This contains the updates discussed at 
San Antonio and Den Haag. I've also uploaded the updated UML model and 
Schemas. Note that the UML model and the schemas also contain the updates 
required for the revised Service Management Common Data Entities Book. 

Also included in the Schemas are a couple of examples for the Planning 
Information, along with the extra schema required to get the extended 
Planning Information to work. 

The Planning Information Formats document, model and schemas can be found 
at the following URLs. 

Document:         
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats.doc

Model:                
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20UmlModel.zip

Schemas:         
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Planning%20Information%20Format/White%20Book/Drafts/902x2-w0.16%20-%20Planning%20Information%20Formats%20-%20Schema.zip

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
---------------------------------------------------------------------------------------------------------

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.
 [attachment "Response to AI 2017-0512-02 (Mars Relay) 01-Aug-2017.pptx" 
deleted by Colin Haddow/esoc/ESA] 

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/smwg/attachments/20180201/fbd689e1/attachment.html>