CSSM Meeting Summary

Spring 2013 Meetings15 – 18 April

E. Barkley Chair (NASA/JPL)C. Haddow Co-Chair (ESA/ESOC)

Bordeaux, France

eb- 2

Contents

1. Action Items Review2. Concept Revision Summary3. Concept Book Review4. Functional Resources (Joint CSA, CSTS,

CSSM)5. CSSM Information Entities 6. Schedule of Services Review7. Schedule of Services Prototype/Test Plan8. Roadmap9. Extensibility Model for Configuration Profile10.Representational State Transfer (REST)11.Situational Awareness12.Planning

Action Items Review

• (See Spreadsheet on CWE)• General action to remind WG about is to review

event compendium created by C. Haddow

Concept Revision Summary: Pre-Bordeaux

Concept (GB)

Schedule Content/Format

(BB)

Planning Information

Content/Format (BB)

Framework (BB)

Lifecycle

Functional Resources

Mgmt Information Entities

Extensibility Model

Management Service Recommendations (BBs)

FWD RTN TRK

Concept Revision Summary: Post-Bordeaux

Concept Book (GB)

Data Format BBs

Schedule Format Planning Data

Service Request, Service Package

Service Catalog, Service

Agreement, Service

Configuration Profile

Event Sequence

Trajectory Prediction

Framework(Internal to WG)

Lifecycle

Functional Resources

Mgmt Information Entities

Extensibility Model

eb- 6

Concept Book Review

• Updates• Figure 3-1: (1st) to be revised to show only functions at

an abstract high level• Figure 3-2: Terrestrial WAN Node moves to be inside the

Provider Domain• Figure 3-2: Add a connection between Control Node +

ESLT• Figure 3-3: All block definitions should be stereotyped• SSI Diagrams – Need same treatment as Fig 3-1, 3-2 (ie

abstract functions vs node definitions)• Open question: Does enterprise model need to show 3-

way configurations (e.g, NASA/DSN uplink, ESA/ESTRACK downlink)?

Functional Resources Review(Joint Mtg w/CSA, CSTS WGs)

• Agreed that FRs are on the right track• Mapping from CSA (Cross Support Architecture) to

FR seems quite feasible• An annex and/or reference to the FR techincal note is to

be added to the CSA• Question of granularity still to be sorted out (functional

resources vs. functional group defintions – later more useful for the CSA)

• Question of reference model refresh• (Subsequent discussion is that this is on hold as

resources are not available to do examine the existing SLE Reference Model)

• ESLT is where DDOR correlator “lives”

CSSM Information Entities (1/3) • Extensibility considerations now more focused on per information

entity basis• Extensibility concerns discussed noted on following slides

CSSM Information Entities (2/3)

• Extensibility Considerations for Service Catalog• New Services Definitions• Additional service capabilities• Agency Specific Offerings

• Extensibility Consideration for Service Agreement• New Service Definitions, e.g. ranging• Additional service capabilities• Agency Specific Offering• Separation of (existing) operational (management service)

constraints from functional resource constraints• Lifecycle phase refinement, e.g., compatibility testing/validation • Financial Information/Data• Functional Resources

- Examples- RF/Modulation Schemes- Terrestrial Data Transfer protocol configuration

CSSM Information Entities (3/3)

• Extensibility Considerations for Configuration Profile• New Services Definitions• Additional service capabilities• Agency Specific Offerings• Functional Resources• Examples• RF/Modulation Schemes• Terrestrial Data Transfer protocol configuration

• Extensibility Considerations for Service Package• Temporal constraints, e.g. Rules for scheduling a series of service packages

Schedule of Services WB Review

• Use Case definitions Generally Okay

• Activity Type This becomes service(s), and become part of schedule item

• Antenna ID becomes AntennaRef

• Frequency Band Added to the Service Type data class- Action to M. Gnat; C. Circolan: provide some frequency band parameter

definitions (apparently there are not standard frequency band definitions)

