Hi Bram, Thanks for the WP1 material. I have revised it and I have corrected some typos. Find my revision attached with track changes. In general I would say that it reflects well what is needed. However, let me add a couple of comments that are personal impressions (so, I may be wrong, but some evaluators may think the same). · Since these are general guidelines for the reference zones and in general for all the other WPs, should not we include important words like replication or large scale here? I understand that they are well covered by the WPs concerned, but I am surprised that important drivers of the project are not even mentioned. Ability to replicate should be somehow one of these elements that require clear guidelines in the beginning of the project · The second comment is that it gives the impression that we are starting from scratch with all the reference zones in terms of co-creation, citizen-engagement, etc, like if all of them were at the same level or like if we were asking all of them to proceed as we want (kind-of top-down approach), but most of them have many of these mechanisms in place (Living Labs, etc). It may be good to acknowledge the different degrees of development of these methodologies and mechanisms in the cities involved and that the support in each of them may be different. In summary, it seems like if we were ignoring what is already in place. But, as said, it is just an impression. Regarding resources, I think Atos rather prefers to concentrate efforts based on the last comments made by Martin. So, in principle there is no need to include us in T4.1 (I include my colleague Clara in CC who is evaluating resources for us). Best regards, Nuria de Lama Research & Innovation ICT Program Manager Vice-Secretary General Big Data Value Association M +34 680645692 T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net<mailto:nuria.delama at atos.net> Albarracín 25 28037 Madrid Spain www.atosresearch.eu<http://www.atosresearch.eu/> es.atos.net [cid:image002.png at 01D19168.FC5B4040] Feel free to download our booklet at http://atos.net/en-us/home/we-are/insights-innovation/research-and-innovation.html From: fiware-oasc-iot-lsp-cities-bounces at lists.fiware.org [mailto:fiware-oasc-iot-lsp-cities-bounces at lists.fiware.org] On Behalf Of Bram Lievens Sent: Thursday, April 07, 2016 11:59 PM To: Fiware-oasc-iot-lsp-cities at lists.fiware.org Subject: [oasc-iot-lsp-cities] WP 1 budget allocations Dear all, Please do find in attach the latest version of WP1 as well as a budget allocation for each partner. As almost all partners are contributing, please do revise. Deadline for this April 8, 2016 - 10h30 CET. Below the rationale behind the figures and the balancing between efforts and type of partners 1. The core work is done by tasked and/or those with substantial efforts. The efforts between the other partners is being balanced as the resources needed to contribute / execute would be the same. 2. For the cities - the main efforts is within T1.1 (mainly for installing the engagement tools and engage with the local eco-system), limited effort is given for T1.2 and T1.3 (for task 1.2 it is contributing on the guidelines, mainly on the architecture part - for task 1.3 is to provide periodic updates for the monitoring) 3. For the technical partners efforts are focused on the contribute to task 2 on the architecture guidelines (which also feeds into T2.1) . the more larger IT partners / with strong connection to the cities - we also provided some effort to contribute to the monitor task (T1.3) 4. For T1.4 we have limited the efforts to mainly to groups like AI, iMinds, FCC that have a core business in user-centered approaches. Some cities are also having some mm there (mainly to contribute from a city-perspective), but this can still potentially change 5. For the taskleaders have for their (sub)task allocated more mm Some specific questions / point of attention: @Sofia / FCC: in consult with Martin we made you task lead for T1.3 (replacing Adrian) - can you look that the effort spread is ok @Engineer: you provide a rather high allocation of MM @Nuria/ATOS: can you confirm you will have no efforts in WP1? > in London you mentioned contribution to T1.4 ATOS WARNING ! This message contains attachments that could potentially harm your computer. Please make sure you open ONLY attachments from senders you know, trust and is in an e-mail that you are expecting. AVERTISSEMENT ATOS ! Ce message contient des pièces jointes qui peuvent potentiellement endommager votre ordinateur. Merci de vous assurer que vous ouvrez uniquement les pièces jointes provenant d’emails que vous attendez et dont vous connaissez les expéditeurs et leur faites confiance. AVISO DE ATOS ! Este mensaje contiene datos adjuntos que pudiera ser que dañaran su ordenador. Asegúrese de abrir SOLO datos adjuntos enviados desde remitentes de confianza y que procedan de un correo esperado. ATOS WARNUNG ! Diese E-Mail enthält Anlagen, welche möglicherweise ihren Computer beschädigen könnten. Bitte beachten Sie, daß Sie NUR Anlagen öffnen, von einem Absender den Sie kennen, vertrauen und vom dem Sie vor allem auch E-Mails mit Anlagen erwarten. [cid:image003.gif at 01D19168.FC5B4040] Bram Lievens | T +32 9 248 55 36 | M +32 478 72 01 54 E bram.lievens at iminds.be<mailto:olivier.rits at iminds.be> | W iminds.be<http://iminds.be/> A AA Tower - Technologiepark 19 - 9052 Zwijnaarde - Belgium .<mailto:olivier.rits at iminds.be> 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/fiware-oasc-iot-lsp-cities/attachments/20160408/68e8c585/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 159 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160408/68e8c585/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 13926 bytes Desc: image002.png URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160408/68e8c585/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 3679 bytes Desc: image003.gif URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160408/68e8c585/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: WP1-description_v2_NDL.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 44868 bytes Desc: WP1-description_v2_NDL.docx URL: <https://lists.fiware.org/private/fiware-oasc-iot-lsp-cities/attachments/20160408/68e8c585/attachment.docx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy