60 likes | 183 Vues
This document outlines the CSA's effort to develop a recommended standard for service agreements. It aims to define templates, including a formal schema, and provide examples based on current inter-agency agreements. It identifies necessary mechanisms for maintaining these agreements and highlights issues like terminology and existing agency practices that need alignment. Current status and next steps are outlined, with a deadline for receiving comments and drafting revisions to ensure comprehensive agreement across involved organizations.
E N D
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 a 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.
Overall Approach This addresses Item 1 This will address Item 3 Item 2 is being addressed initially by comparison with an existing JPL ‘Draft Service Agreement’
Current Status • Section 3 contains a summary of the Service Agreement process • Section 4 contains all the parameters needed to execute an SLE service (RAF, RCF, CLTU) See Service Catalog
Some Issues • Terminology needs to be agreed • Service Agreement process needs to be agreed • Existing agency practices need to be incorporated • Further services need to be added e.g. tracking • Additional services will need to be identified as bilaterally-agreed until the services are defined by the CSTS and SM Working Groups • Examples of instantiated service agreements will be based on existing ESA, NASA documents
Next Steps • Receive comments from CSA 31 May 2009 • Draft sections 2 and 5 31 May 2009 • Revise entire document 30 June 2009 • Next draft should include parameters extracted from NASA, ESA and other agency documents • Further iterations should lead to Red 1 this fall