[Sea-sa] Re: SAWG Reference Architecture planning session - minutes

Shames, Peter M (312B) peter.m.shames at jpl.nasa.gov
Thu Dec 10 19:35:06 UTC 2015


Hi Mario,

As much as you might wish it, it is way too soon to be able to define durations of phases.  We have had one working meeting and at this point have only fractional (small fractions) from a very limited set of participants.

Let us see what kind of progress we can make on this with the available resources and then I will better be able to provide some sort of answer as to timing.

Regards, Peter


From: Mario Merri <Mario.Merri at esa.int<mailto:Mario.Merri at esa.int>>
Date: Thursday, December 10, 2015 at 1:38 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Cc: Brigitte Behal <Brigitte.Behal at cnes.fr<mailto:Brigitte.Behal at cnes.fr>>, Dan Smith <danford.s.smith at nasa.gov<mailto:danford.s.smith at nasa.gov>>, Martin Suess <Martin.Suess at esa.int<mailto:Martin.Suess at esa.int>>, "Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>" <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>, Nestor Peccia <Nestor.Peccia at esa.int<mailto:Nestor.Peccia at esa.int>>, Richard Barton <richard.j.barton at nasa.gov<mailto:richard.j.barton at nasa.gov>>, Roger Thompson <Roger.Thompson at scisys.co.uk<mailto:Roger.Thompson at scisys.co.uk>>, Ramon Krosley <r.krosley at andropogon.org<mailto:r.krosley at andropogon.org>>, "sam at brightascension.com<mailto:sam at brightascension.com>" <sam at brightascension.com<mailto:sam at brightascension.com>>, SEA-SA <sea-sa at mailman.ccsds.org<mailto:sea-sa at mailman.ccsds.org>>, Wallace Tai <Wallace.S.Tai at jpl.nasa.gov<mailto:Wallace.S.Tai at jpl.nasa.gov>>, "yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>" <yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>>
Subject: Re: SAWG Reference Architecture planning session - minutes

Hi Peter,

I do not object with the proposed phasing of the work. I just want to make sure that the the end-to-end aspect of MO services, which is a key part of the concept, is factored in the discussion from the beginning and it is not forgotten as the work progresses. Therefore, as a minimum the 2 phases should be clearly described (as you have done below) in the outcome of the initial work. I was thinking to a top level cartoon presenting at high level the big picture, from which then you "zoom in"  in phase 1 and phase 2.

What is your expectations on the duration of phase 1 and the start/duration of phase 2?

Regards,

__Mario



From:        "Shames, Peter M (312B)" <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
To:        "Mario.Merri at esa.int<mailto:Mario.Merri at esa.int>" <Mario.Merri at esa.int<mailto:Mario.Merri at esa.int>>
Cc:        "Martin Suess" <Martin.Suess at esa.int<mailto:Martin.Suess at esa.int>>, "Richard Barton" <richard.j.barton at nasa.gov<mailto:richard.j.barton at nasa.gov>>, "Brigitte Behal" <Brigitte.Behal at cnes.fr<mailto:Brigitte.Behal at cnes.fr>>, "Nestor Peccia" <Nestor.Peccia at esa.int<mailto:Nestor.Peccia at esa.int>>, "Tai, Wallace S (9000)" <wallace.s.tai at jpl.nasa.gov<mailto:wallace.s.tai at jpl.nasa.gov>>, "danford.s.smith at nasa.gov<mailto:danford.s.smith at nasa.gov>" <danford.s.smith at nasa.gov<mailto:danford.s.smith at nasa.gov>>, "sam at brightascension.com<mailto:sam at brightascension.com>" <sam at brightascension.com<mailto:sam at brightascension.com>>, "Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>" <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>, "Roger Thompson" <Roger.Thompson at scisys.co.uk<mailto:Roger.Thompson at scisys.co.uk>>, "Ramon Krosley" <r.krosley at andropogon.org<mailto:r.krosley at andropogon.org>>, "yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>" <yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>>, "sea-sa at mailman.ccsds.org<mailto:sea-sa at mailman.ccsds.org>" <sea-sa at mailman.ccsds.org<mailto:sea-sa at mailman.ccsds.org>>
Date:        07/12/2015 17:44
Subject:        Re: SAWG Reference Architecture planning session - minutes
________________________________



Dear Mario,

