<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=utf-8">
<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:blue;
text-decoration:underline;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Guys,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just to help clarify the context change in the ASL doc. What we have done is to shift the entire document from talking about "the SOIS Area does this" and "the MOIMS Area does that" to a discussion that is cats in terms of "Spacecraft
Onboard functions" and "Mission Operations functions". A part of this must acknowledge that while SO function only operate on-board, and likely in a real time, time and resource constrained environment, that it is possible for to MO functions, like mission
or observation planning, or navigation route calculations, that normally execute on the ground, to be migrated on-board. There are lots of ways to do this, including developing new code, re-writing code for the on-board, resource constrained, environment,
or running ported code in a co-processor if such a resource is available. This is all part of the whole "3 case" discussion, which remains, but in this same sort of edited format. This is the new intro text related to this in sec 1.3:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">"As in most CCSDS technical documents, in this document these standards will be described based on their functional groupings and deployment locations and will not referenced by the Areas
or Working groups that develop and maintain them. They are described as Mission Operations (MO) services and standards and Spacecraft Onboard (SO) services and standards."</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#4472C4"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The last thing to say is the text that we introduced to describe the difference between [Future] and [Prospective]. This is the new intro text related to this subject in sec 1.3:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">"The policy for CCSDS documents is that they are to be reviewed, and updated as needed, nominally every five years. This document, because of its design that touches on many other standards,
is likely to become out of date during that time. The reader is cautioned that this may be the case and it is strongly recommended that the CCSDS Publications website be consulted for the latest versions of any standards identified herein. This will particularly
be the case for any standards that are marked [Future] or [Prospective].</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#4472C4"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#4472C4"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#4472C4;letter-spacing:-.2pt">In cases where there is no existing
</span><span style="color:#4472C4;letter-spacing:-.2pt;mso-fareast-language:EN-GB">CCSDS Recommended Standard</span><span style="color:#4472C4;letter-spacing:-.2pt">, but one is in process or in the plan for future CCSDS standardization it will be marked [Future].
If there is a described concept for a standard, but no concrete plan to produce it, it will be marked as [Prospective]. There is no guarantee that [Prospective] standards will be produced nor that they will look like what is described herein."</span><span style="color:#4472C4"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal">As Ramon indicated, we want to enlist your help in arriving at a descriptive set of "implementation neutral" SO function names that reflect what you plan to do [Future] or that you think you may do or would like to do [Prospective].<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">SEA-SA <sea-sa-bounces@mailman.ccsds.org> on behalf of Ramon Krosley <r.krosley@andropogon.org><br>
<b>Date: </b>Friday, May 22, 2020 at 5:18 PM<br>
<b>To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov>, "'Hickey, Joseph P. (GSFC-582.0)[VANTAGE SYSTEMS INC]'" <joseph.p.hickey@nasa.gov>, "'Prochazka, Marek (JSC-OA111)[EUROPEAN SPACE AGENCY]'" <marek.prochazka@esa.int>, 'Richard Melvin'
<Richard.Melvin@scisys.co.uk>, "'Rakow, Glenn P. (GSFC-5610)'" <glenn.p.rakow@nasa.gov>, 'Xionwen He' <hexw501@hotmail.com>, SEA-SA <sea-sa@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [Sea-sa] potential SOIS application support functions<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">This message is to obtain a set of potential SOIS application support<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functions in the ASL-ADD Green Book. The names should be reasonably<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">generic, so anyone with experience in the area would be likely to recognize<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">what they do.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The following list includes the silvered magenta book functions, plus the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">list that was given me during the 2019 Spring meeting in Mountain View, plus<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Marek's comments. One of the names was changed from "Memory Dwell" to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">"Diagnostic Telemetry" as a suggestion from the SEA System Engineering<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Working Group.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The text here is copied from the ASL-ADD Green Book in its current state of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">revision in response to CESG review. One of the results of that revision is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">that "SOIS", which is an organizational area in CCSDS, is not used; instead,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the term "SO" (Spacecraft Onboard) is used to refer to an area of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">engineering interest. Another result of the revision is to define the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">[Future] category to represent definite plans of CCSDS working groups, and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">to define the [Prospective] category to represent potential work that is not<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">yet planned and may never be planned.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">These are the silvered application support functions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Command and Data Acquisition Services: This has been revived, and it<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">is the current scope of SEDS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--<span class="apple-tab-span">
</span>Device Data Pooling Service [Future] has been implemented, and so is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">a good candidate for publication as an example application support service<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">SEDS instance.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Time Access Service [Prospective]: This service will provide an<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">interface for setting and indicating time-correlated events for<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">synchronizing applications. Time synchronization is expected to be<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">accessible for most clock devices through command and data acquisition<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">services derived from SEDS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>File and Packet Store Services [Prospective]: These services will<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">provide an interface required by MO functions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>message transfer service: The name of this function is all lowercase<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">because it represents a generic concept that has multiple possible<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">implementations. A simple function that routes space packets, using the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Application Process Identifier (APID) to designate a logical data path, is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">an example implementation. This function has been described as a subset of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">AMS. The subset of AMS for this function will be described by SEDS<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">[Prospective], but an accompanying Recommended Practice will be unnecessary<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">because of the existence of AMS books.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Device Enumeration Service [Prospective]: This service will provide<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">an onboard searchable database of devices managed by SO. The subnetwork<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Device Discovery Service populates the database.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">This is the list of [Prospective] Application Support Services from the 2019<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Spring meeting.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>CCSDS File Distribution Protocol transfers files between vehicle and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">ground.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Checksum functions checks data integrity of memory, data, and files.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Data Storage records housekeeping, engineering, and science data for<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">later download.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>File Manager provides interfaces to the ground for managing files<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">onboard.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Housekeeping collects and packages telemetry from onboard<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">applications.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Health and Safety ensures that critical tasks check in, services<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">watchdog, detects CPU hogging, and calculates CPU utilization. Management<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">of platform resources by SO applies to the processor(s) in which real-time<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">activities occur.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Limit Checker monitors values and takes action when they cross<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">thresholds.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Diagnostic Telemetry allows ground to telemeter the contents of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">memory locations, generally for debugging.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Memory Manager loads and dumps memory, on request.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Scheduler schedules onboard activities, such as housekeeping<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">requests.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">-<span class="apple-tab-span">
</span>Stored Command executes sequences of commands at absolute or<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">relative times.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The following list was provided by Marek Prochazka in a comment on the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">ASL-ADD Green Book.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--<span class="apple-tab-span">
</span>Event-Action Service allows to trigger onboard action based on an<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">event generated onboard.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--<span class="apple-tab-span">
</span>OBCP allows to execute small script-like command sequences with flow<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">control logic. I think this acronym is for On Board Command Processor.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">This function is perhaps close enough to the Stored Command function above<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">that we should consider them to be the same function for the purpose of this<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">list. Unless someone comments otherwise, I'll keep this function, and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">remove the Stored Command function above.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--<span class="apple-tab-span">
</span>Critical Event Log allows generation and retrieval of critical<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">onboard events.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">--------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">When and if SOIS commits any of these functions to publication, their names<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">can change again at that time. If you have any changes to the list above,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">then please send me an email before the end of your local-time business day<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">on 2020 May 29. Thanks!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Ramon<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">SEA-SA mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="mailto:SEA-SA@mailman.ccsds.org">SEA-SA@mailman.ccsds.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</body>
</html>