<HTML>
<HEAD>
<TITLE>Re: [SOIS] RE: SOIS Application Support Services WG - Plug-and-Play Work Plan</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Stuart,<BR>
<BR>
So that you can close some actions promptly, here are my responses. Note that Bill Horne has taken over as GSFC Standards manager, so any process/managerial/voting questions should be directed to him.<BR>
<BR>
#1.3 – This comment was made over a year ago. If memory serves me, there was an ESA programmatic issue which kept the PnP BOF from becoming its own WG...something along the lines of resources for a “new” WG vs. keeping an existing one going, hence the “initial” work is being done under SOIS APP. Chris may recall better than I. Perhaps I’m mistaken. So I’m not sure this is still a valid comment. <BR>
As a side to the primary part of the comment, I also suggested that if someone looking in from the outside wanted to know if there was any PnP work going on in CCSDS, they would only find the BOF description page but no info on the real work being done. Hence it might be advantageous to the WG to somehow get that info, or wording, inserted somewhere in the SOIS public domain.<BR>
<BR>
#1.12 – I am no longer the one to ask. I did see in an e-mail that all comments were due March 18th to Glenn. I myself did not review it, but if Glenn did not solicit or receive any comments, then by default the book goes forward.<BR>
<BR>
Jane<BR>
<BR>
<BR>
On 4/7/11 5:19 AM, "Stuart Fowell" <<a href="Stuart.Fowell@scisys.co.uk">Stuart.Fowell@scisys.co.uk</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Hi,<BR>
<BR>
Attached are the minutes from Tuesday SOIS Plug-and-Play Telecon #1.<BR>
<BR>
Those on the cc list, please can you check that you are in the SOIS-OPP mailing list.<BR>
<BR>
Regards,<BR>
<BR>
Stuart<BR>
<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT>
<P ALIGN=CENTER>
<FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'><HR ALIGN=CENTER SIZE="2" WIDTH="100%"></SPAN></FONT>
<P>
<FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> Stuart Fowell <BR>
<B>Sent:</B> 28 March 2011 15:53<BR>
<B>To:</B> <a href="'sois-opp@mailman.ccsds.org">'sois-opp@mailman.ccsds.org</a>'<BR>
<B>Subject:</B> SOIS Application Support Services WG - Plug-and-Play Work Plan<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>CCSDS SOIS-APP Plug-and-Play Work Plan<BR>
</B>Building on issued standards for subnetwork services, one of the major goals of this group is to agree a coherent architecture for plug-and-play of onboard devices based on use cases and requirements and to produce and agree a set of standards to allow interoperable plug-and-play implementations.<BR>
<BR>
<B>Aims<BR>
</B>The main aim of the SOIS-APP group’s work on plug-and-play is to publish standards for:<BR>
<BR>
</SPAN></FONT></FONT><UL><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A coherent onboard plug-and-play architecture documented in the SOIS Green Book</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Services for carrying out plug-and-play activities and interfacing with plug-and-play devices in the form of Device Enumeration Service (DES) and Device Virtualisation Service (DVS) Magenta Books (no changes have been identified as being required to the current Device Access Service Magenta Book).</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A specification for a SOIS Electronic Datasheet (EDS) standard in the form of a descriptive book and an XML schema – Blue Book?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A specification for the mapping from an IEEE 1451.0 TEDS to a SOIS EDS – part of EDS Blue Book?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A specification for the mapping from an xTEDS datasheet to a SOIS EDS. It may well be that the xTEDS datasheet is just one section of a SOIS EDS. A translation could be specified as an XSLT – part of EDS Blue Book?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A specification for the dictionary of terms (DoT) – part of EDS Blue Book but see below?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A specification for the process of updating the DoT. This needs to be a relatively quick process as, particularly in the beginning, the DoT will need to be updated frequently – under control of SANA?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Template datasheets for each of the specified device classes – part of EDS Blue Book or separate?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>A process for the allocation of unique identifiers, if required – under control of SANA?.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></UL><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'> <BR>
<B>Work Plan<BR>
</B>These are roughly, but not exclusively, in order. Some overlap will be necessary.<BR>
</SPAN></FONT></FONT><OL><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Detailed investigation of IEEE1451.0 including a description of all elements to ensure a strict superset. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Detailed investigation of draft AIAA SPA standards to align DVS-level datasheet section and DVS/DES service interfaces where applicable. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Propose an initial EDS schema. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Specify electronic datasheets for approximately 20-30 existing devices to ensure compatibility and refine EDS schema. These devices must be selected for both breadth (coverage of device classes) and depth (variation within a device class). This process is to ensure that the EDS schema is sufficiently flexible to be able to represent most devices, and to build confidence in the SOIS plug-and-play approach. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Align dictionary of terms with SPA/AIAA CDD. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Merge DVS service interface-level EDS with xTEDS including DoT/CDD merge (political as well as technical). Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Prototype DVS and DES for design-time and run-time adaptivity use cases. This should use the full range of specified electronic datasheets. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Refine DVS to accommodate temporal and non-functional issues. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Develop prototype tool chain including IEEE 1451.0 TEDS import and SPA/AIAA import/export. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Refine DVS and DES and align interfaces with SPA/AIAA. Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Carry out survey of existing devices (probably combined with above) to permit the definition of template device EDSs (for device classes). Lead?</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></OL><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'> <BR>
<B>Progressing the Work Plan<BR>
</B>To progress through the work plan, we aimed to have fortnightly teleconferences, limited to 1 hour and at a regular time, to progress this. Each work item should be allocated an owner, who will commit the time to guide the item through to completion (it is anticipated that others will need to contribute, even if it is only in the form of reviewing).<BR>
<BR>
A Doodle survey has been set up (<a href="http://www.doodle.com/4kdtstb9ayrgc2fm">http://www.doodle.com/4kdtstb9ayrgc2fm</a>) <<a href="http://www.doodle.com/4kdtstb9ayrgc2fm">http://www.doodle.com/4kdtstb9ayrgc2fm</a>> to agree day of week when most people can attend on a regular basis. This will also give us a basis of those who wish to participate (those who respond to the survey).<BR>
<BR>
Agenda of PnP Telecon #1:<BR>
</SPAN></FONT></FONT><OL><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Agree work plan and item owners</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT><LI><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Item 1 on the work plan.</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></OL><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'> <BR>
<FONT COLOR="#136798"><B>___________________________________________________________<BR>
Stuart D. Fowell B.Eng MBCS<BR>
</B>Senior Consultant – Space Division<BR>
<B>SciSys UK Limited<BR>
</B></FONT></SPAN></FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><FONT COLOR="#198AC9"><FONT SIZE="1"><SPAN STYLE='font-size:7pt'>T: +44 (0)117 916 5138 | M: +44 (0)7715 750255 | F: +44 (0)117 916 5299<BR>
E: <a href="stuart.fowell@scisys.co.uk">stuart.fowell@scisys.co.uk</a> | <a href="http://www.scisys.co.uk">http://www.scisys.co.uk</a><BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><FONT COLOR="#808080">SciSys UK Limited. Registered in England and Wales No. 4373530.<BR>
Registered Office: Methuen Park, Chippenham, Wiltshire SN14 0GB, UK.<BR>
</FONT><FONT COLOR="#0000FF"> <BR>
</FONT></SPAN><FONT COLOR="#008000"><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>Before printing, please </SPAN></FONT><FONT SIZE="1"><SPAN STYLE='font-size:7pt'>think about the environment.<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <#> <BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>