FYI.
BR
Javier.
De: old-fiware-bounces at lists.fi-ware.org [mailto:old-fiware-bounces at lists.fi-ware.org] En nombre de SANTIAGO MARTINEZ GARCIA
Enviado el: miércoles, 18 de febrero de 2015 16:36
Para: old-fiware at lists.fi-ware.org
Asunto: [Old-Fiware] RV: FIWARE Periodic and Final reports
Dear all,
This is a last call for including partner’s missing activity reports in the M25-M44 FIWARE Periodic report.
Please look for your company name in the list below, which shows the current missing partner activity reports, and include your contributions in the corresponding WP Google Doc by end of this week.
I don’t guarantee being able to process any contribution provided later than this, so partners which fail again to do this will be in a very high risk of being reflected as “no input from this partner” in the overall periodic report . Report will be submitted during next week.
TID:
- WP4 (missing activity report), WP12 (complete WPL sections?, review own activity report)
IBM:
-WP1 (missing activity report), WP4 (complete all WPL sections & own activity report), WP12 (review inputs: collaboration/dissemination events have been taken from other deliverables)
Thales:
-WP1 (missing activity report), WP4 (missing activity report), WP6 (missing activity report in task 6.3)
TI:
-WP1 (missing activity report), WP2 (missing activity report), WP12 (review inputs: collaboration/dissemination events have been taken from other deliverables)
Orange:
-WP1 (missing activity report), WP2 (missing activity report),WP6 (missing activity report), WP8 (WPL waiting for further input/clarification), WP10 (missing activity report), WP12 (review inputs: collaboration/dissemination events have been taken from other deliverables)
Red.es:
-WP1 (missing activity report),WP10 (missing activity report), WP12 (missing activity report)
Zhaw:
-WP1 (missing activity report), WP13 (complete WPL sections & own activity report)
NSNG:
-WP2 (missing activity report)
NSNG1:
-WP2(missing activity report), WP10 (missing activity report)
NSN-H:
-WP10 (missing activity report), WP12 (missing activity report)
TRDF:
-WP2 (missing activity report), WP4 (missing activity report), WP11 (missing activity report), WP12 (missing activity report)
ALU-I:
-WP2 (missing activity report), WP11 (missing activity report), WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
Intel:
-WP2 (missing activity report), WP4 (missing activity report), WP12 (missing activity report)
Fraunhofer:
-WP2 (missing activity report), WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
University of Surrey:
-WP2 (missing activity report), WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
DFKI:
-WP2 (missing activity report), WP11 (missing activity report), WP12 (missing activity report)
USAAR-CISPA:
-WP2 (missing activity report), WP11 (missing activity report), WP12 (missing activity report)
EPROS:
-WP2 (missing activity report), WP11 (missing activity report), WP13 (missing activity report)
Ludocraft:
-WP2 (missing activity report), WP12 (missing activity report)
ULPGC:
-WP2 (missing activity report), WP12 (missing activity report)
UFC:
-WP2 (missing activity report)
ONE:
-WP2 (missing activity report)
Inria:
-WP4 (missing activity report), WP10 (missing activity input), WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
UPM:
-WP4 (missing activity report)
E-IIS:
-WP10 (complete WPL sections & review own activity report)
Bismart:
-WP10 (missing activity report), WP12 (missing activity report)
ATOS:
-WP11 (complete WPL sections 3, 4 and 6).
Nuria to edit section 2.3.10 “Communication and Exchanges with related projects, initiatives and organizations” in the integrated periodic report
https://docs.google.com/document/d/1TpsBPDkXoz4gsL8RkrnJxCsRNgfdJAXadkajY9F2t2o/edit
Ogilvy-OG1:
-WP12 (missing activity report)
Up Europe:
-WP12 (missing activity report)
ALU-D:
-WP12 (missing activity report)
UniRoma:
-WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
COS:
-WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
NLNET:
-WP12 (missing activity report)
FBK:
-WP12 (missing activity report)
Top Digital:
-WP12 (missing activity report)
UC:
-WP12 (missing activity report)
VTT:
-WP12 (missing activity report)
ALFA:
-WP12 (missing activity report)
DRI:
-WP12 (missing activity report)
FIT:
-WP12 (missing activity report)
IPN:
-WP12 (missing activity report)
INNDEA:
-WP12 (review input: collaboration/dissemination events have been taken from other deliverables)
JMP:
-WP12 (missing activity report)
LCU:
-WP12 (missing activity report)
Many thanks,
Santiago.
De: SANTIAGO MARTINEZ GARCIA
Enviado el: viernes, 30 de enero de 2015 15:14
Para: 'old-fiware at lists.fi-ware.org'
Asunto: RE: FIWARE Periodic and Final reports
Dear all,
Progress so far on the necessary reporting from each of the WPs is rather poor.
Let me highlight again its importance (especially in the final period), and that failing to do this can lead to undesired situations and problems.
I have also granted edit permissions to the WP2 and WP12 shared docs for all partners, after requests from UPM and Cyberlighting. I guess this means other partners from these WPs didn’t try yet to add their contributions to these docs. Please proceed to add your company’s activity report there asap.
For the rest of WPs, I can see there has been some progress in a few of them, but most remain in the same status as last week.
We are going to include your contributions to the general report for the period, on Tuesday 3th February.
Regards,
Santiago.
De: SANTIAGO MARTINEZ GARCIA
Enviado el: lunes, 19 de enero de 2015 19:42
Para: 'old-fiware at lists.fi-ware.org'
Asunto: FIWARE Periodic and Final reports
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
________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-administrative/attachments/20150219/7dd2f70b/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy