[Sois-opp] RE: [SOIS] RE: SOIS Application Support Services WG - Plug-and-Play Work Plan

Rakow, Glenn P. (GSFC-5610) glenn.p.rakow at nasa.gov
Thu Apr 7 14:39:55 EDT 2011


Hi Jane,

#1.12 refers to the Packet and file service (Application Support Service Book).  You mentioned that you had some "worker bees" review that book (if I am not mistaken).  If so those comments were not forwarded.

Glenn

From: Marquart, Jane K. (GSFC-5820)
Sent: Thursday, April 07, 2011 2:26 PM
To: Stuart Fowell; sois-opp at mailman.ccsds.org; sois-app at mailman.ccsds.org; sois-exec at mailman.ccsds.org; sois at mailman.ccsds.org
Cc: Kevin Rice; r.krosley at andropogon.org; Rakow, Glenn P. (GSFC-5610); Kevin Gifford; Aitor.Viana.Sanchez at esa.int; Peter Mendham; Scott Burleigh; Felice Torelli; HORNE, WILLIAM D.. (GSFC-5670)
Subject: Re: [SOIS] RE: SOIS Application Support Services WG - Plug-and-Play Work Plan

Hi Stuart,

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.

#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.
   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.

#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.

Jane


On 4/7/11 5:19 AM, "Stuart Fowell" <Stuart.Fowell at scisys.co.uk> wrote:
Hi,

Attached are the minutes from Tuesday SOIS Plug-and-Play Telecon #1.

Those on the cc list, please can you check that you are in the SOIS-OPP mailing list.

Regards,

Stuart

________________________________

From: Stuart Fowell
Sent: 28 March 2011 15:53
To: 'sois-opp at mailman.ccsds.org<sois-opp at mailman.ccsds.org>'
Subject: SOIS Application Support Services WG - Plug-and-Play Work Plan

CCSDS SOIS-APP Plug-and-Play Work Plan
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.

Aims
The main aim of the SOIS-APP group's work on plug-and-play is to publish standards for:


 *   A coherent onboard plug-and-play architecture documented in the SOIS Green Book
 *   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).
 *   A specification for a SOIS Electronic Datasheet (EDS) standard in the form of a descriptive book and an XML schema - Blue Book?
 *   A specification for the mapping from an IEEE 1451.0 TEDS to a SOIS EDS - part of EDS Blue Book?.
 *   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?.
 *   A specification for the dictionary of terms (DoT) - part of EDS Blue Book but see below?.
 *   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?.
 *   Template datasheets for each of the specified device classes - part of EDS Blue Book or separate?.
 *   A process for the allocation of unique identifiers, if required - under control of SANA?.

Work Plan
These are roughly, but not exclusively, in order. Some overlap will be necessary.

 1.  Detailed investigation of IEEE1451.0 including a description of all elements to ensure a strict superset. Lead?
 2.  Detailed investigation of draft AIAA SPA standards to align DVS-level datasheet section and DVS/DES service interfaces where applicable. Lead?
 3.  Propose an initial EDS schema. Lead?
 4.  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?
 5.  Align dictionary of terms with SPA/AIAA CDD. Lead?
 6.  Merge DVS service interface-level EDS with xTEDS including DoT/CDD merge (political as well as technical). Lead?
 7.  Prototype DVS and DES for design-time and run-time adaptivity use cases.  This should use the full range of specified electronic datasheets. Lead?
 8.  Refine DVS to accommodate temporal and non-functional issues. Lead?
 9.  Develop prototype tool chain including IEEE 1451.0 TEDS import and SPA/AIAA import/export. Lead?
 10. Refine DVS and DES and align interfaces with SPA/AIAA. Lead?
 11. Carry out survey of existing devices (probably combined with above) to permit the definition of template device EDSs (for device classes). Lead?

Progressing the Work Plan
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).

A Doodle survey has been set up (http://www.doodle.com/4kdtstb9ayrgc2fm) <http://www.doodle.com/4kdtstb9ayrgc2fm> 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).

Agenda of PnP Telecon #1:

 1.  Agree work plan and item owners
 2.  Item 1 on the work plan.

___________________________________________________________
Stuart D. Fowell B.Eng MBCS
Senior Consultant - Space Division
SciSys UK Limited
T:  +44 (0)117 916 5138 | M:  +44 (0)7715 750255 | F:  +44 (0)117 916 5299
E:  stuart.fowell at scisys.co.uk | http://www.scisys.co.uk



SciSys UK Limited. Registered in England and Wales No. 4373530.
Registered Office: Methuen Park, Chippenham, Wiltshire SN14 0GB, UK.

Before printing, please think about the environment.
  <#>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sois-opp/attachments/20110407/99bef58b/attachment-0001.html


More information about the Sois-opp mailing list