[Smwg] Fw: CCSDS service catalog review - Comments from Martin Unal

[Colin.Haddow at esa.int]

---------------------------------------------------------------------------------------------------------
Dr. Colin R. Haddow,
HSO-GI, European Space Agency,
European Space Operations Centre,
Robert-Bosch-Str 5,
64293 Darmstadt,
Germany.

Phone; +49 6151 90 2896
Fax;      +49 6151 90 3010
E-Mail;  colin.haddow at esa.int
---------------------------------------------------------------------------------------------------------

----- Forwarded by Colin Haddow/esoc/ESA on 17/01/2017 18:09 -----

From:   Martin Unal/esoc/ESA
To:     Colin Haddow/esoc/ESA at ESA
Date:   22/12/2016 16:45
Subject:        CCSDS service catalog review


Hello

The version I reviewed:


1) SANA registry idea is good. 
I have done a quick check, most of the registry entry are useless, empty 
or outdated.

2) The "constraints" definition looks strange to me.
e.g : Is the cltu service not availble to Ka or Optical link ?
If this is coming from the cltu definition, a reference to the CCSDS 
document defining the cltu standard may be more adequate.
This comment applies to all service "contraint" paragraph in the Chapter 
3.

This document shall only list what needs to be in an Agency Service 
Catalog, (Or I missed the purpose of the this document)

3) 5.2  SCCS SERVICE COMMITMENT PROCESS
It looks a bit dangerous to mention commitment process in a standard.
This may vary a lot depending of each User/Provider relation and needs.
A standard should only define process and terminology to be used if one 
party wants or needs to commit.

Overall) the scope is not clear to me. What is the intention of this 
document ?
- As a standard, I beleive it should only provides rule and terminology to 
build a "provider specific" service catalog. 
In the way it is written, it seems to impose a list of service to be 
implemented by a certain date. It looks more like a "project plan" to me.

- What is RD.1 ?

- Is this a commitment for ESTRACK implementation ? => The core services 
are to be implemented by all IOAG agencies by 2020


For reference:
1.2     Scope 
The document is based on the list of services contained in Service Catalog 
#1 (SC#1, RD.1), produced by the Interagency Operations Advisory Group 
(IOAG). IOAG describes its services as ?core? or ?extended?. The core 
services are to be implemented by all IOAG agencies by 2020, while the 
extended services are to be considered for bilateral cross support.
The Recommended Practice provides a summary of the services and parameters 
that need to be included in an Agency's Service Catalog in order that it 
may support the planning and implementation of SCCS services based on 
those listed in SC#1. 

Regards
________________________________________
Martin UNAL
Ground Operation Manager
Ground Facilities Ops HSO - ONO
H-376
ESOC
Robert-Bosch Strasse 5
64 293 Darmstadt
Germany
Tel +49 6151 90 2959 Fax +49 6151 90 3190
________________________________________

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170117/a0707ca5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SCCS-SM_902.7-M-0.2 (2016 10 14).docx
Type: application/octet-stream
Size: 713716 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20170117/a0707ca5/attachment.obj>