AI 2016 0405 1 Concept Book vs Configuration

AI #2016 -0405 -1 Concept Book vs. Configuration Profiles CSS SM Spring Meetings 2017, San Antonio Marcin Gnat, DLR/GSOC

Action Item AI: Review the Concept Book for Service Agreement and Configuration Profile extensibility and check for consistency with the current concepts. Reviewed: Extensible Space Communication Cross Support – Service Management – Concept, CCSDS 902. 0 -G-1, September 2014

Concept Book vs. Config Profile Developments No. Location Text / Item Comment / Observation 1 Chapter 2. 3, Page 2 -6 Space Link Events Sequence, which specifies when and how a Space User Node is planned to change the configuration of a space link. In this version the Space Link Event Sequence is strictly „Space User Node“ IE. In terms of our new vision of using Event Sequence, it is rather the specification for both space and earth terminal when and how the changes to the Space Link are planned. Rather minor change, and not so high importance. 2 Chapter 2. 4. 2, Page 2 -8 Whole chapter of „EXTENSIBILITY OF SERVICE AGREEMENT AND CONFIGURATION PROFILE INFORMATION ENTITIES” The term „Service Components“ is being used in the chapter, whereas we (John) already decided to go away from that to rather Functional Resource Sets. We do not have also Abstract Service Components anymore, rather we use set of Configuration Profiles which are prebaked (cookie cutters). Now the extensibility is now more based on the principally behind-layered functional resource environment (which is by the way in „nirvana“ at the moment, Blue-Book-wise) than on any abstract classes of components or sets. Likewise general idea to have first a set of fixed (pre-baked) config profiles (simpler) being capable to be used by SMURF, and later fully supporting environment of extensible functional resource sets (with rules how to construct configuration profiles) shall be presented here as well (possibly, maybe, probably…). 3 Chapter 5. 6, Page 5 -4 Text says: „The information in the Configuration Profile is organized by Functional Resources within Service Components that correspond to the SLS services, retrieval services, and forward offline services (see 6. 2. 3). ” The sentence refers to Service Components -> at least one should exchange Service Components with Functional Resource Sets or rework the sentence completely. 4 Chapter 5. 12 Page 5 -9 Currently it describes Event Sequence as purely Space Link related and Space Segment oriented. Depending what are we going to do with Event Sequences, this chapter needs rework. At minimum we need to emphasize the importance of ES for being timing driver for Configuration Profiles.

Concept Book vs. Config Profile Developments No. Location Text / Item Comment / Observation 5 Chapter 5. 15 Page 5 -12 Service Package Request description. Accidentally (or not) the text nicely refers to Config Profiles so that it fits: “Service Package Request specifies the services to be provided (via references to Configuration Profiles) and parameters that control when and for how long the resulting Service Package is to be scheduled. ” What is maybe missing, is the reference to „when and for how long“ to be extended with „via references to Event Sequence“. But I‘m not sure. Btw. do we have the Forward Offline SP Request? 6 Chapter 5. 16 Page 5 -13 Service Package description. Similar as above. Should the Event Sequence shall be mentioned in terms of timing? 7 Chapter 5. 16 Page 5 -13 „One or more Service Packages may be grouped according to predefined selection criteria into a Service Package Set. ” Do we have Service Package Sets? 8 Chapter 5. 20 Page 5 -17 The figure 5 -1 Needs to be adopted wrt dependencies to Configuration Profile. The text around it fits pretty good without changes. 9 Chapter 6. 2. 1 Page 6 -2 „SCCS services are realized through different combinations of functions, each of which has service management aspects (e. g. , it has configuration parameters that need to be set at initial values for the execution of the Service Package). These functions are organized into Abstract Service Components (ASCs), which are the key extension points for the Service Agreement and Configuration Profile Information Entities. […]” This section needs rework wrt Abstract Service Components being now rather Functional Resource Sets or even Pre-Baked Configuration Profiles.

Concept Book vs. Config Profile Developments No. Location Text / Item Comment / Observation 10 Chapter 6. 2. 2 Whole chapter “SPACE COMMUNICATION CROSS SUPPORT ABSTRACT SERVICE COMPONENTS” The chapter needs complete rework or replacement. Good material for that would be parts from John‘s White Book or Requirements Technote. To some extent (soft version) one could start also with just replacing Service Component with Functional Resource Set. At the end it could be treated as an introduction to the Functional Resources which comes later on. This would be also essentialy a place where we define the difference between simpel pre-baked config profiles and the secret-yet-to-bedefined book with construction (and extension) rules for Configuration Profiles based on Fuctional Resources. 11 Chapte 6. 2. 3 Whole chapter „ABSTRACT SERVICE COMPONENT EXTENSION POINTS FOR SERVICE AGREEMENT AND CONFIGURATION PROFILE INFORMATION ENTITIES“ In terms of pre-baked configuration profiles and no Service Components as such at all, this chapter almost obsolete. The potential extensibility mechanisms needs to be annotated in chapter before. 12 Chapters 6. 2. 2 and 6. 2. 3 Whole chapters Ultimately we could argue, while we do not need the notion of Service Component anymore, we skip these chapters, and we rather have JUST Functional Resources (Chapter 6. 2. 4). (see point below) 13 Chapter 6. 2. 4 Functional Resources within Service Components Despite the simple naming corrections and getting rid of Service Component, the chapter is good. To get more in alignment with current concepts, we may think about: 1. reworking the subchapter with examples (like Telecommand Mission Example, Chapter 6. 2. 4. 2) into example of pre baked telecommand configuration profile (which would be effectively a copy of that would be anyhow in the Config Profile BB) or… 2. Describe the idea of „cookie cutters“ here… (probably better fitting for concept book).