<HTML>
<HEAD>
<TITLE>Re: [Sois-opp] SOIS PnP Work Plan</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Stuart,<BR>
<BR>
I applaud your efforts in providing focus. Well done! <BR>
<BR>
In addition to those work items listed below, there needs to be a modification to the SOIS charter/work plan to include the new books. Without the commitment of resources, I don’t think you can go forward (I believe Chris brought this up at the meeting). So I would suggest at your next telecon, have folks sign up/commit with resources to the things on your list just to make sure its doable in the timeframe defined.<BR>
<BR>
Jane<BR>
<BR>
<BR>
On 6/3/09 10:57 AM, "Stuart Fowell" <<a href="Stuart.Fowell@scisys.co.uk">Stuart.Fowell@scisys.co.uk</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE='font-size:11pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial">The next SOIS Plug-and-Play teleconference is fast approaching.<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Here I must hold up my hands and admit that I've been busy on other things recently. I'm sure I'm not the only one. This has got me thinking about how we proceed. I think that without a work plan we can easily drift from telecon to telecon without making any real *coordinated* progress. I, for one, work better when I've some milestones and deadlines!<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Basically we have to produce 4 things:<BR>
1. PnP section for SOIS Green Book<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">- Use Cases<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">- Requirements<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">- Provided Services<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">- Example usage scenarios & architecture<BR>
2. Device Electronic Data Sheet Red Book<BR>
3. Device EDS Access Service Red Book<BR>
4. Update Device Enumeration and Device Virtualisation Service Red Books to cover EDS and EDS Access Service<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">I suggest we work on the Device EDS Red Book before the Device EDS Access Service though there can be some overlap once we'd reaching some maturity on the Device EDS.<BR>
<BR>
Anyway, here's my strawman suggestion for a PnP Work Plan to provoke comment:<BR>
<BR>
1. Identify & write up Use Cases (covering both Device EDS and Device EDS Access Service)<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">2. Derive & write up EDS Generic Requirements (covering both Device EDS and Device EDS Access Service).<BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">3. Write PnP section to SOIS Green Book<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">4. Perform & write up Device EDS Technology Survey (TEDS, xTEDS, any others?)<BR>
5. Perhaps make a preliminary selection?<BR>
6. Perform Device EDS exploratory prototyping. Work some of the the Use Cases. This can be simply a paper exercise working out the xTEDS for a Thermistor through to a full blown demonstrator accessing xTEDS <BR>
7. Collate feedback from prototyping<BR>
8. Write 1st draft of Device EDS Red Book<BR>
9. SOIS review of 1st draft of Device EDS Red Book<BR>
10. CESG & Agency Review of 1st Issue of Device EDS Red Book<BR>
11. Full prototyping of Device EDS Red Book<BR>
12. CESG & Agency Review of 2nd Issue of Device EDS Red Book<BR>
13. Publish 1st Issue of Device EDS Blue/Magenta Book<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">14. Perform Device EDS Access Service exploratory prototyping<BR>
15. Collate feedback from prototyping<BR>
16. Write 1st draft of Device EDS Access Service Red Book<BR>
17. SOIS review of 1st draft of Device EDS Access Service Red Book<BR>
18. CESG & Agency Review of 1st Issue of Device EDS Access Service Red Book<BR>
19. Full prototyping of Device EDS Access Service Red Book<BR>
20. CESG & Agency Review of 2nd Issue of Device EDS Access Service Red Book<BR>
21. Publish 1st Issue of Device EDS Access Service Blue/Magenta Book<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Clearly this is quite a bit of work. Chris Taylor would like this done by end of 2010!<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">I feel we should be able to get the SOIS Green Book PnP section done over the summer<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Getting through to the 1st draft of a Device EDS Red Book can take some time due to the exploratory prototyping. It would be nice to think we could have this by the Fall 2009 meeting but perhaps this is optimistic? Should we be more realistic and aim for a full review of a 1st Red Book at Spring 2010 with the 1st CESG Review during Summer 2010?<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Certainly be Spring 2010 we should be working on the Device EDS Access Service, though this could start earlier.<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">At lot of this depends upon commitments on effort. It's one thing to attend teleconferences and another to do work between the two. There are different levels of commitment: prototyper, standards writer/editor/coordinator captain, reviewer. Who wants to volunteer for these different roles? I would like to nominate one person to own each of the Red Books and also someone to write the PnP section of the Green Book (I'm happy to do this myself though also happy if someone else wants to volunteer).<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">So, long email! What do you all think?<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Stuart D. Fowell BEng MBCS<BR>
Distributed, Real-Time Embedded (DRE) Consultant<BR>
SciSys UK Ltd<BR>
Clothier Road<BR>
Bristol<BR>
BS4 5SS<BR>
UK<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">Tel: +44 (0)117 916 5165<BR>
Mob: +44 (0)7715 750 255<BR>
Fax: +44 (0)117 916 5299<BR>
Email: <a href="stuart.fowell@scisys.co.uk">stuart.fowell@scisys.co.uk</a><BR>
Website: www.scisys.co.uk <<a href="http://www.scisys.co.uk/">http://www.scisys.co.uk/</a>> <BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT></SPAN><FONT SIZE="1"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:8pt'>This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. SciSys UK Limited therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Whilst SciSys UK Limited take reasonable precautions to minimise risk, you must carry out your own virus checks before opening attachments or reading e-mails and SciSys UK Ltd does not accept liability for any damage or loss in this respect. Contracts cannot be concluded with SciSys UK Limited by email.<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'><FONT COLOR="#0000FF"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
</FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><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></FONT></SPAN><FONT COLOR="#008000"><FONT SIZE="5"><FONT FACE="Webdings"><SPAN STYLE='font-size:18pt'>P</SPAN></FONT></FONT></FONT><FONT SIZE="5"><SPAN STYLE='font-size:18pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> </FONT></SPAN></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><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>