1 / 12

CSA WG Service Agreement Status

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:

cutter
Download Presentation

CSA WG Service Agreement Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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.

  3. 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 The parameters are derived from existing agreements and SCCS Service Management This addresses Item 3

  4. Current Status • The latest version is Draft 7 dated 15 December 2010: • Sections 2 and 3 have been completed • Section 4 incorporates feedback on real missions from: • Fred, based on the Juno mission • Takahiro, based on the MMO mission • Wolfgang, based on the Cluster mission • What has not (yet) been done … • Green Book material in Sections 2 and 3 needs to be extracted • Remaining XML Schema in Section 5 need to be produced • Wider discussion is needed relating to terminology, parameters and relationship to CCSDS Service Management

  5. Service Agreement Concept • Section 2 is based on material generated by the Service Management WG several years ago, as reviewed and modified by the CSA WG. Service Reporting Service Package Execution Service Monitoring Service Planning Mission Planning provides …. Configuration Profile Submissions/Updates Mission Registration Trajectory Prediction Submissions/Updates Service Packages Submissions/Updates T0 - years T0 - months T0 – weeks T0 - days T0 T1

  6. Service Agreement Process • Service Planning includes: • Querying Service Catalogs and short listing providers • Iterating high level: • mission schedules • spacecraft contact plans • Service Agreement includes: • Mission registration • Create Service Agreement • Modify Service Agreement • End Service Agreement

  7. Service Agreement Parameters (1 of 2) • Service Agreement parameters are grouped into several templates: • Part 1 - Mission Registration • Part 2 - Options and Constraints • Part 3a - Forward Space Link Parameters • Part 3b - Return Space Link Parameters • Part 4a - Configuration Control Parameters • Part 4b - Trajectory Prediction Parameters • Part 4c – Service Package Parameters e.g. agency contacts, agreement period, services requested e.g. SM timeouts, max number of service instances Mainly SM Mainly Generic

  8. Service Agreement Parameters (2 of 2) • The following templates are on hold, pending wider discussion: • Service Monitoring • Service Reporting • As an example, the Mission Registration parameter table looks like this:

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

  10. Mission Registration XML File • <?xml version="1.0" encoding="UTF-8" ?> • -<xfdfxmlns="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> • -<field name="complexName"> • <value>ESTRACK DSN</value> • </field> • -<field name="contractualReference"> • <value>BepiColumboProgramme Plan (BC-EST-PL-02944)</value> • </field> • -<field name="contractualReference2"> • <value>Spacecraft Contact Plan (preliminary)</value> • </field> ‘Supporting Agency Contacts’ becomes ‘allowedCmSmEntityNames’ with value ‘Wolfgang Hell’ etc.

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

  12. Next Steps • Split documents into “Service Planning” Green Book (Sections 2 and 3) and “Service Agreement” Red Book (Sections 4 and 5) • Align with latest SM and IOAG terminology, as appropriate • Add missing material: • Complete remaining templates • Add links to Service Catalog parameters (when available) • Add sections on security, patents, conformance matrix, SANA • Add appendix for acronyms • Obtain namespace for XML schema • Obtain document references from Secretariat!

More Related