As we agreed during the meeting in Darmstadt, we will do this work in two phases.  For the first we agreed to focus on SOIS in flight and MOIMS (MO Services, Nav, DAI, Robotics, mission planning) on the ground.  There is a lot of work to be done just to get all of these services, interfaces, terminology, and representative configurations sorted out.  And there is the work to specify clearly the relationships to the other four CCSDS areas of work.

I think we should call that Phase 1.

For the second, Phase 2, we will deal with what it means to then migrate elements of the MOIMS on-board.   The first will take a lot of specification work.  This second phase will take a lot of analysis and negotiation, which will be made easier (but not simple) if first have the phase 1 understanding completed.

I believe that this is what we all agreed to and it is what we intend to do.  What is described in these minutes is the plan only for Phase 1.  This will be reviewed and if there is agreement, and continued resources and support to get the job done, we will start Phase 2.  Nothing in Phase 1 precludes Phase 2, so there should be no conflict.

I hope you agree.

Regards, Peter


From: Mario Merri <Mario.Merri at esa.int<mailto:Mario.Merri at esa.int>>
Date: Monday, December 7, 2015 at 1:25 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Cc: Martin Suess <Martin.Suess at esa.int<mailto:Martin.Suess at esa.int>>, Richard Barton <richard.j.barton at nasa.gov<mailto:richard.j.barton at nasa.gov>>, Brigitte Behal <Brigitte.Behal at cnes.fr<mailto:Brigitte.Behal at cnes.fr>>, Nestor Peccia <Nestor.Peccia at esa.int<mailto:Nestor.Peccia at esa.int>>, Wallace Tai <Wallace.S.Tai at jpl.nasa.gov<mailto:Wallace.S.Tai at jpl.nasa.gov>>, Dan Smith <danford.s.smith at nasa.gov<mailto:danford.s.smith at nasa.gov>>, "sam at brightascension.com<mailto:sam at brightascension.com>" <sam at brightascension.com<mailto:sam at brightascension.com>>, "Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>" <Mehran.Sarkarati at esa.int<mailto:Mehran.Sarkarati at esa.int>>, Roger Thompson <Roger.Thompson at scisys.co.uk<mailto:Roger.Thompson at scisys.co.uk>>, Ramon Krosley <r.krosley at andropogon.org<mailto:r.krosley at andropogon.org>>, "yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>" <yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>>, SEA-SA <sea-sa at mailman.ccsds.org<mailto:sea-sa at mailman.ccsds.org>>
Subject: Re: FW: SAWG Reference Architecture planning session - minutes

Dear Peter,

As I mentioned already during the Reference Architecture meeting in Darmstadt, I would like that the WG considers from the very beginning that the "big picture" Reference Architecture includes MO Services on board. This is in fact where the relationship between MO Services and SOIS - that you would like to capture with this work - sits. It is agreeable that initially more detailed work should focus on MO Services on the ground, but I do not want that the MO Services end-to-end concept is lost.

Please confirm that this is your intentions.

Best regards,

__Mario



From:        "Shames, Peter M (312B)" <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
To:        "Martin Suess" <Martin.Suess at esa.int<mailto:Martin.Suess at esa.int>>, "Richard Barton" <richard.j.barton at nasa.gov<mailto:richard.j.barton at nasa.gov>>, "Mario Merri" <Mario.Merri at esa.int<mailto:Mario.Merri at esa.int>>, "Brigitte Behal" <Brigitte.Behal at cnes.fr<mailto:Brigitte.Behal at cnes.fr>>
Cc:        "Nestor Peccia" <Nestor.Peccia at esa.int<mailto:Nestor.Peccia at esa.int>>, "Tai, Wallace S (9000)" <wallace.s.tai at jpl.nasa.gov<mailto:wallace.s.tai at jpl.nasa.gov>>
Date:        02/12/2015 20:26
Subject:        FW: SAWG Reference Architecture planning session - minutes
________________________________



FYI -

Minutes from the CCSDS Ref Arch telecon.

Peter


From: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Date: Tuesday, December 1, 2015 at 4:50 PM
To: Roger Thompson <Roger.Thompson at scisys.co.uk<mailto:Roger.Thompson at scisys.co.uk>>, Ramon Krosley <r.krosley at andropogon.org<mailto:r.krosley at andropogon.org>>, "yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>" <yonghui at nssc.ac.cn<mailto:yonghui at nssc.ac.cn>>
Cc: SEA-SA <sea-sa at mailman.ccsds.org<mailto:sea-sa at mailman.ccsds.org>>
Subject: SAWG Reference Architecture planning session - minutes
================================================================

