1. 1 Space Communications Cross Support Architecture WG: Charter and Work Plan May 2010 Portsmouth, Virginia, 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 M1 - May 2010 Cross Support Service Catalog Recommended Standard (Blue Book) R1 - May 2010 B1 - October 2010 Cross Support Service Agreement Recommended Standard (Blue Book) R1 - May 2010 B1 - October 2010 Technical note identifying modifications needed for the Cross Support Reference Model? InformalOctober 2009

6. 6 Status of Each Item Defined in the Charter  Development of a Space Communication Cross Support Architecture recommended practice  The second issue of White Book (issue 1.1) was distributed by Yamada in September 2009.  Development of a recommended standard for service catalogs  Not much progress since the last meeting.  Development of a recommended standard for service agreements  The second draft of the document and templates were distributed by Kelliher in August and November 2009, respectively.

7. 7 How to Develop the Space Communications Cross Support Architecture  The IOAG CSSA WB should be used as the baseline.  The IOAG SISG ADD was handed over to CCSDS and we should consider how to consolidate the CCSDS and SISG documents (see another presentation).  We should also consider how to harmonize this book with the to-be-developed CCSDS Reference Architecture.

8. 8 How to Develop the Service Catalogs  The attributes defined in Space Communication Cross Support Service Management BB and Space Communication Cross Support Service Agreement (to-be-) BB should be used as the baseline for the template of Service Catalogs.  We should develop a few sample catalogs using the agreed-to attributes.  Goals of this meeting:  Review any available inputs.

9. 9 How to Develop the Service Agreements  The document and the templates should be compared with existing service agreement documents such as NASA’s DSN Service Agreement document, for example.  We should also develop a few sample service agreements using the draft template.  Goals of this meeting:  Review the second draft and templates.  Identify missing items in the draft.

10. Schedule for This Week  Thursday morning (0900-1300)  Work Plan  Action Items  Service Architecture  Thursday afternoon (1400-1800)  Service catalog  Friday morning (0900-1300)  Service agreement  Wrap-up 10