[CMC] CCSDS Strategic Plan Draft 11

peter.allan at stfc.ac.uk peter.allan at stfc.ac.uk
Mon Dec 2 10:46:22 EST 2013


Nick,

Here are my comments on the updated CCSDS strategic plan. I have divided these into high level issues and "typos", the latter including points where I am suggesting rewording something to make it clearer.

Apologies for not getting them to you by last Friday, but my father-in-law died recently and dealing with this has slowed down work in some areas.

Peter Allan


High level issues
--------------------
Page 2 - second bullet, is

*             Developing new standards for critical and innovative space-related communication and information technologies where current standards are considered to be inadequate.

I suggest expanding this to

*             Developing new standards for critical and innovative space-related communication and information technologies where there are no current standards or they are considered to be inadequate.
Surely the largest part of our work is in developing new standards where none currently exist.


Page 4 - last goal is
*             By 2022: to progressively propagate the set of CCSDS standards (which currently, either in part or in whole, support the needs of approximately 40% of all spacecraft across the world community) so that they increasingly contribute towards the missions of a large majority of all civil, military and commercial spacecraft that are launched.

I agree with the sentiment of this goal and I am only querying the numbers. Specifically, will the expected large growth in the number of cubesats mean that the figure of 40% is unlikely to be achieved? If so, should we revise the number, reword the goal to exclude cubesats, or make a concerted effort to get cubesats to adopt CCSDS protocols?


General point about Area Objectives and Goals
Several of the goals have no standards in development and no future work identified. This looks like the goal has been achieved, so why are we mentioning it in a strategic plan? If we wish to retain these goals so that all of the active CCSDS recommended standards and practices are linked to a goal in this document, then we should explain that this is the case. (Was that actually the intention? I have not checked that all recommended standards and practices are actually listed.)
The relevant goals are:
MOIMS-Goal 1
MOIMS-Goal 5
SIS-Goal 1


Typos
-------
Page 1 - Last paragraph in the Introduction, is:

A Collaborative Work Environment (CWE) Workplan provides the current CCSDS program of work and organizational details and supplements this CCSDS Strategic Plan.  The CWE Workplan (i.e. description of the CCSDS Technical Organization, Operating Plan, Charters, Resource Matrix and Project definitions) is  maintained by the CCSDS Engineering Steering Group, and is now  updated in real time, accessible online as charters are approved.

The last sentence is a bit confusing to me. I suggest it should be changed to

The CWE Workplan (i.e. description of the CCSDS Technical Organization, Operating Plan, Charters, Resource Matrix and Project definitions) is  maintained by the CCSDS Engineering Steering Group. It is accessible online and is updated in real time as charters are approved.

(assuming I have interpreted it correctly).


Page 3 - Rationale
This contains the text
Standardization(through standardized products and COTS)

I suggest changing this to
Standardization (through standardized products and COTS products)
i.e. add the missing space after "Standardization" and say what Commercial Off The Shelf stuff we are referring to.



Page 5, at the end, we have
It is a CCSDS Level 1 requirement that recommended standards and practices must be developed to facilitate  interoperability and cross support across those six major interface planes.

This is the only place where we use the term Level 1 (or Level anything). It rather implies that we have other Level 1 requirements and probably that we have Level 2, 3, etc. requirements too, but we don't mention them in this document.

I suggest rewording this to say
It is a fundamental requirement of CCSDS that recommended standards ...


Page 9 - very last line
I am not sure due to the change tracking, but I think it says "-CCSDS support services and capabilities." Surely there should not be a hyphen.


Page 13 - MOIMS goal 2
The bullet
*             Recommended Standards / Practices  Currently in ProductionNone
The word "None" should be on the next line.
"maneuver" looks like a typo to me, but it might be US spelling. My version of Word changes it to "manoeuvre"

Page 15 - MOIMS goal 7
"ervices" should be "services"


From: cmc-bounces at mailman.ccsds.org [mailto:cmc-bounces at mailman.ccsds.org] On Behalf Of Nestor.Peccia at esa.int
Sent: 09 November 2013 11:46
To: cmc at mailman.ccsds.org
Cc: cesg at mailman.ccsds.org
Subject: [CMC] CCSDS Strategic Plan Draft 11

Dear CMC members

