1. 1 Space Communications Cross Support Architecture WG: Charter and Work Plan April, 2009 Colorado Springs, CO, USA Takahiro Yamada, JAXA/ISAS

2. 2 Introduction  This presentation shows:  the charter of the Space Communications Cross Support Architecture WG,  the current status of each item defined in the charter, and  goals of this meeting.

3. 3 Goals Defined in the Charter (1/2)  Development of a Space Communications Cross Support Architecture recommended practice that:  Identifies the cross support forward and return services,  Identifies the management functions, and  Offers various views to fully describe the architecture.  Development of a recommended standard for service catalogs that:  Defines template(s) of catalog contents, including a formal schema,  Offers two or more examples of an instantiated service catalog, and  Identifies mechanism(s) for catalog maintenance.

4. 4 Goals Defined in the Charter (2/2)  Development of a recommended standard for service agreements that:  Defines template(s) of service agreement contents, including a formal schema,  Offers two or more examples of an instantiated service agreement, and  Identifies mechanism(s) for service agreement maintenance.

5. 5 Deliverables Defined in the Charter NameCategorySchedule Space Communication Cross Support Architecture Recommended Best Practice (Magenta Book) R1 - October 2009 B1 - May 2010 Cross Support Service Catalog Recommended Standard (Blue Book) R1 - October 2009 B1 - May 2010 Cross Support Service Agreement Recommended Standard (Blue Book) R1 - October 2009 B1 - May 2010 Technical note identifying modifications needed for the Cross Support Reference Model? InformalMay 2009 We will present the Red Books at IOAG-13 in the fall of 2009.

6. 6 Status of Each Item Defined in the Charter  Development of a Space Communication Cross Support Architecture recommended practice  The White Book on Cross Support Service Architecture (CSSA) provided by IOAG is being reviewed.  Development of a recommended standard for service catalogs  The tables of attributes to be used to characterize services provided by IOAG are being reviewed.  Development of a recommended standard for service agreements  The service agreement template provided by IOAG and some other sample service agreements are being reviewed.  A draft service agreement template is being generated.

7. 7 Resource Driven Approach for Developing Deliverables Cross Support Service Architecture (CSSA WB) It already covers in-space services and contains templates for service catalogs and service agreements. Available resources Space Communication Cross Support Architecture (MB) Cross Support Service Catalogs (BB) Cross Support Service Agreement (BB) We need to identify what to add to the IOAG WB

8. 8 How to Develop the Space Communications Cross Support Architecture  The IOAG CSSA WB should be used as the baseline.  We should identify descriptions missing from the WB and descriptions unnecessary in the WB.  Descriptions we can potentially borrow from NASA’s ADD: management functions, service discovery, etc.  We should determine the scope of this book (see another presentation).  Goals of this meeting:  Review the results of the action items assigned at the previous meeting.  Generate a list of things to be added to and deleted from the WB.  Identify a contributor to generate text to be added to the WB.

9. 9 A/Is related to the Architecture Book 1 No.ActionAssigned to Due dateStatus 1-2Analyze the relationship between the IOAG Cross Support Service Architecture White Book and the NASA architecture definition (ADD) book Brosi Shames 30 Apr 2009Open 1-3Create an Information View with a diagram showing relationship among data items referred to in the architecture book Yamada31 Jan 2009Open 1-4Generate a template for drawing space communications scenarios Yamada31 Jan 2009Open 1-5Develop typical space communications scenarios using inputs from IOAG Space Internetworking Strategy Group (SISG) Yamada30 Apr 2009Open 1-11Define a set of physical and logical terms (including uni/bidirectional) Shames31 Jan 2009Open T1-5Determine what to add to CSSA if CSRM is to be replaced with CSSA as the reference in the SLE transfer service books Brosi15 Apr 2009Open

10. 10 A/Is related to the Architecture Book 2 No.ActionAssigned to Due dateStatus 1-6Identify services (including operations/applications services) to support in-space (DTN, etc.) services, which should be derived from operations concept Barkley Yamada 30 Apr 2009Open 1-7Circulate Barkley’s chart shown at the joint meeting on 15 October Yamada17 Oct 2008Closed 1-8Submit comments on Barkley’s chartAll31 Jan 2009Open 1-10Update the list of services based on Hell’s presentation Yamada31 Jan 2009Open T1-1Distribute the latest version of the IOAG cross support service catalogue Hell17 Mar 2009Open T1-2Review the IOAG cross support service catalogue All15 Apr 2009Open

11. Discussion Items on the Architecture Book  Scope of the book. Should we recommend or refer to particular services?  Can we replace CSRM with this book?  How to incorporate materials from NASA’s ADD.  Do we need an Information View?  Space Communications Scenario  Terms (Forward, Return, etc.) 11

12. 12 How to Develop the Service Catalogs  The tables of attributes contained in Annexes A-E of the CSSA WB should be used as the baseline.  We should identify the following: 1. attributes missing from the tables for characterizing services 2. attributes unnecessary in the tables for characterizing services  Then, we should develop a few sample catalogs using the agreed-to attributes.  Goals of this meeting:  Agree on a set of attributes for some typical cross support services.

13. 13 A/Is related to the the Service Catalogs No.ActionAssigned to Due dateStatus 1-12Review the attribute tables contained in the IOAG Cross Support Service Architecture White Book Brosi Kelliher Hell 31 Jan 2009Open 1-13Talk with IPR people about how to register service catalogs in their system Shames31 Jan 2009Closed

14. 14 How to Develop the Service Agreements  The template for service agreements should be generated based on Annex F of the CSSA WB, some existing service agreements, SLE SM RB.  We should agree on a set of attributes that should be contained in every service agreement.  Then we should develop a few sample service agreements using the agreed-to template.  Goals of this meeting:  Agree on a core set of attributes.  Generate a few sample service agreements.

15. 15 A/Is related to the the Service Agreements No.ActionAssigned to Due dateStatus 1-14Generate a draft template for service agreements based on CCSDS Service Management Red Book and JPL DSN Service Agreement (DSA) Kelliher31 Jan 2009Open T1-3Generate examples of service agreements All15 Apr 2009Open T1-4Review the Service Agreement document generated by Kelliher All15 Apr 2009Open

16. Schedule for This Week  Tuesday morning (0800-1000)  Work Plan  Service Architecture – General  Tuesday morning (1000-1200)  Joint session with MOIMS  Wednesday afternoon (1300-1700)  Service Architecture – Specific topics  Thursday morning (0800-1200)  Service catalog  Friday morning (0800-1200)  Service agreement  Wrap-up 16