[Smwg] Updated Configuration Profile & Service Agreement Requirements Tech Note on CWE

[John Pietras]

CSSMWG colleagues ---
I have uploaded two copies of version 1.4 of the Requirements for Simple Configuration Profiles and Service Agreements Tech Note to the CWE. The "clan" version (all markup removed except for comments) can be found at
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x4-clean.docx?Web=1

The marked-up copy can be found at
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x4-markedup.docx?Web=1

There are some massive changes in the sections that are affected, so unless you have a burning need or desire to see what's changed since v1.3, I recommend downloading the clean copy.

The changes in this section are the result of two things:

1.       The infusion of Marcin's concepts for making the configuration profiles "tailorable" to local (network/Agency) needs by making the CCSDS-standard configuration parameters optional and allowing the addition of non-CCSDS configuration parameters (note - the idea of casting FR schema types that are aligned with the FR strata so as to help enforce proper layering is not addressed in this version) ; and

2.       Eliminating the isConfigured and isAlias configuration parameters to simplify construction and use of the configuration profiles. These parameter were originally introduced to allow a Mission to create a small number of configuration profiles that could be subsequently modified by respecification in the Service Package Request to support broad ranges of configurations, including (for example) configuration profiles for combined forward (Telecommand) and return (Telemetry) services that could be subsequently "downsized" to remove the FRs for either the forward or return service from the profile. Erik has observed that Missions would rather just create multiple profiles for such configurations rather than having to master the rules for manipulating the profiles through the per-Service-Package setting of isConfigured and isAlias configuration parameters.

The affected sections of the Tech Note are as follows: 3.5, 4.1, 4.3.1, 6, 7.11, 7.21, and 8. The other sections of the Tech Note are essentially untouched.

I will be on vacation next week and so will not be participating in next Tuesday's telecon. But if there is interest I can summarize the changes at the 16 July telecon.

Best regards,
John


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20190618/bbddbe49/attachment.html>