[CSS-CLOUD] Action OB-1 - Describe CDDS production

[Holger Dreihahn]

Dear CDDS Colleagues,
I have implemented the OB-1 action to introduce the CDDS Production underlying the CDDS Services. The production is described using Functional Resources, which turned out to be a nice way to provide a generalized description, providing the means to get more details if needed. In addition, the use of Functional Resources provides a consistent way to show, on what CDDS Monitoring Service and CDDS Control Service can actually act on:

  *
Functional Resource Parameter and
  *
Functional Resource Directives

It would be great if you could review the Production State Chapters in section 3 for each service: 931x10-O-draft-1.docx<https://spacecomm.sharepoint.com/:w:/r/sites/CSS/Shared%20Documents/CSS-CLOUD/Draft%20Documents/OrangeBook/931x10-O-draft-1.docx?d=wf40071f9a7574d65828a95064af8f382&csf=1&web=1&e=oqHU6c>
Feedback until end September, it would be very much appreciated.

As I know that some people have trouble with the CWE access, I attach also a copy of the latest CDDS OB draft 1. I attach also the HTML of an updated Functional Resource Tier 3. It can be used to look at the details of the Functional Resources used to describe the CDDS Production.

Example
If you look at the TM Production and wonder what the TmSyncAndChnlDecode does, which monitoring parameters and control directives it has, you can check the attached FRM. Alternatively the FRM Tier 1 is at SANA (https://sanaregistry.org/r/functional_resources/):


[image.png]
For the moment we have only the ASN.1 and XSD definitions generated from FRM, but I have some hope to have generated Protobuf definitions for Functional Resources soon; most probably that will be feature of the FRM editor at GitHub: https://github.com/esa/ccsds-css-frm-editor

With FRM compliant Protobuf definitions, the implementation of CDDS Monitoring and CDDS Control should be straight forward.

Best regards,
Holger
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 433231 bytes
Desc: image.png
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 354973 bytes
Desc: image.png
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 532825 bytes
Desc: image.png
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 931x10-O-draft-1.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 3938273 bytes
Desc: 931x10-O-draft-1.docx
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0001.docx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260820/a07501ce/attachment-0001.html>