[Fiware-iot] Partner assets involved in T5.2 - Resources management -

[Haller, Stephan]

I added a few things regarding assets coming from IoT-A and SENSEI.

https://forge.fi-ware.eu/docman/view.php/11/450/v19_IoT-Architecture-mapping.xlsx



Regards,

-Stephan





From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras
Sent: Montag, 3. Oktober 2011 12:35
To: fiware-iot at lists.fi-ware.eu
Subject: Re: [Fiware-iot] Partner assets involved in T5.2 - Resources management -
Importance: High



Dear partners involved within T5.2

please remember to provide ASAP your specific inputs for the T5.2,
now you can take the last version of the file (sent by Sabrina at  https://forge.fi-ware.eu/docman/view.php/11/448/v18_IoT-Architecture-mapping.xlsx )
So far there are not any additional contributions, we need it for completing the assets map in every task !!!
Please remember to mark in red/yellow/green the level about how your asset fulfills the requirement/functionality described, for a easier identification later.

Please contact me if you have any doubt,
Thanks a lot!

best regards,
Ricardo.

Ricardo de las Heras wrote:

Dear partners

I've added a new sheet (T5.2) within the 'Architecture mapping' file we were already managing, in order to focus the description only in the assets involved in Resource Management, reducing the scope of features and functional blocks we have to manage for define the set of assets that finally will cover the functionality of this task 5.2.

Youn can find it with v16 at:
https://forge.fi-ware.eu/docman/view.php/11/447/v16_IoT-Architecture-mapping.xlsx

Please, NEC, NSN, Orange, ..., try to complete ASAP your column describing the referenced capabilities in the 2nd column. Indeed, thouse blocks are extracted from the Word document where we described the architecture. In this way I have added to the cells on the 2nd column some comments you easily find passing the mouse over the cell in order to clarify their description.

I greatly appreciate the time you take to give me your input, next I hope to better understand how we can combine our assets,
so don't hesitate in contact me if you require additional clarifications.

Thank you very much and best regards,
Ricardo.


Farkas, Lorant (NSN - HU/Budapest) wrote:

Dear Ricardo,



I fully agree, the morning session was OK, the afternoon session was not OK. I also think if we had more time to discuss among ourselves, we could have done more. I will try to compile a minimum set of requirements for the asset description and allocate a task to each asset owner where I don't see these.

The minimum would be:

-licensing conditions (open source, closed source, partially open source etc)

-which GE functionality is covered to which extent



Alternatively I think it would be better for the task leaders could start this exercise of clearing the picture, starting from the Excel sheet as a first input, which gives at least a filter which assets can be dropped right from the beginning.



Thanks & Br,



Lorant



  _____

From: ext Ricardo de las Heras [mailto:rheras at tid.es]
Sent: Wednesday, September 21, 2011 5:21 PM
To: Farkas, Lorant (NSN - HU/Budapest)
Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: Re: [Fiware-iot] Partner assets

Dear Lorant, all,

first thank you for compilling there all the information related with the assets.

I think we still have a hard work to do in order to clarify the list of assets that finally will compose the functional blocks of every task, the steps done so far seems to be not decisive enough.

First I miss to have a document including a clear description of every asset (some literature paragraphs in Word), describing its key capabilities that would be provided to Fiware IoT, and how those capabilities are mapped to every of the tasks and its main functionalities.
IMHO some of the slides are very nice but don't describe clearly which functionalities described in the Word document 'High level Architecture description' are fulfilled or not.

Really I'm a little bit dissappointed after the Turin meeting, because I though we were going to come back home with a clear map of the assets, having a clear picture by task and the most suitable candidate in every case, but this is not the real case I think, at least for me :(

I don't know if this is the best way to proceed, but I'd propose you to take actions in this way in the short term, otherwise I think we have a puzzle that we will not able to solve.

thanks,
br,
Ricardo.


Farkas, Lorant (NSN - HU/Budapest) wrote:

Dear All,

FYI, I uploaded to forge the company asset presentations I saw so far. With the private field set, of course.
https://forge.fi-ware.eu/docman/?group_id=11#<https://forge.fi-ware.eu/docman/?group_id=11>

Thanks & Br,

Lorant



--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es>
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Phone3 Skype: (+34) 91 1878107 + Ext: 327
Telefónica I+D<http://www.tid.es>
-------------------------------------



  _____

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es>
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Phone3 Skype: (+34) 91 1878107 + Ext: 327
Telefónica I+D<http://www.tid.es>
-------------------------------------



--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es>
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Telefónica I+D<http://www.tid.es>
-------------------------------------



  _____

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111004/a01bfb10/attachment.html>