1. 1 Y.Doat (ESA) March 2015 Guidelines Status Guidelines Status CSTS Framework March 2015

2. 2 Y.Doat (ESA) March 2015 3.13 Deriving a New Service From an Existing CSTS Shall contain at least all procedure types from the parent Same prime procedure as parent To be added/clarified Add an existing FW procedure to the CSTS Create a new procedure making use of FW operations

3. 3 Y.Doat (ESA) March 2015 3.12 Derivation of Operation Parameters An operation can be extended from: Unconfirmed to Confirmed Confirmed to Acknowledge Impact: 3.12 Derivation of Operation Parameters -> : Derivation of Operation 3.12.1 - Review the Overview subsection ensuring all subsections are properly introduced Refinement of Parameter Values Extending operation parameters Abstract Parameters Parameter Extension for an Abstract CSTS Operation Extension Subsections 3.12.2 to 3.12.5 do not need update Add a subsection 3.12.x defining the operation extension

4. 4 Y.Doat (ESA) March 2015 3.14 Configuration of CSTS No change

5. 5 Y.Doat (ESA) March 2015 4 Structure & Content of CSTS Specifications Guidelines ChapterMD Service Front Cover & Front Matter ✓ Introduction ✓ 2. Overview ✓ 2.1Service Summary ✓ 2.2Functional Description ✓ 2.2.1Service Provision ✓ 2.2.2Service Production ✓ 2.3Service Management ✓ 2.4Cross Support View ✓ 2.5Operational Scenario ✓

6. 6 Y.Doat (ESA) March 2015 4 Structure & Content of CSTS Specifications Guidelines ChapterMD Service 3. Composition ✓ 3.1 General ✓ 3.2 Component Procedure ✓ 3.3 State Machine ✓ 4. Refined, Extended, & Service-Original Procedures ✓ Procedure ✓ 4.1 Discussion ✓ 4.2 Procedure Type Identifier ✓ 4.3 Refinement or Derivation –One or the other depends on case ✓ 4.4 Behavior ✓ 4.5 Required Operations ✓ 4.6 Configuration Parameters (Re-arranged in latest version) ✓ 4.7 Procedure State Tables ✓

7. 7 Y.Doat (ESA) March 2015 4 Structure & Content of CSTS Specifications Guidelines ChapterMD Service 4.7 Setting of Configuration Parameters Inherited from Framework Procedures - New text from John Section 7 4.8 Refinement of definitions of Framework Parameters, events, directives, AND Diagnostic Values Used by the Service New text from John Section 8 4.9 Monitored Information Section – merge with configuration 4.10 Service Production Annex Not required 4.11 Service Object Identifiers Module Annex Annex B 4.12 Procedure PDU Specification annexes Annex C 4.13 Implementation Conformance Statement Proforma annex – New text Annex A 4.14 Add section explaining how to cross reference the FW in an annex of the new CSTS

8. 8 Y.Doat (ESA) March 2015 FW RID – Notifiable Event (‘Internal’ R-2 RIDs) FW 3.11.2.2.3 has been modified such that FR related events and procedure related events are discussed separately. It should be noted that for a notification defined as part of a procedure specification it must be specified for each notifiable event if the given event is to be transferred with the FR name or the procedure name (Does this need to be added to the Guidelines?) Impact on section "4.6.8.3.9 notification-type extension” subsection

9. 9 Y.Doat (ESA) March 2015 FW RID – Notifiable Event ‘Internal’ R-2 RIDs Parent procedures define procedure-type specific events (except for the generic svc events) also in case the semantic of the event is the same for several (parent) procedures (e.g. ‘xyz configuration change’). However, derived procedures inherit events from the parent procedure, but have to specify a procedure-type specific event-value. This will have to be added to the Guidelines 2 cases to be added in the Guidelines: Event Name inherited: re-specify event values (See BDP example) New event type: specify the associated event values

10. 10 Y.Doat (ESA) March 2015 ‘Internal’ R-2 RIDs Although the way the SFW deals with the two flavors of the PROCESS-DATA operation (unconfirmed or confirmed) appears to be good enough for what is needed in the SFW proper, it may be difficult to document in the Guidelines how to deal with this when for a derived procedure this operation shall be used. Shall the Guidelines permit that new operations are composed of SFW PDUs? Point addressed in previous slide number 3.

11. 11 Y.Doat (ESA) March 2015 Additional Changes Annex A: ASN.1 to be aligned with FW Annex B.1: WH to clarify comment Annex B – 4.7 XML to be provided Annex E: Review cross reference to FW to use the MD format