After several iterations, the CESG is now in a position to deliver an updated version of the CCSDS Strategic Plan (Draft 11) (see attachment below)



CESG will present the main changes introduced in this Plan at the next CMC meeting at Montreal (9th - 11th Dec 2013).

We will appreciate a set of CMC consolidated comments, if possible before the CMC venue. This is the reason of distributing the Plan 1 month prior to the meeting.

CMC needs to consider the following when reviewing the doc.:

  *   Your first reaction will be that it is not only a Strategic Plan because it also includes references to all books produced in the past (i.e. published MBs / BBs and some GBs), books currently in production and books not yet in the CWE.
Why?
  *   The final goal is to include the Strategic Plan in the CWE (as many Standards Organizations do), using the existing web site and augmented materials linked via hyperlinks
e.g. .showing charter, ops concept, objective, the mapping between CCSDS Technical Strategic Goals, Area goals/sub-goals and existing / at work / future recommended standards and practices (including the associated products / works / cross support and interoperability capabilities).
i.e.
        CCSDS Charter                        Update existing text in CWE
        CCSDS Operating Concept         New and hiperlinked to previous
        CCSDS Target Missions        ditto
        CCSDS Objective                ditto
        CCSDS Goals                        ditto
        CCSDS Standard. Concept        ditto
        High level goals                ditto

The Area objectives and goals (e.g. Section 1.1 for SEA) can be included in the corresponding CWE SEA section. It can be linked backwards to the related CCSDS high level goals and forward to the different WGs
The WG objectives and goals can be included in the corresponding CWE SEA WG section and linked backwards to the Area goals and forward to the suite of standards

The document also indicates (highlighted in blue) for every Area / WG goal the following details (to be referenced via hyperlinks in the CWE):

Related CCSDS Technical Strategic Goals: 1, 6
Existing Informational Reports
*        CCSDS 350.0-G-2 The Application of CCSDS Protocols to Secure Systems.
*        CCSDS 350.4-G-1 CCSDS Guide for Secure System Interconnection.
*        CCSDS 350.7-G-1 Security Guide for Mission Planners.
Existing Recommended Standards / Practices
*        CCSDS 352.0-B-1 Crytographic Algorithms
*        CCSDS 311.0-M-1 Reference Architecture for Space Data Systems
*        CCSDS 351.0-M-1 Security Architecture for Space Data Systems
Recommended Standards / Practices Currently in Production
*        CWE Doc. tbd Network Layer Security Adaptation Profile
Milestone ID: MIL-SEA-101                Completion Date: 2015
*        CWE Doc. tbd Symmetric Key Management Recommendations
Milestone ID: MIL-SEA-102                Completion Date: 2016
Future Work
*        None identified

Note: It is clear that this type of information is not part of the Strategy, but it is given for the sake of completeness,
 A potential graphical roadmap form showing the current / future milestones will be discussed later (it could be easily implemented as a report utility)
In order to achieve this, CESG proposes to have 2 classes of projects:

     *   Active (with resources identified)

     *   Inactive (they are long term and included for the sake of strategic completeness)
CESG recommendation is that every goal is linked to existing published docs and CWE Projects

For the sake of completeness, the document contains the references to the whole list of CCSDS published BBs (53) / MBs (28); and 70 out of the 100 Projects currently existing in the CWE. The process has been very useful to discover some issues

     *   There are some inconsistencies between CWE Project titles and the current book names (BB and MB to be updated).

     *   There are inconsistent approaches between WGs (Some include in their Charters a full set of BB/MB/GB  covering a long period in the future, others not). In order to have the full roadmap in the CWE we need also to include the planned books for the next 7-10 years. The notion of active / non-active CWE Projects have to be discussed.


  *   GBs supporting a BB / MB are not included, but stand-alone GBs serving its own purpose are included

  *   Two important subjects are not yet addressed in the Plan, namely Promotion of CCSDS standards and outreach

     *
  *   The CWE will also show the tactical Plan (i.e.Charters, Projects, Resources, Schedule)

  *   Interdependencies between WGs and Projects are not shown (too cumbersome)

ciao
nestor

This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.



Please consider the environment before printing this email.

-- 
Scanned by iCritical.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cmc/attachments/20131202/d13b0eff/attachment-0001.html


More information about the CMC mailing list