[Fiware-wpl] Exploitation and Standardization issues at WP level

[Juan Bareño Guerenabarrena]

Dear WPL,

 

As exploitation leader we will ask you, if you could  book a slot for Exploitation and Standardization issues during the parallel workshops for the individual work packages

issues. Maybe by EOB on Wednesday or at the beginning of the Thursday, we have to arrange them properly for not overlapping.

 

So as a tentative agenda I would propose the following:

 

*             Market Trends (each domain) and State of the Art by selected assets for the GE in each domain( (20 minutes)

 

Generic Enabler 

Existing Assets 

Actors 

Exploited 

Resource Management 

-       In the Market

-       To develop

-       Project investigation 

-Amazon 

-       Separately

-       Bundle 

 

*             SWOT Analysis (each domain) and Product attributes definition by selected assets for the GE in each domain  (20 minutes)

 

Generic Enabler 

Innovation/Disruption 

Added Value 

Target Market 

Resource Management 

- What innovation is provided? 

-       What problem it solve?

-       Extra features provided?

-       Separated/bundle?

-       Potential users

-       Use Cases by Sector and interrelation with the PPP Projects

 

*             Standardization issues at domain level (20 minutes)

 

For continuing this contact at domain level, after the meeting , we will have to appoint a representative for each domain for exploitation and standardization issues

 

Any feedback from any side is welcome and please answer with your slot proposal 

 

Thanks 

 

Juan

 

 

 As I noticed there is already a meeting planned for Wednesday morning 9-12, where experts from Data, IoT, and Apps will come together. I believe there are other constellations that should meet, at least from the perspective of the Apps WP.  f.e.:

*             Cloud - Apps

*             Security - Apps

*             Interface to the network - Apps

I suggest to use the Wednesday morning timeslot for parallel cross WP sessions. This would also produce valuable details for the following backlog etc. discussions

Regards,

Torsten

 

Dear Pier,

 

We agree. If possible we would like to plan it for Thu morning, say 1 hour or 1.5 hours, from 9 AM.

The parts of common interest we identified are:

-cloud proxy, CE vs IoT gateway

-device concept in I2ND (CDI) vs IoT device in IoT

-points of contact/interfaces between I2ND and IoT

 

So as a tentativa agenda I would propose the following:

*             I2ND elaborates on CDI and cloud proxy concepts + interfaces 1+2 (20 minutes)

*             IoT elaborates on IoT device and IoT gateway concepts + the IoT communications task (20 minutes)

*             Brainstorming discussion (10-20 minutes)

*             Conclusions, action items (10-20 minutes)

Any feedback from any side is welcome.

 

Thanks & Br,

 

Lorant

 

  

Juan Bareño

 

Atos Research and Innovation

 

T +34 912148859

juan.bareno at atos.net <mailto:blanca.jordan at atosresearch.eu> 

Albarracín 25

28037 Madrid

Spain

www.atos.net <http://www.atos.net/> 

www.atosresearch.eu <http://www.atosresearch.eu/> 

 

 

 

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy it. 
As its integrity cannot be secured on the Internet, the Atos 
group liability cannot be triggered for the message content. Although 
the sender endeavours to maintain a computer virus-free network, 
the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. 

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial 
destinada solamente a la(s) persona(s) mencionadas anteriormente 
pueden estar protegidos por secreto profesional. 
Si usted recibe este correo electronico por error, gracias por informar 
inmediatamente al remitente y destruir el mensaje. 
Al no estar asegurada la integridad de este mensaje sobre la red, Atos 
no se hace responsable por su contenido. Su contenido no constituye ningun 
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. 
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor 
no puede garantizar nada al respecto y no sera responsable de cualesquiera 
danos que puedan resultar de una transmision de virus. 
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110912/6b337d2a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 78 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110912/6b337d2a/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 816 bytes
Desc: image002.gif
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110912/6b337d2a/attachment-0001.gif>