[Fiware-webui] Fwd: [Fiware] Start of the 2nd year reporting. We need work from ALL

Torsten Spieldenner torsten.spieldenner at dfki.de
Tue Jan 10 16:42:27 CET 2017


Dear all,

there are now contributions from DFKI and Cyberlightning. Adminotech is 
still missing. Please note that there is also input requested for WP 22. 
Our internal deadline is _today by the end of day_.



Best,

Torsten


Am 05.01.17 um 9:26 AM schrieb Torsten Spieldenner:
>
> Good morning,
>
> this is a reminder that your contributions for the 2nd year reporting 
> are due in the document linked below (row WP15). This is similar to 
> what we've already done for the report last year, means, each partner 
> please check for their company and fill in contributions and results, 
> as well as deviations and proposed actions, where it applies. Please 
> note that each partner appears several times in the report, as the 
> report is structured by sets of GE's as they are organized in our 
> chapter (client GE, server core, application oriented ....)
>
> The official deadline for any contributions is *January 17th. *There 
> will be no option for late delivery. In case a partner missed the 
> deadline, the report will be submitted with a note that the partner 
> did not provide any report!
>
> For internal review and final fixes and changes,_*please provide your 
> inpute before end of January 10th.*_
>
>
> Thank you very much and best regards,
> Torsten
>
> -------- Weitergeleitete Nachricht --------
> Betreff: 	[Fiware] Start of the 2nd year reporting. We need work from ALL
> Datum: 	Wed, 21 Dec 2016 18:33:06 +0100
> Von: 	MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com>
> An: 	fiware at lists.fiware.org <fiware at lists.fiware.org>
> Kopie (CC): 	'JAVIER DE PEDRO SANCHEZ' 
> <javier.depedrosanchez at telefonica.com>, JUAN JOSE HIERRO SUREDA 
> <juanjose.hierro at telefonica.com>
>
>
>
> 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/1eMgHbvaQBejfeXdxEBm1mwUoqIbIZByLe1pfOWZ-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--a8vPIYQVXYsUgPw8EmsfNFSdenfP9VKppGs/
> WP14
> 	IoT Services Enablement
> 	https://docs.google.com/document/d/1dUrC_rAcy-RDZdDPdUz3XRrxNhA66TeAralQdzIPqPM/
> 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/1LDGy1ReFpLBcV9t0XfcyqM3XzjJlG5_VQz9hjydzlgY/
> WP21
> 	FIWARE Ops Tools
> 	https://docs.google.com/document/d/1tz-Nb1xd_7eBOhsslXquFCUjE9c4TN0Gyq2FmqYeU9U/
> WP22
> 	FIWARE Lab Setup and Operation
> 	https://docs.google.com/document/d/1QNFRaQWkm5J90J0xqjU6VKZuz_XmCOqPc2hUbC0on1k/
> WP31
> 	Sustainability Support Tools
> 	https://docs.google.com/document/d/1Ahl4rDQYyJvMeBQxNZT2Gha8xgEbDZLvoIO4DPfGD_w/
> WP32
> 	Sustainability Model Definition and Activities
> 	https://docs.google.com/document/d/1Oc7IKsf0oU6nGJhMdyubQVyfEvUA_gLIbcfd70maqXk/
> WP33
> 	Exploitation
> 	https://docs.google.com/document/d/1SRsnaFzYfIzIEUTJUPSLfl6g0ER7GtMCOKS1Gf0gHcI/
> WP41
> 	Project Management
> 	https://docs.google.com/document/d/1o9ojsHHuaYcvtxRhWpq3dGqgi-czSvP-f-KyPpqDjtE/
> WP42
> 	Communication, Collaboration and Dissemination
> 	https://docs.google.com/document/d/1sCkzT6cpcaHEXbFqdbyqvAukBlkQBLGEHo3pczuV4Fc/
>
> 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
>
>
> 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
>
>                           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
> ----------------------------------------------------------------------

-- 
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-webui/attachments/20170110/72b3a4c6/attachment.html>


More information about the Fiware-webui mailing list

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