CSA WG Service Agreement Status Prepared by Hugh Kelliher Space ConneXions Limited hugh.kelliher@spaceconnexions.com

CSA Charter Requirement Development of a recommended standard for service agreements that: defines template(s) of service agreement contents, including formal schema, offers two or more examples of an instantiated service agreement based on the template and two or more current inter-agency service agreements, identifies mechanism(s) for service agreement maintenance.

This addresses Item 1. Schema will be stored on CCSDS web site Overall Approach This addresses Item 1. Schema will be stored on CCSDS web site The concept is derived from IOAG/SISG and SCCS Service Management documents Item 2 is addressed in completed templates corresponding to existing missions This addresses Item 3 The parameters are derived from existing agreements and SCCS Service Management

Current Status Since the Colorado Springs workshop … Section 1 (Introduction) has been drafted Section 2 (Concept) has been drafted Section 3 (Process) has been revised Section 4 (Parameters) has been revised Section 5 (Templates) has been started ‘Mission Registration’ template available as a pdf form MMO mission used as example of instantiated agreement Corresponding schema available XML code for MMO example is included in document

Mission Registration Template ‘Supporting Agency Contacts’ ‘Wolfgang Hell’

Mission Registration XML File   <?xml version="1.0" encoding="UTF-8" ?> - <xfdf xmlns="http://ns.adobe.com/xfdf/" xml:space="preserve"> - <fields> - <field name="allowedCmSmEntityNames">   <value>Wolfgang Hell</value>   </field> - <field name="allowedUmSmEntityNames">   <value>Takahiro Yamada</value> - <field name="complexName">   <value>ESTRACK DSN</value> - <field name="contractualReference">   <value>BepiColumbo Programme Plan (BC-EST-PL-02944)</value> - <field name="contractualReference2">   <value>Spacecraft Contact Plan (preliminary)</value> ‘Supporting Agency Contacts’ becomes ‘allowedCmSmEntityNames’ with value ‘Wolfgang Hell’ etc.

Mission Registration XML Schema Element names are identical to those defined in the SM Schema e.g. allowedCmSmEntityNames These Types are copied from the SM Schema: String256Type UTCTimeType SmEntityNameType Additional elements need to be added to the SM Schema e.g. testSupport1

Next Steps Redraft sections to align with IOAG terminology, where appropriate Complete remaining templates Complete remaining schema Add mandatory section on security Add mandatory conformance matrix Obtain namespace for XML schema and add section on SANA issues Add appendix for acronyms Obtain document reference from Secretariat Further iterations should lead to Red 1 in spring 2010