<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear CSSMWG Colleagues,<o:p></o:p></p>
<p class="MsoNormal">I have uploaded the most recent draft (V1.1) of the Simplified Configuration Profile and Service Agreement Tech Note<o:p></o:p></p>
<p class="MsoNormal">To the CWE at URL:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x1.docx">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x1.docx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The focus of the updates are in sections 6 – 8. Section 6 establishes the overall framework and metamodels for the definition of Space Link Service Profile Templates, and how those Space Link Service Profile Templates are used to create
(a) single-service Space Link Service Configuration Profile Templates and (b) multi-service Configuration Profiles. The single-service Space Link Configuration Profile Templates are intended to be the “cookie cutters” – schemas that need just a little bit
of extra information to create Mission-specific operational configuration profiles. Due to the number of combinatorial possibilities in configuration profiles that contain multiple space link services, multi-service configuration profiles are almost by definition
Mission-unique, and so must be must be built individually by combining the pertinent Space Link Service Profiles.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Section 7 contains the current set of Space Link Service Profiles – that is, the predefined “stacks” of functional resources from aperture to user interface (or data storage for subsequent offline transfer to the user). All Space Link Service
Profiles corresponding the IOAG Service Catalog #1 (our “guidance” for what we need to be tackling in the first round of Service Management) are addressed with at least a diagram of the component Functional Resources. Three of the Profiles – Forward CLTU,
Forward Telecommand Real-Time Communication (which covers Forward Space Packet SLE transfer services and Forward Frame CSTSes), and the Return Online Real-Time Communication (which covers RAF, RCF, and ROCF, plus extraction of CLCWs for use on the TC forward
links) – are fully elaborated, at least in a strawman sense: UML class diagrams for the Space Link Service Profile Template and the corresponding Space Link Service Configuration Profile Template, tables of configuration parameters for each of the member Functional
Resources, and an example instantiation of the Space Link Service Configuration Profile Template.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Section 8 provides examples of how the Forward CLTU and the Return Online Real-Time Communication Space Link Service Profiles and Space Link Service Configuration Profiles can be combined and/or refined in various ways to create service
packages that schedule (a) both forward and return comm services, (b) a forward-only (CLTU) comm service, and (c) a return-only comm service with two RAF service instances.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will not be participating in the March CSSMWG telecon, but I will be prepared to present and discuss this material at the Gaithersburg meeting.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am looking forward to seeing you all again in April.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
</div>
</body>
</html>