SAWG Reference Architecture planning session – Telecon, 1 Dec 15

Attendees: Roger Thompson, Ramon Krosley, Hwang Yonghui, Peter Shames

Agenda

  *   Discuss overall approach and forward plan
  *   Discuss MOIMS approach
  *   Discuss SOIS approach
  *   Forward work and next meeting

Minutes

Discuss overall approach and forward plan
1.        Reviewed the top level materials from the 10 Nov 2015 working session
1.        Scope of Work and Proposed Approach for WG efforts
2.        SCCS-ARD (CCSDS 901x1m1)  - Figure 7-4
3.        Cross Support / Mission Operations Interactions using Standard SLE / SM Services
2.        Discussed the possible adoption of UML/SysML, but decided to shelve it for now due to constrained time and resources
1.        Agree on value of developing SysML Profile for the future RASDS revision in Phase 2
3.        Discussed the general features of the Reference Architecture for Space Data Systems (RASDS) using some of the available diagrams
4.        Confirmed agreement to use existing RASDS PPT approach to align with SCCS-ADD/ARD
5.        Agree to align all new materials with current PPT “cartoon” template (SCCS-ARD materials including template, pg 2, provided here)
Discuss overall MOIMS approach
1.        Reviewed the MOIMS Mission Operations Services Overview (from MOSC 520x0g3)
2.        Discussed the relationships among the elements as depicted
3.        Discussed the fact that this is just an overview example and that many different mission configurations are possible
4.        Discussed the evolving nature of the MOIMS functional models and that some functional groups are more developed than others
5.        Discussed that Nav / OD is well understood, the mission planning is evolving, and that some functional groups could be further aggregated to reduce complexity of top level diagrams
6.        Confirmed agreement for Phase 1 of this effort to limit the MOIMS to the ground and SOIS to space
7.        Agreed to largely stick to what is already documented, but also to propose new [Future] funcitons / standards where their role appears to be clear
1.        Agree to review any such extensions with the SM&C WG
8.        Agreed to develop at least one MOIMS / SM&C top level diagram for the next meeting
9.        Reviewed the Nav / OD diagram from the Nav WG and agreed that the level of detail in this diagram is probably about correct for the lowest level of decomposition that we will develop
10.        Reviewed Nestor’s "MO Services” diagram and agreed to stick to the defined SM&C / MO service names and functions
11.        Discussed the need to cover all of MOIMS and not just SM&C and Nav, needs further thought & discussion
Discuss overall SOIS approach
1.        Reviewed the SOIS Service Architecture  (from 876x0r0)
2.        Discussed the relationships among the elements as depicted
3.        Discussed the fact that this is just an overview of the service layering and that many different mission configurations are possible
4.        Discussed the SOIS approach of defining abstract services and (largely) exchanges of abstract data type
5.        Reviewed the “Plug and Play” View of SOIS Architecture (from 850x0g1)
6.        Agreed that this is the right level of detail, but that we need to identify the types of the data exchanged among these functions
7.        Discussed, in general, the relationship between SOIS and MOIMS (defered until Phase 2)
8.        Agreed on an approach to include future work, where required, in the document and in the figures
1.        Use [Future] prefix marking in the document, as in SCCS-ARD, for document references
2.        Use [F] suffix in the figures to distinguish future functions, protocols, data structures
9.        Agreed to develop at least one SOIS top level diagram and one next level diagram for the next meeting
Forward work and next meeting
1.        Roger will develop a top level view of the MOIMS layered service architecture
2.        Ray will develop a similar top level view of the SOIS layered service architecture
3.        Yonghui will develop a view of the “Plug and Play” parts of the architecture
4.        Peter will distribute the RASDS template and SCCS-ARD materials
5.        Peter will setup a Doodle poll for the next meeting, either 12 or 19 Jan 2016
[attachment "Figures Used in SCCS-ARD-v0x9-29July14.pptx" deleted by Mario Merri/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.



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/sea-sa/attachments/20151210/8c4b54df/attachment.html>


More information about the SEA-SA mailing list