Schedule of Service Prototyping/Test Plan

• Prototyping Activity So Far:• NASA Rep (C. Audain) has produced examples schedules for SN

and one NOAA• DLR Rep (M. Gnat) has received schedules

- Examined via XML SPY- Conclusion: Makes sense, okay so far

• Some Findings:• Set up time: NASA NEN appears to selectively include set-up/tear-

down times; ie not used routinely• Agreed to make optional as it appear that some networks do not use

this/need it.• Agreed to allow additional parameters for Service Type class (bi-

lateral) (in addition to those for Scheduled Activity class)• Agreed to add Orbit number to Scheduled Activity class

• Test Plan Review:• Agreed to remove test case 3• Agreed to add round-trip test case• Agreed that Test case 4 can be done a rather lightly -- no need to set

up the implied infrastructure

Road Map

A preliminary road map for revised concept was produced; subject tofurther revision, refinement, updates based on project definitions, subsequent extensibility analysis, etc.

Extensibility Model, Configuration Profile

Ext. Model, Configuration Profile -- Notes

• Framework meta data• Common across all information entity definitions • Allows for referential framework much like current Blue-1

• Functional resources • Forms the (abstract) basis for identifying the functions that are

being managed

• Functional group• Collection of functional resources with well defined affinities

sufficient that the grouped functional resources can be treated as unit

• Services • Identifies the cross support services in terms of functional groups

• “Wiring”• Composition of the configuration profile information entity with

respect to the above

REST

• May potentially replace or allow for a “slim”/”lightweight” service definition if and when agencies are ready for management services

• See A. Crowson’s presentation darft analysis -- RESTful CSSM

Situational Awareness

Inputs, comments were solicited from WG members in attendance re agency development related to service management…

• ESA• Desire to have something fairly quickly• Recognize that BLUE-1 is not really it

• DLR• Similar concerns to ESA

• UKSA• No plans to implement SM currently• May be some private tracking operations that could consider using

• JAXA• Looking at Blue-1 implementation

• NASA• SN ground sustainment task is taking a conceptually similar approach to

Blue-1 but is not really Blue-1• TTC networks integration project has been initiated is looking to adopt

post-BLUE-1 SM standards

CSSM Planning for Next 6 months

8 Telecons and associated milestones planned – see below

Longer Term Planning

• Planning information project drafted and in the CCSDS CWE Framework -- please do not edit, for reference only

(http://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=359&Source=http%3A%2F%2Fcwe.ccsds.org%2Fcss%2FLists%2FFramework%2FAllItems.aspx)

• Resource estimates for blue books identified in the roadmap were developed

L1 -- Deliverable L2 Work Items L3 Work ItemsEstimated Effort (Work Months)

Subtotal per

deliverable

Schedule of ServicesBook Updates 0.25XML Schema 0.25

Test Plan 0.5Prototype 1 0.5Prototype 2 2Test Report 0.25

3.75Concept Book

Book UpdatesEnterprise Model 0.25

Implication Assessment 0.25Updates Based on

Concept Adjustment3

Roadmap Section 0.25Emergency Section 0.25

4Service Request,

Service Package BBDraft 1 3Draft 2 2

XML Schema 0.5Prototype 3

8.5Planning Information

BB (Request and Plan)

Draft 1 6Draft 2 3

Prototype 6XML Schema 1

16

Sevice Catalog, Service Agreement,

Configuration Profile

Draft 1 3Draft 2 2

XML Schema 1Prototype 3

9

Trajectory Prediction

Draft 1 0.5Draft 2 0.25

Prototype 0.25XML Schema 0.25

1.25Event Sequence

Draft 1 1.5Draft 2 1

Prototype 2XML Schema 0.5

5

Management Svcs (Blue Book)

Draft 1 6Draft 2 3

Prototype 1221

Miscellaneous Notes

• MagicDraw• Agreed to use MD V 17.0.2 as for modeling

Thank You

Thank you to all attendees for a very successful CSSM WG meeting.