[Fiware-tools] Fwd: [Fiware-chapter-leaders] FI-Core: Evaluation of each WP by the WPL pending in the Periodic Report. (*** IMPORTANT & URGENT ***)

Davide Dalle Carbonare davide.dallecarbonare at eng.it
Thu Jan 26 12:20:23 CET 2017


Dear Pedro,
  you should have received this message directly.

Just to be sure you report the proper information and maybe a sentence
about the underspending in WP31.

BR
Davide


Davide Dalle Carbonare
Senior Researcher - Big Data & Future Internet
Engineering Ingegneria Informatica S.p.A. - www.eng.it
Mob: +39-346-3207983
@davdalle <https://twitter.com/davdalle> | linkedin
<https://www.linkedin.com/in/davidedallecarbonare> | about.me
<http://about.me/davidedallecarbonare>

---------- Forwarded message ----------
From: JAVIER DE PEDRO SANCHEZ <javier.depedrosanchez at telefonica.com>
Date: 2017-01-24 16:30 GMT+01:00
Subject: [Fiware-chapter-leaders] FI-Core: Evaluation of each WP by the WPL
pending in the Periodic Report. (*** IMPORTANT & URGENT ***)
To: "fiware-chapter-leaders at lists.fiware.org" <
fiware-chapter-leaders at lists.fiware.org>, "
fiware-wg-leaders at lists.fi-ware.org" <fiware-wg-leaders at lists.fi-ware.org>
Cc: "fiware-chapter-architects at lists.fiware.org" <
fiware-chapter-architects at lists.fiware.org>, eu_research <
eu_research.tid at telefonica.com>


Dear Chapter Leaders of FI-CORE project,

I’m glad to inform you that all the partners have already declared their
consolidated effort and we have integrated them (We have received the last
one today).



So, I kindly ask you to provide an evaluation (according the second period
and the final status) of your WP in the following shared document:
https://docs.google.com/document/d/14fnSAUVOlTxQMDddrjfCDFoycADJr
2ozmuGSpPOLpws



This document will be included in the Periodic Report.



*Deadline: Thursday 26th of January 2017, EOB.*



The summary is the following:







Thank you for your collaboration.



BR

Javier.



Javier de Pedro Sánchez

Telefónica I+D



*De:* JAVIER DE PEDRO SANCHEZ
*Enviado el:* jueves, 29 de diciembre de 2016 18:41
*Para:* ficore-administrative at lists.fi-ware.org
*CC:* eu_research <eu_research.tid at telefonica.com>
*Asunto:* FI-Core: Consolidated effort from M26 (Oct 2016) to M28 (Dec
2016) & Reporting of effort (Periodic Report) (*** IMPORTANT ***)
*Importancia:* Alta



Dear all,



In another particularized e-mail, I’m going to ask you for:

·         *your consolidated effort in FI-CORE project from M26 (Oct 2016)
to M28 (Dec 2016). *



Please take in account that your effort has to match with the FORM-C-3 that
will be managed in January-February 2017 on NEF.



Please, answer me *by January 15th, 2017. *Please share this e-mail with
your technical teams of your company, and take in account the e-mail below
from Miguel.

To avoid spam, I suggest that you don’t copy the admin list in your
response.



As soon as I have received your data, I’ll update the following document:
https://docs.google.com/document/d/14fnSAUVOlTxQMDddrjfCDFoycADJr
2ozmuGSpPOLpws

Then, we´ll need you to explain your deviation between the declared effort
and the expected one (DoW).

This document will be included in the Periodic Report.



Thank you in advance for your collaboration.

I wish you all an Happy New Year 2017.



BR

Javier.

Telefónica I+D





*Asunto: *

Start of the 2nd year reporting. We need work from ALL

*Fecha: *

Wed, 21 Dec 2016 18:33:06 +0100

*De: *

MIGUEL CARRILLO PACHECO

*Para: *

fiware at lists.fiware.org

*CC: *

JUAN JOSE HIERRO SUREDA , 'JAVIER DE PEDRO SANCHEZ'



Dear all,

As announced in the coordination call today, we have launched the 2nd year
report. We have made available the links to edit it for all partners. They
are here:

WP11

Global FIWARE Technical Coordination

https://docs.google.com/document/d/1eMgHbvaQBejfeXdxEBm1mwUoqIbIZ
ByLe1pfOWZ-yig/

WP12

Cloud Hosting

https://docs.google.com/document/d/1j-HIjlqEpjPGn1TlEbxGRb8WzzKDQ_
3zWOIqeBGhI5M/

WP13

Data/Media and Context Management

https://docs.google.com/document/d/1MbIgnZ--a8vPIYQVXYsUgPw8EmsfNFSdenfP9V
KppGs/

WP14

IoT Services Enablement

https://docs.google.com/document/d/1dUrC_rAcy-RDZdDPdUz3XRrxNhA66TeAralQdzIP
qPM/

WP15

Advanced Web-based User Interfaces

https://docs.google.com/document/d/1aQm0EeyGVH_oNSxKUfkN-
AR007k8HfL7VyFjfHPtE9Q/

