Dear Technical WPL, please circulate this mail within your respective WP mailing lists
Tx
Juan
From: Bareno Guerenabarrena, Juan
Sent: Wednesday, February 04, 2015 7:03 PM
To: fiware-exploitation at lists.fi-ware.eu<mailto:fiware-exploitation at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Cc: lindsay.frost at neclab.eu<mailto:lindsay.frost at neclab.eu>; Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>; Tobias Jacobs (Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>); Javier de Vicente (javier.devicente at futuranetworks.com<mailto:javier.devicente at futuranetworks.com>); Raúl Sánchez (raul.sanchez at futuranetworks.com<mailto:raul.sanchez at futuranetworks.com>); De-Lama Sanchez, Nuria (nuria.delama at atos.net<mailto:nuria.delama at atos.net>); Miguel Carrillo (mcp at tid.es<mailto:mcp at tid.es>)
Subject: [old-Fiware-WP11 Exploitation] First version of FIWARE Periodic and Final report
Dear Colleagues,
First draft of progress report with all inputs (from leaving partners on M36 ) has now been uploaded and is available for your review also suggested changes/improvements. Please complete it with your contribution
WP11: https://docs.google.com/document/d/10llFWWZsZXCc61uZVb_1U_P2ZwHWtimWxmlC1IBydGc/edit#<https://docs.google.com/document/d/10llFWWZsZXCc61uZVb_1U_P2ZwHWtimWxmlC1IBydGc/edit>
Actions:
1) ALL WP11 partners: introduce your contribution per task before the 6th of February EOB
- Task 11.1: Market and Competition Analysis
- Task 11.2: Exploitation Strategy, FIWARE sustainability and IPR management
- Task 11.3: Establishing Market and Policy Regulation Awareness
- Task 11.4: Contribution to Standardization
- Task 11.5: Community Building and Engagement Platform
2) NEC Please review the content of 11.4 Standardization and complete it
Thanks in advance for your cooperation and support.
Best Regards
Juan
Da: Garino Pierangelo
Inviato: martedì 20 gennaio 2015 12:23
A: 'old-fiware-i2nd at lists.fi-ware.org'
Oggetto: I: [Old-Fiware] FIWARE Periodic and Final reports
Dear FI-WARE I2ND Partners,
As the mails below have pointed out, we are requested to complete the final Periodic report of the FI-WARE project.
You might remember that we already prepared a nearly-final version last April (M36), when most of you completed their active work in the project.
Those contents have been already included in the WP7 google docs document (link below).
There are however a number of actions to do, although most of them should end up with checks rather than practical contributions, which I summarise in the following:
1. Complete WP introductory part of the report. This must be done by myself, and I'll do it starting on Fri 23 Jan.
2. Complete/update each Task introductory part. This will require a joint effort between the Task coords (Chris, Henk, Thomas, Hans) and myself. Please have a look and propose any update you want to do. We need to complete this by Tue 27 January.
3. Check that the contribution of each partner to Task descriptions is complete, exhaustive and well described. Each Partner has to check this and contribute by Tue 27 January. One remark: there cannot be lists of actions left for next project period, as the project is finished! There can be however references to future releases of FIWARE (there are already some), as the platform and the GEs can extend beyond the project lifetime.
4. An update to the effort table is necessary: this must be done by TID, who should do it asap. Once available, it can happen that some partner will need to justify usage of higher or lower efforts compared to DoW. In such a case, Partners in that situation will have to provide the requested justification. Each Partner should check the effort table and insert justification by Mon 2 Feb, if required. I suggest you wait until mid of next week before checking this part, so that the update by TID should be available.
- How to provide an update:
o I assume the google doc is read-only for you. You can download it as MSWord, activate the track changes, make any update you have to do and send the resulting doc to me.
o Whether you need to make updates or not, please send me a mail telling that you did (or reviewed) them.
Thanks a lot in advance for your final support in completing the FI-WARE documentation. We'll stay in contact up to the review meeting.
BR
Pier
Da: old-fiware-bounces at lists.fi-ware.org<mailto:old-fiware-bounces at lists.fi-ware.org> [mailto:old-fiware-bounces at lists.fi-ware.org] Per conto di MIGUEL CARRILLO PACHECO
Inviato: martedì 20 gennaio 2015 11:05
A: old-fiware at lists.fi-ware.org<mailto:old-fiware at lists.fi-ware.org>
Oggetto: Re: [Old-Fiware] FIWARE Periodic and Final reports
Dear all,
Two important warnings:
* Let me emphasize that this is not "another reporting period". It is the final one and there are serious differences. Not delivering the report on time (in February) would imply the automatic rejection of the costs of all the partners in the 3rd period. We therefore urge you to swiftly provide the data we need, there are many partners and this is extremely complex.
* We have been discussing the matter with the PO and the review will not take place before April
Best regards,
Miguel
El 19/01/2015 a las 19:42, SANTIAGO MARTINEZ GARCIA escribió:
Hi all,
Deadlines for submitting the FIWARE periodic report (M25- M44, May 2013 - December 2014) and final Project report to the EC are getting closer, so we need to start working on this straightaway, to avoid risks in obtaining the expected funding.
Instructions for Work Package Leaders
· We will draft this report collaboratively between the different WPL. For doing this, we will use Google Docs. Each WPL will own the Google Doc corresponding to the WP he/she leads, and use it as the working document for him/her and the partners of the specific WP.
· Each WP doc contains 6 sections with a template and specific instructions on how to complete the info. Text from previous report has also been copied there, in case it may be useful for you as a reference , to be updated and adapted to the given template. It is important to follow these guidelines, since the report needs to be homogeneous.
You can find a completed example for WP6, in case you find it useful at:
https://docs.google.com/document/d/16-6oVZd1Yya0xOzHTj9MT7h-OWtljIkQMvQOjfX1gvI
· Links to the WP working docs (please let me know in case I missed to give edit permission to any WPL. All docs are viewable for all the Consortium):
WP1: https://docs.google.com/document/d/1sSvwKrozwefp-Q0tDMumJ4uvU3ZCycvU0-j35egNoY8
WP2: https://docs.google.com/document/d/1sm2SueeWgi79sCTkAva71n60_P9doSA0XNxbPvTwHoE
WP3: https://docs.google.com/document/d/1RhHiLV1aaTh_e_4D3EK1OyFQbS5HvlODoRk-ad9syLo
WP4: : https://docs.google.com/document/d/1BKr1FZpa0xyPNETB7gEkdiyT_8V-8ccJBTVRuKo98Yc
WP5: https://docs.google.com/document/d/1B17lOH9Ty959jc_zvWcAKVGM4pfHBv5AYxsb0izgVxM
WP7: https://docs.google.com/document/d/1yLLR5sDxR4BrzST7QsKHMUHN68Wg_AZhxc3LIkWNLQQ
WP8: https://docs.google.com/document/d/1D2QVAGnEVkfhjZUmli2PS4i8051b8fPMoCAs5BFrEYg
WP9: https://docs.google.com/document/d/1IgoVQXtQiJ-8FrAdupOBnAwZx7mUXAiuBh_RpEwc-Ts
WP10: : https://docs.google.com/document/d/1kUUTtpWkEFnz_3j-S63k6TVjLHqOvf_Gwc5PRBy4WXs
WP11: https://docs.google.com/document/d/10llFWWZsZXCc61uZVb_1U_P2ZwHWtimWxmlC1IBydGc
WP12: https://docs.google.com/document/d/1TbEpS7gc2r7JIQa8jGDOAE6tqqSJYYChDqbTn_N5oDY
WP13: https://docs.google.com/document/d/1K9WngtdMsLH9Rz1ciB0jLdUQXeNilB49tlmjGyk8604
· There is also a "main" Google Doc that will be used as the integration doc for all the WPL reports, and that currently contains links to the sections expected to be provided by each WPL. This will be the basis for the peer review of the report, to be performed by the Consortium, so the info contained there needs to be stable. Currently, it contains links to all the sections where contribution from WPLs is expected.
As soon as a WPL has available a complete final version of a section(s) under his/her responsability, he/she should copy it in this main doc. The intention is that all partners can review as soon as posible the available material in this doc, and make the peer review more agile.
Link to the integration doc (every WPL has edit permission. Viewable by all Consortium):
https://docs.google.com/document/d/1TpsBPDkXoz4gsL8RkrnJxCsRNgfdJAXadkajY9F2t2o
Calendar for this work
· Contributions to periodic report by Work Package Leaders: 19th Jan - 2nd Feb.
· Closure of WPL contributions and fisrt draft of periodic report available: 2nd Feb.
· Peer review for periodic report: 2nd Feb- 9th Feb.
· Submission of periodic report to EC and reviewers: 9th Feb.
In parallel, we will soon start the work on the final Project report, as well. The calendar for the work on the final report will be:
· First draft of final report (TID): 26th Jan.-2nd Feb.
· Contributions to final report: 2nd Feb-9th Feb.
· Submission of final report to EC and reviewers: 9th Feb.
In case you have any question at this point, or during your report elaboration, please let me know. It is very important we don't miss these deadlines.
Many thanks for your collaboration,
Santiago.
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Old-Fiware mailing list
Old-Fiware at lists.fi-ware.org<mailto:Old-Fiware at lists.fi-ware.org>
https://lists.fi-ware.org/listinfo/old-fiware
--
Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>
Follow FIWARE on the net
Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.
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 endeavors 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 información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico 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 ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-exploitation/attachments/20150216/b9abd864/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-exploitation/attachments/20150216/b9abd864/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy