[Css-csts] Functional Resource Reference Model Tech Note status package on CWE

[John Pietras]

CSSA colleagues ---
I have just uploaded a "status package" for the Functional Resource reference Model Technical Note to the CWE > Cross Support Services Area (CSS)<http://cwe.ccsds.org/css> > Documents<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > CSS Area<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%20Area&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > CWE Private<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%20Area%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D> > Functional Resources and Service Components folder at URL
http://cwe.ccsds.org/css/docs/CSS%20Area/CWE%20Private/Functional%20Resources%20and%20Service%20Components/FunctResRefModel_TechNote-TN-0.10-160630.zip

The zipped package contains a heavily annotated draft of the tech note itself, plus a folder containing the original files and .emz file for the ~80 figures in the document.

There are many changes that are needed in the Tech Note, arising from decisions made at the Cleveland meeting regarding the Service Component terminology and related fine-tuning of concepts regarding how functional resources relate to each other, as well as lower-level refinement of FR names and characteristics resulting from the ongoing developing of the candidate SANA FR registry. The Tech Note contains a Book Captain's Notes section at the beginning, which lays out the major areas of work that is needed. Unfortunately I had neither the time nor the resources to do anything following the Cleveland meeting. So to a large extent the notes represent more goal statements than  prescriptions for specific changes.

Although the FR Reference Model Tech Note needs a lot of work, I don't think that it will deter the near-term work in either the CSTSWG or CSSMWG. The information being prepared by Wolfgang and Holger for the SANA Registry should satisfy the needs of CSTS, in particular the MD-CSTS. With regard to Service Management, the major shortcoming is that the managed (configuration) parameters of the various FRs in the core set still need to be defined, and the FR Reference Model is not needed to that per se.

The real use of the Reference Model is as a longer-term tool for identifying how new standards and capabilities fit into the overall big picture, and for providing a standard language and model for expressing those relationships in a way that can be applied to monitoring, controlling, and configuring (via SM) those capabilities. Hopefully at some point the Reference Model, or something like it, can be picked up and made current.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20160630/f14d18fb/attachment.html>