WP16

Apps/Service and Data Delivery

https://docs.google.com/document/d/1HZeUZFa1cPZ2eF-
kjG_eNI5PtVPJzL2HHf-YHQDQZP0/

WP17

Security

https://docs.google.com/document/d/11DRpLGrJnyhrWECqka_
o9uTWCmve16wkE3ycGwozzKw/

WP18

Advanced Middleware and Interfaces to Networks and Robotics

https://docs.google.com/document/d/1LDGy1ReFpLBcV9t0XfcyqM3XzjJlG
5_VQz9hjydzlgY/

WP21

FIWARE Ops Tools

https://docs.google.com/document/d/1tz-Nb1xd_7eBOhsslXquFCUjE9c4TN0Gyq2FmqY
eU9U/

WP22

FIWARE Lab Setup and Operation

https://docs.google.com/document/d/1QNFRaQWkm5J90J0xqjU6VKZuz_
XmCOqPc2hUbC0on1k/

WP31

Sustainability Support Tools

https://docs.google.com/document/d/1Ahl4rDQYyJvMeBQxNZT2Gha8xgEbD
ZLvoIO4DPfGD_w/

WP32

Sustainability Model Definition and Activities

https://docs.google.com/document/d/1Oc7IKsf0oU6nGJhMdyubQVyfEvUA_
gLIbcfd70maqXk/

WP33

Exploitation

https://docs.google.com/document/d/1SRsnaFzYfIzIEUTJUPSLfl6g0ER7G
tMCOKS1Gf0gHcI/

WP41

Project Management

https://docs.google.com/document/d/1o9ojsHHuaYcvtxRhWpq3dGqgi-
czSvP-f-KyPpqDjtE/

WP42

Communication, Collaboration and Dissemination

https://docs.google.com/document/d/1sCkzT6cpcaHEXbFqdbyqvAukBlkQB
LGEHo3pczuV4Fc/

You are requested to report on your activity in the project in Year 2, from
M14 (Oct/2015) till M28(Dec/2016). You cannot report activity before M14 or
after M28.

*These links and the information within are FIWARE confidential*

Deadline: *17/January*

*Important guidelines*:

   - The *WPLs* are expected to check that the partners per task are the
   right ones according to the current DoW (amendment 2)
   - The *WPLs *are expected to do periodic backup of their part (weekly,
   at least!). This is more serious than you may think, someone may delete all
   by mistake and then we would have a problem.
   - The *WPLs *are expected to fill in the "general" parts of their
   WPs/chapters
   - The *WPLs *are expected to ensure that all is consistent, have good
   quality and that all is delivered on time (Jan, 17). If they throw at me
   things that are in bad shape, they will have a negative observation in the
   report from the coordination
   - The *WPLs *are expected to send reminders to the partners who failed
   to fill in their part.
   - *All the partners* have a clear entry in all the tasks where they
   contribute.
   - If the do not have anything to report, *they do not delete their
   entry. *They state "*Nothing to report in this reporting period*". This
   is entirely unambiguous (deleting your entry leaves room to think that
   maybe it is an oversight and that we forgot this partner).
   - If a given *partner *fails to provide their inputs, I will waste no
   time. If someone is not interested in claiming money from the EC, I respect
   it. In the cases of partners with no info (or those who disregard the
   previous bullet point and delete their entries), I will add this in
red: "*This
   partner did not contribute contents to this part despite the requests of
   the coordination*"
   - We will request financial info in January at a later stage
   - We will also start the creation of the Final Report soon (it is a
   different report from the one we are talking about in this message)
   - If it helps, this is the previous report as we delivered to the
   EC.(you may find change tracking but this is how we delivered it for
   reasons that are out of the scope of this interaction):
   https://drive.google.com/file/d/0B6GGeaQGro3fZEpzSkZQd21PWWs/
   view?usp=sharing
   <https://drive.google.com/file/d/0B6GGeaQGro3fZEpzSkZQd21PWWs/view?usp=sharing>

Regards,

Miguel

--



Please update your address book with my new e-mail address:
miguel.carrillopacheco at telefonica.com



----------------------------------------------------------------------

     _/          _/_/                     Miguel Carrillo Pacheco

    _/   _/     _/  _/   Telefónica       Distrito Telefónica

   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 6

  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N

 _/          _/_/                         28050 Madrid (Spain)

                                          Tel:  (+34) 91 312 94 15
<+34%20913%2012%2094%2015>



                         e-mail: 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

----------------------------------------------------------------------


____________________________________________________________
______________________________

You can get more information about our cookies and privacy policies on the
following links:
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/
index.php/FIWARE_Privacy_Policy
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/
index.php/Cookies_Policy_FIWARE

Fiware-chapter-leaders mailing list
Fiware-chapter-leaders at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-chapter-leaders
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tools/attachments/20170126/e61fcfcc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 57542 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-tools/attachments/20170126/e61fcfcc/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 48473 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-tools/attachments/20170126/e61fcfcc/attachment-0003.jpg>


More information about the Fiware-tools mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy