1. SLE-SM Refactoring Proposal Scope –Allow inclusion of services or modifications to existing ones without having to reedit the entire SLE-SM book. Proposal –Try to keep the information model as close as possible to the existing one and just add some “plugin-points” –Split the book in three parts : SLE-SM Core SLE-SM AddOn : CSSDS 401 Spacelink Services SLE-SM AddOn: CCSDS SLE Transfer Services –Addon books can reference one another This is just an example of what could be done, a real analysis needs to be done before stating that this is even feasible.

2. Dataflow Service Package DataSources DataSinks DataSources DataSinks Transport configuration items 1..* 401-Return&Forward-Transport ADD-ON CORE BOOK Configuration Profiles Transport Config Profile Package Level Config Item Configuration profile Specific operations Specific events Trajectory Reference First Scenario Reference Antenna Reference

3. Currently it deals with: –Either a Space Link Session –Or a RetrievalTsInstanceRequest Replace this with an abstract DataFlow that provides : –Service start time –Service preferred duration –Service minimum duration –DataSink(s) –DataSource(s) –A reference to a Transport Transport is referenced in add-on books : –RetrievalTsInstanceRequest is the SLE Transfer Services Add-on –Space Link Session in the 401 SpaceLink Add-on XML files refactoring using substitution groups (John’s accepted proposal) deals with the mechanics Service Package Services

4. > StartTime, duration, etc. DataSource(s) DataSink(s) SpaceLinkSessionRetrievalTransferServicesWhatever CORE BOOK ADD-ON 1ADD-ON 2ADD-ON x DataFlow

5. A generic (TBD) connector system at the Dataflow’s level –A connector is DataSource/DataSink with a reference to a configuration profile and parameters’ respecification –Dependencies between Space link Sessions and Retrieval Sessions are removed (so that you can put them in different books) –What is possible in terms of DataSource and DataSinks is restricted at transport level (E.g. SLE RAF only accepts R401 Space Link Session - or any compatible DataStore - as a DataSource) Space Link Session : –spaceLinkSession StartTime, PreferredDuration and MinimumDuration replaced by the Dataflow’s equivalents. –SlsTsProfileRespecification is replaced by a generic connector RetrievalTsInstanceRequest : –accessStartTime and accessStopTime replaced by the dataflow’s serviceStartTime and servicePreferredDuration. –RetrievalTsProfileRespecification is replaced by a generic connector Impacts on the CSP info model

6. Is an empty placeholder for generic service configuration or generic datastore configuration defined in add-on books. E.g. Everything that relates to 401 return and forward are moved to the 401 Add-on Book. Dependencies between configuration profiles (e.g. between spacelinkcarriers’s RAFprod and RafTsM or Datasink) shall be reengineered to match the Dataflow/Connectors system used for the Service Package Service. Some of the building blocks (basic services with their configuration stuff) like carrier profiles and such, can be kept in core. Configuration Service

8. DataSink : DataFlow reference

9. Even better, separate “Core” from the rest Other config Items reference what is in the core (or other add-ons)

10. Create Service Package : –Every operations that relate to package management (CSP, RSP, DSP, SPC, SPM, QSP, PSP) are unchanged. –Add a placeholder for Transport specific operations. Theses operations enable the UM to change the value of a transport specific configuration item in the service package e.g. UpdateConfigItem(ItemId, newValue). Use XML substitution groups here –Those operations (and associated XML messages) are documented in the proper add-on book (Eg. Apply New Trajectory and Select Alternate Scenario are moved to the 401 Add-on) Services’ Operations (1)

11. Trajectory Predication Service KEPT AS IS –This is somewhat transport specific since it only impacts the spacelink (retrieval session don’t care about trajectories) –BUT it’s a key element of ground station so I would keep it in the Core, unchanged. –Transports are free to reference trajectories or not. Services’ Operations (2)

12. Configuration Service : –[add|delete]_space_link_session_profile and query_carrier_profile operations are replaced by more generic [add|delete|query]_transport_profile operations that reference a generic transport configuration profile defined in an addon book. –Event related operations are removed from the Configuration Service to a new dedicated Event Service Services’ Operations (3)

13. Event Service –[add|delete|query]_event_profile are moved here. –Event are a generic mechanism to update transport config item’s at a specific time (relative to serviceStartTime) –Event are in the form : date, transport_specific_operation, transport_specific_arguments Services’ Operations (4)

14. Services’ Operations (5) Service Agreement Service : –Split into parts to reflect the changes in the configuration profile service

15. Core Book Overview 1INTRODUCTION 2OVERVIEW OF SLE SERVICE MANAGEMENT 3SLE SERVICE MANAGEMENT DOCUMENT EXCHANGE 4SERVICE PACKAGE OPERATIONS –GENERAL –CREATE_SERVICE_PACKAGE (CSP) OPERATION –REPLACE_SERVICE_PACKAGE (RSP) OPERATION –DELETE_SERVICE_PACKAGE (DSP) OPERATION –UPDATE_SERVICE_PACKAGE_ITEM (USPI) OPERATION –SERVICE_PACKAGE_CANCELLED (SPC) OPERATION –SERVICE_PACKAGE_MODIFIED (SPM) OPERATION –QUERY_SERVICE_PACKAGE (QSP) OPERATION –PROPOSE_SERVICE_PACKAGE (PSP) OPERATION 5CONFIGURATION PROFILE OPERATIONS –GENERAL –ADD_TRANSPORT_PROFILE (ATP) OPERATION –DELETE_TRANSPORT_PROFILE (DSLSP) OPERATION –QUERY_TRANSPORT_PROFILE OPERATION 6EVENT PROFILE OPERATIONS –GENERAL –ADD_EVENT_PROFILE (AEP) OPERATION –DELETE_EVENT_PROFILE (DEP) OPERATION –QUERY_EVENT_PROFILE (QEP) OPERATION 7TRAJECTORY PREDICTION OPERATIONS –GENERAL –ADD_TRAJECTORY_PREDICTION (ATP) OPERATION –DELETE_TRAJECTORY_PREDICTION (DTP) OPERATION –QUERY_TRAJECTORY_PREDICTION (QTP) OPERATION 8SERVICE AGREEMENT OPERATIONS –GENERAL –QUERY_SERVICE_AGREEMENT (QSA) OPERATION Most of the stuff is moved to Add-On books with a reasonable amount of modifications Most of the stuff is moved to Add-On books with limited modifications Most of the stuff is moved to Add-On books. Core Services must be separated from optional services

16. 1INTRODUCTION 2TRANSPORT PRESENTATION 3CONFIGURATION PROFILE –F401 SpaceLink Carrier –R4O1 SpaceLink Carrier 4SERVICE PACKAGE PROFILE –SpaceLinkSession ServiceScenario ServiceScenarioReference –Acceptable DataSources and DataSinks 5SERVICE PACKAGE OPERATIONS –SELECT_ALTERNATE_SCENARIO –APPLY_NEW_TRAJECTORY 6SPECIFIC EVENTS –RSpaceLinkEvents RSpaceLinkAvailableState RSpaceLinkChangeEvent –FSpaceLinkEvents FSpaceLinkAvailableState FSpaceLinkChangeEvent 7SERVICE AGREEMENT PROFILE –R401 SpaceLink Carrier boundaries –F401 SpaceLink Carrier boundaries ANNEX A Specific acronyms and abbreviations (Informative) ANNEX B Transport Specific Xml Schemas (Informative) Add-On Book Overview 401 Return and Forward Example