1. Cross Support Architecture WG: Charter and Work Plan
October, 2008
Berlin, Germany
Takahiro Yamada, JAXA/ISAS

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

3. Goals Defined in the Charter (1/2)
Development of a Space Communication 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. 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. Deliverables Defined in the Charter
Name
Category
Schedule
Space Communication Cross Support Architecture
Recommended Best Practice (Magenta Book)
R1 - October 2009
B1 - May 2010
Cross Support Service Catalog
Recommended Standard (Blue Book)
Cross Support Service Agreement
Technical note identifying modifications needed for the Cross Support Reference Model
Informal
May 2009
We will present the Red Books at IOAG-13 in the fall of 2009.

6. Status of Each Item Defined in the Charter
Development of a Space Communication Cross Support Architecture recommended practice
IOAG provided a White Book called the Cross Support Service Architecture (CSSA).
Development of a recommended standard for service catalogs
IOAG provided preliminary tables of attributes to be used to characterize services in the service catalogs in Annexes A-E of the CSSA WB.
Development of a recommended standard for service agreements
IOAG provided a preliminary template for service agreements in Annex F of the CSSA WB.

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

8. How to Develop the Space Communication Cross Support Architecture
We should review the White Book that IOAG generated last year. It was distributed to the WG members in September.
We should identify the following:
Information or description missing from the WB
Information or description unnecessary in the WB
For the first part, we need to agree on the contents to be added and a contributing author.
Goals of this meeting:
Generate a list of things to be added to and deleted from the WB
Identify a contributor to work on details and/or generate text to be added to the WB.

9. Things to Do about the Architecture Book 1/3
Relationship with the CCSDS Cross Support Reference Model
When By End of Jan 2009
Who FB
Relationship with the NASA book (ADD)
When Jan-Apr 2009
Who FB and PS
Information View (A diagram showing relationship among data items referred to in the architecture book)
When Jan 2009
Who TY
Management functions <-NASA book
Scenario template

10. Things to Do about the Architecture Book 2/3
Scenarios
When By end of Apr 2009
Who SIAG and TY
Service discovery etc. <- NASA book
Identify services (including operations/applications services) to support in-space(DTN, etc.) services (derived from ops. concept)
Who EB and TY
Circulate EB’s chart shown at the joint meeting on 15 October
When 17 Oct 2009
Who TY
Submit comments on EB’s chart
When By end of Jan 2009
Who All

11. Things to Do about the Architecture Book 3/3
Draft a liaison statement to IOAG to allocate resources to develop and maintain service catalogs
When 17 October 2008
Who TY
Update the list of services based on WH’s presentation
When By end of Jan 2009
Define a set of physical and logical terms (including uni/bidirectional)
Who PS

12. How to Develop the Service Catalogs
We should review the tables of attributes contained in Annexes A-E of the WB.
We should identify the following:
attributes missing from the tables for characterizing services
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 core set of attributes
Identify (a) contributor(s) to finalize the tables
Identify (a) contributor(s) to develop sample service catalogs

13. Things to Do about the Service Catalogs
Review the attribute tables in the CSSA WB
When By end of Jan 2009
Who FB, HK, WH
Talk with IPR people about how to register service catalogs in their system
Who PS

14. How to Develop the Service Agreements
We should review the template for service agreements in Annex F of the WB.
We should identify the following:
items missing from the template for service agreements
items unnecessary in the template for service agreements
Then we should develop a few sample service agreements using the agreed-to template.
Goals of this meeting:
Agree on a core set of items
Identify a contributor to finalize the template
Identify (a) contributor(s) to develop sample service agreements

15. Things to Do about the Service Agreements
Generate a draft template for service agreements based on Service Management and JPL DSA
When By end of Jan 2009
Who HK
Provide a sample of DSA and PLAS
When By end of Oct 2009
Who EL