<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.sany-ip.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>SANY Sensors Anywhere - SP5</title>
 <link>http://www.sany-ip.org/taxonomy/term/95/0</link>
 <description>[SANY] marine risks sub project</description>
 <language>en</language>
<item>
 <title>SANY SP5: marine risks sub project</title>
 <link>http://www.sany-ip.org/description/sany_sp5_marine_risks_sub_project</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-1&quot;&gt;&lt;div class=&quot;flexinode-textarea-2&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description: &lt;/label&gt;
  &lt;p&gt;&lt;img src=&quot;http://www.sany-ip.eu/filemanager/active?fid=91&quot; alt=&quot;SANY S54 pilot&quot; align=&quot;right&quot; width=&quot;50%&quot; vspace=&quot;10&quot; hspace=&quot;20&quot; /&gt;“Marine Risks” is the second of three “application sub projects” that will be developed within SANY. The overall structure of the &lt;a class=&quot;glossary-term&quot; href=&quot;http://sany-ip.eu/sany_glossary/sp5&quot;&gt;&lt;acronym title=&quot;SP5: [SANY] marine risks sub project&quot;&gt;SP5&lt;/acronym&gt;&lt;/a&gt; is the same as the structure described in &lt;a class=&quot;glossary-term&quot; href=&quot;http://sany-ip.eu/sany_glossary/sp4&quot;&gt;&lt;acronym title=&quot;SP4: [SANY] air pollution risks sub project&quot;&gt;SP4&lt;/acronym&gt;&lt;/a&gt; with some differences at task levels.&lt;/p&gt;
&lt;p&gt;An overview of the SP5 work packages is given below: &lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.0 Sub project management:&lt;/b&gt; This WP covers the technical management of the sub project and reporting.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.1 Requirements analysis &amp;amp; specification:&lt;/b&gt; This WP will develop and validate a range of marine use-cases, based on existing experience in the field and discussion with a range of end-users.  It will subsequently define and refine the pilot specification, based on these requirements and the evaluation of the rapid prototyping work (WP 5.2)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.2 Baseline implementation:&lt;/b&gt;  This WP will construct a prototype based on the existing MASS/&lt;a class=&quot;glossary-term&quot; href=&quot;http://sany-ip.eu/sany_acronyms/sse&quot;&gt;&lt;acronym title=&quot;SSE: Service Support Environment&quot;&gt;SSE&lt;/acronym&gt;&lt;/a&gt; platform to showcase how the application could address use-cases.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.3 Application implementation:&lt;/b&gt; This WP will develop the application based on the specification from WP 5.1, making use of the systems implemented in core sub-projects (&lt;a class=&quot;glossary-term&quot; href=&quot;http://sany-ip.eu/sany_glossary/sp2&quot;&gt;&lt;acronym title=&quot;SP2: [SANY] sensor networks sub project&quot;&gt;SP2&lt;/acronym&gt;&lt;/a&gt; &amp;amp; &lt;a class=&quot;glossary-term&quot; href=&quot;http://sany-ip.eu/sany_glossary/sp3&quot;&gt;&lt;acronym title=&quot;SP3: [SANY] sensor fusion and decision support sub project&quot;&gt;SP3&lt;/acronym&gt;&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.4 Pilot operation &amp;amp; evaluation:&lt;/b&gt; This WP will manage the launch and operation, and evaluate the 1-st and 2-nd version of the application in terms of user satisfaction, reliability and adherence to specifications.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.5 Consolidation:&lt;/b&gt; This WP managed the interaction between this SP and the other SPs (including communication and knowledge transfer) in the first project year.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;WP5.6 Demonstration:&lt;/b&gt; Within this WP, the results of the SP5 will be presented to a wider public.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <comments>http://www.sany-ip.org/description/sany_sp5_marine_risks_sub_project#comment</comments>
 <category domain="http://www.sany-ip.org/sany_glossary/sp5">SP5</category>
 <pubDate>Tue, 17 Oct 2006 09:16:35 +0200</pubDate>
 <dc:creator>Denis Havlik</dc:creator>
 <guid isPermaLink="false">376 at http://www.sany-ip.org</guid>
</item>
</channel>
</rss>
