Dear colleagues, I would like to share some impressions after reading the available information in google drive and before the next call. I know it is always easier to criticize and comment what others have done, but I hope it is useful in any case and helps the proposal to get better. Meeting in London First thing I wanted to ask if there is an agenda available for the meeting in London. I saw some pointers to logistics information (location, etc), but I am not sure if the agenda was circulated-. Here again I saw some e-mails from Martin related to it, but I am not sure if I missed something. Thanks for clarification. I have some personal constraints on Monday and I thought to be there on Tuesday and Wednesday (I could stay longer on Wednesday to work on the proposal if you feel that is useful...it depends on others' logistics). However, I would not like to miss a slot where we are expected to contribute heavily. That is why the agenda would help quite a lot. Maybe now you can take into consideration this issue :). Comments on WPs WP1. · WP1 points out that we will identify the set of enablers, infrastructure and so on and so forth for the pilots; we may better say that we will maintain and evolve dynamically the elements of this framework. As it is written it seems like we were going to identify all this at the project stage, but the baseline should already be provided at proposal stage. Especially in the case of this project, since we expect to show results very quickly, this work should be partially done before submitting the proposal and evaluators should get the impression that this knowledge is already in place · WP1 includes the pilot set-up and validation methodology --> any conflict with WP4 · The WP mentions that the pilot set-up will happen in WP4. Is that right? WP4 seems to refer more to the validation than the set-up of the pilot, which in the end is a kind-of combination of WP2 and WP3 · Task on Privacy, Trust and security --> you may want to mention here the recently approved data privacy regulation · For the last task on the pilot methodology we may also try to provide a first set of metrics/KPIs at proposal stage. I am sure you already have access to some of the evaluation frameworks currently in use. --> here again I have seen that WP4 will take care of it!! WP2 · Based on the last version uploaded by Sergio I can see that here all reference zones will become OASC-compatible (or the term you may want to use). I understand that if we want to be convincing in front of evaluators we should include a brief analysis of the AS-IS situation in each of the reference zones and the overall description of what needs to be done to reach the TO-BE situation. Maybe this is not needed here, but then I suppose it would be beneficial to have it in a different section of the proposal WP3 · I think we need to revise some of the concepts to avoid overlaps. WP3 says that we will connect the IoT infrastructure to the WP2 middleware. But I understand this is part of what WP2 will address, unless we are more specific and we refer to the Specific IoT infrastructural elements needed by those services · Methodology to select and implement a generic IoT service? I could imagine this as part of WP1. Maybe I am wrong · Here I would like to add a couple of IMPORTANT comments o The workprogramme makes clear that services should come from the user/citizens' needs --> we should point out the way services have already been identified at proposal stage (in line with WP1 concepts)- This also answers some of the concerns by the cities about having some selecting services on their behalf o The workprogramme asks proposals to go for at least some (few) VERY INNOVATIVE services to experiment with regulations and other "not-so-clear" conditions. Specifically they say "solutions that are at the edge of authorised business practices or regulation (ex: sharing of electricity, autonomous vehicles) and thus require dedicated testing zones --> I think we are missing this · In general I would say that this WP should talk more about needs and functionalities and less about technology, or at least it should be more balanced WP4 · T4.3 Stakeholder and market validation --> Of course stakeholder validation means that the user is also included. However, I think that user involvement should appear very explicitly here accompanied by the way we have planned to do so (maybe different depending on the cities...but following learning experiences of Living Labs, etc). I think that as part of this exercise we should include numbers of users/citizens that will be involved in different (phases?) of the validation process · On the other hand I wonder to which extent we will be able to provide market validation in a realistic way. I think it is fine including it, but maybe we should be more specific in what is included here Do we have a draft version of the other WPs? I did not see them. As you can see, looking at it from outside it seems the boundaries of some of the WPs are not so clear but I suppose it is normal at this stage. Maybe the most worrying thing is that I feel that for an evaluator it will be difficult to perceive the added value of this workplan in comparison to the work plan of other proposals. Of course this can be solved if the most strategic aspects are well described in the beginning of the proposal, but we are not there yet. We have to be convincing in showing why OASC is the winning bet. That will be already a lot. If a lot of people are already defining standard data models. I know people from UPM doing that since some years ago, what is new now? Why is our approach "the one"? Again, I know it is easier to make the questions than to provide the answers, but I should say it :). Talk to you on Wednesday, 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 01D17DFD.A928DB40] Feel free to download our booklet at http://atos.net/en-us/home/we-are/insights-innovation/research-and-innovation.html 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/20160314/ba2cb79d/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/20160314/ba2cb79d/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/20160314/ba2cb79d/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy